Sorry for getting back to this so late. We need the orig tarball contents to match the claimed version.
Stonking currently has[1]: doca-ofed-3.4-dkms_3.4.1+1.1.0.0.orig.tar.xz 3.1 MiB 6e3db559ad6d60b87ef153d9fcbc5dac26e5427e57b501348c6ba7272cbbb1d2 Or md5sum: 66de4dcc25d461ea50ba3f4ed0ac7a01 doca-ofed-3.4-dkms_3.4.1+1.1.0.0.orig.tar.xz The resolute upload is also claiming to be version 3.4.1+1.1.0.0. Therefore, it must have the same orig tarball as stonking. But as we established in comment #16, stonking's 3.4.1+1.1.0.0 is actually still 3.4.0+0.8.5.0. Bottom line, I can't upload to resolute something that claims it's 3.4.1+1.1.0.0 when it does not match the orig tarball that launchpad already has for that version. It will be automatically rejected by launchpad. Can you create a proper stonking tarball, using a new version, perhaps 3.4.1+1.1.0.1? What is that secondary version anyway, the one after the +? 1. https://launchpad.net/ubuntu/+source/doca-ofed-3.4-dkms/3.4.1+1.1.0.0-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2165884 Title: doca-ofed 3.4.1 Package Update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/doca-ofed-3.4-dkms/+bug/2165884/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
