[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How shall I report a bug in the .deb packaging itself?



On Mon, 2015-12-21 at 17:03 +0100, Julian Andres Klode wrote:
On Mon, Dec 21, 2015 at 04:57:39PM +0100, Abou Al Montacir wrote:
Hi Julian On Mon, 2015-12-21 at 16:13 +0100, Julian Andres Klode wrote:
I also wrote I am thinking about adding some kind of apt revert command that allows you to revert entries from apt's history.log, which would allow you to undo install commands.
That will be really a great feature. I was always upset that apt(itude) does not have this feature. I was even thinking about a feature that allows you to recover your system at a certain date based on snapshots. The last time I was missing this is today. I updated ssh and suddenly I could not access anymore my github account due to my key was rejected. I would loved to aptitude revert instead of doing this manually.
In a lot of cases it won't work though. For example, reverting an upgrade is formally unsupported (so you'd need to answer yes to some warnings), and in any case, the old versions and packages still need to be available in your sources. Actually, anything where something other than an install happened (whether remove or upgrade) is a bit flaky.
I was more thinking about sid/testing users that stable users. So these people should be experimented enough to be able to deal with warnings.

Normally one can always access snapshots to recover a given version of any package so why should one have to have the old packages?
A better option is to use snapshotting on the file system.
Yes was thinking about putting / in a git repository and playing with .gitignore, but maybe there are better solutions.
-- 
Cheers,
Abou Al Montacir

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: