<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'> On 2019-02-22 22:30, Robert Paschedag wrote: <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"> <div class="pre" style="margin: 0; padding: 0; font-family: monospace">On 2/22/19 7:53 PM, Robert Paschedag wrote: <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Am 22. Februar 2019 13:11:00 MEZ schrieb Florin Portase <<a href="mailto:portase.florin@medianetork.ro">portase.florin@medianetork.ro</a>>: <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">On 2019-02-13 10:56, Florin Portase wrote: <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Hello, I just have upgraded the spacewalk server from 2.7 => 2.9. I have applied also the sql patch from</blockquote> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1661347" target="_blank" rel="noopener noreferrer">https://bugzilla.redhat.com/show_bug.cgi?id=1661347</a> <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"> + upgraded the clients from : </blockquote> <a href="http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.9:/debclients/" target="_blank" rel="noopener noreferrer">http://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.9:/debclients/</a> <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"> Just to mention spacewalk 2.7 + patches was working just fine for</blockquote> both debian & ubuntu. <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"> Now, for ubuntu 16.05 I have over 100 packages marked as up-gradable(</blockquote> over and over....) <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"> _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank" rel="noopener noreferrer">https://www.redhat.com/mailman/listinfo/spacewalk-list</a></blockquote> So, after digging through SPW archive Dec '18 til Feb '19 finally I come to something more acceptable: 1. sync script for Ubuntu channels 2. "spacewalk-add-debian-multiarch-header.py.NEW " took it from "<a href="https://www.redhat.com/archives/spacewalk-list/2018-December/msg00017.html" target="_blank" rel="noopener noreferrer">https://www.redhat.com/archives/spacewalk-list/2018-December/msg00017.html</a>" wget -q <a href="http://de.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/Packages.gz" target="_blank" rel="noopener noreferrer">http://de.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-amd64/Packages.gz</a> \ -O /tmp/Packages-xenial-main.gz && gunzip -f /tmp/Packages-xenial-main.gz wget -q <a href="http://cz.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/Packages.gz" target="_blank" rel="noopener noreferrer">http://cz.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-amd64/Packages.gz</a> \ -O /tmp/Packages-xenial-updates.gz && gunzip -f /tmp/Packages-xenial-updates.gz wget -q <a href="http://cz.archive.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages.gz" target="_blank" rel="noopener noreferrer">http://cz.archive.ubuntu.com/ubuntu/dists/xenial-security/main/binary-amd64/Packages.gz</a> \ -O /tmp/Packages-xenial-security.gz && gunzip -f /tmp/Packages-xenial-security.gz s=180 trap 'echo "Ctrl-C detected."' 2 for (( i=$s ; i>0; i--)); do #printf '\rFinishing sync in: %2d seconds' $i; sleep 1 echo -ne "\rFinishing sync in: $i seconds\033[0K"; sleep 1 done echo -e "\nSync completed!" trap 2 $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW $_PKG_MAIN/Packages /tmp/Packages-xenial-main $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW $_PKG_UPD/Packages /tmp/Packages-xenial-updates $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW $_PKG_SEC/Packages /tmp/Packages-xenial-security $_BIN_PATH/spacewalk-add-debian-multiarch-header.py.NEW $_PKG_UNIV/Packages /tmp/Packages-xenial-universe </blockquote> </blockquote> Below is your error Packages.new is the "modified" Packages which you rename and *afterwards* use its "modified" timestamp. This is wrong. You have to use the "modified" timestamp of the "original" (the one generated by Spacewalk) packages file So when you have the original "Packages" file (by spacewalk), do - run the <add_header> script (which generates "Packages.new") - gzip -c Packages.new > Packages.gz - touch -r Packages Packages.new Packages.gz && mv Packages.new Packages So you have transferred the original timestamp to the new files and all set to "secure" your repo then. Robert <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"> <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"> /bin/mv $_PKG_MAIN/Packages.new $_PKG_MAIN/Packages /bin/mv $_PKG_SEC/Packages.new $_PKG_SEC/Packages /bin/mv $_PKG_UPD/Packages.new $_PKG_UPD/Packages /bin/mv $_PKG_UNIV/Packages.new $_PKG_UNIV/Packages gzip < $_PKG_MAIN/Packages > $_PKG_MAIN/Packages.gz gzip < $_PKG_UPD/Packages > $_PKG_UPD/Packages.gz gzip < $_PKG_SEC/Packages > $_PKG_SEC/Packages.gz gzip < $_PKG_UNIV/Packages > $_PKG_UNIV/Packages.gz cd $_PKG_MAIN $_BIN_PATH/secureApt.sh xenial xenial-main touch -r Packages.gz Packages cd $_PKG_UPD $_BIN_PATH/secureApt.sh xenial xenial-updates touch -r Packages.gz Packages cd $_PKG_SEC $_BIN_PATH/secureApt.sh xenial xenial-security touch -r Packages.gz Packages So just to resume, SYNC =>OK, applying ALL missing headers =>OK, now the packages that are showed as up-gradable dropped from ~120 to only 6 ( base-files libbind9-140 libisc160 libisccc140 libisccfg140 liblwres141 ) ~~BUT~~ Here I run into another problem, it seems taskomatic is generating Package files over and over ( touch -r Packages.gz Packages seems to have no effect)</blockquote> This seems to be new. You might have to check within code, at which conditions a rebuild of the Packages file gets triggered I'm still on SW2.7 so I cannot test on my environment. Robert </blockquote> </div> </blockquote> Hi Rober, So far so good, here is the modified part of sync script: cd $_PKG_MAIN touch -r Packages.gz Packages.new && mv Packages.new Packages gzip < $_PKG_MAIN/Packages > $_PKG_MAIN/Packages.gz touch -r Packages Packages.gz $_BIN_PATH/secureAptDeb.sh stretch stretch-main cd $_PKG_UPD touch -r Packages.gz Packages.new && mv Packages.new Packages gzip < $_PKG_UPD/Packages > $_PKG_UPD/Packages.gz touch -r Packages Packages.gz $_BIN_PATH/secureAptDeb.sh stretch stretch-updates cd $_PKG_SEC touch -r Packages.gz Packages.new && mv Packages.new Packages gzip < $_PKG_SEC/Packages > $_PKG_SEC/Packages.gz touch -r Packages Packages.gz $_BIN_PATH/secureAptDeb.sh stretch stretch-security cd $_PKG_UNIV touch -r Packages.gz Packages.new && mv Packages.new Packages gzip < $_PKG_SEC/Packages > $_PKG_SEC/Packages.gz touch -r Packages Packages.gz $_BIN_PATH/secureAptDeb.sh stretch stretch-universe After this, taskomatic wasn't triggered BUT:: ON client side: => apt-get update && apt-get upgrade => taskomatic is triggered and Pakages && Packages.gz are regenerated :( ing ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/usr/share/java/ehcache-core.jar!/ehcache-failsafe.xml INFO | jvm 1 | 2019/02/26 14:58:00 | 2019-02-26 14:58:00,038 [DefaultQuartzScheduler_Worker-2] INFO com.redhat.rhn.taskomatic.task.ChannelRepodata - In the queue: 3 INFO | jvm 1 | 2019/02/26 14:58:00 | 2019-02-26 14:58:00,188 [Thread-561] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - File Modified Date:2019-02-26 04:42:14 CET INFO | jvm 1 | 2019/02/26 14:58:00 | 2019-02-26 14:58:00,188 [Thread-560] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - File Modified Date:2019-02-26 04:40:05 CET INFO | jvm 1 | 2019/02/26 14:58:00 | 2019-02-26 14:58:00,188 [Thread-561] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Channel Modified Date:2019-02-24 17:58:28 CET INFO | jvm 1 | 2019/02/26 14:58:00 | 2019-02-26 14:58:00,188 [Thread-560] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Channel Modified Date:2019-02-26 14:29:17 CET INFO | jvm 1 | 2019/02/26 14:58:00 | 2019-02-26 14:58:00,238 [Thread-561] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Generating new DEB repository for channel stretch-main INFO | jvm 1 | 2019/02/26 14:58:00 | 2019-02-26 14:58:00,247 [Thread-560] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Generating new DEB repository for channel stretch-updates INFO | jvm 1 | 2019/02/26 14:58:06 | 2019-02-26 14:58:05,957 [Thread-560] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Repository metadata generation for 'stretch-updates' finished in 5 seconds </body></html>