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
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"
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,
+ #
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,
** 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,
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
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
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
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
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
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,
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
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
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
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:
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
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
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
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
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
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
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
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
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
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
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
# 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
# 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
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
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:
** 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:
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
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
** 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
** 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
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
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
** 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)
** 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.
+
+
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
This bug is no more an issue marking fixed
** Changed in: python-django (Ubuntu)
Status: New => Fix Released
** Changed in: django-mailman3 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
@Steve
Since the machines original use case is blocked until we know if we can go on.
Is the above enough for your to have a deeper look together with us?
If so please let Miriam know when once she can reset the machine to go
on with the MRE verifications that this was supposed to do :-)
--
You
FYI Change of the way this shall be tackled.
Per Steves very helpful comment in the MR to the seeds:
"I don't think we want either of these packages in main. They are transitional
packages; while the transition is still ongoing in Debian, in Ubuntu the
transition completed two LTS cycles ago.
** Changed in: keepalived (Ubuntu Xenial)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
** Changed in: keepalived (Ubuntu Bionic)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
** No longer affects: keepalived (Ubuntu Xenial)
** Changed in: keepalived (Ubuntu Focal)
** Changed in: keepalived (Ubuntu)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
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/1815101
Title:
[master]
This is somewhat opinion, so I'm happy to be convinced, but without either
- upstream progress to merge it there
or
- a good explanation why you think that wouldn't lock us in into hard to
maintain delta and issues to users
=> This won't be uploaded IMHO.
When that upstream response or
Debian is at 1.36 already, but without your change landing upstream that
doesn't help us :-/ (This was released before on January 2023 anyway)
The upstream contribubution was nice, but stalled with
http://lists.busybox.net/pipermail/busybox/2023-March/090211.html
It didn't come up again in
Marking todo to recheck how the situation is today.
** Tags removed: server-triage-discuss
** Tags added: server-todo
--
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/1815101
There has been not further update for too long, for now we consider it invalid.
Feel free to re-open if there is effort backing it up and motivation to bring
it to main.
** Changed in: opensc (Ubuntu)
Status: Incomplete => Invalid
** Changed in: pcsc-lite (Ubuntu)
Status:
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/442007
--
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/2015562
@Steve / @Vorlon
As outlined above we still can't see the diff in dependencies due to LTO.
But I'm sure you have seen it or you wouldn't have said so and we want to spot
where in our work the mistake was ...
Therefore let me ask - was that a local build that you did or is that somewhere
we
Hmm - odd,
Michal has checked the files and the build logs as he outlined above.
And in addition to all those checks being done, if we just grep for all final
dependencies and compare there is no difference (other than a glibc min version
level).
I know names are not too helpful:
- ~ppa1 =
Jorge very likely doesn't work on this anymore, so much time has passed.
The assignment created wrong expectations, let us unassign it to reflect that.
Also this isn't ubuntu specific, if tackled it should be done together with
Debian
which has this bug as well
FYI: might be related (or even dup) of bug 2002994
--
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/2012298
Title:
PasswordAuthenticaion in sshd_config.d
Status in openssh
** 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)
** 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:
** 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
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)
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
** 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
** 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
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
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
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
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
** 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
** 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
FYI proposed migration tests should be happy as soon as the migration-
reference run for ubuntu-fan completed (but queues are long)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
@SRU team - please consider accepting and merging the test hint [1] to
resolve the current blocker for this SRU.
[1]: https://code.launchpad.net/~paelzer/britney/+git/hints-
ubuntu/+merge/433770
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Great finding Miriam,
I've looked into it and fully agree.
Since I had all the data at that moment I filed bug 1998184 for ubuntu-fan.
Based on that we need to mask the tests and we can ignore them here in regard
to this SRU (until fixed in ubuntu-fan).
--
You received this bug notification
** Changed in: pcsc-lite (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1892559
Title:
[MIR] ccid opensc pcsc-lite
Status in
Hi Marius,
> What actually is the effect of the denial? Will qemu not use more than one
> CPU,
> or is it something less harmful?
Since the new interface is arch specific and new the code does fall back
tot he old way.
226 /* On some architectures it is possible to distinguish between
Submitted upstream:
https://lists.ubuntu.com/archives/apparmor/2022-November/012528.html
Once discussed and accepted there I suggest a backport to Kinetic.
I hope this debug and patch helps, but to manage expectations, I'd
hope/expect that someone usually looking after apparmor does that follow
Reported upstream at https://gitlab.com/apparmor/apparmor/-/issues/283
** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #283
https://gitlab.com/apparmor/apparmor/-/issues/283
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
That is the commit causing the change [1] in behavior.
That is pretty low level (in libc6) and will probably hit anything that
links against libnuma.
I think the fix should therefore go into
/etc/apparmor.d/abstractions/base
Today it has:
# glibc's sysconf(3) routine to determine free
** Changed in: openssh (Ubuntu Jammy)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
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/1986521
Title:
ssh client
** Changed in: apparmor (Ubuntu Jammy)
Assignee: Michał Małoszewski (michal-maloszewski99) => Andreas Hasenack
(ahasenack)
** Changed in: apparmor (Ubuntu)
Assignee: Michał Małoszewski (michal-maloszewski99) => Andreas Hasenack
(ahasenack)
--
You received this bug notification
** Tags added: cetest
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1989803
Title:
Adjust apport for the new Ubuntu debuginfod service
Status in Apport:
Fix Released
Focal:
- apparmor 2.13.3-7ubuntu5.1
- kernel5.4.0-109-generic
- libvirt:
a) base 6.0.0-0ubuntu8.16
b) server-backport 8.0.0-1ubuntu7.2~backport20.04.202210042317~ubuntu20.04.1
c) UCA Yoga 8.0.0-1ubuntu7.1~cloud0
With none did a restart trigger an issue as reported.
libvirtd is
I'll have a look for the same in server-backports ppa, but it might be
as easy as the old apparmor not knowing about these and failing. If that
is true we might need to remove them on the backports.
@Security - is there more to know about these particular features (will
they come to focal, is
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1989803
Title:
Adjust apport for the new Ubuntu debuginfod service
Status in Apport:
Fix
** Changed in: dnsmasq (Ubuntu Kinetic)
Assignee: (unassigned) => Lena Voytek (lvoytek)
** Changed in: dnsmasq (Ubuntu Jammy)
Assignee: (unassigned) => Lena Voytek (lvoytek)
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch
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
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
** 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
@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
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.
** 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
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 subscribed to rsync in
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.
/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 mem
** 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
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
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
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
** 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
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
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.
1 - 100 of 1232 matches
Mail list logo
