No update for a day on ports?

The Doctor doctor at doctor.nl2k.ab.ca
Sat Apr 3 03:27:38 UTC 2021


On Sat, Apr 03, 2021 at 07:45:56AM +0600, Muhammad Moinur Rahman wrote:
> Once it is publicly mentioned that the conversion is completed run the following command:
> 
> sed -e '/github.com/d' -e 's/freebsd\/freebsd-//g' /usr/local/etc/gitup.conf
> 
> then do `gitup ports`
> 
> Kind Regards,
> Moin
> 
> > On 3 Apr, 2021, at 07:20, The Doctor via freebsd-ports <freebsd-ports at freebsd.org> wrote:
> > 
> > On Fri, Apr 02, 2021 at 05:54:48PM -0700, Mark Millard via freebsd-ports wrote:
> >> 
> >> 
> >> On 2021-Apr-2, at 17:41, Mark Millard <marklmi at yahoo.com> wrote:
> >> 
> >>> The Doctor doctor at doctor.nl2k.ab.ca wrote on
> >>> Sat Apr 3 00:27:42 UTC 2021 :
> >>> 
> >>> Results:
> >>> 
> >>>> gitup -v 1 ports
> >>>> # Host: github.com
> >>>> # Port: 443
> >>>> # Repository: /freebsd/freebsd-ports.git
> >>>> # Target: /usr/ports
> >>>> gitup: get_commit_details: refs/heads/master doesn't exist in /freebsd/freebsd-ports.git: Invalid argument
> >>> 
> >>> When I look at:
> >>> 
> >>> https://github.com/freebsd/freebsd-ports/
> >>> 
> >>> and look at the popup for selecting a branch
> >>> I see a "main" but do not see a "master".
> >>> 
> >>> By contrast when I look at:
> >>> 
> >>> https://github.com/freebsd/freebsd-ports-legacy/
> >>> 
> >>> and look at the popup for selecting a branch
> >>> I see a "master" but do not see a "main".
> >>> 
> >>> It looks like the your gitup is configured for
> >>> before the conversion, when only the combination:
> >> 
> >> One aspect of the above sentence is poor: which
> >> "conversion"? It might not be the current
> >> svn to git one one. For all I know
> >> /freebsd/freebsd-ports-legacy/ could have existed
> >> under that naming for a while and
> >> /freebsd/freebsd-ports/ could have been tracking
> >> svn over the same time frame.
> >> 
> >>> /freebsd/freebsd-ports.git
> >>> refs/heads/master
> >>> 
> >>> existed. Since then the old /freebsd/freebsd-ports.git
> >>> was effectively renamed to /freebsd/freebsd-ports-legacy/
> >>> and a new /freebsd/freebsd-ports/ was created that used
> >>> "main" instead of "master".
> >> 
> > 
> > So what patch is needed to fix the ports issue?
> > 
> >> 
> >> ===
> >> Mark Millard
> >> marklmi at yahoo.com
> >> ( dsl-only.net went
> >> away in early 2018-Mar)
> >> 
> >> _______________________________________________
> >> freebsd-ports at freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> > 
> > --
> > Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
> > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
> > Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b
> > If they can dehumanize the most innocent, they can dehumanize anyone.  -unknown
> > _______________________________________________
> > freebsd-ports at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> 

50/50 .

FreeBSD 13.0-RC workstation works.

Ns2 works

ns1 is hung up.


-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b  
If they can dehumanize the most innocent, they can dehumanize anyone.  -unknown


More information about the freebsd-ports mailing list