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):
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.
> 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:/ /launchpadlibra rian.net/ 426783430/ upload_ 16897586_ log.txt
DEBUG Considering changefile 119211/ ubuntu/ corosync_ 2.4.4-3ubuntu0~bug1831492v20190604b1_ amd64.changes 2.4.4-3ubuntu0~bug1831492v20190604b1_ amd64.changes 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 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
DEBUG Finding fresh policy
INFO Processing upload corosync_
INFO Upload was rejected:
INFO corosync-
INFO corosync-
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: /launchpad. net/ubuntu/ +source/ corosync/ 3.0.0-1 /launchpad. net/ubuntu/ +source/ corosync/ 3.0.1-1 /launchpad. net/ubuntu/ +source/ corosync/ 3.0.1-2
https:/
https:/
https:/
or, disable building the corosync-qdevice and corosync-qnetd binary debs from the disco corosync source.
just an fyi! kthnxbye