[Touch-packages] [Bug 1890892] Re: WSL openssh-server incorrect permissions .ssh
I cannot reproduce this issue. These are the steps I used to attempt to reproduce: 1. Installed Ubuntu 18.04 from the Microsoft Store. 2. Created a new user on launch. 3. Confirmed openssh-server was installed. 4. Confirmed no .ssh folder existed in ~. 5. Ran $ ssh-keygen -t rsa -b 4096 to create keys. 6. Reviewed permissions of the resulting .ssh folder, which are 700, private key 600, and public key 644. I suspect that something else may have modified the permissions on ~/.ssh. We do not modify permissions on openssh for WSL anywhere in the image build or Windows unpacking process, it will have the default permissions from the openssh-server package. ** Attachment added: "Console log of attempt to reproduce" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1890892/+attachment/5400546/+files/duplication-log.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1890892 Title: WSL openssh-server incorrect permissions .ssh Status in openssh package in Ubuntu: Incomplete Bug description: Using Ubuntu Windows Subsystem for Linux (WSL) $ uname -srvmpio Linux 4.4.0-19041-Microsoft #1-Microsoft Fri Dec 06 14:06:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux (Prestep required to add port for access to windows firewall) .ssh directory was set as 777 when 755 (minimum) is required for operation of authentication keys when trying to ssh -i /path-to-key/key user@domain. Generally poor housekeeping. <3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Microsoft 4.4.0-19041.1-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Aug 8 08:44:02 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 127: Error getting authority: Error initializing authority: Could not connect: No such file or directory SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1890892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872824] [NEW] Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package
Public bug reported: Upgrade path from 16.04 to 20.04 fails. console-setup-linux_1.194ubuntu3_all.deb tries to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5. I have reproduced this bug on bare metal and WSL. Log: Unpacking console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5) ... dpkg: error processing archive /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb (--unpack): trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../keyboard-configuration_1.194ubuntu3_all.deb ... Unpacking keyboard-configuration (1.194ubuntu3) over (1.108ubuntu15.5) ... Preparing to unpack .../busybox-initramfs_1%3a1.30.1-4ubuntu6_amd64.deb ... Unpacking busybox-initramfs (1:1.30.1-4ubuntu6) over (1:1.22.0-15ubuntu1.4) ... Preparing to unpack .../initramfs-tools-bin_0.136ubuntu6_amd64.deb ... Unpacking initramfs-tools-bin (0.136ubuntu6) over (0.122ubuntu8.16) ... Preparing to unpack .../cpio_2.13+dfsg-2_amd64.deb ... Unpacking cpio (2.13+dfsg-2) over (2.11+dfsg-5ubuntu1.1) ... Preparing to unpack .../liblz4-1_1.9.2-2_amd64.deb ... Unpacking liblz4-1:amd64 (1.9.2-2) over (0.0~r131-2ubuntu2) ... Processing triggers for libc-bin (2.31-0ubuntu7) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.27) ... Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1872824 Title: Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console- setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 Status in console-setup package in Ubuntu: New Bug description: Upgrade path from 16.04 to 20.04 fails. console-setup-linux_1.194ubuntu3_all.deb tries to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5. I have reproduced this bug on bare metal and WSL. Log: Unpacking console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5) ... dpkg: error processing archive /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb (--unpack): trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../keyboard-configuration_1.194ubuntu3_all.deb ... Unpacking keyboard-configuration (1.194ubuntu3) over (1.108ubuntu15.5) ... Preparing to unpack .../busybox-initramfs_1%3a1.30.1-4ubuntu6_amd64.deb ... Unpacking busybox-initramfs (1:1.30.1-4ubuntu6) over (1:1.22.0-15ubuntu1.4) ... Preparing to unpack .../initramfs-tools-bin_0.136ubuntu6_amd64.deb ... Unpacking initramfs-tools-bin (0.136ubuntu6) over (0.122ubuntu8.16) ... Preparing to unpack .../cpio_2.13+dfsg-2_amd64.deb ... Unpacking cpio (2.13+dfsg-2) over (2.11+dfsg-5ubuntu1.1) ... Preparing to unpack .../liblz4-1_1.9.2-2_amd64.deb ... Unpacking liblz4-1:amd64 (1.9.2-2) over (0.0~r131-2ubuntu2) ... Processing triggers for libc-bin (2.31-0ubuntu7) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.27) ... Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1872824/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871176] [NEW] package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: hayden@t470s:~$ sudo apt-get install gnome-boxes [sudo] password for hayden: Reading package lists... Done Building dependency tree Reading state information... Done gnome-boxes is already the newest version (3.36.2-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.03.07-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked. invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed. ● lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor preset: enabled) Active: active (exited) since Mon 2020-04-06 09:33:50 EDT; 4h 10min ago Docs: man:lvmpolld(8) Tasks: 0 (limit: 23811) Memory: 0B CGroup: /system.slice/lvm2-lvmpolld.service Apr 06 09:33:50 t470s systemd[1]: Starting LSB: LVM2 poll daemon... Apr 06 09:33:50 t470s systemd[1]: Started LSB: LVM2 poll daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu2) ... update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 Date: Mon Apr 6 13:38:10 2020 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871176 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: hayden@t470s:~$ sudo apt-get install gnome-boxes [sudo] password for hayden: Reading package lists... Done Building dependency tree Reading state information... Done gnome-boxes is already the newest version (3.36.2-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.03.07-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked. invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed. ● lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor preset: enabled) Active: active (exited) since Mon 2020-04-06 09:33:50 EDT; 4h 10min ago Docs: man:lvmpolld(8) Tasks: 0 (limit: 23811) Memory: 0B CGroup: /system.slice/lvm2-lvmpolld.service Apr 06 09:33:50 t470s systemd[1]: Starting LSB: LVM2 poll daemon... Apr 06 09:33:50 t470s systemd[1]: Started LSB: LVM2 poll daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu2) ... update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 Date: Mon Apr 6 13:38:10 2020 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
This was determined to be a bug in the WSL1 ELF loader and fix is inbound from the WSL side. https://github.com/microsoft/WSL/issues/4461#issuecomment-536023805 Please close on Ubuntu. ** Bug watch added: github.com/microsoft/WSL/issues #4461 https://github.com/microsoft/WSL/issues/4461 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in gzip package in Ubuntu: Confirmed Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
>From the WSL issues page: > Now, thing is, all of the new binaries (f.e. /bin/ls) have that .plt.sec section also, and they work just fine. Also compiling a hello.c with -fcf-protection works. Because of course it does. The only other new section in there (Disco gzip has 27 sections, Eoan has 29) is .note.gnu.property. No joy after stripping that either. Meh. It's not .note.ABI-tag; I stripped that as a WAG right after this issue was posted. Which is all a long description of things that don't work. Next thing to try would be to grab the apt-source, try to build a broken binary, and then try to guess what makes gzip so special (contrast say /bin/ls). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in gzip package in Ubuntu: Confirmed Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479] [NEW] gzip in Ubuntu Eoan results in Exec format error on WSL1
Public bug reported: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gzip (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gzip in Ubuntu Eoan results in Exec format error + gzip in Ubuntu Eoan results in Exec format error on WSL1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in gzip package in Ubuntu: New Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp