FS#7120 - local database lacking version information for installed dependencies

Attached to Project: Pacman
Opened by Vinay S Shastry (shastry) - Friday, 11 May 2007, 04:43 GMT
Last edited by Aaron Griffin (phrakture) - Saturday, 04 August 2007, 17:22 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Medium
Priority Normal
Reported Version 3.0.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Steps to Reproduce:
Ex:
wxmaxima depends on maxima>=5.12
install and update wxmaxima and maxima
now, do pacman -U maxima-5.10-blah
and it upgrades instead of erroring out

pacman -Qi wxmaxima doesn't show any version info for maxima in the Depends section:
Depends On : maxima libxml2 wxgtkdatabase
This task depends upon

Closed by  Aaron Griffin (phrakture)
Saturday, 04 August 2007, 17:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  In git - thanks Nagy
Comment by Dan McGee (toofishes) - Friday, 11 May 2007, 18:32 GMT
If anything, this is almost a feature request- pacman is smart sometimes, but we have a lot of work to do with regard to versioned dependencies, provides, etc.
Comment by Xavier (shining) - Sunday, 29 July 2007, 17:51 GMT
Hmm, I don't understand this bug report.
LANG=C pacman -Qi xulrunner | grep Depend
Depends On : gtk2>=2.10.11 pango>=1.16.1 gcc libidl2 mozilla-common

The version infos are there...
If the upgrade doesn't fail, it's not because pacman is stupid, it's because the version info isn't in the database.
And I don't have any idea why.
I'm not aware of any bugs in that part, pacman just copies the dependencies from the sync database to the local database anyway.
Comment by Vinay S Shastry (shastry) - Tuesday, 31 July 2007, 07:30 GMT
Hmm. I seem to have forgotten to mention here that this is when you install wxmaxima with pacman -U wxmaxima-foo (I think i told this on irc to phrak).

pacman -Qi wxmaxima is missing version info only when you install with pacman -U
Comment by Vinay S Shastry (shastry) - Tuesday, 31 July 2007, 07:33 GMT
This attachment should tell you exactly what i mean.

Pleae look at the "Depends On" info before and after pacman -U.
   pacman-terminal.log (3.2 KiB)
Comment by Xavier (shining) - Tuesday, 31 July 2007, 09:34 GMT
Oh right, that's yet another bug fixed in pacman git by Nagy :
http://projects.archlinux.org/git/?p=pacman.git;a=commit;h=7653bb93997f52848b54ab80868cd6da52808a75

The only thing I'm not sure about is why this bug only happened with -U and not with -S, but there is most certainly an explanation to that.
Maybe that dependency string is duplicated in -S code before being edited by alpm_splitdep, but not in -U code.

In any cases, it now works fine with both, thanks to the fix above.
Comment by Aaron Griffin (phrakture) - Friday, 03 August 2007, 20:11 GMT
Just checking (didn't have time to test) - this is fixed, yes?
Comment by Xavier (shining) - Saturday, 04 August 2007, 08:31 GMT
Yes, it's fixed.

Loading...