> So this is wontfix for corosync in disco. if you say so.
I subscribed the security team since if they ever need to provide a security release for corosync in disco, this may be the problem they encounter (and of course, anyone trying to do any normal bugfix to corosync in disco will also have this problem): https://launchpad.net/~ddstreet/+archive/ubuntu/lp1831492/+packages from https://launchpadlibrarian.net/426783430/upload_16897586_log.txt DEBUG Considering changefile 119211/ubuntu/corosync_2.4.4-3ubuntu0~bug1831492v20190604b1_amd64.changes DEBUG Finding fresh policy INFO Processing upload corosync_2.4.4-3ubuntu0~bug1831492v20190604b1_amd64.changes INFO Upload was rejected: INFO corosync-qdevice_2.4.4-3ubuntu0~bug1831492v20190604b1_amd64.deb: Version older than that in the archive. 2.4.4-3ubuntu0~bug1831492v20190604b1 <= 3.0.0-2ubuntu1+bug1831492v20190604b1 INFO corosync-qnetd_2.4.4-3ubuntu0~bug1831492v20190604b1_amd64.deb: Version older than that in the archive. 2.4.4-3ubuntu0~bug1831492v20190604b1 <= 3.0.0-2ubuntu1+bug1831492v20190604b1 INFO Committing the transaction and any mails associated with this upload. Of course, if they upgrade corosync to the next major version, which is already in disco-proposed (but never made it to disco-release), that would fix the problem: https://launchpad.net/ubuntu/+source/corosync/3.0.0-1 https://launchpad.net/ubuntu/+source/corosync/3.0.1-1 https://launchpad.net/ubuntu/+source/corosync/3.0.1-2 or, disable building the corosync-qdevice and corosync-qnetd binary debs from the disco corosync source. just an fyi! kthnxbye -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1831492 Title: autopkgtest --apt-pocket=proposed=<any trigger> fails with corosync in disco Status in Auto Package Testing: New Status in corosync package in Ubuntu: Fix Released Status in corosync source package in Disco: Won't Fix Bug description: [impact] running autopkgtest for corosync in disco with any trigger (e.g. using --apt-pocket=proposed=src:systemd) fails because the testbed can't find the corosync source. [test case] $ autopkgtest --apt-pocket=proposed=src:systemd --apt-upgrade corosync -- qemu <DISCO IMG> or see any of the recent disco corosync autopkgtest logs, e.g.: http://autopkgtest.ubuntu.com/packages/corosync/disco/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- disco/disco/amd64/c/corosync/20190531_185143_8d956@/log.gz [regression potential] TBD [other info] this is happening because corosync *before* version 3.0.0 built the 'corosync-qnetd' and 'corosync-qdevice' binary debs directly from the 'corosync' source package. However, at corosync version 3.0.0, those binary debs were split out into their own 'corosync-qdevice' source package. Unfortunately, the latest version of corosync in disco is 2.4.4-3, while corosync-qdevice (source package) also was built and released to disco-release at version 3.0.0-2ubuntu1. This results in autopkgtest looking for the 'latest' version of corosync for all the binary debs in its 'Package-list:' (i.e., running 'apt-cache showsrc --only-source corosync and parsing the Package- List). Since both 'corosync-qdevice' and 'corosync-qnetd' are included in that list, it uses the newer 3.0.0-2ubuntu1 as the 'latest' version of the 'corosync' source package to download, but that isn't available in disco. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1831492/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
