pkgsrc-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
freeze started for 2024Q2
pkgsrc is now frozen in preparation for 2024Q2.
Everyone is welcome to help by
- updating to HEAD ("cvs up -A")
- building packages they care about via
+ pbulk
+ pkg_rolling-replace (or pkgrrx)
+ some other update method
- fixing problems or reporting them
- running bulk builds and sending reports to pkgsrc-bulk
- reading https://releng.netbsd.org/bulktracker/ and trying to fix or
diagnose problems, e.g.
https://releng.netbsd.org/bulktracker/build/883
A longer decription of the freeze process is at
https://www.pkgsrc.org/quarterly/
This freeze will follow the usual "gdt's rules", which I include below.
gdt's rules
No new packages
Build fixes are welcome
Bug fixes (especially security fixes) are very welcome
Micro updates that would be eligible and appropriate for stable branch pullups, because they fix a security bug or something serious, are ok
Micro updates for packages whose recursive total depending package count is < 25 are ok
For any other updates (especially under mk or pkgtools), please ask, explaining why the update furthers pkgsrc's goals of stabilty and usefulness for users. While there's no intent to completely prohibit changes, I'm concerned about impacts to platforms not tested, and I value working packages from the branch over packages being slightly newer.
No large-scale cleanup of things that are not causing failure of a package to build, package, and run, e.g. HOMEPAGE and MASTER_SITES.
As usual, we don't have a specific end time planned, but nominally
7 days so around 27 June 0Z. Could be shorter if all fixable things are
fixed and longer if things are actively being fixed.
Notable for this branch:
- rust didn't get updated since it has been hard to get it building
- we are starting to see issues building on NetBSD 9
- overall the failing package set seems a little higher than usual
Thanks,
Greg
Home |
Main Index |
Thread Index |
Old Index