[Bug 1782560] Re: RM weboob

** Description changed: Please RM weboob from the archive. Whilst the package itself is not offensive as such, it can be perceived as one, irrespective of the original authors' intent. The current naming of the binaries and source/binary packages, and error messages (some of which h

[Bug 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

** Changed in: ubuntu-z-systems Status: Incomplete => Invalid ** Changed in: libjna-java (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662813 Tit

[Bug 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

Is this on Cosmic? Bionic? or Xenial? I see that system.so is used everywhere by default, on things that do intentionally use system jna. However, on xenial, there is one patch missing to ignore the override properties. Jenkins as shipped in the 3rd party repo does not use system deb:libjna- jav

[Bug 1662813] Re: Libjna-jni uses wrong path on package installation on s390x

I installed jenkins using https://jenkins.io/doc/book/installing /#debian-ubuntu on an s390x Ubuntu cosmic, using openjdk-8-jre-headless, without libjna-java or libjna-jni installed on the system as neither are required. -- You received this bug notification because you are a member of Ubuntu Bug

[Bug 1793092] Re: [FFe] openssl 1.1.1

** Description changed: Merge openssl 1.1.1 from debian unstable. OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream LTS release. Preserving existing delta: - Replace duplicate files in the doc directory with symlinks. - debian/libssl1.1.postinst: - + Displa

[Bug 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Also affects: open-iscsi (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: open-iscsi (Ubun

[Bug 1793092] Re: [FFe] openssl 1.1.1

** Description changed: Merge openssl 1.1.1 from debian unstable. OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream LTS release. - Preserving existing delta: - - Replace duplicate files in the doc directory with symlinks. - - debian/libssl1.1.postinst: -   + Displa

[Bug 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

** Changed in: livecd-rootfs (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net

[Bug 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

All the things sound great here, imho we should do all of them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792905 Title: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds To m

[Bug 1793092] Re: [FFe] openssl 1.1.1

@steve updated. Ping? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793092 Title: [FFe] openssl 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openss

[Bug 1793971] [NEW] RM: qca-qt5, binaries overtaken by qca2

Public bug reported: https://launchpad.net/ubuntu/+source/qca2 appears to have fully taken over all binaries from qca-qt5. ** Affects: qca-qt5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscr

[Bug 1794059] [NEW] Slow IO on intel arches in builders, causes FTBFS

Public bug reported: 1) Failure: TestIO#test_copy_stream_no_busy_wait [/<>/test/ruby/test_io.rb:549]: r58534 [ruby-core:80969] [Backport #13533]. Expected 0.0119998678 to be <= 0.011001. Finished tests in 546.343209s, 31.7127 tests/s, 4140.6006 assertions/s. 17326 tests, 2262

[Bug 1794059] Re: Slow IO on intel arches in builders, causes FTBFS

** Attachment added: "buildlog_ubuntu-cosmic-i386.ruby2.5_2.5.1-5ubuntu3_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ruby2.5/+bug/1794059/+attachment/5192377/+files/buildlog_ubuntu-cosmic-i386.ruby2.5_2.5.1-5ubuntu3_BUILDING.txt.gz -- You received this bug notification because

[Bug 1794059] Re: Slow IO on intel arches in builders, causes FTBFS

[FAILEDTOBUILD] Failed to build on lgw01-amd64-033 Retry this build Started 37 minutes ago Finished 1 minute ago (took 35 minutes, 20.7 seconds) buildlog (217.0 KiB) https://launchpad.net/ubuntu/+source/ruby2.5/2.5.1-5ubuntu3/+build/15481916 -- You received this bug notification because you are

[Bug 1794091] [NEW] [MIR] ruby-xmlrpc

Public bug reported: ruby-xmlrpc 0.3.0 is a bundled_gem part of the libruby2.5 ABI, whilst previously missing it is available now as a stand alone package which ruby2.5 depends on. please promote to main. maintained and embeded by ruby interpreter upstream themselves, similar to other bundled ge

[Bug 1793092] Re: [FFe] openssl 1.1.1

** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793092 Title: [FFe] openssl 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sourc

[Bug 1793092] Re: [FFe] openssl 1.1.1

Pythons appear to hardcode the expectations relative the openssl they were built with, despite not gaining >= 1.1.1 shlibsdep, somehow it ends up with >= 1.1.0 only. ** Also affects: ruby2.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: python2.7 (Ubuntu) Importance: Un

[Bug 1790831] Re: lstape, lsluns: handle non-zfcp; lin_tape multiple paths

Opened bionic task for this bug report in Launchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790831 Title: lstape, lsluns: handle non-zfcp; lin_tape multiple paths To manage notifications ab

[Bug 1790831] Re: lstape, lsluns: handle non-zfcp; lin_tape multiple paths

this bug does not appear in any of our bug report queries, as it is closed. and it has never been targetted to 18.04. Please either open a new bug with state "new" in launchpad, or make the bugzilla bug bridge re-open the bug on launchpad side by resetting the status to "new". None of the comments

[Bug 1794290] [NEW] zkey requires a new system group

Public bug reported: --- Comment From heinz-werner_se...@de.ibm.com 2018-08-31 10:03 EDT--- IBM will not add this systemd update into the s390tools package. Please use this as a pattern for implementation. Many thx in advance Example for an RPM, which need to be adapted to DEB packages.

[Bug 1775627] Re: [18.10 FEAT] Protected key dm-crypt key management tool

Follow-up forked into https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1794290 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775627 Title: [18.10 FEAT] Protected key dm-crypt key managemen

[Bug 1785770] Re: [Ubuntu 18.04]Unable to create NetworkPortal in configFS using Targetcli tool

Whilst the bug is set to trianged and assigned to canonical foundations team, I'm not sure if there is anything to do w.r.t. this bug. I'm also not familiar with this stuff, but I guess the next steps is to trace what pre-created things on the default port and figure out if that can be disabled - s

[Bug 1785770] Re: [Ubuntu 18.04]Unable to create NetworkPortal in configFS using Targetcli tool

I wonder if canonical server team might be of help here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785770 Title: [Ubuntu 18.04]Unable to create NetworkPortal in configFS using Targetcli tool

[Bug 1794318] Re: kernel update breaks boot on intel fake raid 1

So which kernel is good and which one is bad? you didn't mention at all which kernels are borked there has been no mdadm updates lately. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: mdadm (Ubuntu) Status: New => Incomplete ** Changed in:

[Bug 1794341] [NEW] s390-tools-zkey should copy keys into the initramfs

Public bug reported: s390-tools-zkey should copy keys into the initramfs if zkey is in use, the keys should be copied into the initramfs, to allow unlocking zkey based volumes from the initrd itself. (i.e. / and /usr and dependencies of that) ** Affects: s390-tools (Ubuntu) Importance: Unde

[Bug 1794341] Re: s390-tools-zkey should copy keys into the initramfs

** Tags added: zkey -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794341 Title: s390-tools-zkey should copy keys into the initramfs To manage notifications about this bug go to: https://bugs.launc

[Bug 1794347] [NEW] test zkey unlocking of root (/, /usr) devices from the initramfs

Public bug reported: if system is configured with zkey encrypted cryptsetup devices, the expectation is that these can be unlocked from the initramfs. test this. Depends on: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1794290 https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bu

[Bug 1794346] [NEW] zkey - check required kernel modules

Public bug reported: for zkey feature, check that all the required modules are in -image package, not extras. check that these are also shipped in udebs (probably like crypto-modules udeb and/or disk drivers). check that these modules are included in the initramfs as well. ** Affects: linux (Ub

[Bug 1794349] [NEW] fix bugs and test zkey udeb (missing directories, permissions, etc)

Public bug reported: in d-i environment, at the point of partitioning, zkey should be available from the s390-tools-zkey-udeb which should be automatically installed. test that zkey in said environment is usable. Things that are probably missing: - https://bugs.launchpad.net/ubuntu/+source/s390-

[Bug 1766865] Re: [18.10 FEAT] Installer support for protected key dm-crypt

** Tags added: zkey -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766865 Title: [18.10 FEAT] Installer support for protected key dm-crypt To manage notifications about this bug go to: https://bugs

[Bug 1794346] Re: zkey - check and fix required kernel modules locations in debs, udebs, and initramfs

** Summary changed: - zkey - check required kernel modules + zkey - check and fix required kernel modules locations in debs, udebs, and initramfs ** Summary changed: - zkey - check and fix required kernel modules locations in debs, udebs, and initramfs + check and fix zkey required kernel modu

[Bug 1794341] Re: make zkeys available in the initramfs

** Summary changed: - s390-tools-zkey should copy keys into the initramfs + make zkeys available in the initramfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794341 Title: make zkeys available i

[Bug 1794351] [NEW] develop zkey setup installer UI, and zkey-based partition/drive encryption

Public bug reported: currently whist zkey utility is available, there is no UI to set that up, or use for the encrypted volumes. either partman-crypto needs extending, or a new partman-crypto-zkey needs to be created. ** Affects: partman-crypto (Ubuntu) Importance: Undecided Status

[Bug 1794347] Re: develop zkey unlocking of root (/, /usr) devices from the initramfs

** Summary changed: - test zkey unlocking of root (/, /usr) devices from the initramfs + develop zkey unlocking of root (/, /usr) devices from the initramfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bu

[Bug 1794349] Re: fix bugs and test zkey udeb (missing directories, permissions, etc)

** Summary changed: - test that udeb provided zkey is operational + fix bugs and test zkey udeb (missing directories, permissions, etc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794349 Title:

[Bug 1794091] Re: [MIR] ruby-xmlrpc

slangasek> xnox: why have you marked LP: #1794091 'confirmed'? doesn't that break the MIR team's bug triage process? Bug #1794091: [MIR] ruby-xmlrpc xnox: if you mean that it should be picked up for promotion by AA without MIR team review, 'fix committed'

[Bug 1794091] Re: [MIR] ruby-xmlrpc

So ubuntu-server team should subscribe to this package. This is part of libruby2.5 bundled gems, and should fix the bundledgems adt test for the first time in ruby2.5. it is obviously part of ruby2.5 itself, just managed as a gem upstream to allow backporting said gem to prior releases as a stand

[Bug 1794059] Re: Slow IO on intel arches in builders, causes FTBFS

retried ruby2.5 build 4 times in the archive now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794059 Title: Slow IO on intel arches in builders, causes FTBFS To manage notifications about this b

[Bug 1792644] Re: If snapd is not working it can take down systemd

*** This bug is a duplicate of bug 1771858 *** https://bugs.launchpad.net/bugs/1771858 yeah, there is/was a bug in both systemd and snapd w.r.t. injecting :/snap/bin. I believe it is fixed in cosmic already, and bionic should be fixed soon too. I will mark this report as a duplicate. ** This

[Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

Using this bug to fix systemd exported environment to the generators. ** Changed in: systemd (Ubuntu Cosmic) Status: Won't Fix => Fix Committed ** Changed in: systemd (Ubuntu Bionic) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of U

[Bug 1794488] [NEW] Reuse unpacked src tree when running autopkgtests

Public bug reported: When running autopkgtests one is located at the top of the unpacked debian source tree. There is no location given as to where that is, in an environment variable, but it is trivial to cache it. Also, one is supposed to use AUTOPKGTEST_TMP directory for most of the disk spa

[Bug 1793092] Re: [FFe] openssl 1.1.1

ruby2.5 ruby-openssl python3.7 correctly gain stronger dep on libssl1.1 >= 1.1.1. python2.7 and python3.6 still need more patches to pick up https://bugs.python.org/issue34670 ** No longer affects: ruby2.5 (Ubuntu) ** No longer affects: python3.7 (Ubuntu) ** Bug watch added: Python Roundup #346

[Bug 1794308] Re: VM devices rdr, pun and prt are not activated after restart

** Also affects: s390-tools (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/ibm-s390-tools/s390-tools/issues #37 https://github.com/ibm-s390-tools/s390-tools/issues/37 ** Also affects: s390-tools via https://github.com/ibm-s390-tools/s390-tools/issues/37

[Bug 1759172] Re: failed unit tests during build & autopkgtest fails with openssl 1.1.1 pre3

** Description changed: - autopkgtest fails with openssl1.1.1 pre3 + autopkgtest fails with openssl1.1.1 As seen at: - - https://bileto.ubuntu.com/excuses/3217/bionic.html - - test test_ftplib failed -- multiple errors occurred; run in verbose mode - for details - - test test_ssl failed --

[Bug 1759172] Re: python 2.7 test_ssl hits AttributeError with openssl 1.1.1

** Summary changed: - failed unit tests during build & autopkgtest fails with openssl 1.1.1 pre3 + python 2.7 test_ssl hits AttributeError with openssl 1.1.1 ** Bug watch added: Python Roundup #34818 http://bugs.python.org/issue34818 ** Also affects: python via http://bugs.python.org/issue

[Bug 1792883] Re: "grub-install: error: disk `md126, 1' not found." for Intel VROC arrays in mdadm

** Also affects: grub-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792883 Title: "grub-install: error: disk `md126,1' not found." for

[Bug 1793444] Re: [wishlist] Request to support software raid devices

** Also affects: casper (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793444 Title: [wishlist] Request to support software raid devices

[Bug 1778844] Re: nvme multipath does not report path relationships

i downloaded that, and tried to poke it. First of all, i've never seen a 77MB tarball of /sys alone. Also unpacking that, is dangerous as it does explode in size. However, is debugging that, please only _list_ the files present in the tarball and only extract things you need/want. Reuploaded to

[Bug 1793369] Re: Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc/sysrq-trigger

The default sysctl setting for kernel.sysrq in Ubuntu is 176 (and was in bionic and xenial) and it is shipped in /etc/sysctl.d/10-magic- sysrq.conf file. This file is provided by a required package from the minimal task, called `procps`. 176 enables: 128 - allow reboot/poweroff 32 - enable remount

[Bug 1794346] Re: check and fix zkey required kernel modules locations in debs, udebs, and initramfs

linux-modules-4.18.0-8-generic has: ./lib/modules/4.18.0-8-generic/kernel/arch/s390/crypto/paes_s390.ko ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/pkey.ko ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt.ko

[Bug 1815057] Re: [UBUNTU] GCC Wrong code generate for floating point workloads Ubuntu 18.04

** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bug

[Bug 1808476] Re: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants

** Also affects: python2.7 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: python2.7 (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: python2.7 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notificati

[Bug 1823332] [NEW] salt --versions-report broken in bionic/cosmic with openssl 1.1.1

Public bug reported: # sudo apt install salt-master # sudo salt --versions-report Traceback (most recent call last):   File "/usr/bin/salt", line 10, in salt_main()   File "/usr/lib/python3/dist-packages/salt/scripts.py", line 476, in salt_main client.run()   File "/usr/lib/python3/dist-p

[Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

@eole-team hm, that shouldn't happen. python3.6, rebuilt against openssl1.1.1, has not been accepted yet into bionic-proposed. And even, when I upgrade to python3.6 from the staging ppa, salt still fails. To get the pending python3.6, you can use the below PPA: $ sudo add-apt-repository ppa:ci-tr

[Bug 1823332] Re: salt --versions-report broken in bionic/cosmic with openssl 1.1.1

** Bug watch added: github.com/saltstack/salt/issues #49661 https://github.com/saltstack/salt/issues/49661 ** Also affects: salt via https://github.com/saltstack/salt/issues/49661 Importance: Unknown Status: Unknown ** Changed in: salt (Ubuntu Disco) Status: New => Fix Rele

[Bug 1823332] Re: salt --versions-report broken in bionic/cosmic with openssl 1.1.1

** Description changed: + [Impact] + + * salt fails to start with OpenSSL 1.1.1 (which is in cosmic-release, + bionic-proposed) + + [Test Case] + + * bionic-only: install openssl/libssl1.1 from bionic-proposed + + sudo apt install salt-master + sudo salt --versions-report + + [bad] Pytho

[Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

** No longer affects: salt (Ubuntu) ** No longer affects: salt (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS To manage notifications

[Bug 1763165] Re: salt-syndic breaks salt-master in 18.04

** Also affects: salt (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763165 Title: salt-syndic breaks salt-master in 18.04 To manage noti

[Bug 1823365] [NEW] salt is unusable in cosmic due to missing python-tornado4

Public bug reported: [Impact]  * Package salt is not compatible with python-tornado v5 in cosmic+ * In bionic, python-tornado is at v4 and salt works there  * In disco python-tornado4 got reintroduced, such that salt continues to be usable  * Please backport python-tornado4 into cosmic, to enab

[Bug 1823365] Re: salt is unusable in cosmic due to missing python-tornado4

** Changed in: python-tornado4 (Ubuntu Cosmic) Status: New => In Progress ** Changed in: python-tornado4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bug

[Bug 1823332] Re: salt --versions-report broken in bionic/cosmic with openssl 1.1.1

** Changed in: salt (Ubuntu Bionic) Status: Confirmed => In Progress ** Description changed: [Impact] - * salt fails to start with OpenSSL 1.1.1 (which is in cosmic-release, +  * salt fails to start with OpenSSL 1.1.1 (which is in cosmic-release, bionic-proposed) [Test Case]

[Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

** Description changed: [Impact]  * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will.  * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of sup

[Bug 1823382] [NEW] backport openssl 1.1.1 fixes to bionic and cosmic

Public bug reported: [Impact] * neon27 doesn't work with openssl 1.1.1 * backport fixes from disco to cosmic and bionic to resolve that [Test Case] * does not FTBFS [Regression Potential] * currently broken in cosmic, and will break once openssl is upgraded in bionic, so for all practical

[Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs

** Also affects: subiquity Importance: Undecided Status: New ** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534162 Title: symlinks managed by kernel postins

[Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs

I think last time it was fixed by fixing base-installer. http://launchpadlibrarian.net/235185956/base-installer_1.158ubuntu1_1.158ubuntu2.diff.gz but this time around, we need to decide who/what/where should write out kernel-img.conf. because we do not have kernel-common by default. ** Also affe

[Bug 1819721] Re: tomcat8 SRU for bionic uses systemd service instead of init scripts

@Sebastian (slovdahl) Well, you have customized init.d scripts and added local features to it, which is not something that Ubuntu can know about, nor has to support. There are obvious ways how you can continue to support those things in an automated manner. For example, you can dpkg-divert systemd

[Bug 1819721] Re: tomcat8 SRU for bionic uses systemd service instead of init scripts

That is for the future. W.r.t. SRU, i don't know if it is ok to do init.d -> systemd switch in an SRU. And if it's ok to do it without support existing (GA-time) config files, or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. ht

[Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs

** Also affects: curtin Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Invalid ** Changed in: curtin Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubu

[Bug 1534162] Re: symlinks managed by kernel postinst are different from zipl-installer and livefs-rootfs

** Description changed: + + On Ubuntu/Debian like systems /etc/kernel-img.conf should be created by the "installer". It is currently done by base-installer/live-installer/ubiquity but not curtin, but it should be. At the moment we require kernel-img.conf and we do not have the correct per-arch

[Bug 1816812] Re: desktop logout delays due to missing PropertiesChanged signal

** Changed in: systemd (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816812 Title: desktop logout delays due to missing PropertiesChanged signal

[Bug 1823382] Re: backport openssl 1.1.1 fixes to bionic and cosmic

Spot checking both bionic and cosmic, these builds look good. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a me

[Bug 1824097] Re: [Ubuntu] Patches on top of binutils 2.32

** Also affects: binutils (Ubuntu) Importance: Undecided Status: New ** No longer affects: binutils-s390x-cross (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824097 Title: [Ubun

[Bug 1824097] Re: [Ubuntu] Patches on top of binutils 2.32

All of the three mentioned patches are already in Disco / 2.32 as shipped by Ubuntu. As we regularly apply stable branch updates. You can check that this code is in the branch-updates.diff. Is everything done here for Disco? Are you asking to backport this to some other series? -- You received t

[Bug 1824097] Re: [Ubuntu] Patches on top of binutils 2.32

These patches are for 2.32, yet the target seems to be set targetmilestone-inin1804 -> are these needed to be backported to every release back to bionic? If yes, do you have patches for 2.31 and 2.30? Or is this for disco only? ** Description changed: + [Impact] + + * Instructions change in z13

[Bug 1786940] Re: Enable arm-linux-gnueabi target on ppc64el toolchain

For bionic, cosmic, this is in proposed still. But will be released into -updates soon. ** Also affects: binutils (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gcc-defaults (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gcc-7-cross (Ub

[Bug 1786940] Re: Enable arm-linux-gnueabi target on ppc64el toolchain

never mind, this is all fix-released. I have missread the output from rmadison. So we are all good on bionic and up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786940 Title: Enable arm-linux-gnu

[Bug 1824342] Re: in 19.04, default user cannot access system journal

build config, tmpfiles config have not changed. Probably a regression in v240 vs v239 of the systemd-tmpfiles utility implementation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824342 Title: in

[Bug 1824342] Re: in 19.04, default user cannot access system journal

fixed in v241 shame I did not upgrade systemd to v241 in disco. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824342 Title: in 19.04, default user cannot access system journal To manage notifi

[Bug 1824342] Re: in 19.04, default user cannot access system journal

Ok, this is fixed in v240-stable branch by https://github.com/systemd /systemd-stable/commit/5b3437338286fde71f66952726840ba7dbdd86b4 But v240-stable branch has many other useful fixes let me try to land them all. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1824342] Re: in 19.04, default user cannot access system journal

** Changed in: systemd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824342 Title: in 19.04, default user cannot access system journal To manage notifica

[Bug 1819207] Re: [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic installation by ubuntu-drivers

** Changed in: ubiquity (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819207 Title: [FFe] Add Modaliases to open-vm-tools-desktop to allo

[Bug 1822898] Re: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i

booted cosmic mini-iso with proposed enabled, manually injected the 2.2 udeb, and wget geoip.ubuntu.com/lookup still works. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- You received this bug notification because you

[Bug 1822984] Re: revert tls security level back to 1

generated new weak key, cert and try to use it with current cosmic's openssl and succeed: # openssl genrsa -des3 -out myCA.key 600 # openssl req -x509 -new -nodes -key myCA.key -sha256 -days 1825 -out myCA.pem # openssl s_server -cert myCA.pem -key myCA.key -WWW # wget --ca-certificate myCA.pem h

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

In addition to debug output from systemd-tmpfiles-setup.service as above, it is also interesting to know the permiissions on / itself, ie. what's the output of: $ ls -la / -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.l

[Bug 1824407] [NEW] why does booting any livefs squashfs has kernel complaining about unable to read metadata something rather

Public bug reported: Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: squashfs_read_data failed to read block 0x6ff3660032757063 Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: Unable to read metadata cache entry [6ff3660032757063] Apr 11 18:32:55 ubuntu-server kernel: SQUASHFS error:

[Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

*** This bug is a duplicate of bug 1804847 *** https://bugs.launchpad.net/bugs/1804847 OpenVZ has been proactive w.r.t. this issue and have issued an update that includes the required backports a long time ago. Please see this comment: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/18

[Bug 1824523] Re: Assertion error during iso build

This still fails for me: http://paste.ubuntu.com/p/vdN9dBxKBr/ Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Preparing boot device: vda (). Done. apt-esm-hook: hook.cc:184: int main(int, char**): Assertion `ppid == getppid_of("self")' failed. Aborted (core dumped) E:

[Bug 1824523] Re: Assertion error during iso build

I think it is racy to assert things about getppid getppid() returns the process ID of the parent of the calling process. This will be either the ID of the process that created this process us‐ ing fork(), or, if that process has already terminated, the ID of the proc

[Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

got a few more tweaks to the storage test, and it's now more consistently passing on all other architectures but ppc64le. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks

[Bug 1824776] Re: New multipath-tools doesn't update in containers (disco)

*** This bug is a duplicate of bug 1823093 *** https://bugs.launchpad.net/bugs/1823093 ** This bug has been marked a duplicate of bug 1823093 cannot be installed in containers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. htt

[Bug 1824810] [NEW] use host uuid on kvm on power too

Public bug reported: use host uuid on kvm on power too On power, the qemu uuid is exposed as /sys/firmware/devicetree/base/vm,uuid and should be used like /sys/class/dmi/id/product_uuid is used on x86. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Affects: syst

[Bug 1824810] Re: use host uuid on kvm on power too

Ack. Also DPM mode has LPAR UUID we should be using. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824810 Title: use host uuid on kvm on power too To manage notifications about this bug go to: htt

[Bug 1824810] Re: use host uuid on kvm on power too

https://github.com/systemd/systemd/pull/12321 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824810 Title: use host uuid on kvm on power too To manage notifications about this bug go to: https://bu

[Bug 1824810] Re: use host uuid on kvm on power too

https://www.redhat.com/archives/libvir-list/2019-April/msg00987.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824810 Title: use host uuid on kvm on power too To manage notifications about thi

[Bug 1822872] Re: Bionic: Luminous radosgw incompatible with libssl1.1

In bionic we ship two OpenSSL: 1.0.2 and 1.1.0, both in main with security support. The latter is getting upgraded from 1.1.0 to 1.1.1. If ceph in bionic only supports 1.0.2 abi, it should build-depend on libssl1.0-dev and use that both at build time and runtime. If cepth in bionic support 1.1.0

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

I see that people who use nodeenv potentially can get trapped, because of: $ apt show nodeenv | grep -e Package -e Depends Package: nodeenv Depends: python3-pkg-resources, python3, python3:any (>= 3.3.2-2~), make, gcc (>= 4:4.9.1) | nodejs, g++ (>= 4:4.9.1) | nodejs, libssl-dev | nodejs, python2

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

nodejs 8.x series uses libssl1.0-dev (OpenSSL 1.0.2) across all linux distributions and upstream. nodejs 10.x series uses libssl-dev (OpenSSL 1.1.0+) across all linux distributions and upstream. libssl1.0-dev and libssl-dev are intentionally non-coinstallable, as they both own the same include he

[Bug 1862255] Re: focal/linux-5.4: 5.4.0-14.17 -proposed tracker

Can I have it as a snap please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862255 Title: focal/linux-5.4: 5.4.0-14.17 -proposed tracker To manage notifications about this bug go to: https://bug

[Bug 1520033] Re: ftbfs on s390x

mono (5.18.0.240+dfsg-3) unstable; urgency=high [ Jo Shields ] * [20a7dd0] Don't build docs on s390x, to work around a dumb issue [ Neale Ferguson ] * [3713407] Fix s390x Outarg_VT (#10632) * Fix outarg_vt processing. Fixes #10549 * Cleanup unused bits and pieces * Correct the

[Bug 1863145] Re: arm64 cloud image contains flash-kernel which leads to apt errors on upgrade

in livecd-rootfs: ubuntu-cpc) case $ARCH in armhf) KERNEL_FLAVOURS=generic-lpae add_package install flash-kernel ;; arm64) add_package install flash-kernel ;; esac So CPC team should stop including flash-k

<    4   5   6   7   8   9   10   11   12   13   >