[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

How to add an origin to unattended upgrades?



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.

I set things up according to
https://wiki.debian.org/UnattendedUpgrades, and it works correctly for
Debian origins. The laptop had not been used for several months, so the
next unattended upgrade did a massive upgrade. So far, so good.

I tried adding the vivaldi origin to the mix. Now I cannot find
whatever web page I got the instructions from, but here are the results:

--------------------------------------------------
root@orca:~# apt-cache policy | grep -i vivaldi
 500 http://repo.vivaldi.com/stable/deb stable/main i386 Packages
     release o=Vivaldi Technologies,a=stable,l=Official Vivaldi package repository,c=main,b=i386
     origin repo.vivaldi.com
 500 http://repo.vivaldi.com/stable/deb stable/main amd64 Packages
     release o=Vivaldi Technologies,a=stable,l=Official Vivaldi package repository,c=main,b=amd64
     origin repo.vivaldi.com
root@orca:~# 
--------------------------------------------------

led to the following in /etc/apt/apt.conf.d/50unattended-upgrades:

--------------------------------------------------
Unattended-Upgrade::Origins-Pattern {
        // Codename based matching:
        // This will follow the migration of a release through different
        // archives (e.g. from testing to stable and later oldstable).
        // Software will be the latest available for the named release,
        // but the Debian release itself will not be automatically upgraded.
//      "origin=Debian,codename=${distro_codename}-updates";
        "origin=Debian,codename=${distro_codename}-updates"; // 2020-06-16
//      "origin=Debian,codename=${distro_codename}-proposed-updates";
        "origin=Debian,codename=${distro_codename},label=Debian";
        "origin=Debian,codename=${distro_codename},label=Debian-Security";
        "origin=Vivaldi Technologies,codename=stable,label=Official Vivaldi package repository";

        // Archive or Suite based matching:
        // Note that this will silently match a different release after
        // migration to the specified archive (e.g. testing becomes the
        // new stable).
//      "o=Debian,a=stable";
//      "o=Debian,a=stable-updates";
//      "o=Debian,a=proposed-updates";
//      "o=Debian Backports,a=${distro_codename}-backports,l=Debian Backports";
};
--------------------------------------------------

There is an upgrade pending for Vivaldi, and the package has been
downloaded. But unattended upgrades has not installed it.

--------------------------------------------------
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, origin=Vivaldi Technologies,codename=stable,label=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: 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: 
Fetched 0 B in 0s (0 B/s)
fetch.run() result: 0
blacklist: []
whitelist: []
No packages found that can be upgraded unattended and no pending auto-removals
root@orca:~# 
--------------------------------------------------


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/


Reply to: