Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#7601 - pacman -c option keeps wrong jdk and jre ?

Attached to Project: Pacman
Opened by Paul Robson (paulr) - Tuesday, 10 July 2007, 18:18 GMT
Last edited by Dan McGee (toofishes) - Sunday, 15 July 2007, 13:30 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 3.0.5
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

If you install openoffice-base, jdk and jre this pulls in the "update 1" versions of jdk and jre - previously this was 6.2 (jdk) and 6.3 (jre).

However, if you pacman using the -c option (tidy up) the u1 versions are deleted and the 6.2/3 versions are kept.

No real problem except for possible reinstallation.
This task depends upon

Closed by  Dan McGee (toofishes)
Sunday, 15 July 2007, 13:30 GMT
Reason for closing:  Duplicate
Additional comments about closing:  dupe of  bug 4995 
Comment by Jens Adam (byte) - Tuesday, 10 July 2007, 23:36 GMT
This belongs to project Pacman (3), not Arch Linux (1).

Yes, this is typical for packages that were installed due to the force=y flag.
Comment by Roman Kyrylych (Romashka) - Sunday, 15 July 2007, 11:35 GMT
moved to pacman project.

yep, -c is pretty simple and doesn't check for renamed/replaced packages
Comment by Dan McGee (toofishes) - Sunday, 15 July 2007, 13:30 GMT
-c is crap, we know. It has always worked off package name heuristics which are not very reliable. Dupe of  bug 4995 .

Loading...