Well, looks like the Ubuntu apt-get is the one that's getting it wrong here and that Spacewalk is correct (for these packages). That's what it looked like to me on your first e-mail but I wasn't certain, however this seems to confirm it. Now, have you tried to update with rhn_check after approving the package updates in Spacewalk?
It's been annoying me that Ubuntu seems to take great liberties with the Debian package versioning standards but it appears to be a new low for them to manage to come up with versions that seem to break their own hacked up versioning algorithms. You could try to crank up the logging on the rhn_check, to verify that those package versions are being recommended by Spacewalk (or look at the event history?) but if Spacewalk is suggesting python-ethtool-0.14-1.amd64-deb and the apt-get client is rejecting it, then the client is wrong. If that only happens with apt-get however, then maybe there's a bug in the apt-get=>spacewalk glue/shim in separating and parsing the package version and breaking it down into epoch/upstream-version/Debian-version (which would be my guess with python-gobject-2 but unfortunately doesn't make sense with the others) Cheers, Paul-Andre On Tue, 30 Jul 2019 17:36:34 +0200, philippe bidault <philippe.bida...@gmail.com> wrote: >Nope, no lock or nothing similar: > >root@debian10:~# dpkg -l | grep python-eth >ii python-ethtool 0.12-1.1 amd64 > Python bindings for the ethtool kernel interface > >Regards, >Philippe. > >On Tue, 30 Jul 2019 at 15:02, Michael Mraka <michael.mr...@redhat.com> >wrote: > >> philippe bidault: >> > Hi Michael, >> > >> > Here are the installed versions: >> > >> > root@debian10:~# dpkg -l | grep python-go >> > ii python-gobject 3.22.0-2 all >> > Python 2.x bindings for GObject - transitional package >> > ii python-gobject-2 2.28.6-13 amd64 >> > deprecated static Python bindings for the GObject library >> > root@debian10:~# dpkg -l | grep python-eth >> > ii python-ethtool 0.12-1.1 amd64 >> > Python bindings for the ethtool kernel interface >> > >> > So this is in fact matching what appears in the "Installed Package" column >> > in the Spacewalk web console. The Debian 10 client just does not see >> > the 3 updates. >> >> Can't they be somehow excluded / version-locked / ... etc? >> If you use dpkg to list all available python-ethtool packages can you >> see >> python-ethtool-0.14-1 among them? >> >> > Regards, >> > Philippe. >> ... >> > > > Latest Package Installed Package >> > > > python-ethtool-0.14-1.amd64-deb python-ethtool-0.12-1.1.amd64-deb >> > > > python-gobject-3.30.4-1.all-deb python-gobject-3.22.0-2.all-deb >> > > > python-gobject-2-2.28.6-13+b1.amd64-deb python-gobject-2-2.28.6-13.amd64-deb >> > > > >> > > > But on the registered debian 10 server, "apt update" is telling me that all >> > > > the packages are already up-to-date. >> > > >> > > What version of python-ethtool, python-gobject and >> > > python-gobject-2 do you have installed on the debian server? >> >> Regards, >> >> -- >> Michael Mr?ka >> System Management Engineering, Red Hat >> > -- At Motorola Solutions and our subsidiaries, your privacy is important to us. That is why we have taken appropriate measures to ensure the data you provide to us is kept secure. To learn more about how we process your personal information, how we comply with applicable data protection laws, and care for the security and privacy of your personal data, please review our Privacy Policy <https://www.motorolasolutions.com/en_us/about/privacy-policy.html#privacystatement>. If you have any questions related to data protection and compliance with applicable laws, please contact us at priva...@motorolasolutions.com <mailto:priva...@motorolasolutions.com> _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list