The testing and bisecting (suggested by Rafael) still need to be done.
This is in our backlog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900374
Title:
fence_aws in Focal and Bionic (LP:
Those are the proposed changes:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/fence-
agents/+git/fence-agents/+merge/417044
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965312
Title:
** Changed in: corosync (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use the hostname as the node name instead of hardcoded
** 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/1965312
Title:
[FFe] Add some agents to the -base binary package
To manage notifications about this bug go to:
Public bug reported:
I'd like to move the following agent from the fence-agents-extra binary
package to the fence-agents-base package:
- fence_sbd
- fence_ipmilan
+ fence_idrac
+ fence_ilo3
+ fence_ilo4
+ fence_ilo5
+ fence_imm
+ fence_ipmilanplus
In practice, fence_ipmilan and all
Filed a bug upstream: https://github.com/nov/json-jwt/issues/100
** Bug watch added: github.com/nov/json-jwt/issues #100
https://github.com/nov/json-jwt/issues/100
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually, this is an issue with ruby-json-jwt, and not ruby-openid-
connect itself which only depends on it.
** Also affects: ruby-json-jwt (Ubuntu)
Importance: Undecided
Status: New
** Tags added: transition-openssl3-jj update-excuse
--
You received this bug notification because you
Public bug reported:
ruby-openid-connect/1.2.0-2 do not support OpenSSL 3 which lead us to
the following test failures during build/autopkgtest time:
Failures:
1) OpenIDConnect::Discovery::Provider::Config::Response#public_keys
Failure/Error: instance.public_keys
ntu Groovy)
Status: Triaged => Won't Fix
** Changed in: corosync (Ubuntu Hirsute)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
** Changed in: corosync (Ubuntu Groovy)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
--
You received this bug notif
** Changed in: ruby3.0 (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/1964813
Title:
Script to generate Provides is broken
To manage
With the version in archive this is the summary of the execution of the
test suite during the build:
1494 runs, 3679 assertions, 28 failures, 395 errors, 0 skips
Applying the WIP patch (attached) the summary is:
1494 runs, 3964 assertions, 16 failures, 332 errors, 0 skips
** Patch added: "WIP
Thanks for the review Athos. I fixed the indentation and uploaded the
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964813
Title:
Script to generate Provides is broken
To manage
The attached debdiff fixes this issue. The changes are in
ruby3.0/3.0.3-1 in Debian:
https://salsa.debian.org/ruby-
team/ruby/-/commit/e6d192830071320905729c8560dbcb7fc5a99746
** Attachment added: "debdiff"
Public bug reported:
The script to generate the content of the Provides field of libruby3.0
(debian/genprovides) is not finding all the gems shipped in ruby3.0.
** Affects: ruby3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
ruby2.7 was removed from Jammy and ruby-defaults does not pull it in
anymore.
** Changed in: ruby3.0 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960185
I also filed this issue which involves some ruby-net-ssh test failures:
https://github.com/ruby/openssl/issues/500
** Bug watch added: github.com/ruby/openssl/issues #500
https://github.com/ruby/openssl/issues/500
** Changed in: vagrant (Ubuntu)
Status: New => Triaged
--
You
** Also affects: ruby-bcrypt-pbkdf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964025
Title:
Do not support OpenSSL 3
To manage
The solution for this issue reported in ruby/openssl will fix part of
the net-ssh issue:
https://github.com/ruby/openssl/issues/498
** Bug watch added: github.com/ruby/openssl/issues #498
https://github.com/ruby/openssl/issues/498
--
You received this bug notification because you are a
It is also impacting vagrant already in Jammy (the release pocket). The
following does not work because of this issue:
$ vagrant init debian/buster64
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in
This issue is currently blocking ruby2.7 removal from Jammy. The removal
requires the migration of ruby-bcrypt-pbkdf in jammy-proposed:
$ reverse-depends src:ruby2.7
Reverse-Depends
* ruby-bcrypt-pbkdf (for libruby2.7)
Packages without architectures listed are reverse-dependencies
Thanks for reporting this bug and trying to make Ubuntu better.
Looking at the logs, I noticed you tried to install mariadb on top of
mysql, that's not a supported use case and you should try to pick one of
them. Once you tried to install mariadb, mysql was supposed to be
removed and for some
Hi Norbert,
All the unmet dependencies you got are already available in the PPA. To
be in the safe side, you might want to specify all of them, one by one,
specifying the version in the PPA. This likely happened because you need
all the dependencies locked to the same version, since you did not
Thanks for describing your findings Norbert, and good to hear you have a
functional environment now. This might be helpful for others. In this
case, I do not think there is much we can do here, since this is a very
specific case in Oracle Cloud.
--
You received this bug notification because you
I upgraded openssh-server in a Impish VM locally and I was not able to
reproduce the issue you described. Are you able to provide some detailed
steps on how to reproduce this bug? Could you check if you face the same
issue with Jammy (22.04)?
--
You received this bug notification because you are
Thanks for letting us know Thomas, since this is already fixed in Jammy
I am marking this task as Fix Released. I am adding tasks for Focal and
Impish to check if this bug is still present there.
** Also affects: samba (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects:
Thanks for letting us know John. I am subscribing ubuntu-server so we
can take a look at this update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963831
Title:
Open-vm-tools 12.0.0 has been
Thanks for taking the time to file this bug and try to make Ubuntu
better.
After taking a look at the mentioned file
(debian/etc/conf.d/20-policy_banks in the source package), it seems that
you are right, this config has no effect since there is no definition of
`$policy_bank{'WHITELIST'}`. In
*** This bug is a duplicate of bug 1960454 ***
https://bugs.launchpad.net/bugs/1960454
Thank you for reporting this bug and trying to make Ubuntu better.
From the logs:
MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of
symbolic links: '/etc/mysql/my.cnf'
Since it seems
Public bug reported:
Upstream still does not support OpenSSL 3, and due to that a bunch of
tests are failing. Fedora has been seeing the same problem and they
filed a bug upstream:
https://github.com/net-ssh/net-ssh/issues/843
** Affects: ruby-net-ssh (Ubuntu)
Importance: High
The agents in resource-agents-base did not require any change. And I was
not able to find any occurrence of this type of issue with a simple grep
command in the other agents inside the extra package. If someone find
any issue please file another bug describing that.
** Changed in: resource-agents
The scope of this bug is only the agents present in
{resource,fence}-agents-base which are in main. The other agents in
{resource,fence}-agents-extra should work just fine but they are not
curated by the Ubuntu Server team.
--
You received this bug notification because you are a member of Ubuntu
The scope of this bug is only the agents present in
{resource,fence}-agents-base which are in main. The other agents in
{resource,fence}-agents-extra should work just fine but they are not
curated by the Ubuntu Server team.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: vsftpd (Ubuntu)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
** Changed in: vsftpd (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Tags removed: server-todo
** Tags added: server-next
--
You received this bug notification b
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
In this case, what you described is exactly what is expected. The
/etc/cron.d/php file is expected to trigger the execution of the
/usr/lib/php/sessionclean script only in systems not running systemd.
That's why we have
Thanks for reporting this bug and trying to make Ubuntu better.
This is indeed something we can cherry-pick from upstream. I talked to
Athos (who did the last upload) and he will be working on it.
** Changed in: bind9 (Ubuntu)
Status: New => Triaged
** Changed in: bind9 (Ubuntu)
You can find the binaries of samba/2:4.7.6+dfsg~ubuntu-0ubuntu2.23 here
(clicking on the architecture you are using):
https://launchpad.net/ubuntu/+source/samba/2:4.7.6+dfsg~ubuntu-0ubuntu2.23
And you could download and install them if you want.
@Andreas do you think this is something
Thanks Michael, it indeed seems flaky. I'll be adding this bug to our
backlog to be tackled when we have some time to do it.
** Changed in: cluster-glue (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I did not find any Oracle specific doc on how to upgrade a Ubuntu system
to Impish, which is kind of expected since they do not support this use
case. I'd recommend you to try to use `do-release-upgrade` to do that.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Groovy and Hirsute reached the end of regular support, so I am marking
those tasks as Won't Fix.
** Changed in: apache2 (Ubuntu Groovy)
Status: Triaged => Won't Fix
** Changed in: apache2 (Ubuntu Hirsute)
Status: Confirmed => Won't Fix
--
You received this bug notification
The fix is available in freeradius v3.0.x, and since we have this
version in all currently supported Ubuntu releases I am marking this bug
as Fix Released.
** Changed in: freeradius (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member
** Changed in: multipath-tools (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/1961633
Title:
Consider dropping d/p/kpartx-Improve-finding-loopback-device-by-
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960036
Title:
[SRU] Doesn't regain quorum when tracked
** Changed in: vsftpd (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/1960837
Title:
New upstream version supports modern
After talking to the Security team, we agreed that once the packages
land in -updates they will upload a no-change rebuild to the security
pocket. I'll let them know when the packages land in -updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the investigation Liam. This is in our backlog for further
investigation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954306
Title:
Action `remove-instance` works but appears to fail
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
This is indeed something that we should ship in the next LTS release. We
do not carry any delta compared to the version in Debian, I'll ping the
Debian maintainer to try to get this new version there and then sync it
Norbert,
Could you also provide which open-iscsi version you are using? I was
checking the difference between open-iscsi in bionic and focal and the
upstream version is the same but some patches were applied. For
instance, this is one bug reported by one Orable Cloud user which was
fixed in
** Changed in: containerd (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: containerd (Ubuntu Impish)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(Ubuntu Impish)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: containerd (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: docker.io (Ubuntu Bionic)
Status: New => Triaged
** Changed in: docker.io (Ubuntu F
I am tracking the backport of the entire container stack (docker.io,
containerd and runc) in this bug:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1960449
Please refer to that when checking the status of the backport.
** Tags removed: server-todo
--
You received this bug notification
** 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/1960449
Title:
Backport container stack in Jammy
To manage notifications about this bug go to:
Public bug reported:
[Impact]
In order to follow our policy on keeping the container stack (docker.io,
containerd, and runc) up-to-date in our supported releases, let's
backport the stack in Jammy to Impish, Focal, and Bionic.
It is also important because the new releases contain some CVE
Thank you for taking the time to file a bug report.
From the logs, we can see that a mysql process not managed by the mysql
package was running during the upgrade:
Configurando mysql-server-8.0 (8.0.28-0ubuntu0.20.04.3) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as
Thank you for taking the time to file a bug report.
From the logs, we can see that a mysql process not managed by the mysql
package was running during the upgrade:
Setting up mysql-server-8.0 (8.0.28-0ubuntu0.20.04.3) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as
Thank you for taking the time to file a bug report.
From the logs, we can see that a mysql process not managed by the mysql
package was running during the upgrade:
Setting up mysql-server-8.0 (8.0.28-0ubuntu0.20.04.3) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as
Thank you for taking the time to file a bug report.
From the logs, we can see that a mysql process not managed by the mysql
package was running during the upgrade:
Setting up mysql-server-8.0 (8.0.28-0ubuntu0.20.04.3) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as
Thank you for taking the time to file a bug report.
From the logs, we can see the following:
2022-02-05T04:58:04.67Z 1 [ERROR] [MY-012592] [InnoDB] Operating system
error number 11 in a file operation.
2022-02-05T04:58:04.655597Z 1 [ERROR] [MY-012596] [InnoDB] Error number 11
means
Thank you for taking the time to file a bug report.
From the logs, we can see that a mysql process not managed by the mysql
package was running during the upgrade:
Setting up mysql-server-8.0 (8.0.28-0ubuntu0.21.10.3) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as
Thank you for taking the time to file a bug report.
Checking your dpkg history log I see you tried to remove python in all
costs from your system (I am not sure why you were trying to do that),
you purged (or at least tried to) multiple times some key packages, I
believe that left your system in
** Description changed:
[Impact]
If a user is tracking a process with PID > 32767 keepalived will not be
able to work as expected.
This bug was fixed upstream here:
https://github.com/acassen/keepalived/commit/23a5b8113bf0b8ec4718443df0406882e8e4d831
[Test Plan]
Launch
** Changed in: keepalived (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960036
Title:
[SRU] Doesn't regain quorum when tracked process
** Description changed:
+ [Impact]
+
+ If a user is tracking a process with PID > 32767 keepalived will not be
+ able to work as expected.
+
+ This bug was fixed upstream here:
+
https://github.com/acassen/keepalived/commit/23a5b8113bf0b8ec4718443df0406882e8e4d831
+
+ [Test Plan]
+
+ Launch
** Summary changed:
- Doesnt regain quorum when tracked process restarts
+ [SRU] Doesn't regain quorum when tracked process restarts with PID > 32767
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the investigation. I agree with your assessment Christian,
backport only the fix seems to be the way to go.
I'll be trying to define a test case for this SRU based on the info we
already have.
Adding server-next tag and setting the importance to high.
** Changed in: keepalived
Thanks for testing it before the Jammy release, it is appreciated.
This is expected if you did not enable jammy-proposed. The current ruby
dependencies in the release pocket were built against ruby2.7, so even
if you install only ruby3.0 its dependencies will pull in ruby2.7. We
need to make
** Changed in: byobu (Ubuntu)
Status: New => Triaged
** Changed in: byobu (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959630
Title:
provide
** Changed in: multipath-tools (Ubuntu)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946834
Title:
Merge multipath-tools f
Public bug reported:
According to the Debian maintainer this package is not functional at the
moment, he also mentioned that he will request a removal in Debian as
well. Since this is currently blocking the ruby-defaults migration I'd
like to request its removal from Ubuntu. It has not reverse
** Changed in: ruby3.0 (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: rubygems (Ubuntu)
Status: Triaged => 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/1946190
You are right, I did not backport the fix to the older LTS releases yet,
it is still in my todo list. I was trying to convince the Debian
maintainer to accept the change but he refused to do that. I was not
willing to carry this as a delta and force us to do merges from now on,
I'd prefer to keep
ged in: rubygems (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: ruby3.0 (Ubuntu)
Status: New => Triaged
** Changed in: rubygems (Ubuntu)
Status: New => Triaged
** Changed in: rubygems (Ubuntu)
Importance: Undecided => High
** Chang
affects: containerd (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: containerd (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: containerd (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskan
Robie, from the SRU team, asked for more deep understanding on why this
was working before (without systemd) and in Focal (with systemd) stopped
working. This is still in our backlog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The upstream PR is still missing a review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912387
Title:
[Patch] check_snmp: support SNMPv3 TSM security (client certificates)
To manage
Thanks for taking the time and trying to make Ubuntu better.
The information you provided is not enough to triage this bug. I see
there is a segmentation fault but it is not possible to figure out
what's happening without more information. You can try to provide a
backtrace for us to help us
Hi Claude,
Are you able to roll rsycn back to version 3.1.3-8 to see if this gets
fixed? In 2021-11-16, we got an update to fix LP #1896251. FWIW, this is
the upstream patch that was applied:
https://github.com/WayneD/rsync/commit/af6118d98b3482cbcfc223bf2a0777bc19eccb02
--
You received this
Ideally, this package should be included in Debian first, and then we
sync it from there. In general, we include Ubuntu-only package if Debian
does not agree in including it and we have a compelling reason to do it.
If this package is included in Debian we could have more eyes on it and
it would
Thank you for taking the time to file a bug report.
In the dpkg logs, we can see that the dovecot service failed to start
because of this:
Jan 10 16:37:51 bfpro-fim-p01 dovecot[80782]: doveconf: Fatal: Error in
configuration file /etc/dovecot/conf.d/10-ssl.conf line 13: ssl_key:
Can't open file
Thank you for taking the time to file a bug report.
Checking the dpkg logs we can see:
Setting up mysql-server-8.0 (8.0.27-0ubuntu0.20.04.1) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 34837
Error: Unable to shut down server with process id 34837
dpkg: error
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
I am not familiar with Puppeteer but since you think this might be
related to kernel, could you please provide any system logs so we can
understand what is happening? In a regular arm64 VM I am able to run
"apt update
As mentioned by Shaun, the fixes for both CVEs already landed in the
security pocket, marking this bug as Fix Released.
** Changed in: apache2 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
Could you provide more information about the package version you are
using? And I think you forgot to add the attachment you mentioned. I
checked the package in Focal and it contains the fix that was applied in
LP
** Changed in: containerd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946851
Title:
Merge containerd from Debian unstable for 22.04
To manage
** Changed in: runc (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946899
Title:
Merge runc from Debian unstable for 22.04
To manage notifications about
** Changed in: containerd (Ubuntu)
Status: Triaged => In Progress
** 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.
@furlongm we try to always ship the latest version to our users, so yes,
this is our plan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955413
Title:
Update to containerd 1.5.9
To manage
This is still not fixed upstream. This is the PR containing the fix:
https://github.com/ClusterLabs/crmsh/pull/883
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947022
Title:
crm cluster health
Nothing to merge so far.
** Changed in: resource-agents (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946897
Title:
Merge resource-agents from Debian
** Changed in: containerd (Ubuntu)
Milestone: ubuntu-21.12 => ubuntu-22.01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946851
Title:
Merge containerd from Debian unstable for 22.04
To
** Changed in: runc (Ubuntu)
Milestone: ubuntu-21.12 => ubuntu-22.01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946899
Title:
Merge runc from Debian unstable for 22.04
To manage
Hi Bernd,
In the web page I linked in my first comment [1] you can find a section
telling you multiple ways to get the debug symbols in place. Did you try
any of the methods listed there?
[1] https://wiki.ubuntu.com/DebuggingProgramCrash
--
You received this bug notification because you are a
Hi,
Thanks for taking the time to file this bug. This seems to be a
recurrent question from users as you can see here [1]. Since rabbitmq-
server is in the main component [2], Canonical will keep supporting it
for the entire life cycle of the Ubuntu release, we will not move to a
newer version
Hi Adam,
Good to hear the issue was fixed for you. Tracking down the build
dependencies changes between those two versions might not be easy, you
could go through the publication history of each of them in Launchpad
and check but I do not think this worth. I am setting the status of this
bug to
Public bug reported:
Nowadays, crmsh is the default and supported tool to manage
Corosync/Pacemaker clusters, but in the future we plan to move to pcs.
We need to put some tests in place and make sure the entire stack is
sill working fine with it, moreover, we need to update all the docs to
tell
I just sync'ed version 1:2.2.4-0.2 from Debian. The only delta we had
was a patch to fix a FTBFS:
* d/p/0001-core-Fix-compiling-on-RHEL-9.patch: Fix FTBFS when
compiling with Linux 5.13/glibc 2.34 headers. (LP: #1939705)
This patch was already included in the version in Debian.
** Summary
In Debian, we have version 4.7.1-1, and in jammy 4.7.1-1ubuntu7. Nothing
to merge so far.
** Changed in: fence-agents (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In Debian, we have version 1.0.12-20, and in jammy version
1.0.12-20ubuntu2. Nothing to do so far.
** Changed in: cluster-glue (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually, we do not follow Debian, no merge is needed. However, upstream
already released version 1.5.8, and we should move to this version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946851
We already have version 0.8.5-2ubuntu2 in the release pocket and
0.8.5-2ubuntu3 in proposed, the latest version in Debian right now is
0.8.5-2. Therefore, nothing to do so far.
** Changed in: multipath-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
FWIW ruby-defaults/1:2.7.6 looks good in the excuses page, my idea is to
finish the rebuilds [1] and then upload a new version of ruby-defaults
disabling ruby2.7 and making ruby3.0 the default. The ruby3.0 MIR is
also ongoing.
You might be seeing some other ruby packages stuck in proposed but
201 - 300 of 1202 matches
Mail list logo
