[Bug 2066285] [NEW] ModuleNotFoundError: No module named 'imp' with python 3.12
Public bug reported: From Noble, using osc (0.169.1-2) from universe and calling osc results in: [~]$ osc Traceback (most recent call last): File "/usr/bin/osc", line 10, in from osc import commandline, babysitter File "/usr/lib/python3/dist-packages/osc/commandline.py", line 14, in import imp ModuleNotFoundError: No module named 'imp' ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: osc 0.169.1-2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 21 17:26:32 2024 InstallationDate: Installed on 2023-10-08 (226 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: osc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: osc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066285 Title: ModuleNotFoundError: No module named 'imp' with python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/osc/+bug/2066285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970227] [NEW] Add Kinetic to distro-info-data
Public bug reported: KK has a name. distro-info needs an update. SRU Test: 1. ubuntu-distro-info -d If you get a DistroDataOutdated exception or similar error, you have old data. If you see 'kinetic', we're happy. [ Test Case ] Verify that the following subcommands of `distro-info` print information about the new devel and current stable releases: * `--devel` * `--supported` * `--stable` and try the same commands with these modifiers: * `--date=<1 day after release>` along with the above * `--fullname` * `--release` ** Affects: distro-info-data (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970227 Title: Add Kinetic to distro-info-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1970227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947368] Re: [SRU] Add Jammy to distro-info-data
** Changed in: distro-info-data (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947368 Title: [SRU] Add Jammy to distro-info-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1947368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958227] Re: Traceback when calling "poetry" command: ModuleNotFoundError: No module named 'cachecontrol'
@Akash, this is about the debian package (which handles the dependencies). The bug ist still there. Easy reproducer is: $ sudo apt install python3-poetry $ poetry Traceback (most recent call last): File "/usr/bin/poetry", line 5, in from poetry.console import main File "/usr/lib/python3/dist-packages/poetry/console/__init__.py", line 1, in from .application import Application File "/usr/lib/python3/dist-packages/poetry/console/application.py", line 7, in from .commands.about import AboutCommand File "/usr/lib/python3/dist-packages/poetry/console/commands/__init__.py", line 4, in from .check import CheckCommand File "/usr/lib/python3/dist-packages/poetry/console/commands/check.py", line 2, in from poetry.factory import Factory File "/usr/lib/python3/dist-packages/poetry/factory.py", line 18, in from .repositories.pypi_repository import PyPiRepository File "/usr/lib/python3/dist-packages/poetry/repositories/pypi_repository.py", line 11, in from cachecontrol import CacheControl ModuleNotFoundError: No module named 'cachecontrol' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958227 Title: Traceback when calling "poetry" command: ModuleNotFoundError: No module named 'cachecontrol' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poetry/+bug/1958227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967982] Re: ua auto-attach on AWS Trusty Pro not working
** Package changed: ubuntu-advantage-tools (Ubuntu) => cloud-images ** Changed in: cloud-images Status: New => Incomplete ** Changed in: cloud-images Status: Incomplete => In Progress ** Changed in: cloud-images Importance: Undecided => Critical ** Changed in: cloud-images Assignee: (unassigned) => Thomas Bechtold (toabctl) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967982 Title: ua auto-attach on AWS Trusty Pro not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1967982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968004] Re: Thunderbird opens new window (login.ubuntu.com for me) when trying to open any mail
recreating the account worked (after the login.ubuntu.com page, I got redirected to the accounts.google.com page to allow thunderbird to access mail & calendar, that was not happening with my existing account after the package update) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968004 Title: Thunderbird opens new window (login.ubuntu.com for me) when trying to open any mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1968004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968004] [NEW] Thunderbird opens new window (login.ubuntu.com for me) when trying to open any mail
Public bug reported: Since the latest update: Upgrade: thunderbird:amd64 (1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1), thunderbird-gnome-support:amd64 (1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1) End-Date: 2022-04-05 06:36:02 Thunderbird opens a new window (title is "Enter credentials for thomas.becht...@canonical.com on imap.gmail.com", url is https://login.ubuntu.com) when I select any new message in thunderbird. Even if I do login, nothing happens and the page reopens when I select another message. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.8.0+build2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BuildID: 20220401203107 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 10:05:04 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-03-21 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.8.0/20220401203107 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to jammy on 2022-03-21 (15 days ago) dmi.bios.date: 12/23/2021 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET68W(1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnLENOVO:bvrR1BET68W(1.37):bd12/23/2021:br1.37:efr1.37:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968004 Title: Thunderbird opens new window (login.ubuntu.com for me) when trying to open any mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1968004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967982] [NEW] ua auto-attach on AWS Trusty Pro not working
Public bug reported: There is a new Trusty Pro image on AWS Marketplace (https://aws.amazon.com/marketplace/pp/prodview-5rutzpvpjl65m ). When launching this image, ua is not auto-attached. Here is some info. root@ip-172-31-28-37:~# dpkg -l|grep ubuntu-advan ii ubuntu-advantage-tools 26.3~14.04.1 amd64management tools for Ubuntu Advantage ^^ this was installed (in the image) from the ua-client/stable ppa. root@ip-172-31-28-37:~# dpkg -l |grep cloud-init ii cloud-init 0.7.5-0ubuntu1.23 all Init scripts for cloud instances root@ip-172-31-28-37:~# ua status SERVICE AVAILABLE DESCRIPTION esm-infra yesUA Infra: Extended Security Maintenance (ESM) fips no NIST-certified FIPS modules fips-updates no Uncertified security updates to FIPS modules livepatch no Canonical Livepatch service This machine is not attached to a UA subscription. See https://ubuntu.com/advantage Calling `ua auto-attach` manually does work: root@ip-172-31-28-37:~# ua auto-attach Enabling default service esm-infra Updating package lists ESM Infra enabled This machine is now attached to 'XXX' SERVICE ENTITLED STATUSDESCRIPTION esm-infra yes enabled UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified FIPS modules fips-updates yes n/a Uncertified security updates to FIPS modules livepatch yes n/a Available with the HWE kernel NOTICES Operation in progress: ua auto-attach Enable services with: ua enable Account: XXX Subscription: XXX Valid until: -12-31 00:00:00 Technical support level: essential ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967982 Title: ua auto-attach on AWS Trusty Pro not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1967982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967982] Re: ua auto-attach on AWS Trusty Pro not working
** Attachment added: "ubuntu-advantage.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1967982/+attachment/5577485/+files/ubuntu-advantage.log ** Description changed: There is a new Trusty Pro image on AWS Marketplace (https://aws.amazon.com/marketplace/pp/prodview-5rutzpvpjl65m ). When launching this image, ua is not auto-attached. Here is some info. root@ip-172-31-28-37:~# dpkg -l|grep ubuntu-advan ii ubuntu-advantage-tools 26.3~14.04.1 amd64management tools for Ubuntu Advantage ^^ this was installed (in the image) from the ua-client/stable ppa. + + root@ip-172-31-28-37:~# dpkg -l |grep cloud-init + ii cloud-init 0.7.5-0ubuntu1.23 all Init scripts for cloud instances root@ip-172-31-28-37:~# ua status SERVICE AVAILABLE DESCRIPTION esm-infra yesUA Infra: Extended Security Maintenance (ESM) fips no NIST-certified FIPS modules fips-updates no Uncertified security updates to FIPS modules livepatch no Canonical Livepatch service This machine is not attached to a UA subscription. See https://ubuntu.com/advantage + + + Calling `ua auto-attach` manually does work: + + root@ip-172-31-28-37:~# ua auto-attach + Enabling default service esm-infra + Updating package lists + ESM Infra enabled + This machine is now attached to 'XXX' + + SERVICE ENTITLED STATUSDESCRIPTION + esm-infra yes enabled UA Infra: Extended Security Maintenance (ESM) + fips yes n/a NIST-certified FIPS modules + fips-updates yes n/a Uncertified security updates to FIPS modules + livepatch yes n/a Available with the HWE kernel + + NOTICES + Operation in progress: ua auto-attach + + Enable services with: ua enable + + Account: XXX +Subscription: XXX + Valid until: -12-31 00:00:00 + Technical support level: essential + + + Is there a specific cloud-init version needed to make auto-attach during boot working? ** Description changed: There is a new Trusty Pro image on AWS Marketplace (https://aws.amazon.com/marketplace/pp/prodview-5rutzpvpjl65m ). When launching this image, ua is not auto-attached. Here is some info. root@ip-172-31-28-37:~# dpkg -l|grep ubuntu-advan ii ubuntu-advantage-tools 26.3~14.04.1 amd64management tools for Ubuntu Advantage ^^ this was installed (in the image) from the ua-client/stable ppa. root@ip-172-31-28-37:~# dpkg -l |grep cloud-init ii cloud-init 0.7.5-0ubuntu1.23 all Init scripts for cloud instances - root@ip-172-31-28-37:~# ua status SERVICE AVAILABLE DESCRIPTION esm-infra yesUA Infra: Extended Security Maintenance (ESM) fips no NIST-certified FIPS modules fips-updates no Uncertified security updates to FIPS modules livepatch no Canonical Livepatch service This machine is not attached to a UA subscription. See https://ubuntu.com/advantage - Calling `ua auto-attach` manually does work: - root@ip-172-31-28-37:~# ua auto-attach + root@ip-172-31-28-37:~# ua auto-attach Enabling default service esm-infra Updating package lists ESM Infra enabled This machine is now attached to 'XXX' SERVICE ENTITLED STATUSDESCRIPTION esm-infra yes enabled UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified FIPS modules fips-updates yes n/a Uncertified security updates to FIPS modules livepatch yes n/a Available with the HWE kernel NOTICES Operation in progress: ua auto-attach Enable services with: ua enable - Account: XXX -Subscription: XXX - Valid until: -12-31 00:00:00 + Account: XXX + Subscription: XXX + Valid until: -12-31 00:00:00 Technical support level: essential - - - Is there a specific cloud-init version needed to make auto-attach during boot working? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967982 Title: ua auto-attach on AWS Trusty Pro not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1967982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967768] [NEW] can not start libreoffice: execv failed: No such file or directory
Public bug reported: I'm trying to execute libreoffice: tom@melisse:~$ libreoffice.writer execv failed: No such file or directory tom@melisse:~$ snap list|grep libreoffice libreoffice 7.3.2.2 250latest/stable canonical* - tom@melisse:~$ ls /snap/libreoffice/2 247/ 250/ tom@melisse:~$ ls /snap/libreoffice/250/ config/ etc/ gnome-platform/ lib/ meta/usr/ data-dir/filebug.py javasettings.py libreoffice.wrapper snap/var/ tom@melisse:~$ ls /snap/libreoffice/250/ config data-dir etc filebug.py gnome-platform javasettings.py lib libreoffice.wrapper meta snap usr var tom@melisse:~$ ls /snap/libreoffice/250/usr/bin/ tom@melisse:~$ ls /snap/libreoffice/250/usr/sbin/ update-java-alternatives tom@melisse:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 17:11:19 2022 InstallationDate: Installed on 2022-03-21 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap: libreoffice 7.3.2.2 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 61 Done2022-04-04T06:42:42+02:00 2022-04-04T06:43:21+02:00 Auto-refresh snaps "libreoffice", "openstackclients" SnapSource: ubuntu/+source/libreoffice UpgradeStatus: Upgraded to jammy on 2022-03-21 (13 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy snap wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967768 Title: can not start libreoffice: execv failed: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] Re: Optionally allow building CPC images with core (16.04) based snaps
I did a testbuild with bartender and it works. But OTOH, this patch is no longer needed given that the Anbox team did update their snaps to be based on core20. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] Re: Optionally allow building CPC images with core (16.04) based snaps
Because impish did not receive the commit that broke our build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] Re: Optionally allow building CPC images with core (16.04) based snaps
** Changed in: livecd-rootfs (Ubuntu Focal) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] Re: Optionally allow building CPC images with core (16.04) based snaps
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/416586 ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] Re: Optionally allow building CPC images with core (16.04) based snaps
** Description changed: + [Impact] Commit 245f7772bdb743547e4d2f7df2475afc0eb5ec1e aborts the build when a snap still depends on core (16.04 runtime). - That's fine for Ubuntu but the CPC team builds images which still depend on core (that will be fixed soon). - So adding an option to allow those builds will fix the problem. + That's fine for Ubuntu but the CPC team builds images which still depend on core (that will be fixed soon). So currently those CPC builds are failing. + Adding an option to allow those builds will fix the problem. + + [Test Plan] + The bug can be reproduced with: + + $ ./scripts/ubuntu-bartender/ubuntu-bartender --hook-extras-dir + ~/devel/canonical/cloudware/cpc_packaging.extra --livecd-rootfs-branch + ubuntu/focal --livecd-rootfs-dir ~/devel/livecd-rootfs/ -- --series + focal --project ubuntu-cpc --image-target ec2-anbox + + So getting this command passing validated that the bug is fixed + + [Where problems could occur] + Other builds could get broken due to this change but it's unlikely because the change is relatively small and the change is tested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959452] Re: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64
** Changed in: linux-raspi (Ubuntu) Status: Incomplete => Invalid ** Changed in: snappy Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959452 Title: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1959452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959452] Re: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64
It's a pi3 with 1 GB so my fault. sorry for the useless bug report. please close -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959452 Title: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1959452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959452] Re: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64
root@ubuntu:~# cat /proc/cpuinfo processor : 0 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 1 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 2 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 3 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 Hardware: BCM2835 Revision: a22082 Serial : d642db6b Model : Raspberry Pi 3 Model B Rev 1.2 root@ubuntu:~# head -1 /proc/meminfo MemTotal: 929936 kB root@ubuntu:~# uname -r 5.4.0-1053-raspi root@ubuntu:~# snap list Name VersionRevTracking Publisher Notes core20 20220215 1360 latest/stable canonical✓ base pi 20-1 97 20/stable canonical✓ gadget pi-kernel 5.4.0-1053.60 41220/stable canonical✓ kernel snapd 2.54.3 14982 latest/stable canonical✓ snapd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959452 Title: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1959452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964303] [NEW] Optionally allow building CPC images with core (16.04) based snaps
Public bug reported: Commit 245f7772bdb743547e4d2f7df2475afc0eb5ec1e aborts the build when a snap still depends on core (16.04 runtime). That's fine for Ubuntu but the CPC team builds images which still depend on core (that will be fixed soon). So adding an option to allow those builds will fix the problem. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964303 Title: Optionally allow building CPC images with core (16.04) based snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1964303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960892] [NEW] Starting "obs" creates a core dump
Public bug reported: This is on Jammy: $ dpkg -l|grep obs-studio ii obs-studio 27.1.3+dfsg1-2 amd64recorder and streamer for live video content $ obs Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Aborted (core dumped) tom@thymian:~/devel/canonical/cloudware/cpc_jenkins/wt1$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: obs-studio 27.1.3+dfsg1-2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 07:01:51 2022 InstallationDate: Installed on 2020-12-08 (433 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: obs-studio UpgradeStatus: Upgraded to jammy on 2021-11-30 (76 days ago) ** Affects: obs-studio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960892 Title: Starting "obs" creates a core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1960892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960892] Re: Starting "obs" creates a core dump
workaround - install from flathub . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960892 Title: Starting "obs" creates a core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1960892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958227] [NEW] Traceback when calling "poetry" command: ModuleNotFoundError: No module named 'cachecontrol'
Public bug reported: I installed poetry via apt (on Jammy amd64) and when I try to call the program, I get: $ poetry Traceback (most recent call last): File "/usr/bin/poetry", line 5, in from poetry.console import main File "/usr/lib/python3/dist-packages/poetry/console/__init__.py", line 1, in from .application import Application File "/usr/lib/python3/dist-packages/poetry/console/application.py", line 7, in from .commands.about import AboutCommand File "/usr/lib/python3/dist-packages/poetry/console/commands/__init__.py", line 4, in from .check import CheckCommand File "/usr/lib/python3/dist-packages/poetry/console/commands/check.py", line 2, in from poetry.factory import Factory File "/usr/lib/python3/dist-packages/poetry/factory.py", line 18, in from .repositories.pypi_repository import PyPiRepository File "/usr/lib/python3/dist-packages/poetry/repositories/pypi_repository.py", line 11, in from cachecontrol import CacheControl ModuleNotFoundError: No module named 'cachecontrol' $ dpkg -l|grep python3-poetry ii python3-poetry 1.1.12+dfsg-1 all Python dependency management and packaging made easy (Python 3) ii python3-poetry-core 1.0.7-2 all Poetry PEP 517 Build Backend ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: python3-poetry 1.1.12+dfsg-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 10:49:59 2022 InstallationDate: Installed on 2020-12-08 (405 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: poetry UpgradeStatus: Upgraded to jammy on 2021-11-30 (49 days ago) ** Affects: poetry (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958227 Title: Traceback when calling "poetry" command: ModuleNotFoundError: No module named 'cachecontrol' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poetry/+bug/1958227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934510] Re: [MIR] fuse3 as a dependency of qemu 6.0 and GNOME apps
Reverting open-vm-tools for now would be good to get image builds for Jammy working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934510 Title: [MIR] fuse3 as a dependency of qemu 6.0 and GNOME apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1934510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
** Changed in: launchpad-buildd Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
It's launchpad-buildd that installs fuse: https://git.launchpad.net/launchpad- buildd/tree/lpbuildd/target/build_livefs.py#n89 ** Also affects: launchpad-buildd Importance: Undecided Status: New ** Changed in: fuse3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934510] Re: [MIR] fuse3 as a dependency of qemu 6.0 and GNOME apps
Looks like this broke CPC AWS image builds for Jammy. See https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1956949 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934510 Title: [MIR] fuse3 as a dependency of qemu 6.0 and GNOME apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1934510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956949] [NEW] CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
Public bug reported: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 ** Affects: fuse3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1956949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
@Brian, yes. Running a test build does execute all the steps from the test plan. And I checked the magic-proxy.log files . They do not include the "AttributeError". Sorry for not being clear here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
Did a successful hirsute testbuild for amd64 and arm64 with repo-snapshot-stamp enabled. See: - amd64: https://launchpad.net/~toabctl/+livefs/ubuntu/focal/proposed/+build/313001 ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
Did a successful hirsute testbuild for amd64 and arm64 with repo-snapshot-stamp enabled. See: - amd64: https://launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed/+build/312995 - arm64: https://launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed/+build/312996 ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
Did a successful impish testbuild for amd64 and arm64 with repo-snapshot-stamp enabled. See: - amd64: https://launchpad.net/~toabctl/+livefs/ubuntu/impish/proposed/+build/312979 - arm64: https://launchpad.net/~toabctl/+livefs/ubuntu/impish/proposed/+build/312978 ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944906] Re: MagicProxy broken when repo-snapshot-stamp is used
SRU verification for hirsute: I did a testbuild with repo-stamp enabled against the livecd-rootfs version from proposed (2.719.3). See - https://launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed/+build/308173 - https://launchpadlibrarian.net/567803112/buildlog_ubuntu_hirsute_amd64_amd64-tarball_proposed_BUILDING.txt.gz That looks good. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944906 Title: MagicProxy broken when repo-snapshot-stamp is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1944906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
SRU verification for hirsute: I did a testbuild with repo-stamp enabled against the livecd-rootfs version from proposed (2.719.3). See - https://launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed/+build/308173 - https://launchpadlibrarian.net/567803112/buildlog_ubuntu_hirsute_amd64_amd64-tarball_proposed_BUILDING.txt.gz That looks good. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
I did a testbuild with repo-stamp enabled against the livecd-rootfs version from proposed (2.664.33). See - https://launchpadlibrarian.net/566970666/buildlog_ubuntu_focal_amd64_amd64-tarball_proposed_BUILDING.txt.gz - https://launchpad.net/~toabctl/+livefs/ubuntu/focal/proposed/+build/307101 That looks good. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944906] Re: MagicProxy broken when repo-snapshot-stamp is used
I did a testbuild with repo-stamp enabled against the livecd-rootfs version from proposed (2.664.33). See - https://launchpadlibrarian.net/566970666/buildlog_ubuntu_focal_amd64_amd64-tarball_proposed_BUILDING.txt.gz - https://launchpad.net/~toabctl/+livefs/ubuntu/focal/proposed/+build/307101 That looks good. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944906 Title: MagicProxy broken when repo-snapshot-stamp is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1944906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
Bionic is not affected ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948929] Re: Stop using apt-key - the tool is deprectated
** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948929 Title: Stop using apt-key - the tool is deprectated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1948929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948929] [NEW] Stop using apt-key - the tool is deprectated
Public bug reported: apt-key is deprectated and livecd-rootfs should stop using it. See https://manpages.ubuntu.com/manpages/impish/man8/apt-key.8.html And https://blog.jak-linux.org/2021/06/20/migrating-away-apt-key/ for a description how to do that. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948929 Title: Stop using apt-key - the tool is deprectated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1948929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/410823 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/410822 ** Changed in: livecd-rootfs (Ubuntu Hirsute) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Hirsute) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/410820 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
** Changed in: livecd-rootfs (Ubuntu Impish) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Impish) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
** Description changed:
- During an impish build of ubuntu-cpc images with magic-proxy enabled,
- the installation of certain packages tried to reach an internet endpoint
- (specifically http://169.254.169.254/latest/meta-data/instance-id -
- which appears to be used for EC2 metadata)
+ [Impact]
+ The fixes for this bug (including the fixes for LP:#1944906) need to be
backported to hirsute, focal and bionic) to be able to re-enable the
"repo-snapshot-stamp" feature for image builds. That feature is important to
get consistent image builds (means the same set of packages included in the
different images) when doing multiple builds (eg. for AWS, Azure and GCE).
+
+ [Test plan]
+ 1) sudo iptables -v -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
daemon -j REDIRECT --to 8080
+ 2) sudo ./magic-proxy --address="127.0.0.1" --port=8080 --run-as=daemon
--cutoff-time=1632467595 --setsid --log-file mp.log
+ 3) curl http://169.254.169.254/latest/meta-data/instance-id
+ (there should be no route to that host to trigger the error case, so don't do
that in an EC2 instance)
+ 4) sudo killall magic-proxy
+ 5) cat mp.log
+ 6) The problem "AttributeError: 'TimeoutError' object has no attribute
'replace'" should not be in the logfile
+
+ [Where problems could occur]
+ The codepath that will be changed is only executed in livecd-rootfs if the
repo-snapshot-stamp feature is enabled. AFAIK this is only enabled for CPC
builds so if there are problems, it will only affect CPC team builds. And
there, builds (at least for AWS) are currently broken anyway due to this bug.
+
+ [Original description]
+ During an impish build of ubuntu-cpc images with magic-proxy enabled, the
installation of certain packages tried to reach an internet endpoint
(specifically http://169.254.169.254/latest/meta-data/instance-id - which
appears to be used for EC2 metadata)
The magic-proxy log indicated :
10.10.10.2 - - [01/Oct/2021 13:21:26] urlopen() failed for
http://169.254.169.254/2009-04-04/meta-data/instance-id with [Errno 110]
Connection timed out
10.10.10.2 - - [01/Oct/2021 13:21:26] code 501, message [Errno 110]
Connection timed out
10.10.10.2 - - [01/Oct/2021 13:21:26] "GET /2009-04-04/meta-data/instance-id
HTTP/1.1" 501 -
Exception occurred during processing of request from ('10.10.10.2', 49672)
Traceback (most recent call last):
- File "/usr/lib/python3.9/urllib/request.py", line 1346, in do_open
- h.request(req.get_method(), req.selector, req.data, headers,
- File "/usr/lib/python3.9/http/client.py", line 1279, in request
- self._send_request(method, url, body, headers, encode_chunked)
- File "/usr/lib/python3.9/http/client.py", line 1325, in _send_request
- self.endheaders(body, encode_chunked=encode_chunked)
- File "/usr/lib/python3.9/http/client.py", line 1274, in endheaders
- self._send_output(message_body, encode_chunked=encode_chunked)
- File "/usr/lib/python3.9/http/client.py", line 1034, in _send_output
- self.send(msg)
- File "/usr/lib/python3.9/http/client.py", line 974, in send
- self.connect()
- File "/usr/lib/python3.9/http/client.py", line 945, in connect
- self.sock = self._create_connection(
- File "/usr/lib/python3.9/socket.py", line 844, in create_connection
- raise err
- File "/usr/lib/python3.9/socket.py", line 832, in create_connection
- sock.connect(sa)
+ File "/usr/lib/python3.9/urllib/request.py", line 1346, in do_open
+ h.request(req.get_method(), req.selector, req.data, headers,
+ File "/usr/lib/python3.9/http/client.py", line 1279, in request
+ self._send_request(method, url, body, headers, encode_chunked)
+ File "/usr/lib/python3.9/http/client.py", line 1325, in _send_request
+ self.endheaders(body, encode_chunked=encode_chunked)
+ File "/usr/lib/python3.9/http/client.py", line 1274, in endheaders
+ self._send_output(message_body, encode_chunked=encode_chunked)
+ File "/usr/lib/python3.9/http/client.py", line 1034, in _send_output
+ self.send(msg)
+ File "/usr/lib/python3.9/http/client.py", line 974, in send
+ self.connect()
+ File "/usr/lib/python3.9/http/client.py", line 945, in connect
+ self.sock = self._create_connection(
+ File "/usr/lib/python3.9/socket.py", line 844, in create_connection
+ raise err
+ File "/usr/lib/python3.9/socket.py", line 832, in create_connection
+ sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
- File "/usr/share/livecd-rootfs/magic-proxy", line 873, in __get_request
- with urllib.request.urlopen(
- File "/usr/lib/python3.9/urllib/request.py", line 214, in urlopen
- return opener.open(url, data, timeout)
- File "/usr/lib/python3.9/urllib/request.py", line 517, in open
- response = self._open(req, data)
- File
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
** Changed in: livecd-rootfs (Ubuntu) Assignee: Thomas Bechtold (toabctl) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
Note: given that the code is maintained in git, please merge https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd- rootfs-1/+merge/410585 when uploading the deb to the archive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
** Patch added: "debdiff to fix this bug" https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+attachment/5535828/+files/debdiff-lp1946520.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] Re: magic-proxy does not gracefully handle error conditions
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/410585 ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946520 Title: magic-proxy does not gracefully handle error conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1946520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943114] Re: changelogs of "native" packages are missing
** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943114 Title: changelogs of "native" packages are missing To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1943114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931841] Re: generic arm64 kernel can not boot initrdless and there is no -kvm kernel
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931841 Title: generic arm64 kernel can not boot initrdless and there is no -kvm kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
** Changed in: livecd-rootfs (Ubuntu Hirsute) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Focal) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Bionic) Assignee: (unassigned) => Thomas Bechtold (toabctl) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
** Description changed: - [Why SRU?] + [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. - [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
** Description changed: + [Why SRU?] + The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). + + [Test Plan] + - build a livecd-rootfs image with the changes for every series in a PPA + - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature + - Check that the build did not fail or hang + + [Where problems could occur] + The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. + + + [Original description] + when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944906] Re: MagicProxy broken when repo-snapshot-stamp is used
** Changed in: livecd-rootfs (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944906 Title: MagicProxy broken when repo-snapshot-stamp is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1944906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944906] Re: MagicProxy broken when repo-snapshot-stamp is used
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/409129 ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944906 Title: MagicProxy broken when repo-snapshot-stamp is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1944906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944906] [NEW] MagicProxy broken when repo-snapshot-stamp is used
Public bug reported:
The CPC team wants to reenable the repo-snapshot-stamp feature in magic proxy
to get similar package sets when building multiple images. But that is
currently broken.
When building in launchpad with something like:
RUN: /usr/share/launchpad-buildd/bin/in-target buildlivefs --backend=lxd
--series=impish --arch=arm64 LIVEFSBUILD-299827 --project ubuntu-cpc
--datestamp 20210924 --image-format ext4 --image-target disk-image
--image-target kvm --image-target qcow2 --image-target squashfs --image-
target tarball --image-target vagrant --image-target vmdk --image-target
azure --image-target azure-pro --image-target hyperv-gcs --image-target
wsl --repo-snapshot-stamp 1632467595 --cohort-key
MSAqIDE2MzI0Njc4OTcgMTVjNTk1ZWQ1NjFlMjM5OWEzNmQ5ZTE0MDlmZjlmMDdiOGNhM2JlMGI0N2UyMzBjZGVjMGUzOWEyNjk0NTA1Mw==
the build fails with:
REDIRECT tcp opt -- in * out * 0.0.0.0/0 -> 0.0.0.0/0 tcp dpt:80 ! owner
UID match 1 redir ports 8080
add password for /cloudware/cpc-livecd-rootfs/ubuntu
Ign:1 http://ftpmaster.internal/ubuntu impish InRelease
Ign:2 http://ftpmaster.internal/ubuntu impish-security InRelease
Ign:3 http://ftpmaster.internal/ubuntu impish-updates InRelease
Ign:4 http://private-ppa.buildd/cloudware/cpc-livecd-rootfs/ubuntu impish
InRelease
Ign:1 http://ftpmaster.internal/ubuntu impish InRelease
Ign:2 http://ftpmaster.internal/ubuntu impish-security InRelease
Ign:3 http://ftpmaster.internal/ubuntu impish-updates InRelease
Ign:4 http://private-ppa.buildd/cloudware/cpc-livecd-rootfs/ubuntu impish
InRelease
Ign:1 http://ftpmaster.internal/ubuntu impish InRelease
Ign:2 http://ftpmaster.internal/ubuntu impish-security InRelease
Ign:3 http://ftpmaster.internal/ubuntu impish-updates InRelease
Ign:4 http://private-ppa.buildd/cloudware/cpc-livecd-rootfs/ubuntu impish
InRelease
Err:1 http://ftpmaster.internal/ubuntu impish InRelease
Connection failed [IP: 10.189.129.95 80]
Err:2 http://ftpmaster.internal/ubuntu impish-security InRelease
Connection failed [IP: 10.189.129.95 80]
Err:3 http://ftpmaster.internal/ubuntu impish-updates InRelease
Connection failed [IP: 10.189.129.95 80]
Err:4 http://private-ppa.buildd/cloudware/cpc-livecd-rootfs/ubuntu impish
InRelease
Connection failed [IP: 91.189.95.85 80]
Reading package lists...
W: Failed to fetch
http://private-ppa.buildd/cloudware/cpc-livecd-rootfs/ubuntu/dists/impish/InRelease
Connection failed [IP: 91.189.95.85 80]
W: Failed to fetch http://ftpmaster.internal/ubuntu/dists/impish/InRelease
Connection failed [IP: 10.189.129.95 80]
W: Failed to fetch
http://ftpmaster.internal/ubuntu/dists/impish-security/InRelease Connection
failed [IP: 10.189.129.95 80]
W: Failed to fetch
http://ftpmaster.internal/ubuntu/dists/impish-updates/InRelease Connection
failed [IP: 10.189.129.95 80]
W: Some index files failed to download. They have been ignored, or old ones
used instead.
P: Setting up cleanup function
[2021-09-24 07:23:31] lb_bootstrap
P: Setting up cleanup function
[2021-09-24 07:23:31] lb_bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2021-09-24 07:23:31] lb_bootstrap_copy
[2021-09-24 07:23:32] lb_bootstrap_cdebootstrap
[2021-09-24 07:23:32] lb_bootstrap_debootstrap
P: Begin bootstrapping system...
[2021-09-24 07:23:32] lb_testroot
P: If the following stage fails, the most likely cause of the problem is with
your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)...
I: Retrieving InRelease
I: Retrieving Release
E: Failed getting release file
http://ftpmaster.internal/ubuntu/dists/impish/Release
P: Begin unmounting filesystems...
P: Saving caches...
= Magic proxy log (start) =
Exception occurred during processing of request from ('10.10.10.2', 39554)
Traceback (most recent call last):
File "/usr/lib/python3.9/socketserver.py", line 683, in process_request_thread
self.finish_request(request, client_address)
File "/usr/lib/python3.9/socketserver.py", line 360, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.9/socketserver.py", line 747, in __init__
self.handle()
File "/usr/lib/python3.9/http/server.py", line 427, in handle
self.handle_one_request()
File "/usr/lib/python3.9/http/server.py", line 415, in handle_one_request
method()
File "/usr/share/livecd-rootfs/magic-proxy", line 787, in do_GET
self.__get_request()
File "/usr/share/livecd-rootfs/magic-proxy", line 829, in __get_request
mirror = get_uri(parsed.hostname, m.group("base"))
File "/usr/share/livecd-rootfs/magic-proxy", line 84, in get_uri
return "http://; + host + path
TypeError: can only concatenate str (not "NoneType") to str
See attached build log (from
[Bug 1943114] Re: changelogs of "native" packages are missing
** Changed in: livecd-rootfs (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943114 Title: changelogs of "native" packages are missing To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1943114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943232] Re: Clicking on a link in a message does not switch the window to the browser
Note: this happens when I don't have the "Ubuntu Dock" and "Ubuntu AppIndicator" extensions enabled. I reenabled both and now it seems to work again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943232 Title: Clicking on a link in a message does not switch the window to the browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1943232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943234] [NEW] "ubuntu-bug thunderbird" produces a stackstrace: TypeError: expected string or bytes-like object
Public bug reported: $ ubuntu-bug thunderbird ERROR: hook /usr/share/apport/package-hooks/source_thunderbird.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_thunderbird.py", line 1386, in add_info if (profile.current or profile.default) and profile.addon_compat_check_disabled: File "/usr/share/apport/package-hooks/source_thunderbird.py", line 1227, in addon_compat_check_disabled is_nightly = re.sub(r'^[^\.]+\.[0-9]+([a-z0-9]*).*', r'\1', self.last_version) == 'a1' File "/usr/lib/python3.9/re.py", line 210, in sub return _compile(pattern, flags).sub(repl, string, count) TypeError: expected string or bytes-like object Note that this does open the window to send the data and it's possible to fill a bug, but it's not nice to get the stacktrace. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:78.13.0+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 BuildID: 20210802223056 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 09:33:35 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-12-08 (275 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=78.13.0/20210802223056 (In use) SourcePackage: thunderbird UpgradeStatus: Upgraded to impish on 2021-08-17 (23 days ago) ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943234 Title: "ubuntu-bug thunderbird" produces a stackstrace: TypeError: expected string or bytes-like object To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1943234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943232] [NEW] Clicking on a link in a message does not switch the window to the browser
Public bug reported: When I click on a link (http or https) in a Thunderbird message, the link gets opened in the browser (in my case google-chrome) but the window (google-chrome) is not focused. So I stay in thunderbird and I need to press 2x! ALT+Tab to get to the google-chrome window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:78.13.0+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 BuildID: 20210802223056 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 09:29:46 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-12-08 (275 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=78.13.0/20210802223056 (In use) SourcePackage: thunderbird UpgradeStatus: Upgraded to impish on 2021-08-17 (23 days ago) ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943232 Title: Clicking on a link in a message does not switch the window to the browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1943232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943114] Re: changelogs of "native" packages are missing
** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943114 Title: changelogs of "native" packages are missing To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1943114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943114] Re: changelogs of "native" packages are missing
** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943114 Title: changelogs of "native" packages are missing To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1943114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943049] Re: Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943049 Title: Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1943049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
I also have that problem now (hirsute, thunderbird version 1:78.11.0+build1-0ubuntu0.21.04.2). The docks shows 2 tabs on Thunderbird while only one is open. The most annoying part is that ALT-TAB window switching does not longer work then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931841] Re: generic arm64 kernel can not boot initrdless and there is no -kvm kernel
** Summary changed: - generic arm64 kernel can not boot initrdless + generic arm64 kernel can not boot initrdless and there is no -kvm kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931841 Title: generic arm64 kernel can not boot initrdless and there is no -kvm kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931841] [NEW] generic arm64 kernel can not boot initrdless
Public bug reported: The CPC team wants to build minimal arm64 images. Those images should boot initrdless (similar to the amd64 images where the -kvm kernel is used). But booting an initrdless image (build with livecd-rootfs) does fail with: $ sudo qemu-system-aarch64 -m 2G -M virt -cpu max -bios /usr/share /qemu-efi-aarch64/QEMU_EFI.fd -drive if=none,format=qcow2,file=livecd .ubuntu-cpc.img,id=hd0 -device virtio-blk-device,drive=hd0 -device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp:127.0.0.1:-:22 -nographic [snipped] [0.945928] VFS: Cannot open root device "PARTUUID=15058d73-bec1-4c7d-9cd7-f0f73f3ec694" or unknown-block(0,0): error -6 [0.946117] Please append a correct "root=" boot option; here are the available partitions: [0.947611] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.948139] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-74-generic #83-Ubuntu [0.948237] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 [0.948453] Call trace: [0.948736] dump_backtrace+0x0/0x190 [0.948864] show_stack+0x28/0x38 [0.948918] dump_stack+0xb4/0x10c [0.948974] panic+0x150/0x364 [0.949027] mount_block_root+0x248/0x304 [0.949090] mount_root+0x48/0x50 [0.949145] prepare_namespace+0x13c/0x1bc [0.949205] kernel_init_freeable+0x270/0x2c4 [0.949274] kernel_init+0x1c/0x114 [0.949336] ret_from_fork+0x10/0x18 [0.949913] Kernel Offset: disabled [0.950175] CPU features: 0x0952,20e0a230 [0.950251] Memory Limit: none [0.950595] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- The reason is, that the the virtio drivers are modules (CONFIG_VIRTIO_BLK=m) but for initrdless boot, they need to be compiled into the kernel. Expected behavior: Booting an arm64 image without an initrd does work in a virtualized environment similar to an amd64 image (that uses the -kvm kernel) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "boot.log" https://bugs.launchpad.net/bugs/1931841/+attachment/5504474/+files/boot.log ** Description changed: The CPC team wants to build minimal arm64 images. Those images should boot initrdless (similar to the amd64 images where the -kvm kernel is used). But booting an initrdless image (build with livecd-rootfs) does fail with: $ sudo qemu-system-aarch64 -m 2G -M virt -cpu max -bios /usr/share /qemu-efi-aarch64/QEMU_EFI.fd -drive if=none,format=qcow2,file=livecd .ubuntu-cpc.img,id=hd0 -device virtio-blk-device,drive=hd0 -device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp:127.0.0.1:-:22 -nographic [snipped] [0.945928] VFS: Cannot open root device "PARTUUID=15058d73-bec1-4c7d-9cd7-f0f73f3ec694" or unknown-block(0,0): error -6 [0.946117] Please append a correct "root=" boot option; here are the available partitions: [0.947611] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.948139] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-74-generic #83-Ubuntu [0.948237] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 [0.948453] Call trace: [0.948736] dump_backtrace+0x0/0x190 [0.948864] show_stack+0x28/0x38 [0.948918] dump_stack+0xb4/0x10c [0.948974] panic+0x150/0x364 [0.949027] mount_block_root+0x248/0x304 [0.949090] mount_root+0x48/0x50 [0.949145] prepare_namespace+0x13c/0x1bc [0.949205] kernel_init_freeable+0x270/0x2c4 [0.949274] kernel_init+0x1c/0x114 [0.949336] ret_from_fork+0x10/0x18 [0.949913] Kernel Offset: disabled [0.950175] CPU features: 0x0952,20e0a230 [0.950251] Memory Limit: none [0.950595] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- + The reason is, that the the virtio drivers are modules + (CONFIG_VIRTIO_BLK=m) but for initrdless boot, they need to be compiled + into the kernel. - The reason is, that the the virtio drivers are modules (CONFIG_VIRTIO_BLK=m) but for initrdless boot, they need to be compiled into the kernel. + + Expected behavior: + Booting an arm64 image without an initrd does work in a virtualized environment similar to an amd64 image (that uses the -kvm kernel) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931841 Title: generic arm64 kernel can not boot initrdless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931537] [NEW] Missing fuse deb package when trying to preseed snaps
Public bug reported: I tried to build an arm64 image on AWS (with ubuntu-bartender): ./scripts/ubuntu-bartender/ubuntu-bartender --no-cleanup --build- provider aws --aws-arm-build --aws-instance-type m6g.xlarge --hook- extras-dir ~/devel/canonical/cloudware/cpc_packaging.extra/ --livecd- rootfs-dir /home/tom/devel/livecd-rootfs/ -- --series focal --project ubuntu-cpc --minimized --image-target ec2 The build fails with: + snap_validate_seed /tmp/tmp.9FX9CNOMhi + local CHROOT_ROOT=/tmp/tmp.9FX9CNOMhi + '[' -e /tmp/tmp.9FX9CNOMhi/var/lib/snapd/seed/seed.yaml ']' + snap debug validate-seed /tmp/tmp.9FX9CNOMhi/var/lib/snapd/seed/seed.yaml ++ realpath /tmp/tmp.9FX9CNOMhi + /usr/lib/snapd/snap-preseed --reset /tmp/tmp.9FX9CNOMhi ++ realpath /tmp/tmp.9FX9CNOMhi + /usr/lib/snapd/snap-preseed /tmp/tmp.9FX9CNOMhi error: cannot mount /var/lib/snapd/seed/snaps/snapd_11843.snap at /tmp/snapd-preseed in preseed mode: exit status 32 So snap-preseed can't mount the snap. Trying to do that manually (from within the chroot) also fails: # mount -t fuse.snapfuse -o ro,x-gdu.hide,x-gvfs-hide /var/lib/snapd/seed/snaps/snapd_11843.snap /mnt mount: /mnt: wrong fs type, bad option, bad superblock on /var/lib/snapd/seed/snaps/snapd_11843.snap, missing codepage or helper program, or other error. The reason is, that the fuse .deb package is not installed. Installing that package into the chroot solves the problem. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931537 Title: Missing fuse deb package when trying to preseed snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1931537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930686] Re: Do not include /dev device node filles in OCI rootfs tarballs
I did the following tests 1) build (with proposed enabled) a livefs with launchpad here: https://code.launchpad.net/~toabctl/+livefs/ubuntu/bionic/proposed/+build/280226 the build passed and the build log shows that livecd-rootfs 2.525.55 (from proposed) is used. 2) Downloaded the tarball from launchpad and build a docker image and run a command $ cat << EOF > Dockerfile FROM scratch ADD bionic-minimal-cloudimg-amd64-root.tar.gz / CMD ["/bin/bash"] EOF $ docker build . Sending build context to Docker daemon 26.08MB Step 1/3 : FROM scratch ---> Step 2/3 : ADD bionic-minimal-cloudimg-amd64-root.tar.gz / ---> 52dfeec884c4 Step 3/3 : CMD ["/bin/bash"] ---> Running in abd576998a3e Removing intermediate container abd576998a3e ---> 0f0bc046d3ad Successfully built 0f0bc046d3ad $ docker run -it 0f0bc046d3ad uname -a Linux 0ff4969cb51f 5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 3) checked the size of the tarball (26077806). Looks good 4) check for device node files: $ tar tfz bionic-minimal-cloudimg-amd64-root.tar.gz |grep ^dev dev/ Looks good. So all tests passed and this can be moved to updates. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930686 Title: Do not include /dev device node filles in OCI rootfs tarballs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1930686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915571] Re: Cannot start bash session for buildd vm images in LXD vm
@Brian, thanks! Both tests pass now. Can you move livecd-rootfs for bionic from proposed to updates please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915571 Title: Cannot start bash session for buildd vm images in LXD vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1915571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930686] Re: Do not include /dev device node filles in OCI rootfs tarballs
** Changed in: livecd-rootfs (Ubuntu) Status: In Progress => New ** Description changed: [Impact] + + Note: this only affects bionic - all other release don't have this + problem. Currently, the official Ubuntu docker images are based on the core rootfs tarballs from https://partner-images.canonical.com/core/ . We want to switch to the newly created OCI tarballs from (https://partner-images.canonical.com/oci). See also LP:#1926732 for details about the OCI rootfs tarballs. While trying to switch the official ubuntu docker images on dockerhub to the newly created OCI rootfs tarballs, it poped up that for the bionic containers, there are device node entries in the rootfs (/dev files). The diff (see https://github.com/docker-library/official- images/pull/10287) looks like: - --- a/ubuntu_bionic/ubuntu-bionic-core-cloudimg-amd64-root.tar.gz 'tar -t' - +++ b/ubuntu_bionic/ubuntu-bionic-oci-amd64-root.tar.gz 'tar -t' + --- a/ubuntu_bionic/ubuntu-bionic-core-cloudimg-amd64-root.tar.gz 'tar -t' + +++ b/ubuntu_bionic/ubuntu-bionic-oci-amd64-root.tar.gz 'tar -t' @@ -86,6 +86,19 @@ bin/zmore - bin/znew - boot/ - dev/ + bin/znew + boot/ + dev/ +dev/fd +dev/full +dev/null +dev/ptmx +dev/pts/ +dev/random +dev/shm/ +dev/stderr +dev/stdin +dev/stdout +dev/tty +dev/urandom +dev/zero - - This causes problems (see https://github.com/tianon/docker-brew-ubuntu-core/issues/62 ) and would be a regression when switching from the core rootfs tarballs to the oci rootfs tarball. + This causes problems (see https://github.com/tianon/docker-brew-ubuntu- + core/issues/62 ) and would be a regression when switching from the core + rootfs tarballs to the oci rootfs tarball. Expected is that there are not /dev files in the rootfs tarball. [Test Plan] 1) build ubuntu-oci project with launchpad 2) do some basic tests with the rootfs tarball: cat << EOF > Dockerfile FROM scratch ADD hirsute-minimal-cloudimg-amd64-root.tar.gz / CMD ["/bin/bash"] EOF $ docker build . docker run -it $image-id uname -a 3) check the tarball size (should not change significantly) 4) check that there are not /dev files in the tarball - [Where problems could occur] This change could break other livecd-rootfs projects which might lead to failed builds. But beside that, there is nothing I can think of that would be affected by this change. And it's very unlikely to break other livecd-rootfs builds. [Other Info] None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930686 Title: Do not include /dev device node filles in OCI rootfs tarballs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1930686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930686] Re: Do not include /dev device node filles in OCI rootfs tarballs
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/403662 ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930686 Title: Do not include /dev device node filles in OCI rootfs tarballs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1930686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930686] [NEW] Do not include /dev device node filles in OCI rootfs tarballs
Public bug reported:
[Impact]
Currently, the official Ubuntu docker images are based on the core rootfs
tarballs from https://partner-images.canonical.com/core/ .
We want to switch to the newly created OCI tarballs from
(https://partner-images.canonical.com/oci). See also LP:#1926732 for details
about the OCI rootfs tarballs.
While trying to switch the official ubuntu docker images on dockerhub to
the newly created OCI rootfs tarballs, it poped up that for the bionic
containers, there are device node entries in the rootfs (/dev files).
The diff (see https://github.com/docker-library/official-
images/pull/10287) looks like:
--- a/ubuntu_bionic/ubuntu-bionic-core-cloudimg-amd64-root.tar.gz 'tar -t'
+++ b/ubuntu_bionic/ubuntu-bionic-oci-amd64-root.tar.gz 'tar -t'
@@ -86,6 +86,19 @@ bin/zmore
bin/znew
boot/
dev/
+dev/fd
+dev/full
+dev/null
+dev/ptmx
+dev/pts/
+dev/random
+dev/shm/
+dev/stderr
+dev/stdin
+dev/stdout
+dev/tty
+dev/urandom
+dev/zero
This causes problems (see
https://github.com/tianon/docker-brew-ubuntu-core/issues/62 ) and would be a
regression when switching from the core rootfs tarballs to the oci rootfs
tarball.
Expected is that there are not /dev files in the rootfs tarball.
[Test Plan]
1) build ubuntu-oci project with launchpad
2) do some basic tests with the rootfs tarball:
cat << EOF > Dockerfile
FROM scratch
ADD hirsute-minimal-cloudimg-amd64-root.tar.gz /
CMD ["/bin/bash"]
EOF
$ docker build .
docker run -it $image-id uname -a
3) check the tarball size (should not change significantly)
4) check that there are not /dev files in the tarball
[Where problems could occur]
This change could break other livecd-rootfs projects which might lead to failed
builds. But beside that, there is nothing I can think of that would be affected
by this change. And it's very unlikely to break other livecd-rootfs builds.
[Other Info]
None
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Assignee: Thomas Bechtold (toabctl)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930686
Title:
Do not include /dev device node filles in OCI rootfs tarballs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1930686/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
bionic verification successful. I changed the testing plan given that using the package from proposed with ubuntu-old-fashioned is not that easy. I did now use launchpad itself to build (see https://code.launchpad.net/~toabctl/+livefs/ubuntu/bionic/proposed): - bionic ubuntu-oci build: https://code.launchpad.net/~toabctl/+livefs/ubuntu/bionic/proposed/+build/275398/+files/buildlog_ubuntu_bionic_amd64_amd64-minimized-all_proposed_BUILDING.txt.gz - bionic ubuntu-base build: https://code.launchpad.net/~toabctl/+livefs/ubuntu/bionic/proposed/+build/275412/+files/buildlog_ubuntu_bionic_amd64_amd64-minimized-all_proposed_BUILDING.txt.gz Testing the docker container tarball: $ cat << EOF > Dockerfile FROM scratch ADD bionic-minimal-cloudimg-amd64-root.tar.gz / CMD ["/bin/bash"] EOF $ docker build . Sending build context to Docker daemon 26.05MB Step 1/3 : FROM scratch ---> Step 2/3 : ADD bionic-minimal-cloudimg-amd64-root.tar.gz / ---> 77389ea55ba2 Step 3/3 : CMD ["/bin/bash"] ---> Running in ed79500badff Removing intermediate container ed79500badff ---> 5cd1b3e0d127 Successfully built 5cd1b3e0d127 $ docker run -it 5cd1b3e0d127 uname -a Linux b4ecacff15c4 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Size of bionic-minimal-cloudimg-amd64-root.tar.gz is 26047357 which is good. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Thomas Bechtold (toabctl) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
focal verification successful. I changed the testing plan given that using the package from proposed with ubuntu-old-fashioned is not that easy. I did now use launchpad itself to build (see https://code.launchpad.net/~toabctl/+livefs/ubuntu/focal/proposed): - focal ubuntu-oci build: https://code.launchpad.net/~toabctl/+livefs/ubuntu/focal/proposed/+build/274969/+files/buildlog_ubuntu_focal_amd64_amd64-minimized-all_proposed_BUILDING.txt.gz - focal ubuntu-base build: https://code.launchpad.net/~toabctl/+livefs/ubuntu/focal/proposed/+build/274966/+files/buildlog_ubuntu_focal_amd64_amd64-minimized-all_proposed_BUILDING.txt.gz Testing the docker container tarball: $ cat << EOF > Dockerfile FROM scratch ADD focal-minimal-cloudimg-amd64-root.tar.gz / CMD ["/bin/bash"] EOF $ docker build . Sending build context to Docker daemon 27.73MB Step 1/3 : FROM scratch ---> Step 2/3 : ADD focal-minimal-cloudimg-amd64-root.tar.gz / ---> ec62f2828d83 Step 3/3 : CMD ["/bin/bash"] ---> Running in 9b9bdbbe6cf9 Removing intermediate container 9b9bdbbe6cf9 ---> 2f88a0922525 Successfully built 2f88a0922525 $ docker run -it 2f88a0922525 uname -a Linux 1086ac358e49 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Size of focal-minimal-cloudimg-amd64-root.tar.gz is 27730133 which is good. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
groovy verification successful. I changed the testing plan given that using the package from proposed with ubuntu-old-fashioned is not that easy. I did now use launchpad itself to build (see https://code.launchpad.net/~toabctl/+livefs/ubuntu/groovy/proposed): - hirsute ubuntu-oci build: https://launchpadlibrarian.net/538319776/buildlog_ubuntu_groovy_amd64_amd64-minimized-all_proposed_BUILDING.txt.gz - hirsute ubuntu-base build: https://launchpadlibrarian.net/538330773/buildlog_ubuntu_groovy_amd64_amd64-minimized-all_proposed_BUILDING.txt.gz Testing the docker container tarball: $ cat << EOF > Dockerfile FROM scratch ADD groovy-minimal-cloudimg-amd64-root.tar.gz / CMD ["/bin/bash"] EOF $ docker build . Sending build context to Docker daemon 87.33MB Step 1/3 : FROM scratch ---> Step 2/3 : ADD groovy-minimal-cloudimg-amd64-root.tar.gz / ---> e188f5d7b5cf Step 3/3 : CMD ["/bin/bash"] ---> Running in 739610b46528 Removing intermediate container 739610b46528 ---> 564bda04f793 Successfully built 564bda04f793 $ docker run -it 564bda04f793 uname -a Linux a7ca765289f1 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Size of groovy-minimal-cloudimg-amd64-root.tar.gz is 30441216 which is good. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
hirsute verification successful. I changed the testing plan given that using the package from proposed with ubuntu-old-fashioned is not that easy. I did now use launchpad itself to build (see https://code.launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed): - hirsute ubuntu-oci build: https://launchpadlibrarian.net/538316605/buildlog_ubuntu_hirsute_amd64_amd64-minimized-all_proposed_BUILDING.txt.gz - hirsute ubuntu-base build: https://launchpadlibrarian.net/538319522/buildlog_ubuntu_hirsute_amd64_amd64-minimized-all_proposed_BUILDING.txt.gz Testing the docker container tarball: $ cat << EOF > Dockerfile FROM scratch ADD hirsute-minimal-cloudimg-amd64-root.tar.gz / CMD ["/bin/bash"] EOF $ docker build . Sending build context to Docker daemon 87.33MB Step 1/3 : FROM scratch ---> Step 2/3 : ADD hirsute-minimal-cloudimg-amd64-root.tar.gz / ---> ba9d835e917e Step 3/3 : CMD ["/bin/bash"] ---> Running in ca61b1822d7e Removing intermediate container ca61b1822d7e ---> 62da9ad33be3 Successfully built 62da9ad33be3 $ docker run -it 62da9ad33be3 uname -a Linux 2a455f31570a 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Size of hirsute-minimal-cloudimg-amd64-root.tar.gz is 28449136 which is good. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
** Description changed: [Impact] Currently the ubuntu-base livecd-rootfs project is used to build tarballs that are the base for building docker/OCI images. The tarballs produced with the ubuntu-base project are modified externally (see https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh ) to create the "official" ubuntu images on dockerhub. When including the ubuntu-oci project into livecd-rootfs, we can build tarballs that already contain the changes that are currently done externally. This has multiple advantages: 1) a Dockerfile using that tarball would no longer have to modify anything (means less layers) 2) publishing new OCI images no longer depends on the external dockerhub image creation. Currently eg. the AWS ECR ubuntu containers depend on the containers from dockerhub. That would be no longer the case with this change 3) Possible faster reaction on CVEs. no longer depending on external processes. [Test Plan] 1) build ubuntu-oci project a) Build a test ubuntu-oci tarball with ubuntu-old-fashioned: ./scripts/ubuntu-bartender/ubuntu-bartender --no-cleanup -- --series impish --image-format plain --project ubuntu-oci --subproject minimized b) create a Dockerfile using the tarball created in step 1): cat << EOF > Dockerfile FROM scratch ADD ubuntu-impish-oci-cloudimg-amd64-root.tar.gz / CMD ["/bin/bash"] EOF c) build the container docker build . d) run something in the container: docker run -it $container-id uname -a e) check the size of the docker image and compare with the image for the same series available on dockerhub 2) build another project (ubuntu-base minimized) - a) Build a test ubuntu-base minimized project with ubuntu-old-fashioned - b) Start the build + a) Build a test ubuntu-base minimized project with ubuntu-old-fashioned to make sure the build does not break + [Where problems could occur] This change could break other livecd-rootfs projects which might lead to failed builds. But beside that, there is nothing I can think of that would be affected by this change. [Other Info] When this is accepted, there will be livefs builds available at https://launchpad.net/~cloud-images-release- managers/+livefs/ubuntu/$SERIES/ubuntu-oci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
** Description changed: [Impact] Currently the ubuntu-base livecd-rootfs project is used to build tarballs that are the base for building docker/OCI images. The tarballs produced with the ubuntu-base project are modified externally (see https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh ) to create the "official" ubuntu images on dockerhub. When including the ubuntu-oci project into livecd-rootfs, we can build tarballs that already contain the changes that are currently done externally. This has multiple advantages: 1) a Dockerfile using that tarball would no longer have to modify anything (means less layers) 2) publishing new OCI images no longer depends on the external dockerhub image creation. Currently eg. the AWS ECR ubuntu containers depend on the containers from dockerhub. That would be no longer the case with this change 3) Possible faster reaction on CVEs. no longer depending on external processes. [Test Plan] 1) build ubuntu-oci project a) Build a test ubuntu-oci tarball with ubuntu-old-fashioned: ./scripts/ubuntu-bartender/ubuntu-bartender --no-cleanup -- --series impish --image-format plain --project ubuntu-oci --subproject minimized b) create a Dockerfile using the tarball created in step 1): cat << EOF > Dockerfile FROM scratch ADD ubuntu-impish-oci-cloudimg-amd64-root.tar.gz / CMD ["/bin/bash"] EOF c) build the container docker build . d) run something in the container: docker run -it $container-id uname -a e) check the size of the docker image and compare with the image for the same series available on dockerhub 2) build another project (ubuntu-base minimized) - TODO: describe test steps + a) Build a test ubuntu-base minimized project with ubuntu-old-fashioned + b) Start the build [Where problems could occur] This change could break other livecd-rootfs projects which might lead to failed builds. But beside that, there is nothing I can think of that would be affected by this change. [Other Info] When this is accepted, there will be livefs builds available at https://launchpad.net/~cloud-images-release- managers/+livefs/ubuntu/$SERIES/ubuntu-oci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
** Changed in: livecd-rootfs (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: livecd-rootfs (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: livecd-rootfs (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: livecd-rootfs (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: livecd-rootfs (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
** Description changed: [Impact] Currently the ubuntu-base livecd-rootfs project is used to build tarballs that are the base for building docker/OCI images. The tarballs produced with the ubuntu-base project are modified externally (see https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh ) to create the "official" ubuntu images on dockerhub. When including the ubuntu-oci project into livecd-rootfs, we can build tarballs that already contain the changes that are currently done externally. This has multiple advantages: 1) a Dockerfile using that tarball would no longer have to modify anything (means less layers) 2) publishing new OCI images no longer depends on the external dockerhub image creation. Currently eg. the AWS ECR ubuntu containers depend on the containers from dockerhub. That would be no longer the case with this change 3) Possible faster reaction on CVEs. no longer depending on external processes. [Test Plan] - 1) Build a test ubuntu-oci tarball with ubuntu-old-fashioned: + 1) build ubuntu-oci project + a) Build a test ubuntu-oci tarball with ubuntu-old-fashioned: ./scripts/ubuntu-bartender/ubuntu-bartender --no-cleanup -- --series impish --image-format plain --project ubuntu-oci --subproject minimized - 2) create a Dockerfile using the tarball created in step 1): + b) create a Dockerfile using the tarball created in step 1): cat << EOF > Dockerfile FROM scratch ADD ubuntu-impish-oci-cloudimg-amd64-root.tar.gz / CMD ["/bin/bash"] EOF - 3) build the container + c) build the container docker build . - 4) run something in the container: + d) run something in the container: docker run -it $container-id uname -a - 5) check the size of the docker image and compare with the image for the + e) check the size of the docker image and compare with the image for the same series available on dockerhub + 2) build another project (ubuntu-base minimized) + TODO: describe test steps [Where problems could occur] This change could break other livecd-rootfs projects which might lead to failed builds. But beside that, there is nothing I can think of that would be affected by this change. [Other Info] When this is accepted, there will be livefs builds available at https://launchpad.net/~cloud-images-release- managers/+livefs/ubuntu/$SERIES/ubuntu-oci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/402072 ** Changed in: livecd-rootfs (Ubuntu Focal) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Focal) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Bionic) Assignee: (unassigned) => Thomas Bechtold (toabctl) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
** Changed in: livecd-rootfs (Ubuntu Hirsute) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Hirsute) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Groovy) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Groovy) Assignee: (unassigned) => Thomas Bechtold (toabctl) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/402071 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/402070 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] Re: Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
** Merge proposal linked: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd-rootfs-1/+merge/402067 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926732] [NEW] Add ubuntu-oci project for building OCI-ready tarballs with livecd-rootfs
Public bug reported: [Impact] Currently the ubuntu-base livecd-rootfs project is used to build tarballs that are the base for building docker/OCI images. The tarballs produced with the ubuntu-base project are modified externally (see https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh ) to create the "official" ubuntu images on dockerhub. When including the ubuntu-oci project into livecd-rootfs, we can build tarballs that already contain the changes that are currently done externally. This has multiple advantages: 1) a Dockerfile using that tarball would no longer have to modify anything (means less layers) 2) publishing new OCI images no longer depends on the external dockerhub image creation. Currently eg. the AWS ECR ubuntu containers depend on the containers from dockerhub. That would be no longer the case with this change 3) Possible faster reaction on CVEs. no longer depending on external processes. [Test Plan] 1) Build a test ubuntu-oci tarball with ubuntu-old-fashioned: ./scripts/ubuntu-bartender/ubuntu-bartender --no-cleanup -- --series impish --image-format plain --project ubuntu-oci --subproject minimized 2) create a Dockerfile using the tarball created in step 1): cat << EOF > Dockerfile FROM scratch ADD ubuntu-impish-oci-cloudimg-amd64-root.tar.gz / CMD ["/bin/bash"] EOF 3) build the container docker build . 4) run something in the container: docker run -it $container-id uname -a 5) check the size of the docker image and compare with the image for the same series available on dockerhub [Where problems could occur] This change could break other livecd-rootfs projects which might lead to failed builds. But beside that, there is nothing I can think of that would be affected by this change. [Other Info] When this is accepted, there will be livefs builds available at https://launchpad.net/~cloud-images-release- managers/+livefs/ubuntu/$SERIES/ubuntu-oci ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926732 Title: Add ubuntu-oci project for building OCI-ready tarballs with livecd- rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1926732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923542] [NEW] "Failed to restart network-manager.service: Unit network-manager.service not found." during package update
Public bug reported: I updated network-manger on hirsute: network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) over (1.30.0-1ubuntu2) During the postinst run, I get: Setting up network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) ... Failed to restart network-manager.service: Unit network-manager.service not found. invoke-rc.d: initscript network-manager, action "force-reload" failed. The reason seems to be that there is no network-manager.service . it's called NetworkManager.service . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 13 06:15:31 2021 InstallationDate: Installed on 2020-12-08 (125 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: network-manager SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2020-12-09 (124 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923542 Title: "Failed to restart network-manager.service: Unit network- manager.service not found." during package update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1923542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923541] [NEW] /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'
Public bug reported: Currently running 21.04, apport version is 2.20.11-0ubuntu62 . When I try to fill a bug, I see: $ ubuntu-bug network-manager ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1002, in attach_casper_md5check del report['CasperMD5json'] File "/usr/lib/python3.9/collections/__init__.py", line 1064, in __delitem__ del self.data[key] KeyError: 'CasperMD5json' It's not crashing the bug reporting itself, but it looks wrong to have a stacktrace on the command line. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923541 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1923541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919968] [NEW] ModuleNotFoundError: No module named 'fido2._pyu2f'
Public bug reported: When starting solo, I get: $ solo Traceback (most recent call last): File "/usr/bin/solo", line 5, in from solo.cli import solo_cli File "/usr/lib/python3/dist-packages/solo/cli/__init__.py", line 17, in from solo.cli.key import key File "/usr/lib/python3/dist-packages/solo/cli/key.py", line 24, in import solo.fido2 File "/usr/lib/python3/dist-packages/solo/fido2/__init__.py", line 3, in import fido2._pyu2f ModuleNotFoundError: No module named 'fido2._pyu2f' Looks like the python3-fido2 package has a to new version (see https://github.com/solokeys/solo-python/blob/main/pyproject.toml#L17 ) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: solo-python 0.0.27-2 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 18 08:51:48 2021 InstallationDate: Installed on 2020-12-08 (99 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: solo-python UpgradeStatus: Upgraded to hirsute on 2020-12-09 (98 days ago) ** Affects: solo-python (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919968 Title: ModuleNotFoundError: No module named 'fido2._pyu2f' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/solo-python/+bug/1919968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918412] [NEW] gnome-shell crashed
Public bug reported: Not sure what I actually did. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 09:03:49 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-08 (91 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-09 (90 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918412 Title: gnome-shell crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915579] Re: lvm2 version 2.03.11-2ubuntu1 breaks initramfs
I also have this problem (with a LUKS & LVM). As a workaround, I did: 1) boot into live CD, start a terminal and do everything as root (sudo -i) 2) open the encrypted LUKS partition: cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt Note that the name (in my case "nvme0n1p3_crypt") must match the name that is in the etc/crypttab . Otherwise the later generated initramfs will not work correctly. 3) vgscan && vgchange -ay vgubuntu 4) mount /dev/vgubuntu/root /mnt 5) mount /dev/nvme0n1p2 /mnt/boot# this is my /boot partition 6) mount --bind /dev /mnt/dev && mount --bind /sys /mnt/sys && mount --bind /proc /mnt/proc 7) chroot /mnt 8) chmod 755 /usr/share/initramfs-tools/hooks/lvm2 9) update-initramfs -u -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915579 Title: lvm2 version 2.03.11-2ubuntu1 breaks initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1915579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916120] Re: Can not install podman and buildah together
Installation works now. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916120 Title: Can not install podman and buildah together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1916120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916120] [NEW] Can not install podman and buildah together
Public bug reported: I tried to install podman and buildah together. I have now podman installed: $ dpkg -l podman [...] ii podman 2.1.1+dfsg1-4ubuntu3 amd64 Now I try to install buildah and with that, podman will be removed: $ sudo apt install buildah [...] Suggested packages: containers-storage The following packages will be REMOVED: golang-github-containers-common podman The following NEW packages will be installed: buildah 0 upgraded, 1 newly installed, 2 to remove and 0 not upgraded. Need to get 5.736 kB of archives. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: podman 2.1.1+dfsg1-4ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 19 08:37:18 2021 InstallationDate: Installed on 2020-12-08 (72 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: libpod UpgradeStatus: Upgraded to hirsute on 2020-12-09 (71 days ago) ** Affects: libpod (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916120 Title: Can not install podman and buildah together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/1916120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638306] Re: [SRU] zypper binary shipped w/ Ubuntu Xenial requires rebuild (relocation error)
** Patch added: "zypper-rebuild.patch" https://bugs.launchpad.net/ubuntu/+source/zypper/+bug/1638306/+attachment/4822821/+files/zypper-rebuild.patch ** Patch removed: "zypper-rebuild.patch" https://bugs.launchpad.net/ubuntu/+source/zypper/+bug/1638306/+attachment/4822820/+files/zypper-rebuild.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638306 Title: [SRU] zypper binary shipped w/ Ubuntu Xenial requires rebuild (relocation error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zypper/+bug/1638306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638306] Re: zypper binary shipped w/ Ubuntu Xenial requires rebuild (relocation error)
** Patch added: "zypper-rebuild.patch" https://bugs.launchpad.net/ubuntu/+source/zypper/+bug/1638306/+attachment/4822820/+files/zypper-rebuild.patch ** Summary changed: - zypper binary shipped w/ Ubuntu Xenial requires rebuild (relocation error) + [SRU] zypper binary shipped w/ Ubuntu Xenial requires rebuild (relocation error) ** Description changed: - 1) The release of Ubuntu you are using: - $ lsb_release -rd - Description:Ubuntu 16.04.1 LTS - Release:16.04 - - 2) The version of the package you are using: - $ apt-cache policy zypper - zypper: - Installiert: 1.12.4-1 - Installationskandidat: 1.12.4-1 - Versionstabelle: - *** 1.12.4-1 500 - 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages - 100 /var/lib/dpkg/status - $ - $ dpkg --list|grep zyp|sed -e 's| a.*|[...]|g' - ii libzypp:amd64 15.3.0-1build1[...] - ii libzypp-bin 15.3.0-1build1[...] - ii libzypp-common 15.3.0-1build1[...] - ii libzypp-config 15.3.0-1build1[...] - ii zypper 1.12.4-1 [...] - ii zypper-common 1.12.4-1 [...] - - 3) What you expected to happen: zypper binary can be executed - - 4) What happened instead: zypper binary cannot be executed due to relocation error: + [IMPACT] + zypper is not usable at all. $ zypper -V zypper: relocation error: zypper: symbol _ZN4zypp5CpeId11NoThrowType13lastMalformedE, version ZYPP_plain not defined in file libzypp.so.1503 with link time reference - (Problem has been solved locally by rebuilding the package in question.) + [TEST CASE] + * run: zypper -V + + [Regression Potential] + None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638306 Title: [SRU] zypper binary shipped w/ Ubuntu Xenial requires rebuild (relocation error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zypper/+bug/1638306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546116] Re: manila share process init script is missing
Hm. Confusing that Ubuntu packaging is mixed with manila upstream bugs... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546116 Title: manila share process init script is missing To manage notifications about this bug go to: https://bugs.launchpad.net/manila/+bug/1546116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469593] Re: Update to 0.3.10
@Sebastian: Can you post a screenshot what the issue is? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1469593 Title: Update to 0.3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-feet/+bug/1469593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311497] Re: Restore function of generated snapshots does not work
Tested with 4.8.2-1ubuntu0.1. Works fine. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311497 Title: Restore function of generated snapshots does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1311497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311497] [NEW] Restore function of generated snapshots does not work
Public bug reported: reprepro can generate snapshots of distributions. But the restore of a snapshot does not work. Steps to reproduce the problem in a clean directory: 1) mkdir conf/ 2) cat conf/distributions EOF Codename: testcode Description: testdesc Architectures: amd64 source Components: main Contents: .gz EOF 3) reprepro includedeb testcode hello-debhelper_2.7-2_amd64.deb #Include a deb 4) reprepro gensnapshot testcode mysnapshot # generates a snapshot under dists/testcode/snashot 5) reprepro includedeb testcode hello-debhelper_2.7-2dtag1_amd64.deb #Include another deb (this is just another rebuild with a different version number) 6) restore testcode mysnapshot hello-debhelper #should restore the package but nothing happens The last step should restore the package but that does not work. The fix for that can be found upstream: http://anonscm.debian.org/gitweb/?p=mirrorer/reprepro.git;a=commitdiff;h=38bdd869f617e8872e3194501bd79e3ecc94e425 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: reprepro 4.8.2-1build1 Uname: Linux 3.13-1-amd64 x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Apr 23 07:00:16 2014 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) SHELL=/bin/bash SourcePackage: reprepro UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: reprepro (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311497 Title: Restore function of generated snapshots does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1311497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311497] Re: Restore function of generated snapshots does not work
** Patch added: LP1311497.debdiff https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1311497/+attachment/4093794/+files/LP1311497.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311497 Title: Restore function of generated snapshots does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1311497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311497] Re: Restore function of generated snapshots does not work
** Attachment removed: NonfreeKernelModules.txt https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1311497/+attachment/4093777/+files/NonfreeKernelModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311497 Title: Restore function of generated snapshots does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1311497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
