On Tue, Dec 1, 2020 at 4:50 AM Trent Lloyd <1847...@bugs.launchpad.net> wrote:
>
> Note: This patch has related regressions in Hirsute due to the version number
> containing a space:
> https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906245
> https://bugs.launchpad.net/ubuntu/+source/qemu/+bug
Add another 1/3 fails to r10-7093
Now I am on the next two
- r10-6760
- r10-6839
--
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
(1) yeah makes sense now, thanks
(2) So we can't get good-vs-bad data, but is the behavior any different
at least with non MacOS guests then?
(3) no please no filtering - add all of it to see everything from
kernel-apparmor denials to anything odd with udev rules.
--
You received this bug notif
(2)+(3) bonus, since the device will need to be detached on the host to
be passed through and IIRC that depends a bit on USB topology. Can you
provide pre/booted/after-reset output of "lsusb -t" of the host as well
pelase?
--
You received this bug notification because you are a member of Ubuntu
B
2/7 runs of r10-6839 failed with
r10-6839 add_regs_to_insn_regno_info (lra)
Next will be r10-6760
--
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): intern
Updated Result Overview:
20190425 good
r10-1014
r10-2027 good?4
r10-2533
r10-3040 good?4
r10-3220
r10-3400 good?4
r10-3450
r10-3475
r10-3478
r10-3593
r10-3622
r10-3657 good?5
r10-3727 good?3
r10-4054 other kind of bad - signature different, and rare?
r10-6080 good?10
r10-6586 good?27
r10-6760 next
We'll need more runs to be sure, but so far r10-6760 seems good.
In preparation - could I requests builds between r10-6760 - r10-6839 please ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890435
Tit
FYI: Still no other libvirt change in the queue for bionic that would justify
an SRU upload.
Current test ratio on the flaky test ~60% passes on smoke-lxc and all other
subtests pass 100%.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hi TJ,
that reminds me of some bugs for arm* chroots with static that we fixed
recently.
Hmm no, that was bug 1890881 which isn't completely the same - but it also was
not backportable to 20.04 anyway :-/
I've checked my inbox and found plenty of upstream references to this in
https://bugs.launc
The logs make total sense, thank you!
OK on lsusb:
We see the HID devices flip from "usbhid" driver to "usbfs" with the initial
start.
They no more change on the reset.
On the journal entries we see on the initial guest start that gnome has to
yield the devices (OK).
USB isn't mentioned at al
** Description changed:
- Cherry-picking upstream changes for ESM Product renaming and messaging
- 1901627 triggered autopkgtest failures on for Xenial(pep8) and
- Bionic(pep8 & pyflakes) during SRU review.
+ [Impact]
- Also changes in the Xenial base cloud-images used for testing dropped
- pep
Ok, r10-6760 reached 20 good runs and is considered good.
Doko was so kind to build 6779 6799 6819 for me - of which 6799 will be next.
Note: I've aligned the comments to all have the same style and dropped
the untested revisions.
Updated Result Overview:
20190425 good 0 of 13
r10-2027 good 0 of
Public bug reported:
Request:
Please remove the following from hirsute-proposed:
- postgresql-13-omnidb 2.17.0+ds-5build1
- postgresql-13-omnidb-dbgsym 2.17.0+ds-5build1
Reasoning:
The build/rebuild of 2.7...-5 in hirsute created an unwanted binary
package in hirsute-proposed that blocks the foll
Needs an AA to resolve - so I'm subscribing ubuntu-archive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906517
Title:
omnidb: please remove no more existing binaries that never left
proposed
To
FYI: r10-6799 had 14 good runs so far, I'll let it run for a bit longer to be
sure.
Then - later today - if nothing changes r10-6819 will be next.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890435
Hmm,
I was guessing the paths from your former log output.
Thanks for fixing it up as needed on your system.
So we know that just resetting it from the Host POV won't change anything.
And thanks for the info on "auto-recovering" on guest reboot.
The one obvious next test would be to shut down the
Completed 20 good runs on r10-6799, continuing with r10-6819 as
planned.
Updated Result Overview:
20190425 good 0 of 13
r10-2027 good 0 of 4
r10-3040 good 0 of 4
r10-3400 good 0 of 4
r10-3657 good 0 of 5
r10-3727 good 0 of 3
r10-4054 other kind of bad 1 of 18 (signature different)
r10-6080 good 0
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages
MP:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/398447
Build log:
[1023/8456] cc -Ilibqemu-s390x-softmmu.fa.p -I. -I../.. -Itarget/s390x
-I../../target/s390x -Iqapi -Itrace -Iui -Iui/shad
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916462
Title:
dnsmasq failed to send packet: Network is unreachable
To manage notifications about this bug go to:
htt
I've yesterday pinged the security Team as FYI on this.
In the meanwhile by tracking the upstream list this seems to be the follow up
fix:
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=141a26f979b4bc959d8e866a295e24f8cf456920
With the following being related
https://thekelleys.org.uk
Hi, this somewhat sounds like beign affected by translation issues. So
if I misunderstood you, please let me know and try try to clarify the
misunderstanding.
> I found the windows vm that I boot with 2C16G40G
Which number is that?
Is this especially about very huge instances or was that meaning
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
> Technically, is the GUI that facilitates easy sharing a part of Files and
> therefore Ubuntu? In
> light of your understanding that this operation is in fact possible, it seems
> that that the GUI
> is the faulty component.
>
> I view samba and its tools as an implementation detail of the shar
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915006
Title:
Consider merging 4.0-5 for Hirsute
To manage notifications about this bug go
> First of all, 2C16G40G is my vm flavor specification(2 vcpus, 16G ram,
> 40G disk), and this issue occurred regardless of what ram configured.
Thanks for clarifying
> In short, this issue is that the compute node will allocated 16G ram by
> `top -p ` when I boot a 16G ram windows vm instead of
This now has a related upstream issue
https://gitlab.com/libvirt/libvirt/-/issues/135
** Bug watch added: gitlab.com/libvirt/libvirt/-/issues #135
https://gitlab.com/libvirt/libvirt/-/issues/135
** Also affects: libvirt via
https://gitlab.com/libvirt/libvirt/-/issues/135
Importance: Unkn
** 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/1915828
Title:
pacemaker fails to release clustered filesystem dlm locks on failover
To manage notifications about this bug
** Changed in: mtd-utils (Ubuntu Hirsute)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913321
Title:
[MIR] iniparser (dependency of mtd-utils)
To manage notif
FYI - MIR review assignments done in MIR Team meeting.
** Changed in: libmodule-find-perl (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: libmodule-scandeps-perl (Ubuntu)
Assignee: (unassigned) => Matthias Klose (doko)
** Changed in: libsort-nat
Public bug reported:
qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz
Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages
Error:
../../disa
Public bug reported:
On install:
Setting up python3-rtslib-fb (2.1.74-0ubuntu1) ...
Job for rtslib-fb-targetctl.service failed because the control process exited
with error code.
See "systemctl status rtslib-fb-targetctl.service" and "journalctl -xe" for
details.
invoke-rc.d: initscript rtslib-
P.S. I'm not sure how this evaded our detection on Sergio's merge in
January nor in Groovy by Rafael. Maybe I'm mis-interpreting all the data
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916715
Ti
*** This bug is a duplicate of bug 1864279 ***
https://bugs.launchpad.net/bugs/1864279
Hi Björn,
that sounds very familiar - I think the discussion around this is already
happening in bug 1864279
Please chime in there ...
I'm marking it as a dup.
** This bug has been marked a duplicate of bu
We'd want to fix groovy as well I guess, adding server-next tag.
** Also affects: python-rtslib-fb (Ubuntu Groovy)
Importance: Undecided
Status: New
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: tgt (Ubuntu)
Status: New => Invalid
** Changed in: multipath-tools (Ubuntu)
Status: New => Invalid
** Changed in: fio (Ubuntu)
Status: Triaged => Fix Released
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Ub
Complete in Hirsute as well
postgresql-13 | 13.2-1 | hirsute | source, amd64, arm64, armhf, i386, ppc64el,
riscv64, s390x
** Changed in: postgresql-13 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've found no other issues and also the multitude of dep8 tests all completed.
https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#postgresql-10
https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#postgresql-9.5
Per the
Upstream
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
** Changed in: libmodule-find-perl (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Changed in: libmodule-find-perl (Ubuntu)
Status: New => Incomplete
--
You
** Changed in: python-rtslib-fb (Ubuntu Groovy)
Assignee: (unassigned) => Utkarsh Gupta (utkarsh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916715
Title:
fails on install due to systemd-se
You had a whitespace issue in the changelog, but other than that all seem
reasonable.
Thanks for starting the discussion with Debian as all our delta seems to be
autopkgtest related maybe we can sort it out.
Sponsored and later needs to be ran against the other new bits to then
hopefully work.
Hi,
to simplify the following text let us call order that lists 1-1 first "1-1" and
the one that lists 11 first "11".
I checked the following:
bionic container (up to date) => 11
focal container (up to date) => 1-1
hirsute container (up to date) => 1-1
bionic vm (up to date) => 11
bionic vm (down
FYI - This happens only to a login shell
$ ssh ubuntu@192.168.122.177 "env | grep LC_NUM";
LC_NUMERIC=de_DE.UTF-8
ssh ubuntu@192.168.122.177 -t 'bash -l -c "env | grep LC_NUM"'
LC_NUMERIC=C.UTF-8
And while downgrading I saw the suspicious
/etc/profile.d/01-locale-fix.sh: line 2: /usr/bin/locale-
FYI: Until resolved, hard setting the "other" LC_* values will get you
either behavior as you need it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916935
Title:
Major changes in sorting method up
Indeed @Axel.
But this will onl really resolve after Hirsute as in the fight for Priorities
the security reviews of the related packages lost to other more urgent issues.
Due to that 4.x can not migrate into hirsute release this cycle, but
will as soon as the related MIR
(https://bugs.launchpad.n
** 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/1916541
Title:
smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade
To manage notifications about this bug g
Hmm,
since you have tested this before I wonder, but here
https://launchpad.net/ubuntu/+source/puma/4.3.6-1ubuntu3
https://launchpadlibrarian.net/525169018/buildlog_ubuntu-hirsute-s390x.puma_4.3.6-1ubuntu3_BUILDING.txt.gz
This is an FTBFS on s390x now.
Please debug and resolve!
--
You received t
Julian said in comment #9 that 2.5.1 would be good.
But then Florians comment #11 does not make me feel so sure.
In any case we now have:
libseccomp | 2.5.1-1ubuntu1 | hirsute| source
Does that mean we are good now?
Subscribing Alex who did the 2.5.1 upload ...
Thanks, thereby libmodule-find-perl is ready then.
Let us see how it overall looks once the other got to do their reviews.
** Changed in: libmodule-find-perl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Ok, thanks - thereby this seems to be ready.
Marking as such.
** Changed in: iniparser (Ubuntu Hirsute)
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/1913321
Title
There still are known issues around volume usage with apparmor isolation which
are tracked elsewhere. But you are right - thanks Garry - one of the inderlying
issues about
a) modifying non-local storage
(https://listman.redhat.com/archives/libvir-list/2020-November/msg01252.html)
b) internatl sn
Following the arguments made before on this bug about this being an
uncommon or maybe even unsupported setup variant I'm marking the tasks
that represent backports as won't fix.
This setup only becomes more reasonable after [1] which isn't on
anyone's active work-queue atm AFAIK - and even then is
*** This bug is a duplicate of bug 1925488 ***
https://bugs.launchpad.net/bugs/1925488
Public bug reported:
I was upgrading Hirsute to hirsute-proposed and got this text:
"
Pending kernel upgrade
Newer kernel available
*** This bug is a duplicate of bug 1925488 ***
https://bugs.launchpad.net/bugs/1925488
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1928625/+attachment/5498145/+files/AudioDevicesInUse.txt
--
You received this bug notification because y
*** This bug is a duplicate of bug 1925488 ***
https://bugs.launchpad.net/bugs/1925488
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1928625/+attachment/5498146/+files/CurrentDmesg.txt
--
You received this bug notification because you are a m
*** This bug is a duplicate of bug 1925488 ***
https://bugs.launchpad.net/bugs/1925488
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1928625/+attachment/5498147/+files/Dependencies.txt
--
You received this bug notification because you are a m
*** This bug is a duplicate of bug 1925488 ***
https://bugs.launchpad.net/bugs/1925488
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1928625/+attachment/5498148/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because
*** This bug is a duplicate of bug 1925488 ***
https://bugs.launchpad.net/bugs/1925488
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1928625/+attachment/5498149/+files/ProcEnviron.txt
--
You received this bug notification because you are a mem
*** This bug is a duplicate of bug 1925488 ***
https://bugs.launchpad.net/bugs/1925488
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1928625/+attachment/5498150/+files/ProcInterrupts.txt
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1925488 ***
https://bugs.launchpad.net/bugs/1925488
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1928625/+attachment/5498151/+files/ProcModules.txt
--
You received this bug notification because you are a mem
*** This bug is a duplicate of bug 1925488 ***
https://bugs.launchpad.net/bugs/1925488
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1928625/+attachment/5498152/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubun
*** This bug is a duplicate of bug 1925488 ***
https://bugs.launchpad.net/bugs/1925488
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1928625/+attachment/5498153/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: New => Confirmed
Testing former status with 5.11.0-17-generic
Journal:
Add:
May 17 05:56:26 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3,
anc=0, erc=4, rsid=5
May 17 05:56:26 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3,
anc=0, erc=4, rsid=0
May 17 05:56:26 h kernel: virtio_blk
Thanks TJ!
I agree to "I am extremely confused" - /e as well :-)
I mean I'm glad it was resolved by kernel upgrades, but there isn't much
attack surface left to solve anything on the distro-packaging level.
Let me know if you find the underlying root cause so we can have a look
at it.
--
You r
Hi Nelson,
this is a deficiency in your installation.
The Multipath-tools package expects dm-multipath to exist and be a
loadable module.
And we see it fail loading - in your logs:
May 13 14:34:19 banana multipathd[70987]: start up
May 13 14:34:19 banana multipathd[70987]: read /e
Thanks for the test, that ensures it still is in 5.2
Unfortunately since a few days that isn't the very most recent version [1] as
6.0 release two weeks ago. I don't have a 6.0 version ready as Ubuntu package
yet that I could ask you to try.
Usually for an upstream bug report (which IMHO is the
From:
https://launchpadlibrarian.net/539104376/buildlog_ubuntu-impish-amd64.python-aws-requests-auth_0.4.3-2_BUILDING.txt.gz
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:232: cd
/<>/.pybuild/cpython3_3.9_aws-requests-auth/build; python3.9 -m
unittest discover -v /<>/aws_requests_auth
On Mon, May 17, 2021 at 3:01 PM John Hartley <1876...@bugs.launchpad.net> wrote:
>
> Hi Christian,
>
> now I have env setup that test is pretty straight forward.
Glad to hear that1
> $ qemu-system-x86_64 --version
> QEMU emulator version 6.0.50 (v6.0.0-540-g6005ee07c3)
...
>
> So looks like an up
** Also affects: qemu-gitlab via
https://gitlab.com/qemu-project/qemu/-/issues/337
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/1876678
Title:
Ubunt
Public bug reported:
[Impact]
* MRE for latest stable fixes of Postgres released on May 2021
[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.
[Regression P
Hi Markus,
yeah the intention is to pick one once we agree with Debian which one to not go
back&forth too often. That was discussion was stuck for a while but recently
unblocked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
It is in component mismatches as of today.
** Changed in: libmanette (Ubuntu)
Status: In Progress => 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/1918446
Title:
[MIR] libmanet
Hi,
there is a suspicious entry in the log
> debconf: unable to initialize frontend: Passthrough
> debconf: (Cannot connect to /run/user/1000/pk-debconf-socket: No such file or
> directory at (eval 18) line 3.)
> debconf: falling back to frontend: Noninteractive
I'm not sure what this is about b
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Thank you for reporting back ArTaX,
way too often these bug just hang around forever.
I'm glad to hear that the discussion indirectly resolved your issue - marking
the bug as invalid to properly close it.
** Changed in: open-iscsi (Ubuntu)
Status: Incomplete => Invalid
--
You received th
Hi Akanksha,
in your logs I see
mysqld is running as pid 9221
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.
Which implies it failed to start/restart on an upgrae,.
When looking for errors I f
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration problem
*** This bug is a duplicate of bug 1928568 ***
https://bugs.launchpad.net/bugs/1928568
Hi,
from your log
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 29776
Error: Unable to shut down server with process id 29776
dpkg: error processing package mysql-server-8.0 (-
*** This bug is a duplicate of bug 1928568 ***
https://bugs.launchpad.net/bugs/1928568
Hi,
from your log
Configurando mysql-server-8.0 (8.0.25-0ubuntu0.20.04.1) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 6866
Error: Unable to shut down server with process
*** This bug is a duplicate of bug 1928568 ***
https://bugs.launchpad.net/bugs/1928568
Hi,
from your log
mysqld is running as pid 21651
Error: Unable to shut down server with process id 21651
dpkg: error processing package mysql-server-8.0 (--configure):
I've found a few more like that and w
>From the various logs of the Dup'ed reports
2021-05-16T06:50:50.121637Z 0 [System] [MY-013172] [Server] Received SHUTDOWN
from user . Shutting down mysqld (Version:
8.0.25-0ubuntu0.20.04.1).
2021-05-16T06:52:11.158581Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld:
Shutdown complete (mysqld
>From the log:
mysqld is running as pid 40206
Error: Unable to shut down server with process id 40206
dpkg: error processing package mysql-server-8.0 (--configure):
installed mysql-server-8.0 package post-installation script subprocess
returned error exit status 1
I have found a few more of the
Thanks for reporting back Renat !
Closing the bug as invalid due to the above statement.
** Changed in: nagios-nrpe (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
PPA builds and tests ran:
Bionic - https://bileto.ubuntu.com/#/ticket/4555
Focal - https://bileto.ubuntu.com/#/ticket/4556
Groovy - https://bileto.ubuntu.com/#/ticket/4557
Hirsute - https://bileto.ubuntu.com/#/ticket/4558
Of those Focal-Hirsute look all good to me.
Bionic is a bit problematic wit
Of the above
- postgis
- psqlodbc
- slony1-2
All fail on:
/usr/bin/pg_virtualenv: line 174: /tmp/pgpassword.o2j3Z4: Permission denied
- postgresql-10
# Failed test 'default log is not used'
# at ./t/020_create_sql_remove.t line 133.
not ok 31 - default log is not used
...
not ok 36 - default
LXD uses a self built qemu and not "qemu (Ubuntu)"
I guess we will have to go to the upstream tracker eventually.
But for the time being switching it to a LXD task is slightly more correct.
** Package changed: qemu (Ubuntu) => lxd (Ubuntu)
--
You received this bug notification because you are a
> Hi Chhristian.
>
> I am going to try to install the ppa on a different Ubuntu 18.04 server
> and will let you know my findings.
Thanks in advance
> The only difference from the preduction servers and my test server is
> the following:
>
> Production servers were upgraded from Ubuntu 16.04 to Ub
Thank you Sergio,
so the one bit we still need now is security to say "yes we already monitor it
and it is ok to be promoted to main" which should be much quicker than a full
security review from scratch.
** Changed in: telegraf (Ubuntu)
Assignee: Didier Roche (didrocks) => Ubuntu Security
** Also affects: qemu (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Focal)
Status:
Thanks for the report, it LGMT and makes sense - although uretprobe inside of
s390x emulation is super rare and therefore not urgent IMHO.
I'd make this part of the qemu 6.0 (it is applied upstream after that) that
I'll prep for Ubuntu 21.10 and once that is completed consider SRUs.
If you are n
FYI postgresql-10 resolved, it was just flaky after all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928773
Title:
New upstream microreleases 10.17 12.7 13.3
To manage notifications about this b
Manual checks on armhf in canonistack
Test: postgis (but slony and psqlodbc have the exact same error)
1. installing dependencies (works as in the autopkgtest)
2. check pg_buildext supported-versions
=> 10
ok that works and is as expected
3. + pg_virtualenv -v 10 sh -e
/usr/bin/pg_virtualenv:
MP for the test hints of what I found in Bionic
https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/403517
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928773
Title:
New upstream
** Changed in: prips (Ubuntu)
Assignee: MIR approval team (ubuntu-mir) => 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/1930207
Title:
[MIR] prips package
ashers, etc) in Debian or Ubuntu or Upstream
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
** Changed in: prips (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Changed in: prips (Ubuntu)
Status: New => In Progres
@James - will the openstack team own (and you do the reviews) on these ?
** Changed in: jaraco.classes (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.launch
Hi gu,
I was trying to reproduce your case and spawned a guest to attach&detach an ISO.
When started the guest had this XMLrepresentation of the cd drive:
Yours was slightly different:
** Bug watch added: Debian Bug tracker #989378
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989378
** Also affects: dnsmasq (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989378
Importance: Unknown
Status: Unknown
--
You received this bug notification because
This was meant to and evaluated for promotion back to Bionic.
MIR Team Ack to the extra releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930207
Title:
[MIR] prips package
To manage notifica
Hi,
Thanks for outlining the steps that you follow.
"ubuntu iso will not trigger this" is interesting, so the guest must do
something unexpected.
I was fetching the very same iso CentOS-7-x86_64-Minimal-2009.iso and tried
this with Focal (as you did) and the virt stack of the most recent Hirsute
"4.vm will boot from iso again."
That is due to you having set the boot order manually, usually virt-manager
would boot from CD once and not again afterwards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
101 - 200 of 10728 matches
Mail list logo
