ged
** Changed in: corosync (Ubuntu Hirsute)
Status: New => Triaged
** Changed in: pacemaker (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: corosync (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in
In case anyone here wants to try the proposed solution, I did upload
corosync version 3.0.3-2ubuntu2.2~ppa1 to my PPA and it indeed fixes the
issue, it uses the hostname as the node name by default now:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/ha-stack
I'll be working to release
The package is FTBFS on non-amd64 architectures (64-bits only) due to
LTO. I could disable LTO in d/rules as well but since the runc SRU was
unblocked (already landed) I am not sure if this is still an update we
want to land. WDYT?
--
You received this bug notification because you are a member
The last test re-trigger from laney passed so I am considering this is
not an issue anymore.
** Changed in: ruby2.5 (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As reference I found this bug report in Debian related to this issue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912748
If you prefer you can file a bug upstream and see what the maintainers
think about it, here is the link to do it:
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
If you check the killall manpage you will see the following option:
-e, --exact
Require an exact match for very long names. If a command name is
longer than 15 charac‐
ters, the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I did reproduce what you mentioned and I got this segfault when running
the mysql command:
root@mysql-triage:~# mysql --ssl-mode=DISABLED -h 127.0.0.1 -u root
--password=root < stdin.txt
mysql: [Warning] Using a
Thank you for taking the time to file a bug report.
I'd like to ask which Ubuntu release you are using. I see you are
installing postfix version 3.5.6-1 but this version is available in
Ubuntu Groovy, Hirsute and Impish (development release). This info is
important for us to try to reproduce the
Thank you for taking the time to file a bug report.
With what you mentioned is not possible to assess whether this is a bug
in the package. Could you please explain in details what you are trying
to do and also what you already did to achieve that? Moreover, public
bug reports are usually written
Thanks for checking Gustavo. Since you mentioned this is not
reproducible in Ubuntu 20.04 I'll be marking this bug as Invalid.
** Changed in: screen (Ubuntu)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
This is a change in the default corosync config file
(/etc/corosync/corosync.conf), it impacts pacemaker clusters but it is
not directly related to pacemaker. The change was made in Debian here:
https://salsa.debian.org/ha-team/corosync/-/commit/2f8aa88
Between corosync version 2.4.3 (present in
** Also affects: containerd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: containerd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: containerd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: containerd
Public bug reported:
[Impact]
runc has been updated to version 1.0.0~rc95 in all supported releases
(LP: #1927219). To make containerd better support this new runc version
we also need to update it. The current version of containerd in Impish
is 1.5.2-0ubuntu1 and this one has a better support
@Brian to be honest I also do not know how to mock the date in those
tests. I tried some options that I found on some forums but none of them
worked out. Upstream is still unresponsive and those same tests are also
failing in their master branch.
If you think this is not a suitable SRU I'd ask
I did the verification of the packages in -proposed in all releases:
Hirsute
---
ubuntu@hirsute:~/runc/runc-1.0.0-rc95$ dpkg -l runc
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required
runc (LP: #1929106).
-- Lucas Kanashiro Thu, 20 May 2021 10:53:22 -0300
ubuntu@hirsute:~/runc/runc-1.0.0-rc95$ sudo autopkgtest . -- null
...
autopkgtest [16:38:08]: summary
basic-smoke PASS
command1 PASS
Groovy
--
ubuntu@groovy:~/runc/runc-1.0.0
Regarding the golang-github-containers-common/0.33.4+ds1-1 regression in
Hirsute, it was reported here in LP #1931258 as a LTO optimization
issue. We could SRU this package adding the
export DEB_BUILD_MAINT_OPTIONS=optimize=-lto
to d/rules but I believe this does not worth a SRU. If the SRU team
Thank you for taking the time to file a bug report.
This is the error message presented by apt when trying to install mysql:
Setting up mysql-server-8.0 (8.0.25-0ubuntu0.20.04.1) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 57791
Error: Unable to shut down
** Also affects: clamav via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989549
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930393
Title:
Public bug reported:
Actually golang-github-containers-{common,image} are already present in
the lto-disabled-list but only for amd64. We have seen the following
build failures against both packages in Impish and Hirsute on non-amd64
arches:
# github.com/containers/storage/pkg/devicemapper
The containerd regressions in Focal and Bionic were already sorted out,
the tests are passing now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219
Title:
context deadline exceeded: unknown in
I've been trying to find a fix for the golang-github-containers-
common/0.33.4+ds1-1 regression in Hirsute but without success so far.
However, the issue seems to be unrelated to this runc SRU, it is a
compilation issue in one of its components:
# github.com/containers/storage/pkg/devicemapper
All comments regarding the reported regressions were added to LP
#1927219 and they apply here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929106
Title:
runc -v empty output
To manage
I confirmed the golang-github-docker-go-connections regression in
Hirsute and I filed another SRU bug to fix it:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-
connections/+bug/1930891
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After further discussion within the team we decided that using
ubuntu0.21.04.1 is the best option here. There is the unlikely but
possible case where -3 is removed from impish-proposed and Impish gets
released with -2.
** Attachment added: "debdiff3"
Thanks for taking another look on this Utkarsh!
We append ubuntu0.XX.YY.1 to the version string when we have the same
version in 2 releases but in this case this version was released only in
Hirsute, Impish was not released yet :)
I'll be uploading the last debdiff I attached.
--
You received
There you go, the attached debdiff has some DEP-3 headers in the added
patch.
** Attachment added: "debdiff2"
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+attachment/5502460/+files/debdiff2
--
You received this bug notification because you are
I tried to just import the patch added by the Debian maintainer with no
changes but I think it is better to add some DEP-3 headers as you
mentioned. Checking the upstream bug tracker I noticed I filed this very
same bug some months ago :) but no replies so far:
The attached debdiff adds the patch to skip the tests as mentioned in
the description and fixes the FTBFS.
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+attachment/5502458/+files/debdiff
** Description changed:
+
Public bug reported:
golang-github-docker-go-connections is FTBFS in Hirsute because a couple
of tests rely on an expired certificate. This failure is blocking the
runc migration.
The Debian maintainer fixed it in the next revision but it did not make
into Hirsute. The simple fix is to backport
Thanks for the testing Colin!
FYI I already uploaded the fix to Impish (development release) and as
soon it lands in the release pocket I can start the SRUs. At the moment
it is blocked by one regression:
https://people.canonical.com/~ubuntu-archive/proposed-
Thanks for the patches Sergio. The changes LGTM, the patch was provided
by upstream (more like a workaround for the stable release) and they
said it'd be safe.
A small thing I'd fix in the changelog of both packages is to align the
text better. Instead of:
* Fix FTBFS with OpenLDAP 2.5. (LP:
The maintainer will be uploading a fixed version (0.1.2-1) to Debian. We
will need to sync it when it gets available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929613
Title:
Unblock version
The description of this bug was updated after the renaming of the binary
packages happened. Now we have src:fence-agents providing the following
binary packages in Impish:
- fence-agents (transitional package)
- fence-agents-common
- fence-agents-base
- fence-agents-extra
If I got everything
There is still an issue with non-amd64 architectures. I filed a bug
upstream to start a discussion:
https://github.com/bdrung/bdebstrap/issues/2
** Bug watch added: github.com/bdrung/bdebstrap/issues #2
https://github.com/bdrung/bdebstrap/issues/2
--
You received this bug notification
Thanks for the review Andreas! Package uploaded:
$ dput ubuntu ../bdebstrap_0.1.1-2ubuntu1_source.changes
Checking signature on .changes
gpg: ../bdebstrap_0.1.1-2ubuntu1_source.changes: Valid signature from
F823A2729883C97C
Checking signature on .dsc
gpg: ../bdebstrap_0.1.1-2ubuntu1.dsc: Valid
The attached debdiff fixes the regression.
autopkgtest is happy now:
autopkgtest [17:59:38]: summary
unittest PASS
examples PASS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/1929613/+attachment/5500320/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929613
Title:
Public bug reported:
bdebstrap/0.1.1-2 is blocked in impish-proposed because of a missing
autopkgtest dependency on debian-archive-keyring.
I submitted a PR to upstream to fix this and it was already merged:
https://github.com/bdrung/bdebstrap/commit/91c4ac2a3b67e835eb628f11680bb9df17bf1e2f
Thanks for taking the time to file this bug.
Your analysis seems right and there is nothing we can do as Ubuntu,
upstream decided to remove that option and we cannot support it without
upstream. What you need to do is to avoid the usage of the
NO_AUTO_CREATE_USER sql_mode option if you want to
Thanks for the heads-up Graham. Our team will be taking a look at it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912390
Title:
[Patch] TLS/DTLS: inconsistent allowed_uses behaviour when in
Thanks for the heads-up Graham. Our team will be taking a look at it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912389
Title:
[Patch] SIGSEGV: crash when certificate contains extension longer
** Changed in: runc (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: runc (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: runc (Ubuntu Groovy)
Assignee: (unassigned) => Lucas Kanashiro (lucas
al; urgency=medium
- * Backport version 1.0.0~rc93-0ubuntu1 from Hirsute (LP: #1919322,
- LP: #1916485).
+ * Backport version 1.0.0~rc93-0ubuntu1 from Hirsute (LP: #1919322,
+ LP: #1916485).
- -- Lucas Kanashiro Tue, 16 Mar 2021 15:34:35 -0300
+ -- Lucas Kanashiro Tue, 16 Mar 2021
** Description changed:
+ [Impact]
+
+ Users cannot check the runc version running 'runc --version'. This is
+ not a big deal but it would land along with LP #1927219 which is an
+ important fix.
+
+ [Test Plan]
+
+ Check if 'runc --version' returns the runc version.
+
+ [Where problems could
** Also affects: runc (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Focal)
** Also affects: runc (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Groovy)
Thanks for taking the time to file this bug.
This is a known issue and I already addressed it in my PPA where I am
preparing the next version to be uploaded to the archive:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/container-
stack/+packages
Therefore, this will be fixed soon across
@Colin I updated my PPA with version 1.0-rc95 which also contains the
fix for CVE-2021-30465. Could you test this new version and make sure
your regression is fixed?
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30465
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1928635 ***
https://bugs.launchpad.net/bugs/1928635
Thank you for taking the time to file a bug report.
After checking the logs the only thing relevant to your problem was this
part of the apt log:
Setting up mysql-server-8.0 (8.0.25-0ubuntu0.20.04.1) ...
Thank you for taking the time to file a bug report.
After checking the logs the only thing relevant to your problem was this
part of the apt log:
Setting up mysql-server-8.0 (8.0.25-0ubuntu0.20.04.1) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 8278
Error:
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
ubuntu-advantage-tools does not provide only a way to enable ESM, it
also provides a bunch of other services (from the project README):
"The Ubuntu Advantage client provides users with a simple mechanism to
view,
Thank you for taking the time to file a bug report.
I created a Bionic container to test the upgrade of mysql version
5.7.21-1ubuntu1 to 5.7.34-0ubuntu0.18.04.1 and it worked as expected:
root@mysql-test:~# apt list --upgradable
Listing... Done
mysql-server-5.7/bionic-updates,bionic-security
** Description changed:
[Impact]
- This feature allows the use of other mechanisms to deal with failures.
+ This feature allows the use of other mechanisms to deal with failures
instead of fencing nodes (usually reboot a machine), and let for
instance MS SQL server handle some failures
** Description changed:
+ [Impact]
+
+ This feature allows the use of other mechanisms to deal with failures.
+ instead of fencing nodes (usually reboot a machine), and let for
+ instance MS SQL server handle some failures by itself. We can consider
+ this SRU as part of a "hardware enablement"
Thanks for raising this issue. The VERSION file is not missing but we
are not using the upstream Makefile to build the source, that's why the
version is not set.
I fixed this issue and uploaded the fix to my PPA (it might take some
minutes to get it published), now if you update the runc package
I updated the runc package to version 1.0-rc94 and it is available in
this PPA for testing:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/container-stack
Let me know if this indeed fix your issue. If yes, I'll update runc in
the development release (a.k.a. impish) and then start the SRU
I just noticed you filed a new bug here:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1927982
I replied to the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857404
Title:
Thank you for taking the time to file a bug report.
The error in the log is the following:
Setting up mysql-server-8.0 (8.0.23-0ubuntu0.20.04.1) ...
update-alternatives: error: alternative path /etc/mysql/mysql.cnf doesn't exist
[1mdpkg:[0m error processing package mysql-server-8.0
Thank you for taking the time to file a bug report and try to make
Ubuntu better.
The configuration process did hang in this part of the postinst script:
# We switched over to modules-load.d logic, so we have to take
# care of this in postinst now.
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
This bug is present in Debian as well and Ubuntu currently does not make any
changes to the Debian package. Therefore, this bug would be best fixed
directly in Debian, and then Ubuntu will pick up the fix
Thanks for the investigation! It seems that a bunch of regressions were
found in 1.0.0~rc93 as we can see in the 1.0.0~rc94 release notes:
"This release fixes several regressions found in v1.0.0-rc93. We
recommend users update as soon as possible."
@Tanmay, you did not provide some useful information. What are you
trying to achieve? What did you do? Did you change any default settings?
Without these kind of info we cannot distinguish this from a local
config issue or a real bug. Moreover, this should be reported as a
separate bug since this
Also please keep in mind that the usage of pcs is still not fully
supported by the Ubuntu community, we still recommend crmsh:
https://ubuntu.com/server/docs/ubuntu-ha-introduction
If you want to prepare a package to apply the upstream patch Paride
linked I'll be happy to review/sponsor it. For
Thanks for the review Dan! Some comments below:
- I'll make sure the Server team is subscribed to this package.
- Regarding the CVE-2019-10153 fix, it is mentioned in the changelog:
$ cat debian/changelog | grep -B2 -A4 CVE-2019-10153
fence-agents (4.3.3-2) unstable; urgency=high
*
FWIW I submitted a pacemaker merge proposal which add changes to
recommend fence-agents-supported. Since pacemaker is already in main the
fence-agents-supported package will need to be pulled in.
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/pacemaker/+git/pacemaker/+merge/402284
--
** Also affects: libvirt via
https://gitlab.com/libvirt/libvirt/-/issues/160
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692458
Title:
[21.10
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided => Low
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Availability]
fence-agents is present in the Ubuntu archive since Precise, it builds
fine and tests pass in all supported architectures. It was promoted in
Precise:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/897492
In Trusty it was demoted, not sure about
I am marking this bug as Won't Fix because the recommended way to fence
nodes on AWS is using the fence_aws agent present in the fence-agents
packages (already available in Bionic and Focal).
** Changed in: cluster-glue (Ubuntu Bionic)
Status: Confirmed => Won't Fix
** Changed in:
Thank you for taking the time to file a bug report.
I found the following in the log:
2021-04-24T15:06:45.359221Z 0 [ERROR] [MY-010262] [Server] Can't start server:
Bind on TCP/IP port: Address already in use
2021-04-24T15:06:45.359439Z 0 [ERROR] [MY-010257] [Server] Do you already have
@Kendrick could you please tell us which version of Ubuntu and qemu you
are using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323758
Title:
Mouse stops working when connected usb-storage-device
@fernando-ferraz I updated the bug description to try to make it more
general.
For the verification work needed by the SRU process you need to trigger
the bug, update the package to the version in -proposed, and then
demonstrate that the bug was fixed. If you can do this using your
SolidFire
The package built fine on LP which means all the upstream tests passed
during build time.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@mats if you still think this is a bug you can provide detailed
steps on how to reproduce it in a new system. Please, do not provide
steps using scripts found in non-official tutorials on the internet,
they are not supported by us. In case we reproduce it locally this
becomes actionable, until
I launched a brand new Focal container and tried to install libudev-dev,
it worked as expected:
root@libudev-test:~# apt install -y libudev-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is
** Changed in: net-snmp (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806421
Title:
perl_bulk_gets patch breaks some scripts
To manage
More detailed analysis of the reverse build dependencies:
Groovy
==
$ reverse-depends -r groovy -b docker.io
Reverse-Testsuite-Triggers
* python-docker
* ubuntu-fan
* ubuntu-make
Status of the reverse build dependencies listed above in Groovy:
- python-docker
+ It builds fine with the
Public bug reported:
Groovy
==
ubuntu-make/18.09+disco1 currently FTBFS in Groovy. The following tests
are failing during build time:
==
ERROR: we deliver one successful download under ssl with known cert
Public bug reported:
systemd-docker/0.2.1+dfsg-2 currently FTBFS in Bionic. A build
dependency seems to be missing:
src/github.com/ibuildthecloud/systemd-docker/main.go:19:2: cannot find package
"github.com/docker/docker/pkg/mflag" in any of:
Public bug reported:
notary/0.1~ds1-1 currently FTBFS in Bionic. A build dependency seems to
be missing:
src/github.com/docker/notary/cmd/notary-server/main.go:25:2: cannot find
package "github.com/Sirupsen/logrus/hooks/bugsnag" in any of:
** Also affects: nomad (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
Groovy
=
nomad/0.10.5+dfsg1-1ubuntu2 currently FTBFS in Groovy. The following
test has been failing:
=== CONT TestServer_Reload_Vault
testing.go:129: timed out
Public bug reported:
Focal
=
cadvisor/0.27.1+dfsg2-4 currently FTBFS in Focal. A build dependency
seems to be missing:
src/github.com/google/cadvisor/container/common/inotify_watcher.go:20:2: cannot
find package "golang.org/x/exp/inotify" in any of:
Public bug reported:
golang-github-docker-libnetwork/0.8.0-dev.2+git20170202.599.45b4086-3
currently FTBFS in Bionic. The following error is reported during build
time:
github.com/docker/libnetwork
# github.com/docker/libnetwork
src/github.com/docker/libnetwork/controller.go:1096:69: undefined:
** Summary changed:
- FTBFS
+ FTBFS in multiple Ubuntu series
** Also affects: nomad (Ubuntu Focal)
Importance: Undecided
Status: New
** Description changed:
+ Groovy
+ =
+
nomad/0.10.5+dfsg1-1ubuntu2 currently FTBFS in Groovy. The following
test has been failing:
===
Public bug reported:
nomad/0.10.5+dfsg1-1ubuntu2 currently FTBFS in Groovy. The following
test has been failing:
=== CONT TestServer_Reload_Vault
testing.go:129: timed out while shutting down server
--- FAIL: TestServer_Reload_Vault (60.08s)
FAIL
FAILgithub.com/hashicorp/nomad/nomad
The test plan indicates that the build time tests and DEP-8 tests should
pass.
- Both packages built fine on LP.
- libpod DEP-8 test is passing but the golang-github-containers-buildah DEP-8
test is failing for a while so I'd ask to ignore it.
golang-github-containers-buildah autopkgtest
I have checked the reverse build dependencies and I noticed the
following FTBFS due to the new docker.io version:
- golang-github-fsouza-go-dockerclient (bionic)
Other reverse build dependencies are failing to build but it is not
because of the container stack update, they were failing already
Package uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923108
Title:
FTBFS against docker 20.10
To manage notifications about this bug go to:
Thanks for the review Sergio!
I indeed forgot the add references to the LP bug, it is done now.
Regarding the DEP-8 tests you are right, there is no definition for
them. I'll update the bug description to add the upstream tests executed
during build time instead of DEP-8 tests, I think we do not
** Description changed:
[Impact]
The version in Bionic FTBFS against docker 20.10 currently in bionic-
- proposed. This would be consider a regression.
+ proposed. This would be considered a regression.
[Test Plan]
DEP-8 tests passing.
[Where problems could occur]
There
The attached patch fixes the FTBFS in bionic (with bionic-proposed
enabled). I uploaded this packages to this PPA to confirm that:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/buildah-and-libpod
** Attachment added: "debdiff"
Public bug reported:
[Impact]
The version in Bionic FTBFS against docker 20.10 currently in bionic-
proposed. This would be considered a regression.
[Test Plan]
DEP-8 tests passing.
[Where problems could occur]
There could be any breakage related to the move from Go 1.10 to 1.13.
Moreover,
Sorry, I forgot to update the tags. Nothing is missing in the runc
verification, we can release it.
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Hi "bw...@de.ibm.com", could you perform the same tests you did
previously but now using the fence-agents package from focal-proposed
instead of my PPA? You can check the "Test plan" section in the bug
description but it is basically what you already did. This is part of
the SRU process and we
Packages uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921011
Title:
Fix build against new runc version
To manage notifications about this bug go to:
Both packages built fine in this PPA:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/buildah-and-
libpod/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921011
Title:
Fix build
The libpod package FTBFS because of the new version of the docker.io
package in groovy-proposed. The attached debdiff fixes this issue.
** Patch added: "libpod.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/1921011/+attachment/5485291/+files/libpod.debdiff
--
You received
The golang-github-containers-buildah package FTBFS because of the new
version of the docker.io package in groovy-proposed. The attached
debdiff fixes this issue.
** Patch added: "golang-github-containers-buildah.debdiff"
The test plan says the upstream test suite should be executed to catch
any regression. This was done during the package build process and it
succeeded. Therefore, I am considering the validation as done for this
SRU.
** Tags removed: verification-needed verification-needed-bionic
501 - 600 of 1202 matches
Mail list logo
