<div dir="ltr">Hi Jakub,<div><br></div><div>Thanks for working on this.</div><div><br></div><div>You are correct about that issue with init-system-helpers , I had completely forgotten about it.</div><div><br></div><div>We are running bird2 primarily on bionic, and I created a backport of init-system-helpers 1.56+nmu1~ubuntu18.04.1 and placed it in one of our internal repos to work around the for our use cases.</div><div><br></div><div>I was not sure why init-system-helpers (>= 1.56~) was specified at the time, but I suspected it may have been because of the build system it was built on.</div><div><br></div><div>Actually, it looks like it has been officially place in bionic backport snow too: <a href="https://packages.ubuntu.com/bionic-backports/init-system-helpers">https://packages.ubuntu.com/bionic-backports/init-system-helpers</a></div><div><br></div><div>So, in summary, the ppa was not completely valid beforehand for bionic at least :)</div><div>I think it would be better to include all deps in the PPA, so relevant versions of init-system-helpers too. Most production systems won't include the backports repo anyway.</div><div><br></div><div>The other option is to try and work out if the dependency init-system-helpers (>= 1.56~) is valid, or just a build system signature artifact of some kind.</div><div><br></div><div><br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div><br></div>Cheers,<div>Just</div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 13 Apr 2021 at 21:39, Jakub Ružička <<a href="mailto:jakub.ruzicka@nic.cz">jakub.ruzicka@nic.cz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Hey Justin,<br>
<br>
I managed to get bird2-2.0.8 packages built (and lightly tested)
for all current Ubuntu versions in bird-experimental launchpad [1]
🥳 </p>
* Ubuntu 20.10 (Groovy Gorilla)<br>
<p>* Ubuntu 20.04.2 LTS (Focal Fossa)</p>
<p>* Ubuntu 18.04.5 LTS (Bionic Beaver)</p>
<p>* Ubuntu 16.04.7 LTS (Xenial Xerus)<br>
<br>
However, when I started testing migration from current official
bird launchpad [2] I noticed that bird2 doesn't really install on
Ubuntu 16.04 Xenial Xerus (package not found after adding ppa even
though it's displayed on the web 🤔) and 18.04 Bionic Beaver
(init-system-helpers (>= 1.56~) isn't available, that is the
same for Xenial even if the package was found). <br>
<br>
Ubuntu 19.04 Disco Dingo is rejected by launchpad as "disco is
obsolete and will not accept new uploads."<br>
<br>
I've fixed build issues by relaxing deps and disabling -docs
subpackage which was causing FTBFS on older distros. I'll try to
re-enable docs in the future package builds and they remain
available from downstream distro packages and more importantly
online.<br>
<br>
But I'm still quite confused by the current state of the launchpad
repo - can you confirm that [2] is the PPA you're using? Maybe
there are some other unofficial ones? If so, on which Ubuntu
version are you?<br>
<br>
Could you by any chance test upgrade on a testing
system/VM/container with your setup by adding [1] and checking if
bird2-2.0.8 does what you expect it to do before I push new
packages to [2]?<br>
<br>
For example:<br>
<br>
sudo add-apt-repository ppa:cz.nic-labs/bird-experimental<br>
sudo apt install bird2<br>
sudo systemctl status bird<br>
bird --version<br>
dpkg -l bird2<br>
<br>
I wasn't sure how much testing I should do before pushing new
packages into official launchpad but it seems broken to a point
where there isn't a single upgrade path I could test so I reckon
the sooner the better ¯\_(ツ)_/¯<br>
<br>
<br>
[1]:
<a href="https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird-experimental/" target="_blank">https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird-experimental/</a><br>
<br>
[2]: <a href="https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird" target="_blank">https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird</a><br>
</p>
<div><br>
Cheers,<br>
Jakub 📦<br>
<br>
On 4/9/21 9:36 AM, Justin Cattle wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Jakuk,
<div><br>
</div>
<div><br>
</div>
<div>That sounds very positive :)</div>
<div>I would vote for updating the Launchpad PPA too, at least
for this point release it would be helpful for us.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br clear="all">
<div>
<div dir="ltr">
<div><br>
</div>
Cheers,
<div>Just</div>
</div>
</div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, 9 Apr 2021 at 03:58,
Jakub Ružička <<a href="mailto:jakub.ruzicka@nic.cz" target="_blank">jakub.ruzicka@nic.cz</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
I bring good news!<br>
<br>
I've been recently tasked with updating Debian and Ubuntu bird
packages<br>
and I'm probably going to maintain all bird packaging
(including Debian<br>
downstream) from now on as I do with Knot DNS and Knot
Resolver packages<br>
which were also previously maintained by Ondra Surý the
current official<br>
Debian bird package Maintainer. He agreed to pass the
maintenance of<br>
bird and bird2 Debian packages to me as well. Please note that
I'm a<br>
fresh Debian Maintainer, not a Debian Developer (yet?) so my
powers are<br>
slightly limited but I've been able to solve all Debian
packaging tasks<br>
so far with the kind help of my awesome sponsor and mentors
and I intend<br>
to do the same for bird.<br>
<br>
Debian unstable is in hard freeze and bird2 Debian package
doesn't have<br>
autopkgtests which means it can't be updated until Debian 11
Bullseye is<br>
released.<br>
<br>
I've prepared bird2-2.0.8 on my Salsa fork and I also enabled
Salsa CI<br>
which is green (some harmless blhc warnings and reproducible
build are<br>
skipped):<br>
<br>
<a href="https://salsa.debian.org/jruzicka/bird2" rel="noreferrer" target="_blank">https://salsa.debian.org/jruzicka/bird2</a><br>
<br>
I'll make sure these changes will make it to Debian (and
Ubuntu by<br>
transition) eventually.<br>
<br>
<br>
Regarding upstream packages, I initially intended to update
the bird<br>
launchpad you mentioned, but after a careful consideration I
chose to<br>
leverage openSUSE Build Service (OBS) instead to provide wider
platform<br>
support than just Ubuntu.<br>
<br>
OBS is already used in Knot Resolver and Knot DNS projects for
packaging<br>
and CI and while it has its share of problems, it currently
provides<br>
best value for building upstream packages on many different
distros and<br>
archs from shared packaging source.<br>
<br>
I already have bird2 packages built in a testing OBS repo for
latest<br>
Debian, Ubuntu, Fedoras, and CentOS but there are some
remaining issues<br>
with docs generation on older distro versions which I need to
address.<br>
In worst case scenario I will temporarily drop doc packages in
order to<br>
get bird built.<br>
<br>
I plan to announce the new OBS repos sometimes next week to
provide<br>
Debian, Ubuntu, and hopefully SUSE packages as opposed to
Ubuntu only<br>
through Launchpad.<br>
<br>
However, after seeing your interest in the Launchpad repo,
I'll see if I<br>
can get it updated as well to make the transition smoother.<br>
<br>
<br>
I have bright plans for both upstream and downstream bird
packaging but<br>
I'll share the them only after I'm done with bird-2.0.8
packages you've<br>
been waiting for.<br>
<br>
<br>
Thank you for your patience!<br>
<br>
<br>
Jakub Ružička<br>
CZ.NIC packager 📦<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote>
</div>
<br>
<p style="margin:0px;background-color:rgb(255,255,255)"><font face="Calibri, sans-serif" color="#aeaaaa"><span style="font-size:14.6667px">Notice: <br>
This email is confidential and may contain copyright
material of members of the Ocado Group. Opinions and views
expressed in this message may not necessarily reflect the
opinions and views of the members of the Ocado Group.<br>
<br>
If you are not the intended recipient, please notify us
immediately and delete all copies of this message. Please
note that it is your responsibility to scan this message for
viruses.<br>
<br>
References to the "Ocado Group" are to Ocado Group plc
(registered in England and Wales with number 7098618) and
its subsidiary undertakings (as that expression is defined
in the Companies Act 2006) from time to time. The registered
office of Ocado Group plc is Buildings One & Two,
Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10
9UL.</span></font></p>
</blockquote>
</div>
</blockquote></div>
<br>
<p style="margin:0px;background-color:rgb(255,255,255)"><font face="Calibri, sans-serif" color="#aeaaaa"><span style="font-size:14.6667px">Notice: <br>This email is confidential and may contain copyright material of members of the Ocado Group. Opinions and views expressed in this message may not necessarily reflect the opinions and views of the members of the Ocado Group.<br><br>If you are not the intended recipient, please notify us immediately and delete all copies of this message. Please note that it is your responsibility to scan this message for viruses.<br><br>References to the "Ocado Group" are to Ocado Group plc (registered in England and Wales with number 7098618) and its subsidiary undertakings (as that expression is defined in the Companies Act 2006) from time to time. The registered office of Ocado Group plc is Buildings One & Two, Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9UL.</span></font></p>