Is there a particular reason to SRU this FTBFS fix without any other fix
together with it?
An FTBFS is listed as a valid safe case[1] for an SRU, but with the
remark that usually it should be released together with another bug fix.
We can stage this fix in proposed, by adding the block-proposed-focal
tag.
Something that concerns me is that the current binary in focal
(3.1.6+nmu2build1) is the same since cosmic:
2020-04-27 21:55:20 -03 Superseded Groovy release main admin
3.1.6+nmu2build1
2019-10-18 06:15:30 -03 Published Focal release main admin
3.1.6+nmu2build1
2020-12-29 11:18:15 -03 Obsolete Eoan release main admin
3.1.6+nmu2build1
2020-07-14 03:39:25 -03 Obsolete Disco release main admin
3.1.6+nmu2build1
2020-07-12 23:35:12 -03 Obsolete Cosmic release main admin
3.1.6+nmu2build1
Deleted Cosmic proposed main admin 3.1.6+nmu2build1
Rebuilding it now will definitely change it, and there are no DEP8
tests. We should at least have some test plan for the new binary.
1. https://canonical-sru-docs.readthedocs-
hosted.com/en/latest/reference/requirements/#other-safe-cases
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870085
Title:
xfsdump ftbfs in focal (all archs)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfsdump/+bug/1870085/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
