** Changed in: console-setup (Ubuntu Xenial)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1604737
Title:
headless installat
** 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
$ cat /boot/config-5.0.0-16-generic | grep LOG_BUF
CONFIG_LOG_BUF_SHIFT=18
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
$ uname -a
Linux doerfel 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:54:19 UTC 2019
aarch64 aarch64 aarch64 GNU/Linux
And journal shows complete kernel boot messages, thus this all no
Ubuntu core devices forced set LZMA which is now unsupported, fixing to
use LZ4 on these now as well.
** Also affects: initramfs-tools-ubuntu-core (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Also affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lvm2 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: e2fsprogs (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch
@IBM
Please close your LTC bugzilla entry. We will continue to use this LP issue to
pursue busybox upstream. Thanks a lot for your input!
** Changed in: busybox (Ubuntu)
Status: New => Triaged
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notificat
Will do! thanks for digging into this even though it's well, busybox
issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1828282
Title:
busybox 1.30.1 crashes bzip2 test
** Changed in: icu (Ubuntu Eoan)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/1827391
Title:
Japanese era Reiwa SRU
Status in icu packag
The question is, if we should be seeding it back into cloud images,
server, and desktop.
--
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/1550566
Title:
ubuntu-minimal s
Given that `init` is seeded, it means systemd and journald will be
present on the system and provide a syslog compatible interface on the
local system. For a minimal system that is sufficient.
Please note that persistent logs have not been enabled in xenial, thus
ideally such a change should only
** Changed in: bash (Ubuntu Trusty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1614080
Title:
PATH contains dot when PATH is unset
(xenial-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(xenial-amd64)root@ottawa:~# dpkg-query -W bash
bash4.3-14ubuntu1.3
Xenial looks good.
** Tags removed: verification-needed verification-needed-xenial
** Tags added:
(bionic-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(bionic-amd64)root@ottawa:~# dpkg-query -W bash
bash4.4.18-2ubuntu1.1
Bionic looks good.
** Tags removed: verification-needed-bionic
** Tags added: verification-done
(disco-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(disco-amd64)root@ottawa:~# dpkg-query -W bash
bash5.0-3ubuntu1.1
Disco looks good.
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
(xenial-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(xenial-amd64)root@ottawa:~# dpkg-query -W bash
bash4.3-14ubuntu1.3
Xenial looks good.
** Tags removed: verification-needed verification-needed-xenial
** Tags added:
(disco-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(disco-amd64)root@ottawa:~# dpkg-query -W bash
bash5.0-3ubuntu1.1
Disco looks good.
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
(bionic-amd64)root@ottawa:~# env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
(bionic-amd64)root@ottawa:~# dpkg-query -W bash
bash4.4.18-2ubuntu1.1
Bionic looks good.
** Tags removed: verification-needed-bionic
** Tags added: verification-done
Trusty is closed for SRUs, here is the diff that may be suitable for
ESM.
** Patch added: "trusty-bash.diff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+attachment/5262678/+files/trusty-bash.diff
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
Steps to reproduce:
1) Get a system with glibc 2.29
2) Get busybox 1.30.1 installed (e.g. eoan, or download busybox package
from
https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3/+build/16724246
and use $ apt install ./busybox*.deb to install)
3) Get busybox 1.
Hm, the test case is incomplete. As I appear to not be able to use the
stock config, and I need a CA generated too. I should get better details
for it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https:/
@tim
As that is a regression already in cosmic, disco and eoan, it's best to track
fixing that up and track via a separate SRU bug #. Please see
https://bugs.launchpad.net/openssl/+bug/1828215 and subscribe to that bug and
use that one to track releasing updates for the issue you report.
Which
Public bug reported:
[Impact]
* openssl command line utility option parsing has regressed in 1.1.0i+
and produces binary output, where text output is expected, breaking
applications that parse that.
[Test Case]
* OPENSSL_ENABLE_MD5_VERIFY=1 openssl ca -config test.openssl.cnf
-passin stdin -b
In regression potential, in the connectivity section, added more info
about "non-application data records" issues that may cause main-loop
hangs.
** Description changed:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer
Nova is tracked in
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1771506
** No longer affects: nova (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1797
** Description changed:
Japanese era Reiwa SRU
$ rmadison icu
4.8.1.1-3ubuntu0.7 | precise-updates
52.1-3ubuntu0.8| trusty-updates
55.1-7ubuntu0.4| xenial-updates
60.2-3ubuntu3 | bionic
60.2-6ubuntu1 | cosmic
63.1-6 | disco
63.1-6 | e
** Description changed:
Japanese era Reiwa SRU
+
+ $ rmadison icu
+ 4.8.1.1-3ubuntu0.7 | precise-updates
+ 52.1-3ubuntu0.8| trusty-updates
+ 55.1-7ubuntu0.4| xenial-updates
+ 60.2-3ubuntu3 | bionic
+ 60.2-6ubuntu1 | cosmic
+ 63.1-6 | disco
+ 63.1-6 | e
** Also affects: bash (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: bash (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: bash (Ubuntu Eoan)
Importance: Medium
Status: Fix Released
** Also affects: bash (Ubuntu Trusty)
Impor
Public bug reported:
Japanese era Reiwa SRU
** Affects: icu (Ubuntu)
Importance: Undecided
Status: New
** Affects: icu (Ubuntu Precise)
Importance: Undecided
Status: New
** Affects: icu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: icu
Ping, does vaultlocker work, _without_ work arounds, race free on bionic
and up?
** Changed in: cryptsetup (Ubuntu)
Status: New => Incomplete
** Changed in: lvm2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seede
This is not a regression in any stable releases, failing tests is not a
problem at all. As release and SRU processes only consider regressions
(previously passed, now failing). Things that have always failed are
treated as such by proposed-updates and the rest of the tooling ("always
failed"). This
SRU policy, Section 2 "When", has three major categories listing in
bullet points cases that are eligible for SRU.
Which one is this SRU submitted under?
https://wiki.ubuntu.com/StableReleaseUpdates#When
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
Adding new autopkgtests in devel series - good.
Adding new autopkgtests in stable series - not good.
Fixing regressions that got introduced during the lifetime of a stable
series - good.
The only times when we introduced new autopkgtests in stable series, is
when we upload fixes for regressions
** Description changed:
+ [Impact]
+
+ * For consistency reasons sbin should be ordered before bin in PATH.
+
+ [Test Case]
+
+ * $ env -u PATH /bin/bash -c 'echo $PATH'
+
+ And check that matching pairs in PATH, have /sbin variant leading /bin
+ variant.
+
+ [Regression Potential]
+
+ *
** Description changed:
+ [Impact]
+
+ * The fallback path built into bash contains '.' which leads to
+ unexpected addition of the current working directory. It should not be
+ there, just like it isnt' in pre-precise and cosmic+.
+
+ [Test Case]
+
+ * $ env -u PATH /bin/bash -c 'echo $PATH'
** Information type changed from Private to Public
** Changed in: gzip (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1825350
Titl
libnet-ssleay-perl 1.86 is currently at beta9 and that version
implements more comprehensive support for tls 1.3, including for example
exposing APIs needed to implement post-handshake-authentication
(changing client/server certs, post establishing a session, without
establishing a new session/conn
You are running a correct/ubuntu kernel, and otherwise things look up to
date.
But you do report the below
Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks
encountered in /var/lib/colord/icc, refusing.
Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks
well, libssl1.1 >= 1.1.1 is available from bionic-proposed, but not yet
from bionic-updates.
I guess we should not have yet published neon27 into bionic-updates, and
should probably keep the update in bionic-proposed for now.
** Tags added: regression-update
** Changed in: neon27 (Ubuntu)
On Tue, 26 Feb 2019 at 18:05, Matt P <1811...@bugs.launchpad.net> wrote:
>
> Okay. I guess I would have expected that if there was a dependency on a
> specific kernel version, that I wouldn't be able to install a package
> that wasn't compatible and breaks the system by installing a security
> upd
** Description changed:
+ [Impact]
+
+ * Too small dmsg kernel buf ring size leads to loosing/missing early
+ boot kernel messages which happen before journald starts slurping them
+ up and storing them on disc. This results in messages similar to this
+ one on boot "missed NN kernel messages on
Public bug reported:
[Impact]
* openssl has BUF_MEM regression that may affect packages at runtime.
* openssl has a regression of failing to initialize SSL context without
openssl.cnf file
[Test Case]
* Compile an old r-cran-openssl and run its autopkgtest against the
current & fixed openss
In unapproved
** Changed in: util-linux (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) =>
(unassigned)
** Changed in: ubuntu-power-systems
Assignee: Canonical Foundations Team (canonical-foundations) =>
(unassigned)
--
You received this bug notification becaus
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at lea
https://www.redhat.com/archives/libvir-list/2019-April/msg00987.html
--
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/1824810
Title:
use host uuid on kvm on power too
Statu
https://github.com/systemd/systemd/pull/12321
--
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/1824810
Title:
use host uuid on kvm on power too
Status in libvirt package in
Ack. Also DPM mode has LPAR UUID we should be using.
--
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/1824810
Title:
use host uuid on kvm on power too
Status in libvirt pac
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
*** 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
Touch seeded packages, which is subscrib
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/18143
*** 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
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
Touch seeded packages, which is subscribed to syste
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
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
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
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/1824342
Title:
in 19.04, default user cannot access system
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
Touch
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1824342
Title:
in 19.04, default user cannot access syst
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.ne
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
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
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1786940
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
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
** 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
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net
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
** Changed in: systemd (Ubuntu Disco)
Status: New => Fix Committed
--
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/1816812
Title:
desktop logout delays due to missin
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
** 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
** No longer affects: salt (Ubuntu)
** No longer affects: salt (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04
@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
** 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
** 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
Normally one should have plymouth installed, and fold code path
shouldn't be used.
Do you not have plymouth installed, and/or does it not work in you
environment?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubu
Also, cryptsetup uses Depends: busybox-static | busybox
and both of those variants have FOLD enabled.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1822730
Title:
Disco s
sigh, looks like initramfs-tools-core now depends on busybox-initramfs,
instead of using busybox nor busybox static.
** Changed in: busybox (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
** Changed in: openssl (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1822984
Title:
revert tls security level back to 1
** Changed in: openssl (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1822898
Title:
wget https://geoip.ubuntu.com/lookup
But equally, I would not want to keep cosmic more insecure than what
bionic and disco will be. And currently, cosmic is a release regression
w.r.t. bionic GA. Upgrading to newer releases, should not result in
looser acceptance of insecure protocols.
** Description changed:
[Impact]
* increase
** Also affects: openssl (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: openssl (Ubuntu Disco)
Status: New => Fix Committed
--
You received this bug notification because you ar
** Changed in: openssl (Ubuntu Disco)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1822984
Title:
revert tls security level back to 1
Public bug reported:
[Impact]
* increase minimum default tls security level from 0 to 1, as is the default
upstream
[Test Case]
* generate 80bits TLS certificate and attempt to use it
* with prior openssl it should work, but with this update it should fail
[Regression Potential]
* This incre
** Also affects: openssl (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: wget (Ubuntu)
** Bug watch added: Debian Bug tracker #926315
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926315
** Also affects: openssl (Debian) via
https://bugs.debian.org/cgi-bin/bu
Public bug reported:
wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i
with
Disabling SSL due to encountered errors
** Affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** Affects: tzsetup (Ubuntu)
Importance: Undecided
Status: New
** Af
Not sure if blake support is in TLS certificates.
I see many more constants for sha3, than for blake:
https://paste.ubuntu.com/p/gjzTwVTCBX/
did you try to use sha3-512 and did that work?
** Changed in: openssl (Ubuntu)
Status: New => Incomplete
--
You received this bug notification bec
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to
@manjo as you can see from launchpad and proposed-updates report it has
been synced 17h ago, built and stuck in disco-proposed with autopkgtest
regressions, and awaiting results for many more.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I have filed the usability issue of --disk-usage upstream at
https://github.com/systemd/systemd/issues/12063
** Bug watch added: github.com/systemd/systemd/issues #12063
https://github.com/systemd/systemd/issues/12063
** Summary changed:
- systemd journals take up too much space, aren't vacuu
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Incomplete
--
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/1798369
Title:
Reinstall Ubuntu (with preserving existing
I disagree with the title and description of the bug report.
Journald, calculates a hard limit on logs (based on the system
configuration).
$ journalctl -b -u systemd-journald.service -n 1
-- Logs begin at Mon 2018-09-17 14:21:50 BST, end at Thu 2019-03-21 15:16:25
GMT. --
Mar 21 11:27:37 ottawa
This PPA:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3681
Will soon have openssl-ibmca with above mentioned patch, built and
published.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https
This cannot be reproduced on 18.10, as on 18.10 openssh uses libssl1.0.0
package, yet openssl-ibmca is provided for libssl1.1 only.
In disco (19.04), openssh has been upgraded to use libssl1.1 with a
matching openssl-ibmca for libssl1.1.
If you want to reproduce this on 18.10, do add 'disco' repo
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
** 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
@ntyni excellent analysis! i like it a lot, and the patch is clean and
easy to understand.
Are you going to make a debian upload soon, or should I cherrypick that
for Ubuntu now?
** Also affects: perl (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924517
Importance: Unknown
** Also affects: systemd (Ubuntu Disco)
Importance: Low
Status: In Progress
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
On Tue, 12 Mar 2019 at 19:35, Seth Arnold <1797...@bugs.launchpad.net> wrote:
>
> On Tue, Mar 12, 2019 at 04:05:45PM -0000, Dimitri John Ledkov wrote:
> > defaults. And all of them however have committed to drop support for
> > those in 2020. My expectation is to foll
On Mon, 11 Mar 2019 at 21:20, Steve Langasek
wrote:
>
> Acceptance of openssl currently blocked on coverage of the (distro
> patch) OPENSSL_TLS_SECURITY_LEVEL change as part of the SRU template.
>
In Debian (but never ubuntu) they have bumped the default security
level from 1, to 2.
In Ubuntu, w
/etc/mke2fs.conf:
[defaults]
blocksize = 4096
[fs_types]
small = {
blocksize = 1024
inode_size = 128
inode_ratio = 4096
}
We default to 4k, unless one is formatting small filesystems which from manpage:
If the filesystem size
This is a well-known upstream issue/bug.
This is not s390x, Ubuntu 18.10, any other Ubuntu release specific.
There is no dataloss -> one can execute pvmove operation in reverse (or i guess
onto any 512 sector size PV) to mount the filesystems again.
Thus this is not critical at all.
Also, I am f
Ok, reproduced this on x86_64 with raw files which are in multiples of
4k.
This is not an architecture specific issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1817097
T
bah, mbrtowc claims to fail, tested that with C too, that works too.
And I cannot understand how perl XS stuff works. But it is fairly recent that
mbrtowc was started to be used.
See: 6de6aebdf89cb5abd8296cf686184e4b9461d11b
--
You received this bug notification because you are a member of Ubun
Sample C usage of mblen() appears to be fine, so libc is probably fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1818953
Title:
mblen() failing in Perl / Perl core dump
901 - 1000 of 2764 matches
Mail list logo
