Am 19. Juli 2018 17:24:17 MESZ schrieb Dalton Miner <dmi...@datto.com>: >Hi all, > >I'm working on packaging the most recent stable versions of the >Spacewalk >client for newer versions of Ubuntu (18.04). I've made a lot of >progress so >far and most of the client-server interactions work, but I'm hitting a >wall >on package pushes. If I try to remotely schedule a package install and >run >`rhn_check`, or run an `apt update`, the command on the client hangs >indefinitely. > >>From what I can tell, it's hanging on this line ><https://github.com/spacewalkproject/spacewalk/blob/apt-spacewalk-1.0.14-1/client/debian/packages-already-in-debian/apt-transport-spacewalk/spacewalk#L57> >in the spacewalk apt method, and isn't receiving input on stdin from >apt at >all. I've tried installing my version of the package on a 16.04 VM and >experience the same issue, so it doesn't seem to be an issue with a >change >in apt. The version that is currently packaged in the Ubuntu >repositories >does work, however. Any ideas where I should look next or what could be >wrong? > >Best, >Dalton Miner >dmi...@datto.com
I'm pretty sure, it's the same error I had. Do you use signed repositories? If not, that might be the error. The apt preferences you can set (e.g allow untrusted repos) do not work with the Python modules. At least, this is the experience I made, while I was debugging clients, that could not install errata anymore. The problem is, that the Python modules try to update the repos and get (on newer systems) the error, that the repos are not signed. See @philicious excellent blog here http://www.devops-blog.net/spacewalk/gpg-signing-apt-repository-in-spacewalk for how to sign repos. The "server" part is already included in the nighty repos of spacewalk. Give that a try Robert -- sent from my mobile device _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
