On 01/07/2021 14:34, Morten Linderud via aur-general wrote:
On Wed, Jun 30, 2021 at 09:52:54PM -0400, Eli Schwartz via aur-general wrote:
On 6/30/21 9:35 PM, George Rawlinson via aur-general wrote:
On 21-06-30 15:05, alad via aur-general wrote:
The question if the package will ever make it to community - most people won't have community-testing enabled. It's not very typical for new packages that weren't in the repositories before. My guess it was because an alpha version was packaged, which shouldn't have been packaged in the repos in the first place.
Alad
I'm the packager for pijul (in community).
There's a decent chunk of packages in community that have alpha/beta releases so I assumed it was OK. Apologies if this is not the case. e.g. a notable one that I'm aware of is qt5-webkit which unfortunately is not very well maintained by Qt and the alpha by annulen provides life support with e.g. various needed security fixes. runc, which the entire container ecosystem has been depending on the past 7 years, got it's first stable release last week after almost 100 release candidates :) As summarized by eschwartz, the guidelines [1] clearly point out that:
Stable packages package stable releases: Release candidates (i.e. 1.0.0-rc1), alpha (e.g. 1.0.0-alpha1) and beta (e.g. 1.0.0-beta1) releases are not allowed and are only to be used under the following circumstances:
* The non-stable release holds urgent security fixes (and backporting is non-trivial). * The non-stable release allows for the package to be built (e.g. problems introduced due to updated dependencies) and those changes can not otherwise be backported easily. * The non-stable release allows the distribution to drop an EOL component (e.g. qt4, python2).
Apparently personal preference goes above the package guidelines. So remind me why we have them in the first place? Alad [1] https://wiki.archlinux.org/title/Arch_package_guidelines#Package_versioning