Woohoo! Thank you very much for doing this Ted! And like Ted, I say thank you to everyone who contributed (whether by dealing with bug reports, testing, coding, or however else they have) Packagers, if you would be so kind as to do your fun tasks, that would be great! And yes, there will very likely be a 0.48.3 down the line as 0.49 will undoubtedly have issues that we did not catch and that may make things difficult for users and we don't want them too frustrated. :) Note: A must for 0.48.3 will be functioning tablet support on Windows (which if someone finds a magic version of GTK that works in the near future, we can just repackage 0.48.2 for windows). Cheers, Josh On Fri, Jul 8, 2011 at 1:42 PM, Ted Gould <ted@...11...> wrote: > > Hello, > > I've made tarballs of the 0.48.2 release of Inkscape.  Please, as per > usual don't announce these generally until packages have a chance to > make binary packages for users. > > I'd really like to thank those that worked on backporting all of the > patches, it's tireless and unforgiving work.  But I'm sure this will > delight a bunch of people. > >  https://sourceforge.net/projects/inkscape/files/inkscape/0.48.2/ > > == MD5 Sums == > > f60b98013bd1121b2cc301f3485076ba  inkscape-0.48.2.tar.bz2 > 889dcffb2fc72ea8522ca4bed95427e1  inkscape-0.48.2.tar.gz > 7cbac56025f9cbabc3b765b2ce4f1610  inkscape-0.48.2.zip > > == SHA1 Sums == > > be30ab2d2714d04ddd69b400bd6ad30b09e83067  inkscape-0.48.2.tar.bz2 > 422a4bacd4dc42adafa203244bc9816783cba4d3  inkscape-0.48.2.tar.gz > 356d770d853bd96299d2c8d5f3f3d4949fac2a58  inkscape-0.48.2.zip > >        --Ted > > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

>> On Fri, Jul 8, 2011 at 1:42 PM, Ted Gould <ted@...11...> wrote: >>> I've made tarballs of the 0.48.2 release of Inkscape. Please, as per >>> usual don't announce these generally until packages have a chance to >>> make binary packages for users. This release seemed to go quickly and painless, am I right? This is good news, and makes it more fun to work on bug fixes for 'point-releases'. We should mark 0.48.2 as released on Launchpad,

and create a 0.48.3 milestone.

Woohoo! Thank you very much for doing this Ted! And like Ted, I say thank you to everyone who contributed (whether by dealing with bug reports, testing, coding, or however else they have) Packagers, if you would be so kind as to do your fun tasks, that would be great! And yes, there will very likely be a 0.48.3 down the line as 0.49 will undoubtedly have issues that we did not catch and that may make things difficult for users and we don't want them too frustrated. :)

BTW [1] - any news on which devlibs version to use for the stable releases (0.48.x)? What about possibly branching the devlibs for stable releases of the Inkscape 0.48.x branch? [2]

I've some problems creating 0.48.2 for windows. I get a couple of error messages during building.

2011/8/14 Uwe Schöler <mail@...2227...>: > I've some problems creating 0.48.2 for windows. I get a couple of error > messages during building. I just checked out 0.48.2 from Bazaar in my Windows XP VM, and I encounter no problems when building from a source checkout with TDM-GCC 4.4.1. It looks like the warning emitted when compiling btool is irrelevant (and I don't even get the warning). I'm 90% sure the first error is caused by building from a tarball (you just need to create the required inkscape-version.cpp file manually), the second looks like a problem with permissions (maybe UAC is getting in the way?) Regards, Krzysztof ------------------------------------------------------------------------------ FREE DOWNLOAD - uberSVN with Social Coding for Subversion. Subversion made easy with a complete admin console. Easy to use, easy to manage, easy to install, easy to extend. Get a Free download of the new open ALM Subversion platform now. http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

recently, I noticed some problems with the JessyInk-extension causing errors in Firefox. The problem seems to be the hashbang line (#!/usr/bin/env js) that is present in the js files distributed in the debian package (used for example with Linux Mint Debian Edition). These lines are neither present in the repository nor in the tar-ball. Therefore, my guess is that they are added at the packaging stage. Since the presence of a hashbang line breaks JessyInk, I wanted to ask whether it is possible to modify the packaging script in such a way that the lines are not added any more to the js files belonging to the JessyInk-extension (jessyInk.js, jessyInk_core_mouseHandler_noclick.js, jessyInk_core_mouseHandler_zoomControl.js). If packaging is not the problem please let me know, so that I can keep digging for the real cause.

On 10/07/11 09:10, ~suv wrote: > On 10/7/11 08:44, Hannes Hochreiner wrote: > >> recently, I noticed some problems with the JessyInk-extension causing >> errors in Firefox. The problem seems to be the hashbang line >> (#!/usr/bin/env js) that is present in the js files distributed in the >> debian package (used for example with Linux Mint Debian Edition). These >> lines are neither present in the repository nor in the tar-ball. >> Therefore, my guess is that they are added at the packaging stage. >> >> Since the presence of a hashbang line breaks JessyInk, I wanted to ask >> whether it is possible to modify the packaging script in such a way that >> the lines are not added any more to the js files belonging to the >> JessyInk-extension (jessyInk.js, jessyInk_core_mouseHandler_noclick.js, >> jessyInk_core_mouseHandler_zoomControl.js). If packaging is not the >> problem please let me know, so that I can keep digging for the real cause. > > AFAIU this only affected on some linux distributions (0.48.1 with custom > patches on Ubuntu and Debian), and after having been reported on irc and > in debian's bug tracker, was addressed in: > > Bug #602005 "permissions of script files wrong/missing shebang lines" > <https://bugs.launchpad.net/inkscape/+bug/602005> > > (see comment #11 et seq.) > > > ~suv > > Thanks for pointing out the bug report to me and especially for taking care of the issue. Cheers, Hannes ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Hi Hannes, I patched the Ubuntu package (>= 0.48.1-2ubuntu5) to fix this problem.  You can try installing this in another DEB based distribution.  I don't foresee any problems as long as the distro has all the package dependencies available. ...

Hi John, The new version of the inkscape package is available in Ubuntu Oneiric (the latest development version).  Unfortunately, it is Ubuntu policy that only *major* issues get fixed in stable versions of Ubuntu (e.g. bugs that make the core functionality of packages completely unusable).  The rationale for this is that it is better to support packages with a few well known minor bugs than it is to support poorly-understood/experimental patches.  Because JessyInk is just an extension, it is unlikely that the fix will make it into Ubuntu Natty.