Bug#684707: Acknowledgement (unattended-upgrades: Add a distro_release macro)

2017-09-20 Thread Balint Reczey
Control: fixed -1 0.80

Hi Russel,

On Wed, 15 Aug 2012 11:19:37 +1000 Russell Stuart
 wrote:
> On Tue, 2012-08-14 at 15:10 +0200, Michael Vogt wrote:
> > I removed this example for now and added codename based matching in
> > python-apt,unattended-upgrades in the debian-experimental bzr branch.
>
> Wow! Thanks. Looks like you've addressed all my wishes.

This seems to be fixed long time ago.

Cheers,
Balint



Bug#684707: Acknowledgement (unattended-upgrades: Add a distro_release macro)

2012-08-14 Thread Michael Vogt
On Mon, Aug 13, 2012 at 08:19:21PM +1000, Russell Stuart wrote:
 Oh, and I should have added, the current documentation in
 50unattended-upgrades says this:
 
 // Codename based matching:
 // This will follow the migration of a release through different
 // archives (e.g. from testing to stable and later oldstable).
 //  o=Debian,n=squeeze;
 //  o=Debian,n=squeeze-updates;
 //  o=Debian,n=squeeze-proposed-updates;
 //  o=Debian,n=squeeze,l=Debian-Security;
 
 I think the idea is n=squeeze is supposed to match the Codename
 attribute in the Release file.  It would be great if it worked, but I
 don't see how it can because the python apt package doesn't include an
 element describing the codename in
 apt.Cache()[package].candidate.origins, and neither can I see any code
 in unattended-upgrades that would match it.
 
 It may looks like it works because unattended-upgrade doesn't report an
 error if you give it a keyword it doesn't understand (like n or
 codename).  A side effect of this is if you included a line like
 true=true (or any other unknown keyword) every package will always
 match.

Uh, thanks indeed. I added code now that will raise a error if it
finds unknown matcher entry. And I will check out what it takes to add
the n matcher.

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#684707: Acknowledgement (unattended-upgrades: Add a distro_release macro)

2012-08-14 Thread Michael Vogt
On Mon, Aug 13, 2012 at 08:19:21PM +1000, Russell Stuart wrote:
 Oh, and I should have added, the current documentation in
 50unattended-upgrades says this:
 
 // Codename based matching:
 // This will follow the migration of a release through different
 // archives (e.g. from testing to stable and later oldstable).
 //  o=Debian,n=squeeze;
 //  o=Debian,n=squeeze-updates;
 //  o=Debian,n=squeeze-proposed-updates;
 //  o=Debian,n=squeeze,l=Debian-Security;
 
 I think the idea is n=squeeze is supposed to match the Codename
 attribute in the Release file.  It would be great if it worked, but I
 don't see how it can because the python apt package doesn't include an
 element describing the codename in
 apt.Cache()[package].candidate.origins, and neither can I see any code
 in unattended-upgrades that would match it.
[..]

I removed this example for now and added codename based matching in
python-apt,unattended-upgrades in the debian-experimental bzr branch. 

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#684707: Acknowledgement (unattended-upgrades: Add a distro_release macro)

2012-08-14 Thread Russell Stuart
On Tue, 2012-08-14 at 15:10 +0200, Michael Vogt wrote:
 I removed this example for now and added codename based matching in
 python-apt,unattended-upgrades in the debian-experimental bzr branch. 

Wow!  Thanks.  Looks like you've addressed all my wishes.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#684707: Acknowledgement (unattended-upgrades: Add a distro_release macro)

2012-08-13 Thread Russell Stuart
Oh, and I should have added, the current documentation in
50unattended-upgrades says this:

// Codename based matching:
// This will follow the migration of a release through different
// archives (e.g. from testing to stable and later oldstable).
//  o=Debian,n=squeeze;
//  o=Debian,n=squeeze-updates;
//  o=Debian,n=squeeze-proposed-updates;
//  o=Debian,n=squeeze,l=Debian-Security;

I think the idea is n=squeeze is supposed to match the Codename
attribute in the Release file.  It would be great if it worked, but I
don't see how it can because the python apt package doesn't include an
element describing the codename in
apt.Cache()[package].candidate.origins, and neither can I see any code
in unattended-upgrades that would match it.

It may looks like it works because unattended-upgrade doesn't report an
error if you give it a keyword it doesn't understand (like n or
codename).  A side effect of this is if you included a line like
true=true (or any other unknown keyword) every package will always
match.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org