On Tue, Aug 31, 2010 at 10:05:19PM -0400, Alexandre Quessy wrote:
Thanks a lot Jonas and everyone!
I followed the end of this thread and learn a little bit more from it.
I learned some rudiments of Debian, plus git-buildpackage in this
process. I'll learn more in the next ones, and with this one
On Wed, Sep 01, 2010 at 02:38:41 (CEST), Jonas Smedegaard wrote:
>>> Sorry - I am confused: why not suppress wrongly included private
>>> shared libraries from being registered by dh_shlibdeps?
>>
>>because you do want to consider their library dependencies
>>
>> (these shared libraries might have
Thanks a lot Jonas and everyone!
I followed the end of this thread and learn a little bit more from it.
I learned some rudiments of Debian, plus git-buildpackage in this
process. I'll learn more in the next ones, and with this one ore later
on as well.
Thanks again!
--
Alexandre Quessy
http://alex
On Tue, Aug 31, 2010 at 10:32:50PM +0200, Reinhard Tartler wrote:
On Tue, Aug 31, 2010 at 20:50:05 (CEST), Jonas Smedegaard wrote:
On Tue, Aug 31, 2010 at 06:48:21PM +0200, Reinhard Tartler wrote:
On Tue, Aug 31, 2010 at 17:44:38 (CEST), Jonas Smedegaard wrote:
On Tue, Aug 31, 2010 at 11:10:
On Tue, Aug 31, 2010 at 20:50:05 (CEST), Jonas Smedegaard wrote:
> On Tue, Aug 31, 2010 at 06:48:21PM +0200, Reinhard Tartler wrote:
>>On Tue, Aug 31, 2010 at 17:44:38 (CEST), Jonas Smedegaard wrote:
>>
>>> On Tue, Aug 31, 2010 at 11:10:03AM -0400, Felipe Sateler wrote:
On 31/08/10 08:41, Jona
On Tue, Aug 31, 2010 at 06:48:21PM +0200, Reinhard Tartler wrote:
On Tue, Aug 31, 2010 at 17:44:38 (CEST), Jonas Smedegaard wrote:
On Tue, Aug 31, 2010 at 11:10:03AM -0400, Felipe Sateler wrote:
On 31/08/10 08:41, Jonas Smedegaard wrote:
I am not sure how to properly package non-public share
On Tue, Aug 31, 2010 at 06:49:38PM +0200, Reinhard Tartler wrote:
On Tue, Aug 31, 2010 at 18:06:06 (CEST), Jonas Smedegaard wrote:
really depends on how the package uses them. In general, putting them
into /usr/lib/$package/ should do it, but it really depends on how
the package uses them. are
On Tue, Aug 31, 2010 at 18:06:06 (CEST), Jonas Smedegaard wrote:
>>really depends on how the package uses them. In general, putting them
>>into /usr/lib/$package/ should do it, but it really depends on how the
>>package uses them. are they used as plugins like in xine, vlc? or are
>>they convenien
On Tue, Aug 31, 2010 at 17:44:38 (CEST), Jonas Smedegaard wrote:
> On Tue, Aug 31, 2010 at 11:10:03AM -0400, Felipe Sateler wrote:
>>On 31/08/10 08:41, Jonas Smedegaard wrote:
>>
>>> I am not sure how to properly package non-public shared libraries.
>>>
>>> Please someone advice on this.
>>
>> Ins
On Tue, Aug 31, 2010 at 05:23:55PM +0200, Reinhard Tartler wrote:
On Tue, Aug 31, 2010 at 14:41:47 (CEST), Jonas Smedegaard wrote:
On Mon, Aug 30, 2010 at 10:26:12PM -0400, Alexandre Quessy wrote:
Hello everyone
2010/8/17 Alexandre Quessy :
2010/8/15 Alexandre Quessy :
2010/8/15 Jonas Smede
On Tue, Aug 31, 2010 at 11:10:03AM -0400, Felipe Sateler wrote:
On 31/08/10 08:41, Jonas Smedegaard wrote:
I am not sure how to properly package non-public shared libraries.
Please someone advice on this.
Install into /usr/lib/ and use RPATH on the executables using
it. If upstream uses aut
On Tue, Aug 31, 2010 at 14:41:47 (CEST), Jonas Smedegaard wrote:
> On Mon, Aug 30, 2010 at 10:26:12PM -0400, Alexandre Quessy wrote:
>>Hello everyone
>>
>>2010/8/17 Alexandre Quessy :
>>> 2010/8/15 Alexandre Quessy :
2010/8/15 Jonas Smedegaard :
> Manpage of milhouse says "There is also a
On 31/08/10 08:41, Jonas Smedegaard wrote:
> I am not sure how to properly package non-public shared libraries.
>
> Please someone advice on this.
Install into /usr/lib/ and use RPATH on the executables using
it. If upstream uses autotools, I think just passing an appropriate
libdir will do the
On Mon, Aug 30, 2010 at 10:26:12PM -0400, Alexandre Quessy wrote:
Hello everyone
2010/8/17 Alexandre Quessy :
2010/8/15 Alexandre Quessy :
2010/8/15 Jonas Smedegaard :
Manpage of milhouse says "There is also a shared video library". If
we expect this to be ever used, we should not ship the he
On Mon, Aug 30, 2010 at 10:26:12PM -0400, Alexandre Quessy wrote:
Hello everyone
2010/8/17 Alexandre Quessy :
2010/8/15 Alexandre Quessy :
2010/8/15 Jonas Smedegaard :
Manpage of milhouse says "There is also a shared video library". If
we expect this to be ever used, we should not ship the he
Hello everyone
2010/8/17 Alexandre Quessy :
> 2010/8/15 Alexandre Quessy :
>> 2010/8/15 Jonas Smedegaard :
>>> Manpage of milhouse says "There is also a shared video library". If we
>>> expect this to be ever used, we should not ship the header files together
>>> with the binary (in scenic-utils)
Hello Jonas,
Here is a little update about the libscenic-dev that we should create as well.
(I have never packaged C++ libraries. Should be relatively simple, no?)
2010/8/15 Alexandre Quessy :
> 2010/8/15 Jonas Smedegaard :
>> Manpage of milhouse says "There is also a shared video library". If we
Hello Jonas,
I see you have done more work on these packages. Nice.
2010/8/15 Jonas Smedegaard :
> Sorry - have been busy elsewhere. I am fine with you pinging me - doesn't
> annoy me at all, au contrare.
Ok. Yes, it brings up the email thread in the mail box. :)
> We did not make it for Debian
On Fri, Aug 06, 2010 at 09:59:27AM -0400, Alexandre Quessy wrote:
Hello again,
2010/7/31 Alexandre Quessy :
2010/7/26 Jonas Smedegaard :
Ok.
So? Are we close to the upload time? It seems to me we have solved
the most important issues with this packaging. The version packaged
is now the lat
Hello again,
2010/7/31 Alexandre Quessy :
> 2010/7/26 Jonas Smedegaard :
>> Ok.
>
> So? Are we close to the upload time? It seems to me we have solved the
> most important issues with this packaging. The version packaged is now
> the latest of the 0.6 stable branch. This software will be a useful
Hello!
2010/7/26 Jonas Smedegaard :
>
> Ok.
>
So? Are we close to the upload time? It seems to me we have solved the
most important issues with this packaging. The version packaged is now
the latest of the 0.6 stable branch. This software will be a useful
contribution to Debian, I believe.
Best
On Sun, Jul 25, 2010 at 09:06:34PM -0400, Alexandre Quessy wrote:
2010/7/22 Jonas Smedegaard :
I am having another look at it now...
Thanks for those fixes you have done. I was close to something that
works with my scenic.install and midistream.install files. Now, thanks
to you, each Python
Hello Jonas,
2010/7/22 Jonas Smedegaard :
> I am having another look at it now...
Thanks for those fixes you have done. I was close to something that
works with my scenic.install and midistream.install files. Now, thanks
to you, each Python files go in the right package.
I only find somewhat str
On Thu, Jul 22, 2010 at 02:28:11PM -0400, Alexandre Quessy wrote:
2010/7/20 Jonas Smedegaard :
On Tue, Jul 20, 2010 at 12:16:38PM -0400, Alexandre Quessy wrote:
On 10-07-20 12:07 PM, Alexandre Quessy wrote:
2) Replace the shebang by the proper Python version
We still need to set up the /usr
Hello Jonas and all,
2010/7/20 Jonas Smedegaard :
> On Tue, Jul 20, 2010 at 12:16:38PM -0400, Alexandre Quessy wrote:
>> On 10-07-20 12:07 PM, Alexandre Quessy wrote:
>>> 2) Replace the shebang by the proper Python version
>>
>> We still need to set up the /usr/bin/python2.6 thing.
That's still
Hi Alexandre (and others following this thread),
On Tue, Jul 20, 2010 at 12:16:38PM -0400, Alexandre Quessy wrote:
I just remebered that the man page bug has been fixed upstream! They
are now distributed with the tarball, and not rebuilt by
git-buildpackage.
On 10-07-20 12:07 PM, Alexandre Qu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello again,
I just remebered that the man page bug has been fixed upstream! They are
now distributed with the tarball, and not rebuilt by git-buildpackage.
On 10-07-20 12:07 PM, Alexandre Quessy wrote:
>
> Ok, so we have two major bugs to fix.
> 1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Jonas and the team,
I'm finally managing to put some more time on this. I spent a few weeks
without much Internet access. Meanwhile, we applied you patch upstream
and made a new release. There are issues to fix, though, since we
changed the way
On Mon, Jun 21, 2010 at 10:58:47AM -0400, Alexandre Quessy wrote:
On 10-06-21 06:38 AM, Jonas Smedegaard wrote:
From a quick glance it seems that your latest attempts are wrong. I
had a go at compiling now (my earlier laptop disk space problems have
been solved now!) but unfortunately didn'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Jonas and the team,
On 10-06-21 06:38 AM, Jonas Smedegaard wrote:
>
> From a quick glance it seems that your latest attempts are wrong. I
> had a go at compiling now (my earlier laptop disk space problems have
> been solved now!) but unfortun
Hi Alexandre (and others),
On Sun, Jun 20, 2010 at 11:51:10AM -0400, Alexandre Quessy wrote:
On 10-06-11 07:11 PM, Jonas Smedegaard wrote:
Hmmm. I see now that your Makefile.in for the python code uses
$(libdir) and not $(pythondir). This causes the code to not use
standard Python paths, so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
On 10-06-11 07:11 PM, Jonas Smedegaard wrote:
>
> Hmmm. I see now that your Makefile.in for the python code uses $(libdir)
> and not $(pythondir). This causes the code to not use standard Python
> paths, so that a) it is not possible to suppo
Hello Jonas,
On 10-06-11 07:11 PM, Jonas Smedegaard wrote:
>
> Right now the files are simply installed - not handled properly :-(
>
>
> I am heading for bed now, and am busy all day tomorrow. I will try find
> some time tomorrow night to elaborate more on this.
>
So, I think we will not mak
[commenting on other parts - missed in my first reply]
On Sat, Jun 12, 2010 at 10:04:22AM -0400, Alexandre Quessy wrote:
2010/6/11 Jonas Smedegaard :
Hmm. There is something weird with the pristine-tar data.
Did you use git-import-orig or something custom?
I first used git-import-orig, bu
On Sat, Jun 12, 2010 at 10:04:22AM -0400, Alexandre Quessy wrote:
Hello Jonas!
2010/6/11 Jonas Smedegaard :
Hmm. There is something weird with the pristine-tar data.
Did you use git-import-orig or something custom?
I first used git-import-orig, but it failed, since I had not set up my
gi
Hello Jonas!
2010/6/11 Jonas Smedegaard :
>
> Hmm. There is something weird with the pristine-tar data.
>
> Did you use git-import-orig or something custom?
>
I first used git-import-orig, but it failed, since I had not set up my
gitconfig with my correct user.name and user.email. It failed with
On Fri, Jun 11, 2010 at 06:32:48PM -0400, Alexandre Quessy wrote:
Hello !
I should import a new original tarball within a few hours. The 0.6.1
upstream release is out.
It's online!
Yes, I saw your commit messages :-)
I hope everything is OK.
Hmm. There is something weird with the
On Fri, Jun 11, 2010 at 05:49:13PM -0400, Alexandre Quessy wrote:
Thanks! It seems to work now. It's nice that it takes care of
deleting the .pyo files. The .pyc files are byte-compiled for Python
2.5, but it seems to work with 2.6 as well.
Good.
Not sure I read you correctly above: Do the s
Hello !
>
> I should import a new original tarball within a few hours. The 0.6.1
> upstream release is out.
>
It's online!
I hope everything is OK.
--
Alexandre Quessy
http://alexandre.quessy.net/
___
pkg-multimedia-maintainers mailing list
pkg-multim
Hello!
>>
>> Thanks! It seems to work now. It's nice that it takes care of deleting the
>> .pyo files. The .pyc files are byte-compiled for Python 2.5, but it seems to
>> work with 2.6 as well.
>
> Good.
>
> Not sure I read you correctly above: Do the snippet only cleanup half of the
> Python comp
On Wed, Jun 09, 2010 at 09:18:14PM -0400, Alexandre Quessy wrote:
Still working on this... It's not easy, but it's likely I will work
with more free projects involving multimedia, Python and the autotools
for a little while again. :)
Happy to hear that these challenges haven't turned you off.
Hello!
Still working on this... It's not easy, but it's likely I will work
with more free projects involving multimedia, Python and the autotools
for a little while again. :)
2010/6/9 Jonas Smedegaard :
>
> It should be DEB_PYTHON_MODULE_PACKAGES (not DEB_PYTHON_PACKAGES)
>
Thanks! It seems to wo
On Wed, Jun 09, 2010 at 02:23:51AM -0400, Alexandre Quessy wrote:
I changed my debian/rules files in order to use python-autotools.mk:
{{{
DEB_PYTHON_PRIVATE_MODULES_DIRS_scenic = /usr/lib/scenic/py
DEB_BUILDDIR = build
DEB_PYTHON_SYSTEM = pysupport
DEB_PYTHON_PACKAGES = scenic rtpmidi
include
Hello Jonas and everyone!
I greatly appreciate your help, by the way. :)
2010/6/8 Jonas Smedegaard :
>
> Until fixed upstream (which should be doable with autotools, I believe) we
> can probably (depending on the exact kind of problem happening, off course)
> hack the hashbang after build but befo
On Mon, Jun 07, 2010 at 12:29:55PM -0400, Alexandre Quessy wrote:
Hello Jonas and the team,
Here are some updates about the packaging of Scenic.
2010/6/3 Jonas Smedegaard :
Some additional packaging comments:
The project includes python code. We must then follow to Debian
Python Policy!
Si
Hello Jonas and the team,
Here are some updates about the packaging of Scenic.
2010/6/3 Jonas Smedegaard :
> Some additional packaging comments:
>
> The project includes python code. We must then follow to Debian Python
> Policy!
>
> Since the Python code apparently is all handled with GNU autoto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Jonas and the list!
On 10-06-05 03:51 AM, Jonas Smedegaard wrote:
> Lower that package relation to suggests, and document the benefit of
> installing that suggestion (without explaining the reason it is only
> suggested, that is development-grad
On Sat, Jun 05, 2010 at 08:03:18PM +0200, Jonas Smedegaard wrote:
On Sat, Jun 05, 2010 at 01:26:00PM -0400, Alexandre Quessy wrote:
I am not sure how to get rid of this lintian warning:
W: scenic source: package-lacks-versioned-build-depends-on-debhelper 7
Normal approach: Let debian/compat c
On Sat, Jun 05, 2010 at 01:26:00PM -0400, Alexandre Quessy wrote:
I am not sure how to get rid of this lintian warning:
W: scenic source: package-lacks-versioned-build-depends-on-debhelper 7
Normal approach: Let debian/compat contain "7" and edit debian/control
to have a tightened build-depen
Hello Jonas!
I am not sure how to get rid of this lintian warning:
W: scenic source: package-lacks-versioned-build-depends-on-debhelper 7
N:
N:The package doesn't declare a versioned build dependency on debhelper.
N:Recommended practice is to always declare an explicit versioned
N:dep
On Sat, Jun 05, 2010 at 03:44:01AM -0400, Alexandre Quessy wrote:
Hello again!
Just a quick update: I have create the 3 .install and .manpages files.
I think it doesn't make sense to separate the libraries from at least
the milhouse command-line tool, since they are used by it or with it
only.
On Sat, Jun 05, 2010 at 12:55:32AM -0400, Alexandre Quessy wrote:
I just thought about an issue that makes my package 33% unusable. :)
The MIDI streaming feature (which would be provided by the new
midistream package) relies on either python-portmidi or python-pygame
= 1.9.1. Those two packages
Hello again!
Just a quick update: I have create the 3 .install and .manpages files.
I think it doesn't make sense to separate the libraries from at least
the milhouse command-line tool, since they are used by it or with it
only.
I am still thinking about splitting the doc from the scenic package
Hello!
2010/6/5 Alexandre Quessy :
> Hello again!
>
> I just thought about an issue that makes my package 33% unusable. :)
> The MIDI streaming feature (which would be provided by the new
> midistream package) relies on either python-portmidi or python-pygame
>>= 1.9.1. Those two packages are not
Hello again!
I just thought about an issue that makes my package 33% unusable. :)
The MIDI streaming feature (which would be provided by the new
midistream package) relies on either python-portmidi or python-pygame
>= 1.9.1. Those two packages are not in Debian yet!
Actually, python-pygame 1.9.1
On Fri, Jun 04, 2010 at 04:57:40PM -0400, Alexandre Quessy wrote:
Hello Jonas,
So I have set up a Debian sid box. That will help. :)
Good!
2010/6/4 Jonas Smedegaard :
On Thu, Jun 03, 2010 at 11:59:18AM -0400, Alexandre Quessy wrote:
Done. I will have to add your license to the copyright o
Hello Jonas,
So I have set up a Debian sid box. That will help. :)
2010/6/4 Jonas Smedegaard :
> On Thu, Jun 03, 2010 at 11:59:18AM -0400, Alexandre Quessy wrote:
>
>> Done. I will have to add your license to the copyright of some of the
>> Debian packaging.
>
> What I do is maintain packaging li
On Thu, Jun 03, 2010 at 11:59:18AM -0400, Alexandre Quessy wrote:
Done. I will have to add your license to the copyright of some of the
Debian packaging.
What I do is maintain packaging licensing in debian/rules. And I
(ideally, when not too lazy) do not add licensing info of others but
ins
On Thu, Jun 03, 2010 at 12:13:11PM -0400, Alexandre Quessy wrote:
2010/6/3 Jonas Smedegaard :
Some additional packaging comments:
The project includes python code. We must then follow to Debian
Python Policy!
Since the Python code apparently is all handled with GNU autotools I
recommend t
Hello!
By the way, I will setup a Debian sid box tomorrow... If that can
reassure you guys on my sincerity. :)
I used to use mainly Debian for at least a year, but got lazy since
Ubuntu is so easy - but there's a tradeoff to it.
Anyways, back to work!
a
2010/6/3 Felipe Sateler :
> On Thu, Jun 3, 2
On Thu, Jun 3, 2010 at 11:59, Alexandre Quessy wrote:
>>
The binary package is arch: any, but the configure.ac checks for
linux/videodev2.h which I suspect means that the package will only
succesfully compile on Linux architectures. If correct, then the best
would
proba
Hello again. :)
2010/6/3 Jonas Smedegaard :
> Some additional packaging comments:
>
> The project includes python code. We must then follow to Debian Python
> Policy!
>
> Since the Python code apparently is all handled with GNU autotools I
> recommend to include python-autotools.mk (instead of au
Hello!
Some updates, since I'm currently working on this...
I have to fix the make clean upstream. There are still *.pyc files not
cleaned. (fixed) Some files are removed from the dist target. (It will
be effective in the next upstream release, which is 0.5.12)
There are "_trial_temp" and ".libs"
On Thu, Jun 3, 2010 at 06:23, Jonas Smedegaard wrote:
> As a related not, there are several ways to keep track of packaging changes,
> common ones being dch+dcommit and git+git-dch.
>
> Probably the most common one generally in Debian is to make your packaging
> change, add a changelog entry using
Some additional packaging comments:
The project includes python code. We must then follow to Debian Python
Policy!
Since the Python code apparently is all handled with GNU autotools I
recommend to include python-autotools.mk (instead of autotools.mk), add
the needed hints to debian/control,
On Wed, Jun 02, 2010 at 10:52:23PM -0400, Alexandre Quessy wrote:
2010/6/2 Jonas Smedegaard :
After a nice meal I now have some comments on your packaging:
First of all: Please package using git-buildpackage and upload to the
pkg-multimedia repository - more info here:
http://wiki.debian.org/
Hello Jonas and the team!
2010/6/2 Jonas Smedegaard :
> After a nice meal I now have some comments on your packaging:
>
> First of all: Please package using git-buildpackage and upload to the
> pkg-multimedia repository - more info here:
> http://wiki.debian.org/DebianMultimedia/DevelopPackaging
>
After a nice meal I now have some comments on your packaging:
First of all: Please package using git-buildpackage and upload to the
pkg-multimedia repository - more info here:
http://wiki.debian.org/DebianMultimedia/DevelopPackaging
When you have switched to Git, then add Vcs-Git and Vcs-Brow
Hello Jonas and the team!
I just released the 0.5.11 tag of Scenic. It contains a few bugfixes,
and I've worked on the packaging since 0.5.10-2. My first packaging
for it is on
http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=scenic
and is, of course, 0.5.11-1.
It builds s
On Wed, Jun 02, 2010 at 01:03:23PM -0400, Alexandre Quessy wrote:
Thanks for the precious informations. I rather work through a team and
build long-term cooperation, rather than though sponsors. I can work
with the Python-app team and the pkg-multimedia team.
Excellent!
2010/6/2 Jonas Smed
Hello Jonas,
Thanks for the precious informations. I rather work through a team and
build long-term cooperation, rather than though sponsors. I can work
with the Python-app team and the pkg-multimedia team.
2010/6/2 Jonas Smedegaard :
> Hi Alexandre,
>
> On Wed, Jun 02, 2010 at 10:42:27AM -0400, A
Hi Alexandre,
On Wed, Jun 02, 2010 at 10:42:27AM -0400, Alexandre Quessy wrote:
As a new member of this team, I would like to find a sponsor for the
scenic package.
There is sponsoring, and there is team maintainance. They are two
different styles of working together.
With sponsoring you
Hello dear members of the pkg-multimedia team,
As a new member of this team, I would like to find a sponsor for the
scenic package.
I use cdbs, but I am ready to switch to debhelper 7 if we fix some
issues I had with it. (we need to build it with --enable-mt)
I'm much active on the IRC.
a
--
73 matches
Mail list logo
