Yeah as expected with a broken config this was broken all the time.
E.g. in Bionic
Apr 26 06:01:23 b libvirtd[6154]: 2021-04-26 06:01:23.898+: 6172: error :
virConfParseValue:529 : configuration file syntax error:
/etc/libvirt/qemu.conf:784: expecting a value
Apr 26 06:01:23 b libvirtd[6154]
Thank Markus you for chiming in as well here with your impressive set of
chips available to you.
I've also not seen the detection change on cascade lakes I've got.
Regression tests are still running, I'll mark verified once completed.
--
You received this bug notification because you are a memb
FYI I'm mostly waiting for impish to open to be able to go on with this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Title:
socket is inaccessible for libvirt-dbus
To manage notifications
** Merge proposal unlinked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/401771
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921880
Title:
Add EPYC-Milan model
To
** Merge proposal unlinked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/401771
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921754
Title:
Add missing cpu feature b
** Description changed:
+ [Impact]
+
+ * The current space reserved can be too small and we can end up
+with no space at all for BRK. It can happen to any case, but is
+much more likely with the now common PIE binaries.
+
+ * Backport the upstream fix which reserves a bit more space wh
For Focal:
- SRU Template added to the bug
- MP:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/401771
- PPA:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4535/+packages
(still building)
I'd ask anyone affected by this on Focal to give it a try on the PP
Thanks,
In your log I see that stopping remote file systems and libvirtd
properly was ordered AFTER libvirt-guests tried to shut down the guest.
I've checked this in a few ways
1. libvirt/libvirt-guests vs remote fs (e.g. NFS)
2. libvirt/libvirt-guests vs NBD
#1 Remote-FS - well ordered
Apr 23
For your experiments, here a few examples
1. using a mount unit for ntfs
https://brunofontes.net/enu/post/mounting-partitions-systemd
2. doing disk setup with a service
https://unix.stackexchange.com/questions/608431/systemd-fix-ordering-cycle-when-mounting-an-ntfs-volume-on-a-legacy-raid-ar
Thanks Markus.
Also testing groovy here ...
Before:
++-=---=
ii libvirt-daemon-system 6.6.0-1ubuntu3.4 amd64Libvirt daemon
configuration files
ii qemu-system-x86 1:5.0-5ubuntu9.7 amd64Q
Thanks Markus.
Also testing groovy here ...
Before:
++-=---=
ii libvirt-daemon-system 6.6.0-1ubuntu3.4 amd64Libvirt daemon
configuration files
ii qemu-system-x86 1:5.0-5ubuntu9.7 amd64Q
The regression tests are good as well with the only hiccups being the
known postcopy-after-precopy denial and a known bug in hirsute guest
kernels on s390x. Nothing new introduced by the changes as far as I can
see.
prep (x86_64): Pass 20 F/S/N 0/0/0 - RC 0 (10 min 38961 lin)
migrate (x86_
The regression tests are good as well with the only hiccups being the
known postcopy-after-precopy denial and a known bug in hirsute guest
kernels on s390x. Nothing new introduced by the changes as far as I can
see.
prep (x86_64): Pass 20 F/S/N 0/0/0 - RC 0 (10 min 38961 lin)
migrate (x86_
The regression tests are good as well with the only hiccups being the
known postcopy-after-precopy denial and a known bug in hirsute guest
kernels on s390x. Nothing new introduced by the changes as far as I can
see.
prep (x86_64): Pass 20 F/S/N 0/0/0 - RC 0 (10 min 38961 lin)
migrate (x86_
Public bug reported:
FYI: this is an intended change, can be overwritten via config and this
bug is mostly to have something puzzled users can find via search
engines to explain and solve their issue.
postcopy migration can in some cases be very useful
=> https://wiki.qemu.org/Features/PostCopyLi
Also documented in https://askubuntu.com/questions/1334249/qemu-kvm-
postcopy-migration-fails-in-hirsute-v5-11-kernels-solved/1334250
Also added as known issue in https://discourse.ubuntu.com/t/hirsute-
hippo-release-notes/19221
I hope that this will help the case to be found by affected users.
I've checked my cases and they were not regressing. That is good, but as
we've found before they are not authoritative for the issue we want to
fix here.
@Michael - would you be able to do the real verification for Focal and
Groovy with your setup please?
--
You received this bug notification be
Hmm, activity here seems to have died.
The PPA is cleaned by the end-of-cycle cleanup and Hirsute released with 5.2.
Maybe by now all kernels have got 5d971f9e67 ("memory: Revert "memory:
accept mismatching sizes in memory_region_access_valid"") and so it
triggers no more?
Thereby I'm setting 5.2
Thank you Michael !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922976
Title:
iscsid fails to log out from target on shutdown
To manage notifications about this bug go to:
https://bugs.launchpad
After some setup and preparation I was bisecting through v5.2.0..v6.0.0
to see which change exactly added this new behavior.
Summary:
- build reduced qemu
- build, configure and log-check errors will be skips
- run the extracted systemd test
- redirect serial to file
- check log if the servic
And that matches:
Offending commit:
bcb0b7b1a1c05707304f80ca6f523d557816f85c is the first new commit
commit bcb0b7b1a1c05707304f80ca6f523d557816f85c
Author: Giuseppe Musacchio
Date: Mon Nov 9 10:17:11 2020 +0100
ppc/translate: Rewrite gen_lxvdsx to use gvec primitives
Make the im
Ok, that fix works fine in a test.
I'm uploading this for a full test and hope that there are no further issues
with it that were hidden behind it so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906266
Title:
After upgrade: "libvirt.libvirtError: Requested operation is not
I can easily make it pass configure via
src/lxc/lxc_fuse.h:
#define FUSE_USE_VERSION 30
meson.build:
fuse_version = '3.0.0'
fuse_dep = dependency('fuse3', version: '>=' + fuse_version, required:
get_option('fuse'))
But then as you'd expect the actual changes for the new API are needed.
../../sr
Indeed, right now it seems to only support fuse2
libfuse-dev
Run-time dependency fuse found: YES 2.9.9
libfuse3-dev
Run-time dependency fuse found: NO (tried pkgconfig and cmake)
This is only needed for libvirt-lxc which is universe only and strongly
discouraged in favor of LXD (much better for
Filed upstream issue https://gitlab.com/libvirt/libvirt/-/issues/190
about it
** Bug watch added: gitlab.com/libvirt/libvirt/-/issues #190
https://gitlab.com/libvirt/libvirt/-/issues/190
** Also affects: libvirt via
https://gitlab.com/libvirt/libvirt/-/issues/190
Importance: Unknown
That is true, but the analysis was worth anyway as was the upstream
report.
But indeed for the reason you opened the bug I think we can close it as
"invalid" as it isn't needed to get fuse2 out of main.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Invalid
--
You received this bug n
FYI - Uploaded for impish as part of 2.15.1-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731916
Title:
ifupdown integration does not start ovs daemon
To manage notifications about this b
Ok, now that we know the root cause we can mark systemd as invalid and the ppc
project as fixed.
The qemu task will be fixed once the upload migrates - but currently the test
queue is rather full.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: ubuntu-power-systems
Public bug reported:
Hi,
I was actually looking for needrestart as it has the last messages in an apt
transaction and then seems to stall. But I found that it isn't
/etc/apt/apt.conf.d/99needrestart
instead it is the other 99 which is
/etc/apt/apt.conf.d/99update-notifier
I've littered the s
How about fully decoupling the hook and the check?
Like letting /usr/lib/update-notifier/update-motd-updates-available only do the
post-apt processing if a check "is needed" and then touch a stamp or similar.
That would give apt the fast path we want to have.
Independently we could then have som
i#m not entirely sure on PathChanged= vs PathModified= but want to hear
an opinion on the general approach first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936175
Title:
apt hook slows down apt
For adcli The bug is closed and the changes are part 0f 0.9.1 so it will be
picked up by a merge of that version.
$ git tag --contains 85097245b57f190
0.9.1
$ git tag --contains a6f795ba3d6048b
0.9.1
Changelog:
...
+ - Use GSS-SPNEGO if available [rhbz#1762420]
+ - add option use-ldaps [rhbz#1762
While some other flaky tests still hold it back the issue is fixed.
Here the PPC test of the new upload:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20210714_130923_091d6@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Still the systemd tests are very flaky.
I went through some re-runs and these last 7 tests all did test the very same
packages.
impish
amd64
boot-and-services (F 14% f 0% S 0% B 0% => P 85%/) ...F...
systemd-fsckd (F 0% f 0% S 100% B 0% => P 0%/) SSS
** Also affects: qemu (Ubuntu Hirsute)
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/1913421
Title:
Load of pre-upgrade qemu modules needs to avoid noexec
libsdl2 | 2.0.14+dfsg2-3 | impish |
source
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256185
Title:
[MIR] libsdl2
To manage notifications about this bug go to:
h
hmm, the auto update was missing
But it is done:
This bug was fixed in the package qemu - 1:6.0+dfsg-1~ubuntu3
---
qemu (1:6.0+dfsg-1~ubuntu3) impish; urgency=medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Finally - Now that we have settled on a way how to resolve the noexec issue and
have it in 21.10 we consider how to SRU this. Either as an opt-in or default-on
feature.
Both approaches have arguments that speak for them, but first we need to prep
the changes which can have various slight behavio
Public bug reported:
if running on a FIPS system I get:
+ uvt-kvm create --memory 2048 --cpu 4 --disk 16 --password=ubuntu bionic-kvm
release=bionic arch=amd64 label=daily
Warning: using --password from the command line is not secure and should be
used for debugging only.
DSA keys are not allow
We iterate over
KEY_TYPES = ['rsa', 'dsa', 'ecdsa', 'ed25519']
maybe we can ignore errors as long as one works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936473
Title:
DSA keys are not allowed
>> Either as an opt-in or default-on feature.
>> Both approaches have arguments that speak for them
> sorry, could you actually list those arguments? Just for clarification
To be clear I'm on the "let us enable it" side of things.
But I see the two SRU questions:
a) but that changes behavior of t
Public bug reported:
Due to a mistake in the hirsute cycle we released it with the hirsute type
being slightly broken.
The normal and common hirsute type is all fine and probably the reason why we
haven'd seen any reports yet.
But there is the option to use a named type with a -hbp suffix which
Public bug reported:
Qemu 5.2 was released with
https://git.qemu.org/?p=qemu.git;a=commit;h=af1b80ae56c9495999e8ccf7b70ef894378de642
Due to that a bug is triggered for windows guests that use OVMF changing
the device identification in a way that (for windows) it appears to be a
new device and t
Public bug reported:
I've had a few issues with that in the migration tests, but not reproducible
between new systemd.
Turns out that was a red herring and it actually is a bad flag
https://bugzilla.redhat.com/show_bug.cgi?id=1978526
Fixed by
https://libvirt.org/git/?p=libvirt.git;a=commit;
From upstream discussion:
> -if (!(flags & QEMU_MONITOR_MIGRATE_NON_SHARED_INC) &&
> +if (!(flags & VIR_MIGRATE_NON_SHARED_INC) &&
Oops yet another cut&paste fail on my side.
The comment directly above this also mentions the wrong flag. Please fix
that one as well before pushing.
>
Public bug reported:
Hi,
this is the return of bug 1919432
Sadly upstream mininet did not continue on it
https://github.com/mininet/mininet/issues/1060
Due to that we need to resolve it somehow or we will stay behind the new
iperf for (too) long.
The details in the links above are long, but the
** Changed in: iperf (Ubuntu)
Status: New => Confirmed
** Changed in: mininet (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936796
Title:
iperf >2.0.1
FYI showing up with iperf 2.1.2 again in bug 1936796
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919432
Title:
[REMOVE] please remove iperf 2.0.14a+dfsg1 fom hirsute-proposed
To manage notificat
Public bug reported:
There are (at least) two issues why the tests fail in Impish right now.
It blocks xtensor itself, but also src:xtensor-blas.
The test fails on all architectures, but for different reasons.
The last good test was more than two years ago.
s390x / arm64 / i386 fail on bad-pac
** Description changed:
There are (at least) two issues why the tests fail in Impish right now.
It blocks xtensor itself, but also src:xtensor-blas.
The test fails on all architectures, but for different reasons.
The last good test was more than two years ago.
-
s390x / arm64 /
The three TODOs that were identified are submitted.
Test reset on architectures that miss libxtensor-dev:
=> https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/405894
Mark as big_package to provide the test more memory:
=>
https://code.launchpad.net/~paelzer/autopkgtest-cloud/+
After various tests in launchpad infrastructure I can confirm that my upstream
suggested fix works (for us).
Therfore I have nudged upstream again and prepared a merge proposal to fix the
package.
=>
https://code.launchpad.net/~paelzer/ubuntu/+source/mininet/+git/mininet/+merge/405896
--
You r
Public bug reported:
In Focal microvm worked and it was a fine addition for those that wanted
to try this approach (mature solution of qemu/kvm reduced for a specific
use case) to minimal VMs compared to the new projects (very use-case
dedicated, but therefore missing quite some features) that spa
Thanks for the bump to this one.
I've marked it fixed in Focal according to the reports above.
By that it also is fixed in the Ubuntu Cloud Archive Ussuri which is availble
for Bionic.
Only the libvirt version in bionic itself (4.0.0-1ubuntu8.19) is affected by
this still.
From your testing and
Public bug reported:
The current version 0.4.30 is FTBFS on s390x.
https://launchpad.net/ubuntu/+source/gegl/1:0.4.30-1
https://launchpad.net/ubuntu/+source/gegl/1:0.4.30-1/+build/21795068
https://launchpadlibrarian.net/549105404/buildlog_ubuntu-impish-s390x.gegl_1%3A0.4.30-1_BUILDING.txt.g
Public bug reported:
The new nftables
https://launchpad.net/ubuntu/+source/nftables/0.9.8-3
is stuck in proposed since it fails autopkgtest of firewalld
https://autopkgtest.ubuntu.com/packages/f/firewalld/impish/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/f/
Fail #1 - stdout mismatch
# -*- compilation -*-
97. icmp_block_in_forward_chain.at:1: testing ICMP block present FORWARD chain
...
./icmp_block_in_forward_chain.at:1: if ! cp
"${FIREWALLD_DEFAULT_CONFIG}/firewalld.conf" ./firewalld.conf; then exit 77; fi
./icmp_block_
Fail #2 - stdout mismatch
# -*- compilation -*-
124. rhbz1855140.at:1: testing rich rule icmptypes with one family ...
./rhbz1855140.at:1: if ! cp "${FIREWALLD_DEFAULT_CONFIG}/firewalld.conf"
./firewalld.conf; then exit 77; fi
./rhbz1855140.at:1: sed -i 's/^CleanupOnEx
The fix is upstream accepted by now:
https://git.netfilter.org/nftables/commit/?id=533565244d88a818d8828ebabd7625e5a8a4c374
And it is released as part of v0.9.9
0.9.9 might change a bunch of other things we are not prepared for, so
for the time being I'd try to resolve this regression in a backpor
$ LC_ALL=C.UTF-8 MESON_TESTTHREADS=1 meson test rgb_params --print-errorlogs
ninja: Entering directory `/root/gegl-0.4.30/obj-s390x-linux-gnu'
ninja: no work to do.
1/1 gegl:composition / rgb_params FAIL 0.67s (exit status 250 or
signal 122 SIGinvalid)
The output from the failed tests:
With that we see that the backtrace and values are:
Thread 1 "gegl-imgcmp" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
49 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../
The very same on x86 shows a valid header:
(gdb) p info->header.bytes_per_pixel
$1 = 16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936901
Title:
Tests of 0.4.30 crash on s390x
To manage notif
** Bug watch added: gitlab.gnome.org/GNOME/gegl/-/issues #289
https://gitlab.gnome.org/GNOME/gegl/-/issues/289
** Also affects: gegl via
https://gitlab.gnome.org/GNOME/gegl/-/issues/289
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
Also reported to Debian since they are affected the same way
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991300
Depending on an upstream response we can then consider
a) waiting for a fix as 0.4.30 is broken (real regression) and we
don't want it to migrate
b) it was always broken, just
Hmm,
I thought that is conceptually this way, from the man page of e.g. virsh:
"--copy-storage-all indicates migration with non-shared storage with
full disk copy ... In both cases the disk images have to exist on
destination host, the --copy-storage-* options only tell libvirt to
transfer data f
As I assumed the backporting (to make it apply, not in regard to potential
regressions) is trivial and was already done here
https://git.centos.org/rpms/libvirt/blob/c8s-stream-rhel/f/SPECS/libvirt.spec#_286
Maybe we can spin a PPA for you to give it a try if it even achieves what you
expect.
With all hints in place I got two passes now:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/x/xtensor/20210720_065346_146d0@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/x/xtensor/20210720_065542_50c0e@/log.gz
Rechecking later if that als
It completed 7 minutes ago:
2021-07-20 11:53:50 CESTPublished Impish release universe
misc0.22.0-5
Thereby this bug can be marked fixed.
** Changed in: xtensor (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member o
MP Review complete, uploading new mininet to resolve the issue in
Impish.
** Changed in: iperf (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936796
Tit
https://launchpad.net/ubuntu/+source/mininet/2.3.0-1ubuntu1 built and
works fine AFAICS.
The openvswitch tests of iperf triggered with the new mininet worked as well:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/o/openvswitch/20210720_113258_ddb48@/log.gz
https://autopkgt
> On Tue, Jul 20, 2021 at 12:55 PM Balashov Dmitry <1929...@bugs.launchpad.net>
> wrote:
> ...
> but this functionality worked in 18.04, but does not work in 20.04
Really, I didn't expect that - thanks for the info.
I'll need to try that myself - if true then this clearly can be
considered a regr
I found no follow up fixes to those commits in git.
So I have prepared a (very quick and untested) PPA:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4629
Could you please let me know if that would for for your case?
--
You received this bug notification because you are a member
After confirming the build and effect of the fix in PPA
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4626/+packages
I recreated the same in a VM and isolated the broken tests.
Then I updated to the PPA and with these tests I was able to confirm that they
now pass.
97: ICMP block
** Also affects: nftables (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991309
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/1936902
T
I re-ran the full test - it really seems good now:
242 tests were successful.
2 tests were skipped.
Thanks Graham for the second pair of eyes on this.
I Uploaded it to Impish and hope to unblock nftables by that.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
And by that iperf migrated as well
iperf | 2.1.2+dfsg1-1 | impish/universe | source,
amd64, arm64, armhf, ppc64el, riscv64, s390x
** Changed in: iperf (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of
Added an SRU template to this bug and an MP here
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/405967
** Description changed:
+ [Impact]
+
+ * On copy-storage-all migration for certain combinations one
+expects the creation of the target storage (it is kn
** Changed in: egl-wayland (Ubuntu)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935082
Title:
[MIR] egl-wayland
To manage notifications ab
Public bug reported:
Hi,
src:ntopng - program to monitor traffic
src:ndpi - library only used in/for ntopng
There were issues around s390x failing an binary removals, but that isn't all
of it.
Just from history one would expect this to build only for some architectures,
but on those to be fine
Thank you Seth, this is fully ready now and just needs to be promoted.
It also is in component-mismatches already (for a long time)
I'll ping the archive admins to do so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Hi,
thanks for the report - I'm super busy this week and on PTO afterwards.
So answers might be delayed a bit and I beg your pardon in advance.
I have asked a few friends more into arm, maybe that provides a quick help.
Otherwise I'll try to squeeze in some debugging.
--
You received this bug not
@SRU Team - I'd appreciate if we could take this into -proposed early but
release it late.
Late in this case means the two weeks of my PTO and the time for me to run the
full regression tests. That extra exposure in -proposed should further help to
cover potential issues.
** Description changed
Uploaded to Focal-unapproved for evaluation by the SRU Team
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929202
Title:
[Ubuntu 20.04] Libvirtd will not pre-create images on the target host
durin
Public bug reported:
That was blocked by a autopkgtest-fail that happens in Ubuntu
https://autopkgtest.ubuntu.com/packages/p/pyspread
and Debian
https://ci.debian.net/packages/p/pyspread/
with the new 1.99.6-1 version.
This was already brought up in April in
https://bugs.debian.org/cgi-bin/b
While we are waiting for upstream and Debian to pick this up I have
uploaded the fix to impish to get it out of update-excuses for now
(Since it is only a test and not a real issue that should be fine).
https://launchpad.net/ubuntu/+source/pyspread/1.99.6-1ubuntu1
--
You received this bug notifi
Public bug reported:
After fixing bug 1937058 it still is blocked as on s390x there are further
fails around code that already tries to handle byteorder but seems to fail on
big endian.
Example test log:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/p/pyspread/20210721_1
Reproducible on s390x via:
$ apt install python3-matplotlib python3-numpy python3-pyqt5
python3-pyqt5.qtsvg python3-pytest python3-pytest-xvfb python3-setuptools
$ apt build-dep pyspread
$ cd pyspread-1.99.6/pyspread
$ py.test-3 lib/test/test_qimageview.py
It expects
0xff123456
or on big endia
Reported upstream in
https://gitlab.com/pyspread/pyspread/-/issues/93
And I have fixed the test until we know if there is something deeper to fix
that seems to be the best option since it
a) does not seem to be a regression to before (1.99.5 didn't have the test but
seems to behave the same)
b)
While not wworth a report on its own as an FYI I added it to the other known
FTFBS debian bug at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986488
** Bug watch added: Debian Bug tracker #986488
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986488
--
You received this bug notifi
also tracking another packaged blocked by this test "dulwich"
** Also affects: dulwich (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dulwich (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Public bug reported:
Plenty of self-test fails like
==
FAIL: breezy.tests.test_plugins.TestPlugins.test_plugin_appears_in_plugins
--
Traceback (most recent call
This change seems "infectionous" as now dependent packages break like
lintian-brush in
https://launchpadlibrarian.net/548012775/buildlog_ubuntu-impish-amd64.lintian-brush_0.107_BUILDING.txt.gz
** Also affects: lintian-brush (Ubuntu)
Importance: Undecided
Status: New
--
You received thi
The build of breeze itself is now showing a different issue (maybe just
hiding this one) tracked in bug
https://bugs.launchpad.net/ubuntu/+source/breezy-debian/+bug/1937173
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989634
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988909
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989633
Should be fixed in lintian-brush >=0.106
But what is left is that breezy and packages depending on it are blocked by
https://bu
** Description changed:
- Plenty of self-test fails like
+ 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
==
** Package changed: breezy-debian (Ubuntu) => breezy (Ubuntu)
** Tags added: update-excuse
--
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.1-1
To manage notifications
In Debian this build issue is not present, compare these s390x builds
for example (done on almost the same time - so not as it often happens
months apart introducing a lot of build environment differences)
failing:
https://launchpadlibrarian.net/547563235/buildlog_ubuntu-impish-s390x.breezy_3.2.1-
Locally reproducible in sbuild of impish
Most obvious difference is a newer python 3.9.2-3 -> 3.9.4-1
A re-build in Debian unstable works fine
Even Re-runnning the test in Impish after a failed build (chrooted into
the sbuild environment)
a) as a whole
BRZ_CONCURRENCY=3 BRZ_HOME=debian/brzhome B
Finally I found a command that fails in bad and works in good env
$ BRZ_CONCURRENCY=3 BRZ_HOME=debian/brzhome BRZ_PLUGIN_PATH=-site:-user
LC_ALL=C.UTF-8
PYTHONPATH=/build/breezy-xbGxjH/breezy-3.2.1/.pybuild/cpython3_3.9_breezy/build
python3.9 ./brz -Derror selftest -v breezy.tests.test_plugins.
501 - 600 of 10728 matches
Mail list logo
