...actually, would a mechanism like beneath implemented natively in pacman be worth a feature request?
cheers! mar77i
---------- Forwarded message ---------- From: Martin Kühne mysatyre@gmail.com Date: Tue, Sep 27, 2016 at 2:46 PM Subject: Re: [arch-general] Removing infinality To: General Discussion about Arch Linux arch-general@archlinux.org
Just a thought. If you find the excerpt in the pacman logs where you did the transaction got you into this mess, you might be able to reverse just that without risking too much for the current install and save you a complete reinstall. Ignoring dependencies is then not so bad, because you then just install the packages again that were uninstalled to get you into this.
cheers! mar77i
On 28/09/16 17:14, Martin Kühne wrote:
...actually, would a mechanism like beneath implemented natively in pacman be worth a feature request?
cheers! mar77i
I have no context, so I'll assume we can already do that and it is user error.
Allan
---------- Forwarded message ---------- From: Martin Kühne mysatyre@gmail.com Date: Tue, Sep 27, 2016 at 2:46 PM Subject: Re: [arch-general] Removing infinality To: General Discussion about Arch Linux arch-general@archlinux.org
Just a thought. If you find the excerpt in the pacman logs where you did the transaction got you into this mess, you might be able to reverse just that without risking too much for the current install and save you a complete reinstall. Ignoring dependencies is then not so bad, because you then just install the packages again that were uninstalled to get you into this.
cheers! mar77i
Having a mechanism to choose from past transactions and undoing them properly has to be done by hand right now and tends to be tedious and error-prone. There might be ways to mitigate that by parsing the logs and offering actions based on such data, assuming that the logs stay parseable as they are. Would that be considered eg. as a contrib script?
cheers! mar77i
On 28/09/16 19:03, Martin Kühne wrote:
Having a mechanism to choose from past transactions and undoing them properly has to be done by hand right now and tends to be tedious and error-prone. There might be ways to mitigate that by parsing the logs and offering actions based on such data, assuming that the logs stay parseable as they are. Would that be considered eg. as a contrib script?
I'm not going to say no... but I am not keen on contrib existing, so expanding it is not a priority.
A
pacman-dev@lists.archlinux.org