FS#12291 - Pacman asks twice to replace packages

Attached to Project: Pacman
Opened by sinister99 (sinister99) - Sunday, 30 November 2008, 20:17 GMT
Last edited by Xavier (shining) - Saturday, 17 January 2009, 17:24 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Dan McGee (toofishes)
Architecture i686
Severity Low
Priority Normal
Reported Version 3.2.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

Upon upgrading to xorg 7.4 I was asked twice to replace packages (answered yes to all).

Steps to Reproduce:

:: Replace esd with extra/esound? [Y/n]
:: Replace synaptics with extra/xf86-input-synaptics? [Y/n]
:: Starting full system upgrade...
:: Replace esd with extra/esound? [Y/n]
:: Replace synaptics with extra/xf86-input-synaptics? [Y/n]
resolving dependencies...
warning: dependency cycle detected:
warning: xorg-server will be installed before its catalyst-utils dependency
looking for inter-conflicts...

Remove (2): esd-0.2.40-1 synaptics-0.14.6.99-2
This task depends upon

Closed by  Xavier (shining)
Saturday, 17 January 2009, 17:24 GMT
Reason for closing:  Works for me
Additional comments about closing:  No one is able to reproduce that bug, and besides it is not important.
Please reopen if you ever manage to reproduce and add some information.
Comment by Dan McGee (toofishes) - Sunday, 30 November 2008, 22:19 GMT
I'm not quite sure what happened here. Do you remember exactly what command you used? The entire output would have been much appreciated here, as adding the -y flag (-Syu) may produce different results than just doing an -Su operation.
Comment by sinister99 (sinister99) - Sunday, 30 November 2008, 23:23 GMT
I used pacman -Syu. I aborted that time, and later did a pacman -Su and none of these replaces were mentioned.
Comment by Dan McGee (toofishes) - Sunday, 30 November 2008, 23:26 GMT
My guess is we somehow do the replaces check twice because of the sync update? Anyone else have ideas here? I couldn't trace the double checking in the code, but maybe you know this better.
Comment by Nagy Gabor (combo) - Tuesday, 02 December 2008, 21:50 GMT
Off-topic: Why are our output logs so messy? (Probably ":: Starting full system upgrade..." should come first.)

I guess, there was a %REPLACES% field duplication in our sync dbs. Our find_replacement code ignores the fact that we have already selected the to-be-replaced package. I don't know if this behavior is good, but probably this behavior was introduced to handle multiple replacements (I mean, foo *and* bar can replace baz).
Comment by Xavier (shining) - Friday, 16 January 2009, 15:08 GMT
I find it strange that there are the two same messages displayed both before and after the "system upgrade" message.
If there was a RELACES field duplication, I would expect the following output :
:: Starting full system upgrade...
:: Replace esd with extra/esound? [Y/n]
:: Replace esd with extra/esound? [Y/n]
:: Replace synaptics with extra/xf86-input-synaptics? [Y/n]
:: Replace synaptics with extra/xf86-input-synaptics? [Y/n]

Also it looks really strange that the same mistake was made on two replacements.

What the user report is very strange as well :
"I used pacman -Syu. I aborted that time, and later did a pacman -Su and none of these replaces were mentioned."
So duplicated messages in case of -Syu, and none at all in case of -Su? Very weird.

Anyway, if we cannot figure out what could have happened without further informations, we might as well just close this bug indeed :P
Comment by Nagy Gabor (combo) - Friday, 16 January 2009, 16:21 GMT
"If there was a RELACES field duplication, I would expect the following output:..."

You are right, good catch. OK, then we should wait for user feedback.
Btw, I have no clue what happened here.
Comment by sinister99 (sinister99) - Friday, 16 January 2009, 17:37 GMT
I haven't had this happen since, though replaces aren't that common. ???

Loading...