RFS: mercury

2009-08-24 Thread Paul Bone
Dear mentors, I am looking for a sponsor for my package "mercury". * Package name: mercury Version : 0.13.1+rotd20090725-1 Upstream Author : Mercury Develoeprs * URL : http://www.mercury.csse.unimelb.edu.au * License : GNU GPLv2 Section : devel I

Re: RFS: mercury

2009-08-24 Thread Paul Bone
On Tue, Aug 25, 2009 at 10:47:44AM +1000, Paul Bone wrote: > > Dear mentors, > > I am looking for a sponsor for my package "mercury". > > * Package name: mercury > Version : 0.13.1+rotd20090725-1 > Upstream Author : Mercury Develoeprs > * URL : http://www.mercury.cs

Re: RFS: micro-inetd (updated package)

2009-08-24 Thread Patrick Matthäi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hervé Rousseau schrieb: > On Sun, Aug 23, 2009 at 10:11 AM, Patrick Matthäi wrote: > [snip] >> Hello, >> >> could you please fix following lintian warnings: >> >> I: micro-inetd: copyright-with-old-dh-make-debian-copyright >> I: micro-inetd source: deb

Re: RFS: immv

2009-08-24 Thread Marco Herrn
On Mon, Aug 24, 2009 at 10:45:46AM -0300, Eduardo M KALINOWSKI wrote: > On Seg, 24 Ago 2009, Marco Herrn wrote: > >I know of the lintian warning about this package, that upstream sources > >don't differ from debian sources. The reason is that I am the upstream > >author and it is convenient for me

Re: RFS: immv

2009-08-24 Thread Eduardo M KALINOWSKI
On Seg, 24 Ago 2009, Marco Herrn wrote: I know of the lintian warning about this package, that upstream sources don't differ from debian sources. The reason is that I am the upstream author and it is convenient for me to store the /debian in the same repository as the programs source. It's fine

RFS: immv

2009-08-24 Thread Marco Herrn
Dear mentors, I am looking for a sponsor for my package "immv". * Package name: immv Version : 0.2-1 Upstream Author : Marco Herrn * URL : http://immv.berlios.de * License : GPL Section : utils It builds these binary packages: immv - Rename mu

Re: how to solve a non pic code in an shlib due to assembly code

2009-08-24 Thread Goswin von Brederlow
Ove Kaaven writes: > Goswin von Brederlow skrev: >> Ove Kaaven writes: >> >>> However, if they can't or won't fix it, there's *some* good news. In >>> general, shared libraries must be compiled as PIC because on some >>> platforms, the library just won't work properly if you don't. However, >>>