Re: RFS: torrentflux-b4rt

2012-05-24 Thread Panayiotis Karabassis
On 24/05/2012 05:27 μμ, Panayiotis Karabassis wrote: > On 10/07/2011 04:35 πμ, Michael Tautschnig wrote: >> Hi, >> >> [...] >> >> Here's a preliminary review of your package: >> >> - The source package contains several versions of other clients a

Re: RFS: torrentflux-b4rt

2012-05-24 Thread Panayiotis Karabassis
On 10/07/2011 04:35 πμ, Michael Tautschnig wrote: > Hi, > > [...] > > Here's a preliminary review of your package: > > - The source package contains several versions of other clients as archives in > the clients/ directory. For one, this seems strange, as both other clients > appear to be packa

RFS: torrentflux-b4rt

2011-05-03 Thread Panayiotis Karabassis
ebian/pool/main/t/torrentflux-b4rt/torrentflux-b4rt_1.0-beta2-1.dsc I would be glad if someone reviewed, and if it is ok, uploaded this package for me. - -- Best regards, Panayiotis Karabassis -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozi

Re: pbuilder and ${shlibs:Depends}

2011-03-18 Thread Panayiotis Karabassis
> Unfortunately this is wrong, at least for ELF binaries. Usually if you > don't have all the dependencies that you expect, it's because they are > optional and are disabled when they are not found during ./configure. > > Thus the correct solution is to add the required -dev packages in the > Buil

Re: pbuilder and ${shlibs:Depends}

2011-03-18 Thread Panayiotis Karabassis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/18/2011 05:57 PM, Paul Gevers wrote: > I believe that this variable will only resolve libraries which you > depend on (and you need the -dev package in the build dependencies). It > will never find a executable which you need to RUN your program.

pbuilder and ${shlibs:Depends}

2011-03-18 Thread Panayiotis Karabassis
Reposted from debian-user: Hi, I have a question regarding pbuilder. My Debian package uses ${shlibs:Depends} in its Depends field. However, in a pbuilder environment not all dependencies are installed, and hence ${shlibs:Depends} does not expand to *all* real dependencies. My question is: how