Re: [DNG] etckeeper
Hi Hendrik, Hendrik Boom writes: > On Mon, Oct 18, 2021 at 06:52:05PM +0900, Olaf Meeuwissen via Dng wrote: >> Hi Steve, >> >> Steve Litt writes: >> >> > After that, take a backup of the new system including /etc and >> > $HOME, then restore *strategic* config files from /etc/ and ~ and >> > ~/.config. By strategic, I mean configs that you hand-crafted. >> > Sometimes it's better to copy your hand-crafting into current >> > package-installed config files. I find this especially true of Dovecot. >> >> I keep track of /etc with etckeeper which puts that directory under git >> version control. That means I can always track back changes to package >> updates or me mucking around there and see exactly what changed. That >> can be very helpful if an `apt upgrade` broke stuff, more so because I >> track "testing" ;-) > > Sounds like etckeeper should be the first thing installed during > Devuan installation, before any packages at all are configured, so as > to track changed that are made during installation. I don't know if tracking all the nitty-gritty package changes *during* installation makes a lot of sense, but I quite habitually install etckeeper as the first package *after* the installation. The first commit (made during its install) then records the system's initial configuration (but not the list of packages that are installed; I add that manually afterwards via `etckeeper vcs commit --amend`). Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] etckeeper
On Mon, Oct 18, 2021 at 06:52:05PM +0900, Olaf Meeuwissen via Dng wrote: > Hi Steve, > > Steve Litt writes: > > > After that, take a backup of the new system including /etc and > > $HOME, then restore *strategic* config files from /etc/ and ~ and > > ~/.config. By strategic, I mean configs that you hand-crafted. > > Sometimes it's better to copy your hand-crafting into current > > package-installed config files. I find this especially true of Dovecot. > > I keep track of /etc with etckeeper which puts that directory under git > version control. That means I can always track back changes to package > updates or me mucking around there and see exactly what changed. That > can be very helpful if an `apt upgrade` broke stuff, more so because I > track "testing" ;-) Sounds like etckeeper should be the first thing installed during Devuan installation, before any packages at all are configured, so as to track changed that are made during installation. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] etckeeper: was: Er, Not that way ? .Re: Announcing Devuan 4.0: Chimaera!
On Sun, Oct 24, 2021 at 1:01 AM Olaf Meeuwissen wrote: > > o1bigtenor writes: > > > On Thu, Oct 21, 2021 at 6:47 AM Olaf Meeuwissen via Dng < > dng@lists.dyne.org> > > wrote: > > > >> [... illustrating etckeeper commit messages ...] > > > > Mr Olaf > > (and the rest of devuan land) > > > > I found apt-cacher-ng to be a useful tool in tracking updates and in > > minimizing my bandwidth. > > > > Would apt-cacher-ng work with etckeeper? > > Suggestions please. > > The etckeeper utility hooks into a few select apt-get commands, those > that upgrade, install and remove packages on your system. It has > nothing to do with updating whatever local APT repository caches you > use. > > That is to say, the two are unrelated. > > You can continue using apt-cacher-ng to maintain your local APT > repository caches and keep your individual systems up-to-date with > apt-get (apt, aptitude, synaptic, etc.) as you do now. Adding etckeeper > to the mix would only create a historical record of what packages you > have upgraded, installed and/or removed on your system. > > > Thank you for your information Using apt-cacher-ng and etckeeper sounds like something useful for here. Appreciate your sharing! Regards ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] etckeeper: was: Er, Not that way ? .Re: Announcing Devuan 4.0: Chimaera!
o1bigtenor writes: > On Thu, Oct 21, 2021 at 6:47 AM Olaf Meeuwissen via Dng > wrote: > >> [... illustrating etckeeper commit messages ...] > > Mr Olaf > (and the rest of devuan land) > > I found apt-cacher-ng to be a useful tool in tracking updates and in > minimizing my bandwidth. > > Would apt-cacher-ng work with etckeeper? > Suggestions please. The etckeeper utility hooks into a few select apt-get commands, those that upgrade, install and remove packages on your system. It has nothing to do with updating whatever local APT repository caches you use. That is to say, the two are unrelated. You can continue using apt-cacher-ng to maintain your local APT repository caches and keep your individual systems up-to-date with apt-get (apt, aptitude, synaptic, etc.) as you do now. Adding etckeeper to the mix would only create a historical record of what packages you have upgraded, installed and/or removed on your system. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] etckeeper: was: Er, Not that way ? .Re: Announcing Devuan 4.0: Chimaera!
Hi wirelessduck,
wirelessd...@gmail.com writes:
>> On 21 Oct 2021, at 22:47, Olaf Meeuwissen wrote:
>>
>> Hi wirelessduck,
>>
>> wirelessduck--- via Dng writes:
>>
> On 20 Oct 2021, at 20:45, Olaf Meeuwissen via Dng
> wrote:
I really looked into snapshotting but the etckeeper commit messages also
list which packages changed, like so (after I "beautified" the logging a
bit to suit my taste and needs)
commit dd9602a525e590f24ec19904248938e6ab76e999 (HEAD -> master)
Author: olaf
Date: Mon Oct 11 21:48:25 2021 +0900
Committing changes in /etc after APT run
Package changes:
- debconf 1.5.71 all
+ debconf 1.5.71+deb10u1 all
- libgssapi-krb5-2 1.17-3+deb10u2 amd64
+ libgssapi-krb5-2 1.17-3+deb10u3 amd64
- libk5crypto3 1.17-3+deb10u2 amd64
+ libk5crypto3 1.17-3+deb10u3 amd64
- libkrb5-3 1.17-3+deb10u2 amd64
+ libkrb5-3 1.17-3+deb10u3 amd64
- libkrb5support0 1.17-3+deb10u2 amd64
+ libkrb5support0 1.17-3+deb10u3 amd64
- libmariadb3 1:10.3.29-0+deb10u1 amd64
+ libmariadb3 1:10.3.31-0+deb10u1 amd64
which gives me a chance to pinpoint any culprits and submit bug reports
if necessary with detailed info on the changed packages.
>>>
>>> Is this formatting configured in etckeeper or gitconfig? I would like
>>> to try and replicate. It looks very useful.
>>
>> TL;DR: in etckeeper.
>>
>> The etckeeper utility does a good job of collecting the package changes
>> out-of-the-box but the exact output is slightly different from what I
>> included above. The out-of-the-box behaviour includes the output of
>>
>> diff -U0 $before $after | egrep '^[-+]'
>>
>> where $before and $after are "files" with the output of
>>
>> dpkg-query -W -f '${Status}\t${Package} ${Version}\n' | \
>> egrep '(ok installed|ok config-files)' | cut -f2,3
>>
>> I've tweaked that a bit to insert a space after the '^[-+]' and run the
>> diff output through `sort -k2` so I get the before and after package
>> info closer together. I've also made a few very minor changes to start
>> the message with a capital and capitalized APT.
>>
>> Without my changes, the above would have looked something like
>>
>> commit dd9602a525e590f24ec19904248938e6ab76e999 (HEAD -> master)
>> Author: olaf
>> Date: Mon Oct 11 21:48:25 2021 +0900
>>
>> committing changes in /etc after apt run
>>
>> Package changes:
>> -debconf 1.5.71 all
>> +debconf 1.5.71+deb10u1 all
>> -libgssapi-krb5-2 1.17-3+deb10u2 amd64
>> +libgssapi-krb5-2 1.17-3+deb10u3 amd64
>> -libk5crypto3 1.17-3+deb10u2 amd64
>> -libkrb5-3 1.17-3+deb10u2 amd64
>> -libkrb5support0 1.17-3+deb10u2 amd64
>> +libk5crypto3 1.17-3+deb10u3 amd64
>> +libkrb5-3 1.17-3+deb10u3 amd64
>> +libkrb5support0 1.17-3+deb10u3 amd64
>> -libmariadb3 1:10.3.29-0+deb10u1 amd64
>> +libmariadb3 1:10.3.31-0+deb10u1 amd64
>>
>> BTW, the version in chimaera (and later) also includes a section that
>> lists the packages with configuration changes and includes the command
>> line invocation that triggered the changes.
>>
>> Oh, I've also made a few changes to record package changes if nothing
>> below /etc has changed.
>>
>> Hope this helps,
>
> Many thanks.
>
> I think the piping to sort alone is good enough that it should be
> implemented upstream. I wonder if there is any special ordering to the
> original non-sorted output as I can’t now see why you would want it
> unsorted?
The piping to sort relies on inserting a space. Without the space,
you'd be sorting on package version numbers, doh!, but yes, trying to
get this included upstream might be a good idea.
# `dpkg-query -W` already sorts on package name. It's just that diff
# only looks at what it gets. The `sort` I added is after the egrep.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
Support Free Softwarehttps://my.fsf.org/donate
Join the Free Software Foundation https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] etckeeper: was: Er, Not that way ? .Re: Announcing Devuan 4.0: Chimaera!
On Thu, Oct 21, 2021 at 6:47 AM Olaf Meeuwissen via Dng
wrote:
> Hi wirelessduck,
>
> wirelessduck--- via Dng writes:
>
> >> On 20 Oct 2021, at 20:45, Olaf Meeuwissen via Dng
> wrote:
> >>
> >> I really looked into snapshotting but the etckeeper commit messages also
> >> list which packages changed, like so (after I "beautified" the logging a
> >> bit to suit my taste and needs)
> >>
> >> commit dd9602a525e590f24ec19904248938e6ab76e999 (HEAD -> master)
> >> Author: olaf
> >> Date: Mon Oct 11 21:48:25 2021 +0900
> >>
> >> Committing changes in /etc after APT run
> >>
> >> Package changes:
> >> - debconf 1.5.71 all
> >> + debconf 1.5.71+deb10u1 all
> >> - libgssapi-krb5-2 1.17-3+deb10u2 amd64
> >> + libgssapi-krb5-2 1.17-3+deb10u3 amd64
> >> - libk5crypto3 1.17-3+deb10u2 amd64
> >> + libk5crypto3 1.17-3+deb10u3 amd64
> >> - libkrb5-3 1.17-3+deb10u2 amd64
> >> + libkrb5-3 1.17-3+deb10u3 amd64
> >> - libkrb5support0 1.17-3+deb10u2 amd64
> >> + libkrb5support0 1.17-3+deb10u3 amd64
> >> - libmariadb3 1:10.3.29-0+deb10u1 amd64
> >> + libmariadb3 1:10.3.31-0+deb10u1 amd64
> >>
> >> which gives me a chance to pinpoint any culprits and submit bug reports
> >> if necessary with detailed info on the changed packages.
> >
> > Is this formatting configured in etckeeper or gitconfig? I would like
> > to try and replicate. It looks very useful.
>
> TL;DR: in etckeeper.
>
> The etckeeper utility does a good job of collecting the package changes
> out-of-the-box but the exact output is slightly different from what I
> included above. The out-of-the-box behaviour includes the output of
>
> diff -U0 $before $after | egrep '^[-+]'
>
> where $before and $after are "files" with the output of
>
> dpkg-query -W -f '${Status}\t${Package} ${Version}\n' | \
> egrep '(ok installed|ok config-files)' | cut -f2,3
>
> I've tweaked that a bit to insert a space after the '^[-+]' and run the
> diff output through `sort -k2` so I get the before and after package
> info closer together. I've also made a few very minor changes to start
> the message with a capital and capitalized APT.
>
> Without my changes, the above would have looked something like
>
> commit dd9602a525e590f24ec19904248938e6ab76e999 (HEAD -> master)
> Author: olaf
> Date: Mon Oct 11 21:48:25 2021 +0900
>
> committing changes in /etc after apt run
>
> Package changes:
> -debconf 1.5.71 all
> +debconf 1.5.71+deb10u1 all
> -libgssapi-krb5-2 1.17-3+deb10u2 amd64
> +libgssapi-krb5-2 1.17-3+deb10u3 amd64
> -libk5crypto3 1.17-3+deb10u2 amd64
> -libkrb5-3 1.17-3+deb10u2 amd64
> -libkrb5support0 1.17-3+deb10u2 amd64
> +libk5crypto3 1.17-3+deb10u3 amd64
> +libkrb5-3 1.17-3+deb10u3 amd64
> +libkrb5support0 1.17-3+deb10u3 amd64
> -libmariadb3 1:10.3.29-0+deb10u1 amd64
> +libmariadb3 1:10.3.31-0+deb10u1 amd64
>
> BTW, the version in chimaera (and later) also includes a section that
> lists the packages with configuration changes and includes the command
> line invocation that triggered the changes.
>
> Oh, I've also made a few changes to record package changes if nothing
> below /etc has changed.
>
> Hope this helps,
>
Mr Olaf
(and the rest of devuan land)
I found apt-cacher-ng to be a useful tool in tracking updates and in
minimizing my bandwidth.
Would apt-cacher-ng work with etckeeper?
Suggestions please.
TIA
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] etckeeper: was: Er, Not that way ? .Re: Announcing Devuan 4.0: Chimaera!
> On 21 Oct 2021, at 22:47, Olaf Meeuwissen wrote:
>
> Hi wirelessduck,
>
> wirelessduck--- via Dng writes:
>
On 20 Oct 2021, at 20:45, Olaf Meeuwissen via Dng
wrote:
>>>
>>> I really looked into snapshotting but the etckeeper commit messages also
>>> list which packages changed, like so (after I "beautified" the logging a
>>> bit to suit my taste and needs)
>>>
>>> commit dd9602a525e590f24ec19904248938e6ab76e999 (HEAD -> master)
>>> Author: olaf
>>> Date: Mon Oct 11 21:48:25 2021 +0900
>>>
>>> Committing changes in /etc after APT run
>>>
>>> Package changes:
>>> - debconf 1.5.71 all
>>> + debconf 1.5.71+deb10u1 all
>>> - libgssapi-krb5-2 1.17-3+deb10u2 amd64
>>> + libgssapi-krb5-2 1.17-3+deb10u3 amd64
>>> - libk5crypto3 1.17-3+deb10u2 amd64
>>> + libk5crypto3 1.17-3+deb10u3 amd64
>>> - libkrb5-3 1.17-3+deb10u2 amd64
>>> + libkrb5-3 1.17-3+deb10u3 amd64
>>> - libkrb5support0 1.17-3+deb10u2 amd64
>>> + libkrb5support0 1.17-3+deb10u3 amd64
>>> - libmariadb3 1:10.3.29-0+deb10u1 amd64
>>> + libmariadb3 1:10.3.31-0+deb10u1 amd64
>>>
>>> which gives me a chance to pinpoint any culprits and submit bug reports
>>> if necessary with detailed info on the changed packages.
>>
>> Is this formatting configured in etckeeper or gitconfig? I would like
>> to try and replicate. It looks very useful.
>
> TL;DR: in etckeeper.
>
> The etckeeper utility does a good job of collecting the package changes
> out-of-the-box but the exact output is slightly different from what I
> included above. The out-of-the-box behaviour includes the output of
>
> diff -U0 $before $after | egrep '^[-+]'
>
> where $before and $after are "files" with the output of
>
> dpkg-query -W -f '${Status}\t${Package} ${Version}\n' | \
> egrep '(ok installed|ok config-files)' | cut -f2,3
>
> I've tweaked that a bit to insert a space after the '^[-+]' and run the
> diff output through `sort -k2` so I get the before and after package
> info closer together. I've also made a few very minor changes to start
> the message with a capital and capitalized APT.
>
> Without my changes, the above would have looked something like
>
> commit dd9602a525e590f24ec19904248938e6ab76e999 (HEAD -> master)
> Author: olaf
> Date: Mon Oct 11 21:48:25 2021 +0900
>
> committing changes in /etc after apt run
>
> Package changes:
> -debconf 1.5.71 all
> +debconf 1.5.71+deb10u1 all
> -libgssapi-krb5-2 1.17-3+deb10u2 amd64
> +libgssapi-krb5-2 1.17-3+deb10u3 amd64
> -libk5crypto3 1.17-3+deb10u2 amd64
> -libkrb5-3 1.17-3+deb10u2 amd64
> -libkrb5support0 1.17-3+deb10u2 amd64
> +libk5crypto3 1.17-3+deb10u3 amd64
> +libkrb5-3 1.17-3+deb10u3 amd64
> +libkrb5support0 1.17-3+deb10u3 amd64
> -libmariadb3 1:10.3.29-0+deb10u1 amd64
> +libmariadb3 1:10.3.31-0+deb10u1 amd64
>
> BTW, the version in chimaera (and later) also includes a section that
> lists the packages with configuration changes and includes the command
> line invocation that triggered the changes.
>
> Oh, I've also made a few changes to record package changes if nothing
> below /etc has changed.
>
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
> Support Free Softwarehttps://my.fsf.org/donate
> Join the Free Software Foundation https://my.fsf.org/join
Many thanks.
I think the piping to sort alone is good enough that it should be implemented
upstream. I wonder if there is any special ordering to the original non-sorted
output as I can’t now see why you would want it unsorted?
--
Tom
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] etckeeper: was: Er, Not that way ? .Re: Announcing Devuan 4.0: Chimaera!
Hi wirelessduck,
wirelessduck--- via Dng writes:
>> On 20 Oct 2021, at 20:45, Olaf Meeuwissen via Dng wrote:
>>
>> I really looked into snapshotting but the etckeeper commit messages also
>> list which packages changed, like so (after I "beautified" the logging a
>> bit to suit my taste and needs)
>>
>> commit dd9602a525e590f24ec19904248938e6ab76e999 (HEAD -> master)
>> Author: olaf
>> Date: Mon Oct 11 21:48:25 2021 +0900
>>
>> Committing changes in /etc after APT run
>>
>> Package changes:
>> - debconf 1.5.71 all
>> + debconf 1.5.71+deb10u1 all
>> - libgssapi-krb5-2 1.17-3+deb10u2 amd64
>> + libgssapi-krb5-2 1.17-3+deb10u3 amd64
>> - libk5crypto3 1.17-3+deb10u2 amd64
>> + libk5crypto3 1.17-3+deb10u3 amd64
>> - libkrb5-3 1.17-3+deb10u2 amd64
>> + libkrb5-3 1.17-3+deb10u3 amd64
>> - libkrb5support0 1.17-3+deb10u2 amd64
>> + libkrb5support0 1.17-3+deb10u3 amd64
>> - libmariadb3 1:10.3.29-0+deb10u1 amd64
>> + libmariadb3 1:10.3.31-0+deb10u1 amd64
>>
>> which gives me a chance to pinpoint any culprits and submit bug reports
>> if necessary with detailed info on the changed packages.
>
> Is this formatting configured in etckeeper or gitconfig? I would like
> to try and replicate. It looks very useful.
TL;DR: in etckeeper.
The etckeeper utility does a good job of collecting the package changes
out-of-the-box but the exact output is slightly different from what I
included above. The out-of-the-box behaviour includes the output of
diff -U0 $before $after | egrep '^[-+]'
where $before and $after are "files" with the output of
dpkg-query -W -f '${Status}\t${Package} ${Version}\n' | \
egrep '(ok installed|ok config-files)' | cut -f2,3
I've tweaked that a bit to insert a space after the '^[-+]' and run the
diff output through `sort -k2` so I get the before and after package
info closer together. I've also made a few very minor changes to start
the message with a capital and capitalized APT.
Without my changes, the above would have looked something like
commit dd9602a525e590f24ec19904248938e6ab76e999 (HEAD -> master)
Author: olaf
Date: Mon Oct 11 21:48:25 2021 +0900
committing changes in /etc after apt run
Package changes:
-debconf 1.5.71 all
+debconf 1.5.71+deb10u1 all
-libgssapi-krb5-2 1.17-3+deb10u2 amd64
+libgssapi-krb5-2 1.17-3+deb10u3 amd64
-libk5crypto3 1.17-3+deb10u2 amd64
-libkrb5-3 1.17-3+deb10u2 amd64
-libkrb5support0 1.17-3+deb10u2 amd64
+libk5crypto3 1.17-3+deb10u3 amd64
+libkrb5-3 1.17-3+deb10u3 amd64
+libkrb5support0 1.17-3+deb10u3 amd64
-libmariadb3 1:10.3.29-0+deb10u1 amd64
+libmariadb3 1:10.3.31-0+deb10u1 amd64
BTW, the version in chimaera (and later) also includes a section that
lists the packages with configuration changes and includes the command
line invocation that triggered the changes.
Oh, I've also made a few changes to record package changes if nothing
below /etc has changed.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
Support Free Softwarehttps://my.fsf.org/donate
Join the Free Software Foundation https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] etckeeper: was: Er, Not that way ? .Re: Announcing Devuan 4.0: Chimaera!
> On 20 Oct 2021, at 20:45, Olaf Meeuwissen via Dng wrote: > > I really looked into snapshotting but the etckeeper commit messages also > list which packages changed, like so (after I "beautified" the logging a > bit to suit my taste and needs) > > commit dd9602a525e590f24ec19904248938e6ab76e999 (HEAD -> master) > Author: olaf > Date: Mon Oct 11 21:48:25 2021 +0900 > > Committing changes in /etc after APT run > > Package changes: > - debconf 1.5.71 all > + debconf 1.5.71+deb10u1 all > - libgssapi-krb5-2 1.17-3+deb10u2 amd64 > + libgssapi-krb5-2 1.17-3+deb10u3 amd64 > - libk5crypto3 1.17-3+deb10u2 amd64 > + libk5crypto3 1.17-3+deb10u3 amd64 > - libkrb5-3 1.17-3+deb10u2 amd64 > + libkrb5-3 1.17-3+deb10u3 amd64 > - libkrb5support0 1.17-3+deb10u2 amd64 > + libkrb5support0 1.17-3+deb10u3 amd64 > - libmariadb3 1:10.3.29-0+deb10u1 amd64 > + libmariadb3 1:10.3.31-0+deb10u1 amd64 > > which gives me a chance to pinpoint any culprits and submit bug reports > if necessary with detailed info on the changed packages. Is this formatting configured in etckeeper or gitconfig? I would like to try and replicate. It looks very useful. Thanks ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] etckeeper: was: Er, Not that way ? .Re: Announcing Devuan 4.0: Chimaera!
Hi Curtis, Curtis Maurand via Dng writes: > On 10/18/21 4:36 PM, Steve Litt wrote: >> Olaf Meeuwissen said on Mon, 18 Oct 2021 18:52:05 +0900 >> >> >>> I keep track of /etc with etckeeper which puts that directory under git >>> version control. That means I can always track back changes to package >>> updates or me mucking around there and see exactly what changed. That >>> can be very helpful if an `apt upgrade` broke stuff, more so because I >>> track "testing" ;-) >> Nice!!! > I run on a BTRFS file system and /etc is in it's on sub volume. I just > take a snapshot of it. restoration is as easy as overwriting a file or > folder from the snapshot. I store the snapshots both locally and > externally. Works great. I handle /var/lib/mysql that way, too. I really looked into snapshotting but the etckeeper commit messages also list which packages changed, like so (after I "beautified" the logging a bit to suit my taste and needs) commit dd9602a525e590f24ec19904248938e6ab76e999 (HEAD -> master) Author: olaf Date: Mon Oct 11 21:48:25 2021 +0900 Committing changes in /etc after APT run Package changes: - debconf 1.5.71 all + debconf 1.5.71+deb10u1 all - libgssapi-krb5-2 1.17-3+deb10u2 amd64 + libgssapi-krb5-2 1.17-3+deb10u3 amd64 - libk5crypto3 1.17-3+deb10u2 amd64 + libk5crypto3 1.17-3+deb10u3 amd64 - libkrb5-3 1.17-3+deb10u2 amd64 + libkrb5-3 1.17-3+deb10u3 amd64 - libkrb5support0 1.17-3+deb10u2 amd64 + libkrb5support0 1.17-3+deb10u3 amd64 - libmariadb3 1:10.3.29-0+deb10u1 amd64 + libmariadb3 1:10.3.31-0+deb10u1 amd64 which gives me a chance to pinpoint any culprits and submit bug reports if necessary with detailed info on the changed packages. When tracking "testing" and doing regular, say weekly or even more frequent, updates (maybe even via unattended-upgrades), you don't always notice issues rightaway. Being able to track things down to the upgrade that introduced the issue retroactively in this kind of detail helps a lot. The commit itself has the byte-by-byte changes that may point to the root cause of the issue and the commit logs also let me check very easily if I modified related files myself for some reason. Yes, I know that /var/log/apt/ has some of this info but I find my commit messages a bit easier to parse. Besides, they won't be rotated into oblivion by logrotate ;-) Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] etckeeper: was: Er, Not that way ? .Re: Announcing Devuan 4.0: Chimaera!
On 10/18/21 4:36 PM, Steve Litt wrote: Olaf Meeuwissen said on Mon, 18 Oct 2021 18:52:05 +0900 I keep track of /etc with etckeeper which puts that directory under git version control. That means I can always track back changes to package updates or me mucking around there and see exactly what changed. That can be very helpful if an `apt upgrade` broke stuff, more so because I track "testing" ;-) Nice!!! I run on a BTRFS file system and /etc is in it's on sub volume. I just take a snapshot of it. restoration is as easy as overwriting a file or folder from the snapshot. I store the snapshots both locally and externally. Works great. I handle /var/lib/mysql that way, too. Cheers, Curtis SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] etckeeper: was: Er, Not that way ? .Re: Announcing Devuan 4.0: Chimaera!
Olaf Meeuwissen said on Mon, 18 Oct 2021 18:52:05 +0900 >I keep track of /etc with etckeeper which puts that directory under git >version control. That means I can always track back changes to package >updates or me mucking around there and see exactly what changed. That >can be very helpful if an `apt upgrade` broke stuff, more so because I >track "testing" ;-) Nice!!! SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
