Re: Version numbers

Hey, On 1/12/24 13:08, Ray Bellis wrote: Hi BIRD folks! Could you please consider using consistent semantic versioning in your release numbers? (see semver.org) Up until 2.13 all releases used the x.y.z format, with a trailing .0 for the first release in each minor release.  However the the

Re: Bird2 on Rocky9.3

Hi, latest bird2-2.14-1.e7 is available for Rocky 7 from EPEL, but no 8 or 9 builds. Upstream BIRD packaging is tested on Rocky 8 and AlmaLinux 9 which are both RHEL clones so it should be easy to build. I've CC'd Fedora package maintainer in hopes he might do the builds. Note that upstrea

Re: Current bird via bookworm-backports?

Hello, I maintain pkg.labs.nic.cz and rsync wasn't supported until today, but you're a second user interested in mirroring the repos so I had a look and enabled the rsync daemon: $ rsync rsync://pkg.labs.nic.cz/ bird2 "BIRD 2.x Debian & Ubuntu packages repo" knot-resolver "K

Re: Current bird via bookworm-backports?

First, thank you all for these emergent mirrors :) On 4/23/24 20:26, netravnen+birdl...@gmail.com wrote: On Tue, 23 Apr 2024 at 14:50, Jakub Ružička wrote: A next step could be to add a list at the homepage (https://pkg.labs.nic.cz/doc/) of public mirrors on a per-region basis. Maybe? I can do

Re: Current bird via bookworm-backports?

Hi Daniel, That's correct. I maintain BIRD 2 packages in Debian unstable/testing and stable, and also our pkg.labs.nic.cz/bird2/ repos I could also maintain -backports and Ubuntu package and various other forks but I don't really have cycles to do all that, so I leave that on the community

Re: Debian builds

Hello, On 5/8/24 11:10, Gunnar Guðvarðarson via Bird-users wrote: Hey, It looks like https://bird.network.cz/?download&tdir=debian/  is abandoned, both the key is wrong (does not match the packages) and the latest build is wheezy, which dropp

Re: Bird 2.16 ASPA issue

Hello, On 1/6/25 10:51, Job Snijders wrote: On Mon, Jan 06, 2025 at 10:50:15AM +0100, Maria Matejka wrote: The right one is "providers", yet there is probably some package out with "provider", so i'm expecting to allow both in the end because we botched it in such a stupid way. I'd recommend t