Re: Putting apt-listchanges and dpkg output in mail sent by unattended-upgrades

From	David Wright <deblis@lionunicorn.co.uk>
Newsgroups	linux.debian.user
Subject	Re: Putting apt-listchanges and dpkg output in mail sent by unattended-upgrades
Date	2015-10-15 17:10 +0200
Message-ID	<qjSkh-1BA-15@gated-at.bofh.it> (permalink)
References	(1 earlier) <qit4C-7d2-7@gated-at.bofh.it> <qiPou-64e-17@gated-at.bofh.it> <qj8r8-ok-33@gated-at.bofh.it> <qjbyG-4SC-21@gated-at.bofh.it> <qjJAl-5vp-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Quoting moxalt (moxalt@riseup.net):
> On Tue, 13 Oct 2015 19:22:55 +0200, Ondřej Grover <ondrej.grover@gmail.com>
> wrote:

> > It wouldn't be an overkill if there was a simple way to manage a local
> > repository and packages with custom modifications. I have looked around and
> > it didn't seem that straight-forward. Is there some helper tool perhaps?
> 
> Even if you were able to manage a local repository of some sort, the only way
> you would be able to prevent your custom .debs from being overwritten is by
> assigning them really high version numbers so that they are never overwritten
> by updates. Of course, you wouldn't be able to get official Debian updates that
> way, which could cause problems later. The same is true if you just made a
> modified standalone .deb.

You can of course leave the version number alone (to indicate the base
version of your customisations) and just use a higher epoch value on
your package to protect it from being overwritten. This would also
allow you to set up an alert from, say, cron if your version number
(without epoch) didn't match the (new) version available from Debian,
so you would know it was about time to check/rerun your customisations.

> You have two options- either make a custom package once and for all (but never
> get updates) or edit it locally and backup your edits so that you can restore
> them after updates. I would take the second option. It's not as if
> apt-listchanges and dpkg get updated every day- and when they do it's just a
> simple copy-paste job from your backed up script.

Cheers,
David.

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Putting apt-listchanges and dpkg output in mail sent by unattended-upgrades Ondřej Grover <ondrej.grover@gmail.com> - 2015-10-11 10:40 +0200
  Re: Putting apt-listchanges and dpkg output in mail sent by  unattended-upgrades moxalt <moxalt@riseup.net> - 2015-10-11 20:00 +0200
    Re: Putting apt-listchanges and dpkg output in mail sent by unattended-upgrades Ondřej Grover <ondrej.grover@gmail.com> - 2015-10-12 19:50 +0200
      Re: Putting apt-listchanges and dpkg output in mail sent by  unattended-upgrades moxalt <moxalt@riseup.net> - 2015-10-13 16:10 +0200
        Re: Putting apt-listchanges and dpkg output in mail sent by unattended-upgrades Ondřej Grover <ondrej.grover@gmail.com> - 2015-10-13 19:30 +0200
          Re: Putting apt-listchanges and dpkg output in mail sent by  unattended-upgrades moxalt <moxalt@riseup.net> - 2015-10-15 07:50 +0200
            Re: Putting apt-listchanges and dpkg output in mail sent by  unattended-upgrades David Wright <deblis@lionunicorn.co.uk> - 2015-10-15 17:10 +0200

csiph-web