[pacman-dev] Pacman 3.0.5-3: strange behaviour
Hi guys, I noticed that new pacman release doesn't ever show the message "is up to date" when I run pacman -Sy (or -Syu). Pacman thinks there are always new dbs. -- Giovanni Scafora Arch Linux Trusted User (voidnull) http://www.archlinux.org linuxmania@gmail.com
On 8/17/07, Giovanni Scafora <linuxmania@gmail.com> wrote:
Hi guys,
I noticed that new pacman release doesn't ever show the message "is up to date" when I run pacman -Sy (or -Syu). Pacman thinks there are always new dbs.
Hmm, I see this behavior as well. I'm not sure what in the patch I applied would cause this, as we never touch any of the sync db download code: http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/base/pacman/pacman-cumulative.patch?rev=1.1&content-type=text/vnd.viewcvs-markup 3.0.5-2 already included the removal of the chmod lines, so that can be ruled out. The other code in add.c shouldn't affect DB downloads at all, so that can be eliminated as well. That leaves two possibilities: the large file support, or the config file parsing. I would tend to think the latter shouldn't affect this issue, so perhaps large file support is buggy? If anyone wants to trial it by rebuilding and installing without large file support (use the --disable-largefile flag to ./configure), it might help us get to the bottom of this issue. AC_SYS_LARGEFILE documentation: http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_node/autoconf... EDIT: I did the above and rebuilt without large file support, and it did in fact fix this issue. Very interesting. The root of it looks to be with the .lastupdate files: with largefile support disabled: $ cat /var/lib/pacman/current/.lastupdate 20070817163345 with largefile support enabled: $ cat /var/lib/pacman/current/.lastupdate 19350919013712 Clearly something wrong in the second case. Time to do some digging. -Dan
On 8/17/07, Dan McGee <dpmcgee@gmail.com> wrote:
On 8/17/07, Giovanni Scafora <linuxmania@gmail.com> wrote:
Hi guys,
I noticed that new pacman release doesn't ever show the message "is up to date" when I run pacman -Sy (or -Syu). Pacman thinks there are always new dbs.
Hmm, I see this behavior as well. I'm not sure what in the patch I applied would cause this, as we never touch any of the sync db download code: http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/base/pacman/pacman-cumulative.patch?rev=1.1&content-type=text/vnd.viewcvs-markup
3.0.5-2 already included the removal of the chmod lines, so that can be ruled out. The other code in add.c shouldn't affect DB downloads at all, so that can be eliminated as well.
That leaves two possibilities: the large file support, or the config file parsing. I would tend to think the latter shouldn't affect this issue, so perhaps large file support is buggy?
If anyone wants to trial it by rebuilding and installing without large file support (use the --disable-largefile flag to ./configure), it might help us get to the bottom of this issue.
AC_SYS_LARGEFILE documentation: http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_node/autoconf...
EDIT: I did the above and rebuilt without large file support, and it did in fact fix this issue. Very interesting. The root of it looks to be with the .lastupdate files:
with largefile support disabled: $ cat /var/lib/pacman/current/.lastupdate 20070817163345
with largefile support enabled: $ cat /var/lib/pacman/current/.lastupdate 19350919013712
Clearly something wrong in the second case. Time to do some digging.
Digging reveals the problem lies with libdownload- as it wasn't compiled with large file support, some of the structs/sizes of things are different, thus resulting in the erroneous extra downloads. It can be fixed by rebuilding libdownload with large file support which I have done locally. I will push this verision to the repos shortly once I figure out a more sane way of doing it. -Dan
2007/8/18, Dan McGee <dpmcgee@gmail.com>:
Digging reveals the problem lies with libdownload- as it wasn't compiled with large file support, some of the structs/sizes of things are different, thus resulting in the erroneous extra downloads. It can be fixed by rebuilding libdownload with large file support which I have done locally. I will push this verision to the repos shortly once I figure out a more sane way of doing it.
Pacman works fine now. Thanks. -- Giovanni Scafora Arch Linux Trusted User (voidnull) http://www.archlinux.org linuxmania@gmail.com
participants (2)
-
Dan McGee
-
Giovanni Scafora