FS#1162 - Coding errors in db.c
Attached to Project:
Pacman
Opened by Mircea Bardac (IceRAM) - Wednesday, 21 July 2004, 12:33 GMT
Last edited by Jason Chu (jason) - Saturday, 24 July 2004, 22:53 GMT
Opened by Mircea Bardac (IceRAM) - Wednesday, 21 July 2004, 12:33 GMT
Last edited by Jason Chu (jason) - Saturday, 24 July 2004, 22:53 GMT
|
Details
Pacman v2.8.1
I've recently tried to update my system with -Syu but encountered some lines like this ones: check3: !strncmp(/usr/lib/libldap-2.2.so.7.0.6, /usr/lib/libldap-2.2.so.7.0.6) check3: !strncmp(/usr/lib/libldap_r-2.2.so.7.0.6, /usr/lib/libldap_r-2.2.so.7.0.6) check1: is_in(usr/man/man3/lber-types.3.gza, openldap->files) check1: is_in(usr/man/man3/lber-types.3.gz, openldap->files) check1: is_in(usr/man/man3/lber-types.3.gze.3.gz, openldap->files) check1: is_in(usr/man/man3/lber-types.3.gz3.gz, openldap->files) check1: is_in(usr/man/man3/lber-types.3.gz.gz, openldap->files) A short look through the code revealed that the resposible lines for the "checks" above belong to Jason's patch about symlinks. Please note that the files/symlinks mentioned in the checks do not exist (eg:usr/man/man3/lber-types.3.gze.3.gz) - some kind of bad string manipulation is in the middle. Maybe -v switch should be more verbose in the "Checking for conflicts" section.. or another switch could be usefull, because it's very difficult to debug the recent segfaults & errors caused right in this part of the update process. |
This task depends upon
output-2.8.1.txt
bad-stuff.patch
Jason, mind taking a look at those ".3gze.3.gz" strings? Looks like it's missing a properly-placed '\0' character in the string manipulation.
Is it just openldap that's being upgraded or others as well?
I have to mention that pacman 2.8.2 took CPU(!!!) TIME:
- 7sec loading packages... etc
- 3m25sec checking for file conflicts (I'm sure that the pre-check for file conflicts didn't even take)
That's A LOT!.. Too much I can say...