FYI, multiple parties and people promised me more input, but so far none
has arrived over the last weeks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1833322
Title:
It was nice to have LXD around and ready for many test/dev workloads,
and I feel it was worth it back then.
But we already replaced it with lxd-installer in minimal environments and it
was fine there too.
I never heard someone complaining that LXD takes a bit there, but every second
of boot time
On Fri, Feb 16, 2024 at 06:51:46PM -, Philip Roche wrote:
> @vorlon @jchittum @paelzer given the above findings are you still -1 on
> any snap preseeding? Based on the data, I vote not to preseed any snaps.
I was already leaning that way and thank you for adding the data.
I agree to not to pre
Hey Henry, thanks for chiming in and I agree in general that tech moved on.
Myself and others said similar before, thanks for adding more details and
voices - that is what such a discussion is about.
> they just don't go ping-ponging around between
In particular on this aspect, so much has happe
Interesting, that is more towards irqbalance than I heard so far.
thanks Fabio!
So we might end up needing to go like "Generally disabled except this
list of places [...] where it stays enabled".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
While there was sadly neither enough time not enough resources to do all
the deep dive analysis that could have been done, we succeeded by
reaching out to many more parties and got their input as well. Thank you
all!
Since Noble feature freeze is coming we need to make a call either way.
I propose
Steve was so kind reviewing and approving my proposal.
Doing that now is also helpful as it should make sure it still has quite some
exposure and thereby chances for people to report issues (vs if we'd land it
much later like after beta freeze).
Changes will:
- change the seeds in regard to irqb
FYI: Seed change landed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1833322
Title:
Please consider no more having irqbalance enabled by default (per
image/use-cas
FYI: updated ubuntu-meta, now in noble-proposed as version 1.532
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1833322
Title:
Please consider no more having irqbalanc
I've added a section to the release notes summing this up and linking
back here and to some of the past links.
** Changed in: ubuntu-release-notes
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
** Description changed:
+ Christian summarizes this after the great reports by Martin:
+
+ gnutls started to ship forceful disables in pkg/import/3.8.1-4ubuntu3
+ and added more later.
+
+ Due to that anything linked against gnutls while being apparmor isolated
+ now hits similar denials, preven
There is precedence in /etc/apparmor.d/abstractions/base holding various rules
like these
$ grep etc_ro /etc/apparmor.d/abstractions/base
@{etc_ro}/locale/** r,
@{etc_ro}/locale.alias r,
@{etc_ro}/localtime r,
@{etc_ro}/bindresvport.blacklistr,
@{etc_ro}/ld.so
Suggestion would be something like:
--- /etc/apparmor.d/abstractions/crypto.orig2024-03-11 11:05:24.027597234
+
+++ /etc/apparmor.d/abstractions/crypto 2024-03-11 11:06:12.035895701 +
@@ -24,4 +24,7 @@
/etc/crypto-policies/*/*.txt r,
/usr/share/crypto-policies/*/*.txt r,
+ #
FYI - submitted as https://gitlab.com/apparmor/apparmor/-/merge_requests/1178
@John if merged, would you mind adding a bug-ref to the Ubuntu upload changelog
so this bug 2056739 closes?
Given that there seems to be some agreement to fix this in apparmor,
I'll set the other tasks to "Won't Fix"
*
FYI the fix and a related cleanup are merged into upstream apparmor and
I'd expect the next upload to Ubuntu to then fix this issue.
@Martin
Thanks for the extra info for completeness, I assume we might find even more if
we spend more time (but tat would provide no extra gain).
@John
Up to you t
We are - as always - trying to clean and recheck old bugs.
This - sadly - clearly is one of them.
The situation is still correct, but with the full switch to networkd and
netplan as well as the demotion of ifupdown in later versions of Ubuntu this
has become even less important. And it didn#t eve
** Tags added: network-online-ordering
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1588915
Title:
ifup does not block for interface to be up with static addresses
Sta
Andreas fixed that in 2.4.49+dfsg-2ubuntu1 [Focal] which started to have
profile in openldap and include ssl_cert which (as Christian Bolz
outlined above) do include those paths.
# grep ssl_c /etc/apparmor.d/usr.sbin.slapd
#include
# grep enc /etc/apparmor.d/abstractions/ssl_certs
/etc/let
Thanks Simon to pick this up with your SME,
have you opened a tracker bug for this in Debian or Upstream so that we can
track it if it is implemented some day.
** Tags removed: server-triage-discuss
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: dnsmasq (Ubu
Hi,
I'm revisiting bugs that have been dormant for too long trying to retriage them.
In this case the current situation to me looks like:
- openldap change 3cd50fa having landed in v2.5.8 and later
- cyrus-sasl change 975edbb6 still isn't in any release AFAICS
- that is odd as https://github.com
Waiting for an answer, setting incomplete to reflect that
** Changed in: openldap (Ubuntu Bionic)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad
Thank you Lars,
Debian maintainer confirmed the issue and agreed on making the necessary
changes which is great as we do not have to deviate. They didn't land yet, but
once they do (which will update the now linked Debian bug).
>From there we can then consider SRUs - I added bug tasks for these.
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1805115
Title:
problem with (ubuntu/cosmic)mawk /^[[:space:]]*http://archive.ubuntu.com/ubuntu co
FYI - related but not a dup - bug 1828749
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1937953
Title:
systemd forcibly disables use of dummy/bond interfaces
Status in s
Hi,
I come by trying to clear old bugs that were dormant for too long either
resolving or reviving them.
First of all I can confirm what you have found (insmod vs modprobe
changes), but I also found why.
I've found that this makes modprobe work like before:
modprobe dummy numdummies=1
So I w
Due to a ping on IRC I wanted to summarize the situation here as it
seems this still affects people.
In nested LXD container we seem to have multiple issues:
- apparmor service failing to start (might need to work with LXD to sort out
why and how to fix it)
- if it doesn't work at least fail to
** No longer affects: libmnl (Ubuntu Impish)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl p
/rsync/-/commit/34390672fadd347f157148deb3b66cbf27ae6ed1
** Tags removed: needs-merge
** Tags added: needs-sync
** Changed in: rsync (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => Christian Ehrhardt
(paelzer)
--
You received this bug notification because you are a member
Test build in PPA: https://launchpad.net/~paelzer/+archive/ubuntu/kinetic-rsync
Once built I'll also run the autopkgtests there ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bu
andled as fast as I hoped :-/
Yielding back to Sergio
** Changed in: rsync (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Sergio Durigan Junior
(sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1897932
Title:
systemd-repart not packag
I was asked to add a Jammy task, I did so - the details and if that will
be done is up to your consideration/discussion/decision.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bu
@Michal
Sponsored for Kinetic, once complete there please have a look at considering an
SRU.
This might be on the brink between fix and feature depending on someones
POV.
Make your own decision and add some arguments for it to the SRU template
(if that is what you go for). Or explain why you dec
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1871465
Title:
ssh_config(5) contains outdated information
Status in openssh package in Ubunt
With Michal: Marked block-proposed, added SRU content, re-reviewed and
sponsored the upload to Focal-unapproved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1871465
Title
FYI: I've today had two systems exposing that issue.
The cleanup in comment #32 helped, but I wonder what caused it initially.
Sadly I can't recreate it anymore with a new system/container - might have been
related to the keying update to 2021.03.26 a few days ago.
--
You received this bug notif
Hi Jeremy
> I do not understand why bugs like this cannot get fixed even years after
> several people have reported the same issue and the repro steps are clear
I understand this might seem frustrating, but the TL;DR is: Because it
isn't as clear as it might seem
Detail:
As you see throughout t
Thanks for the great debug work so far already, I think it is "apparmor
or kernel" enough that we should add those packages and subscribe a few
folks we know dealing with those details - I'd start with jjohansen as
he'd be the best to map us to either knowledge or a known case.
** Also affects: ap
Hey Ravi,
thanks for driving this!
We see progress on the meta packages \o/.
Furthermore I was able to process many but not all of the related removals.
Therefore it might be time to re-check, summarize and double down on the
few tasks that are left to make it in time for beta freeze?
--
You re
** Description changed:
+ Window actions (like maximize) no more work in wayland for QEMU using
+ GTK backend once the guest UI is intialized.
+
+ This can be seen by running an installed or even a trial Ubuntu from an
+ ISO like:
+
+ $ qemu-system-x86_64 \
+ -boot d \
+ -cdrom ubuntu-22.04.
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2002994
Title:
sshd_config makes some changes awkward
Status in openssh package in U
I agree as well, it is great that we have .d function at all, but it could be
better.
As reported there is no control yet at what goes early or late and that would
be a great enhancement. Just including it late isn't an easy option either as
you might unintentionally to a different section that
Public bug reported:
Hi,
I just upgraded a system from Jammy to Lunar and openssh-server refuses to
upgrade well.
Setting up openssh-server (1:9.0p1-1ubuntu8) ...
Replacing config file /etc/ssh/sshd_config with new version
Replacing config file /etc/ssh/sshd_config with new version
Synchronizing
As expected, on reboot all is fine for the service status
ubuntu@node-horsea:~$ systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.service.d
└─0
Thank you Steve, documenting what kind of debug data you'd expect helps
me or anyone else who might run into this next time.
Once I'm done with my current tasks on this system I'll try to redeploy
and re-upgrade to check if it happens again.
--
You received this bug notification because you are
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1647285
Title:
SSL trust not system-wide
Status in ca-certificates package i
** Changed in: rsync (Ubuntu Jammy)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2007837
Title:
Regression
Hey,
it turns out this worked for most people but if you go into enough detail they
start to disagree.
This was discussed [1], got "no it is not supported" [2] and people saying "yes
we do" [3] and some people stating what I'd have expected [4] to be related to
only-auto-update.
But no matter w
This was done by Graham Inggs in
https://launchpad.net/ubuntu/+source/bridge-utils/1.7.1-1ubuntu1 and no
other merge was needed.
bridge-utils | 1.7.1-1ubuntu1 | lunar | source, amd64, arm64, armhf,
ppc64el, riscv64, s390x
=> Done (and thanks Graham)
** Changed in: bridge-utils (Ubuntu)
** Changed in: krb5 (Ubuntu Jammy)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1981697
Title:
KDC: weak crypto
** Changed in: cloud-initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1967593
Title:
kernel
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2000739
Title:
Window actions (like maximize)
Hi Athos,
agreed:
According to [1] all that is holding it back is MAAS still referrring to it.
But I'm afraid of doing the demotion last minute as a surprise to the wider
Ubuntu.
The MAAS team has been involved in planning and preparing for this.
They have committed to get rid of their dependenc
** Description changed:
- This was demoted due to LP: #2045577. This will keep showing in
- component mismatches as ipmitool for now.
+ This was demoted due to LP: #2045577.
+
+ This will keep showing in component mismatches as needed from MAAS (just
+ like ipmitool did for years) for now.
+
+ M
** Description changed:
+ This isn't really MIR, but a reminder found by the tooling that tells us
+ why it is no more in main >=Noble.
+
+ ---
+
This was demoted due to LP: #2045577.
This will keep showing in component mismatches as needed from MAAS (just
like ipmitool did for years) f
I've discussed with MAAS and Dimitri, we moved it to the community-maas seed.
=> https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/platform/+merge/457339
Thereby it should (tm) no more be in component mismatches.
The other AAs haven't replied yet if they'd need something else, that
answer migh
Verifying according to the instructions - Before the update I got this as
expected:
root@Jdnsmasq:~# dig A netflix.com @127.0.0.1
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: connection refused
;; communications error to 127.0.0.1#53: connection refu
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2037703
Title:
dpkg-reconfigure openssh-server doesn't ask questions again
Status in o
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2047082
Title:
upgrading openssh-server always shows error: rescue-ssh.target is a
disabled or
Hi and thanks for the report,
it seems that the automatic "try to backup and upgrade" failed.
That is usually due to local config that does not behave well as it needs
knowledge or assumptions the package can't have. Or at other times by using
features that have been removed.
The log output is a
Thank you for taking the time to report bugs and help make Ubuntu
better.
This looks like a local configuration issue rather than a bug in the
software itself. Please check your configuration to make sure it's
correct. If you need help configuring, you can get community support in
the Ubuntu chann
** Tags removed: server-triage-discuss
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2037703
Title:
dpkg-
Hey, while passing by I admit I only looked at the test plan and tried to get
this moving by executing it.
Thanks for hinting at these further things to check ...
I still had the environment around
root@Jdnsmasq:~# apt-cache policy dnsmasq
dnsmasq:
Installed: 2.86-1.1ubuntu0.4
Candidate: 2.8
Hi,
this was overlooked for too long but came up in bug 2046470 again which made me
see this for the first time.
I'd wish we'd have had that even a bit earlier e.g. to release it with
mantic and not half way through noble, but still now is the time to
still change the next LTS.
I needed to make
# Referred Arguments
An argument that might not have been so strong more than a decade ago
but is much more today is power savings and that is an aspect that comes up
over and over.
It also had reports of conflicts with power saving [10] and e.g. dynamically
disabling/enabling cores which is much
# Integration and maintenance
Despite some saying it is for the past only, it is regularly updated
and has multiple releases per year throughout all the time [4]. Those
updates flow well into Debian and Ubuntu - so it is not a classic "old
and outdated" case. And while not much changes in those up
# Actions by Others
Times have changes, as mentioned above the kernel learned many new tricks.
More new I/O hardware virtual or physical appeared that tries to be smart
and thereby sometimes conflict with what irqbalance does.
Some are mostly based on the links referred above, the Debian disucssi
# Summary
This discussion was seeminly easier to make the more dedicated to a singluar
use case you are - as then you have less "but what if" cases to consider.
That wide usage is great for Ubuntu but sometimes delays decisions.
List of reasons to remove it from the default dependencies:
- Seems
I subscribed a few people directly to get their input.
@Steve
I've subscribed you after trying to find, refer and summarize all of the past
to allow you and anyone else to read into this in one go. I think I'll need
your input as Architect and as participant of these discussions right from when
After all the history I was looking at where we are right now:
- irqbalance already is not in ubuntu-cloud-minimal images
- irqbalance is in normal cloud images and installed systems via the dep from
ubuntu-server
--
You received this bug notification because you are a member of Ubuntu
Touch see
Hi Steve,
> I see a lot of strong opinions ... I would want any decision to remove
> irqbalance from the desktop to be based on evidence, not conjecture.
I agree that there is plenty of opinion (often backing up each other with cyclic
links) and not much data. Hence my compilation of the history
Hi Ethanay
> All I can find is a recommendation not to use it on CPUs with 2 or fewer
> cores as the overhead is said to be too high
This isn't a real problem anyway, the service will stop immediately if only
running on one core - even if running on multiple cores with the same
cache (as the inten
Hi Mike
> SUSE ... says that the first step to get there is to disable
irqbalance
I've read the same, IMHO that is just "if you want to manually tune, disable
it" which does not imply that it is bad to have it. But this is how I read
it, I have not talked to the authors to get their underlaying r
Hi Dough
> If irqbalance is to be included by default, then there should be due
> diligence to demonstrate a clear benefit.
You are right that we should have that as well.
But this would be even more ture if this would be about "making it the default
when it was not before".
Right now (purely opi
Hi Paride
> Back in the day I asked upstream their take on irqbalance usefulness with
> newer kernels, here is their reply:
> https://github.com/Irqbalance/irqbalance/issues/151
Thanks for this and the other extra pointers.
The Debian bug was referenced before, AFAIC it is mostly around
a) the ke
I want to try to avoid that this becomes too stale, so I wondered
what we can do from here. Two things came to my mind.
On one hand I will try to use some indirect relations to pull in some
HW manufacturer experts. They often have large performance teams tracking
things like that against different
Pings done, in a perfect world (if all reply) that would cover more than
we ever need, but then there is 0% guarantee they even have time or care
about this at the moment :-)
If anyone has connections as well, please ask them to participate too.
--
You received this bug notification because you
Hi Etanay,
I realize I maybe wrote too much :-/
So I start with a TL;DR:
AFAICS you are right in all you say, but I think there can not be "one right
answer" anyway. Hence I'm trying to leave all parties their freedom of defining
what is important to them and try to learn from them what impact i
Since the discussion is no more only covering Desktop I updated the
title (thanks Seb128 for suggesting)
** Summary changed:
- Consider removing irqbalance from default install on desktop images
+ Please consider no more having irqbalance enabled by default (per
image/use-case/TBD)
--
You rece
Thank you Marco and Sebastien,
> * the launchpad buglist has been triaged a bit and fixed issues closed
Thanks!
>From your bug cleanup did you spot any kind of setup/HW that you want to
>restrict/exclude?
Was there any common pattern that makes up most of the formerly seen bad
reports?
> * the
On Mon, May 3, 2021 at 10:20 AM Ludovic Rousseau
<1892...@bugs.launchpad.net> wrote:
>
> opensc-pkcs11.so is a PKCS#11 lib so the its API conforms to the
> standard defined in https://docs.oasis-
> open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html
Thanks Ludovic for adding the expert
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
** 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
I was adding a few of the blocked packages as incomplete tasks to have
this bug update-excuse show up in excuses. Right now until we know
better I'd consider this a systemd issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Public bug reported:
Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
before now slipping into a bad mode.
Now it seems all tests failed in boot-and-services by hanging until killed by
VirtSubproc.Timeout of autokgtest.
The last [1] test log has a bit more, it shows a py
As I said I tried to recreate this, but it worked.
It was fine under Focal/5.4.0-53-generic Host with the Impish-armhf container.
Upgrading the host to impish it Impish/5.11.0-16-generic still works fine.
It seems it only fails in autopkgtest infrastructure, not sure why yet
:-/
--
You received
Public bug reported:
The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz
Bad:
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed: ('Con
FYI by tjaaltonen - there's another crasher in 3.66 on ppc64el..
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989410
So 3.66 won't be the "take this and it works" solution.
** Bug watch added: Debian Bug tracker #989410
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989410
--
You re
While we wait for 3.67 and maybe (Thanks Timo) for [1] I have ensured that we
have a 3.66 test build.
=> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4577/+packages
The check of it's delta also showed that we can drop a bit of it nowadays.
=>
https://code.launchpad.net/~paelzer/ub
I was able to verify that a merge of 3.66 would on Ubuntu trigger the
very same bug that Debian has blocking the dogtag-pki test on powerpc64.
=> https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-
ppa-service-4577/impish/ppc64el/d/dogtag-
pki/20210608_031158_a9d4a@/log.gz
--
You
There is another fix in master that belongs to
https://bugzilla.mozilla.org/show_bug.cgi?id=1566124 - I've bumped my
PPA build to include both as it is worth a try if this fixes the current
ppc64 issues in v3.66.
Build of 3.66-1ubuntu1~impishppa2 started, later on I'll let the
autopkgtests run.
*
Also blocking isc-dhcp now, added a task
** Also affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: isc-dhcp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Public bug reported:
Ubuntu https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu5 is an FTBFS
https://launchpadlibrarian.net/542966965/buildlog_ubuntu-impish-amd64.gdebi_0.9.5.7+nmu5_BUILDING.txt.gz
The same https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu4 worked
as it was builds against
This feels like a circle with nss/2:3.66-1ubuntu1~impishppa2 in
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4577/+packages now ppc64 works but s390x fails
with (on the surface) the same symptom as it started with in 3.63 :-/
I retriggered the tests to see if that is flaky or repro
** Branch linked: lp:~paelzer/gdebi/gdebi-fix-glib-2.68
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1931394
Title:
With glib2 2.68 gdebi is an FTBFS (hangs)
Status in gd
Reproducible, ppc64 is fixed and s390x broken by the latest 3.66 + fixes from
master.
Links:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_065306_2e698@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-trai
Without the recent PPC fixes s390x was broken as well, so I'm not saying "the
ppc fixes broke s390x":
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210608_073451_f187d@/log.gz
Instead there seems to be a new crash affecting s390x t
** Changed in: openssh (Ubuntu)
Assignee: Colin Watson (cjwatson) => (unassigned)
** Changed in: openssh (Ubuntu Trusty)
Status: Triaged => Won't Fix
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1761096
Title:
dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed
Status in
Thanks Seth and Robert,
I'll follows Seth advise and for now propose (B) being the fix for libvirt.
But I'll add a task for apparmor (which carries abstraction/namespace) as that
still might be an avenue worthwhile to follow independent to this libvirt fix.
If more people speak up or we find more
1 - 100 of 1289 matches
Mail list logo
