Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Hi Paul,
Bugs in launchpad are filed against source packages, and "src:kvm" doesn't
exist for more than 8 years now :-) Instead you'd want to file it against the
package the code is in, in your case most likely src:qemu [1] or src:linux [2].
Also you should talk about the target Ubuntu release
Summary for postgresql-mysql-fdw:
1. mysql-fdw needs >=2.7 for compatibility with postgresql-14 [1].
2. The new version adds tests (independent to PG-14) that fail on 32 bit
platforms like armhf [2][3]
3. Currently these test issues block proposed migration of the new version
Right now upstream
Hi,
yes the security fixes in
https://launchpad.net/ubuntu/+source/samba/2:4.7.6+dfsg~ubuntu-0ubuntu2.26
might have affected that. Thanks Lorenzo for already identifying a candidate
and a config based workaround.
Assigning to security-team to have a look (as usual) at update
regressions.
**
I was happy for a second as I thought I found a related case, but this
is the very same case on askubuntu [1], so no more insights from there.
[1]: https://askubuntu.com/questions/1377700/ubuntu-20-04-3-nginx-
crashes-with-segfault
--
You received this bug notification because you are a member
Hi Bernd,
For your issues with apport-retrace, yes it should download the files it needs,
but in your case seems to fail for permission issues. Could you mabe just try
it with sudo and rebuild instead of a direct binary path like:
$ sudo apport-retrace --sandbox system --rebuild-package-info
Summary on postgresql-13
reverse dependencies are a bit tricky as some binary names transition to the
new source (like libpq-dev, libpq5) while others get new versioned names like
postgresql-13 -> postgresql-14.
Out of the following we can derive the list of binary packages we need to check:
I have experimented with glom a bit and the summary for now is:
1. it also fails in Debian, I filed bug [3]
2. it is a FTBFS regression in release independent to postgres
3. The newer glom 1.32 fails as well, Desktop let me know that it would need
the not yet packaged libxml++3.0
4. In a
Hi Bert,
thanks for the extra info.
I'm still confused by "Ubuntu 21.10+Virtualbox 6.1.30 run on the bare metal a
Ryzen 3 2200G" vs "highest level is always Ubuntu 14.04". Probably a
terminology thing what in virtualization is up and down :-)
Let me try to make sense of it :-)
So are we
Public bug reported:
With the postgresql-14 transition in bug 1949579 done we want to clean
up the remainders of the former version.
Once things are ready I'll update this and ask the AAs for the removals,
for now this tracks the effort to resolve the last few steps needed for
that.
TODO:
- get
postgresql-14 | 14.1-1ubuntu1 | jammy | source, amd64, arm64, armhf, ppc64el,
riscv64, s390x
postgresql-common | 234 | jammy | source, all
This is complete.
The cleanup will be getting glom to build as then we can remove
src:postgresql-13 tracked in bug 1954374
** Changed
Status => Incomplete until the agreed required TODOs are resolved.
Then ready for promotion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951066
Title:
[MIR] dh-elpa
To manage notifications
of the UI for extra checks
- no translation present, but none needed for this case (dev only)
** Changed in: dh-elpa (Ubuntu)
Status: New => Incomplete
** Changed in: dh-elpa (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification becau
pgsql-ogr-fdw@amd64 migration-reference/0 (was auto-scheduled it seems) is bad
as expected.
That should (tm) have been the last blocker.
Maybe I need to check installability in update_output after the next
run, I didn't do so so far ...
--
You received this bug notification because you are a
FYI: The debdiff really LGTM to resolve most of the weak points
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951066
Title:
[MIR] dh-elpa
To manage notifications about this bug go to:
python-sqlalchemy-utils fully resolved now
Now excuses lists the amd64 variant of pgsql-ogr-fdw as failing (it didn't
before)
https://autopkgtest.ubuntu.com/packages/p/pgsql-ogr-fdw/jammy/amd64
Here (as on the other architectures) a migration-reference run is running,
assuming that fails like
FYI: Pulling also dh-elpa would trigger a bunch of further dependencies
in universe, so this really is a no.go: libdebian-source-perl, dh-make-
perl, emacs-nox, libarray-utils-perl, libconfig-tiny-perl
But since you already said dh-elpa-helper is enough I'll focus on that
--
You received this
- no translation present, but none needed for this case
** Changed in: python-asgiref (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Thanks to RAOF the postgresql-server-dev-1 -> llvm issue is resolved.
python-sqlalchemy-utils was a test on an old version 0.36.8-2ubuntu2 failing
when openssl3 migrated. There now is a merge of the new version 0.37.8-1ubuntu1
with new tests.
Migration reference runs with that new version
Hi,
so to be sure to get it right. This is:
slow: BareMetal -> Ubuntu ??.?? -> Virtualbox -> Ubuntu 22.04
fast: BareMetal -> Ubuntu ??.?? -> Virtualbox -> Ubuntu before 22.04
That matches the screenshots, but not the description you gave.
So there must be something wrong here - I fail to see in
python-sqlalchemy-utils was not shown before, but now is a test fail for
postgresql-common
About the dependency to llvm-11-dev, clang-11.
Two things to know here, first of all that will sooner or later be llvm-13 due
to [1].
But right now there is an issue around s390x that blocks this:
Thank you,
it seems its llvm-11 dependency (incompatible with 13 on s390x, being worked on
in Debian) still prevents migration to -release. I'll have a more detailed look
tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548486
Title:
Sleep hook in a subdirectory ignored but causes double execution of
previous hook
To manage
sqlalchemy worked out as expected, some tests are still in the queue but
others completed.
** No longer affects: sqlalchemy-i18n (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949579
All other entries on the transition tracker that are left are false
positives AFAICS.
Thereby all that is left I'm aware of is glom, which I found to be an FTBFS
(independent to postgresql-14). The work on glom can continue after
postgresql-14 migrates as we do not immediately remove
sqlalchemy was a case of re-debugging, I'll skip all the details, it
essentially is the same as:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997086
That works for us as well, but the version was an FTBFS - on all PPA and local
tests that I had for the tests I used 1.0.1 already - so it
Note: this is related to bug https://bugs.launchpad.net/bugs/1953334
It shares the motivation and the test steps.
Both fixes can exists along (no hard version requirement needed in he uploads)
but only when both are together it can fully work.
--
You received this bug notification because you
Status update:
- Both removals got resolved
- sqlalchemy-i18n still has issues, but seems to be a flaky heisenbug
(any debug I add makes it work fine)
- next to resolve is glom, it still has a dependency to postgresql-13 but it
FTBFS right now.
In Debian [1] it worked to pick up PG-14, both
We assigned James as MIR reviewer as he usually takes yours, please let
us know if that does not work fro any reason and in that case unassign
him please.
** Changed in: python-xmlschema (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification
** Changed in: libdecor-0 (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952130
Title:
[MIR] libdecor-0
To manage notifications about
** Changed in: dh-elpa (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: cmake (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to cmake in Ubuntu.
** Changed in: pipewire-media-session (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/1952924
Title:
[MIR] pipewire-media-session
To
** Changed in: python-asgiref (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953173
Title:
[MIR] python-asgiref
To man
** Changed in: xdg-desktop-portal-gnome (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/1953197
Title:
[MIR] xdg-desktop-portal-gnome
Since the MIR Acks is here let us mark this committed to show up
correctly
** Changed in: postgresql-14 (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: postgresql-common (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you
Also filed a removal bug against the known-bad multicorn at
https://bugs.launchpad.net/debian/+source/postgresql-multicorn/+bug/1953515
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949579
Title:
** Summary changed:
- [RM] please remove pgloader from jammy (incompatible with PG-14 and FTBFS)
+ RM: please remove pgloader from jammy (incompatible with PG-14 and FTBFS)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This is following Debian with:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001213
And the upstream issue:
https://github.com/Segfault-Inc/Multicorn/issues/269
This is incompatible with postgresql-14 (bug 1949579) and generally no more
maintained.
Please remove it
FYI I created a tracker for postgresql-14
https://people.canonical.com/~ubuntu-archive/transitions/html/postgresql-14.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949579
Title:
[MIR]
They might be backported to plain 4.2, but they do not apply cleanly to
1:4.2-3ubuntu6.19.
0001 & 0002:
The patch directly from upstream git applies, but your backport does not - so I
just used cherry picks
0003:
Neither your backprt nor a cherry pick worked as-is.
Here things start to be
Thanks for the provided backports.
So far I was assuming this is a new feat for Jammy, but now no more.
Maybe we need to talk about what the target of this bug is - is it Focal and
therefore the backport target here was 4.2 :-)
backport/origin upstream-hash patch
B 912d70d2
** Changed in: sqlalchemy-i18n (Ubuntu)
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/1949579
Title:
[MIR] postgresql-14
To manage notifications about this
After talking with the maintainer and further summarizing the situation I
really think pgloader should be removed for now and come back into jammy later.
I filed bug 1953486 for that removal - removing the pgloader task here as it
now has an own bug.
** No longer affects: pgloader (Ubuntu)
--
Thank you Alberto for clarifying that last bit.
By that we now have the MIR-team and the security-team Acks.
That should indeed be ready for promotion now \o/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hi,
as part of the postgresql-14 transision (bug 1949579) I was looking into
pgloads test fails.
I found that there is more which isn't ready yet.
The package is rather old without updates, the same in G/H/I/J:
https://launchpad.net/ubuntu/+source/pgloader/3.6.2-1
Bonus-pain on pgloader - pgloader wasn't updated for ages:
https://launchpad.net/ubuntu/+source/pgloader/3.6.2-1
And the new rebuild (openssl 3) fails on armhf:
https://launchpad.net/ubuntu/+source/pgloader/3.6.2-1build1
--
You received this bug notification because you are a member of Ubuntu
PGLOADER
The pgloader issue stays reproducible but unclear.
I double checked if this was a regression in release, but without
PG-14/PG-common from proposed it continues to work fine.
Debian seems to be affected by the same (at least for subtest ssl)
Hi,
in the past we have handled such re-promotions rather lightly as long as the
project had no major changes.
Foundations was and still is subscribed (for the older releases), so
that is ok as well.
The delta between hirsute (in main) and jammy (to be promoted) is nearly
none and negligible.
Current Autopkgtest-Blockers:
Note: all of those that remain already had "just reruns" from vorlon and
ginggs on their +1 duty, to each of them there must be more :-/
Postgreql-14:
- dovecot
Affects all architectures.
This wasn't really a PG-14 issue. But with the new dovecot 2.3.16 +
** Changed in: postgresql-common (Ubuntu)
Status: Invalid => 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/1949579
Title:
[MIR] postgresql-14
To manage notifications about this
Some smaller fixes related got uploaded to Ubuntu recently:
- https://launchpad.net/ubuntu/+source/postgis/3.1.4+dfsg-3ubuntu1
- https://bugs.launchpad.net/ubuntu/+source/postgresql-14/+bug/1953128
But all of them still wait on the overall transition to happen.
As usual we waited for the
14 (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: postgresql-14 (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19531
Migrated to release
** Changed in: libvirt-dbus (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/1946870
Title:
Merge libvirt-dbus from Debian
]
+ The Package description explains the package well
+ Upstream Name is libdecor
+ Link to upstream project https://gitlab.gnome.org/jadahl/libdecor
** Changed in: libdecor-0 (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Changed in: libdecor-0 (Ubuntu)
Status: Incomple
Thanks for the heads up,
Please let us know when the upstream discussion settled and there is a commit
id we shall import.
Furthermore as usual if this shall go to older active releases I wanted
to ask from your dev/testing what the best way to trigger/fake diag 318
for testing would be?
**
** Changed in: pacemaker (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/1946885
Title:
Merge pacemaker from Debian unstable for 22.04
To manage
Hi Costinel and Robert,
sorry that we all had dropped the ball on this for a while - it was mostly by
the lack of being able to reproduce it anywhere else that stalled this.
... [imagine a long useless trip trying to re-trigger it, but details of
that would not help] ...
Much better I found
Set "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/1946870
Title:
Merge libvirt-dbus from Debian unstable for 22.04
To manage notifications about this
to keep libvirt-dbus working under other init systems
* [b141c8c] debhelper: Use compat level 13
* [85643fe] control: Update Standards-Version to 4.6.0
- No changes needed
[ Christian Ehrhardt ]
* [a99e33e] d/postinst: add libvirtdbus user to libvirt group
- This is only done
https://launchpad.net/ubuntu/+source/libvirt-dbus/1.4.1-1 exists now
** Changed in: libvirt-dbus (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is complete in Debian now:
https://metadata.ftp-master.debian.org/changelogs//main/libv/libvirt-dbus/libvirt-dbus_1.4.1-1_changelog
It can be a sync which I'm triggering ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Done for Jammy,
is anyone doing a check if this is security critical and/or working on test
steps for a normal SRU?
** Changed in: virglrenderer (Ubuntu Jammy)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Tags removed: server-todo
--
You received this bug notificat
https://launchpad.net/ubuntu/+source/gpsd/3.22-4ubuntu1/+build/22469668
built now
** Changed in: gpsd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libdecor-0 (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952130
Title:
[MIR] libdecor-0
To man
Uploaded as lto-disabled-list 17
** Changed in: lto-disabled-list (Ubuntu)
Status: Triaged => Fix Committed
** Bug watch added: gitlab.com/gpsd/gpsd/-/issues #178
https://gitlab.com/gpsd/gpsd/-/issues/178
** Also affects: gpsd via
https://gitlab.com/gpsd/gpsd/-/issues/178
Status: Unknown
** Affects: gpsd (Ubuntu)
Importance: Undecided
Assignee: Christian Ehrhardt (paelzer)
Status: Triaged
** Affects: lto-disabled-list (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Tags: server-todo
** Also affects: lto-disabled
Since i386 was mostly dropped this is IMHO a whishlist item.
Please speak up if anyone disagrees.
** Changed in: dlm (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could it be just
https://bugs.launchpad.net/snapd/+bug/1712808/comments/18 and all we
need would be an empty directory in the images (or a fix to not need
it)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: server-todo
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548486
Title:
Sleep hook in a subdirectory ignored but causes double execution of
Still nothing new, bump it for a recheck late in the cycle.
** Changed in: jq (Ubuntu)
Milestone: ubuntu-21.12 => ubuntu-22.02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946862
Title:
We are not much behind (one minor version atm) and often need to adapt
it late in the cycle due to the new glibc anyway. Therebe move this to
February just before the feature freeze.
** Changed in: chrony (Ubuntu)
Milestone: ubuntu-22.01 => ubuntu-22.02
--
You received this bug notification
became a sync picking up my changes
In release now:
https://launchpad.net/ubuntu/+source/libvirt-python/7.9.0-0.1
** Changed in: libvirt-python (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Approved and uploaded
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading postgis_3.1.4+dfsg-3ubuntu1.dsc: done.
Uploading postgis_3.1.4+dfsg-3ubuntu1.debian.tar.xz: done.
Uploading postgis_3.1.4+dfsg-3ubuntu1_source.buildinfo: done.
Uploading
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4729/+packages
MP:
https://code.launchpad.net/~paelzer/ubuntu/+source/virglrenderer/+git/virglrenderer/+merge/412670
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Ubuntu Focal)
Status: New => Incomplete
** Changed in: virglrenderer (Ubuntu Bionic)
Status: New => Invalid
** Changed in: virglrenderer (Ubuntu Jammy)
Status: Incomplete => Triaged
** Changed in: virglrenderer (Ubuntu Jammy)
Assignee: (unassigned) =>
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950028
Title:
FTBFS against g++ 11
To manage notifications about this bug go to:
** 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
801 - 900 of 10003 matches
Mail list logo
