SOLVED??: Re: How to add an origin to unattended upgrades?
On Fri, 16 Oct 2020 13:24:06 -0600
Charles Curley <charlescurley@charlescurley.com> wrote:
> I have unattended upgrades running on a testbed laptop. I would like
> to add an origin to the list, but I don't think I am getting the entry
> quite right. The origin is for vivaldi, which has its own repo outside
> the Debian repos.
On further reflection, I looked at the sample entries for origins, and
realized that the line for Debian Backports in the Archive or Suite
section might be a better model to try. After commenting out my
original effort, I added:
--------------------------------------------------
// "o=Debian Backports,a=${distro_codename}-backports,l=Debian
Backports"; "o=Vivaldi Technologies,a=stable,l=Official Vivaldi package
repository"; };
--------------------------------------------------
This appears to work in a dry run:
--------------------------------------------------
root@orca:~# unattended-upgrades --dry-run -d
Initial blacklist :
Initial whitelist:
Starting unattended upgrades script
Allowed origins are: origin=Debian,codename=buster-updates,
origin=Debian,codename=buster,label=Debian,
origin=Debian,codename=buster,label=Debian-Security, o=Vivaldi
Technologies,a=stable,l=Official Vivaldi package repository Using
(^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^linux-image-unsigned-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*|^linux-buildinfo-[0-9]+\.[0-9\.]+-.*|^linux-source-[0-9]+\.[0-9\.]+-.*)
regexp to find kernel packages Using
(^linux-image-4\.19\.0\-11\-amd64$|^linux-headers-4\.19\.0\-11\-amd64$|^linux-image-extra-4\.19\.0\-11\-amd64$|^linux-modules-4\.19\.0\-11\-amd64$|^linux-modules-extra-4\.19\.0\-11\-amd64$|^linux-signed-image-4\.19\.0\-11\-amd64$|^linux-image-unsigned-4\.19\.0\-11\-amd64$|^kfreebsd-image-4\.19\.0\-11\-amd64$|^kfreebsd-headers-4\.19\.0\-11\-amd64$|^gnumach-image-4\.19\.0\-11\-amd64$|^.*-modules-4\.19\.0\-11\-amd64$|^.*-kernel-4\.19\.0\-11\-amd64$|^linux-backports-modules-.*-4\.19\.0\-11\-amd64$|^linux-modules-.*-4\.19\.0\-11\-amd64$|^linux-tools-4\.19\.0\-11\-amd64$|^linux-cloud-tools-4\.19\.0\-11\-amd64$|^linux-buildinfo-4\.19\.0\-11\-amd64$|^linux-source-4\.19\.0\-11\-amd64$)
regexp to find running kernel packages Checking: linux-image-amd64
([<Origin component:'main' archive:'stable' origin:'Debian'
label:'Debian-Security' site:'security.debian.org' isTrusted:True>])
Checking: linux-libc-dev ([<Origin component:'main' archive:'stable'
origin:'Debian' label:'Debian-Security' site:'security.debian.org'
isTrusted:True>]) Checking: vivaldi-stable ([<Origin component:'main'
archive:'stable' origin:'Vivaldi Technologies' label:'Official Vivaldi
package repository' site:'repo.vivaldi.com' isTrusted:True>]) pkgs that
look like they should be upgraded: linux-image-amd64 linux-libc-dev
vivaldi-stable Get:1 http://repo.vivaldi.com/stable/deb stable/main
amd64 vivaldi-stable amd64 3.4.2066.76-1 [75.7 MB] Fetched 75.7 MB in
6s (14.6 MB/s) fetch.run() result: 0 <apt_pkg.AcquireItem
object:Status: 2 Complete: 1 Local: 0 IsTrusted: 1 FileSize: 75666120
DestFile:'/var/cache/apt/archives/vivaldi-stable_3.4.2066.76-1_amd64.deb'
DescURI:
'http://repo.vivaldi.com/stable/deb/pool/main/vivaldi-stable_3.4.2066.76-1_amd64.deb'
ID:1 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/vivaldi-stable_3.4.2066.76-1_amd64.deb)
found pkg: vivaldi-stable No conffiles in
deb /var/cache/apt/archives/vivaldi-stable_3.4.2066.76-1_amd64.deb
(There is no member named 'conffiles') <apt_pkg.AcquireItem
object:Status: 2 Complete: 1 Local: 1 IsTrusted: 1 FileSize: 48261216
DestFile:'/var/cache/apt/archives/linux-image-4.19.0-12-amd64_4.19.152-1_amd64.deb'
DescURI:
'http://security.debian.org/debian-security/pool/updates/main/l/linux-signed-amd64/linux-image-4.19.0-12-amd64_4.19.152-1_amd64.deb'
ID:0 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/linux-image-4.19.0-12-amd64_4.19.152-1_amd64.deb)
No conffiles in
deb /var/cache/apt/archives/linux-image-4.19.0-12-amd64_4.19.152-1_amd64.deb
(There is no member named 'conffiles') <apt_pkg.AcquireItem
object:Status: 2 Complete: 1 Local: 1 IsTrusted: 1 FileSize: 8208
DestFile:'/var/cache/apt/archives/linux-image-amd64_4.19+105+deb10u7_amd64.deb'
DescURI:
'http://security.debian.org/debian-security/pool/updates/main/l/linux-latest/linux-image-amd64_4.19+105+deb10u7_amd64.deb'
ID:0 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/linux-image-amd64_4.19+105+deb10u7_amd64.deb)
found pkg: linux-image-amd64 No conffiles in
deb /var/cache/apt/archives/linux-image-amd64_4.19+105+deb10u7_amd64.deb
(There is no member named 'conffiles') <apt_pkg.AcquireItem
object:Status: 2 Complete: 1 Local: 1 IsTrusted: 1 FileSize: 1402344
DestFile:'/var/cache/apt/archives/linux-libc-dev_4.19.152-1_amd64.deb'
DescURI:
'http://security.debian.org/debian-security/pool/updates/main/l/linux/linux-libc-dev_4.19.152-1_amd64.deb'
ID:0 ErrorText: ''>
check_conffile_prompt(/var/cache/apt/archives/linux-libc-dev_4.19.152-1_amd64.deb)
found pkg: linux-libc-dev No conffiles in
deb /var/cache/apt/archives/linux-libc-dev_4.19.152-1_amd64.deb (There
is no member named 'conffiles') blacklist: [] whitelist: [] Option
--dry-run given, *not* performing real actions Packages that will be
upgraded: linux-image-amd64 linux-libc-dev vivaldi-stable Writing dpkg
log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
applying set ['linux-image-4.19.0-12-amd64', 'linux-image-amd64']
apt-listchanges: Reading changelogs... /usr/bin/dpkg --status-fd 11
--no-triggers --unpack
--auto-deconfigure /var/cache/apt/archives/linux-image-4.19.0-12-amd64_4.19.152-1_amd64.deb /var/cache/apt/archives/linux-image-amd64_4.19+105+deb10u7_amd64.deb /usr/bin/dpkg
--status-fd 11 --configure --pending localepurge: Disk space freed
in /usr/share/locale: 0 KiB localepurge: Disk space freed
in /usr/share/man: 0 KiB localepurge: Disk space freed
in /usr/share/gnome/help: 0 KiB localepurge: Disk space freed
in /usr/share/omf: 0 KiB
Total disk space freed by localepurge: 0 KiB
left to upgrade {'vivaldi-stable', 'linux-libc-dev'}
applying set ['vivaldi-stable']
apt-listchanges: Reading changelogs...
/usr/bin/dpkg --status-fd 11 --no-triggers --unpack
--auto-deconfigure /var/cache/apt/archives/vivaldi-stable_3.4.2066.76-1_amd64.deb /usr/bin/dpkg
--status-fd 11 --configure --pending localepurge: Disk space freed
in /usr/share/locale: 0 KiB localepurge: Disk space freed
in /usr/share/man: 0 KiB localepurge: Disk space freed
in /usr/share/gnome/help: 0 KiB localepurge: Disk space freed
in /usr/share/omf: 0 KiB
Total disk space freed by localepurge: 0 KiB
left to upgrade {'linux-libc-dev'}
applying set ['linux-libc-dev']
apt-listchanges: Reading changelogs...
/usr/bin/dpkg --status-fd 11 --no-triggers --unpack
--auto-deconfigure /var/cache/apt/archives/linux-libc-dev_4.19.152-1_amd64.deb /usr/bin/dpkg
--status-fd 11 --configure --pending localepurge: Disk space freed
in /usr/share/locale: 0 KiB localepurge: Disk space freed
in /usr/share/man: 0 KiB localepurge: Disk space freed
in /usr/share/gnome/help: 0 KiB localepurge: Disk space freed
in /usr/share/omf: 0 KiB
Total disk space freed by localepurge: 0 KiB
left to upgrade set()
All upgrades installed
InstCount=0 DelCount=0 BrokenCount=0
root@orca:~#
--------------------------------------------------
We will see what happens when the actual run goes some time early
tomorrow morning.
Thanks to Andrei POPESCU <andreimpopescu@gmail.com> for help in
debugging this.
Incidentally, it appears from an error message I got while trying a
malformed entry that the program simply treats the configuration file
as a chunk of python code to execute. Folks familiar with python may
find that useful.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Reply to: