Trac 0.10.3-1 needed in edgy-backports
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Edgy Backports |
Undecided
|
Unassigned | ||
| | trac (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: trac
Trac 0.10.2-1, which is the latest version in edgy-backports, still has the "NoSuchChangeset" bug. This was fixed in 0.10.3~rc1-1. Feisty currently has 0.10.3-1, which is the latest stable version.
This bug prevents having a working Trac environment on a system that is using apache2-
| Changed in trac: | |
| status: | Unconfirmed → Rejected |
| Justin R. Cutler (justin-r-cutler) wrote : | #2 |
0.10.3-1 builds, installs, and works perfectly well under prevu.
+1 edgy
(This is not a particularly common package, so it may be a while before three more people test this, but this is a rather major bugfix. Is there any chance of putting this into backports earlier?)
| Peter Magnusson (kmpm) wrote : | #3 |
0.10.3-1 builds, installs and works so far.
+1 edgy
| Matti Lindell (mlind) wrote : | #4 |
Yep, builds on Edgy chroot without problems and seems to work okay.
| Mark Lynch (mark-lynchconsulting) wrote : | #5 |
I'd like to vote for this bug - I was recently very happy to see the 10.x series of trac in edgy backports.
I have upgraded my trac on my development servers only to run into this bug after they have all been upgraded.
I understand that backports is use at your own risk etc, so what is the risk reward for putting in version 0.10.3? Risk is potential new bugs introduced to a "unsupported" package. Reward is a major bug is closed.
Is there significant effort in porting the feisty 0.10.3 package back?
Cheers,
Mark
| Mark Lynch (mark-lynchconsulting) wrote : | #6 |
For further information, here is the bug report for this problem on trac: http://
| John Dong (jdong) wrote : | #7 |
Thanks for your backports bug report. This backports request is primarily motivated by bugfixes. The Ubuntu Technical Board has stated that Backports is primarily for introducing new features, and that bugfixes should be handled using the StableReleaseUp
As a result, I will turn this bug report over to the main Ubuntu bug tracker. If SRU cannot resolve this situation, feel free to re-open the backports request.
For more information on the Stable Release Updates process, please read: https:/
| Changed in trac: | |
| status: | Rejected → Unconfirmed |
| Changed in edgy-backports: | |
| status: | Confirmed → Rejected |
| Changed in trac: | |
| status: | Unconfirmed → Fix Released |
| Justin R. Cutler (justin-r-cutler) wrote : | #8 |
This bug is only in the version of Trac in edgy-backports (0.10.2-1~edgy1). All other versions of Trac in Ubuntu do not have this bug.
The 0.10 series of Trac does introduce many new features over the version in edgy (0.9.6-2), and likely does not belong in edgy.
Multiple people (4 at last count, including myself) have verified that the version in feisty (0.10.3-1) works. Indeed, I am using this version on multiple live systems and have not encountered any problems.
| Changed in edgy-backports: | |
| status: | Rejected → Confirmed |
| John Dong (jdong) wrote : | #9 |
I'm sorry, I misunderstood. This backport is now approved.
| Changed in edgy-backports: | |
| status: | Confirmed → In Progress |
| Martin Pitt (pitti) wrote : | #10 |
* Trying to backport trac...
- <trac_0.
- <trac_0.
- <trac_0.10.3-1.dsc: downloading from librarian>
I: Extracting trac_0.10.3-1.dsc ... done.
I: Building backport of trac-0.10.3 as 0.10.3-1~edgy1 ... done.
| Changed in edgy-backports: | |
| status: | In Progress → Fix Released |
| Rouben (rouben) wrote : | #11 |
Since this backport got approved for Edgy, would it be possible to do the same for Dapper?
0.10.3-1 in feisty b/i/(dont know how to test but assumes it will work) under prevu
+1 edgy