[Spacewalk-list] strange behavior with SW 2.7 and Debian 8 Clients

Tue Aug 21 18:40:02 UTC 2018

Am 21. August 2018 16:11:39 MESZ schrieb "Thomas Müller" <4thomasmueller at gmail.com>:
>Robert, your perl script does not extract Packages.gz from Ubuntu
>Repositories.
>I'm doing this in an own python script, which uses the Packages.xz.
>The run your add header script and all was fine.
>
>Thank you and the other guys for the hints.
>
>2018-08-11 15:50 GMT+02:00 Robert Paschedag <robert.paschedag at web.de>:
>
>> Am 8. August 2018 09:26:43 MESZ schrieb "Thomas Müller" <
>> 4thomasmueller at gmail.com>:
>> >Hello,
>> >I use now the advised sync script and the add-header script for
>Debian
>> >systems, it works. In Packages I can see the different Multi-Arch:
>> >headers.
>> >Then I tried this for Ubuntu 16.04 as well, but the sync script
>fails
>> >with:
>> >
>> >INFO: Repo URL:
>> >http://ftp.tu-chemnitz.de/pub/linux/ubuntu/dists/xenial-
>> security/multiverse/binary-amd64/
>> >INFO: Ubuntu root is http://ftp.tu-chemnitz.de/pub/linux/ubuntu/
>> >INFO: Fetching Packages.gz... done
>> >ERROR: Failed to uncompress Packages.gz
>> >
>> >Who knows how packages.gz from Ubuntu can be uncompressed?
>> >or should I use the packages.xz file for ubuntu instead packages.gz?
>> >
>> >file Packages-debian8.gz:
>> >gzip compressed data, max compression, from Unix
>> >
>> >file Packages-ubuntu16.gz
>> >UTF-8 Unicode text, with very long lines
>> >
>> >Regards, Thomas
>> >
>> >
>> >
>> >2018-08-04 17:19 GMT+02:00 Robert Paschedag
><robert.paschedag at web.de>:
>> >
>> >> Am 4. August 2018 17:02:50 MESZ schrieb "Thomas Müller" <
>> >> 4thomasmueller at gmail.com>:
>> >> >Ok, I saw it...
>> >> >But if I use the advised spacewalk-debian-sync script (to add
>header
>> >> >later with the other script) instead of spacewalk-repo-sync have
>all
>> >> >channels to be synchronized „from scratch“?
>> >> >The script says <numbers> of packages synced, <more> to sync.
>> >>
>> >> If you look at the code you'll see, that it's independent from
>what
>> >you
>> >> have synced. It extracts the header from all packages within the
>> >original
>> >> packages. You can then use that file later to patch the packages
>> >created by
>> >> spacewalk.
>> >>
>> >>
>> >> Robert
>> >> >
>> >> >
>> >> >Von meinem iPad gesendet
>> >> >
>> >> >Thomas Müller
>> >> >
>> >> >
>> >> >
>> >> >> Am 03.08.2018 um 19:06 schrieb Robert Paschedag
>> >> ><robert.paschedag at web.de>:
>> >> >>
>> >> >> Am 3. August 2018 12:35:52 MESZ schrieb "Thomas Müller"
>> >> ><4thomasmueller at gmail.com>:
>> >> >>> Hello,
>> >> >>>
>> >> >>> I've got it fixed by a dirty way.
>> >> >>> in /var/cache/rhn/repodata/<debian channel>
>> >> >>>
>> >> >>> mv Packages Packages.orig
>> >> >>> mv Packages.gz Packages.gz.orig
>> >> >>> cat Packages.orig | sed '/^\Package:/a Multi-Arch: allowed' >
>> >> >Packages
>> >> >>> cp Packages Packages.raw
>> >> >>> gzip Packages
>> >> >>> mv Packages.raw Packages
>> >> >>>
>> >> >>> Resigning via secureApt.sh, on clients apt-get update.
>> >> >>> works on 3 testsystems :-)
>> >> >>> Debian9 has right now no problem
>> >> >>>
>> >> >>> Many thanks.
>> >> >>>
>> >> >>> 2018-08-02 18:16 GMT+02:00 Robert Paschedag
>> >> ><robert.paschedag at web.de>:
>> >> >>>
>> >> >>>> Am 2. August 2018 18:10:09 MESZ schrieb "Thomas Müller" <
>> >> >>>> 4thomasmueller at gmail.com>:
>> >> >>>>> An additional question: If I use the spacewalk-debian-sync
>> >script
>> >> >to
>> >> >>>>> fix the multiarch header problem should I use as repo
>> >binary-all
>> >> >>>>> instead of binary-amd64 for main, contrib and non-free?
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Von meinem iPad gesendet
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>> Am 02.08.2018 um 17:20 schrieb Robert Paschedag
>> >> >>>>> <robert.paschedag at web.de>:
>> >> >>>>>>
>> >> >>>>>> Am 2. August 2018 12:30:24 MESZ schrieb "Thomas Müller"
>> >> >>>>> <4thomasmueller at gmail.com>:
>> >> >>>>>>> Hi @all,
>> >> >>>>>>>
>> >> >>>>>>> we've set up a spacewalk server 2.7 and registered
>debian8,
>> >> >>> debian8
>> >> >>>>> and
>> >> >>>>>>> oracle linux systems to it.
>> >> >>>>>>> The oracle and debian9 systems work like a charm with
>> >spacewalk,
>> >> >>> but
>> >> >>>>>>> the
>> >> >>>>>>> debian8 systems removes all rhn- and spacewalk tools after
>> >> >>>>> installing a
>> >> >>>>>>> package.
>> >> >>>>>>>
>> >> >>>>>>> Some investigations shows any unresolved dependencies
>> >> >>> (python:any)
>> >> >>>>> (??)
>> >> >>>>>>> But - if we change the /etc/apt/sources.list to let the
>> >system
>> >> >>> look
>> >> >>>>> at
>> >> >>>>>>> the
>> >> >>>>>>> original debian repositories all works as expected.
>> >> >>>>>>>
>> >> >>>>>>> sources.list spacewalk only:
>> >> >>>>>>>
>> >> >>>>>>> # Debian 8 (Jessie)
>> >> >>>>>>> #
>> >> >>>>>>> # wird durch Spacewalk verwaltet
>> >> >>>>>>> #
>> >> >>>>>>> # deb http://ftp.de.debian.org/debian/ jessie main
>> >> >>>>>>> # deb-src http://ftp.de.debian.org/debian/ jessie main
>> >> >>>>>>>
>> >> >>>>>>> # deb http://security.debian.org/ jessie/updates main
>contrib
>> >> >>>>>>> # deb-src http://security.debian.org/ jessie/updates main
>> >> >contrib
>> >> >>>>>>>
>> >> >>>>>>> # jessie-updates, previously known as 'volatile'
>> >> >>>>>>> # deb http://ftp.de.debian.org/debian/ jessie-updates main
>> >> >>> contrib
>> >> >>>>>>> # deb-src http://ftp.de.debian.org/debian/ jessie-updates
>> >main
>> >> >>>>> contrib
>> >> >>>>>>>
>> >> >>>>>>> spacewalk.list:
>> >> >>>>>>>
>> >> >>>>>>> deb [trusted=yes] spacewalk://it-srv-space01.nbintern.net
>> >> >debian8
>> >> >>>>>>> repodata
>> >> >>>>>>> deb [trusted=yes] spacewalk://it-srv-space01.nbintern.net
>> >> >>>>>>> debian8-main-security repodata
>> >> >>>>>>> deb [trusted=yes] spacewalk://it-srv-space01.nbintern.net
>> >> >>>>>>> debian8-main-update repodata
>> >> >>>>>>> deb [trusted=yes] spacewalk://it-srv-space01.nbintern.net
>> >> >>>>>>> debian8-contrib
>> >> >>>>>>> repodata
>> >> >>>>>>> deb [trusted=yes] spacewalk://it-srv-space01.nbintern.net
>> >> >>>>>>> debian8-contrib-security repodata
>> >> >>>>>>> deb [trusted=yes] spacewalk://it-srv-space01.nbintern.net
>> >> >>>>>>> debian8-contrib-update repodata
>> >> >>>>>>> deb [trusted=yes] spacewalk://it-srv-space01.nbintern.net
>> >> >>>>>>> debian8-nonfree
>> >> >>>>>>> repodata
>> >> >>>>>>> deb [trusted=yes] spacewalk://it-srv-space01.nbintern.net
>> >> >>>>>>> debian8-nonfree-security repodata
>> >> >>>>>>> deb [trusted=yes] spacewalk://it-srv-space01.nbintern.net
>> >> >>>>>>> debian8-nonfree-update repodata
>> >> >>>>>>> deb [trusted=yes] spacewalk://it-srv-space01.nbintern.net
>> >> >>>>> debian8-main
>> >> >>>>>>> repodata
>> >> >>>>>>>
>> >> >>>>>>> apt install atop:
>> >> >>>>>>>
>> >> >>>>>>> Paketlisten werden gelesen... Fertig
>> >> >>>>>>> Abhängigkeitsbaum wird aufgebaut.
>> >> >>>>>>> Statusinformationen werden eingelesen.... Fertig
>> >> >>>>>>> atop ist schon die neueste Version.
>> >> >>>>>>> Probieren Sie »apt-get -f install«, um dies zu
>korrigieren:
>> >> >>>>>>> Die folgenden Pakete haben unerfüllte Abhängigkeiten:
>> >> >>>>>>> apt-transport-spacewalk : Hängt ab von: python:any (>=
>> >2.6.6-7~)
>> >> >>> ist
>> >> >>>>>>> aber
>> >> >>>>>>> nicht installierbar
>> >> >>>>>>> python-cffi : Hängt ab von: python:any (>= 2.7.5-5~) ist
>aber
>> >> >>> nicht
>> >> >>>>>>> installierbar
>> >> >>>>>>> python-cryptography : Hängt ab von: python:any (>=
>2.7.5-5~)
>> >ist
>> >> >>>>> aber
>> >> >>>>>>> nicht installierbar
>> >> >>>>>>> python-openssl : Hängt ab von: python:any (>= 2.7.5-5~)
>ist
>> >aber
>> >> >>>>> nicht
>> >> >>>>>>> installierbar
>> >> >>>>>>>                Hängt ab von: python:any (< 2.8) ist aber
>> >nicht
>> >> >>>>>>> installierbar
>> >> >>>>>>> python-pkg-resources : Hängt ab von: python:any (>= 2.7)
>ist
>> >> >aber
>> >> >>>>> nicht
>> >> >>>>>>> installierbar
>> >> >>>>>>>                      Hängt ab von: python:any (< 2.8) ist
>> >aber
>> >> >>>>> nicht
>> >> >>>>>>> installierbar
>> >> >>>>>>> python-pycparser : Hängt ab von: python:any (>= 2.7.5-5~)
>ist
>> >> >>> aber
>> >> >>>>>>> nicht
>> >> >>>>>>> installierbar
>> >> >>>>>>>                  Hängt ab von: python:any (< 2.8) ist aber
>> >nicht
>> >> >>>>>>> installierbar
>> >> >>>>>>> python-six : Hängt ab von: python:any (>= 2.7.5-5~) ist
>aber
>> >> >>> nicht
>> >> >>>>>>> installierbar
>> >> >>>>>>>        Hängt ab von: python:any (< 2.8) ist aber nicht
>> >> >>>>> installierbar
>> >> >>>>>>> rhn-client-tools : Hängt ab von: python:any ist aber nicht
>> >> >>>>>>> installierbar
>> >> >>>>>>>                Empfiehlt: apt-spacewalk ist aber nicht
>> >> >>>>> installierbar
>> >> >>>>>>> E: Unerfüllte Abhängigkeiten. Versuchen Sie »apt-get -f
>> >install«
>> >> >>>>> ohne
>> >> >>>>>>> Angabe eines Pakets (oder geben Sie eine Lösung an).
>> >> >>>>>>>
>> >> >>>>>>> apt install -f:
>> >> >>>>>>>
>> >> >>>>>>> Paketlisten werden gelesen... Fertig
>> >> >>>>>>> Abhängigkeitsbaum wird aufgebaut.
>> >> >>>>>>> Statusinformationen werden eingelesen.... Fertig
>> >> >>>>>>> Abhängigkeiten werden korrigiert ... Fertig
>> >> >>>>>>> Das folgende Paket wurde automatisch installiert und wird
>> >nicht
>> >> >>> mehr
>> >> >>>>>>> benötigt:
>> >> >>>>>>> python-ply
>> >> >>>>>>> Verwenden Sie »apt-get autoremove«, um es zu entfernen.
>> >> >>>>>>> Die folgenden Pakete werden ENTFERNT:
>> >> >>>>>>> apt-transport-spacewalk python-cffi python-cryptography
>> >> >>>>> python-openssl
>> >> >>>>>>> python-pkg-resources python-pycparser python-rhn
>python-six
>> >> >>>>>>> rhn-client-tools rhncfg rhnsd
>> >> >>>>>>> 0 aktualisiert, 0 neu installiert, 11 zu entfernen und 1
>> >nicht
>> >> >>>>>>> aktualisiert.
>> >> >>>>>>> Nach dieser Operation werden 6.971 kB Plattenplatz
>> >freigegeben.
>> >> >>>>>>> Möchten Sie fortfahren? [J/n]
>> >> >>>>>>>
>> >> >>>>>>> As stated, if the souces.list is
>> >> >>>>>>>
>> >> >>>>>>> # Debian 8 (Jessie)
>> >> >>>>>>> #
>> >> >>>>>>> # wird durch Spacewalk verwaltet
>> >> >>>>>>> #
>> >> >>>>>>> deb http://ftp.de.debian.org/debian/ jessie main
>> >> >>>>>>> # deb-src http://ftp.de.debian.org/debian/ jessie main
>> >> >>>>>>>
>> >> >>>>>>> deb http://security.debian.org/ jessie/updates main
>contrib
>> >> >>>>>>> # deb-src http://security.debian.org/ jessie/updates main
>> >> >contrib
>> >> >>>>>>>
>> >> >>>>>>> # jessie-updates, previously known as 'volatile'
>> >> >>>>>>> deb http://ftp.de.debian.org/debian/ jessie-updates main
>> >contrib
>> >> >>>>>>> # deb-src http://ftp.de.debian.org/debian/ jessie-updates
>> >main
>> >> >>>>> contrib
>> >> >>>>>>>
>> >> >>>>>>> no issue....
>> >> >>>>>>
>> >> >>>>>> This is because of the missing MultiArch header within the
>> >> >>>>> packages.gz files created by spacewalk.
>> >> >>>>>>
>> >> >>>>>> Strange enough that your Debian 9 systems are running. They
>> >> >should
>> >> >>>>> have the same problem.
>> >> >>>>>>
>> >> >>>>>> Robert
>> >> >>>>>> --
>> >> >>>>>> sent from my mobile device
>> >> >>>>
>> >> >>>> Just leave it as it is right now. That should fit.
>> >> >>>>
>> >> >>>> This is all just a workaround. The main problem currently is,
>> >that
>> >> >>> there
>> >> >>>> is no field (or tables) within the DB scheme to store this
>> >header
>> >> >>> within
>> >> >>>> the DB, so this can be put into the packages.gz file while it
>> >gets
>> >> >>> created.
>> >> >>>>
>> >> >>>> Robert
>> >> >>>> --
>> >> >>>> sent from my mobile device
>> >> >>>>
>> >> >>
>> >> >> This will not work.
>> >> >>
>> >> >> It's because "allowed" is not the only possible value for a
>> >package.
>> >> >>
>> >> >> You might want to try a
>> >> >>
>> >> >> grep ^Multi packages.gz | sort | uniq -c
>> >> >>
>> >> >> to get an idea.
>> >> >>
>> >> >> robert.paschedag at netlution.de
>> >> >> --
>> >> >> sent from my mobile device
>> >>
>> >>
>> >> --
>> >> sent from my mobile device
>> >>
>>
>> Well...I think the script should be able to uncompress the Ubuntu
>packages
>> files... At least...I remember it was also tested with Ubuntu.
>>
>> Robert
>> --
>> sent from my mobile device
>>

Feel free to create a pull request at https://github.com/philicious/spacewalk-scripts

So everybody will gain from this.

Robert
-- 
sent from my mobile device