2022Q2 binary question

[jmccue]

SOLVED

I saw this bsdsec.net about the new branch.

I am wondering, if I wanted to get the latest firefox-esr, should I just compile it (via pkgsrc) ?

I am hoping I could modify file "/usr/pkg/etc/pkgin/repositories.conf " with the 2022Q2 binary location, but seems that is not the case (after may searches).

BTW, I am OK compiling the firefox-esr, but would like to avoid it if possible.

Thanks

[shep]

Binary packages are built on the New York NBSD servers. At the time of this post, the builds are in progress with no 2022Q2 binaries published.
http://nyftp.netbsd.org/pub/pkgsrc/p...64/9.0_2022Q2/

You have 2 options. Wait until the projects binaries are published or start building them yourself.

On a long build like firefox, it is tempting to use the latest source and it can often lead to dependency issues if you mix source builds and binaries.

Also note that the Mozilla project just released Firefox-esr 102.0esr
https://ftp.mozilla.org/pub/firefox/releases/102.0esr/

At this time, pkgsrc for firefox-esr still points to firefox91
http://cvsweb.netbsd.org/bsdweb.cgi/...x-esr/Makefile
My sense is that 102.Xesr will not enter binary builds until 2022Q3.

[Sehnsucht94]

Originally Posted by shep

You have 2 options. Wait until the projects binaries are published or start building them yourself.

You may also consider switching to pkgsrc-current packages. Their update cycle is somewhat acceptable (last build dated 02/07).

[jmccue]

Thanks all.

I will wait for the binary packages on the New York servers. I was doing that but got confused thinking Q2 packages would not be available until the first week in Q3.

Will try and mark this solved

[jmccue]

SOLVED -- (for 9.x)

I just had to wait

As a note to people wanting to upgrade packages to the latest quarter, you should use port pkgin, it makes things easier.

But I got odd messages when doing a pkgin, which I ignored for a while. Seems I had entries in /usr/pkg/etc/pkgin/repositories.conf that caused issues. The pkgsrc docs with comments in the file confused me a bit. (Thanks to @Riastradh in #pkgsrc on liberachat on setting me straight)

This shows what to do:

1. wait for binaries to be built
2. Modify /usr/pkg/etc/pkgin/repositories.conf as noted below

Change Entry From
https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$arch/9.0/All
TO
https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$arch/9.0_2022Q2/All

The do a `pkgin upgrade` as root once packages are built.

That is how I was able to upgrade packages to the latest quarterly without any issues.