Welcome to the Pacman bug collection. Please search the current bugs and feature requests before filing a new one! Use advanced search and select "Search in Comments".

* Please select the correct category and version.
* Write a descriptive summary, background info, and provide a reproduceable test case whenever possible.
Tasklist

FS#5005 - pacman dependency check

Attached to Project: Pacman
Opened by Hussam Al-Tayeb (hussam) - Sunday, 09 July 2006, 10:01 GMT-5
Last edited by Dan McGee (toofishes) - Thursday, 15 November 2007, 10:29 GMT-5
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Xavier (shining)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 2.9.8
Due in Version 3.1.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

pacman should have a option -check "pacman -check" ( like in apt-get )
This option would check if there are any broken dependencies in all packages installed on the system.
apt already has this, not sure about rpm.
This task depends upon

View Dependency Graph

This task blocks these from closing
 FS#8109 - Pacman 3.1 Release Roadmap 
Closed by  Dan McGee (toofishes)
Thursday, 15 November 2007, 10:29 GMT-5
Reason for closing:  Implemented
Additional comments about closing:  Use testdb in pacman 3.1/GIT release
Comment by Roman Kyrylych (Romashka) - Thursday, 15 November 2007, 06:48 GMT-5
testdb?
Comment by Dan McGee (toofishes) - Thursday, 15 November 2007, 09:10 GMT-5
As far as I know, yes. Xavier, just give me a thumbs up here and I'll close this if testdb in fact covers it.

(Note to anyone else that may close it- add it to the 3.1 issue catcher too)
Comment by Xavier (shining) - Thursday, 15 November 2007, 09:53 GMT-5
Indeed, that's exactly what testdb does.
It used to check broken requiredby and broken dependencies, and now, it only looks for broken dependencies.
There was still a discussion to reintroduce this as a pacman option though.
This might make the code easier to extend, for example with conflicts checking :
check that there aren't two packages locally installed that conflict with each other.

In any cases, this feature will stay available, so this can be closed.

Loading...