Comments on: Third-party unattended upgrades in three steps

By: Things I learned today: apt, cron, and unattended-upgrades « Notatypewriter's Blog

Fri, 05 Aug 2011 03:36:43 +0000

[...] Here are some instructions on adding third party repositories to the unattended-upgrades list. But rather than pointing your browser at the Release file at each repository (Google’s repository actually seems to disallow this, possibly through some user agent magic), you can look at your apt cache for the cached versions of these files. These are located in /var/lib/apt/lists. The files you want are the ones ending in *_Release. [...]

By: Dotdeb packages unattended upgrade | blog.erben.sk

Dotdeb packages unattended upgrade | blog.erben.sk — Thu, 07 Apr 2011 07:39:23 +0000

[...] this page how to enable other repositories. Filed under: uncategorized Leave a comment Comments (0) [...]

By: Edward Z. Yang

Edward Z. Yang — Fri, 14 Jan 2011 04:08:39 +0000

There might be some quoting mumble going on, but I suspect the obvious thing probably will work. Try it and report back?

By: Andres Cimmarusti

Andres Cimmarusti — Fri, 14 Jan 2011 03:53:30 +0000

Thanks for this post, it’s just what I was looking for… Well, almost.
I run Debian Squeeze on several computers and I use some packages from Debian Backports and Debian Multimedia repositories (I have my apt preferences setup so that only the packages already installed from these repos become upgradeable).

Naturally I want to add these repos to the list of Allowed origins. Following your tutorial I get to, for example the Debian multimedia release file: http://www.debian-multimedia.org/dists/squeeze/Release
But you can see that in the field ORIGINS there are the 3 words: Unofficial Multimedia Packages.
I’m hesitant to put these 3 words in my 50unattended-upgrades followed by the SUITE.
Is this going to work at all? what should I do?

By: Edward Z. Yang

Edward Z. Yang — Mon, 14 Jun 2010 03:35:21 +0000

My understanding is that apt-pinning works regardless of how the update gets taken (whether it’s unattended or not). You should try and see how it goes.

By: syaman

syaman — Sun, 13 Jun 2010 23:36:36 +0000

Is it also possible to do apt-pinning for unattended upgrades? For instance if several updated packages appear in both the security repository and a third party one, but I only want a particular package to always be updated from the third party repository?

Thanks in advance

By: Edward Z. Yang

Edward Z. Yang — Fri, 07 May 2010 18:34:50 +0000

It worked for me without the namespace qualifier.

By: James Revillini

James Revillini — Fri, 07 May 2010 15:38:37 +0000

Great post! Question – you said:

This translates into the following configuration:

Unattended-Upgrade::Allowed-Origins {
“Ksplice karmic”;
};

Should “Unattended-Upgrade::Allowed-Origins {” be “APT::Periodic::Unattended-Upgrade::Allowed-Origins {“?

Maybe you assumed we’d know that, but I wasn’t sure.

By: Edward Z. Yang

Edward Z. Yang — Wed, 03 Mar 2010 21:45:43 +0000

Updated post to include this vital bit of information.

By: Ken Takusagawa

Ken Takusagawa — Wed, 03 Mar 2010 21:35:56 +0000

One should also verify that

APT::Periodic::Unattended-Upgrade “1″;

is in /etc/apt/apt.conf.d/10periodic

I think I had to add it manually for Debian Lenny.