Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #227885 > unrolled thread

How to add an origin to unattended upgrades?

Started byCharles Curley <charlescurley@charlescurley.com>
First post2020-10-16 21:50 +0200
Last post2020-10-20 20:00 +0200
Articles 9 — 2 participants

Back to article view | Back to linux.debian.user

Contents

  How to add an origin to unattended upgrades? Charles Curley <charlescurley@charlescurley.com> - 2020-10-16 21:50 +0200
    Re: How to add an origin to unattended upgrades? Andrei POPESCU <andreimpopescu@gmail.com> - 2020-10-17 08:30 +0200
      Re: How to add an origin to unattended upgrades? Charles Curley <charlescurley@charlescurley.com> - 2020-10-17 16:10 +0200
        Re: How to add an origin to unattended upgrades? Andrei POPESCU <andreimpopescu@gmail.com> - 2020-10-18 12:30 +0200
          Re: How to add an origin to unattended upgrades? Charles Curley <charlescurley@charlescurley.com> - 2020-10-19 20:40 +0200
    SOLVED??: Re: How to add an origin to unattended upgrades? Charles Curley <charlescurley@charlescurley.com> - 2020-10-19 21:00 +0200
      Re: SOLVED??: Re: How to add an origin to unattended upgrades? Andrei POPESCU <andreimpopescu@gmail.com> - 2020-10-20 09:40 +0200
        Re: SOLVED??: Re: How to add an origin to unattended upgrades? Charles Curley <charlescurley@charlescurley.com> - 2020-10-20 20:00 +0200
      Re: SOLVED: Re: How to add an origin to unattended upgrades? Charles Curley <charlescurley@charlescurley.com> - 2020-10-20 20:00 +0200

#227885 — How to add an origin to unattended upgrades?

FromCharles Curley <charlescurley@charlescurley.com>
Date2020-10-16 21:50 +0200
SubjectHow to add an origin to unattended upgrades?
Message-ID<B0DTH-Uo-5@gated-at.bofh.it>
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/

[toc] | [next] | [standalone]

#227898

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2020-10-17 08:30 +0200
Message-ID<B0NT3-743-1@gated-at.bofh.it>
In reply to#227885

[Multipart message — attachments visible in raw view] — view raw

On Vi, 16 oct 20, 13:24:06, Charles Curley wrote:
> 
> --------------------------------------------------
> 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:~# 
> --------------------------------------------------

Please show also the output of 'apt policy vivaldi' (or whatever the 
package name is).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#227911

FromCharles Curley <charlescurley@charlescurley.com>
Date2020-10-17 16:10 +0200
Message-ID<B0V4d-2Y9-7@gated-at.bofh.it>
In reply to#227898

[Multipart message — attachments visible in raw view] — view raw

On Sat, 17 Oct 2020 09:21:22 +0300
Andrei POPESCU <andreimpopescu@gmail.com> wrote:

> Please show also the output of 'apt policy vivaldi' (or whatever the 
> package name is).

--------------------------------------------------
root@orca:~# apt policy vivaldi-stable
vivaldi-stable:
  Installed: 3.1.1929.45-1
  Candidate: 3.4.2066.76-1
  Version table:
     3.4.2066.76-1 500
        500 http://repo.vivaldi.com/stable/deb stable/main amd64 Packages
 *** 3.1.1929.45-1 100
        100 /var/lib/dpkg/status
root@orca:~# 
--------------------------------------------------


-- 
Does anybody read signatures any more?

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

[toc] | [prev] | [next] | [standalone]

#227939

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2020-10-18 12:30 +0200
Message-ID<B1e6R-5WP-1@gated-at.bofh.it>
In reply to#227911

[Multipart message — attachments visible in raw view] — view raw

On Sb, 17 oct 20, 07:34:53, Charles Curley wrote:
> On Sat, 17 Oct 2020 09:21:22 +0300
> Andrei POPESCU <andreimpopescu@gmail.com> wrote:
> 
> > Please show also the output of 'apt policy vivaldi' (or whatever the 
> > package name is).
> 
> --------------------------------------------------
> root@orca:~# apt policy vivaldi-stable
> vivaldi-stable:
>   Installed: 3.1.1929.45-1
>   Candidate: 3.4.2066.76-1
>   Version table:
>      3.4.2066.76-1 500
>         500 http://repo.vivaldi.com/stable/deb stable/main amd64 Packages
>  *** 3.1.1929.45-1 100
>         100 /var/lib/dpkg/status
> root@orca:~# 
> --------------------------------------------------

This looks good to me.

After looking through the bugs list for unattended-upgrades I would 
suggest you check whether upgrading vivaldi-stable requires installing 
new packages or package removals ('apt upgrade -s' should tell), as this 
will also block the upgrade (by design, see #645382).

I'm also not quite sure about the spaces in the origin and label. The 
log suggests they are interpreted correctly, though you could try 
escaping them (the submitter in #940151 is using ', ' to separate the 
fields, which might be the cause for his issues).

Other that that you could try to debug /usr/bin/unattended-upgrade 
(Python) or contact the maintainer, e.g. via a follow-up to #799754.

Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#227983

FromCharles Curley <charlescurley@charlescurley.com>
Date2020-10-19 20:40 +0200
Message-ID<B1IeC-7e2-11@gated-at.bofh.it>
In reply to#227939

[Multipart message — attachments visible in raw view] — view raw

On Sun, 18 Oct 2020 13:29:26 +0300
Andrei POPESCU <andreimpopescu@gmail.com> wrote:

> This looks good to me.
> 
> After looking through the bugs list for unattended-upgrades I would 
> suggest you check whether upgrading vivaldi-stable requires
> installing new packages or package removals ('apt upgrade -s' should
> tell), as this will also block the upgrade (by design, see #645382).

--------------------------------------------------
root@orca:~# apt upgrade -s
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-image-4.19.0-12-amd64
The following packages will be upgraded:
  linux-image-amd64 linux-libc-dev vivaldi-stable
3 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Inst vivaldi-stable [3.1.1929.45-1] (3.4.2066.76-1 Official Vivaldi package repository:stable [amd64])
Inst linux-image-4.19.0-12-amd64 (4.19.152-1 Debian-Security:10/stable [amd64])
Inst linux-image-amd64 [4.19+105+deb10u6] (4.19+105+deb10u7 Debian-Security:10/stable [amd64])
Inst linux-libc-dev [4.19.146-1] (4.19.152-1 Debian-Security:10/stable [amd64])
Conf vivaldi-stable (3.4.2066.76-1 Official Vivaldi package repository:stable [amd64])
Conf linux-image-4.19.0-12-amd64 (4.19.152-1 Debian-Security:10/stable [amd64])
Conf linux-image-amd64 (4.19+105+deb10u7 Debian-Security:10/stable [amd64])
Conf linux-libc-dev (4.19.152-1 Debian-Security:10/stable [amd64])
root@orca:~# 
--------------------------------------------------

It looks to me like a straight upgrade with no removals.


> 
> I'm also not quite sure about the spaces in the origin and label. The 
> log suggests they are interpreted correctly, though you could try 
> escaping them (the submitter in #940151 is using ', ' to separate the 
> fields, which might be the cause for his issues).

I figured from the supplied origins that they are comma delimited, but
your point about spaces is a good one. I tried that.

--------------------------------------------------
        "origin='Vivaldi Technologies',codename=stable,label='Official Vivaldi package repository'";
--------------------------------------------------

--------------------------------------------------
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: 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
Fetched 0 B in 0s (0 B/s)                                                                                                          
fetch.run() result: 0
<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
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 {'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:~# 
--------------------------------------------------

It appears to parse the origin correctly. Indeed, it appears that the
program supplies single quotes even if I don't.


> 
> Other that that you could try to debug /usr/bin/unattended-upgrade 
> (Python) or contact the maintainer, e.g. via a follow-up to #799754.

Sorry, I'm not a skilled snake charmer. I will keep the suggestion to
contact the maintainer in mind.

-- 
Does anybody read signatures any more?

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

[toc] | [prev] | [next] | [standalone]

#227984 — SOLVED??: Re: How to add an origin to unattended upgrades?

FromCharles Curley <charlescurley@charlescurley.com>
Date2020-10-19 21:00 +0200
SubjectSOLVED??: Re: How to add an origin to unattended upgrades?
Message-ID<B1IxY-7kP-11@gated-at.bofh.it>
In reply to#227885
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/

[toc] | [prev] | [next] | [standalone]

#228005 — Re: SOLVED??: Re: How to add an origin to unattended upgrades?

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2020-10-20 09:40 +0200
SubjectRe: SOLVED??: Re: How to add an origin to unattended upgrades?
Message-ID<B1Upr-6f4-1@gated-at.bofh.it>
In reply to#227984

[Multipart message — attachments visible in raw view] — view raw

On Lu, 19 oct 20, 12:51:20, Charles Curley wrote:
> 
> 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"; };
> --------------------------------------------------

Did your mail program mangle long lines here?

For the archives it would be good to repost the correct line(s) that 
work.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#228034 — Re: SOLVED??: Re: How to add an origin to unattended upgrades?

FromCharles Curley <charlescurley@charlescurley.com>
Date2020-10-20 20:00 +0200
SubjectRe: SOLVED??: Re: How to add an origin to unattended upgrades?
Message-ID<B245s-3BN-5@gated-at.bofh.it>
In reply to#228005

[Multipart message — attachments visible in raw view] — view raw

On Tue, 20 Oct 2020 10:38:20 +0300
Andrei POPESCU <andreimpopescu@gmail.com> wrote:

> > --------------------------------------------------
> > //      "o=Debian Backports,a=${distro_codename}-backports,l=Debian
> > Backports"; "o=Vivaldi Technologies,a=stable,l=Official Vivaldi
> > package repository"; };
> > --------------------------------------------------  
> 
> Did your mail program mangle long lines here?
> 
> For the archives it would be good to repost the correct line(s) that 
> work.

Oops. Thank you for saying something.

--------------------------------------------------
//      "o=Debian Backports,a=${distro_codename}-backports,l=Debian Backports";
	"o=Vivaldi Technologies,a=stable,l=Official Vivaldi package repository";
};
--------------------------------------------------


-- 
Does anybody read signatures any more?

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

[toc] | [prev] | [next] | [standalone]

#228035 — Re: SOLVED: Re: How to add an origin to unattended upgrades?

FromCharles Curley <charlescurley@charlescurley.com>
Date2020-10-20 20:00 +0200
SubjectRe: SOLVED: Re: How to add an origin to unattended upgrades?
Message-ID<B245s-3BN-3@gated-at.bofh.it>
In reply to#227984
On Mon, 19 Oct 2020 12:51:20 -0600
Charles Curley <charlescurley@charlescurley.com> wrote:

> 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:

This worked in a live run. Vivaldi was updated this morning.

The correct line, not mangled by my mail program, is:

--------------------------------------------------
//      "o=Debian Backports,a=${distro_codename}-backports,l=Debian Backports";
	"o=Vivaldi Technologies,a=stable,l=Official Vivaldi package repository";
};
--------------------------------------------------

Thanks to Andrei POPESCU <andreimpopescu@gmail.com> for catching that.

-- 
Does anybody read signatures any more?

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web