Re: history transparency
On 15/03/13 02:19, Dmitrijs Ledkovs wrote:
On 15 March 2013 00:56, Philip Ashmore<contact@philipashmore.com> wrote:
On 09/02/12 08:58, Paul Wise wrote:
On Thu, Feb 9, 2012 at 4:45 PM, Philip Ashmore wrote:
I think Debian needs a way to be able to pick a point in history and
obtain
at least the versions + patches of all the source packages that would
have
been installed / available to reproduce the Debian system running on the
users machine at the time they reported the bug.
With more and more source packages becoming available under publicly
accessible version control, what needs to change in Debian to make this
possible?
Nothing, it already exists:
http://snapshot.debian.org/archive/debian/20091229T215155Z/
How do I work out which snapshot I have installed now?
I download from Sid.
Take the checksum of Packages from /var/lib/apt/lists and find a
matching one on snapshots.
Is there a web interface for that, or a script that can do this?
It will be close, but not everything.
A better way is to use apt-clone which will generate a more
comprehensive state tarball.
Is there a micro-version file that stores this information or is it a time
stamp on some file?
How would that help at all? Given that it will never know the set of
packages you have installed, or obsolete packages not-removed,
modified conffiles etc.
I get you, but I'm talking from a pbuilder or similar perspective.
If I run into a problem and a week later it's gone it would be nice to
be able to tell what packages changed.
Backing up /var/lib/apt/lists would do it but then you would start
backing it up all over the place, that's why a micro-version number
would be better, just increment it every time new packages appear in
snapshots.
It it were in its own file or available from lsb_release or similar then
even better.
Regards,
Dmitrijs.
Cheers.
Reply to: