Re: No update for a day on ports?
Mark Millard via freebsd-ports wrote on 2021/04/02 08:13: >> On 4/1/21 6:04 PM, Tatsuki Makino wrote: >>> We have to learn by looking at such files. orz >>> https://git.wiki.kernel.org/index.php/File:Git-svn-cheatsheet.pdf >>> [...] > > Be careful: Git-svn-cheatsheet.pdf is about how to use git > with a svn server, not with a git server: > > "Cheatsheet for Git as an SVN Client" > > The "as an SVN Client" is what says that the > server involved is an SVN server. > I was using it only to find something similar to svn's commands among git's many incomprehensible commands. :) I didn't realize it had that kind of meaning. :) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
George Mitchell george+freebsd at m5p.com wrote on
Thu Apr 1 22:19:32 UTC 2021 :
> On 4/1/21 6:04 PM, Tatsuki Makino wrote:
> > Dewayne Geraghty wrote on 2021/04/01 17:47:
> >> [...]
> >> Would appreciate if anyone can provide insight as to the 4 git commands
> >> that I need to function, in a manner similar to the way I use svnlite
> >> use. Git equivalents for:
> >>
> >> svnlite update /usr/ports
> >> svnlite update -r '{$-$MM-$DD}' /usr/ports/$category/$port
> >> svnlite log -l $N /usr/ports/$category/$port
> >> svnlite diff /usr/ports/$category/$port
> >>
> >
> > We have to learn by looking at such files. orz
> > https://git.wiki.kernel.org/index.php/File:Git-svn-cheatsheet.pdf
> > [...]
>
> Thank you very much for this link! -- George
Be careful: Git-svn-cheatsheet.pdf is about how to use git
with a svn server, not with a git server:
"Cheatsheet for Git as an SVN Client"
The "as an SVN Client" is what says that the
server involved is an SVN server.
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
On 4/1/21 6:04 PM, Tatsuki Makino wrote:
Dewayne Geraghty wrote on 2021/04/01 17:47:
[...]
Would appreciate if anyone can provide insight as to the 4 git commands
that I need to function, in a manner similar to the way I use svnlite
use. Git equivalents for:
svnlite update /usr/ports
svnlite update -r '{$-$MM-$DD}' /usr/ports/$category/$port
svnlite log -l $N /usr/ports/$category/$port
svnlite diff /usr/ports/$category/$port
We have to learn by looking at such files. orz
https://git.wiki.kernel.org/index.php/File:Git-svn-cheatsheet.pdf
[...]
Thank you very much for this link! -- George
OpenPGP_signature
Description: OpenPGP digital signature
Re: No update for a day on ports?
Dewayne Geraghty wrote on 2021/04/01 17:47:
> On 1/04/2021 6:19 pm, Herbert J. Skuhra wrote:
>> https://wiki.freebsd.org/git
>>
> Thanks Milan for bringing this to everyone's attention.
>
> Would appreciate if anyone can provide insight as to the 4 git commands
> that I need to function, in a manner similar to the way I use svnlite
> use. Git equivalents for:
>
> svnlite update /usr/ports
> svnlite update -r '{$-$MM-$DD}' /usr/ports/$category/$port
> svnlite log -l $N /usr/ports/$category/$port
> svnlite diff /usr/ports/$category/$port
>
We have to learn by looking at such files. orz
https://git.wiki.kernel.org/index.php/File:Git-svn-cheatsheet.pdf
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
On 01 Apr 2021, at 01:54, Milan Obuch wrote: > This is unpleasant move for me. This means git or equivalent (and > dependencies) must be installed on any box where tracking ports tree is > planned/needed... and no tool like svnlite could be expected in base > system for some time. You only need to install git if you are going to keep git commit hostly and branches of the ports, which you would already be doing if that was something you needed, I'd think. Simply updating the ports tree does not require installing git. > So I need some work on my local infrastructure to adjust to this move. I don't think so, I am pulling the ports tree from the git repo without git installed. # portmaster -l | grep git ===>>> gitup-0.90_1 # -- I do believe Marsellus Wallace, my husband, your boss, told you to take *me* out and do *whatever I wanted*. Now I wanna dance, I wanna win. I want that trophy, so dance good. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Deprecation of portsnap (was: Proposed ports git transition schedule)
On 01 Apr 2021, at 04:19, Felix Palmen wrote: > * Christoph Moench-Tegeder [20210326 19:45]: >> ## Felix Palmen (fe...@palmen-it.de): >>> I'd assume (someone may correct me) that portsnap will still be >>> supported, >> https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119098.html > Is this finally decided, and is there a timeline? That post I read as the official decision that port snap was going to die. But WITHOUT_PORTSANP added to the default base would be the single, I'd think. Most of the ground work has already been done. > portsnap is still built by default on releng/13.0. We'll see if it makes it to RELEASE or not. gitup is working well right now, but it looks more fiddly and I wish the 'fake JSON' configuration file was actual valid JSON, OTOH, it seems o run a lot faster than portsnap. -- I WILL NOT TRADE PANTS WITH OTHERS Bart chalkboard Ep. 7F05 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Port's OpenSSL 1.1.1k, 1 on FreeBSD 11-STABLE shows strange error (Inappropriate ioctl for device) on handshake (Server-side)
On 01/04/2021 00:10, Lev Serebryakov wrote: System is 11.4-STABLE r366937. I've ports built with OpenSSL from ports (DEFAULT_VERSIONS+=ssl=openssl). After upgrade to latest 1.1.1k,1 my nginx reject HTTPS connections with cryptic SSL_do_handshake() failed (SSL: error:02015019:system library:ioctl:Inappropriate ioctl for device error:1427D044:SSL routines:construct_stateless_ticket:internal error error:02015019:system library:ioctl:Inappropriate ioctl for device) What happens? What did I do wrong? Previous OpenSSL version worked without problem. We are using FreeBSD 11.4 with port's OpenSSL too. Already deployed newer version of OpenSSL on all machines without any troubles. (Apache / Nginx / Lighttpd / Postfix / ProFTPd and some other openssl library consumers) Do you have any special SSL / TLS configuration in nginx.conf? (protocol version, ciphers etc.) Kind regards Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
D'Arcy Cain wrote on 01/04/2021 22:08: On 2021-04-01 4:55 a.m., Bob Eager wrote: I got a partial answer. There is a port, net/gitup, that will do an update of sorts. (Note: I was just told 'gitup' and there is an old port, now renamed 'git-up', which is not the right one). I just tried gitup and was told tha I had no permissions for /var/db/gitup. I just tried gitup and it was killed after apparently exhausting my swap space. I had no such problem with portsnap :-( My system (Vultr VPS) has 512K memory and 1.5G swap. > Can I not run gitup as a normal user? I don't believe so. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
Citerar D'Arcy Cain : On 2021-04-01 4:55 a.m., Bob Eager wrote: I got a partial answer. There is a port, net/gitup, that will do an update of sorts. (Note: I was just told 'gitup' and there is an old port, now renamed 'git-up', which is not the right one). I just tried gitup and was told tha I had no permissions for /var/db/gitup. Can I not run gitup as a normal user? Trying to run the latest poudriere from ports (git) and that seems to still use the subversion variant, or do I need to reinitialize something? Have I missed some migration guide for this? Cheers, Jimmy ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
On 2021-04-01 4:55 a.m., Bob Eager wrote: I got a partial answer. There is a port, net/gitup, that will do an update of sorts. (Note: I was just told 'gitup' and there is an old port, now renamed 'git-up', which is not the right one). I just tried gitup and was told tha I had no permissions for /var/db/gitup. Can I not run gitup as a normal user? -- D'Arcy J.M. Cain | Democracy is three wolves http://www.druid.net/darcy/| and a sheep voting on +1 416 788 2246 (DoD#0082)(eNTP) | what's for dinner. IM: da...@vybenetworks.com, VoIP: sip:da...@druid.net Disclaimer: By sending an email to ANY of my addresses you are agreeing that: 1. I am by definition, "the intended recipient". 2. All information in the email is mine to do with as I see fit and make such financial profit, political mileage, or good joke as it lends itself to. In particular, I may quote it where I please. 3. I may take the contents as representing the views of your company if I so wish. 4. This overrides any disclaimer or statement of confidentiality that may be included or implied in your message. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Illegal instruction on new port mongodb49 on arm64
On Thu, 2021-04-01 at 10:37 +0200, Ronald Klop wrote: > Hi, > > I created a new port for mongodb49: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254631 > It compiles fine: https://www.klop.ws/mongodb49-4.9.0.r0.log > > When I run an application I get "Illegal Instruction" error. > > == > [root@rpi4 /tmp]# lldb /usr/local/bin/mongo > (lldb) target create "/usr/local/bin/mongo" > Current executable set to '/usr/local/bin/mongo' (aarch64). > (lldb) run > Process 55420 launching > Process 55420 launched: '/usr/local/bin/mongo' (aarch64) > Process 55420 stopped > * thread #1, name = 'mongo', stop reason = signal SIGILL: illegal trap > frame #0: 0x016a320c mongo`___lldb_unnamed_symbol32$$mongo + 1784 > mongo`___lldb_unnamed_symbol32$$mongo: > -> 0x16a320c <+1784>: ldaddal x9, x8, [x8] According to [1], this instruction requires ARMv8.1. If I grep correctly, rpi4 is ARMv8-A. Yet you're compiling with -march=armv8.2-a, so it's a case of wrong -march. [1] https://developer.arm.com/documentation/100069/0608/A64-Data-Transfer-Instructions/LDADDA--LDADDAL--LDADD--LDADDL--LDADDAL--LDADD--LDADDL -- Best regards, Michał Górny ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
Citerar Bob Eager :
On Thu, 1 Apr 2021 19:47:01 +1100
Dewayne Geraghty wrote:
Would appreciate if anyone can provide insight as to the 4 git
commands that I need to function, in a manner similar to the way I
use svnlite use. Git equivalents for:
svnlite update /usr/ports
svnlite update -r '{$-$MM-$DD}' /usr/ports/$category/$port
svnlite log -l $N /usr/ports/$category/$port
svnlite diff /usr/ports/$category/$port
I got a partial answer. There is a port, net/gitup, that will do an
update of sorts. (Note: I was just told 'gitup' and there is an old
port, now renamed 'git-up', which is not the right one).
I'm sure many other users would have a similar usage (and similar
non-knowledge of git)
Indeed. I feel this should have been done in advance. And been in
Appendix A of the Handbook in plenty of time.
As a minor aside, has anyone stated the reason why the user-base of
base or ports are moving to git?
Going with the fashion, IMO. But I will no doubt get shouted down.
If it is deprecated where do I find the information I need, this does
not help:
https://docs.freebsd.org/en_US.ISO8859-1/books/handbook/ports-using.html
Cheers, Jimmy
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Deprecation of portsnap (was: Proposed ports git transition schedule)
Hallo Christoph,
* Christoph Moench-Tegeder [20210326 19:45]:
> ## Felix Palmen (fe...@palmen-it.de):
>
> > I'd assume (someone may correct me) that portsnap will still be
> > supported,
>
> https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119098.html
Is this finally decided, and is there a timeline? Right now, it seems
portsnap is still built by default on releng/13.0.
--
Dipl.-Inform. Felix Palmen ,.//..
{web} http://palmen-it.de {jabber} [see email] ,//palmen-it.de
{pgp public key} http://palmen-it.de/pub.txt // """
{pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A
signature.asc
Description: PGP signature
Re: Illegal instruction on new port mongodb49 on arm64
Van: "Micha? Górny" Datum: donderdag, 1 april 2021 10:47 Aan: Ronald Klop , freebsd-ports@freebsd.org, freebsd-...@freebsd.org Onderwerp: Re: Illegal instruction on new port mongodb49 on arm64 On Thu, 2021-04-01 at 10:37 +0200, Ronald Klop wrote: > Hi, > > I created a new port for mongodb49: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254631 > It compiles fine: https://www.klop.ws/mongodb49-4.9.0.r0.log > > When I run an application I get "Illegal Instruction" error. > > == > [root@rpi4 /tmp]# lldb /usr/local/bin/mongo > (lldb) target create "/usr/local/bin/mongo" > Current executable set to '/usr/local/bin/mongo' (aarch64). > (lldb) run > Process 55420 launching > Process 55420 launched: '/usr/local/bin/mongo' (aarch64) > Process 55420 stopped > * thread #1, name = 'mongo', stop reason = signal SIGILL: illegal trap > frame #0: 0x016a320c mongo`___lldb_unnamed_symbol32$$mongo + 1784 > mongo`___lldb_unnamed_symbol32$$mongo: > -> 0x16a320c <+1784>: ldaddal x9, x8, [x8] According to [1], this instruction requires ARMv8.1. If I grep correctly, rpi4 is ARMv8-A. Yet you're compiling with -march=armv8.2-a, so it's a case of wrong -march. [1] https://developer.arm.com/documentation/100069/0608/A64-Data-Transfer-Instructions/LDADDA--LDADDAL--LDADD--LDADDL--LDADDAL--LDADD--LDADDL -- Best regards, Micha Górny Hi, Thank you for the quick insight. Now I found this update upstream: https://jira.mongodb.org/browse/SERVER-55178 and https://github.com/mongodb/mongo/commit/8f708f3b68c3c85108294a8f58d780b6ccf18194 . Not much info why this was necessary though. I hate it when a commit message describes *what* changed instead of *why* it changed. The what is already in the diff. Anyways. Thanks for the reply. I think I'll need to try to contact somebody at MongoDB. Regards, Ronald. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
On Thu, 1 Apr 2021 19:47:01 +1100
Dewayne Geraghty wrote:
> Would appreciate if anyone can provide insight as to the 4 git
> commands that I need to function, in a manner similar to the way I
> use svnlite use. Git equivalents for:
>
> svnlite update /usr/ports
> svnlite update -r '{$-$MM-$DD}' /usr/ports/$category/$port
> svnlite log -l $N /usr/ports/$category/$port
> svnlite diff /usr/ports/$category/$port
I got a partial answer. There is a port, net/gitup, that will do an
update of sorts. (Note: I was just told 'gitup' and there is an old
port, now renamed 'git-up', which is not the right one).
>
> I'm sure many other users would have a similar usage (and similar
> non-knowledge of git)
Indeed. I feel this should have been done in advance. And been in
Appendix A of the Handbook in plenty of time.
> As a minor aside, has anyone stated the reason why the user-base of
> base or ports are moving to git?
Going with the fashion, IMO. But I will no doubt get shouted down.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
On 1/04/2021 6:19 pm, Herbert J. Skuhra wrote:
> https://wiki.freebsd.org/git
>
Thanks Milan for bringing this to everyone's attention.
Would appreciate if anyone can provide insight as to the 4 git commands
that I need to function, in a manner similar to the way I use svnlite
use. Git equivalents for:
svnlite update /usr/ports
svnlite update -r '{$-$MM-$DD}' /usr/ports/$category/$port
svnlite log -l $N /usr/ports/$category/$port
svnlite diff /usr/ports/$category/$port
I'm sure many other users would have a similar usage (and similar
non-knowledge of git)
Is this
git clone -o freebsd --config
remote.freebsd.fetch='+refs/notes/*:refs/notes/*'
https://git.freebsd.org/${repo}.git
really the equivalent of
svnlite update /usr/ports
I have a few changes to the infrastructure that I don't want to loose by
overwriting those changes.
As a minor aside, has anyone stated the reason why the user-base of base
or ports are moving to git? (And its greatly appreciated that 12-stable
will continue to feed svn as it provides an opportunity for users to
migrate to, what for many, is new)
Kind regards, Dewayne.
PS We use ports to build, no remote packages (since FreeBSD 4).
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Illegal instruction on new port mongodb49 on arm64
Hi, I created a new port for mongodb49: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254631 It compiles fine: https://www.klop.ws/mongodb49-4.9.0.r0.log When I run an application I get "Illegal Instruction" error. == [root@rpi4 /tmp]# lldb /usr/local/bin/mongo (lldb) target create "/usr/local/bin/mongo" Current executable set to '/usr/local/bin/mongo' (aarch64). (lldb) run Process 55420 launching Process 55420 launched: '/usr/local/bin/mongo' (aarch64) Process 55420 stopped * thread #1, name = 'mongo', stop reason = signal SIGILL: illegal trap frame #0: 0x016a320c mongo`___lldb_unnamed_symbol32$$mongo + 1784 mongo`___lldb_unnamed_symbol32$$mongo: -> 0x16a320c <+1784>: ldaddal x9, x8, [x8] 0x16a3210 <+1788>: ldrq0, [x11] 0x16a3214 <+1792>: movw10, #0x20 0x16a3218 <+1796>: strb wzr, [sp, #0x68] (lldb) bt * thread #1, name = 'mongo', stop reason = signal SIGILL: illegal trap * frame #0: 0x016a320c mongo`___lldb_unnamed_symbol32$$mongo + 1784 frame #1: 0x42b29b58 frame #2: 0x42b289f8 == [root@rpi4 /tmp]# /usr/local/bin/mongo Illegal instruction (core dumped) [root@rpi4 /tmp]# lldb /usr/local/bin/mongo -c /var/tmp/0.mongo.0.55421.core (lldb) target create "/usr/local/bin/mongo" --core "/var/tmp/0.mongo.0.55421.core" Core file '/var/tmp/0.mongo.0.55421.core' (aarch64) was loaded. (lldb) bt * thread #1, name = 'mongo', stop reason = signal SIGILL * frame #0: 0x016a320c mongo`___lldb_unnamed_symbol32$$mongo + 1784 frame #1: 0x42b29b58 ld-elf.so.1`objlist_call_init(list=, lockstate=) at rtld.c:2855:7 frame #2: 0x42b289f8 ld-elf.so.1`_rtld(sp=, exit_proc=, objp=) at rtld.c:828:5 frame #3: 0x42b264d8 ld-elf.so.1`.rtld_start at rtld_start.S:41 == NB: The default of the port uses LTO. I disabled it on my build system because of lack of memory. Can anybody help me with this? It would be interesting to know if this also happens on amd64. Regards, Ronald. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
On Thu, Apr 01, 2021 at 09:54:16AM +0200, Milan Obuch wrote: > On Thu, 1 Apr 2021 09:47:04 +0200, Mathieu Arnold > wrote: > > > On Thu, Apr 01, 2021 at 09:16:15AM +0200, Milan Obuch wrote: > > > Also, what about svn mirror, as is done for src repository, for 11 > > > and 12 branches at least? I did not tried it recently, but it used > > > to work. For some boxes, adding git to the mix would be big PITA. > > > > There will be no Git to Subversion conversion for ports, like for > > docs. The only reason there is for the base system on 11 and 12 is > > because Subversion was the source control software used when they > > were released. > > > > This is unpleasant move for me. This means git or equivalent (and > dependencies) must be installed on any box where tracking ports tree is > planned/needed... and no tool like svnlite could be expected in base > system for some time. > > So I need some work on my local infrastructure to adjust to this move. > C'est la vie... If you actually need a repository, and not just the latest files, all you need is run pkg install git on the machines you are actually using a ports tree on, if you have more than one machine, you should probably be using binary packages anyway, either the ones provided by FreeBSD, or ones built yourself using ports-mgmt/poudriere. If you only need the latest files, you can probably use something like net/gitup. -- Mathieu Arnold signature.asc Description: PGP signature
Re: No update for a day on ports?
* Milan Obuch [20210401 09:54]:
> This is unpleasant move for me. This means git or equivalent (and
> dependencies) must be installed on any box where tracking ports tree is
> planned/needed... and no tool like svnlite could be expected in base
> system for some time.
If all you need is to keep your ports tree up to date, have a look at
net/gitup. No dependencies and can't possibly get any simpler.
--
Dipl.-Inform. Felix Palmen ,.//..
{web} http://palmen-it.de {jabber} [see email] ,//palmen-it.de
{pgp public key} http://palmen-it.de/pub.txt // """""""""""
{pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A
signature.asc
Description: PGP signature
Re: No update for a day on ports?
On Thu, 1 Apr 2021 09:47:04 +0200, Mathieu Arnold wrote: > On Thu, Apr 01, 2021 at 09:16:15AM +0200, Milan Obuch wrote: > > Also, what about svn mirror, as is done for src repository, for 11 > > and 12 branches at least? I did not tried it recently, but it used > > to work. For some boxes, adding git to the mix would be big PITA. > > There will be no Git to Subversion conversion for ports, like for > docs. The only reason there is for the base system on 11 and 12 is > because Subversion was the source control software used when they > were released. > This is unpleasant move for me. This means git or equivalent (and dependencies) must be installed on any box where tracking ports tree is planned/needed... and no tool like svnlite could be expected in base system for some time. So I need some work on my local infrastructure to adjust to this move. C'est la vie... Regards, Milan ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
On Thu, Apr 01, 2021 at 09:16:15AM +0200, Milan Obuch wrote: > Also, what about svn mirror, as is done for src repository, for 11 and > 12 branches at least? I did not tried it recently, but it used to work. > For some boxes, adding git to the mix would be big PITA. There will be no Git to Subversion conversion for ports, like for docs. The only reason there is for the base system on 11 and 12 is because Subversion was the source control software used when they were released. -- Mathieu Arnold signature.asc Description: PGP signature
Re: No update for a day on ports?
On Thu, 1 Apr 2021 09:35:11 +0200, Kurt Jaeger wrote: > Hi! > > > > The repo moved/is moving to git, so svn is no longer updated. > > > I did not catch any notice about the move. I know it was planned, > > but not announcing actual move is... not that nice. > > The announcement was this post, although it was maybe a bit terse > on the exact date: > > https://lists.freebsd.org/pipermail/freebsd-ports/2021-March/120566.html > OK, but one more mail 'HEADSUP: Move to git just started, see $URL' sent here yesterday would make everything much better visible. Don't take this as critique, move to git is surely big move, and, judging from src transition to git and its outcome, allows for better tooling as well. As an old fart, I am against changing tools just for the sake of change, and being not involved in the process directly, I am just waiting for the end. Only then I start to evaluate new state... I think there are many like me here. Regards, Milan ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
Hi! > > The repo moved/is moving to git, so svn is no longer updated. > I did not catch any notice about the move. I know it was planned, but > not announcing actual move is... not that nice. The announcement was this post, although it was maybe a bit terse on the exact date: https://lists.freebsd.org/pipermail/freebsd-ports/2021-March/120566.html -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
On Thu, Apr 01, 2021 at 08:22:47AM +0200, Milan Obuch wrote: > Hi, > > did somebody encountered this issue? I am using svn daily to update > ports tree on some (maybe 15, exact number not important) boxes. No new > updates today. I noticed it first actually yesterday afternoon or early > evening, but I did not consider asking then. > > Is there some breakage in ports infrastructure? I see request comming > in on ports-bugs mailing list, but no update past revision 569609. > Also, I did not read anything on switching to git for ports, but I > would expect svn mirror for older (11 and 12) systems anyway as it is > done for src tree now. https://wiki.freebsd.org/git -- Herbert ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
On Thu, 1 Apr 2021 09:09:16 +0200, Kurt Jaeger wrote: > Hi! > > > did somebody encountered this issue? I am using svn daily to update > > ports tree on some (maybe 15, exact number not important) boxes. No > > new updates today. I noticed it first actually yesterday afternoon > > or early evening, but I did not consider asking then. > > The repo moved/is moving to git, so svn is no longer updated. > I did not catch any notice about the move. I know it was planned, but not announcing actual move is... not that nice. On the other side, it did no damage actually, it was just unusual or unexpected behavior. Also, what about svn mirror, as is done for src repository, for 11 and 12 branches at least? I did not tried it recently, but it used to work. For some boxes, adding git to the mix would be big PITA. Regards, Milan ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
On 1 Apr 2021, at 8:22, Milan Obuch wrote: > did somebody encountered this issue? I am using svn daily to update > ports tree on some (maybe 15, exact number not important) boxes. No new > updates today. I noticed it first actually yesterday afternoon or early > evening, but I did not consider asking then. > > Is there some breakage in ports infrastructure? I see request comming > in on ports-bugs mailing list, but no update past revision 569609. > Also, I did not read anything on switching to git for ports, but I > would expect svn mirror for older (11 and 12) systems anyway as it is > done for src tree now. > https://wiki.freebsd.org/git Best regards, Kristof ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: No update for a day on ports?
Hi! > did somebody encountered this issue? I am using svn daily to update > ports tree on some (maybe 15, exact number not important) boxes. No new > updates today. I noticed it first actually yesterday afternoon or early > evening, but I did not consider asking then. The repo moved/is moving to git, so svn is no longer updated. -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
No update for a day on ports?
Hi, did somebody encountered this issue? I am using svn daily to update ports tree on some (maybe 15, exact number not important) boxes. No new updates today. I noticed it first actually yesterday afternoon or early evening, but I did not consider asking then. Is there some breakage in ports infrastructure? I see request comming in on ports-bugs mailing list, but no update past revision 569609. Also, I did not read anything on switching to git for ports, but I would expect svn mirror for older (11 and 12) systems anyway as it is done for src tree now. Regards, Milan ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
