Re: [Bug 858954] Re: [needs-packaging] goocanvas 2.0

2011-12-15 Thread Timo Kluck
> * "dh_install: usr/lib/python2.7/site-packages/gi/overrides/GooCanvas.py > exists in debian/tmp but is not installed to anywhere" > > -> you need to install this one This one is only created if you have python-gobject-2-dev installed, which is deprecated. Do you think I should add a build depende

Re: [Bug 858954] Re: [needs-packaging] goocanvas 2.0

2011-12-08 Thread Timo Kluck
Another question: in addition to libgoocanvas-2.0-9, should there be a metapackage called libgoocanvas-2.0 that always depends on the current version? Should this package be made from the same source package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is

Re: [Bug 858954] Re: [needs-packaging] goocanvas 2.0

2011-12-07 Thread Timo Kluck
Can you explain (or find a link) where the soname number comes from? In this case, the libtool library version info is equal to 11:0:2. Where does the 9 come from? Guess: it's 11 - 2, but why? Relatedly, should I manually rename the binary package (and only the binary package?) to libgoocanvas-2.0

Re: [Bug 858954] Re: [needs-packaging] goocanvas 2.0

2011-11-24 Thread Timo Kluck
What's the standard here? I've already renamed the binary package to libgoocanvas-2.0{,-common,-dev}. Should the source package just be goocanvas-2.0 ? (I'm kind of confused by the existence of a libgoocanvas3 package which just contains version 0.15). -- You received this bug notification becaus