** Changed in: pycryptodome (Ubuntu)
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/1904987
Title:
Please add this package to i386-whitelist
To manage no
This looks similar to bug #1904633
** Tags added: fr-960
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905156
Title:
netplan KeyError with gretap in bridge
To manage notifications about this bug
This looks kind of similar to LP: #1888726
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904549
Title:
MTU is not set on vlan interface
To manage notifications about this bug go to:
https://bugs.l
I can confirm this is now working with hirsute images on MAAS 2.9.0~rc3,
not using any additional PPAs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898997
Title:
MAAS cannot deploy/boot if OVS br
I think this should actually already be fixed upstream via
https://github.com/CanonicalLtd/netplan/pull/163 where the tunnel
interfaces were added to the python parser (configmanager.py). I will
prepare a test-case to make sure it always works in the future.
--
You received this bug notification
test case and extra protection here:
https://github.com/CanonicalLtd/netplan/pull/172
** Changed in: netplan
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905156
Titl
Both autopkgtest regressions have turned out to be intermittent failures
and have been resolved by retriggering the corresponding tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903814
Title:
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
** Changed in: netplan.io (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.launchp
** Changed in: rmatrix (Ubuntu)
Status: New => Fix Released
** Changed in: r-cran-matrixstats (Ubuntu)
Status: New => Fix Released
** Changed in: r-bioc-s4vectors (Ubuntu)
Status: New => Fix Released
** Changed in: r-bioc-rhdf5lib (Ubuntu)
Status: New => Fix Released
The new io.netplan.Netplan.Generate() DBus API has been implemented in netplan
upstream:
https://github.com/canonical/netplan/pull/208
https://github.com/canonical/netplan/pull/209
It needs to be released and SRUed down to Bionic for the snapd change to
be accepted (https://github.com/snapcore/sn
** Also affects: dbus (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: accountsservice (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Tags added: rls-ff-incomin
LGTM, thanks for the debdiff!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919451
Title:
Update (python-)zhmcclient to latest release
To manage notifications about this bug go to:
https://bugs.la
After crushing the logs a bit more, I found a few interesting things and
also have a few open questions. Thank you very much for your `date`
timestamps in between the different steps, those are very helpful in
linking the order of events!
Open questions:
1) The "udevadm-monitor.txt" log shows that
Looks like I can at least reproduce the issue on an arm64 Canonistack
machine, utilizing an armhf container:
ubuntu@focal-arm64:~$ time autopkgtest systemd --test-name=boot-and-services -U
-- lxd autopkgtest/ubuntu/impish/armhf
[...]
autopkgtest [15:59:21]: test boot-and-services: [--
> Gave some time between netplan apply and check without success, I can leave
> it for
> hours and the IP never gets assigned
Indeed, I cannot see it being assigned an IPv4 address in your latest
"_delay" run. (Well, there is some assignment of an IP to enP53p0s0.171
at 15:05:29 in the journal lo
Thank you! The core problem still is that systemd-networkd does not find
any .link and .network file for the enP53p0s0.171 interface, that's why
it cannot apply any configuration (IP address):
> ? 9: enP53p0s0.171
> Link File: n/a
> Network File: n/a
This might very well be related to the additio
So I can reproduce the problem even locally, using a simple:
`autopkgtest systemd --test-name=boot-and-services -- lxd
autopkgtest/ubuntu/impish/amd64`
When logging into the (stalled) system, while it is waiting for its
timeout I can see that eth0 gets configured, but then put in DOWN state.
Ther
** Also affects: lxd (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/1931088
Title:
boot-and-services tests fails in impish on armhf (248.3)
To ma
This should fix the problem:
https://github.com/lxc/distrobuilder/pull/476
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931088
Title:
boot-and-services tests fails in impish on armhf (248.3)
To m
*** This bug is a duplicate of bug 1931088 ***
https://bugs.launchpad.net/bugs/1931088
** This bug has been marked a duplicate of bug 1931088
boot-and-services tests fails in impish on armhf (248.3)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: systemd (Ubuntu Impish)
Status: Confirmed => Invalid
** Changed in: lxd (Ubuntu Impish)
Status: New => Fix Committed
** Changed in: lxd (Ubuntu Impish)
Assignee: (unassigned) => Lukas Märdian (slyon)
** Changed in: auto-package-testing
Status: I
An interesting observation I made is that all journal logs (in this LP
bug and the upstream systemd bug) show the "polkit.service: Unexpected
error response from GetNameOwner(): Connection terminated" message, in
addition to a bunch of other "Connection terminated" errors from
changing services acr
** Changed in: lxd (Ubuntu Impish)
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/1931088
Title:
boot-and-services tests fails in impish on armhf (248.3)
** Changed in: netplan.io (Ubuntu)
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/1922126
Title:
autopkgtest fails in hirsute on some architectrures
To manage not
Public bug reported:
Include latest version of s390-tools 2.17.0 related to kernel 5.12+
v2.17.0 was just released:
https://github.com/ibm-s390-linux/s390-tools/releases/tag/v2.17.0
** Affects: s390-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: rls-ii-incoming
** Als
** Summary changed:
- networkd-dispatcher gives corrupted information
+ [SRU] networkd-dispatcher gives corrupted information
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
[SRU] netw
** Description changed:
+ [Impact]
+
+ * Due to changes in systemd's networkctl output networkd-dispatcher 2.0
contains a bug, producing invalid keys/values inside the JSON it provides to
its scripts
+ * e.g.: json={"A": ["ress: 119.224.106.22 (DHCP4)"], ...}
+ * Therefore the scripts cannot
** Changed in: networkd-dispatcher (Ubuntu Hirsute)
Status: Fix Released => Triaged
** Also affects: networkd-dispatcher (Ubuntu Impish)
Importance: High
Status: Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Thank you! This one is looking pretty solid overall.
But I think the "hex detection" has some flaws, as it only checks for capital
letters and there is a discrepancy between accepting float hex numbers (which
is unexpected IMO) but rejecting float octal numbers.
Could you please test for some mo
Fixed in 0.10-15ubuntu1
** Changed in: baycomepp (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/bugs/1925212
Title:
FTBFS with GCC-11
To manage notifications
Works again, since we changed it back to NOT being in `big_packages`.
** Changed in: netplan.io (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/bugs/1922126
Title
ACK.
I've drafted some code a while ago which will improve this situation:
https://github.com/canonical/netplan/pull/204
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922126
Title:
autopkgtest fail
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-groovy verification-done-hirsute
** Tags removed: verification-done-groovy
** Tags added: verification-needed-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I re-verified the Groovy SRU (0.102-0ubuntu1~20.10.3) and updated the
corresponding test logs for Groovy in the bug description. The logs are
the same as in LP: #1922898 (same package, version & tests).
All tests passed on first run.
** Description changed:
[Impact]
This release contains bot
** Description changed:
[Impact]
This release contains a regression bug-fix for un-breaking the ABI
compatibility between libnetplan 0.102 and netplan.io 0.101, which was taken
from a pending upstream pull request:
https://github.com/canonical/netplan/pull/206 (d/patches/fix-lp1922898)
I verified the Groovy SRU (for 0.102-0ubuntu1~20.10.3) and attached the
corresponding test logs to the bug description.
Furthermore, I've verified the regression case, where libnetplan0 v0.102
is used with the netplan.io "generate" binary v0.101, which also passes
(i.e. does not crash anymore):
r
Public bug reported:
Removal request
---
Please remove the "jack-rack" source package from the archive. It blocks
the python2-rm transition, has been removed from Debian testing/unstable
and seems rather unmaintained upstream.
The binary package names are:
jack-rack
The (release) ar
This bug was fixed in the package python-pyscss - 1.3.7-3
Sponsored for Logan Rosen (logan)
---
python-pyscss (1.3.7-3) unstable; urgency=medium
* Team upload.
* d/control: Update Maintainer field with new Debian Python Team
contact address.
* d/control: Update Vcs-* fields
I agree. The Debian package contains all relevant changes from Ubuntu
and is in better shape.
** Changed in: python-pyscss (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.launch
LGTM. And I confirmed it fixes the build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923626
Title:
Mismatch error in test_barbican.py
To manage notifications about this bug go to:
https://bugs.
This bug was fixed in the package cdrkit - 9:1.1.11-3.2
Sponsored for Dave Jones (waveform)
---
cdrkit (9:1.1.11-3.2) unstable; urgency=medium
* Non-maintainer upload.
* debian/patches: Apply patch from Fedora to fix build with GCC 10 (Closes:
#957074)
-- Sebastian Ramacher
Thanks!
$ syncpackage -f -V 9:1.1.11-3.2 -b 1927944 -s waveform cdrkit
Source cdrkit -> impish/Proposed: current version 9:1.1.11-3.1ubuntu2, new
version 9:1.1.11-3.2
Using existing file cdrkit_1.1.11-3.2.dsc
Using existing file cdrkit_1.1.11-3.1ubuntu2.dsc
Using existing file cdrkit_1.1.11-3.2.d
Thank you, LGTM!
$ dput ubuntu ../db5.3_5.3.28+dfsg1-0.8ubuntu1_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: ../db5.3_5.3.28+dfsg1-0.8ubuntu1_source.changes: Valid signature from
5889C17AB1C8D890
Checking signature on .dsc
gpg: ../db5.3_5.3.28+dfsg1-0.8ubuntu1.dsc:
** Changed in: db5.3 (Ubuntu)
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/1927978
Title:
Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
To manage not
Hello Szilard,
I don't think this is related to the netplan project, thus I'm marking
it invalid and re-assigning it to the cdimage-rootfs project instead.
I'm not sure if that is the correct place for this feature request, so
feel free to re-assign to a better suited project.
Lukas
** Also affe
** Also affects: netplan.io (Ubuntu Hirsute)
Importance: Undecided
Status: Fix Released
** Also affects: netplan.io (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu Groovy)
Status: New => Confirmed
** Changed in: netplan
Status
Defining the netplan.io -> libnetplan0 dependency as "libnetplan0 (=
${binary:Version})" makes it work for this specific "unattended-upgrade
case", but unfortunately the regression is more generic than that...
There are some other consumers of libnetplan0, such as the
NetworkManager snap on Ubuntu
Previous fix in Hirsute is not enough, so I'm resetting it to "Triaged".
** Changed in: netplan.io (Ubuntu Hirsute)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
+ [Impact]
+ This release contains a regression bug-fix for un-breaking the ABI
compatibility between libnetplan 0.102 and netplan.io 0.101, which was taken
from a pending upstream pull request:
https://github.com/canonical/netplan/pull/206 (d/patches/fix-lp1922898)
+
+
Public bug reported:
Removal request
---
Please remove the "aws-shell" source package from the archive. It fails
to build from scratch, has been removed from Debian testing and seems
rather unmaintained upstream.
The FTBFS failure has been reported upstream: https://github.com/awslab
Public bug reported:
bayecomepp failed to build from scratch in the latest archive rebuild, using
GCC-11:
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210325-hirsute-hirsute.html
Attached is a patch for fixing the problem, which should be uploaded
after the Hirsute final freeze
Public bug reported:
Upstream badger does not have good support for 32bit architectures, therefore
the armhf binary was removed in Groovy. See:
https://pad.lv/1884753
https://github.com/dgraph-io/badger/issues/1384
This bug is here for reference of the 32bit FTBFS issue, so we do not
re-investig
** Bug watch added: Debian Bug tracker #987250
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987250
** Also affects: baycomepp (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987250
Importance: Unknown
Status: Unknown
--
You received this bug notification becau
** Description changed:
[Impact]
This release contains a regression bug-fix for un-breaking the ABI
compatibility between libnetplan 0.102 and netplan.io 0.101, which was taken
from a pending upstream pull request:
https://github.com/canonical/netplan/pull/206 (d/patches/fix-lp1922898)
** Description changed:
[Impact]
This release contains both bug-fixes and new features and we would like to
make sure all of our supported customers have access to those improvements.
The most notable changes (besides usual bug-fixes) incoming in 0.102:
- New API for NetworkManager YAM
I re-verified the Focal SRU (0.102-0ubuntu1~20.04.2) and updated the
corresponding test logs for Focal in the bug description. The logs are
the same as in LP: #1922898 (same package, version & tests).
All tests passed on first run.
** Tags removed: verification-needed-focal
** Tags added: verific
Thank you very much Brian, for quickly accepting the regression fix into
focal-proposed!
I verified the Focal SRU (for 0.102-0ubuntu1~20.04.2) and attached the
corresponding test logs to the bug description.
Furthermore, I've verified the regression case, where libnetplan0 v0.102
is used with the
The build failure is fixed in Debian, but it requires a complex merge, including
special handling of s390x instruction set and cross-compilation of Z14 on Z13.
Also, there are some incompatibilities between the new debhelper-compat 13 and
the previous dh-exec logic.
I prepared a merge from Debian
** Tags added: verification-needed-hirsute
** Changed in: netplan.io (Ubuntu Hirsute)
Status: Triaged => 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/1922898
Title:
[SRU] SEGF
Thanks William, this LGTM now!
I've modified your debian/changelog and the XML/man pages a bit, to
account for the removed handling of floating point numbers. And uploaded
the package.
$ dput ubuntu ../shadow_4.8.1-1ubuntu9_source.changes
D: Setting host argument.
Checking signature on .changes
g
** Changed in: networkd-dispatcher (Ubuntu Hirsute)
Status: Triaged => In Progress
** Changed in: networkd-dispatcher (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Thank you very much for providing the debdiffs!
They are looking good so far.
In the -signed package, you wouldn't even need to adopt the s390-tools-
zkey version manually as that would be generated from debian/control.in
But it's perfectly fine doing it this way as well!
For s390-tools I have a
Hello Brian,
thank you for accepting it into hirsute-proposed. I tested networkd-
dispatcher 2.1-2~ubuntu21.04.1 and can confirm the bug is fixed:
# dpkg -l | grep systemd
ii systemd 247.3-3ubuntu3.1
# networkctl status eth0
● 149: eth0
This bug does not happen for Bionic, as the networkctl output was only
changed in systemd v244 while Bionic is on v237.
** Changed in: networkd-dispatcher (Ubuntu Bionic)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Description changed:
[Impact]
- * Due to changes in systemd's networkctl output networkd-dispatcher 2.0
contains a bug, producing invalid keys/values inside the JSON it provides to
its scripts
- * e.g.: json={"A": ["ress: 119.224.106.22 (DHCP4)"], ...}
- * Therefore the scripts cannot
Thanks, uploaded!
** Changed in: s390-tools (Ubuntu Impish)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934988
Title:
Upgrade s390-tools to latest version
Hello Brian,
thank you for accepting it into focal-proposed. I tested networkd-
dispatcher 2.1-2~ubuntu20.04.1 and can confirm the bug is fixed:
# dpkg -l | grep systemd
ii systemd 245.4-4ubuntu3.7
# networkctl status eth0
● 258: eth0
Thanks, I've sponsored the HH & FF uploads.
** Changed in: shadow (Ubuntu Focal)
Status: Fix Committed => In Progress
** Changed in: shadow (Ubuntu Hirsute)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The nm-online util does not return successfully as of 1.32.2-0ubuntu1
(currently in impish-proposed).
systemd VS network-manager autopkgtests (in LXD) fail, because the
autopkgtest-virt-lxd runner tries to wait for "network ready" before it
is reconnecting after a reboot. Thi
Related to: LP: #1914062
Two patches exist, both were dropped from their corresponding packages:
https://git.launchpad.net/network-manager/commit/?id=4c4f7172
https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?h=ubuntu-
impish&id=efebddfe37efff6a259ef7fd59212d65ad1b848b
It looks like this error happens when the package is only available in
-proposed, but not the release pocket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860672
Title:
Autopkgtest failing badly s
Upstream patch: https://github.com/ibm-s390-linux/s390-tools/pull/117
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935666
Title:
s390-tools FTBFS when built with libfuse3-dev
To manage notificati
** Bug watch added: Debian Bug tracker #895342
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895342
** Also affects: suricata (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895342
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
This should have been fixed upstream by:
https://github.com/systemd/systemd/pull/18559
Or https://github.com/systemd/systemd/pull/18684 and
https://github.com/systemd/systemd/pull/18717 respectively. I wonder why
this fix isn't working for network-manager, while it seems to be good
for LXD?
--
Y
After reading a bit more about this issue, I can see where the conflict
happens:
1/ systemd requires any container manager to mount /sys read-only,
according to https://systemd.io/CONTAINER_INTERFACE/ in order to make
udevd behave properly.
2/ NetworkManager checks for /sys to be read-only in ord
After enabling the unified cgroups hierarchy in systemd and running some
tests, I can confirm that most things are working as expected, except
for snapd.
https://bileto.ubuntu.com/excuses/4602/impish.html
The Bileto autopkgtests show (ignoring two unrelated/flaky failures in
universe packages: su
Thank you for providing a patch! That patch looks straight forward and
(almost) resembles the upstream change, obviously missing the parts that
do not yet exist in systemd v245.
The only other thing I found missing is an upstream change in
src/resolve/resolved-dns-transaction.c:
```
static void
** Patch added: "Focal"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5512235/+files/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd
systemd v248 as can be found in Impish already contains the upstream
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications about this bu
Public bug reported:
basic.target waits for dbus.socket (via sockets.target) AND dbus.socket
waits for basic.target, too, delaying dbus-daemon startup. At some point
a timeout happens, dbus is started and all queued services try to start
registering to the bus at the same time.
All services regis
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936948
Title:
Dependency loop via sockets.target
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Patch added: "Hirsute"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5512243/+files/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Description changed:
- systemd-resolve keep crashing and it is very annoying as sometimes it
- severely interrupt normal dns resolving.
+ [Impact]
+
+ * systemd-resolved stops replying to clients on the local LAN.
+ * logging segfault crashes in dmesg:
+ [836786.046514] systemd-resolve[87200
** Also affects: zhmcclient (Ubuntu Focal)
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/1919451
Title:
Update (python-)zhmcclient to latest release
To m
** Description changed:
+ [Impact]
+
+ In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM LinuxONE
+ III (or newer) machines/LPARs from within a MAAS controller, the
+ python3-zhmcclient libraray (>= v0.29) is needed, to provide all the
+ functions required for controlling the HMC.
+
** Description changed:
[Impact]
In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM LinuxONE
III (or newer) machines/LPARs from within a MAAS controller, the
python3-zhmcclient libraray (>= v0.29) is needed, to provide all the
functions required for controlling the HMC.
** Changed in: zhmcclient (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919451
Title:
Update (python-)zhmcclient to latest release
To manage notifi
** Description changed:
[Impact]
In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM LinuxONE
III (or newer) machines/LPARs from within a MAAS controller, the
python3-zhmcclient libraray (>= v0.29) is needed, to provide all the
functions required for controlling the HMC.
Public bug reported:
Neither phoc 0.6.0 nor 0.8.0 (from Debian experimental) seem to be
compatible with wlroots 0.13, yet. There are some upstream patches being
worked on: https://source.puri.sm/Librem5/phoc/-/merge_requests/241/
** Affects: phoc (Ubuntu)
Importance: Undecided
Statu
** Also affects: wlroots (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/1938404
Title:
Phoc is not (yet) compatible with wlroots >= 0.13
To manag
Denys, what kind of MDNS traffic is flowing in your network? I'm not
really able to reproduce the problem locally. Maybe I'm missing this
special network packets?
Have you already been able to find out what triggers the issue for you?
--
You received this bug notification because you are a membe
** Changed in: user-setup (Ubuntu)
Status: In Progress => Fix Committed
** Tags removed: 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/1902533
Title:
Please merge user-setup 1
Public bug reported:
Please merge s390-tools 2.14.0-2 (main) from Debian unstable (main)
Also upload s390-tools-signed 2.14.0-2ubuntu1 afterwards.
Debdiff: https://paste.ubuntu.com/p/NtTYKQ7k6q/
** Affects: s390-tools (Ubuntu)
Importance: Undecided
Assignee: Lukas Märdian (slyon
Hi Bruno, you can call `dpkg -l | grep netplan` to see the installed
version. Netplan 0.100 is available in Ubuntu Focal 20.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743200
Title:
No su
Thanks for the upload!
Would you mind to also push the corresponding `s390-tools-signed` debdiff from
the bug description above?
** Changed in: s390-tools (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Doing some experiments this seems to be working with netplan.io 0.100 in
Groovy. No matter if 'match.macaddress' is set or not on my local eth
interface.
As far as I can tell the fix was released with netplan 0.99 in Focal
final and was SRU'ed to Bionic as well.
(https://github.com/CanonicalLtd/ne
** Changed in: s390-tools (Ubuntu)
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/1903688
Title:
Please merge s390-tools 2.14.0-2 (main) from Debian unsta
The 'zkey list' command does not seem to be available in Bionic. Also
the patched zkey/keystore.c file does not exist in s390-tools v2.3.0, so
it looks like this bug isn't available either:
ubuntu@juju-96c787-test-0:~$ zkey list
zkey: Invalid command 'list'
Try 'zkey --help' for more information.
The 'zkey list' command does not seem to be available in Bionic
(s390-tools v2.3.0), so it looks like this bug isn't available either:
ubuntu@juju-96c787-test-0:~$ zkey list
zkey: Invalid command 'list'
Try 'zkey --help' for more information.
ubuntu@juju-96c787-test-0:~$ zkey --help
Usage: zkey CO
** Changed in: s390-tools (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/bugs/1865032
Title:
[UBUNTU] zipl/libc: Fix potential buffer overflow in printf
1 - 100 of 1563 matches
Mail list logo
