Weblog entry #3 for JulienV
See all weblog entries made by JulienV.
Since I moved from debpool to reprepro following to Steve's article, I noticed that, when updating apt databases, I get the following lines:
julien@hathor:~$ LANG=C sudo aptitude update | grep packages.kirya.net Ign http://debian.kirya.net internal/contrib Packages Get:4 http://packages.kirya.net unstable Release.gpg [189B] Hit http://packages.kirya.net unstable Release Ign http://packages.kirya.net unstable/main Packages Ign http://packages.kirya.net unstable/contrib Packages Ign http://packages.kirya.net unstable/non-free Packages Hit http://packages.kirya.net unstable/main Packages Hit http://packages.kirya.net unstable/contrib Packages Hit http://packages.kirya.net unstable/non-free Packages
The same happens with apt-get update.
I don't understand what the "Ign" prefix means, I guess "Ignore", but ignore what?
All the packages are downloadable and installable without any warning (I thought it could be linked with secure apt and something broken with my signed archive).
Does someone have an idea about this cosmetic problem?
Cheers,
Julien
Comments on this Entry
[ Send Message | View Steve's Scratchpad | View Weblogs ]
I'm pretty sure that it means that it has ignored re-downloading a Packages file because it knows it hasn't changed.
If you delete your local copies of the package(s) files from /var/lib/apt/lists you'll find they are downloaded correctly.
You can see the same thing if you run "apt-get update" against the Debian servers twice, without anything having changed between the two runs.
[ Parent | Reply to this comment ]
Thanks for your answer.
When doing an 'apt-get update' twice in a few seconds on Debian servers, I only see some 'Hit...'
When something has changed, I see 'Get...'.
It does only happen with my repository.
Cheers,
Julien
[ Parent | Reply to this comment ]
[ Send Message | View Steve's Scratchpad | View Weblogs ]
Hmmm looks like I was mistaken then. I'm not sure what is going on!
When I fetch against my site I see:
skx@itchy:~$ update Ign http://www.steve.org.uk sarge Release.gpg Hit http://www.steve.org.uk sarge Release Hit http://www.steve.org.uk sarge/main Packages Hit http://www.steve.org.uk sarge/contrib Packages Hit http://www.steve.org.uk sarge/non-free Packages Hit http://www.steve.org.uk sarge/main Sources Hit http://www.steve.org.uk sarge/contrib Sources Hit http://www.steve.org.uk sarge/non-free Sources
The first line is the only one ignored - and that is a 404, there is no Release.gpg upon the server. I wonder if that is related...
[ Parent | Reply to this comment ]
Hope this helps
Julien
[ Parent | Reply to this comment ]
[ Parent | Reply to this comment ]
Yes, thank you for the hint:
# tail -f /var/log/apache2/packages-error.log [Fri Dec 09 07:02:21 2005] [error] [client 192.168.1.51] File does not exist: /var/www/packages.kirya.net/dists/unstable/main/binary-i386/Packa ges.bz2
It seems that new apt versions look for a bz2 compressed Packages file before anything else.
I will then have to try and apply reprepro example to use bzip2.
Thank you again to both for halping!
Cheers,
Julien
[ Parent | Reply to this comment ]
Thanks again
Julien
[ Parent | Reply to this comment ]
Hi,
reprepro 0.8 has now been in unstable for a few days. This new version includes native bzip2 compression.
I have built a backport for Sarge: http://packages.kirya.net/packages.php?dist=stable
Cheers,
Julien
[ Parent | Reply to this comment ]