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#20786 - Backup older packages and better clean mechanism

Attached to Project: Pacman
Opened by Shiva Wu (shivawu) - Thursday, 09 September 2010, 05:59 GMT
Last edited by Allan McRae (Allan) - Sunday, 22 April 2012, 11:17 GMT
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 3.4.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Summary and Info:

In my opinion, a "backup installed packages" option should be added when upgrading the system or packages. Because the newer could be incompatible with existing packages, and the most repository don't have the previous versions. Since we have the file list of the current package, pacman can regenerate a old package in case for rolling back.

Furthermore, a more specific cleanup mechanism is appreciated. We can, for example, clean the packages older than 7-days, or clean the old packages from community...
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 22 April 2012, 11:17 GMT
Reason for closing:  None
Additional comments about closing:  bacman and paccache should cover most use cases here
Comment by Xavier (shining) - Thursday, 09 September 2010, 06:34 GMT
You already have bacman at your disposal.
Feel free to implement the rest.
Comment by Allan McRae (Allan) - Thursday, 09 September 2010, 09:00 GMT
Or do not clear important packages from your cache.
Comment by Shiva Wu (shivawu) - Thursday, 09 September 2010, 09:15 GMT
This is an idea too. But it's hard to exclude the important packages when there are too many packages in the cache. pacman should provide such a tool to control it, I suppose.

Comment by Dan McGee (toofishes) - Thursday, 09 September 2010, 11:20 GMT
You should write such a tool because the current maintainers are not interested in this, as you can see. :)

I'll leave this open but don't expect any progress from us on it.
Comment by jon (emphire) - Friday, 11 February 2011, 22:35 GMT
In the meantime, you might want to checkout a tool from AUR such as: http://aur.archlinux.org/packages.php?ID=37572
Comment by Karol Błażewicz (karol) - Thursday, 11 August 2011, 22:48 GMT
I think it's related to / duplicate of https://bugs.archlinux.org/task/11913
Comment by Dave Reisner (falconindy) - Saturday, 22 October 2011, 17:46 GMT
I think paccache and bacman satisfy this... paccache doesn't directly implement repo filtering, but that's because packages (as files) have no concept of belonging to a repo. It's flexible enough that you could wrap paccache and do this, though.

Loading...