I'd like to ask for a feature freeze exception for an upload of the new python-foolscap version 0.6.1.
An update of the package is required due to the recent twisted 10.2 upload (https://launchpad.net/ubuntu/+source/twisted/10.1.0-2)
which is not completely compatible with foolscap (details in bug 724837).
The difference between the new version and the packaged version are mainly bugfixes and only few new features (changelog attached).
There was one api change in 0.6.0 but that has begun in 0.5.0, the packaged version is 0.5.1 so dependent packages should have migrated by now.
I checked ipython and it is migrated. But I am still waiting for a reply from tahoe-lafs maintainers.
So I see no real blockers for the new version but alternatively I could
also only backport the fix for twisted 10.2 to the existing version.
Please decide on which route to take at this stage of development.
** Affects: foolscap (Ubuntu)
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/725145
Title:
Feature freeze exception for python-foolscap, new upstream 0.6.1 or
backport fix
--
ubuntu-bugs mailing list
ubunt...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "news.txt"
https://bugs.launchpad.net/ubuntu/+source/foolscap/+bug/725145/+attachment/1871319/+files/news.txt
But as I do not use that package myself I cannot verify this myself and
have wrote to the maintainer to be sure.
I'd like to ask for a feature freeze exception for an upload of the new python-foolscap version 0.6.1.
An update of the package is required due to the recent twisted 10.2 upload (https://launchpad.net/ubuntu/+source/twisted/10.1.0-2)
which is not completely compatible with foolscap (details in bug 724837).
The difference between the new version and the packaged version are mainly bugfixes and only few new features (changelog attached).
- There was one api change in 0.6.0 but that has begun in 0.5.0, the packaged version is 0.5.1 so dependent packages should have migrated by now.
- I checked ipython and it is migrated. But I am still waiting for a reply from tahoe-lafs maintainers.
+ There was one api change in 0.6.0 but that has begun in 0.5.0, the packaged version is 0.5.1 so dependent packages (ipython, tahoe-lafs) should have migrated by now.
+ I checked ipython and it is migrated.
+ the tahoa-lafs is up to date with upstream so also there should be no problems (although I am still waiting for a verification from tahoe-lafs maintainers).
So I see no real blockers for the new version but alternatively I could
also only backport the fix for twisted 10.2 to the existing version.
Please decide on which route to take at this stage of development.
--
I'd like to ask for a feature freeze exception for an upload of the new python-foolscap version 0.6.1.
An update of the package is required due to the recent twisted 10.2 upload (https://launchpad.net/ubuntu/+source/twisted/10.1.0-2)
which is not completely compatible with foolscap (details in bug 724837).
The difference between the new version and the packaged version are mainly bugfixes and only few new features (changelog attached).
There was one api change in 0.6.0 but that has begun in 0.5.0, the packaged version is 0.5.1 so dependent packages (ipython, tahoe-lafs) should have migrated by now.
I checked ipython and it is migrated.
- the tahoa-lafs is up to date with upstream so also there should be no problems (although I am still waiting for a verification from tahoe-lafs maintainers).
+ the tahoa-lafs is up to date with upstream so also there should be no problems.
- So I see no real blockers for the new version but alternatively I could
- also only backport the fix for twisted 10.2 to the existing version.
-
+ I propose three routes which make sense:
+ - sync with a complete repackage of foolscap 0.6.1 done by my using newest debian python policy currently under review. It should get uploaded within this week
+ - minimal repackage of 0.6.1 using existing packaging practice, see branch https://code.launchpad.net/~jtaylor/ubuntu/natty/foolscap/foolscap.0.6.1
+ - backport of the fix and remain with 0.5.1
Please decide on which route to take at this stage of development.
--
** Changed in: foolscap (Ubuntu)
Status: New => Confirmed
when syncing all ubuntu changes can be dropped.
I'd like to ask for a feature freeze exception for an upload of the new python-foolscap version 0.6.1.
An update of the package is required due to the recent twisted 10.2 upload (https://launchpad.net/ubuntu/+source/twisted/10.1.0-2)
which is not completely compatible with foolscap (details in bug 724837).
The difference between the new version and the packaged version are mainly bugfixes and only few new features (changelog attached).
There was one api change in 0.6.0 but that has begun in 0.5.0, the packaged version is 0.5.1 so dependent packages (ipython, tahoe-lafs) should have migrated by now.
I checked ipython and it is migrated.
the tahoa-lafs is up to date with upstream so also there should be no problems.
I propose three routes which make sense:
- sync with a complete repackage of foolscap 0.6.1 done by my using newest debian python policy currently under review. It should get uploaded within this week
- minimal repackage of 0.6.1 using existing packaging practice, see branch https://code.launchpad.net/~jtaylor/ubuntu/natty/foolscap/foolscap.0.6.1
- backport of the fix and remain with 0.5.1
Please decide on which route to take at this stage of development.
** Affects: foolscap (Ubuntu)
Importance: Medium
Status: Confirmed
--
Feature freeze exception for python-foolscap, new upstream 0.6.1 or backport fix
https://bugs.launchpad.net/bugs/725145
You received this bug notification because you are a member of Ubuntu Package Archive Administrators, which is a direct subscriber.
--
ubuntu-archive mailing list
ubuntu-...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-archive
** Changed in: foolscap (Ubuntu)
Importance: Undecided => Medium