Your patch looks much better now, thanks Iain! I made some small changes
in your changelog and uploaded it to a PPA [1] for testing purposes:
* Changed the target to bionic instead of UNRELEASED
* Added "~ppa1" to the string version. With that if someone decides to install
the package from the PP
Thanks for the patch and the steps to reproduce the bug Iain! I played
with it and it indeed fixes the package and now I can "require
'ncurses'" in Bionic.
To get it ready for the SRU we need to fix a couple of things in your
patch:
* The version string. You used 1.4.9-1ubuntu1 but this version i
** Changed in: postfix (Ubuntu Eoan)
Status: Triaged => 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/1881196
Title:
[SRU] postfix tls deploy-server-cert fails with "can't shift tha
golang-github-armon-go-metrics got fixed and made its way into the
release pocket, now there is no runtime dep blocking this removal.
$ reverse-depends -r groovy golang-prometheus-client-dev
$ reverse-depends -r groovy -b golang-prometheus-client-dev
Reverse-Build-Depends
* nomad
--
You receive
Thank you for taking the time to file a bug report.
>From your logs I can see these errors:
2020-07-04T12:58:32.542859Z 2 [ERROR] [MY-010767] [Server] Error in fixing SE
data for family_tree.user
2020-07-04T12:58:32.560061Z 2 [ERROR] [MY-012083] [InnoDB] Table
family_tree/family_tree is not fou
Updated list of rdeps:
$ reverse-depends -r groovy golang-prometheus-client-dev
Reverse-Depends
* golang-github-armon-go-metrics-dev
Packages without architectures listed are reverse-dependencies in:
amd64, arm64, armhf, i386, ppc64el, s390x
$ reverse-depends -r groovy -b golang-prometheus-clie
** Summary changed:
- cadvisor/0.35.0+ds1-4 FTBFS in Groovy
+ containerd library package is not working with vendorized deps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884663
Title:
containerd
cadvisor is uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884663
Title:
cadvisor/0.35.0+ds1-4 FTBFS in Groovy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
mwhudson gave a +1 for this cadvisor debdiff as a workaround for now:
" kanashiro: yes, that debdiff is fine for now"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884663
Title:
cadvisor/0.35.0+ds
Public bug reported:
In version 2.20.4, pristine-tar was added to Recommends because it is an
optional dependency of origtargz. Since pristine-tar is not in main it
caused a component-mismatch. Downgrade its dependency relation to
Suggests should fix the issue.
** Affects: devscripts (Ubuntu)
Public bug reported:
ruby-webmock/3.8.3-1 is blocked in groovy-proposed because some tests
rely on http://0.0.0.0 and the proxy used in autopkgtest environment is
not allowing it. The easy way to fix it is adding '0.0.0.0' to the
'no_proxy' environment variable used by autopkgtest.
** Affects: ru
Salsa MR updating the Debian patch:
https://salsa.debian.org/debian/puppet-beaker/-/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885614
Title:
Version 4.21.0-2 is blocking ruby-n
Also submitted a PR:
https://github.com/puppetlabs/beaker/pull/1661
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885614
Title:
Version 4.21.0-2 is blocking ruby-net-scp/3.0.0-1 migration
To mana
Public bug reported:
puppet-beaker/4.21.0-2 is blocking ruby-net-scp/3.0.0-1 migration
because it has a tight version constraints regarding dependency on net-
scp (and also net-ssh 6.x which is already in the Groovy release
pocket).
Upstream already patched its gemspec file to be compatible with
Public bug reported:
puppetdb/6.2.0-4 is stuck in groovy-proposed for 64 days and in Debian
unstable for 347 days. Version 6.2.0-3 was removed from Debian testing
because it did not migrate to testing for too long [1]. After gathering
all these information seems that the Debian maintainer is not h
This issue was fixed in Debian on version
1:0.0~git20200410.79a7a31+ds-2. It was already sync'ed and it migrated
to the release pocket as you can see here:
https://launchpad.net/ubuntu/+source/golang-golang-x-tools
** Changed in: golang-golang-x-tools (Ubuntu)
Status: New => Fix Released
** 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/1820288
Title:
Tomcat Web Application Manager does not copy context configuration
To manage notifications about this bug g
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868955
Title:
[SRU] after upgra
Thanks for all the debugging Christian! Very useful :)
I also did some investigation and this behavior is expected by the
Debian maintainers. According to the maintainers the current
implementation does not support using copyXML=true, because in this case
when the app is deployed the context file
This bug was already fixed in Xenial on version 8.0.32-1ubuntu1.9:
tomcat8 (8.0.32-1ubuntu1.9) xenial; urgency=medium
* d/p/fix-class-resource-name-filtering.patch: Fix class and resource name
filtering in WebappClassLoader (LP: #1606331).
-- Karl Stenerud Mon, 10 Dec 2018
15:08:07 +010
Hi Nick and Jan (and anyone affected by this bug),
Could you please try out version 3.4.13-0ubuntu1 in focal-proposed? And
tell us if it's properly fixed for the sake of the SRU process? If it is
the case please remove verification-needed and verification-needed-focal
tags from this bug and add ve
** 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/1845845
Title:
follow gnome-terminal libexec migration
To manage notifications about this bug go to:
https://bugs.launchp
Thank you Luis! The MP I submitted with those changes was also reviewed
and accepted, I am uploading the package now and let's wait for the SRU
team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18716
Sorry for the delay, and also thanks for the feedback you provided!
I talked to the Debian maintainer and the warnings you mention were
tackled and the upstream PR was updated accordingly:
https://github.com/hashicorp/vagrant/pull/11459
I applied the new changes locally and I was able to run som
Above is attached a cadvisor debdiff, I forgot to mention it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884663
Title:
cadvisor/0.35.0+ds1-4 FTBFS in Groovy
To manage notifications about this b
The attached debdiff contains a workaround for this issue, it disables
the containerd support. With this new version the package builds fine
and autopkgtest passes.
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1884663/+attachment/5386585/+files/debdi
Unfortunately we cannot guide you through a fix nor a workaround because
we are not able to reproduce the bug. If by any mean you provide a core
dump as Sergio mentioned (or better: a step by step on how to reproduce
it) you can come back to this bug and we will be happy to investigate
this crash.
Thank you for taking the time to file a bug report.
Checking the logs I noticed there is a bad configuration option:
/etc/ssh/sshd_config: line 111: Bad configuration option: sudo
Could you please share what you have changed in your sshd_config file? I
set up a brand new Xenial conatainer with o
Public bug reported:
Currently, version 0.35.0+ds1-4 FTBFS in Groovy because of a bug in the
`golang-github-containerd-containerd-dev` package. The containerd
library package provides all the dependencies vendorized and there is a
namespace issue. I started a discussion here to figure out the best
Public bug reported:
Version 0.1.3-2 is blocked in proposed because of a test failure on
armhf:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/armhf/g/golang-
procfs/20200622_123558_68ee3@/log.gz
A patch was submitted upstream
** Summary changed:
- postfix tls deploy-server-cert fails with "can't shift that many"
+ [SRU] postfix tls deploy-server-cert fails with "can't shift that many"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Description changed:
+ [Impact]
+
+ "postfix tls deploy-server-cert" did not handle a missing optional
+ argument which makes users get a "can't shift that many..." error.
+
+ In this SRU we are proposing a microrelease update in Focal from version
+ 3.4.10 to 3.4.13 since the changes are sel
** Description changed:
[Impact]
Users cannot send emails using dane-only policy in Focal.
In this SRU we are proposing a microrelease update from version 3.4.10
- to 3.4.11 since the changes are minimal (and also seems there is an
- authorization from the Tech Board to do that). Here
Updated list of rdeps at the moment:
$ reverse-depends -r groovy golang-prometheus-client-dev
Reverse-Depends
* golang-github-armon-go-metrics-dev
* golang-github-google-cadvisor-dev
* golang-github-influxdb-influxdb-dev
Packages without architectures listed are reverse-dependencies in: amd64,
a
** Changed in: postfix (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: postfix (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please do not consider version 3.4.11-0ubuntu1. I am preparing a SRU to
include version 3.4.13 which also fixes LP #1881196.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868955
Title:
[SRU] after
FYI the SRU exception for Postfix is documented here:
https://wiki.ubuntu.com/StableReleaseUpdates#Postfix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881196
Title:
postfix tls deploy-server-cer
Awesome, thank you for that. Since it was already approved there is no
reason to go through the whole process again, but to keep it documented
I'll create a wiki page for this Postfix exception and link it here:
https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases
After th
Scott, I asked around about this subject and those past SRUs with micro-
release updates were accepted probably based on this:
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
And since Debian is also including those micro-releases in stable point
releases I also think we s
Thanks for the pointer Scott, appreciated. And also for fixing it in
Debian and consequently in Groovy which is a sync.
I see this fix in version 3.4.13. Hopefully this postfix SRU [1] will be
accepted and we will have version 3.4.11 in Focal, so we have two patch
level releases to consider if we
Public bug reported:
Hi,
the socat version in Focal (1.7.3.3) breaks certain applications (i.e.
qemu serial console), when using raw mode or disabling echo (required
for serial consoles). Example: start socket in listening mode: "qemu-
system-x86_64 -serial unix:/tmp/socket,server", connect with
** Also affects: containerd (Ubuntu Bionic)
Importance: Undecided
Status: New
** No longer affects: containerd (Ubuntu Focal)
** Also affects: containerd (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: containerd (Ubuntu Focal)
--
You received this bu
** Also affects: containerd (Ubuntu Focal)
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/1870514
Title:
update containerd:amd64 1.3.3-0 stops docker daemo
** Description changed:
[Impact]
Users cannot send emails using dane-only policy in Focal.
In this SRU we are proposing a microrelease update from version 3.4.10
to 3.4.11 since the changes are minimal (and also seems there is an
authorization from the Tech Board to do that). Here
** Summary changed:
- [SRU] after upgrade to 20.04: posttls cannot connect to private/tlsmgr
+ [SRU] after upgrade to 20.04: dane support is not working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Attach file ec2-sru-20.2.45.txt.
** Attachment added: "ec2-sru-20.2.45.txt"
https://bugs.launchpad.net/bugs/1881018/+attachment/5383085/+files/ec2-sru-20.2.45.txt
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would
** Changed in: postfix (Ubuntu Focal)
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/bugs/1868955
Title:
[SRU] after upgrade to 20.04: posttls cannot connect to priva
I'm also experiencing this problem.
Linux nblucas 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
[44262.937772] GpuWatchdog[1602155]: segfault at 0 ip 5616ee370587 sp
7f75ed8b64d0 error 6 in mqtt-explorer.bin[5616eb195000+53d8000]
[44262.93777
Hi Robie,
With the proposed change users will not get the error mentioned in the
description while trying to reload the service and get a better error
(reload not supported). The current status is:
1 - User tries to reload the service
2 - Reload fails
3 - User gets an error
The problem here is t
** Changed in: postfix (Ubuntu Focal)
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/1868955
Title:
[SRU] after upgrade to 20
** Description changed:
+ [Impact]
+
+ Users cannot send emails using dane-only policy in Focal.
+
+ In this SRU we are proposing a microrelease update from version 3.4.10
+ to 3.4.11 since the changes are minimal (and also seems there is an
+ authorization from the Tech Board to do that). Here
Good to hear that Jan. I might have messed up my local setup. I'll
proceed with the SRU process to make this fix land in Focal.
** Changed in: postfix (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
@seb128, yes. It is still in issue on 20.04 (focal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766230
Title:
Strange window matching behaviour between Slack and Chrome
To manage notifications
probably just an packaging issue? pyvenv is officially removed in
python-3.8[1], so the symlink pyvenv should no longer be created?
[1] https://docs.python.org/dev/whatsnew/3.8.html#api-and-feature-
removals
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Nick and @Jan: could you please try postfix 3.4.11 available in the PPA
I mentioned above and give us some feedback? I'd like to confirm that
before asking for help on postfix-users mailing list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Changed in: postfix (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868955
Title:
after upgrade to 20.04: posttls cannot connect to private/tlsmgr
Thank you for taking the time to file a bug report.
I tried to reproduce the error you mentioned in a brand new Focal
container and I failed. It works as expected. My attempt was installing
the freeradius package and run the commands you described (check the
config and restart the service).
Are y
As you mentioned it is not fixed yet, so I am changing the status to
Triaged. I tried to find a way to link the Github issue to this bug
report but I failed.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you ar
That was my initial thought. So I am not sure if just a postfix update
to version 3.4.11 (or 3.5.2 in Groovy) fixes the mentioned issue.
FWIW, I have a PPA here with the version 3.4.11 built in Focal and the
behavior is the same as version 3.5.2 in Groovy:
https://launchpad.net/~lucaskanashiro/+a
After Scott's comment about updating postfix to 3.4.11 I checked the
changelog of this version and I noticed the only change from 3.4.10 is:
20200416
Workaround for broken builds after an incompatible change
in GCC 10. Files: makedefs, Makefile.in.
Workaround for broken D
/7
** Changed in: postfix (Ubuntu)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
** Changed in: postfix (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ntu Focal)
Status: New => Triaged
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: postfix (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Also affects: postfix (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: postfix (Ubuntu Focal)
Status: New => Triaged
** Changed in: postfix (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: postfix (Ubuntu)
Status: Triaged => Fix Released
** Changed in: neutron
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881771
Title:
neutron-ipset-cleanup fails with Traceback: Unhandled error:
oslo_config.cfg.No
As Bryce mentioned the bug was fixed in version 5.7.29. The security
team already made available version 5.7.30 in Xenial (and also Bionic).
So the fix is already available if you have the security pocket enabled
in your system.
** Changed in: mysql-5.7 (Ubuntu)
Status: Triaged => Fix Relea
Thank you for taking the time to file a bug report.
Unfortunately, I am not able to reproduce the bug, and I also did not
find any insightful information from your log files. Are you trying to
upgrade from Ubuntu 17.10 "Artful Aardvark" to 20.04 "Focal Fossa"?
Could you please provide some detail
Thank you for taking the time to file a bug report.
The mysql-server-8.0 package Pre-Depends on mysql-common package which
contains the missing script:
/var/lib/dpkg/info/mysql-server-8.0.postinst: line 191: /usr/share
/mysql-common/configure-symlinks: No such file or directory
Checking the dpk
The piuparts test failures is fixed now. Up to the SRU team to review
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875231
Title:
[SRU] [20.04] Update NGINX version string to 1.18.0
To manage
** Changed in: monitoring-plugins (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881208
Title:
check_disk should look at /proc/mounts, not mtab
To mana
Thanks for taking the time to report this bug and try to make Ubuntu
better.
Checking the logs I noticed those errors:
2020-05-29T16:59:19.347285Z 1 [ERROR] [MY-012209] [InnoDB] Multiple files found
for the same tablespace ID:
2020-05-29T16:59:19.347488Z 1 [ERROR] [MY-012202] [InnoDB] Tablespace
Thank you for taking the time to file a bug report.
Even with the information you provided I cannot reproduce the bug you
mentioned. It'd be great to have detailed steps on how to reproduce it.
Moreover, if you believe this bug is related to kernel you also need to
attach some kernel logs.
Since
Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.
As you mentioned in Trusty /etc/mtab is not a
** Also affects: monitoring-plugins (Ubuntu Trusty)
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/1881208
Title:
check_disk should look at /proc/mounts, n
** Tags added: 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/1881196
Title:
postfix tls deploy-server-cert fails with "can't shift that many"
To manage notifications about this bug go t
** Changed in: openssh (Ubuntu)
Status: Triaged => In Progress
** Changed in: openssh (Ubuntu Focal)
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/bugs/1876320
The Debian maintainer suggested to also add a WantedBy= entry in the
Install section:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774970#32
** Also affects: dnsmasq (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: dnsmasq (Ubuntu Xenial)
Importance: Undecided
** Changed in: mysql-5.7 (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/1881053
Title:
package mysql-server-5.7 5.7.30-0ubuntu0.16.04.1 failed to
install/u
Public bug reported:
In version 1.3.4-0ubuntu4 we changed the name of the binary package
containing the dev files to actually match what we have upstream. Some
other packages are currently blocked in proposed because they expect
golang-github-containerd-containerd-dev and the binary does not exist
I got patches accepted in all the mentioned projects (some of them were
already fixed when I checked). Now we need to wait for a release of
those packages in Debian to sync them.
https://salsa.debian.org/go-team/packages/prometheus-haproxy-exporter/-/merge_requests/1
https://salsa.debian.org/go-te
Actually the new binary package provides the old transitional package:
https://sources.debian.org/src/golang-github-prometheus-client-
golang/1.2.1-3/debian/control/#L36
Yet, I submitted merge requests on salsa for all the mentioned packages
which still build/runtime depend on the old transitiona
** Description changed:
[Impact]
The command 'systemctl reload openvpn @ $ foo' is broken for a while and
no one have reported that. Users should not be using it a lot. After
some investigation we notice the restart command does basically the same
thing, and users should be using rest
** Description changed:
+ [Impact]
+
+ The command 'systemctl reload openvpn @ $ foo' is broken for a while and
+ no one have reported that. Users should not be using it a lot. After
+ some investigation we notice the restart command does basically the same
+ thing, and users should be using rest
** Changed in: openvpn (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: openvpn (Ubuntu Eoan)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: openvpn (Ubuntu Focal)
Assignee: (unassigned) => Lucas
I brought more people into this discussion and we decided to drop the
reload support from the stable/supported releases since it is already
broken and the restart does basically the same thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Also affects: docker.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: docker.io (Ubuntu Disco)
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/18
Thank you for taking the time to file a bug report.
Could you please provide some information on how to reproduce this bug?
Which packages you have installed on your system (like mariadb-server)?
Since there is not enough information in your report to begin triage or to
differentiate between a lo
** Changed in: libseccomp (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: libseccomp (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: libseccomp (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: libseccomp (Ubuntu Xenial)
Importance: Undecided =
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Also affects: openssh (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Focal)
Status: New => Triaged
** Changed in: openssh (Ubuntu Focal)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Thanks for taking the time to file this bug and try to make Ubuntu
better.
The ruby2.7-dev and libruby2.7 need to be at the same version to work as
expected. So you need to update your libruby2.7 to version
2.7.0-5ubuntu1.1 to make it work with ruby2.7-dev 2.7.0-5ubuntu1.1.
Notice that both packag
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878887
Title:
[SRU] No EAP-PEAP
After a discussion with a colleague I think we should leave it as is in
the supported/stable releases (I already fixed it in Groovy, it should
land in the archive soon). The rationale is: even if the reload command
fails the service keeps active and running, the proposed solutions would
not fix the
worth to SRU a "fix" for this to the supported releases.
** Changed in: openvpn (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: openvpn (Ubuntu)
Status: Triaged => In Progress
** Changed in: openvpn (Ubuntu)
Importance: Undecided =&g
Executing the ExecReload= command with full privileges (adding '+')
indeed fixes the reload failure (I ran my tests in a Bionic and Focal
VMs but it should apply to the other releases):
May 26 10:01:41 openvpn-reload kill[1764]: kill: (1738): Operation not
permitted
I mean the command 'systemctl
** Also affects: openvpn (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: openvpn (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: openvpn (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: openvpn (Ubuntu Bionic)
Thanks for taking the time to file this bug!
This bug was reported against openvpn in Ubuntu 17.10 which is not
supported anymore. I was not able to reproduce this issue in 18.04 (LTS
version after 17.10), so I am marking it as Invalid.
** Changed in: openvpn (Ubuntu)
Status: Confirmed =>
Thanks for filing this bug and try to make Ubuntu better!
Since there is no response from the reporter for a while and this bug is
reported against Disco (not supported anymore), I am marking it as
Incomplete.
If you still face this issue please reopen (change the Status to New
again) the bug and
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878887
Title:
[SRU] No EAP-PEAP support anymore
To manage notifications about this bug go to:
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879692
Title:
[SRU] Strongswan pki creates CA certificates with invalid Key Usage
flags
To
The proposed package is available here:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/focal-strongswan-
bug-fixes
I performed the test above to check if the CA certificate is generated
correctly:
[in the same container I was using to describe the Test Case section in the
description]
$
1201 - 1300 of 3481 matches
Mail list logo
