- Inkscape Devel - Inkscape Mailman

Bazaar repository error
by Krzysztof Kosiński 29 Nov '09

29 Nov '09

Hello I tried to push the node tool work to Launchpad, and I get this: bzr: ERROR: KnitRepository('lp-46092624:///~inkscape.dev/inkscape/trunk/.bzr/repository') is not compatible with CHKInventoryRepository('lp-46092624:///~tweenk/inkscape/gsoc-node-tool/.bzr/repository') different serializers Would a 'bzr upgrade' on the Launchpad repository fix this? Regards, Krzysztof

4 5

0.47 tarballs
by Ted Gould 29 Nov '09

29 Nov '09

Hello All, I have built and put up 0.47 tarballs on Sourceforge. I'll start by reminding everyone to not widely announce this yet, we'll wait for binaries to be available before doing so. Also, sorry to take so long on this, I was away from home for work but I'm back now :) https://sourceforge.net/projects/inkscape/files/inkscape/0.47/ I'll tag everything and update that stuff tomorrow (as I'm tired now) but the tarball is correct. --Ted == MD5 Sums == 7b497c8f673e40b05295a29f6e2111f4 inkscape-0.47.tar.bz2 79e83b29956727e8c86a27f815d71f76 inkscape-0.47.tar.bz2.asc 916c85b501bcfb0ae61fcf7318f36348 inkscape-0.47.tar.gz 95bc78c1c24262dd8f89c347a1ffdc5a inkscape-0.47.tar.gz.asc 64e59540374de68dd81eaabedca741dc inkscape-0.47.zip fbc4affd7bcc88453abb5f13b279d45e inkscape-0.47.zip.asc == SHA1 Sums == 7c75352f3882ebf4fcaebc22413bcb79bf3b7895 inkscape-0.47.tar.bz2 d2633fcd7451b7d1b98e0aa139890c960ef504ed inkscape-0.47.tar.bz2.asc aa39d5f7306edb21be4987651041bf50c13baf75 inkscape-0.47.tar.gz 2f6a238a606906822f11f162d95dd1876028f2f6 inkscape-0.47.tar.gz.asc d838901d8312a3e88e8a16f8e4710d923c89567c inkscape-0.47.zip d595cca3f55bab899b33905f35f087f67811445c inkscape-0.47.zip.asc

8 18

URGENT: Please update Mac OS X install instructions in the tarball !
by Wolf Drechsel 29 Nov '09

29 Nov '09

Hello, I want to repeat a request I stated a time ago: From my experience (which was graciously shared by ~suv), the present state of install instructions for Mac OS X is extremely misleading and can cause people to waste a lot of time. When a less experienced person downloads the tarball, he will tend to read the README, which will tell him: > Inkscape uses the standard procedure for compilation and installation: > > ./configure > make > make install When trying this, this man will run into trouble. I am very grateful that a lot of people invested lots of time in the wonderful packaging/macosx/osx-build.sh script. PLEASE, add a few lines to the READMEs - or create a distinguished "README_Mac_OS_X" to make clear, that the install procedure on a Mac is a different one. At this occasion the wiki entries should be revised. At least concerning the inkscape aqua affairs, the wiki is quite outdated; I added instructions which worked on my Mac. I think, using the osx- build.sh it's very simple now, it would be a pity to let things occur more complicated than they are in fact… Thanks and greetings, Wolf

2 1

Extension Repo
by Chris Mohler 29 Nov '09

29 Nov '09

Hi all, I was thinking about starting on an extension repo[0], and have a couple of questions. Should this be hosted by the Inkscape project? If so, how do I go about getting access? Or at least finding out what version of php/python/mysql are available to set up a local test site? If not, is anyone willing to pool resources for hosting? Or know of a good FOSS-friendly place to host? Any thoughts or opinions on server/language/db? I'm leaning toward apache/php/mysql, but something like cherrypy/python/sqlite would be well suited to this task as well. Thanks, Chris [0] http://wiki.inkscape.org/wiki/index.php/ExtensionsRepository

6 6

please provide support for graphicsmagick
by Dennis Heuer 29 Nov '09

29 Nov '09

hello inkscape supports imagemagick, which is nowadays usable but had a lot of issues. this is why i switched to graphicsmagick, a faster and more reliable (maintained) port of it. please consider supporting graphicsmagick. except of the names, both expose the same api. many thanks -- GorgonZola <gorgonzola@...1955...>

3 2

inkscape vs. vanilla system
by unknown＠example.com 29 Nov '09

29 Nov '09

seems that inkscape doesn't like to install on an up-to-date vanilla system. it relies too much on distro defaults. first, python is not found because the path searched at is not existing. it is not mentioned in any file on my system. python-config doesn't spit it out either: configure:9578: g++ -o conftest -g -O2 -fopenmp -Werror=format-security -Wall -Wformat -Wformat-security -W -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.cpp -lgc /opt/development/python-2.5/lib/python2.5/config/libpython2.5.so -lpthread -ldl -lutil >&5 g++: /opt/development/python-2.5/lib/python2.5/config/libpython2.5.so: No such file or directory the point is that "python2.5/config/" is a redundant fiction. also, i re-installed poppler with support for the unsupported xpdf headers. inkscape still didn't compile. then i turned off poppler support, which was also confirmed in the configuration overview. however, it is still used. and, the way it is used seems to be targeting at an older version: extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetExtGState(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:812: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetFillColorSpace(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1012: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp:1014: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetStrokeColorSpace(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1035: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp:1037: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetFillColorN(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1104: error: no matching function for call to 'GfxResources::lookupPattern (char*)' /usr/include/poppler/Gfx.h:113: note: candidates are: GfxPattern* GfxResources::lookupPattern(char*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opSetStrokeColorN(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1148: error: no matching function for call to 'GfxResources::lookupPattern (char*)' /usr/include/poppler/Gfx.h:113: note: candidates are: GfxPattern* GfxResources::lookupPattern(char*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::opShFill(Object*, int)': extension/internal/pdfinput/pdf-parser.cpp:1546: error: no matching function for call to 'GfxResources::lookupShading (char*)' /usr/include/poppler/Gfx.h:114: note: candidates are: GfxShading* GfxResources::lookupShading(char*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::doImage(Object*, Stream*, GBool)': extension/internal/pdfinput/pdf-parser.cpp:2510: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp:2595: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) extension/internal/pdfinput/pdf-parser.cpp: In member function 'void PdfParser::doForm(Object*)': extension/internal/pdfinput/pdf-parser.cpp:2770: error: no matching function for call to 'GfxColorSpace::parse (Object*)' /usr/include/poppler/GfxState.h:182: note: candidates are: static GfxColorSpace* GfxColorSpace::parse(Object*, Gfx*) i now tried the compilation process several times, always getting stuck, and always getting stuck after about half an hour. possibly you should port inkscape to "go" to make it break faster. also, if anybody wants to help me in this case, your surname should not be alexandre. many thanks. -- GorgonZola <gorgonzola@...1955...>

2 1

lp:inkscape should be operational
by Ted Gould 29 Nov '09

29 Nov '09

Hey all, Sorry to take so long on this. But, it turns out when you mess up one little thing -- you need to regen everything -- and that sucks :) Currently there is a trunk branch from SVN in Launchpad and associated with the name "lp:inkscape". The other branches are currently uploading, and are likely to be available tonight. I created a group for Inkscape developers: inkscape.dev[1]. Anyone in that group should have access to trunk. Anyone in the inkscape.admin[2] team should be able to add people, so if you have commit access in SF currently, grab someone on Jabber/IRC and get added to the inkscape.dev group. If you want, you can get the same effect of the -cvs mailing list by subscribing to the trunk branch. You can then edit your e-mail settings for what mail you want to get.[3] Lastly, some people might find the 5-minute tutorial on Bazaar.[4] --Ted [1] https://launchpad.net/~inkscape.dev [2] https://launchpad.net/~inkscape.admin [3] https://help.launchpad.net/Code/FindingAndDownloading#Staying%20up% 20to%20date [4] http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html

2 2

need help: trying to compile 047 X11 for Tiger
by Wolf Drechsel 29 Nov '09

29 Nov '09

Hello everybody, people who asked me to compile 0.47 X11 for Tiger did probabely not know what a bad idea that was - because things tend to be done much faster by oneself than when teaching a complete ignorant is required… - Nevertheless, I feel honoured by the request and regret having to bother all you with another set of childish questions. What I did up to now: I set up my machine and compiled 0.47 aqua, the description given here: http://wiki.inkscape.org/wiki/index.php/ CompilingMacOsX#Building_Aqua_November_2009 should be fairly accurate. Now I'd like to set up another tree for a X11 version, trying to follow this: http://wiki.inkscape.org/wiki/index.php/ CompilingMacOsX#Installing_a_second_Macports_tree_. 28recommended_approach.29 - but just the other way round - as my aqua building environment was the first in place. This is what the instructions say: > Installing a second Macports tree (recommended approach) > Rather than deactivating and reactivating ports, you can also keep > two MacPorts trees side by side, provided you install the second > one from source. Let say I want to install a new tree for native > versions in /opt/local/native, I would do > Right. I created a /opt/local/x11 instead > export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin > cd ~/MacPorts-1.x.x/ This is the first place to stumble - I dont have a ~/MacPorts- whatever, allthough the latest macports is installed. What's going wrong here? > ./configure --prefix=/opt/local-native --with-tclpackage=/Library/ > Tcl/macports-native make sudo make install Next stumble - I learned that the osx-build.sh script can do nearly everything. So does it make sense to call configure? > You can set this second tree up to always build packages with > specific variants. For example, you can edit the /opt/local-native/ > etc/macports/variants.conf file to have the following line: > > +universal +no_x11 +quartz O.k. - created a /opt/x11/etc/macports/variants.conf containing +x11 > You can remove the +universal if you only want to build inkscape > for your host architecture. You may also need to set alternate > applications_dir and frameworks_dir variables in the /opt/local- > native/etc/macports/macports.conf > There is not such a file. I can create /opt/x11/etc/macports/ macports.conf, but > file so that applications and frameworks install by this macports > (for example by python) don't clash with your standard macports tree. > … not the shadow on an idea what that means… > Then you need to have only one version of the port command in the > path at any time so you need to setup your .bashrc > (or .bash_profile or .profile) accordingly. I use shell aliases to > quickly and temporarily switch to the universal version: > > alias portpathregular="export PATH=/opt/local/bin:/opt/local/sbin:/ > Developer/Tools:/usr/local/bin: \ /usr/X11R6/bin:/bin:/sbin:/usr/ > bin:/usr/sbin" alias portpathnative="export PATH=/opt/local-native/ > bin:/opt/local-native/sbin:/Developer/Tools:/usr/local/bin: \ /usr/ > X11R6/bin:/bin:/sbin:/usr/bin:/usr/sbin" o.k. - that was easy. Inbetween I try to install the x11 variants of cairo +x11 pango +x11 poppler +x11 gtk2 +x11… As the patient reader, who came down to this place in my opus may have noticed - there is a big lack of fundamental knowledge here. So if anybody would be kind enough to give me further instructions on the questions mentioned above, mainly in what way the osx-build-sh can be part of it - I'd be grateful. Yours, Wolf

2 1

Release Notes for 0.48
by Joshua A. Andler 29 Nov '09

29 Nov '09

Hey All, As usual, if you add new features or fix really noteworthy bugs, please add appropriate information to the Release Notes page. I started the 0.48 page here: http://wiki.inkscape.org/wiki/index.php/ReleaseNotes048 Cheers, Josh

1 0

Re: [Inkscape-devel] [Inkscape-user] Inkscape 0.47 is released!
by JiHO 28 Nov '09

28 Nov '09

On Wed, Nov 25, 2009 at 02:12, Gary Hawkins <dragonlord666@...400...> wrote: > I know it's known of, just wondering if a solution was n the horizon. > I did try installing python but guess I don't know what I'm doing as it > didn't work LOL I will try to fix that next week. JiHO --- http://maururu.net

2 1