Re: how to solve little bugs found by lintian

Sean 'Shaleh' Perry [EMAIL PROTECTED] writes: On 25-Jun-99 Christian Kurz wrote: E: debauch: no-shlibs-control-file usr/lib/libdebauch.so.0.1 N: N: Though the package includes a shared library, the package does not N: have a shlibs control file. If this is intentional, please contact

Could someone sanity-check my first .debs?

I've just made my first two .debs. I'm going to upload these as soon as I get registered as a developer (I just need to dig up a copy of my birth certificate so that I can submit my application.) They are the File::KGlob and MPEG::MP3Info modules from CPAN. I use them as dependencies for a

Re: how to solve little bugs found by lintian

[Please don't send me any Cc, I read the list where I write.] James Troup [EMAIL PROTECTED] wrote: Sean 'Shaleh' Perry [EMAIL PROTECTED] writes: On 25-Jun-99 Christian Kurz wrote: E: debauch: no-shlibs-control-file usr/lib/libdebauch.so.0.1 N: N: Though the package includes a shared

Re: replacing conflicting packages

Christian Hammers wrote: Hello List I have two sets of packages: A1,A2.. and B1,B2,B3... which each provides a working system (in this case a database) and conflict to each other. My intend was now to show the user - when he tries to update just one component - that that is not possible

Autoconf question

I am attempting to package a program that includes some icons. in Makefile.in, it has the following: [EMAIL PROTECTED]@ [EMAIL PROTECTED]@ [EMAIL PROTECTED]@ [EMAIL PROTECTED]@ [EMAIL PROTECTED]@/share/icons and these variables are referred to elsewhere. My problem is that when the Makefile is

Source packages?

I'm packaging some Perl modules and a program which is a bunch of Perl scripts. Everything in these packages is Perl code (and documentation). Do I need to make source packages for these? How would I go about doing that? -- Matthew Sachs [EMAIL PROTECTED] -- random fortune quote -- But like

maint-doc and dh_make

Ok, I'm trying to follow the maint-guide to build my own package. The problem is that the doc is assuming that dh_make is doing things that it isn't doing, like creating the .orig dir and making a default changelog entry. I followed the damn thing exactly, so whats going on? Should I be able to

Re: maint-doc and dh_make

On Sun, Jun 27, 1999 at 05:08:11PM -0400, Rahsheen Porter wrote: Ok, I'm trying to follow the maint-guide to build my own package. The problem is that the doc is assuming that dh_make is doing things that it isn't doing, like creating the .orig dir and making a default changelog entry. I

Re: Source packages?

Le Sun, Jun 27, 1999 at 04:52:47PM -0400, Matthew Sachs écrivait: I'm packaging some Perl modules and a program which is a bunch of Perl scripts. Everything in these packages is Perl code (and documentation). Do I need to make source packages for these? How would I go about doing that? Of

Re: maint-doc and dh_make

Ok, I'm trying to follow the maint-guide to build my own package. The problem is that the doc is assuming that dh_make is doing things that it isn't doing, like creating the .orig dir and making a default changelog entry. I followed the damn thing exactly, so whats going on? Should I be able

Re: Source packages?

On Sun, Jun 27, 1999 at 04:52:47PM -0400, Matthew Sachs wrote: Do I need to make source packages for these? Of course. Even if the binaries are identical to the sources, you need some scripting (ie. debian/rules etc) to produce the .debs, and that requires a source package. How would I go

Re: maint-doc and dh_make

On Sun, Jun 27, 1999 at 11:54:55PM +0200, Tomas Pihl wrote: Ok, I'm trying to follow the maint-guide to build my own package. The problem is that the doc is assuming that dh_make is doing things that it isn't doing, like creating the .orig dir and making a default changelog entry. I