This was a mistake on my end. I thought I was the owner of the package, but I think I was only the owner of it back in el6. I assume systemd then wasn't depending on it. I saw a PR the other day, assumed it was to me as package owner, and saw no reason to not upgrade since it was long over due. I didn't realise this would break systemd.
Note, it is a bit worrying that systemd depends on this package, which wasn't updated in 5 years, and for which the upstream changelog mostly states "bug fixes".
nirik untagged the package for me. I pinged Zbyszek to coordinate things. I've reverted the commits for f29 and f30 (no updates were issued for these branches yet)
Ironically, this seems to not be the first time this happened either. I see someone else made the exact same mistake in January 2018 and reverted their changes to the package. So let's see if we can fix this now in rawhide so it does not happen again in another year.
Paul
On Tue, Jun 25, 2019 at 4:33 PM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
qrencode was bumped from 3.4.4 to 4.0.2.
It has a bumped soname from libqrencode.so.3 to libqrencode.so.4.
systemd once again cannot be installed and all my packages fail to resolve build
dependencies.
Please, announce those changes and coordinate!
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
