date:20191011

This bug was fixed in the package network-manager - 1.20.4-2ubuntu2

---
network-manager (1.20.4-2ubuntu2) eoan; urgency=medium

  * debian/patches/git_wpa_sae.patch:
- PMF can be used with SAE, allow it, fixes WPA3 handling
  (lp: #1844422)

 -- Sebastien Bacher   Fri, 11 Oct 2019 00:06:27
+0200

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1844422

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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 1847820] Re: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is different from other instance

2019-10-11 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpng in Ubuntu.
https://bugs.launchpad.net/bugs/1847820

Title:
  package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is
  different from other instances of package libpng12-0:amd64

Status in libpng package in Ubuntu:
  New

Bug description:
  Bug in libpng package.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpng12-0 1.2.50-2+deb8u3
  ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Sat Oct 12 03:09:34 2019
  Dependencies:
   gcc-8-base 8.1.0-5ubuntu1~16.04 [origin: unknown]
   libc6 2.23-0ubuntu11
   libgcc1 1:8.1.0-5ubuntu1~16.04 [origin: unknown]
   multiarch-support 2.23-0ubuntu11
   zlib1g 1:1.2.8.dfsg-2ubuntu4.1
  DpkgTerminalLog:
   Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ...
   Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.50-2+deb8u3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
  DuplicateSignature:
   package:libpng12-0:1.2.50-2+deb8u3
   Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.50-2+deb8u3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpng12-0/ANNOUNCE', which is different from other instances 
of package libpng12-0:amd64
  InstallationDate: Installed on 2018-08-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: libpng
  Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is different 
from other instances of package libpng12-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1847820/+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 1847820] [NEW] package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is different from other instan

2019-10-11 Thread Gaurav Singh

Public bug reported:

Bug in libpng package.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpng12-0 1.2.50-2+deb8u3
ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Sat Oct 12 03:09:34 2019
Dependencies:
 gcc-8-base 8.1.0-5ubuntu1~16.04 [origin: unknown]
 libc6 2.23-0ubuntu11
 libgcc1 1:8.1.0-5ubuntu1~16.04 [origin: unknown]
 multiarch-support 2.23-0ubuntu11
 zlib1g 1:1.2.8.dfsg-2ubuntu4.1
DpkgTerminalLog:
 Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ...
 Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.50-2+deb8u3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
DuplicateSignature:
 package:libpng12-0:1.2.50-2+deb8u3
 Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.50-2+deb8u3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
ErrorMessage: trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', 
which is different from other instances of package libpng12-0:amd64
InstallationDate: Installed on 2018-08-11 (426 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: libpng
Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is different from 
other instances of package libpng12-0:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libpng (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict third-party-packages xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpng in Ubuntu.
https://bugs.launchpad.net/bugs/1847820

Title:
  package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is
  different from other instances of package libpng12-0:amd64

Status in libpng package in Ubuntu:
  New

Bug description:
  Bug in libpng package.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpng12-0 1.2.50-2+deb8u3
  ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Sat Oct 12 03:09:34 2019
  Dependencies:
   gcc-8-base 8.1.0-5ubuntu1~16.04 [origin: unknown]
   libc6 2.23-0ubuntu11
   libgcc1 1:8.1.0-5ubuntu1~16.04 [origin: unknown]
   multiarch-support 2.23-0ubuntu11
   zlib1g 1:1.2.8.dfsg-2ubuntu4.1
  DpkgTerminalLog:
   Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1.1_amd64.deb ...
   Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.50-2+deb8u3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
  DuplicateSignature:
   package:libpng12-0:1.2.50-2+deb8u3
   Unpacking libpng12-0:amd64 (1.2.54-1ubuntu1.1) over (1.2.50-2+deb8u3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1.1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is 
different from other instances of package libpng12-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpng12-0/ANNOUNCE', which is different from other instances 
of package libpng12-0:amd64
  InstallationDate: Installed on 2018-08-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: libpng
  Title: package libpng12-0 1.2.50-2+deb8u3 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libpng12-0/ANNOUNCE', which is different 
from other instances of package libpng12-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1847820/+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 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

@zhangyoufu, unfortunately this still isn't fixed upstream.  I can reproduce it 
at boot time even with the latest upstream systemd code.
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd-upstream

I'll have to review the upstream code to see what's going on.

** Tags removed: ddstreet

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1845909

Title:
  [SRU] IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  when a networkd interface is configured with LinkLocalAddressing=no,
  networkd still assigns a link-local address to it

  [test case]

  see comment 3.

  note I was only able to reproduce this at boot time; if the vlan
  interface is removed (i.e. 'sudo ip l del pppoe') and then networkd
  restarted, the pppoe interface is created and does not have a link-
  local address.

  [regression potential]

  this moves the point when ipv6ll is configured; regressions would most
  likely involve failure to correctly configure an ipv6ll address when
  desired.

  [other info]

  this bug was attempted to be fixed by 
'debian/patches/networkd-honour-LinkLocalAddressing.patch' from upstream issue 
9890, using a commit that does not correctly fix the issue and was never 
accepted upstream:
  https://github.com/systemd/systemd/issues/9890#issuecomment-455168751

  this SRU completely reverts that patch, and adds the correct fix which
  was merged upstream:
  
https://github.com/systemd/systemd/commit/0e2fdb83bb5e22047e0c7cc058b415d0e93f02cf

  that commit is already included in Eoan so this sru is needed only for
  Disco.

  original description:

  --

  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1845909/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

2019-10-11 Thread fossfreedom

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1847815] Re: storage autopkgtest is flaky

** Tags added: bionic ddstreet disco systemd xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1847815

Title:
  storage autopkgtest is flaky

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  the systemd autopkgtest 'storage' is flaky.

  [test case]

  look at the autopkgtest test log and see some of them are failures due
  to failing 'storage' test; on re-running the test is passes.

  [regression potential]

  only an autopkgtest fix; very low if any.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847815/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

This bug was fixed in the package ubiquity - 19.10.19

---
ubiquity (19.10.19) eoan; urgency=medium

  [ Sebastien Bacher ]
  * Update the 'Skip' string to '_Skip', matching  the change done to
ubiquity.ui some years ago. The template needs to be manual updated which
wasn't done at the time, should make it translatable again (LP: #1731070)

  [ Mathieu Trudel-Lapierre ]
  * Update translations from Launchpad.
  * debian/real-po/templates.pot: update template using debconf-updatepo.

  [ Jean-Baptiste Lallement ]
  * Switch zpool sync property back to standard after installation
  * zfsutils-linux and zfs-initramfs moved to the live task, don't remove them
at the end of installation (LP: #1847739)
  * Change partition types to Solaris Boot and Root types

  [ Didier Roche ]
  * As we are not going to own in the end org.zsys, move our identifier tags
to com.ubuntu.zsys (LP: #1847711)

 -- Jean-Baptiste Lallement 
Fri, 11 Oct 2019 12:05:23 +0200

** Changed in: ubiquity (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1847816] [NEW] storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module

Public bug reported:

[impact]

the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails.  On some custom
kernels, this module isn't built, so the test always fails when doing a
reverse-dep autopkgtest using such a kernel.

As it doesn't make sense for the custom kernels to build the scsi_debug
module for these kernels just so the systemd autopkgtest can pass, there
should be some kind of check in the systemd 'storage' test for a non-
standard kernel (that doesn't include the scsi_debug module) and skip
the test in that case.

[test case]

run the 'storage' autopkgtest with a kernel that doesn't provide the
scsi_debug module, or check the autopkgtest.u.c history.

[regression potential]

test case skipping only, so very low if any regression potential

** Affects: systemd (Ubuntu)
 Importance: Low
 Status: New

** Affects: systemd (Ubuntu Xenial)
 Importance: Low
 Status: New

** Affects: systemd (Ubuntu Bionic)
 Importance: Low
 Status: New

** Affects: systemd (Ubuntu Disco)
 Importance: Low
 Status: New

** Affects: systemd (Ubuntu Eoan)
 Importance: Low
 Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Eoan)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Disco)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1847816

Title:
  storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
  that don't include scsi_debug module

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  New
Status in systemd source package in Eoan:
  New

Bug description:
  [impact]

  the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
  can't load it (and it's not built-in), the test fails.  On some custom
  kernels, this module isn't built, so the test always fails when doing
  a reverse-dep autopkgtest using such a kernel.

  As it doesn't make sense for the custom kernels to build the
  scsi_debug module for these kernels just so the systemd autopkgtest
  can pass, there should be some kind of check in the systemd 'storage'
  test for a non-standard kernel (that doesn't include the scsi_debug
  module) and skip the test in that case.

  [test case]

  run the 'storage' autopkgtest with a kernel that doesn't provide the
  scsi_debug module, or check the autopkgtest.u.c history.

  [regression potential]

  test case skipping only, so very low if any regression potential

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847816/+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 1847815] [NEW] storage autopkgtest is flaky

Public bug reported:

[impact]

the systemd autopkgtest 'storage' is flaky.

[test case]

look at the autopkgtest test log and see some of them are failures due
to failing 'storage' test; on re-running the test is passes.

[regression potential]

only an autopkgtest fix; very low if any.

** Affects: systemd (Ubuntu)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: Fix Released

** Affects: systemd (Ubuntu Xenial)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: systemd (Ubuntu Bionic)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: systemd (Ubuntu Disco)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: systemd (Ubuntu Eoan)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: Fix Released

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Eoan)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Disco)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Disco)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Eoan)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1847815

Title:
  storage autopkgtest is flaky

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  the systemd autopkgtest 'storage' is flaky.

  [test case]

  look at the autopkgtest test log and see some of them are failures due
  to failing 'storage' test; on re-running the test is passes.

  [regression potential]

  only an autopkgtest fix; very low if any.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847815/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

This bug was fixed in the package ubuntustudio-meta - 0.198

---
ubuntustudio-meta (0.198) eoan; urgency=medium

  * Refreshed dependencies
  * Removed zfs-initramfs from desktop-core-recommends [amd64 arm64
ppc64el s390x], desktop-recommends [amd64 arm64 ppc64el s390x]
(LP: #1847739)
  * Removed zfsutils-linux from desktop-core-recommends, desktop-
recommends (LP: #1847739)
  * Removed zsys from desktop-core-recommends [amd64 arm64 armhf i386
ppc64el], desktop-recommends [amd64 arm64 armhf i386 ppc64el]
(LP: #1847739)

 -- Erich Eickmeyer   Fri, 11 Oct 2019
07:54:57 -0700

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

This bug was fixed in the package ubuntu-meta - 1.439

---
ubuntu-meta (1.439) eoan; urgency=medium

  * Refreshed dependencies
  * Only install zfs-initramfs and zfsutils-linux when needed (LP: #1847739)
  * Removed zfs-initramfs from desktop-minimal-recommends [amd64 arm64
ppc64el s390x], desktop-recommends [amd64 arm64 ppc64el s390x]
  * Removed zfsutils-linux from desktop-minimal-recommends, desktop-
recommends

 -- Didier Roche   Fri, 11 Oct 2019 12:22:14 +0200

** Changed in: ubuntu-meta (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

2019-10-11 Thread fossfreedom

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1847527] Re: Backport systemd-journal-remote fix PR #11953

@drdabbles can you provide steps and/or conf files to reproduce this
please

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1847527

Title:
  Backport systemd-journal-remote fix PR #11953

Status in openstack-ansible:
  New
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Disco:
  New

Bug description:
  I'm requesting that systemd 240 receive the fix in upstream PR 11953
  found here https://github.com/systemd/systemd/pull/11953

  This fixes remote journal shipping using systemd components. I believe
  only Disco (19.04) is impacted by this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

2019-10-11 Thread fossfreedom

** Changed in: ubuntu-budgie-meta (Ubuntu)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  In Progress
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu

2019-10-11 Thread Roque

Is the fix on the link a patch proposed for the kernel? Sorry, I don't
understand.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1846140

Title:
  Realtek RTL8723BU doesn't work well in ubuntu

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have one laptop with Realtek RTL8723BU wifi card. It runs, but
  signal is weak (it only works if the router is less than a meter
  away), and even if it gets signal it's slow and it gets interrupted
  frequently. In windows it works normally, and with a much stronger
  signal. I tested it on Ubuntu 18.04.3 and 19.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set

2019-10-11 Thread Bryce Harrington

I'm able to reproduce the faulty on bionic (not upgraded from xenial),
with GTK_IM_MODULE=xim and an empty .xinputrc.

Can also confirm the workaround suggested by Heiko L seems to fix this
issue, by changing /usr/share/themes/Ambiance/gtk-3.20/gtk.css to this:

> textview text {
>background-color: white;
> }
> scrollbar {
>background-color: white;
> }
> @import url("gtk-main.css");

This worked immediately after restarting gnome-calculator (installed
from deb, not snap) and gedit, no other system changes were required.


** Package changed: gtk+3.0 (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1760818

Title:
  gedit and gnome-calculator transparency/graphics corruption issue when
  GTK_IM_MODULE=xim is set

Status in Ubuntu:
  Confirmed
Status in im-config package in Ubuntu:
  Confirmed

Bug description:
  In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
  suffer from a graphics issue where parts of their windows hold parts
  of wallpaper or other windows' contents as background.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 09:12:31 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1760818/+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 1847742] Re: "sudo apt remove libpcsclite1" tries to remove network-manager and more

2019-10-11 Thread Ludovic Rousseau

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1847742

Title:
  "sudo apt remove libpcsclite1" tries to remove network-manager and
  more

Status in pcsc-lite package in Ubuntu:
  Fix Released

Bug description:
  I recently needed to remove and reinstall
  libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this
  package would result in the removal of various network-relevant
  packages (see below). I saw bug report #949912 which reported a
  similar thing in 2012 and marked it fixed. I understand that report
  dealt with the support of multiarch, but the behaviour of apt in the
  case of removal of libpcsclite1 seems undesirable to me. Here's the
  console output I got when trying to remove libpcsclite1 (sorry for the
  German output):

  sudo apt remove libpcsclite1
  [sudo] Passwort für clemens:
  Paketlisten werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut.
  Statusinformationen werden eingelesen Fertig
  Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
 fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni 
libccid libcolord-gtk1
 libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0
  libtomcrypt1 libtommath1 vpnc-scripts
  Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
  Die folgenden Pakete werden ENTFERNT:
 ca-certificates-java gnome-control-center libfreerdp-plugins-standard 
libopenconnect5 libpcsclite1
 network-manager network-manager-config-connectivity-ubuntu 
network-manager-gnome network-manager
 openconnect network-manager-openconnect-gnome network-manager-pptp 
network-manager-pptp-gnome
 openconnect openjdk-8-jre openjdk-8-jre-headless pcscd 
plainbox-provider-checkbox
 plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop 
wpasupplicant
  0 aktualisiert, 0 neu installiert, 22 zu entfernen und 30 nicht aktualisiert.
  Nach dieser Operation werden 126 MB Plattenplatz freigegeben.
  Möchten Sie fortfahren? [J/n]

  The crucial part is all those packages which apt wants to remove
  ("werden ENTFERNT"). I guess I could be doing a stupid thing trying to
  remove the libpcsclite1, but it really seems like unwanted behaviour
  since continuing this package removal as suggested by apt would result
  in an offline computer.

  Cheers,

  Hans

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1847742/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

2019-10-11 Thread Erich Eickmeyer

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1844422] Re: WPA3-SAE support

2019-10-11 Thread Teunis Peters

well, those running KDE (like me) will still have problems but it should solve 
it for many.
(Lots of reasons, but suffice the gnome shell UI is intensely 
counter-productive for me).  Any chance of it being supported on LTS or disco?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1844422

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

  ==
  Update 09-10-2019:
  So it has come to my attention that NetworkManager needs one additional 
commit backported from upstream to make WPA3-SAE work:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08

  Without this latest commit connecting to WPA3-personal networks will
  still fail because of a lack of 802.11w support in the network-manager
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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

Re: [Touch-packages] [Bug 1847742] Re: "sudo apt remove libpcsclite1" tries to remove network-manager and more

2019-10-11 Thread Hans von Wurscht

OK, sorry. I just found it odd that removing a library for smart card stuff 
also removes things like ubuntu-desktop or rdesktop.
Thanks for your work and your quick reply, though!

Am October 11, 2019 1:02:09 PM UTC schrieb Ludovic Rousseau 
:
>Just do not remove libpcsclite1.
>
>You can reinstall it with:
>sudo apt install --reinstall libpcsclite1
>
>If you *really* think it is a bug then please report it to
>wpasupplicant
>that depends on libpcsclite1.
>
>-- 
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/1847742
>
>Title:
>  "sudo apt remove libpcsclite1" tries to remove network-manager and
>  more
>
>Status in pcsc-lite package in Ubuntu:
>  New
>
>Bug description:
>  I recently needed to remove and reinstall
>  libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this
>  package would result in the removal of various network-relevant
>  packages (see below). I saw bug report #949912 which reported a
>  similar thing in 2012 and marked it fixed. I understand that report
>  dealt with the support of multiarch, but the behaviour of apt in the
>  case of removal of libpcsclite1 seems undesirable to me. Here's the
> console output I got when trying to remove libpcsclite1 (sorry for the
>  German output):
>
>  sudo apt remove libpcsclite1
>  [sudo] Passwort für clemens:
>  Paketlisten werden gelesen... Fertig
>  Abhängigkeitsbaum wird aufgebaut.
>  Statusinformationen werden eingelesen Fertig
>Die folgenden Pakete wurden automatisch installiert und werden nicht
>mehr benötigt:
>fonts-dejavu-extra java-common libatk-wrapper-java
>libatk-wrapper-java-jni libccid libcolord-gtk1
> libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0
>  libtomcrypt1 libtommath1 vpnc-scripts
>  Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
>  Die folgenden Pakete werden ENTFERNT:
>ca-certificates-java gnome-control-center libfreerdp-plugins-standard
>libopenconnect5 libpcsclite1
>network-manager network-manager-config-connectivity-ubuntu
>network-manager-gnome network-manager
>openconnect network-manager-openconnect-gnome network-manager-pptp
>network-manager-pptp-gnome
>openconnect openjdk-8-jre openjdk-8-jre-headless pcscd
>plainbox-provider-checkbox
>plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop
>wpasupplicant
>0 aktualisiert, 0 neu installiert, 22 zu entfernen und 30 nicht
>aktualisiert.
>  Nach dieser Operation werden 126 MB Plattenplatz freigegeben.
>  Möchten Sie fortfahren? [J/n]
>
>  The crucial part is all those packages which apt wants to remove
> ("werden ENTFERNT"). I guess I could be doing a stupid thing trying to
>  remove the libpcsclite1, but it really seems like unwanted behaviour
> since continuing this package removal as suggested by apt would result
>  in an offline computer.
>
>  Cheers,
>
>  Hans
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1847742/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1847742

Title:
  "sudo apt remove libpcsclite1" tries to remove network-manager and
  more

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I recently needed to remove and reinstall
  libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this
  package would result in the removal of various network-relevant
  packages (see below). I saw bug report #949912 which reported a
  similar thing in 2012 and marked it fixed. I understand that report
  dealt with the support of multiarch, but the behaviour of apt in the
  case of removal of libpcsclite1 seems undesirable to me. Here's the
  console output I got when trying to remove libpcsclite1 (sorry for the
  German output):

  sudo apt remove libpcsclite1
  [sudo] Passwort für clemens:
  Paketlisten werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut.
  Statusinformationen werden eingelesen Fertig
  Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
 fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni 
libccid libcolord-gtk1
 libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0
  libtomcrypt1 libtommath1 vpnc-scripts
  Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
  Die folgenden Pakete werden ENTFERNT:
 ca-certificates-java gnome-control-center libfreerdp-plugins-standard 
libopenconnect5 libpcsclite1
 network-manager network-manager-config-connectivity-ubuntu 
network-manager-gnome network-manager
 openconnect network-manager-openconnect-gnome network-manager-pptp 
network-manager-pptp-gnome
 openconnect openjdk-8-jre openjdk-8-jre-headless pcscd 
plainbox-provider-checkbox
 plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop 
wpasupplicant
  0 aktualisiert, 0 neu installiert, 22 zu en

[Touch-packages] [Bug 1847496] Re: [trusty] policy not always initialized when building depcache

2019-10-11 Thread Julian Andres Klode

It passed!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1847496

Title:
  [trusty] policy not always initialized when building depcache

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  apt in trusty does not always initialize the policy before constructing the 
depcache. This means that if you access the depcache, it does not respect 
pinning when calculating upgrades.

  This is not a general problem - according to current knowledge, it
  only affects apt list. It does affect any code that requests a
  depCache from pkgCacheFile without having explicitly build caches, or
  explicitly initialized policy (which other parts of apt do).

  
  [Test case]

  1. Add deb https://esm.ubuntu.com/ubuntu/ trusty-infra-security main to 
sources.list
  2. Pin it down

  Package: *
  Pin: release trusty-infra-security
  Pin-Priority: -1

  3. Look at apt list apport

  Currently it shows:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed,upgradable to: 2.14.1-0ubuntu3.29]

  because when calculating whether the package is upgradable, it did not
  see the pinning.

  Correct would be:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed]

  [Regression potential]
  Behavior of code that only initializes depcache, but not policy will change. 
For example, pinning will be applied in such code (as it is in later versions, 
and should be). This adds some more error cases as well, such as parsing 
failures for preferences files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1847496/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

2019-10-11 Thread Erich Eickmeyer

** Changed in: ubuntustudio-meta (Ubuntu)
 Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntustudio-meta package in Ubuntu:
  In Progress
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

(in unapproved)

** Changed in: ubiquity (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntustudio-meta package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1840435] Re: Systemd >=240 sets a clamp of 64MB for RLIMIT_MEMLOCK, too low for some applications.

2019-10-11 Thread Balint Reczey

Marking as fixed in Eoan, since it already has systemd v242.

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1840435

Title:
  Systemd >=240 sets a clamp of 64MB for RLIMIT_MEMLOCK, too low for
  some applications.

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Disco:
  New

Bug description:
  Systemd >= 240 sets a clamp for RLIMIT_MEMLOCK, which is too low for
  some realistic applications.  This clamp should probably be increased.
  This breaks a number of current jackd setups, for example.

  See upstream bug: https://github.com/systemd/systemd/issues/13331.

  This occurs on at Ubuntu Disco and newer, Disco being the first
  release to ship with systemd >= 240.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1840435/+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 1847496] Re: [trusty] policy not always initialized when building depcache

2019-10-11 Thread Julian Andres Klode

The tests on armhf timed out, but the others all passed; I retried the
armhf ones, but not sure if they won't time out again.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1847496

Title:
  [trusty] policy not always initialized when building depcache

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  apt in trusty does not always initialize the policy before constructing the 
depcache. This means that if you access the depcache, it does not respect 
pinning when calculating upgrades.

  This is not a general problem - according to current knowledge, it
  only affects apt list. It does affect any code that requests a
  depCache from pkgCacheFile without having explicitly build caches, or
  explicitly initialized policy (which other parts of apt do).

  
  [Test case]

  1. Add deb https://esm.ubuntu.com/ubuntu/ trusty-infra-security main to 
sources.list
  2. Pin it down

  Package: *
  Pin: release trusty-infra-security
  Pin-Priority: -1

  3. Look at apt list apport

  Currently it shows:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed,upgradable to: 2.14.1-0ubuntu3.29]

  because when calculating whether the package is upgradable, it did not
  see the pinning.

  Correct would be:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed]

  [Regression potential]
  Behavior of code that only initializes depcache, but not policy will change. 
For example, pinning will be applied in such code (as it is in later versions, 
and should be). This adds some more error cases as well, such as parsing 
failures for preferences files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1847496/+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 1847496] Re: [trusty] policy not always initialized when building depcache

2019-10-11 Thread Julian Andres Klode

Verified OK

root@t:~# apt list apport
Listing... Done
apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all 
[installed,upgradable to: 2.14.1-0ubuntu3.29]
root@t:~# apt install libapt-pkg4.12
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libfreetype6 os-prober
Use 'apt-get autoremove' to remove them.
The following packages will be upgraded:
  libapt-pkg4.12
1 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
Need to get 646 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libapt-pkg4.12 
amd64 1.0.1ubuntu2.24 [646 kB]
Fetched 646 kB in 0s (2692 kB/s)  
(Reading database ... 25111 files and directories currently installed.)
Preparing to unpack .../libapt-pkg4.12_1.0.1ubuntu2.24_amd64.deb ...
Unpacking libapt-pkg4.12:amd64 (1.0.1ubuntu2.24) over (1.0.1ubuntu2.23) ...
Setting up libapt-pkg4.12:amd64 (1.0.1ubuntu2.24) ...
Processing triggers for libc-bin (2.19-0ubuntu6.15) ...
root@t:~# apt list apport
Listing... Done
apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all [installed]


** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1847496

Title:
  [trusty] policy not always initialized when building depcache

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  apt in trusty does not always initialize the policy before constructing the 
depcache. This means that if you access the depcache, it does not respect 
pinning when calculating upgrades.

  This is not a general problem - according to current knowledge, it
  only affects apt list. It does affect any code that requests a
  depCache from pkgCacheFile without having explicitly build caches, or
  explicitly initialized policy (which other parts of apt do).

  
  [Test case]

  1. Add deb https://esm.ubuntu.com/ubuntu/ trusty-infra-security main to 
sources.list
  2. Pin it down

  Package: *
  Pin: release trusty-infra-security
  Pin-Priority: -1

  3. Look at apt list apport

  Currently it shows:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed,upgradable to: 2.14.1-0ubuntu3.29]

  because when calculating whether the package is upgradable, it did not
  see the pinning.

  Correct would be:

  apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all
  [installed]

  [Regression potential]
  Behavior of code that only initializes depcache, but not policy will change. 
For example, pinning will be applied in such code (as it is in later versions, 
and should be). This adds some more error cases as well, such as parsing 
failures for preferences files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1847496/+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 1847742] Re: "sudo apt remove libpcsclite1" tries to remove network-manager and more

2019-10-11 Thread Ludovic Rousseau

Just do not remove libpcsclite1.

You can reinstall it with:
sudo apt install --reinstall libpcsclite1

If you *really* think it is a bug then please report it to wpasupplicant
that depends on libpcsclite1.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1847742

Title:
  "sudo apt remove libpcsclite1" tries to remove network-manager and
  more

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I recently needed to remove and reinstall
  libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this
  package would result in the removal of various network-relevant
  packages (see below). I saw bug report #949912 which reported a
  similar thing in 2012 and marked it fixed. I understand that report
  dealt with the support of multiarch, but the behaviour of apt in the
  case of removal of libpcsclite1 seems undesirable to me. Here's the
  console output I got when trying to remove libpcsclite1 (sorry for the
  German output):

  sudo apt remove libpcsclite1
  [sudo] Passwort für clemens:
  Paketlisten werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut.
  Statusinformationen werden eingelesen Fertig
  Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
 fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni 
libccid libcolord-gtk1
 libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0
  libtomcrypt1 libtommath1 vpnc-scripts
  Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
  Die folgenden Pakete werden ENTFERNT:
 ca-certificates-java gnome-control-center libfreerdp-plugins-standard 
libopenconnect5 libpcsclite1
 network-manager network-manager-config-connectivity-ubuntu 
network-manager-gnome network-manager
 openconnect network-manager-openconnect-gnome network-manager-pptp 
network-manager-pptp-gnome
 openconnect openjdk-8-jre openjdk-8-jre-headless pcscd 
plainbox-provider-checkbox
 plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop 
wpasupplicant
  0 aktualisiert, 0 neu installiert, 22 zu entfernen und 30 nicht aktualisiert.
  Nach dieser Operation werden 126 MB Plattenplatz freigegeben.
  Möchten Sie fortfahren? [J/n]

  The crucial part is all those packages which apt wants to remove
  ("werden ENTFERNT"). I guess I could be doing a stupid thing trying to
  remove the libpcsclite1, but it really seems like unwanted behaviour
  since continuing this package removal as suggested by apt would result
  in an offline computer.

  Cheers,

  Hans

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1847742/+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 1847765] [NEW] network manager using small timeout polling timeouts

2019-10-11 Thread Colin Ian King

Public bug reported:

I've been trying to identify wakeup events that cause the CPU to wakeup
from idle on a "idle" laptop on Ubuntu Eoan. The good news is that
NetworkManager doesn't utilize much CPU when idle, however, it does seem
to wakeup from poll()/epool_wait() system calls once every 4-5 seconds
on timer timeouts and I was wondering if those are necessary as they
keep the CPU from being idle.

I ran heath-check [1] for 1 hour to monitor NetworkManager. See the
attached output. Look at the "Top polling system calls:" section and
you see that poll() and epoll_wait() are polling with timeouts set to be
0.0 seconds, 6.0 and 4.0 seconds.

Also look at the "Polling system call analysis:" section and you see a
breakdown of the poll()/epoll_wait() calls.

Recommendation:

1. Are the 4.0/6.0 poll waits necessary? Why a timeout every 4.0/6.0 seconds?
2. Why are there so many polls with zero timeouts? These normally occur when a
quick peek at busy pool events on file descriptors occurs. Are these necessary?

Anyhow, this is quite low in priority, but it would be nice to get
investigated and fixed just to reduce CPU wakeups.

References
[1] https://kernel.ubuntu.com/~cking/health-check/

** Affects: network-manager (Ubuntu)
Importance: Low
Status: New

** Attachment added: "network manager health-check report log file."

https://bugs.launchpad.net/bugs/1847765/+attachment/5296572/+files/network-manager-health-check.log

** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low

** Summary changed:

- network manager using non-blocking zero timeout polling
+ network manager using small timeout polling timeouts

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1847765

Title:
network manager using small timeout polling timeouts

Status in network-manager package in Ubuntu:
New

Bug description:
I've been trying to identify wakeup events that cause the CPU to
wakeup from idle on a "idle" laptop on Ubuntu Eoan. The good news is
that NetworkManager doesn't utilize much CPU when idle, however, it
does seem to wakeup from poll()/epool_wait() system calls once every
4-5 seconds on timer timeouts and I was wondering if those are
necessary as they keep the CPU from being idle.

Also look at the "Polling system call analysis:" section and you see a
breakdown of the poll()/epoll_wait() calls.

Recommendation:

1. Are the 4.0/6.0 poll waits necessary? Why a timeout every 4.0/6.0 seconds?
2. Why are there so many polls with zero timeouts? These normally occur when
a quick peek at busy pool events on file descriptors occurs. Are these
necessary?

Anyhow, this is quite low in priority, but it would be nice to get
investigated and fixed just to reduce CPU wakeups.

References
[1] https://kernel.ubuntu.com/~cking/health-check/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1847765/+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 1758271] Re: error message at start of vim in shell

2019-10-11 Thread Claudio Fior

** Changed in: vim (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1758271

Title:
  error message at start of vim in shell

Status in vim package in Ubuntu:
  Invalid

Bug description:
  This is the message

  Error detected while processing /usr/share/vim/vim80/debian.vim:
  line   29:
  E319: Sorry, the command is not available in this version: function! 
MapExists(name, modes)
  line   30:
  E319: Sorry, the command is not available in this version:   for mode in 
split(a:modes, '\zs')
  line   34:
  E319: Sorry, the command is not available in this version:   endfor
  line   35:
  E319: Sorry, the command is not available in this version:   return 0
  line   36:
  E319: Sorry, the command is not available in this version: endfunction

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim 2:8.0.1401-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Fri Mar 23 09:30:07 2018
  InstallationDate: Installed on 2018-02-21 (29 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=it_IT
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1758271/+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 1840510] Re: Please enable PGO and LTO for arm64

2019-10-11 Thread Francis Ginther

** Tags added: id-5d926655f9e2a5107c03e668

** Tags added: id-5d9f8a1e11e3927e713981ef

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1840510

Title:
  Please enable PGO and LTO for arm64

Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3-defaults source package in Bionic:
  New
Status in python3-defaults package in Debian:
  Fix Released

Bug description:
  The rules file conditionally enables PGO and LTO in the python3 build
  and while it's enabled for many platforms it's not enabled for arm64.
  This is worth about 30% performance. Please enable it.

  A patch is available here with the original debian bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1840510/+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 1624673] Re: package ca-certificates 20160104ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1624673

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Sep 17 00:19:48 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2016-02-19 (210 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-09-13 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1624673/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

2019-10-11 Thread Jean-Baptiste Lallement

I added zfsutils-linux and zfs-initramfs to filesystem.manifest-remove
on the iso (bind mount) and did the following tests:

* Normal zfs installation without the patch: zfs-initramfs is removed (but not 
zfsutils-linux which is a different issue that needs investigation)
* Normal zfs installation with the patch: both packages are kept installed on 
target.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2019-10-11 Thread Rafael David Tinoco

Eoan SRU:

MR: 
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/systemd/+git/systemd/+merge/374027
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1815101

Add:

KeepConfiguration=static

to .network file to keep aliases to.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in Keepalived Charm:
  New
Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Triaged
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in heartbeat source package in Bionic:
  Triaged
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in heartbeat source package in Disco:
  Triaged
Status in keepalived source package in Disco:
  Confirmed
Status in systemd source package in Disco:
  Confirmed
Status in heartbeat source package in Eoan:
  Triaged
Status in keepalived source package in Eoan:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth2:
  addresses:
- 12.13.14.18/29
- 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  vrrp_sync_group collection {
  group {
  wan
  lan
  phone
  }
  vrrp_instance wan {
  state MASTER
  interface eth2
  virtual_router_id 77
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass BlahBlah
  }
  virtual_ipaddress {
  12.13.14.20
  }
  }
  vrrp_instance lan {
  state MASTER
  interface eth3
  virtual_router_id 78
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MoreBlah
  }
  virtual_ipaddress {
  10.22.11.13/24
  }
  }
  vrrp_instance phone {
  state MASTER
  interface eth4
  virtual_router_id 79
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MostBlah
  }
  virtual_ipaddress {
  10.22.14.3/24
  }
  }

  At boot the affected interfaces have:
  5: eth4:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether ab:cd:ef:90:c0:e3 brd ff:ff:ff:ff:ff:ff
  inet 10.22.14.6/24 brd 10.22.14.255 scope global eth4
 valid_lft forever preferred_lft forever
  inet 10.22.14.3/24 scope global secondary eth4

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

** Merge proposal linked:
   
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/systemd/+git/systemd/+merge/374027

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in Keepalived Charm:
  New
Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Triaged
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in heartbeat source package in Bionic:
  Triaged
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in heartbeat source package in Disco:
  Triaged
Status in keepalived source package in Disco:
  Confirmed
Status in systemd source package in Disco:
  Confirmed
Status in heartbeat source package in Eoan:
  Triaged
Status in keepalived source package in Eoan:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth2:
  addresses:
- 12.13.14.18/29
- 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  vrrp_sync_group collection {
  group {
  wan
  lan
  phone
  }
  vrrp_instance wan {
  state MASTER
  interface eth2
  virtual_router_id 77
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass BlahBlah
  }
  virtual_ipaddress {
  12.13.14.20
  }
  }
  vrrp_instance lan {
  state MASTER
  interface eth3
  virtual_router_id 78
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MoreBlah
  }
  virtual_ipaddress {
  10.22.11.13/24
  }
  }
  vrrp_instance phone {
  state MASTER
  interface eth4
  virtual_router_id 79
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MostBlah
  }
  virtual_ipaddress {
  10.22.14.3/24
  }
  }

  At boot the affected interfaces have:
  5: eth4:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether ab:cd:ef:90:c0:e3 brd ff:ff:ff:ff:ff:ff
  inet 10.22.14.6/24 brd 10.22.14.255 scope global eth4
 valid_lft forever preferred_lft forever
  inet 10.22.14.3/24 scope global secondary eth4
 valid_lft forever preferred_lft forever
  inet6 fe80::ae1f:6bff:fe90:c0e3/64 scope link 
 valid_lft foreve

[Touch-packages] [Bug 1842352] Re: autopkgtest: boot-and-services test fails in armhf containers

2019-10-11 Thread Balint Reczey

This is fixed in Eoan's 242-6ubuntu1.

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842352

Title:
  autopkgtest: boot-and-services test fails in armhf containers

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/armhf/s/systemd/20190902_092319_bc0af@/log.gz

  ...
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'

  ==
  ERROR: test_profile (__main__.AppArmorTest)
  AppArmor confined unit
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.3bj70k/build.TYC/src/debian/tests/boot-and-services", line 
286, in test_profile
  subprocess.check_call(['apparmor_parser', '-r', '-v', aa_profile.name])
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['apparmor_parser', '-r', '-v', 
'/tmp/aa_violator.hg3olay4']' returned non-zero exit status 243.

  --
  Ran 23 tests in 5.848s

  FAILED (errors=1, skipped=5)

  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842352/+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 1847742] [NEW] "sudo apt remove libpcsclite1" tries to remove network-manager and more

2019-10-11 Thread Hans von Wurscht

Public bug reported:

I recently needed to remove and reinstall
libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this
package would result in the removal of various network-relevant packages
(see below). I saw bug report #949912 which reported a similar thing in
2012 and marked it fixed. I understand that report dealt with the
support of multiarch, but the behaviour of apt in the case of removal of
libpcsclite1 seems undesirable to me. Here's the console output I got
when trying to remove libpcsclite1 (sorry for the German output):

sudo apt remove libpcsclite1
[sudo] Passwort für clemens:
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
   fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni 
libccid libcolord-gtk1
   libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0
libtomcrypt1 libtommath1 vpnc-scripts
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
Die folgenden Pakete werden ENTFERNT:
   ca-certificates-java gnome-control-center libfreerdp-plugins-standard 
libopenconnect5 libpcsclite1
   network-manager network-manager-config-connectivity-ubuntu 
network-manager-gnome network-manager
   openconnect network-manager-openconnect-gnome network-manager-pptp 
network-manager-pptp-gnome
   openconnect openjdk-8-jre openjdk-8-jre-headless pcscd 
plainbox-provider-checkbox
   plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop 
wpasupplicant
0 aktualisiert, 0 neu installiert, 22 zu entfernen und 30 nicht aktualisiert.
Nach dieser Operation werden 126 MB Plattenplatz freigegeben.
Möchten Sie fortfahren? [J/n]

The crucial part is all those packages which apt wants to remove
("werden ENTFERNT"). I guess I could be doing a stupid thing trying to
remove the libpcsclite1, but it really seems like unwanted behaviour
since continuing this package removal as suggested by apt would result
in an offline computer.

Cheers,

Hans

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1847742

Title:
  "sudo apt remove libpcsclite1" tries to remove network-manager and
  more

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I recently needed to remove and reinstall
  libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this
  package would result in the removal of various network-relevant
  packages (see below). I saw bug report #949912 which reported a
  similar thing in 2012 and marked it fixed. I understand that report
  dealt with the support of multiarch, but the behaviour of apt in the
  case of removal of libpcsclite1 seems undesirable to me. Here's the
  console output I got when trying to remove libpcsclite1 (sorry for the
  German output):

  sudo apt remove libpcsclite1
  [sudo] Passwort für clemens:
  Paketlisten werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut.
  Statusinformationen werden eingelesen Fertig
  Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
 fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni 
libccid libcolord-gtk1
 libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0
  libtomcrypt1 libtommath1 vpnc-scripts
  Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
  Die folgenden Pakete werden ENTFERNT:
 ca-certificates-java gnome-control-center libfreerdp-plugins-standard 
libopenconnect5 libpcsclite1
 network-manager network-manager-config-connectivity-ubuntu 
network-manager-gnome network-manager
 openconnect network-manager-openconnect-gnome network-manager-pptp 
network-manager-pptp-gnome
 openconnect openjdk-8-jre openjdk-8-jre-headless pcscd 
plainbox-provider-checkbox
 plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop 
wpasupplicant
  0 aktualisiert, 0 neu installiert, 22 zu entfernen und 30 nicht aktualisiert.
  Nach dieser Operation werden 126 MB Plattenplatz freigegeben.
  Möchten Sie fortfahren? [J/n]

  The crucial part is all those packages which apt wants to remove
  ("werden ENTFERNT"). I guess I could be doing a stupid thing trying to
  remove the libpcsclite1, but it really seems like unwanted behaviour
  since continuing this package removal as suggested by apt would result
  in an offline computer.

  Cheers,

  Hans

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1847742/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

2019-10-11 Thread Sean Davis

** Also affects: xubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1847527] Re: Backport systemd-journal-remote fix PR #11953

2019-10-11 Thread Balint Reczey

This is fixed with v242, present in Eoan.

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1847527

Title:
  Backport systemd-journal-remote fix PR #11953

Status in openstack-ansible:
  New
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Disco:
  New

Bug description:
  I'm requesting that systemd 240 receive the fix in upstream PR 11953
  found here https://github.com/systemd/systemd/pull/11953

  This fixes remote journal shipping using systemd components. I believe
  only Disco (19.04) is impacted by this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

Here is the change to the ubuntu desktop seed as an example:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/ubuntu/commit/?h=eoan&id=00192c2d530e6b9a636ac0dcd754c4a80a2319e5.
Ubiquity upload is on the way.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1847739] Re: Make zfs-initramfs and zfsutils-linux install optional

Subscribed infinity for tracking the release. Look at the commit why
it's not (yet) added to live-common.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1847739

Title:
  Make zfs-initramfs and zfsutils-linux install optional

Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  Move those 2 to the live seed to have them available in the installer.

  Mark them then manually installed in the installer if needed. Then,
  ubiquity will purge them if not used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847739/+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 1847739] [NEW] Make zfs-initramfs and zfsutils-linux install optional