On 01/09/10 20:40, Stephen Sinclair wrote:
> Hello,
>
> This is a general question about linking to proprietary libraries.
> Specifically I am thinking about developing a library which will work
> normally in the general case, but in some cases the user might have a
> proprietary library installed
Hello,
This is a general question about linking to proprietary libraries.
Specifically I am thinking about developing a library which will work
normally in the general case, but in some cases the user might have a
proprietary library installed on their system, in which case I'd like
to dynamically
Thanks, I was using incorrect names for the additional source packages.
Thanks again,
Chris
On Wed, 2010-09-01 at 15:13 +0200, Simon Richter wrote:
> Hi,
>
> On Wed, Sep 01, 2010 at 01:37:37PM +0100, Chris Baines wrote:
>
> > I think it should say something about the other original tarballs th
Dear mentors,
I am looking for a sponsor for the new version 1.7a-1
of my package "sslh".
It builds these binary packages:
sslh - ssl/ssh multiplexer
The package appears to be lintian clean.
The upload would fix these bugs: 563156, 565858, 593673, 593766, 594019,
594124, 594212, 594508,
Something left to do?
Regards
Matthias
---
The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/p/packagekit
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- d
Hi,
On Wed, Sep 01, 2010 at 01:37:37PM +0100, Chris Baines wrote:
> I think it should say something about the other original tarballs there
> as well. Is there anything I am missing?
Look at my package "foundry" for an example on how to use multiple
tarballs.
Simon
--
To UNSUBSCRIBE, emai
This is a QA upload that really fixes #527416. It was supposed to be
fixed in -3, but
* Package name: libjackasyn
Version : 0.11
Debian Revision : 5
* URL : http://covered.sourceforge.net
* License : GPL-2+
Languages : C, Tcl
Section
Dear Mentors,
My package uses 4 original tarballs, one of the files within these needs
to be patched, however the patch fails. I think this is because it is
not extracting the additional original tarballs in to the temporary
build directory.
This is part of the build log:
dpkg-source: inf
Dear mentors!
Recently I started a conversation about uploading new release of
buildbot package with a lot of changes in the Debian part of the
package too (http://lists.debian.org/debian-mentors/2010/08/msg00258.html).
Since the package has an official maintainer who uploads his work on
other pac
9 matches
Mail list logo
