bugSynaptic - Bugs: bug #12529, Difficulty downgrading packages...


bug #12529: Difficulty downgrading packages with dependencies

Submitter:  None
Submitted:  Fri 01 Apr 2005 06:45:29 PM UTC
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup

Fri 01 Apr 2005 06:45:29 PM UTC, original submission:  

There are some difficulties that I have found with downgrading packages that have dependencies on the version that I am changing.  It would be nice if downgrades were as easy as upgrades (though I completely understand the difficulty in this).  There are two particular situations that I have been frustrated with:

1) If the package to be downgraded is depended on at that version by other packages.  This will usually notify you that those packages will be removed because of breaking dependencies.  However it is commonly the case (I'm thinking *-dev packages) where the dependent package could be downgraded and, as a result, no package removals would be necessary.

2) If a package being downgraded depends on a package of the current version.  This is even more frustrating.  Synaptic will actually just ignore the request and not provide an explanation.  If the depended package were downgraded along with this package all conflicts would be resolved.

The current method I have been using to get around this is to let synaptic remove the prackages, and before I commit I'll force the versions to what they need to be.  This is difficult and annoying.  I see two ways of fixing this, an easy to implement but less automated way, and a difficult to implement but highly optimized way.  The easy way is to actually support force version for packages under a multiple select and try and force all of them not just the last clicked.  The other way would be to check to see when a downgrade is requested that causes conflicts if there is a set of version changes that will fix the problem.  In either case I think allowing force version on a selection of packages is a must.  This (ideally) would let you even deal with different packages that have different versions to choose from all collected together.

Hope this is constructive, I enjoy this software and hope you guys keep up the good work.



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


CC list is empty


There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.


No changes have been made to this item

Back to the top

Powered by Savane 3.13-4b48.
Corresponding source code