Just wondering what the official position is on the 0.47.x branch. A number of bug reports have been filed recently about build failures with recent versions of Glib, Poppler etc. At the moment, we list 0.47.x as being supported [1], but as far as I know, we have no plans to backport any fixes for the build failures, so it isn't actually usable on current linux distros. As such, would it be appropriate to "retire" the branch and encourage users to upgrade to 0.48.x?
Cheers,
AV
On 06/06/2012 12:39, Alex Valavanis wrote:
Just wondering what the official position is on the 0.47.x branch. A number of bug reports have been filed recently about build failures with recent versions of Glib, Poppler etc. At the moment, we list 0.47.x as being supported [1], but as far as I know, we have no plans to backport any fixes for the build failures, so it isn't actually usable on current linux distros. As such, would it be appropriate to "retire" the branch and encourage users to upgrade to 0.48.x?
<off-topic>
The mentioned reports [2] with patches had been filed without specifying which version/branch they are based on - with comments like "This patch is needed when compiling with GCC 4.5 and newer."
Neither the current release branch 0.48.x nor current trunk need any of these patches [3] - hence my assumption about them being based on Inkscape 0.47, even more so since one of the patches was a 1:1 copy of the diff supplied with the relevant earlier bug report (which had been filed against Inkscape 0.47, and fixed with the release of 0.48).
Maybe I closed the reports prematurely as duplicates of earlier ones, but based on my experience we get such reports about build failures (with poppler, mostly) or patches from users who checked out the old source tree from SVN at sourceforge.net - mistaking it as current trunk.
The links on inkscape.org had been updated quite some time ago to refer to the BZR repository at launchpad.net for the current sources. There might be a few outdated pages in the wiki which still mention SVN at sf.net - those usually get updated whenever noticed or someone reports it on irc or in the bug tracker.
</off-topic>
~suv
[2] for convenience -> direct links to the individual reports: Bug #1008101 "new glib (2.32+) patch" https://bugs.launchpad.net/inkscape/+bug/1008101 Bug #1008103 "new libpng patch" https://bugs.launchpad.net/inkscape/+bug/1008103 Bug #1008104 "new poppler (0.12.2+) patch" https://bugs.launchpad.net/inkscape/+bug/1008104 Bug #1008107 "new poppler (0.15.1+) patch" https://bugs.launchpad.net/inkscape/+bug/1008107 Bug #1008108 "new gcc (4.5+) patch" https://bugs.launchpad.net/inkscape/+bug/1008108
[3] only exception: the fix for building with libpng 1.5+ still needs to be backported to 0.48.x, which is properly tagged in the relevant earlier report
0.47 is no longer supported. I've gone ahead and marked the series as "Obsolete" in Launchpad. Thank you for pointing this out!
Cheers, Josh
On Wed, Jun 6, 2012 at 3:39 AM, Alex Valavanis <valavanisalex@...400...> wrote:
Just wondering what the official position is on the 0.47.x branch. A number of bug reports have been filed recently about build failures with recent versions of Glib, Poppler etc. At the moment, we list 0.47.x as being supported [1], but as far as I know, we have no plans to backport any fixes for the build failures, so it isn't actually usable on current linux distros. As such, would it be appropriate to "retire" the branch and encourage users to upgrade to 0.48.x?
Cheers,
AV
[1] https://launchpad.net/inkscape/0.47.x
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Why not commiting a full delete to the sourceforge svn trunk repository and adding a README that redirects to the launchpad project page ?
On Wed, Jun 20, 2012 at 9:43 AM, Yann Papouin <yann.papouin@...400...> wrote:
Why not commiting a full delete to the sourceforge svn trunk repository and adding a README that redirects to the launchpad project page ?
Integrity of history.
The last revision of trunk in SVN was 22636 The current revision of trunk on BZR is 11509
There have been a few times where revision history has been lost or mangled in some fashion. There's probably something like 15,000 commits worth of non-truncated revision history in SVN which needs to be preserved for history.
Cheers, Josh
2012/6/20 Josh Andler <scislac@...400...>:
On Wed, Jun 20, 2012 at 9:43 AM, Yann Papouin <yann.papouin@...400...> wrote:
Why not commiting a full delete to the sourceforge svn trunk repository and adding a README that redirects to the launchpad project page ?
Integrity of history.
The last revision of trunk in SVN was 22636 The current revision of trunk on BZR is 11509
There have been a few times where revision history has been lost or mangled in some fashion. There's probably something like 15,000 commits worth of non-truncated revision history in SVN which needs to be preserved for history.
If we did a commit that removed all files from the SVN repository, people interested in history could still check out revisions from before that using the -r switch. This could even be specified in the README file.
Regards, Krzysztof
On Thu, Jun 21, 2012 at 12:06 PM, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
If we did a commit that removed all files from the SVN repository, people interested in history could still check out revisions from before that using the -r switch. This could even be specified in the README file.
Fair enough... if you feel like doing it, feel more than free to. It doesn't particularly interest me at this point. :)
Cheers, Josh
2012/6/21 Josh Andler <scislac@...400...>
On Thu, Jun 21, 2012 at 12:06 PM, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
If we did a commit that removed all files from the SVN repository, people interested in history could still check out revisions from before that using the -r switch. This could even be specified in the README file.
Fair enough... if you feel like doing it, feel more than free to. It doesn't particularly interest me at this point. :)
Done. I added a short README that points to Launchpad. Regards, Krzysztof
participants (5)
-
Alex Valavanis -
Josh Andler -
Krzysztof Kosiński -
Yann Papouin -
~suv