** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899611
Title:
Purpose unclear of unknown file /etc/apache2/apache2.conf.in
To manage notifications about this bug go to:
Thank you for taking the time to file a bug report.
From the logs we can see:
mysqld is running as pid 16349
Error: Unable to shut down server with process id 16349
Do you have by any chance another mysqld process running not managed by
the Debian package provided by Ubuntu? I am asking that
Thank you for taking the time to file a bug report.
The mysql-server postinst script is failing because of this:
/var/lib/dpkg/info/mysql-server-8.0.postinst: line 191:
/usr/share/mysql-common/configure-symlinks: No such file or directory
The /usr/share/mysql-common/configure-symlinks file is
Thank you for taking the time to file a bug report.
From the logs we can see:
mysqld is running as pid 12852
Error: Unable to shut down server with process id 12852
Do you have by any chance another mysqld process running not managed by
the Debian package provided by Ubuntu? I am asking that
Thank you for taking the time to file a bug report.
I noticed that your attached logs are missing the mysql error log
(/var/log/mysql/error.log), could you attach the content of this file as
well?
You also mentioned you installed mysql and mariadb (you indeed have
mariadb packages in the
Thank you for taking the time to file a bug report.
The mysql-server postinst script is failing because of this:
/var/lib/dpkg/info/mysql-server-8.0.postinst: line 191:
/usr/share/mysql-common/configure-symlinks: No such file or directory
The /usr/share/mysql-common/configure-symlinks file is
** 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.
https://bugs.launchpad.net/bugs/1938208
Title:
No CI testing for the case that cloud-init is installed but
This issue should be resolved now that package 27.2.2 is out.
Let us know if that issue still persists
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: ubuntu-advantage-tools (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/1938137
Title:
doesnt let me enable esm or any tools of advantage
** 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.
https://bugs.launchpad.net/bugs/1938207
Title:
ubuntu-advantage-tools.postinst and cloud-id are not robust
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-hirsute verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-hirsute verification-done-xenial
--
You received
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-hirsute verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-hirsute verification-done-xenial
--
You received
Hi Mammon, can you post the output of the ua enable command so we can
better understand what is happening.
Also, can you please add the ubuntu-advantage-tools log located in
/var/log/ubuntu-advantage.log. This will also allow us to better
understand what is happening here
--
You received this
Hi Bruna, thanks for reporting this issue.
Just to confirm, are you using a custom python installation in the system ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938074
Title:
package
We have landed #1743 which should fix this issue
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Confirmed => 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/1936833
Title:
I have tested the scenario Rafael described above and it works as
expected in Impish but in Focal, as he described, the configuration is
lost. The workaround presented in comment #5 is needed.
From my understanding, after the upgrade from Bionic to Focal there is
no regression apparently but
So far no news in the PR, it is still waiting for 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
This is still impacting corosync version 2.4.3-0ubuntu1.2 present in
Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677684
Title:
/usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox:
This is still impacting corosync version 2.4.3-0ubuntu1.2 present in
Bionic. As described by Rafael this is affecting only non-systemd users
which seem to be the minority of our users, so I am setting the
importance to Low in Bionic.
** Changed in: corosync (Ubuntu Bionic)
Importance:
I can confirm that this bug is fixed in the proposed 27.2.1 package on
Xenial, Bionic, Focal and Hirsute by using the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-check
lxc delete --force $name
lxc launch ubuntu-daily:$series $name
lxc exec $name -- sudo
Thank you for taking the time to file a bug report.
I was not able to reproduce your issue in a clean LXD container running
Ubuntu 20.04. Checking the logs I noticed the following:
Warning: Fake start-stop-daemon called, doing nothing.
/usr/sbin/policy-rc.d returned 101, not running 'start
** Description changed:
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
* Schema of `ua status --format=json` has been updated to include more
This are the test results for the ubuntu-advantage-tools 27.2.1 package.
** Attachment added: "ua-27.2.1-test-results.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1934902/+attachment/5512237/+files/ua-27.2.1-test-results.tar.xz
** Tags removed:
Hi Brian, thanks for reporting this issue.
We have already released a fix for it on impish (27.2.1~21.10.1)
Let us know if that does not solve the issue here
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are
** Summary changed:
- package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade:
installed mysql-server-8.0 package post-installation script subprocess returned
error exit status 1
+ package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade:
local config
Thank you for taking the time to file a bug report.
In your dmesg output you can see the following:
[5284027.672979] audit: type=1107 audit(1626087263.974:189): pid=748 uid=103
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
Thank you for taking the time to file a bug report.
It seems you already found the root cause of the problem and fixed it.
Since this is not a bug in Ubuntu I am marking this bug as Invalid.
** Changed in: mysql-8.0 (Ubuntu)
Status: New => Invalid
--
You received this bug notification
In your rabbitmq-server error log attached you can see the following:
Error during startup:
{error,{could_not_start_listener,"::",5672,eaddrinuse}}
Which means you already have something using port 5672 and rabbitmq-
server is trying to use that port. You can stop whatever service is
running in
** Also affects: ubuntu-advantage-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ubuntu-advantage-tools (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: ubuntu-advantage-tools (Ubuntu Focal)
Importance: Undecided
Status:
-tests-with-privilege.patch: add a patch to skip tests which
require a certain level of privilege not achievable in the build
environment.
-- Lucas Kanashiro Fri, 21 May 2021 16:48:34
-0300
ubuntu@hirsute:~/containerd/containerd-1.5.2$ sudo autopkgtest . -- null
...
autopkgtest [16:06:54
The reason to set GO111MODULE to off is to build using the GOPATH mode
and ignore the go.mod file. When it checks the go.mod file it tries to
fetch some information from the Internet. Using Go >= 1.14 setting this
variable to auto is enough, but in Focal and Bionic where we are using
Go 1.13 it
Thank you for taking the time to file a bug report.
I tried to install rabbitmq-server in a fresh container running Ubuntu
21.10 (Hirsute) and it worked as expected. Also tried to install the
previous version and upgrade to the latest one (the one you are trying
to install) and everything worked
Thank you for taking the time to file a bug report.
I tried to install and upgrade postfix in a container running Ubuntu
21.04 and I could not reproduce the error you mentioned. Could you
please share the logs containing the error when you upgrade the package?
Also the postfix config file in case
Hi Hafeez, just to confirm, does your system have this path:
/etc/apt/sources.list.d/ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932182
Title:
Error when attaching UA
To manage notifications
Thanks for all the reports and letting us know about this issue.
However, there are some updates on the sssd package in Groovy since the
last comment, I do not know if they could fix this issue for you but
could you please give it a try? Also, since Groovy will become EOL soon,
could you check if
Thanks for the patch Sergio. I tried it locally and it indeed fixes the
build issue.
I see some html code in the attached patch but I think it was just a
small issue when you were creating this file, to do my test I removed
those chunks.
LGTM, +1.
--
You received this bug notification because
Thanks for the patch and for the thought on the next steps, I agree with
you and this package should be removed from the archive at some point.
The changes look good to me, +1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just want to say that after 2 years I remembered I had an SSD with
different brand tham Samsung, a Kingston one. I installed it on my razer
and it worked perfectly for days, I did several SSD stress tests and no
errors.
The error is defintely with Samsung AND linux. And it's not a faulty SSD
** Changed in: ubuntu-advantage-tools (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/1928416
Title:
Error when attaching UA ESM key
To manage notifications
Hi Phoenix, can you provide the error that you faced when enabling livepatch ?
This will probably be found on /var/log/ubuntu-advantage.log
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Every time a log into Ubuntu it sends me this error.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: openmpi-bin 4.0.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114
Uname: Linux 5.4.0-74-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
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
Hi Joseph, looking at the logs it seems that the `cloud-id` command
failed. That command is actually provided by `cloud-init`. What is the
output of running:
$ cloud-init status --long
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This test failure is expected on all releases after Focal, since we dropped
32-bit i386 support on those releases. Therefore, we are not producing the
binary package for i386 on these releases.
Because of that, we believe that we can ignore those tests and treat them not
as a regression.
Hi Chris, the i386 build is expected to fail on focal.
Is there a way for us to officially ignore those tests for i386 on focal ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929597
Title:
[SRU]
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
** Attachment added: "ua-27.1-proposed.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1929597/+attachment/5504896/+files/ua-27.1-proposed.tar.xz
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
We are now adding all of the tests that were performed using the package in
proposed.
There is only one test that is not passing:
Attached FIPS upgrade across LTS releases
On this test we enable FIPS on xenial and then upgrade the machine to bionic.
The reason that it is failing is because we
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
We use the distro information all over the code, for example, to perform
the check if a package is from a security pocket or if it is an ESM
package.
We also use the distro to correctly select the ESM messages we will
deliver to the user
--
You received this bug notification because you are a
Hi Brian, do you have any suggestions about what could be done here ? It
seems that the problem occurred on both the /etc/os-release file and the
lsb_release command.
I don't think there is anything else we can do on that situation right ?
--
You received this bug notification because you are a
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
Hi Lukasz, those instructions were created before the package was
uploaded into ṕroposed. In the script I have used to test this bug, I
have used the proposed package.
But if needed, I can update the instructions to use the proposed
packages instead
--
You received this bug notification because
Hi Lukasz, those instructions were created before the package was
uploaded into ṕroposed. In the script I have used to test this bug, I
have used the proposed package.
But if needed, I can update the instructions to use the proposed
packages instead
--
You received this bug notification because
I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.
To perform the verification I have used the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-dev
function generate_motd_message() {
message=$1
I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.
To perform the verification I have used the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-dev
function generate_motd_message() {
message=$1
I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.
To perform the verification I have used the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-dev
function generate_motd_message() {
message=$1
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
** Description changed:
[Impact]
- This release includes bug-fixes and we would like to
- make sure all of our supported customers have access to these
- improvements. The notable ones are:
+ This release provides fixes to numerous issues encountered and reported by
users against the recent
Also, regarding the autopkgtest failures we are seeing, they seem related to
this update-manager bug:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1929865
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.
To perform the verification I have used the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-dev
function generate_motd_message() {
message=$1
** Changed in: update-notifier (Ubuntu Xenial)
Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)
** Changed in: update-notifier (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)
** Changed in: update-notifier (Ubuntu
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
Hi bigsicret, thanks for reporting that. We will definitely take a look
on it.
However, this bug reporting is leaking your private token.
Please, contact customer services to invalidate that token and get a new one
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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
** Description changed:
update-notifier-common does not depend on lsb-release and both
apt_check.py and apt-cdrom-check both utilize lsb_release.
The Ubuntu Error Tracker has been receiving reports about a problem regarding
update-notifier. This problem was most recently seen with
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
601 - 700 of 3389 matches
Mail list logo
