Re: pkg_add in -current
Stuart Henderson wrote: > On 2022/06/04 15:23, Theo de Raadt wrote: > > Stuart Henderson wrote: > > > > > If you are running -current and have not updated base recently, you > > > may run inTO "pkg_add: Unknown option: always-update ". > > > To fix it, just update to a newer base snapshot. > > > > > > > > What happened is that a developer made a change to the pkg tools which > > creates completely incompatible package files. > > > > Noone knew this was happening beforehands. An email was circulated > > after-the-fact to ports@ list (which is mostly read by developers, and > > not read by users). It has now been weeks, and it still hasn't been > > clearly communicated. > > People can decide for themselves about that, > > First commit enabling parsing in pkg_add > https://github.com/openbsd/src/commit/5cb7aebf4211294fd2891b0bc45c383ab7fd66af That commit message does not say: There will be no backwards compatiblity. > "REMINDER: snapshots go with -current" > https://marc.info/?l=openbsd-ports&m=165355109123377&w=2 That message says: There is zero effort being made for backwards compatiblity. It also says it is going to be FUN. Are we having fun? We are not having fun. This is the case of one developer (who did not even explain what was happening to any non-ports developer) making a decision in their own bubble, without communicating the impact in a way that everyone can understand. > Second commit, after base is updated with this subsequent package builds > use the new annotation > https://github.com/openbsd/src/commit/c2e596a17ac45689d758df0d67597fef94480ebe That commit message does not say: No effort has been made for backwards compatibility. > (Then it takes time for new packages to be built on the various archs > and it's not until *then* that errors would show up for people who > haven't updated base yet) So here we are: There is no backwards compatibility, and users are starting to encounter the problem, and the answer for them is that they must reboot. No it's not just that, they are being told the PROCESS WAS GREAT, and what is wrong here is *THEIR* process of using snapshots. It has also been pointed out that current.html has no information about this change. I have been saying for a while we should delete current.html because it seems to always contain useless information, and here we see it lacks crucial information.
Re: pkg_add in -current
On 2022/06/04 15:23, Theo de Raadt wrote: > Stuart Henderson wrote: > > > If you are running -current and have not updated base recently, you > > may run inTO "pkg_add: Unknown option: always-update ". > > To fix it, just update to a newer base snapshot. > > > > What happened is that a developer made a change to the pkg tools which > creates completely incompatible package files. > > Noone knew this was happening beforehands. An email was circulated > after-the-fact to ports@ list (which is mostly read by developers, and > not read by users). It has now been weeks, and it still hasn't been > clearly communicated. People can decide for themselves about that, First commit enabling parsing in pkg_add https://github.com/openbsd/src/commit/5cb7aebf4211294fd2891b0bc45c383ab7fd66af "REMINDER: snapshots go with -current" https://marc.info/?l=openbsd-ports&m=165355109123377&w=2 Second commit, after base is updated with this subsequent package builds use the new annotation https://github.com/openbsd/src/commit/c2e596a17ac45689d758df0d67597fef94480ebe (Then it takes time for new packages to be built on the various archs and it's not until *then* that errors would show up for people who haven't updated base yet)
Re: pkg_add in -current
Stuart Henderson wrote: > If you are running -current and have not updated base recently, you > may run inTO "pkg_add: Unknown option: always-update ". > To fix it, just update to a newer base snapshot. What happened is that a developer made a change to the pkg tools which creates completely incompatible package files. Noone knew this was happening beforehands. An email was circulated after-the-fact to ports@ list (which is mostly read by developers, and not read by users). It has now been weeks, and it still hasn't been clearly communicated. We break compatibility often, but generally ensure the right people -- both developers and users -- know when they need to know. This is important because people who follow snapshots (in various ways) should have a good experience because if they don't enjoy the snapshot experience, we may end up with a smaller test community between releases. Sometimes there are surprises in snapshots of a testing nature, but this particular change was not deployed or communicated as a test (we cannot go back). The normal model was not followed in this instance.
pkg_add in -current
If you are running -current and have not updated base recently, you may run inTO "pkg_add: Unknown option: always-update ". To fix it, just update to a newer base snapshot.
Re: regarding the default path for pkg_add in -current
On Wed, Sep 27, 2017 at 08:57:10PM -0600, and...@quickstick.net wrote: > Hello Folks !! > > Regarding GENERIC.MP #115 > > I have a feeling you are about to roll into 6.2, however I just want to > bring the following to your attention in case it matters. > > I just did a clean install of -current using the bsd.rd dated 2017-09-27. > Within the install sequence of questions, the default download path has been > hardcoded to ../6.2/... as opposed to ../snapshots/.. > > I manually changed it to ../snapshots/ and it installed as expected. > > Also, after login, pkg_add is very determined to use to the same ../6.2/.. > directory path. For the benefit of others who might find themselves in the > same spot, the workaround is to use the full path while using pkg_add. In my > case, it is: > > $ doas pkg_add \ > https://ftp3.usa.openbsd.org/pub/OpenBSD/snapshots/amd64/pkgname Unless you have good reasons to care about confidentiality, I'd advise against https for pkg_add right now for performance reasons.
Re: regarding the default path for pkg_add in -current
On Wed, 27 Sep 2017 20:57:10 -0600, and...@quickstick.net wrote: > Also, after login, pkg_add is very determined to use to the same > ../6.2/.. directory path. For the benefit of others who might find > themselves in the same spot, the workaround is to use the full path > while using pkg_add. A better solution is to use pkg_add -Dsnap Cheers, Daniel
Re: regarding the default path for pkg_add in -current
On Wed, Sep 27, 2017 at 7:57 PM, wrote: > Regarding GENERIC.MP #115 > > I have a feeling you are about to roll into 6.2, however I just want to > bring the following to your attention in case it matters. > > I just did a clean install of -current using the bsd.rd dated 2017-09-27. > Within the install sequence of questions, the default download path has > been hardcoded to ../6.2/... as opposed to ../snapshots/.. > > I manually changed it to ../snapshots/ and it installed as expected. > Also, after login, pkg_add is very determined to use to the same ../6.2/.. > directory path. For the benefit of others who might find themselves in the > same spot, the workaround is to use the full path while using pkg_add. > <...> Instead of using a full path, does invoking pkg_add with the option -Dsnap result in the desired behavior? Philip Guenther
regarding the default path for pkg_add in -current
Hello Folks !! Regarding GENERIC.MP #115 I have a feeling you are about to roll into 6.2, however I just want to bring the following to your attention in case it matters. I just did a clean install of -current using the bsd.rd dated 2017-09-27. Within the install sequence of questions, the default download path has been hardcoded to ../6.2/... as opposed to ../snapshots/.. I manually changed it to ../snapshots/ and it installed as expected. Also, after login, pkg_add is very determined to use to the same ../6.2/.. directory path. For the benefit of others who might find themselves in the same spot, the workaround is to use the full path while using pkg_add. In my case, it is: $ doas pkg_add \ https://ftp3.usa.openbsd.org/pub/OpenBSD/snapshots/amd64/pkgname --- It looks like another great release is around the corner and as always I want to take the opportunity to thank Theo for his dedicated leadership and to all the past and present devs who make OpenBSD so special. Cheers !!!
