The wily update was not verified in half a year, and wily is almost EOL.
So I removed the -proposed package.
** Changed in: corosync (Ubuntu Wily)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
This bug was fixed in the package corosync - 2.3.3-1ubuntu3
---
corosync (2.3.3-1ubuntu3) trusty; urgency=medium
* debian/patches/Totempg-Fix-memory-leak.patch: Fixes memory leak on
Totempg. (LP: #1563089).
-- Jorge Niedbalski Tue, 05 Apr 2016
10:01:37 +0200
** Changed in:
Based on my latest comment, I am marking the Trusty version as
verification-done-trusty
** Tags removed: verification-needed
** Tags added: verification-done-trusty verification-needed-wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hello,
I ran the verification for the Trusty version.
root@juju-niedbalski-sec-machine-15:/home/ubuntu# dpkg -l|grep corosync
ii corosync 2.3.3-1ubuntu3
amd64Standards-based cluster framework (daemon and modules)
ii libcorosync-common4
Hello Jorge, or anyone else affected,
Accepted corosync into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/corosync/2.3.3-1ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Fix accepted to the development release.
Fix sponsored for Trusty and wily; unsubscribing the Ubuntu-sponsor team
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563089
Title:
Memory Leak when new c
This bug was fixed in the package corosync - 2.3.5-3ubuntu1
---
corosync (2.3.5-3ubuntu1) xenial; urgency=high
* debian/patches/Totempg-Fix-memory-leak.patch: Fixes memory leak on
Totempg. (LP: #1563089).
-- Jorge Niedbalski Fri, 01 Apr 2016
15:52:13 +0200
** Changed in: co
** Patch added: "Trusty Patch"
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+attachment/4619423/+files/fix-lp-1563089-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Patch added: "Wily Pathc"
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+attachment/4619421/+files/fix-lp-1563089-wily.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/156
** Patch removed: "Xenial Patch"
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+attachment/4617458/+files/fix-lp-1563089-xenial.debdiff
** Patch added: "Xenial Patch"
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+attachment/4618461/+files/fix-lp-1563089
The attachment "Xenial Patch" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you a
** Patch added: "Xenial Patch"
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+attachment/4617458/+files/fix-lp-1563089-xenial.debdiff
** Changed in: corosync (Ubuntu Wily)
Status: New => In Progress
** Changed in: corosync (Ubuntu Wily)
Importance: Undecided => Hig
** Also affects: corosync (Ubuntu Wily)
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/1563089
Title:
Memory Leak when new cluster configuration is formed.
** Changed in: corosync (Ubuntu)
Status: New => In Progress
** Changed in: corosync (Ubuntu Trusty)
Status: New => In Progress
** Changed in: corosync (Ubuntu)
Importance: Undecided => High
** Changed in: corosync (Ubuntu Trusty)
Importance: Undecided => High
** Changed in:
** Description changed:
[Environment]
Trusty 14.04.3
Packages:
ii corosync 2.3.3-1ubuntu1
amd64Standards-based cluster framework (daemon and modules)
ii libcorosync-common4 2.3.3-1ubuntu1
** Summary changed:
- Memory Leak when new configuration is formed.
+ Memory Leak when new cluster configuration is formed.
** Tags added: sts-needs-review
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Also affects: corosync (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/1563089
Title:
Memory Leak when new cluster configuration is forme
17 matches
Mail list logo