Hi Enoch.
I wonder if, maybe, the definition you shared just asks for an impossible
configuration.
Indeed if it wants acpi, so let us add it.
If you add
FYI - As of today both build issues are still locally reproducible in
sbuild.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933034
Title:
FTBFS in impish due to test failures
To manage notificatio
Yeah the former blocker
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989638
should be fixed by now as we now see only builds that can provide this in
https://launchpad.net/ubuntu/+source/qemu-web-desktop/21.05.03-4
+1 to this removal of old binaries
** Bug watch added: Debian Bug tracker
It is already clear that eventually once all FTBFS are resolved all
these need to be tested combined from proposed. So please combine
"dulwich, silver-platter, breezy-debian, breezy, lintian-brush" as
triggers together for all the tests of them.
--
You received this bug notification because you a
This blocks breezy, but also breezy-debian, lintian-brush and dulwich (see bug
1933034).
Once the FTFBS here is resolved there is a series of rebuilds and combined
tests that need to be executed.
I outlined them at
https://bugs.launchpad.net/ubuntu/+source/breezy-debian/+bug/1933034/comments/6
The fail is on:
File "/usr/lib/python3/dist-packages/breezy/git/tree.py", line 1324, in
_recurse_index_entries
(ctime, mtime, dev, ino, mode, uid, gid, size, sha,
ValueError: too many values to unpack (expected 10)
And indeed if we check the data there is has 11 elements, here with
names:
So it is an incompatibility of
ii python3-dulwich 0.20.23-1ubuntu1 amd64Python Git library - Python3
module
ii python3-breezy 3.2.0-1 amd64distributed version control
system - Python 3 library
That would be resolved by:
breezy | 3.2.1-1 | impish-proposed/univers
** Description changed:
Recent (rebuild) is here
https://launchpadlibrarian.net/545919434/buildlog_ubuntu-impish-amd64.breezy-debian_2.8.63build1_BUILDING.txt.gz
It has plenty of self-test fails like
==
FAIL: bree
To be clear a bunch of the warnings are intentional e.g. on the try to
load breezy.testingplugins.some_error
But I tried to reduce the variables:
test_plugins_with_the_same_name_are_not_loaded was failing when run
combined.
Overall we have:
test_plugins.TestLoadingPlugins.test_plugin_with_bad_ap
Ok, I found a pair.
test_plugin_with_bad_api_version_reports and test_plugin_with_error work
individually.
But if run after one another the second one fails.
I changed their order and it is always the second that fails.
--
You received this bug notification because you are a member of Ubuntu
Bu
Of the test test_plugin_with_error seems the most simple and even if the same
is executed twice the second one fails.
So i leaves something yet unknown behind in the test environment that breaks
the second execution
.
brz selftest: /build/breezy-xbGxjH/breezy-3.2.1/brz
/build/breezy-xbGxjH/
The load error is intentional (it is a bad module name).
But the test expects the stringified exception
bad
while on the second execution it gets:
No module named 'breezy.testingplugins.some_error'
This checked error message comes from breezy/plugin.py
It is set by:
return record_plugin_war
load_with_paths (tests/test_plugins.py) from sets up the paths that are needed
for this to work.
It reached load_plugins (from breezy/plugin.py) with
path _Path('breezy.testingplugins', [], [], ['.'])
I wondered if the python cache might keep the (failed) module and remember that
it failed to
I have also lead in with two tests of type B and then it is
B - good
B - good
A - bad
So it seems like the ones that want to evaluate the log for the raised "bad"
can only go first and once. So it still could be that python no more re-loads
the code at all and thereby no more triggered "bad".
T
I mentioned before that giving each test an individual file name does NOT help
to resolve the issue. Still the latter modules are not (re)-loaded and do not
trigger the
'raise Exception("bad")\n'
I wondered if python might not keep it's cache by path/filename but instead
per-hash.
In which cas
I think I have laid some debugging groundwork here, but I'm lost.
This probably needs a reset and a new pair of eyes :-/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937173
Title:
FTBFS breezy 3.2
You could give the involved components a try on Focal+[1].
That would allow to switch the components one by one while staying on Focal.
There is no linux-generic-hwe-20.04 yet that is on the new level. But
that you could try from [2] (even more versions to compare if needed).
[1]:
https://launch
** Changed in: python-certbot (Ubuntu Bionic)
Assignee: Robie Basak (racb) => Christian Ehrhardt (paelzer)
** Changed in: python-certbot (Ubuntu Focal)
Assignee: Robie Basak (racb) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a mem
** Changed in: python-certbot (Ubuntu Focal)
Assignee: Robie Basak (racb) => 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/1876933
Title:
FTBFS in focal due
We need a Bionic and a Focal system for that reachable from the Internet
with a DNS name.
I have created those test systems temporarily on canonistack (an
internal openstack service)
These notes are mostly for myself to re-do it once things land in proposed,
but also illustrate for everyone how t
Testing the test instructions:
Without the fix this indeed fails
Note: You can run it with --verbose to see the issue in more detail if needed.
Plugins selected: Authenticator apache, Installer apache
Attempting to renew cert (cb-test-bionic.dd-dns.de) from
/etc/letsencrypt/renewal/cb-test-bioni
Thank you all, I'll take over as Robie is unavailable atm.
The test suggestions of Brad were awesome, I think I have created something SRU
compatible out of that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Ok we have:
- the packaging changes ready
- reviewed the packaging changes
- created a test build
- come up with test instructions for verification
- exercised the test on the test build
I think this is ready to enter SRU [1] processing.
I'm uploading to Focal/Bionic-unapproved
[1]: https://wiki.
This is fixed in 0.4.2 synced into Ubuntu by MVO (thanks!).
It needs a follow on 0.4.3 which already is on the way.
** Changed in: apt-clone (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Fixed by https://launchpad.net/ubuntu/+source/python-apt/2.1.3ubuntu3
migrating after some work on dependencies.
Note cloud and lxd images do not yet contain this, so you'll need to
update before add-apt-repository or wait another day or two.
Thanks everyone.
** Changed in: python-apt (Ubuntu)
Changes:
- "any_layout" "off" no more present (all six entries of the bad compat are
gone)
- 2.4 values in "qemu32-x86_64-cpu" "model-id" (matches Bionic now, formerly
had 2.4+2.3 set)
- "migration" "send-configuration" (still present as before and as in Bionic)
- all other implied compat changes
Good - now the compat attributes in Focal for a wily type machine fully
match what was present in Bionic.
@Trya - could I ask you to try qemu - 1:4.2-3ubuntu6.9~ppa3 from PPA
[1] on Focal and do a migration of the kind of windows-guest that
formerly failed onto a Focal target that has that instal
Also thanks for testing the PPA @Trya!
Once this has become an SRU you'll be asked once more to test it, but until
then I need to first fix it in the current Ubuntu release in Development and
then do SRUs.
** Changed in: qemu (Ubuntu)
Status: Triaged => In Progress
--
You received this
Yeah I understand that it is bad i you realize only rather later that it
is a release, but the full name references the Ubuntu release quite
literally.
$ qemu-system-x86_64 -M ? | grep wily
pc-i440fx-wily Ubuntu 15.04 PC (i440FX + PIIX, 1996)
We can't change the actual type names but the de
** Description changed:
+ [Impact]
+
+ * History: Xenial's qemu as once released with a machine type that was
+very broken. This was later on fixed in bug 1621042 but for
+compatibility reasons we need to carry the broken type as well (to e.g.
+allow migrations from guests started
FYI: I added the SRU template in preparation and opened three MPs for
the required packaging changes. Waiting for review on those now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902654
Title:
fa
*** This bug is a duplicate of bug 857651 ***
https://bugs.launchpad.net/bugs/857651
Hi Mikko,
this unfortunate behavior was discussed a few times already. The central bug
for it is bug 857651.
It isn't so much a bug in the libvirt package as much more accountservice it
seems. Depending on t
Interesting thanks Jakub, 0.38 is in groovy and later
spice-gtk | 0.37-2fakesync1 | focal/universe | source
spice-gtk | 0.38-2ubuntu1 | groovy/universe | source
spice-gtk | 0.38-2ubuntu1 | hirsute/universe | source
But being a protocol change [1] I'm unsure we can SRU this to Focal easil
*** This bug is a duplicate of bug 1215411 ***
https://bugs.launchpad.net/bugs/1215411
** This bug has been marked a duplicate of bug 1215411
libcpupower.so is not installed from linux-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yeah as Brian I came by this a while ago (and now again). Bug 1891336 is about
the same.
This one here is older and closer to a conclusion.
So I'll make the other one a dup, but added bug-tasks and an update-excuse tag
to show up in excuses.
** Also affects: gkrellm2-cpufreq (Ubuntu)
Importan
https://launchpad.net/ubuntu/+source/python-certbot/0.40.0-1ubuntu0.1 built
fine in proposed.
Since this part of the upload was just the FTBFS this is hereby "validated" to
work.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-foc
Prepared the test env as described above on Bionic and Focal.
With the current -release package on renewal I got:
Focal:
ubuntu@bos01-amd64-certbot-focal:~$ sudo certbot renew --force-renewal
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - -
Public bug reported:
Hi,
this is broken on non x86 due to upstream
https://github.com/NGSolve/netgen/issues/44
The Debian maintainer was made aware
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974136
and there is a PPA as alternative for Ubuntu users.
https://launchpad.net/~ngsolve/+a
On Wed, Nov 11, 2020 at 1:11 AM John Chittum <1889...@bugs.launchpad.net>
wrote:
> ...
> Is this where the "Supported" seed is used?
>
Yes, that allows to seed it into main without pushing it onto any image/iso
build.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Public bug reported:
Hi,
with gcc-10.2 clustalo segfaults on s390x.
First of all I beg your pardon, but I didn't find an upstream bug tracker for
custalo but
think you should be aware. But furthermore I think this might eventually be a
gcc bug (or at least needs the s390x gcc experts to look a
@Frank - could you get this properly tagged and mirrored so that the IBM
gcc people could have a look?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903817
Title:
Clustalo 1.2.4-6 segfaults on s390
FYI: Temporary mitigation forwarded to Debian clustalo packaging at
https://salsa.debian.org/med-team/clustalo/-/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903817
Title:
Clustal
On Wed, Nov 11, 2020 at 6:30 PM Matthias Klose <1902...@bugs.launchpad.net>
wrote:
> yes, but the package still needs a bug subscriber
>
Yeah, since we were not yet ready on this it wasn't done yet - thanks for
the ping.
Ubuntu-server is now subscribed.
--
You received this bug notification bec
This is a known issue around TZ which will be fixed in the next round of
stable release updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903573
Title:
autopkgtest fails in hirsute
To manage
Since it breaks the multipath-tools test I'll add a bug task just for
tracking
** Also affects: multipath-tools (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.launchpa
Public bug reported:
Example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/m/multipath-tools/20201110_202353_71c1e@/log.gz
Error:
+ fio /tmp/autopkgtest.d8v3Mz/tgtbasedmpaths-artifacts/path-change-check.fio
verify-ph
Since it breaks the tgt test I'll add a bug task just for tracking
** Also affects: tgt (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/1903963
Titl
Public bug reported:
While this looks like an odd flaky I/O issue there is a real upstream issue
behind it:
https://github.com/axboe/fio/issues/1065
With an existing fix:
https://github.com/axboe/fio/commit/fd56c235caa42870e6dc33d661514375ea95ffc5
I have prepped all we need into a Debian merg
So far it "only" breaks the multipath-tools run on ppc64el, but I'm
concerned that the other architectures are just surviving on a sliver of
free memory (since I was able to reproduce the same fio behavior on all
architectures).
Therefore I'll propose adding it to big_packages on all architectures
Public bug reported:
[Impact]
* MRE for latest stable fixes of Postgres release on August 13th.
[Test Case]
* The Postgres MREs traditionally rely on the large set of autopkgtests
to run for verification. In a PPA those are all already pre-checked to
be good for this upload.
[Regressio
** Changed in: postgresql-12 (Ubuntu)
Status: Triaged => 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/1903573
Title:
autopkgtest fails in hirsute
To manage notifications about t
the fix in 21.04 is in -proposed but will (due to a compiler bug) only fully
release with the 5.1 upload of hopefully next week.
Never the less it is in hirsute-proposed and that is enough to get the SRUs
started.
I uploaded the fix to F/G -unapproved queue
--
You received this bug notificatio
FYI - the same timetz issue was on build and I can confirm from the PPA
that it is fixed with 12.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903573
Title:
autopkgtest fails in hirsute
To manag
Prio to the fix
root@g:~# dpkg -l libvirt-daemon-system
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionArchitecture Descript
** Also affects: tgt (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/1903962
Title:
Autopktest broken on ppc64el (hirsute fio 3.21)
To manage not
Fixed by the new FIO 3.23 in hirsute proposed now
** Changed in: tgt (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/1903963
Title:
Autopktest broken on s
FYI: Uploaded to hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903573
Title:
autopkgtest fails in hirsute
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
Public bug reported:
Hi,
I have an issue with ebtables that affects libvirt.
While initially found in hirsute I had to realize this is broken in
Groovy and even Bionic (might be a different reason back then) as well right
now.
But working in Focal (witch matches my memory of it being good before
FYI
Since I started on this with libvirt and the libvirt people were helpful as
always in debugging this I also pinged the ML since this issue should affect
libvirt in any place where it runs with the new ebtables.
https://www.redhat.com/archives/libvir-list/2020-November/msg00790.html
@Oibaf -
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/ssl-cert/+git/ssl-cert/+merge/393784
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853021
Title:
ssl-cert generate-def
I haven't seen any suspicious warnings myself, but I can retry
with/without -fno-strict-aliasing and attach the log for your own
consideration.
And BTW o/ Andreas :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
FYI: via the libvirt discussion it was reported that
- legacy 2.0.11 works on fedora (for us as well on Ubuntu)
- 1.8.4 works on RHEL8 (we have 1.8.5 that fails)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Bug watch added: Red Hat Bugzilla #1898130
https://bugzilla.redhat.com/show_bug.cgi?id=1898130
** Also affects: iptables (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1898130
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Attachment added: "buildlog O2 fno-strict-aliasing - failing as well"
https://bugs.launchpad.net/ubuntu/+source/clustalo/+bug/1903817/+attachment/5435052/+files/O2-fno-strict-aliasing.buildlog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
As I said it is 100% reproducible and should be for you as well if you
follow my steps I mentioned in the report.
Let me know if you see anything in the logs that you need me to work on,
otherwise all that is left for me is wishing you best luck with
debugging.
--
You received this bug notificat
** Attachment added: "buildlog O0 - working"
https://bugs.launchpad.net/ubuntu/+source/clustalo/+bug/1903817/+attachment/5435050/+files/O0.buildlog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/190
** Attachment added: "buildlog O2 - failing"
https://bugs.launchpad.net/ubuntu/+source/clustalo/+bug/1903817/+attachment/5435051/+files/O2.buildlog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/190
TL;DR: "-O2 -fno-strict-aliasing is as broken as -O2, while -O0 still works"
I'll attach logs of the three cases ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903817
Title:
Clustalo 1.2.4-6 seg
@trya - do you have a chance to test focal-proposed and groovy-proposed as a
migration target with your windows machines that are affected?
It would be the preferred way to validate this, if you can't please let me know
(then I'll do at least the GDB based attribute check that I did before to
en
As discussed via IRC here a tarball of my build result (the whole tree)
Executing this in it segfaults:
src/clustalo -i debian/tests/biopython_testdata/f002 --guidetree-out
temp_test.dnd -o temp_test.aln --outfmt clustal --force
** Attachment added: "tar of the built tree that contains the faili
>From your log:
/var/lib/dpkg/info/python-six.postinst: 6: pycompile: not found
The missing binary pycompile is of pkg:python2
And python-six in Focal has:
Depends: python2:any (<< 2.8), python2:any (>= 2.7~)
According to your log you should have python2-minimal:amd64 2.7.17-2ubuntu4
Which p
Forgot, also:
dpkg --verify python2-minimal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903484
Title:
package python-six 1.14.0-2 failed to install/upgrade: installed
python-six package post-in
In a discussion with Andreas we failed to break it in his environment
but it reliably failed in mine. Then I found the crash in dmesg, there
it looks like this:
[2431454.082712] User process fault: interruption code 003b ilc:2 in
clustalo[2aa2d00+d4000]
[2431454.082725] Failing address: 0
The crash happens in 5.4.0-51-generic and a Hirsute LXD container therein.
But also in a Hirsute VM under 5.8.0-25-generic
On the latter the crash looks like (similar):
[520179.980824] report_user_fault: 5 callbacks suppressed
[520179.980827] User process fault: interruption code 003b ilc:3 in
c
** Attachment added: "Core dump gatheres in a Hirsute s390x VM with
5.8.0-25-generic - matches the source/build tarball formerly attached"
https://bugs.launchpad.net/ubuntu/+source/clustalo/+bug/1903817/+attachment/5435116/+files/core.0.84593.1605606619.tar.gz
--
You received this bug notifi
Segfault avoidable (thanks AndiKr) if we set OMP_NUM_THREADS, but that
is just hiding the underlying issue which probably is code that isn't
s390x compatible.
OMP_NUM_THREADS=1 src/clustalo -i debian/tests/biopython_testdata/f002
--guidetree-out temp_test.dnd -o temp_test.aln --outfmt clustal --fo
For the sake of a potential upstream change I was trying qemu from git up to
current master, but it still fails with the same error: ‘TYPE_CANONICAL’ is not
compatible.
Due to that - as long as the checking is enabled - qemu is unbuildable in
Hirsute.
At the same time Doko and I began with test
The issue was confirmed and a fix now committed to the upstream repository.
=>
http://git.netfilter.org/iptables/commit/?id=55b7c71dce7144f4dc0297c17abf0f04879ee247
@Alex will you (as usual) do the upload of that - will eventually be
Groovy and Hirsute that needs this.
** Also affects: iptables
Public bug reported:
With the most recent versions of livbirt 6.8 and qemu 5.1 migrations
with --p2p --tunnelled block.
Example:
$ virsh migrate --unsafe --live --p2p --tunnelled kvmguest-hirsute-normal
qemu+ssh://10.222.1.159/system
--p2p works, but --p2p --tunneled hangs, eventually ending in
Issue in livecd-rootfs/2.694 resolved.
The one in systemd likely as well (known to be flaky) but it is still running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902654
Title:
failure to migrate
** Changed in: python-tzlocal (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903700
Title:
[MIR] python-tzlocal
To manage notificatio
** Changed in: python-calmjs.types (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903704
Title:
[MIR] python-calmjs.types
To manage n
** Changed in: python-calmjs.parse (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903703
Title:
[MIR] python-calmjs.parse
To manage n
** Changed in: natsort (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903698
Title:
[MIR] natsort
To manage notifications about this
** Changed in: python-calmjs (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903702
Title:
[MIR] python-calmjs
To manage notifications
Autopkgtest on systemd/245.4-4ubuntu3.3 (amd64) resolved as well now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902654
Title:
failure to migrate virtual machines with pc-i440fx-wily type to ubu
** Bug watch added: Debian Bug tracker #975028
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975028
** Also affects: iptables (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975028
Importance: Unknown
Status: Unknown
** Changed in: iptables (Ubuntu Groovy)
The originally reported check via qtree (just looking at
virtio-balloon-pci) now correctly reports true for any_layout.
Focal
dev: virtio-balloon-pci, id "balloon0"
...
bus: virtio-bus
type virtio-pci-bus
dev: virtio-balloon-device, id ""
...
any_lay
GDB check attributes of the wily type in gdb in regard to
virtio-blk-pci
virtio-balloon-pci
virtio-serial-pci
virtio-9p-pci
virtio-rng-pci
migration send-configuration
migration send-section-footer
migration store-global-state
Focal (2.10 is starting at 62)
(gdb) p (GlobalProperty*)(object_compa
Setting verified tags as I confirmed in GDB and qtree.
@trya - still if there would be a chance to also try the windows guests
on these before we release that would be great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
First of all - the upgrades to the versions in proposed worked just
fine.
Groovy
root@g-wily:~# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
alsa-ucm-conf apport ap
Bisect step #1 - Expected to ICE and indeed does so.
gcc-20200507.tar.xz
/root/qemu-5.0/linux-user/syscall.c: In function ‘do_syscall1.constprop’:
/root/qemu-5.0/linux-user/syscall.c:12479:1: internal compiler error:
Segmentation fault
12479 | }
| ^
0x5518cb crash_signal
../../gcc
** Tags added: libvirt-21.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904584
Title:
libvirt 6.8 / qemu 5.1 - --p2p --tunnelled is hanging
To manage notifications about this bug go to:
https:/
FYI currently on 20190425.
First build passed, but we need a few more to be sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890435
Title:
gcc-10 breaks on armhf (flaky): internal compiler error
I analyzed test issues.
Merged gvmd to fix one, retriggered a few others (no resolved).
Some further test issues will be fixed in the future, for now there are
hints to mitigate them at:
https://code.launchpad.net/~paelzer/britney/+git/hints-
ubuntu/+merge/394114
--
You received this bug notific
On Wed, Nov 18, 2020 at 8:15 PM trya uuum <1902...@bugs.launchpad.net> wrote:
>
> Everything works. I tested migration to focal and groovy.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/190
20190425 can be considered good it completed 4.5 times before I scheduled the
next run.
Next is r10-4054 which has -v of:
gcc version 10.0.0 20191022 (experimental) (GCC)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
r10-4054 failed with
during RTL pass: reload
/root/qemu-5.0/fpu/softfloat.c: In function ‘sf_canonicalize’:
/root/qemu-5.0/fpu/softfloat.c:670:1: internal compiler error: Segmentation
fault
670 | }
| ^
0x4b7443 crash_signal
../../gcc/gcc/toplev.c:326
0x66b7c7 thumb2_legitimate_ad
Interim update on the dependent upstream projects I mentioned in commend #3.
This is important if we later need to remove it.
BTW all of them are removed from debian-testing already.
looking good:
- pgl-ddl-deploy fixed in v2.0 (needs debian to merge)
- pg-wait-sampling fixed in 1.1.2 (needs debia
=> https://launchpad.net/ubuntu/+source/cyrus-imapd/3.2.4-3
** Changed in: cyrus-imapd (Ubuntu)
Status: New => In Progress
** Changed in: cyrus-imapd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
601 - 700 of 10728 matches
Mail list logo
