I am uploading src:runc to the SRU queue but it should land once the
src:runc-app is accepted from NEW (in all supported releases).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040460
Title:
MRE u
c (Ubuntu Mantic)
Status: New => In Progress
** Changed in: runc (Ubuntu Mantic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: runc (Ubuntu Jammy)
Status: New => In Progress
** Changed in: runc (Ubuntu Jammy)
Assignee: (unassigned) =&
** Description changed:
- Backport container-stack as MRE to noble once the update for noble has
- been completed.
+ [Impact]
-
+ In order to follow our policy on keeping the container stack (docker.io-
+ app, containerd-app, runc, runc-app, docker-buildx, and docker-
+ compose-v2) up-to-date
ntu Mantic)
Status: New => In Progress
** Changed in: docker-buildx (Ubuntu Jammy)
Status: New => In Progress
** Changed in: docker-buildx (Ubuntu Mantic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: docker-buildx (Ubuntu Jammy)
Assignee: (u
Hi Helga,
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
From what I understood this is an issue with the snap package of
Thunderbird, if that's the case you should try to report here (?):
https://snapcraft.io/thunderbird
I am not sure if this bug will reach the
Could you provide your config file? Also state if you applied any
customization in your set up? Those things would be useful to reproduce
what you described locally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Shouldn't this be marked as duplicate then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056443
Title:
CHECK_RCPT_SPF SPF check fails if inbound IP address is IPv6
To manage notifications about t
I am working on it.
** Changed in: containerd-app (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: docker.io-app (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: containerd-app (Ubuntu)
Status: New
Public bug reported:
ruby-gruff/0.6.0-2 do not support ruby-rmagick/5.3.0-2build2 and this is
blocking the ruby-defaults migration.
There is a new upstream release of ruby-gruff (a.k.a. version 0.23.0)
which seems to support this newer version of ruby-rmagick, however, it
requires some new depend
** Changed in: pcs (Ubuntu)
Status: New => In Progress
** Changed in: pcs (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/2040410
Title:
Me
Public bug reported:
ruby-rgfa/1.3.1+dfsg-2 does not support ruby 3.2. Many core feature of
this gem rely on methods that were removed from ruby 3.2. I do not
expect any fix from upstream, since the last commit is from 8 years ago:
https://github.com/ggonnella/rgfa
FWIW this is the autopkgtest l
Public bug reported:
diaspora-installer/0.7.18.2+debian4 do not support ruby 3.2. Initially
we have an issue with the configurate gem native extension build, which
can be seen in the autopkgtest log:
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/aut
Hi,
Could you please share the core dump with us? That would help us
investigate better this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/720638
Title:
snmpd crashes with segfault (
Hi Luís,
This CVE is indeed not fixed yet in none of the Ubuntu releases:
https://ubuntu.com/security/CVE-2022-22747
As you can see on the top of the page the priority was marked as Low, so
I think the Security team is not considering this too important. Maybe
someone from the Security team coul
*** This bug is a duplicate of bug 1960449 ***
https://bugs.launchpad.net/bugs/1960449
The backport of the following packages were done in Jammy, Impish and
Focal:
- runc version 1.1.0
- containerd version 1.5.9
- docker.io version 20.10.12
This is not fully complete (missing Bionic) because
ember)
** Changed in: containerd (Ubuntu)
Milestone: ubuntu-22.08 => ubuntu-22.09
** Changed in: containerd (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: docker.io (Ubuntu)
Milestone: ubuntu-22.08 => ubuntu-22.09
** Changed in: docker.io (Ubuntu)
** Changed in: cluster-glue (Ubuntu)
Milestone: ubuntu-22.05 => ubuntu-22.06
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971268
Title:
Merge cluster-glue from Debian unstable for kinetic
To
** Changed in: containerd (Ubuntu)
Milestone: ubuntu-22.05 => ubuntu-22.10
** Changed in: containerd (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: docker.io (Ubuntu)
Milestone: ubuntu-22.05 => ubuntu-22.10
** Changed in: docker.i
** Changed in: resource-agents (Ubuntu)
Milestone: ubuntu-22.05 => ubuntu-22.06
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971317
Title:
Merge resource-agents from Debian unstable for kineti
** Changed in: fence-agents (Ubuntu)
Milestone: ubuntu-22.05 => ubuntu-22.06
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971275
Title:
Merge fence-agents from Debian unstable for kinetic
To
** Description changed:
+ [Impact]
+
+ The package is FTBFSing in Jammy which does not allow anyone to perform
+ any kind of update there. This package is in main and to be fully
+ supported one needs to be able to rebuild it and perform updates.
+
+ [Test Plan]
+
+ Build the package in jammy s
Thanks for the feedback everyone. I'll give a chance to others to test
it over the weekend, if I get no negative feedback until Monday I'll be
uploading this fix to kinetic and SRU it to jammy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Changed in: rubygems (Ubuntu Kinetic)
Status: Triaged => Fix Committed
** Changed in: rubygems (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Thanks for reporting this bug Claudio.
As you might have expected I was not able to reproduce it locally. After
checking the the core dump, we can see the crash happened when executing
the sec_poll function in drivers/gamatronic.c file. I went through the
upstream history of this file and I found
tus: New => Triaged
** Changed in: rubygems (Ubuntu Jammy)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: rubygems (Ubuntu Kinetic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Tags added: server-todo
--
You received this bug
** Changed in: pmdk (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/1976279
Title:
FTBFS ppc64el: obj_ctl_arenas/TEST3 failure
To manage notifications about thi
Hi all,
I prepared a patch myself to fix this. Could you please test the package
in this PPA?
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/puppet/
This is a workaround and I'd like to make sure this is not impacting
anything else. Please, report back with your findings. Once we get
enoug
Thanks for the reproducer Mat! I can reproduce it locally now, and this
is also impacting kinetic. I'll be working on it.
** Changed in: puppet (Ubuntu Kinetic)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
libdancer2-plugin-passphrase-perl was removed from Debian testing in
February during the Perl transition [1], and it is blocking libdigest-
bcrypt-perl migration in kinetic for more than 120 days. This package is
also blocked in Debian unstable for more than 765 days [2]. This
Filed an upstream bug: https://github.com/piotrmurach/tty-
screen/issues/14
** Bug watch added: github.com/piotrmurach/tty-screen/issues #14
https://github.com/piotrmurach/tty-screen/issues/14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
As you can see in comment #17, I have not been able to reproduce the
error people are reporting, so I can't help with this analysis. From
what I understood, this is not crashing anything (like it is right now
when someone tries to create a symlink).
--
You received this bug notification because y
This fix is also released in kinetic, ruby-net-ssh/1:7.0.0~beta1-2
contains the fix.
** Changed in: ruby-net-ssh (Ubuntu Kinetic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Since no one gave me a way yet to reproduce the mentioned errors
locally, and the originally reported bug (the symlink issue) is fixed, I
am marking the verification as done.
Please, file a new bug with reproduction steps for the error you all
mentioned, so I can investigate it further.
** Tags r
Hirsute has reached the end of standard support.
** Changed in: exim4 (Ubuntu Hirsute)
Status: New => 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/1927755
Title:
Fix for CVE-2020-
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
From the sshd logs in the description we can see:
Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255:
/etc/ssh/sshd_config: line 125: Bad configuration option: Host
/etc/ssh/sshd_config: line 126: Ba
Considering that version 2.4.53 is fixed, this should land in Kinetic
soon. In order to fix this issue in Jammy, we need to follow the SRU
process [1], and to do that we would need to have a test case with
reproduction steps. Another thing that is needed here is to bisect the
changes between 2.4.52
According to the user report, the following bug is fixed in version
2.4.53:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1974251
Let's keep that in mind when finishing up the merge.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Trusty has reached the end of the standard support.
** Changed in: samba (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/1304557
Title:
rmdir: failed to
I did run autopkgtest locally using the proposed packages and it indeed
fixes the test failure. The log is attached.
** Attachment added: "log"
https://bugs.launchpad.net/ubuntu/+source/debos/+bug/1940077/+attachment/5592392/+files/log
--
You received this bug notification because you are a
Since we did not get a reply from the Debian maintainers I am proposing
the attached debdiff to fix this issue. As Steve suggested, I patched
the failing test to use --disable-fakemachine and adjusted the test
dependencies and added the needs-root restrictions.
** Attachment added: "debdiff"
h
Public bug reported:
[Availability]
ruby-webrick is already in Ubuntu universe since Jammy. It is an arch:all
package and it builds fine in amd64, all tests pass successfully. Here its LP
page:
https://launchpad.net/ubuntu/+source/ruby-webrick
[Rationale]
This ruby gem was embedded in the ruby
+1, please go ahead and sync it Athos.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971294
Title:
Merge nbd from Debian unstable for kinetic
To manage notifications about this bug go to:
https://
No, you do not need to enable any repository. ruby-net-
ssh/1:6.1.0-2ubuntu0.1 landed in jammy-updates which should be enabled
by default on your system.
The link to the stackoverflow page you sent is old, and at that time it
was broken. This fix was even acknowledged on an upstream issue:
https:/
** Changed in: apache2 (Ubuntu Eoan)
Status: Fix Released => 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/1641238
Title:
as a reverse proxy, a 100 continue response is sent prematu
** Also affects: mysql-5.5 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: mysql-5.5 (Ubuntu)
Status: Confirmed => Does Not Exist
** Changed in: mysql-5.5 (Ubuntu Trusty)
Status: New => Won't Fix
--
You received this bug notification because you are a me
What are the next steps here? Are people willing to try to promote wsdd
to main?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831441
Title:
Please add WS-Discovery ( WSD ) support for Windows Samb
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
From the attached logs:
May 12 08:50:07 paradise sshd[59551]: /etc/ssh/sshd_config: line 125: Bad
configuration option: Host
May 12 08:50:07 paradise sshd[59551]: /etc/ssh/sshd_config: line 126: Bad
configuration opti
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
I see you are using the option NO_AUTO_CREATE_USER in sql_mode, as you
can see here [1] this is no more supported in MySQL 8 which is the
version we have in Ubuntu 20.04. So to fix your issue you need to remove
that opti
You mentioned it is taking longer to process the request but it is
working. So I am setting the priority to Low and I am adding this bug to
the server team backlog. It will be looked at once we find some time.
** Changed in: openldap (Ubuntu)
Importance: Undecided => Low
--
You received this
** Changed in: tgt (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971330
Title:
Merge tgt from Debian unstable for kine
** Changed in: cluster-glue (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971268
Title:
Merge cluster-glue from Deb
** Changed in: containerd (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971269
Title:
Merge containerd from Debian unsta
** Changed in: corosync (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971270
Title:
Merge corosync from Debian unstable
** Changed in: openvpn (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971306
Title:
Merge openvpn from Debian unstable
** Changed in: fence-agents (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971275
Title:
Merge fence-agents from Deb
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971307
Title:
Merge pacemaker from Debian unsta
** Changed in: resource-agents (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971317
Title:
Merge resource-agents f
** Changed in: strongswan (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971328
Title:
Merge strongswan from Debian unsta
** Changed in: runc (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971320
Title:
Merge runc from Debian unstable for kine
** Changed in: targetcli-fb (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971329
Title:
Merge targetcli-fb from Deb
Sure, thanks for the bug report. However, this is just a deprecation
warning and it does not crash AFAIU, so I am setting the importance to
Low and will add it to the server team todo list.
** Also affects: ruby-faraday (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: rub
Since no one replied yet, I tried to setup a VM using vagrant as I
described in comment #2, and it worked as expected:
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_U
Thanks for working with upstream to fix this. Would you be willing to
backport this fix to Jammy? Or do you prefer me to do it?
For Kinetic we will be moving to the newer version (4.4.0 as upstream
suggested) so this will not be an issue. I am going to talk to the
Debian maintainer to see if we ca
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
I was not able to reproduce the issue you reported locally. Could you
please describe the previous status of you system and what did you do to
get into this error? That could help us understand what happened here.
I am
@peterzay did you try to boot the system when you got to the screen you
attached in comment #16? This is the UEFI interactive shell, it does not
look like a boot error. You might try to change to the UEFI directory,
maybe /EFI/BOOT, and execute the *.efi file in there. This might be a
matter of boo
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971489
Title:
exim4 GnuTLS breakage with outgoing TLS 1.3 "Resource temporarily
unavailable"
To manage notifications abou
Yes, it is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968039
Title:
DEP-8 test fails in Focal after Corosync update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
# Test Plan
$ lxc launch ubuntu-daily:jammy ruby-net-ssh-test
$ lxc shell ruby-net-ssh-test
# apt update && apt upgrade -y
# apt install -y ruby-net-ssh
# dpkg -l | grep ruby-net-ssh
ii ruby-net-ssh 1:6.1.0-2ubuntu0.1
all Ruby implementat
To be honest, the bug initially reported here is fixed, I just tried
what is described in the Test Plan section and it works:
root@puppet-test:~# dpkg -l puppet
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/R
According to the Gemfile, msgpack is not a mandatory dependency, so in
theory the lack of ruby-msgpack should not be a big deal. From Gemfile:
gem "msgpack", :require => false
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
)
Status: In Progress => Fix Committed
** Changed in: ruby-net-ssh (Ubuntu Jammy)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: ruby-net-ssh (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a
Thanks for testing the proposed package Adrián. Unfortunately, the
output you presented does not help much in identifying the root cause of
the error you got. Could you please try to pass '--verbose' and '--
debug' to see if we get more useful information? Just to make sure, by
the end of the comma
A PR adding support to openssl 3 was submitted here:
https://github.com/nov/json-jwt/pull/101
** Changed in: ruby-json-jwt (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: ruby-json-jwt (Ubuntu)
Status: New => In Progress
** Also affects: rub
** Changed in: ruby-net-ssh (Ubuntu Kinetic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964025
Title:
Do not support OpenSS
** Description changed:
+ [Impact]
+
+ puppet crashes if one tries to create/ensure symlinks via a puppet
+ manifest. I believe this is an feature broadly used by our users.
+
+ [Test Plan]
+
+ $ lxc launch ubuntu-daily:jammy puppet-test
+ $ lxc shell puppet-test
+ # apt update && apt install -
Should we re-assess this during the Kinetic cycle?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742761
Title:
Drop dh-apport to reduce delta with Debian
To manage notifications about this bug go
Thanks for getting back to us with more information Norbert.
I went through the Debian bug and it seems to be a linux bug instead of
ocfs2-tools one. The Debian maintainer came to a conclusion that this
commit needs to be included in the linux build:
From de19433423c7bedabbd4f9a25f7dbc62c5e78921
After a more in-deep analysis and trying to backport the patches
mentioned above I noticed some of them are not even applicable to the
version we have in the archive. The following patches will be added to
Kinectic, and later on backported to Jammy:
* PUP-10537 (https://tickets.puppetlabs.com/brow
/PUP-11048)
This is also related to ruby 3.0 transition. This is the commit:
https://github.com/puppetlabs/puppet/commit/93c86d6dc8
** Also affects: puppet (Ubuntu Kinetic)
Importance: Undecided
Assignee: Lucas Kanashiro (lucaskanashiro)
Status: Confirmed
** Also affects: puppet
Thanks for taking a look at this proposed change Robie. The behavior we
are trying to backport to Focal is already present in all supported
releases, Focal is the only one that differs at the moment.
What you said is indeed true, the default configuration file is not
production ready to most of th
** Tags added: server-todo
** Changed in: puppet (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969939
Title:
puppe
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
I did try to run the same command you did in a clean Jammy lxd container
and it just hangs:
root@bind9-test:~# dig google.com +nssearch
SOA ns1.google.com. dns-admin.google.com. 444516783 900 900 1800 60 from server
20
Forwarded the bug to debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1010237
** Bug watch added: Debian Bug tracker #1010237
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010237
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
python3-pkg-resources should indeed be a runtime dependency of
python3-mako, at least for the current version we have in the archive
which is 1.1.3. In this version, pkg_resources is conditionally
imported, I think this
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
It seems that you are trying to install mariadb which is not co-
installable with mysql, due to that it is trying to remove mysql. During
its removal it tries to stop the mysql service and the error happened
because the
@Stefan you might be correct. The development of run-one seems stalled
for many years, I subscribed Dustin (the maintainer) to see if we get
any feedback.
** Changed in: run-one (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs
We should try to take a look at this delta during the KK cycle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961633
Title:
Consider dropping d/p/kpartx-Improve-finding-loopback-device-by-
file.p
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
The attached logs are not that helpful to understand what is happening.
I did set up a Focal container and installed rabbitmq-server, also
changed the default config to match yours (setting "ulimit -n 1024"),
after that
Since this is a non-critical issue, I think it is best to wait until it
get merged upstream to fix it in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957924
Title:
rpc-worker: debugfs acce
Thanks for the detailed steps on how to reproduce the issue. I know you
faced this issue using vmware technologies but since I do not have a
setup in hands to test it, I gave it a try to reproduce it in my local
setup with qemu/libvirt and I was not able to get the same results:
$ dpkg -l sg3-util
# Verification for Impish and Focal - remaining packages
## Focal
### runc
lucas@poseidon:/tmp/test/runc-focal$ pull-lp-source runc focal
Found runc 1.1.0-0ubuntu1~20.04.1 in focal
Good signature by Lucas Kanashiro (0xF823A2729883C97C)
Downloading runc_1.1.0.orig.tar.xz from archive.ubuntu.com
Thanks for accepting the remaining packages into -proposed. I updated
the description as you requested, I hope that's enough. I'll be
verifying runc in impish-proposed and focal-proposed.
** Description changed:
[Impact]
In order to follow our policy on keeping the container stack (docker.
FTR runc is still waiting for approval (Focal and Impish). The SRU
exception was updated to allow that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960449
Title:
Backport container stack in Jammy
# containerd verification in focal-proposed and impish-proposed
## Impish
root@container-stack-verification:~/containerd# apt source containerd
Reading package lists... Done
NOTICE: 'containerd' packaging is maintained in the 'Git' version control
system at:
https://github.com/tianon/debian-cont
Hi,
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
This systemd-networkd behavior has been seeing in other bugs, like:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1815101
Could you please tell us which Ubuntu release you are using?
I am setting this
Hi Marcus,
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
With the information you provided is hard to predict what is happening
in your system. Could you share any information/config files/steps to
reproduce this issue? Otherwise we cannot act on this bug.
I am se
@jamesps this applies to Ubuntu Focal 20.04 as described in the manpage.
This seems to me a local configuration issue and not a bug in the
package. Due to that I am marking this bug as Invalid.
** Changed in: openssh (Ubuntu)
Status: New => Invalid
--
You received this bug notification be
@family-gan are you saying this is an issue in Ubuntu Impish (21.10)? It
seems to be already fixed in supported releases. Could you share any
steps to reproduce it? If you consider the issue you are facing
different than the one discussed in this bug please consider filing a
separate bug.
--
You
)
Status: Fix Released => In Progress
** Changed in: sbd (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968226
Title:
DEP-
According to the latest changes in the docker.io group SRU exception
approved here:
https://lists.ubuntu.com/archives/ubuntu-release/2022-April/005371.html
now, .0 releases of runc and containerd are eligible for backporting.
Considering that, could we now accept runc into {focal,impish}-proposed
101 - 200 of 1137 matches
Mail list logo
