Hi list, the prebuilt packages under [1] seem to be a bit outdated. While Fedora and CentOS at least have 1.6.4 available, Debian only has 1.6.3, and there is not a single package for 2.0. Are there any plans to provide prebuilt packages for 2.0? Is there anything one can do to help that process? Best regards, Jan-Philipp Litza [1] http://bird.network.cz/?download -- Jan-Philipp Litza PLUTEX GmbH Hermann-Ritter-Str. 108 28197 Bremen Hotline: 0800 100 400 800 Telefon: 0800 100 400 821 Telefax: 0800 100 400 888 E-Mail: support@plutex.de Internet: http://www.plutex.de USt-IdNr.: DE 815030856 Handelsregister: Amtsgericht Bremen, HRB 25144 Geschäftsführer: Torben Belz, Hendrik Lilienthal
On Mon, May 14, 2018 at 09:12:30AM +0200, Jan-Philipp Litza wrote:
Hi list,
the prebuilt packages under [1] seem to be a bit outdated. While Fedora and CentOS at least have 1.6.4 available, Debian only has 1.6.3, and there is not a single package for 2.0.
Hi We added Debian packages for 1.6.4 to our repository. Sorry for the delay. We are updating our infrastructure to have automatic package builds in the future. Packages for BIRD 2.0 will likely be released with the next release. We plan to have some transition in packages to keep both 1.6 and 2.0 as independent packages in repository without automatic update, similarly to how grub->grub2 transition was done in Debian. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
On Wed, May 23, 2018 at 3:05 PM Ondrej Zajicek <santiago@crfreenet.org> wrote:
Hi
We added Debian packages for 1.6.4 to our repository. Sorry for the delay. We are updating our infrastructure to have automatic package builds in the future. Packages for BIRD 2.0 will likely be released with the next release.
We plan to have some transition in packages to keep both 1.6 and 2.0 as independent packages in repository without automatic update, similarly to how grub->grub2 transition was done in Debian.
Hi, I need to rename the FreeBSD port name too because right now we've got: - net/bird : bird 1.X branch - net/bird-devel: bird 2.X branch Do you have an idea for the most appropriate port name ? - net/bird1 and net/bird2 - Or net/bird-legacy (for 1.X branch) and net/bird (for 2.X branch) - Or other idea ? Thanks
Hello!
On Wed, May 23, 2018 at 3:05 PM Ondrej Zajicek <santiago@crfreenet.org <mailto:santiago@crfreenet.org>> wrote: We plan to have some transition in packages to keep both 1.6 and 2.0 as independent packages in repository without automatic update, similarly to how grub->grub2 transition was done in Debian.
On 05/23/2018 03:54 PM, Olivier Cochard-Labbé wrote:
Hi, I need to rename the FreeBSD port name too because right now we've got: - net/bird : bird 1.X branch - net/bird-devel: bird 2.X branch
Do you have an idea for the most appropriate port name ? - net/bird1 and net/bird2 - Or net/bird-legacy (for 1.X branch) and net/bird (for 2.X branch) - Or other idea ?
I suggest this way: 1) rename bird -> bird-legacy and bird-devel -> bird2 2) keep this for quite a long time to let users manually change from bird-legacy to bird2 (one whole release cycle?) and not force them into upgrade 3) rename bird2 -> bird 4) drop bird-legacy when we stop supporting it Maria
Jan Maria Matejka <jan.matejka@nic.cz> writes:
Hello!
On Wed, May 23, 2018 at 3:05 PM Ondrej Zajicek <santiago@crfreenet.org <mailto:santiago@crfreenet.org>> wrote: We plan to have some transition in packages to keep both 1.6 and 2.0 as independent packages in repository without automatic update, similarly to how grub->grub2 transition was done in Debian.
On 05/23/2018 03:54 PM, Olivier Cochard-Labbé wrote:
Hi, I need to rename the FreeBSD port name too because right now we've got: - net/bird : bird 1.X branch - net/bird-devel: bird 2.X branch
Do you have an idea for the most appropriate port name ? - net/bird1 and net/bird2 - Or net/bird-legacy (for 1.X branch) and net/bird (for 2.X branch) - Or other idea ?
I suggest this way: 1) rename bird -> bird-legacy and bird-devel -> bird2 2) keep this for quite a long time to let users manually change from bird-legacy to bird2 (one whole release cycle?) and not force them into upgrade 3) rename bird2 -> bird 4) drop bird-legacy when we stop supporting it
As a point of reference, we went with bird1/bird2 in openwrt: https://github.com/openwrt-routing/packages/pull/378 -Toke
Ondrej, thank you for packages! Sysadmins everywhere appreciate them greatly (including myself and MBIX). On Wed, May 23, 2018 at 9:27 AM, Jan Maria Matejka <jan.matejka@nic.cz> wrote:
I suggest this way: 1) rename bird -> bird-legacy and bird-devel -> bird2 2) keep this for quite a long time to let users manually change from bird-legacy to bird2 (one whole release cycle?) and not force them into upgrade 3) rename bird2 -> bird 4) drop bird-legacy when we stop supporting it
This is too complicated, in my view. Do it like apache. Leave the bird 1.x package as bird Add new bird 2.x package as bird2 In future, bird 3.x can bird3 No need to change package names, fewest surprises to sysadmins. Cheers, Jonathan
participants (6)
-
Jan Maria Matejka -
Jan-Philipp Litza -
Jonathan Stewart -
Olivier Cochard-Labbé -
Ondrej Zajicek -
Toke Høiland-Jørgensen