This bug was fixed in the package resiprocate - 1:1.9.7-4~ubuntu14.10.1
---
resiprocate (1:1.9.7-4~ubuntu14.10.1) utopic; urgency=medium
* Rebuild for Ubuntu 14.10. (LP: #1420956)
-- Marc Deslauriers marc.deslauri...@ubuntu.com Tue, 31 Mar 2015 09:18:52
-0400
** Changed in:
This bug was fixed in the package resiprocate - 1:1.9.7-4~ubuntu14.04.1
---
resiprocate (1:1.9.7-4~ubuntu14.04.1) trusty; urgency=medium
* Rebuild for Ubuntu 14.04 LTS. (LP: #1420956)
-- Marc Deslauriers marc.deslauri...@ubuntu.com Tue, 31 Mar 2015 09:21:16
-0400
** Changed
Tested on trusty and utopic
** Tags removed: removal-candidate verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420956
Title:
hard-coded to use
Tested for both utopic and trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420956
Title:
hard-coded to use OpenSSL TLSv1_method
To manage notifications about this bug go to:
Hello Daniel, or anyone else affected,
Accepted resiprocate into utopic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/resiprocate/1:1.9.7-4~ubuntu14.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Daniel, or anyone else affected,
Accepted resiprocate into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/resiprocate/1:1.9.7-4~ubuntu14.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Branch linked: lp:ubuntu/trusty-proposed/resiprocate
** Branch linked: lp:ubuntu/utopic-proposed/resiprocate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420956
Title:
hard-coded to use
The resiprocate MRE has been approved by the tech board.
I assume the intention behind the debdiffs in comments #3 and #4 is to
push the vivid package into trusty and utopic.
I have uploaded packages for trusty and utopic based on the vivid
package, but with appropriate versioning for processing
** Tags added: trusty utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420956
Title:
hard-coded to use OpenSSL TLSv1_method
To manage notifications about this bug go to:
I've opened another bug report for the issue that exists in 1.9.6 (trusty) and
is fixed in upstream 1.9.7:
https://bugs.launchpad.net/ubuntu/+source/resiprocate/+bug/1422786
All the changes in the debdiff are bug fixes. If you really want me to
I can open an Ubuntu bug report for each of them
The problem with these debdiffs is that we don't ship new versions of
packages as stable updates, they would have to land as backports. Stable
updates would require just applying
https://github.com/resiprocate/resiprocate/commit/645c9f461ca6e2d9d5167cc9c0ca4781c3e7c19b.
Is there any way to apply
Daniel,
Your email to the Technical Board appears to have been received:
https://lists.ubuntu.com/archives/technical-
board/2015-February/002080.html
I'm just following the guidelines for SRU here, which make me think this
isn't exactly suitable for SRU without a proper exception from the TB.
I agree with your comments about the logger config parsing (rutil:
accept case insensitive log level strings), it is not a bug fix and
therefore it is clearly not in the scope of the SRU policy.
On the other hand, everything on that branch has been carefully cherry-
picked with a view to
You can't just sync a new pkg revision to released ubuntu versions.
Provide a debdiff to current trusty/utopic pkgs instead and they get
sponsored.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the debdiff that was approved for jessie, it will be the same for
Ubuntu as there are no patches to the Ubuntu package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772634
Notice the version number was changed again because of a rejected
upload, I eventually had to upload it to NEW
** Patch added: debdiff from version of reSIProcate in utopic to 1:1.9.7-4
https://bugs.launchpad.net/ubuntu/+source/resiprocate/+bug/1420956/+attachment/4318731/+files/resiprocate-utopic-1.9.7-4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For trusty, the debdiff is a bit bigger because it includes all upstream
fixes between 1.9.6 and 1.9.7.
They are itemized one by one in the upstream Git branch for 1.9.x:
https://github.com/resiprocate/resiprocate/commits/resiprocate-1.9
The most critical of these fixes is:
** Patch added: debdiff from version of reSIProcate in trusty to 1:1.9.7-4
https://bugs.launchpad.net/ubuntu/+source/resiprocate/+bug/1420956/+attachment/4318730/+files/resiprocate-trusty-1.9.7-4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch removed: Debian Bug tracker #772634
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772634
** Bug watch added: Debian Bug tracker #772632
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772632
** Also affects: resiprocate (Debian) via
** Changed in: resiprocate (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420956
Title:
hard-coded to use OpenSSL TLSv1_method
To manage
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420956
Title:
hard-coded to use OpenSSL TLSv1_method
To manage notifications about this bug go to:
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420956
Title:
hard-coded to use OpenSSL TLSv1_method
To manage notifications about this bug go to:
22 matches
Mail list logo
