** Changed in: trusty-backports
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/b
Packag eapache2_2.4.10-1ubuntu1.1 from Utopic builds & verifies without
modification
** Description changed:
Please backport apache2 2.4.9-1ubuntu2 (main) from utopic to trusty.
Reason for the backport:
I find it simplier and trustfull to use ubuntu backport
** Summary changed:
- Please backport apache2 2.4.9-1ubuntu2 (main) from utopic
+ Please backport apache2 2.4.18-1ubuntu1 (main) from Xenial
** Changed in: trusty-backports
Status: New => Confirmed
** Changed in: trusty-backports
Assignee: (unassigned) => Louis Bouchard
** Description changed:
Please backport makedumpfile 1:1.5.9-5 (main) from xenial to trusty.
Reason for the backport:
The most recent version of makedumpfile source package includes major
additions
to the kdump-tools package, including the functionalities
Public bug reported:
Please backport makedumpfile 1:1.5.9-5 (main) from xenial to trusty.
Reason for the backport:
The most recent version of makedumpfile source package includes major additions
to the kdump-tools package, including the functionalities required to
** Summary changed:
- HAProxy 1.5 init script does not terminate processes
+ Please backport haproxy 1.5.14-1ubuntu0.15.10.1 from wily-updates
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions:
Hello,
Here are the following verifications that were made on trusty :
1) haproxy-1.5.14-1ubuntu0.15.10.1 builds correctly
2) haproxy-1.5.14-1ubuntu0.15.10.1 installs correctly
3) when nbproc > 1 is used, all haproxy processes are stopped correctly
I am now positive that 1.5.14 fixes the
>From what I can gather, the proper version that will fix this issue is
the version which is in wily-updates :
http://archive.ubuntu.com/ubuntu/pool/main/h/haproxy/haproxy_1.5.14-1ubuntu0.15.10.1.dsc
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is
** Changed in: trusty-backports
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/b
** Changed in: precise-backports
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
** Changed in: quantal-backports
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
** Changed in: sosreport (Ubuntu)
Assignee: Louis Bouchard (louis-bouchard) => (u
** Changed in: precise-backports
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
** Changed in: quantal-backports
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
** Changed in: sosreport (Ubuntu Saucy)
Assignee: Louis Bouchard (louis-bouchard) => (u
Vincent Bernat (vbernat) is the Debian maintainer for haproxy. His PPA
assumes a version of dpkg that is newer than 1.17.7. I'll try to open a
Debian bug on that.
The problem lies in the use of start-stop-daemon's new --pid option that
is only available after wily.
If 1.6 is backported to any
Greg, 1.6.2 is not packaged for Trusty. I don't know where it comes
from.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/bugs/1494141
Title:
Claudio, it is only partly fixed by Jorge's patch.
I have proposed the same fix than for this bug in LP: #1481737.
Unfortunately, not being a core dev, it needs to be sponsored to be
accepted. Then I can backport the fix here in 1.5
Sorry for the delay, I'll chase a sponsor.
--
You received
Hello,
Unfortunately Jorge's patch is incomplete. The reason for the looping on
pid is that, if nproc > 1, the pidfile will contain more than one PID
and using --pidfile will only kill the first one.
The proposed patch here will fix both situation, i.e. the fact that
--pid is silently ignored
FYI, I will rebase the debdiff on the new version currently in backport
& repost.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/bugs/1494141
Good catch Claudio. The bug is present in Trusty and Trusty-backports.
Prior to LP: #1477198, the stop script did not stop at all because it
relied on the --pid option that is introduced in dpkg version 1.17.6 as
outlined in the man page of start-stop-daemon :
[--pid] pid
Marking task Trusty as invalid, since haproxy 1.4 uses --pidfile and is
unaffected.
Marking task Wily as fix released as the --pid option is available in
Wily so haproxy 1.5 is unaffected
** Also affects: haproxy (Ubuntu)
Importance: Undecided
Status: New
** Also affects: haproxy
Bonjour Claudio,
No, I have just submitted the fix for inclusion in the backported
package. Once the backport team has taken care of it, it will be
indicated as such in the bug.
Kind regards,
..Louis
--
You received this bug notification because you are a member of Ubuntu
Backporters, which
Patch for the fix to the backport package
** Patch added: "lp1494141_fix_stop_failure.debdiff"
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1494141/+attachment/4466700/+files/lp1494141_fix_stop_failure.debdiff
--
You received this bug notification because you are a member of
** Package changed: haproxy (Ubuntu) => trusty-backports
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to trusty-backports.
Matching subscriptions: ubuntu-backporters
https://bugs.launchpad.net/bugs/1494141
Title:
HAProxy 1.5 init
Public bug reported:
Please backport squid-deb-proxy 0.8.11 (universe) from wily to trusty.
Reason for the backport:
Bring the current backported version in line with Debian upstream
Testing:
Mark off items in the checklist [X] as you test them, but please
This backport request is for a fix to the current backported package.
** No longer affects: sosreport (Ubuntu Trusty)
** Package changed: sosreport (Ubuntu) = trusty-backports
** Changed in: trusty-backports
Assignee: Jorge Niedbalski (niedbalski) = (unassigned)
** Summary changed:
-
Iain,
I just retested it here it does fail again (after removing the
$build_arch_all = 1 from my .sbuildrc) .
** Changed in: precise-backports
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to
Public bug reported:
The most recent HWE kernels (3.13.0.49.43 from linux-image-generic-lts-
trusty) and onward can work again. A kernel modification breaks the
DKMS build of openafs-modules-dkms.
This builds upon the previous backport request that is already in
precise-backports (openafs
No longer a valid request, sosreport 3.2 is now available. Marking it
Invalid.
** Changed in: precise-backports
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
-Suggests)
* bittwist
[ ] precise (Reverse-Recommends)
* python-ns3
[ ] precise (Reverse-Suggests)
** Affects: precise-backports
Importance: Undecided
Assignee: Louis Bouchard (louis-bouchard)
Status: In Progress
--
You received this bug notification because you are a member
** Changed in: precise-backports
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
** Changed in: precise-backports
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https
)
+ [ ] precise (Reverse-Suggests)
** Tags added: cts
** Changed in: precise-backports
Assignee: Louis Bouchard (louis-bouchard) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https
** Changed in: precise-backports
Assignee: Louis Bouchard (louis-bouchard) = (unassigned)
** Changed in: quantal-backports
Assignee: Louis Bouchard (louis-bouchard) = (unassigned)
** Changed in: sosreport (Ubuntu)
Assignee: Louis Bouchard (louis-bouchard) = (unassigned
No need for sponsoring on this one anymore, I just uploaded myself but I
can't seem to be able to remove the 'ubuntu-sponsors' subscription
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
** Description changed:
+ [SRU justification]
+ Squid-deb-proxy information is necessary for diagnostic purposes
+
+ [Impact]
+ Diagnostic of squid-deb-proxy issues are mostly impossible without this fix
+
+ [Fix]
+ Backport squid-deb-proxy plugin from upstream.
+
+ [Test Case]
+ Run as root :
Hi Brian,
I had 3.1.1ubuntu3 at the beginning for Utopic, then version numbered
for the other releases and I switched to all version numbered. But I do
agree that the version in Utopic should be 3.1.1ubuntu3.
Let me upload a new debdiff for you
--
You received this bug notification because you
new debdiff with version number changed
** Patch added: lp1308232_rabbitmq_upstart_squid-deb_ceilometer_v2.debdiff
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1311131/+attachment/4194254/+files/lp1308232_rabbitmq_upstart_squid-deb_ceilometer_v2.debdiff
** Patch removed:
** Patch removed: lp1308232_rabbitmq_upstart_squid-deb.debdiff
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1311131/+attachment/4182632/+files/lp1308232_rabbitmq_upstart_squid-deb.debdiff
--
You received this bug notification because you are a member of Ubuntu
Backporters, which
Added patch for LP: #1355279 as well
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https://bugs.launchpad.net/bugs/1311131
Title:
sosreport needs to collect squid-deb-proxy info
To manage notifications about
Patch for this bug is made available as part of LP: #1311131
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https://bugs.launchpad.net/bugs/1311131
Title:
sosreport needs to collect squid-deb-proxy info
To
Contains fix for this bug LP: #1308232, LP: #1309679 LP: #1355279
** Patch added: lp1308232_rabbitmq_upstart_squid-deb_ceilometer.debdiff
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1311131/+attachment/4189265/+files/lp1308232_rabbitmq_upstart_squid-deb_ceilometer.debdiff
--
** Patch added: lp1308232_rabbitmq_upstart_squid-deb.debdiff
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1311131/+attachment/4182632/+files/lp1308232_rabbitmq_upstart_squid-deb.debdiff
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is
The following debdiff fixes this bug, and the two following bugs :
- Add rabbitmq log collection (LP: #1308232)
- Collect upstart log files (LP: #1309679)
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
** Changed in: sosreport (Ubuntu Saucy)
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https://bugs.launchpad.net/bugs/1296755
Title:
sosreport archive /var/lib/maas by
** Changed in: precise-backports
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https://bugs.launchpad.net/bugs/1296755
Title:
sosreport archive /var/lib/maas by default
To
** Changed in: quantal-backports
Status: Confirmed = Invalid
** Changed in: sosreport (Ubuntu Saucy)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
Indeed this is a follow up from the Saucy's SRU backport request.
Saucy will be EOL in a few days. This request is to take care of the
future so sosreport in Precise does not goes incredibly out of sync
--
You received this bug notification because you are a member of Ubuntu
Backporters, which
Fix for this bug and LP: #1230209, LP: #1301819, LP: #1302837 for
precise-backport. Includes changes following jamespage's suggestion
** Patch added: sosreport_lp1296755_mass_precise-backports_v3.debdiff
Fix for this bug and LP: #1230209, LP: #1301819, LP: #1302837 for saucy.
Includes changes following jamespage's suggestion
** Patch removed: sosreport_lp1296755_mass_precise-backports_v2.debdiff
The previous debdiff above is for Precise
Fix for this bug and LP: #1230209, LP: #1301819, LP: #1302837 for saucy.
** Patch added: sosreport_lp1296755_mass_saucy_v2.debdiff
Fix for this bug and LP: #1230209, LP: 1301819, LP: #1302837
** Patch added: sosreport_lp1296755_mass_precise-backports_v2.debdiff
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1296755/+attachment/4111270/+files/sosreport_lp1296755_mass_precise-backports_v2.debdiff
--
You
** Changed in: precise-backports
Status: New = Confirmed
** Patch removed: sosreport_lp1296755_mass_precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1296755/+attachment/4041004/+files/sosreport_lp1296755_mass_precise.debdiff
** Patch removed:
New version of the debdiff including patches for other bugs
** Changed in: quantal-backports
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https://bugs.launchpad.net/bugs/1296755
)
Assignee: Louis Bouchard (louis-bouchard) = (unassigned)
** Changed in: quantal-backports
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
** Changed in: precise-backports
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
--
You received this bug notification because
** Changed in: sosreport (Ubuntu Precise)
Status: Confirmed = Invalid
** Changed in: sosreport (Ubuntu Precise)
Assignee: Louis Bouchard (louis-bouchard) = (unassigned)
** Changed in: quantal-backports
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
** Changed in: precise
** Changed in: precise-backports
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
** Changed in: quantal-backports
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
** Changed in: sosreport (Ubuntu Precise)
Status: Confirmed = Invalid
** Changed in: sosreport (Ubuntu
Accepted upstream : https://github.com/sosreport/sos/pull/277
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https://bugs.launchpad.net/bugs/1311131
Title:
sosreport needs to collect squid-deb-proxy info
To
I found out this morning that another SRU for sosreport had been started
:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1302808
I must synchonize with Chris on this one before doing anything here
--
You received this bug notification because you are a member of Ubuntu
Backporters,
55 matches
Mail list logo
