zesty_openssl_lp1674399.debdiff
** Patch added: "zesty_openssl_lp1674399.debdiff"
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/+attachment/4868385/+files/zesty_openssl_lp1674399.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch se
xenial_openssl_lp1674399.debdiff
** Patch added: "xenial_openssl_lp1674399.debdiff"
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/+attachment/4868386/+files/xenial_openssl_lp1674399.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
** Patch removed: "zesty_openssl_lp1674399.debdiff"
https://bugs.launchpad.net/ubuntu/zesty/+source/openssl/+bug/1674399/+attachment/4868385/+files/zesty_openssl_lp1674399.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
signee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1674399
Title:
OpenSSL CPU detection for AMD Ryzen CPUs
Status in openssl p
** Description changed:
[Impact]
* Context:
AMD added support in their processors for SHA Extensions[1] (CPU flag:
sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
only (Confirmed with AMD representative). Current OpenSSL version in
Ryzens still calls SHA
yakkety_openssl_lp1674399.debdiff
** Patch added: "yakkety_openssl_lp1674399.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/+attachment/4868959/+files/yakkety_openssl_lp1674399.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch see
zesty_openssl_lp1674399.debdiff
** Description changed:
[Impact]
* Context:
AMD added support in their processors for SHA Extensions[1] (CPU flag:
sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
only (Confirmed with AMD representative). Current OpenSSL ver
Installing isc-dhcp-client-noddns on Trusty and then upgrade to Xenial
with a local archive of a modified Xenial's isc-dhcp-client to replace
isc-dhcp-client-noddns package to isc-dhcp-client during release upgrade
from Trusty to Xenial work as expected with a completed successful
release upgrade.
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1648901
Title:
SPNEGO crash on mechanism failure
Status in krb5 package in Ubuntu:
Fix Released
** Description changed:
== SRU JUSTIFICATION ==
[Impact]
* Chrome (and other things) crash (segfault) when Kerberos fails to
authenticate.
Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdd687700 (LWP 14851)]
spnego_gss_inq
As per a irc conversation with the SRU team (apw),
The existing krb5 (1.13.2+dfsg-5ubuntu1) has a regressing ADT test so it stuck
in -proposed.
Thus, preventing krb5 (1.13.2+dfsg-5ubuntu2) to land in -proposed.
SRU team are looking at this as we speak.
- Eric
--
You received this bug notifica
@dwmw2,
@Andrew Jorgensen,
or anyone else affected by this bug.
As you may have notice, there is currently a call for testing a proposed
version of the source package "krb5".
This is the last step before the package make its way into xenial-
updates (final destination)
Could you please try the p
Great thanks Andrew !
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1648901
Title:
SPNEGO crash on mec
Quick note saying that the work is still in progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
St
Public bug reported:
It has been brought to my attention that :
"CPUID detection in OpenSSL does not properly detect potential optimizations
for AMD processors."
After further verification on my side :
Extended feature flags were not pulled on AMD processors, as result a
number of extensions we
* Repository : https://github.com/openssl/openssl.git
* Commits :
1aed5e1 crypto/x86*cpuid.pl: move extended feature detection.
f8418d8 crypto/x86_64cpuid.pl: move extended feature detection upwards.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Here's some context after a conversation about this bug on channel :
#ubuntu-release
...
[10:01:50] hi SRU, I'm currently working on a case (no LP bug yet)
about an OpenSSL bug on new AMD CPU (Ryzen) released last Feb ... where the SHA
Extension routine is not called on AMD Ryzen cores. My
** Changed in: openssl (Ubuntu)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1674399
Title:
OpenSSL
Hi,
After some discussions with xnox and tkamppeter, here's a summary of the
situations for this particular bug.
The foundation team know how to fix this issue, but so far they do not
have a broken system to test the fixes on, before uploading, thus not
reproducer.
We basically needs someone who
I tried to reproduce on my side using the reproducer explain in comment
#98 and #99, and I couldn't reproduce it.
@xnox
Since foundation know how to fix it, can we try to fixing it blind for
now ? Upload in xenial-proposed, and wait for users feedbacks ?
If something goes wrong, we can still dro
Hi Frode,
Now that cyphermox sponsored it for Artful ... Could you prepare the
debdiff(s) for the affected supported releases ? and I'll sponsored
them.
Regards,
Eric
** Changed in: rsyslog (Ubuntu Artful)
Status: In Progress => Fix Committed
--
You received this bug notification becaus
Hi Dariusz,
Since no upload has been done since last April for this particular bug,
this now need to be in devel release, thus Artful, before proceeding
with affected stable releases (if relevant).
I would suggest you prepare a debdiff for Artful get it sponsored by a
CoreDev, and then I'll be ab
Hi Dariusz,
Accordint to : https://merges.ubuntu.com/main.html
Jeremy Bicha is the one that did the last merge for bluez.
You could also asked him if there is any plan to merge bluez debian
upstream to Artful before the freeze.
bluez | 5.43-0ubuntu1 | zesty | source, amd64, arm64,
** Tags removed: patch
** Changed in: bluez (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: bluez (Ubuntu Artful)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
@iiro, yes I tried your reproducer a couple of time without success.
- Clean Ubuntu install
- Install updates
- Enable -proposed
- Make sure that cupsd is running with stuck job using an invalid printer IP
--
▼ ID ▼ NameUserSizePages State Control
Bug1642966-1Unknown
I tried the same exact reproducer (as described by iiro) using different
scenarios such as :
- Server image inside LXC and KVM guest
- Server image inside KVM guest
- Desktop image inside a KVM guest
and every time it worked well for me without any issue.
- Eric
--
You received this bug notifi
)
Status: New => In Progress
** Changed in: logrotate (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: logrotate (Ubuntu Artful)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Bug watch added: Debian Bug tracker #871592
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592
** Also affects: logrotate (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592
Importance: Unknown
Status: Unknown
** Description changed:
- - Install logrota
Debdiff for devel release Artful.
** Patch added: "lp1709670-logrotate-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+attachment/4929643/+files/lp1709670-logrotate-artful.debdiff
** Tags added: patch
** Changed in: logrotate (Ubuntu Trusty)
Status: N
unassigned) => Eric Desrochers (slashd)
** Changed in: logrotate (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: logrotate (Ubuntu Trusty)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a mem
** Description changed:
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it
or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate"
@iiro,
That is interesting ...
To recap using KVM you can't reproduce the situation (just like me) that
you are experience using virtualbox ... so we are on the same page about
not being able to reproduce using LXC nor KVM, but you can reproduce it
if using virtualbox.
I'll give it a try this we
** Description changed:
[Impact]
logrotate never recovers if the statefile is corrupted unless you remove it
or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
[Test Case]
- Install logrotate
- Run "/etc/cron.daily/logrotate"
** Patch removed: "lp1709670-logrotate-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+attachment/4929665/+files/lp1709670-logrotate-zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
** Changed in: logrotate (Ubuntu Zesty)
Status: Confirmed => In Progress
** Changed in: logrotate (Ubuntu Trusty)
Status: Confirmed => In Progress
** Changed in: logrotate (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are
** Changed in: logrotate (Ubuntu Artful)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1709670
Title:
logrotate never recove
** Description changed:
[Impact]
- logrotate never recovers if the statefile is corrupted unless you remove it
or fix the corruption by hand.
- System will eventually run out of disk space on /var/log for instance.
+ logrotate never recovers if the statefile is corrupted unless you remove
+
Debdiff for stable release : Zesty/17.04
** Patch added: "lp1709670-logrotate-zesty.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/logrotate/+bug/1709670/+attachment/4929988/+files/lp1709670-logrotate-zesty.debdiff
--
You received this bug notification because you are a member of
Trusty, Xenial & Zesty has been sponsored by myself in their respective
upload queues.
Now waiting for the SRU verification team approval for the package to
start building in $RELEASE-proposed for the testing phase.
- Eric
** Tags added: sts-sponsor-done
--
You received this bug notification b
Debdiff for stable release : Xenial/16.04 LTS
** Patch added: "lp1709670-logrotate-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/logrotate/+bug/1709670/+attachment/4929989/+files/lp1709670-logrotate-xenial.debdiff
** Changed in: logrotate (Ubuntu Trusty)
Importance: Unde
Debdiff for stable release : Trusty/14.04 LTS lp1709670-logrotate-
trusty.debdiff
** Patch added: "lp1709670-logrotate-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/logrotate/+bug/1709670/+attachment/4929987/+files/lp1709670-logrotate-trusty.debdiff
--
You received this bu
@iiro,
I was able to reproduce the situation (explained in comment #111) ONLY
using virtualbox.
To recap :
- Desktop image using KVM: Success # Same result for iiro and I
- Xenial image using LXC: Success
- Server image using KVM: Success
- Desktop image using Virtual
Using Desktop image on KVM :
--
Log started: 2017-08-08 14:07:24
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Re
Using Desktop image on VirtualBox :
--
Log started: 2017-08-10 10:07:00
(Reading database ... ^M(Reading database ... 5%^M(Reading database ...
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database
... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading
d
On a broken VirtualBox system, if I perform ;
systemctl stop cups.service
I got the following message : "Job for cups.service canceled."
Obviously, cups remain started with same PID, so no effect on the stop
action requested.
Exactly as during the package upgrade.
On the other side, syslog sho
If I manually stop or stop/start cups.socket & cups.path, then
cups.service is stopping successfully, and I can now proceed with the
cups upgrade on a broken system.
With that being said, this could be a good workaround for Xenial users
blocked by this situation.
systemctl stop cups.socket
system
### VERIFICATION XENIAL ###
* Couldn't reproduce the above situation using the proposed package
version "3.8.7-2ubuntu2.16.04.2" using Xenial/16.04 LTS.
* Ran the testsuite against "3.8.7-2ubuntu2.16.04.2" and no errors were found,
apart from a recurrent one which look to me like it did succeed
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1709670
Title:
logrotate never recover
Hi iiro,
Could you please give it a try with the following test package I have
prepare for you :
sudo add-apt-repository ppa:slashd/cupsupgrade
sudo apt-get update
Use the same exact reproducer but instead of upgrading from xenial-
proposed like you normally do, please upgrade from this PPA.
Le
@iiro,
I just uploaded a new version of the test package a few minutes ago...
Please make sure when you will give the PPA a try that you are upgrading
to "2.1.3-4ubuntu0.3+test1" version.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
lp1642966_xenial.debdiff
** Patch added: "lp1642966_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+attachment/4934838/+files/lp1642966_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
** Patch removed: "lp1642966_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+attachment/4934838/+files/lp1642966_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
h
The patch has been uploaded in the xenial upload queue.
It is now waiting for the SRU verification team approval for the CUPS
derived binary packages to start building in xenial-proposed and re-
enter in the users test phase.
- Eric
--
You received this bug notification because you are a membe
f"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+attachment/4934958/+files/lp1642966_xenial.debdiff
** Changed in: cups (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: cups (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
** T
### VERIFICATION ZESTY ###
* Couldn't reproduce the above situation using the proposed package
version "3.8.7-2ubuntu3.1" using Zesty/17.04.
* Ran the testsuite against "3.8.7-2ubuntu3.1" "/usr/sbin/logrotate" binary and
no errors were found, apart from a recurrent one which look to me like it d
** Description changed:
This is in xenial-proposed, please block release to -updates accordingly
:)
[Impact]
* fail to upgrade
[testcase]
Root cause is believed to be reproducible with:
#!/bin/bash
systemctl stop cups.path cups.service
rm /var/cache/cups/org.cups.cupsd
** Description changed:
This concerns only Xenial (16.04)!
[Impact]
* fail to upgrade
[testcase]
Root cause is believed to be reproducible with:
#!/bin/bash
systemctl stop cups.path cups.service
rm /var/cache/cups/org.cups.cupsd
systemctl start cups.path
touch /var/cac
** Description changed:
This concerns only Xenial (16.04)!
[Impact]
* fail to upgrade
[testcase]
Root cause is believed to be reproducible with:
#!/bin/bash
systemctl stop cups.path cups.service
rm /var/cache/cups/org.cups.cupsd
systemctl start cups.path
touch /var/cac
** Description changed:
This concerns only Xenial (16.04)!
[Impact]
* fail to upgrade
[testcase]
Root cause is believed to be reproducible with:
#!/bin/bash
systemctl stop cups.path cups.service
rm /var/cache/cups/org.cups.cupsd
systemctl start cups.path
touch /var/cac
** Description changed:
after 6 minutes or so, cups is not responding.
it do not produce error on the log, just stop working, worse, it exit with 0
⌌—⌍
|root@cupsmachine :~# systemctl status cups
** Changed in: cups (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: cups (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: cups (Ubuntu Xenial)
Assignee: Eric Desrochers (slashd) => Till Kamppeter (till-kamppeter)
--
You rece
** Tags removed: patch regression-proposed verification-needed
verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.
** Also affects: open-iscsi (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: High
Assignee: Nish Aravamudan (nacc)
Status: Confirmed
*
** Also affects: systemd (Ubuntu Artful)
Importance: Medium
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: N
** Changed in: rsyslog (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: rsyslog (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: rsyslog (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: rsyslog (Ubuntu Zesty)
Status: Confirmed => In Progress
** Ch
Feedback from the field about the test package of "isc-dhcp-client-
noddns" I made for someone interested to give it a try before the SRU:
"... we've tried it out and didn’t notice anything unusual, but I
suspect we would only see problems if there are any if we ran it 1000s
of times in ci.
I als
Feedback from the field about the test package of "isc-dhcp-client-
noddns" I made for someone interested to give it a try before the SRU:
"... we've tried it out and didn’t notice anything unusual, but I
suspect we would only see problems if there are any if we ran it 1000s
of times in ci.
I als
** Changed in: rsyslog (Ubuntu Artful)
Status: New => Confirmed
** Changed in: rsyslog (Ubuntu Artful)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://
4) - Don't forget to file the SRU justification tmpl.
https://wiki.ubuntu.com/StableReleaseUpdates
3.1. SRU Bug Template
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/
# Sponsor review :
Additionally ...
3) A quilt header in DEP3 format is missing in "fix-typo-in-doc-
de.patch"
http://dep.debian.net/deps/dep3/
- Eric
** Changed in: cups (Ubuntu)
Status: New => Confirmed
** Also affects: cups (Ubuntu Xenial)
Importance: Undecided
Status: New
# Sponsor review :
Hi Ivy,
1) The patch doesn't apply cleanly via quilt:
Applying patch fix-typo-in-doc-de.patch
patching file doc/de/index.html.in
Hunk #1 FAILED at 23.
1 out of 1 hunk FAILED -- rejects in file doc/de/index.html.in
Patch fix-typo-in-doc-de.patch does not apply (enforce with -f)
** Also affects: rsyslog (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: rsyslog (Ubuntu Trusty)
Assignee: (unassigned) => Seyeong Kim (xtrusia)
** Changed in: rsyslog (Ubuntu Trusty)
Importance: Undecided => Medium
** Tags added: sts-sru-needed
--
You receiv
[ STS SPONSOR REVIEW ]
@Seyeong,
According to your dediff you are only cherry-picking "7a2e247 bugfix:
plug a memleak in imuxsock".
This commit has been introduced upstream starting with
"v7.6.3-158-g7a2e247", thus it seems like this bug is only affecting
Trusty as you previously mentioned.
Acc
[STS SPONSOR]
Thanks Seyeong for the quick patch rework to include the second upstream
commit.
The trusty debdiff has been uploaded in the Trusty upload queue, now
waiting for SRU verification team approval in order to start building in
trusty-proposed.
https://launchpad.net/ubuntu/trusty/+queue
[Verificaton YAKKETY]
# i386
- Significant performance increase using the yakkety-proposed/i386 package
inside a 32-bit LXD container build using a Ryzen CPU with Intel SHA Extension
capability.
- Same performance (as expected) using the yakkety-proposed/i386 package on a
non SHA Extension Inte
@Norman Henderson (norm-audrey)
I would suggest you to report a separate bug/wishlist for this topic.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
** Also affects: isc-dhcp (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1689854
Title:
Multiple DHCPv6 client
** Changed in: isc-dhcp (Ubuntu Trusty)
Status: New => In Progress
** Changed in: isc-dhcp (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: isc-dhcp (Ubuntu Trusty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you
** Description changed:
[Impact]
When using isc-dhcp-client on a Trusty system, with multiple interfaces
configured to use DHCPv6, not all the DHCPv6 clients will receive the
server responses on some of the interfaces. This results in not all
DHCPv6 interfaces being configured.
** Description changed:
[Impact]
When using isc-dhcp-client on a Trusty system, with multiple interfaces
configured to use DHCPv6, not all the DHCPv6 clients will receive the
server responses on some of the interfaces. This results in not all
DHCPv6 interfaces being configured.
** Description changed:
[Impact]
When using isc-dhcp-client on a Trusty system, with multiple interfaces
configured to use DHCPv6, not all the DHCPv6 clients will receive the
server responses on some of the interfaces. This results in not all
DHCPv6 interfaces being configured.
** Description changed:
[Impact]
When using isc-dhcp-client on a Trusty system, with multiple interfaces
configured to use DHCPv6, not all the DHCPv6 clients will receive the
server responses on some of the interfaces. This results in not all
DHCPv6 interfaces being configured.
[Verificaton XENIAL]
# i386
- Significant performance increase using the xenial-proposed/i386 package
inside a 32-bit LXD container build using a Ryzen CPU with Intel SHA Extension
capability.
- Same performance (as expected) using the xenial-proposed/i386 package on a
non SHA Extension Intel C
The same precision verification testing has been tested for zesty-
proposed with the same result as X and Y :
[Verificaton zesty]
# i386
- Significant performance increase using the zesty-proposed/i386 package inside
a 32-bit LXD container build using a Ryzen CPU with Intel SHA Extension
capabi
Thanks William, I'll set the proposed pkg as verification-failed, and
will work on backporting the patch[1] you are suggesting and that has
been proven to fix the issue.
[1] -
https://github.com/openssl/openssl/commit/08d09628d2c9f3ef599399d8cad021a07ab98347
Eric
** Tags removed: verificatio
William, as per our IRC conversation, we have decided that you will do
the upload for this specific fix for the 4 releases.
Thanks for your collaboration.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubu
[sts-sponsor note]
I am concerned about just adding the service unit, and not making your package
work
with systemd, especially for maintainer scripts (It may possibly break package
upgrade, ..)
IMHO it would be good to test and include an upgrade to the actual [Test Case]
field.
May I sugges
[sts-sponsor note]
I am concerned about just adding the service unit, and not making your package
work
with systemd, especially for maintainer scripts (may break package upgrade...
would be good to test and add this to the [test case].
May I suggest you look at debian/control and debian/rules t
** Description changed:
[Impact]
Systemd service reports slapd as active, even though it may have failed
[Description]
The slapd package for OpenLDAP is shipped with a SysV-style init script
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service
by generating th
Sponsored in disco.
** Changed in: openldap (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1821343
Title:
slapd process
This is affecting radosgw's civetweb (embedded webserver) when SSL is in
used for Bionic which doesn't yet support OpenSSL 1.1 in civetweb v1.8
-> LP: #1822872 .
The support of OpenSSL 1.1 start only with civetweb v1.10 and later.
- Eric
--
You received this bug notification because you are a m
** Changed in: cups (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: cups (Ubuntu Eoan)
Status: New => In Progress
** Changed in: cups (Ubuntu Eoan)
Assignee: (unassigned) => Victor Tapia (vtapia)
--
You received this bug notification because you are a member of Ubunt
There is a debian->ubuntu sync right now in eoan-proposed.
I'll sponsor it once the actual sync is completed and found in eoan-
releases.
Meanwhile, could you please report a bug and forward the patch to debian
to make sure the problem is fix to prevent re-introducing the issue at
next debian->ub
Sponsored for 'Eoan'. Let's start the SRU once cups land in eoan-
releases (Fix Released).
Thanks Victor !
- Eric
** Changed in: cups (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: cups (Ubuntu Disco)
Status: New => In Progress
** Changed in: cups (Ubuntu Cosmi
Sponsored for D/C/B/X.
Thanks Victor !
-Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1822062
Title:
Race condition on boot between cups and sssd
Status in cups pack
[sts-sponsor]
@dgadomski
I don't think you can add a runtime dependency from universe to a
package found in main
apport-gtk | 2.20.11-0ubuntu42 | groovy
konsole | 4:20.04.3-0ubuntu1 | groovy/universe
This would most likely require an MIR for konsole first.
https://wiki
[sts-sponsor]
Sponsored in active development release (groovy)
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchp
** Bug watch added: Debian Bug tracker #966621
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966621
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966621
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to
'syslog' for the user and group, and don't match the
ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 rsyslogd: file '/dev/console': open
error: Permission denied
One easy fix would possibly be the following:
# debian/rsyslog.postinst
case "$1" in
configure)
adduser --system --group --no-create-home --quiet syslog || true
adduser syslog adm || true
+adduser syslog tty || true
I'll give it a try and test.
--
You received this bu
501 - 600 of 770 matches
Mail list logo
