** Changed in: php7.4 (Ubuntu Focal)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
** Changed in: php7.4 (Ubuntu Hirsute)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948880
Title:
libvirt should not use user tss for swtpm
To manage notifications about this bug go to:
** Changed in: libvirt-python (Ubuntu)
Milestone: ubuntu-21.11 => ubuntu-21.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946871
Title:
Merge libvirt-python from Debian unstable for 22.04
This should be ready'ish to upload in Debian now.
** Changed in: libvirt-dbus (Ubuntu)
Milestone: ubuntu-22.01 => ubuntu-21.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946870
Title:
Setting to fix committed until migration into -release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946871
Title:
Merge libvirt-python from Debian unstable for 22.04
To manage notifications
https://launchpad.net/ubuntu/+source/libvirt-python/7.9.0-0.1 exists now
** Changed in: libvirt-python (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package libvirt-python - 7.9.0-0.1
---
libvirt-python (7.9.0-0.1) unstable; urgency=medium
* Non-maintainer upload.
* New upstream release
(Closes: #997719)
-- Stefano Rivera Wed, 24 Nov 2021 20:02:38
-0400
** Changed in: libvirt-python (Ubuntu)
7.9.0-0.1 arrived and has
6 * Switch from nose to pytest, following upstream.
Which matches our
10 - d/t/control, d/t/smoke3: tests now use pytest
by that - this can be a sync
** Tags removed: needs-merge
** Tags added:
There is no movement upstream on this that would make a real fix
achievable near term.
I thought about sending the change to Debian, but since they are not
affected and 3.2 is around the corner (where things could be much
different for everyone again) this makes not much sense right now.
Instead
Focal
old
$ sudo apt install --reinstall qemu-user-static=1:4.2-3ubuntu6.18
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 21.3 MB of archives.
After this
FYI - the autopkgtest on lava was flaky and is now resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929926
Title:
[UBUNTU 21.10] qemu: target/s390x: Fix translation exception on
illegal
*** This bug is a duplicate of bug 1926122 ***
https://bugs.launchpad.net/bugs/1926122
Same as bug 1926122 just a slightly different signature
** This bug has been marked a duplicate of bug 1926122
Hi Ian,
If snap isn't supported/working in privileged containers that is a constraint
that is ok.
But while it is ok to "not work" since it is default installed in all images it
should at least not block all other activity in there (which blocking the full
boot is).
Could I ask for making
Thanks for accepting this @SRU Team
I added block-proposed-hirsute as outlined in the description.
Up to testing ...
** Tags added: block-proposed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Uploaded to F-unapproved, waiting for the SRU team to accept it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749393
Title:
sbrk() not working under qemu-user with a PIE-compiled binary?
To
Thanks, I agree and I guess if it really is a problem (I think not) then
the SRU team will speak up on review.
Uploaded to F/H-unapproved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929926
Title:
** Changed in: qemu (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: qemu (Ubuntu Focal)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: qemu (Ubuntu Focal)
Status: Won't Fix => In Progress
** Changed in: qemu (Ubuntu Hirsute)
Status: Won't Fix => In Progress
** Changed in: qemu (Ubuntu Focal)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: qemu (Ubunt
Test built in https://launchpad.net/~paelzer/+archive/ubuntu/gpsd-
lp1952229/+packages and uploaded to Jammy to unblock a few entangled
transitions.
Via the Debian PR we can make this a sync again later.
** Changed in: gpsd (Ubuntu)
Status: New => Fix Committed
--
You received this bug
SRU template updated, PPA rebuilt, Merge requests updated.
Also bundled another bug fix.
Waiting for MR review now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749393
Title:
sbrk() not working
Hi,
while there was no new insight for this bug you might try the builds in the
PPAs in bug 1749393 which fix a very similar issue on arm64. There it was
reproducible and we could identify the fix.
Maybe it is the same fix for you even if no one else could re-create your case
exactly.
It would
** Description changed:
[Impact]
- * A bad return in handling uretprobe makes qemu tcg to crash the probed
-application.
+ * A bad return in handling uretprobe makes qemu tcg to crash the probed
+ application.
- * Fix is small and upstream, backport as SRU to fix it in active
Ok, since you are ok with the alternative of GVT-g and other users have
SDL now I'll close this bug as incomplete (even though as stated in
comment 23 it isn't a real fix to the issues in the GTK backend for this
particular use case).
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
*** This bug is a duplicate of bug 1952246 ***
https://bugs.launchpad.net/bugs/1952246
Hi Masato, I think I have re-discovered that with more detail in bug 1952246
Still waiting for the kernel team to look at.
** This bug has been marked a duplicate of bug 1952246
5.13 (I/J/F-HWE) Hosts
FYI this was reported earlier as bug 1944104 and still waits kernel team action
there.
Since this bug here has more data/details I've marked the other a dup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
sorry this has fallen through the cracks, but bug 1928075 made me re-discover
it and it is time finally to complete that.
** Tags added: server-next
** Description changed:
[Impact]
- * The current space reserved can be too small and we can end up
-with no space at all for BRK.
*** This bug is a duplicate of bug 1749393 ***
https://bugs.launchpad.net/bugs/1749393
Bisect completed.
I deleted the PPAs as they are no more needed.
$ grep -e '^DEBUG' -e '^Com' bisect.log
DEBUG: saved as
'/home/ubuntu/qemu-aarch64-static.bisect.v4.2.0-1511-g381063d778'
DEBUG: latest
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952229
Title:
FTBFS in jammy - format not a string literal and no format arguments
To manage notifications about this bug
After being set up in the broken way we can run the test more quickly
$ sudo chroot /home/ubuntu/bullseye-arm64 /bin/sh /debootstrap/debootstrap
--second-stage
$ tail -n 1 /home/ubuntu/bullseye-arm64/debootstrap/debootstrap.log
This is repeatable and will as last line contain:
good case:
To complete the former tests:
fail - 1:4.2-3ubuntu6.19~focalppa2 = lp-1928075-qemu-static-builds-f-plusfix
Which confirms the former thought that it isn't about the binfmt changes
in debian/* but an upstream change.
I'll need some builds for that ...
P.S. somewhere in the back of my mind forms
Works - 1:5.0-5ubuntu9.10~focalppa2 = lp-1928075-qemu-static-builds-g-
minusfix
Since the debian/* is the same in regard to binfmt this might indicate a
fix in qemu git 4.2 .. 5.0
The other PPA still builds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Discussed in IRC and then reported upstream
https://trac.osgeo.org/postgis/ticket/5030#ticket
** Bug watch added: trac.osgeo.org/postgis/ #5030
https://trac.osgeo.org/postgis/ticket/5030
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
I can confirm your report and have tested it in Focal (1:4.15.2-5) and Jammy
(1:4.15.2-5build1) which both behave that way.
I want to thank you for taking the time to report this bug and helping
to make Ubuntu better. I appreciate the quality of this bug report and
I'm sure it'll be helpful
You are right Artyom and the ubunt-security Team also somewhat regularly
backports clamav.
That is how focal started with
0.102.2+dfsg-2ubuntu1
and nowadays has
0.103.2+dfsg-0ubuntu0.20.04.2
Assigning to ubuntu-security as they usually deal with this.
** Changed in: clamav (Ubuntu)
@Athos - this still is assigned to you, did you have a chance to look at
it, was it aborted for some reason, ... ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492212
Title:
postinst should
already in 1:4.2-3ubuntu5:
commit 8075687f92b6e177f646a9a7db8cfd63262d033aswitch binfmt registration
to use update-binfmts --[un]import (#866756)
Remaining fixes
commit 2a3a3f66c07e3ccae80115d994c627fe9df19880more binfmt-install updates
commit 9ce886cd819b1f9900b84c55f416977e8f418d27
Tests are ignored on almost all architectures already
ifneq (,$(filter $(DEB_BUILD_ARCH),mips mips64el mipsel s390x alpha hppa
hurd-i386 kfreebsd-i386 powerpc ppc64 sparc64))
e.g. s390x
./regress/core/mvt .. failed (diff expected obtained:
/tmp/pgis_reg/test_110_diff)
Using PPAs:
https://launchpad.net/~paelzer/+archive/ubuntu/lp-1928075-qemu-static-builds-h
https://launchpad.net/~paelzer/+archive/ubuntu/lp-1928075-qemu-static-builds-g
Test results:
works 1:6.0+dfsg-2expubuntu1.1~backport20.04-202111060014~ubuntu20.04.1
works 1:5.2+dfsg-9ubuntu3.3~focalppa1
Public bug reported:
FTBFS on ppc64 as synced over from Debian
=> https://launchpad.net/ubuntu/+source/postgis/3.1.4+dfsg-3build1
Failing log:
https://launchpadlibrarian.net/569861170/buildlog_ubuntu-jammy-ppc64el.postgis_3.1.4+dfsg-3build1_BUILDING.txt.gz
The same built fine in Debian
=>
FYI it does not depend on Everyone is waiting btw
$ lxc exec testkvm-jammy-from -- cloud-init status --wait
.
$ lxc exec testkvm-jammy-from systemctl is-system-running
starting
--
You received this bug notification
Today I found another test system blocked by the same, this time x86
Bionic.
It runs 18.04 HWE
$ uname -a
Linux torkoal 5.4.0-90-generic #101~18.04.1-Ubuntu SMP Fri Oct 22 09:25:04 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
LXD is on latest/stable (4.20 right now)
In that environment - again -
Hi Frank,
I was trying to grasp the exact details that you are describing and giving this
another repro run. You are saying
bullseye armhf chroot @ focal on an x86 host
is failing for you, correct?
Note: We have just fixed a similar (only on the surface of it) issue in
Impish (bug 1947860).
Comment #6 looks like an incomplete quote of comment #4, please double
check what you wanted to answer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932522
Title:
[22.04 FEAT] New package
** Description changed:
[Impact]
- When certain code paths where an ErrorException should be raised, php
- will enter an infinite loop, which could possibly lead to having the
- process and a web server connection hanging.
+ When an ErrorException is raised on certain code paths, php will
Messing around with someone elses crypto functions rarely is good ;-)
So I reported it Upstream at the skiboot project as:
=> https://github.com/open-power/skiboot/issues/271
** Bug watch added: github.com/open-power/skiboot/issues #271
https://github.com/open-power/skiboot/issues/271
**
** Tags added: transition-openssl3-jj
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952448
Title:
qemu 1:6.0+dfsg-2expubuntu2: Fail to build against OpenSSL 3.0
To manage notifications about this
https://launchpad.net/ubuntu/+source/nbd/1:3.23-3 worked and migrated
** Changed in: nbd (Ubuntu)
Status: Confirmed => 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/1951839
** Also affects: ldc (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000431
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951845
Now that all data is in place I set it to confirmed to silence the bots.
@Kernel people - is this known, if so where? If it is not known what else would
you need here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since it seems to depend on the host it likely is the chip, so here some info
about that.
This is the bad system.
** Attachment added: "cpuinfo-badsystem.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952246/+attachment/5543370/+files/cpuinfo-badsystem.txt
--
You received this
Since it seems to depend on the host it likely is the chip, so here some info
about that.
This is the good system.
** Attachment added: "cpuinfo-goodsystem.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952246/+attachment/5543371/+files/cpuinfo-goodsystem.txt
** Changed in:
Now I have completed attaching (apport-collect) data of both:
- Host (hostname: node-horse)
- first level guest (hostname: f)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
Title:
5.13
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543369/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543367/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543368/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543366/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543365/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543364/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543363/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543362/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543359/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543361/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543358/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543360/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543356/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543357/+files/acpidump.txt
** Description changed:
Issue - on start the second level Guest enters paused state due to a KVM
fail:
$ sudo cat
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543355/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543354/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543353/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543352/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543349/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543351/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543350/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543348/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543346/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543347/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543345/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543344/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1952246/+attachment/5543343/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952246
Title:
5.13
Public bug reported:
Issue - on start the second level Guest enters paused state due to a KVM
fail:
$ sudo cat /var/log/libvirt/qemu/focal-2nd-lvm-test.log
...
KVM: entry failed, hardware error 0x7
EAX= EBX= ECX= EDX=0663
ESI= EDI= EBP=
*** This bug is a duplicate of bug 1951943 ***
https://bugs.launchpad.net/bugs/1951943
This issue will be fixed in openssl via bug 1951943
Closing this one as a dup.
** Changed in: bind9 (Ubuntu)
Assignee: Miriam España Acebal (mirespace) => (unassigned)
** Changed in: bind9-libs
** Changed in: dnsmasq (Ubuntu)
Assignee: Miriam España Acebal (mirespace) => (unassigned)
** Changed in: dnsmasq (Ubuntu Bionic)
Assignee: Miriam España Acebal (mirespace) => (unassigned)
** Changed in: dnsmasq (Ubuntu Focal)
Assignee: Miriam España Acebal (mirespace) =>
Public bug reported:
This is an FTBFS in jammy atm
https://launchpadlibrarian.net/569860174/buildlog_ubuntu-jammy-arm64.gpsd_3.22-4build1_BUILDING.txt.gz
The same affected Debian, their bug is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997178
I have tested and submitted the fix there
We all wanted to have a look, this is what I found:
boost/boost1.74-1.74.0/tools/quickbook/build/warning-check:5:tmpfile=$(tempfile)
That is in jammy's current 1.74.0-13ubuntu1 but only referenced for travis runs
(of the doc build).
Worth a task to check in detail, but unlikely to need a fix.
Regression tests completed as well on x86 and s390x
I only had:
- 8 fails in known-flaky tests which re-ran and worked fine.
- x86 second level VMs failed to start (But tests confirmed that this is not
related to this upload)
- needed some fixup for LXD 4.20 behavior
The other slightly more than
** Changed in: ldc (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/1951845
Title:
1.28.0-1 FTBFS in Jammy - libldc-jit.so not built
To manage
** Changed in: rss-glx (Ubuntu)
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/1951968
Title:
FTBFS in Jammy error: ‘size_t’ does not name a type
To manage
** Changed in: monitoring-plugins (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940916
Title:
Incorrectly excludes tmpfs
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
** Changed in: bind9-libs (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: librabbitmq (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951102
Title:
librabbitmq calls
** Changed in: freeradius (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951099
Title:
freeradius calls
** Changed in: nginx (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948699
Title:
Please enable luajit for arm64
To manage notifications about this
** Changed in: dnsmasq (Ubuntu Bionic)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639452
Title:
systemd ExecStartPre test config
> It's suitable to run in a single VM. I'll create a PR soon.
Nice, that will help to catch changes in other packages impacting
wireguard to be spotted early on.
BTW - the MIR team discussion has come to the conclusion that we can
and want to have it along with the functionality that exists in
Synced, but needs to migrate to be fully fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946890
Title:
Merge python-django from Debian unstable for 22.04
To manage notifications about this
This bug was fixed in the package python-django - 2:3.2.9-2
---
python-django (2:3.2.9-2) unstable; urgency=medium
* Team upload.
* Fix __in lookup crash when combining with filtered aggregates.
Fix for: https://code.djangoproject.com/ticket/32690
This issue affects
Public bug reported:
This seems like the return of the giant hogweed, ... umm bug 1944004 I
meant.
The twist is that it only happens with some conditions met:
Constraints that I found from my testing so far:
1. Fails on s390x, but not on x86 (but that was Focal host, see #4)
2. Fails on
Thank you Steve, uploaded that to Jammy now to un-break the version in
-proposed.
** Changed in: libvirt (Ubuntu)
Status: New => Fix Committed
** Tags added: server-next
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You re
I'm happy that you are fine with it Patrick, but I want it resolve now.
While sleeping about that I think I found what is missing/broken and needs
evaluation.
As I said the libvirt group was considered insecure and therefore the new group
add is different.
But on upgrade to Bionic that should
** Changed in: raqm (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951069
Title:
[MIR] raqm
To manage notifications about this bug
1001 - 1100 of 10122 matches
Mail list logo
