Re: RFS: php-ezcomponents

I've updated the package to the new upstream version 2009.1.1. > Dear mentors, > > I am looking for a sponsor for my package "php-ezcomponents". > > * Package name: php-ezcomponents > Version : 2009.1-1 > Upstream Author : eZ Systems AS > * URL : http://ezcomponents.org

Re: [php-maint] RFS: php-ezcomponents

Do you really need to split ALL components into separate packages? For me it would make more sense to: - strip all tests out (huge save of disk space) - separate */docs to separate package (php-ezcomponents-docs) - remove */design or move it to docs if needed - strip all kind of useless junk in *

Re: [php-maint] RFS: php-ezcomponents

Hi Ondrej, thanks for looking at my package. Does it matter, how big the source package is? Since the files you mention don't end up in the binary package, I'd rather just leave it as is. Yes, upstream and me really like to have each component in an individual binary package. Upstream puts big

Can't open man1/optin.so: No such file or directory

Hi there,  I am working on the dicom3tools package. The dicom3tools is writing the man page using groff '.so' macro (source) (*). Which leads to the following lintian warning : W: dicom3tools: manpage-has-errors-from-man usr/share/man/man1/andump.1.gz  can't open man1/optin.so: No such file or di

Re: [php-maint] RFS: php-ezcomponents

Hi Thomas, On Tue, Jul 28, 2009 at 14:09, Thomas Koch wrote: > Hi Ondrej, > > thanks for looking at my package. > > Does it matter, how big the source package is? Since the files you mention > don't end up in the binary package, I'd rather just leave it as is. It's not about size of source file.

Re: [php-maint] RFS: php-ezcomponents

Hi Ondrej, > > Yes, upstream and me really like to have each component in an individual > > binary package. Upstream puts big efforts into makeing each component > > independent and usable as standalone. > > They're not - some of components have dependencies on another > components (*/DEPS) There

ldconfig symlink issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I apologize for this question, as it's probably easy to answer for someone experienced in packaging libraries. When packaging a shared library, I can't seem to create the symlinks correctly. If I let the Makefile create the symlinks I get ldconfig-sym

Re: MUMmer patches and Artistic license.

On Sun, Jul 12, 2009 at 10:50:10PM +0900, Charles Plessy wrote: > > This patch is a good idea -- fixed length buffers are rarely considered > > user-friendly. However, it is executed poorly; it's not ready for upstream > > in its current state. > > Hi, thank you for the comment. > > I will sto

Re: ldconfig symlink issue

On Wednesday 29,July,2009 12:38 AM, Harry Rickards wrote: > I apologize for this question, as it's probably easy to answer for > someone experienced in packaging libraries. > > When packaging a shared library, I can't seem to create the symlinks > correctly. If I let the Makefile create the symlin

Re: MUMmer patches and Artistic license.

In <20090728163525.gc31...@an3as.eu>, Andreas Tille wrote: >On Sun, Jul 12, 2009 at 10:50:10PM +0900, Charles Plessy wrote: >> > This patch is a good idea -- fixed length buffers are rarely >> > considered user-friendly. However, it is executed poorly; it's not >> > ready for upstream in its curre

Re: ldconfig symlink issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chow Loong Jin wrote: > On Wednesday 29,July,2009 12:38 AM, Harry Rickards wrote: >> I apologize for this question, as it's probably easy to answer for >> someone experienced in packaging libraries. >> >> When packaging a shared library, I can't seem t

RFS: libpcapnav

Dear mentors, I am looking for a sponsor for my package "libpcapnav". * Package name: libpcapnav Version : 0.8-1 Upstream Author : Christian Kreibich * URL : http://netdude.sourceforge.net Section : libs It builds these binary packages:

Re: MUMmer patches and Artistic license.

In <200907281303.42301@iguanasuicide.net>, Boyd Stephen Smith Jr. wrote: >In <20090728163525.gc31...@an3as.eu>, Andreas Tille wrote: >>On Sun, Jul 12, 2009 at 10:50:10PM +0900, Charles Plessy wrote: >>> > This patch is a good idea -- fixed length buffers are rarely >>> > considered user-friendl

Re: Can't open man1/optin.so: No such file or directory

> Hi there, Hi, > I am working on the dicom3tools package. The dicom3tools is writing > the man page using groff '.so' macro (source) (*). Which leads to the > following lintian warning : > > W: dicom3tools: manpage-has-errors-from-man > usr/share/man/man1/andump.1.gz can't open man1/optin.so:

Define files for multiple packages from one tarball

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry to bother everyone again with a noob question (Google was no help), but how do you define which files go in which package when you have multiple packages for one tarball. I've got 4 packages, libweed-dev, libweed0, lives and lives-data. I've crea

Re: Define files for multiple packages from one tarball

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harry Rickards wrote: > Sorry to bother everyone again with a noob question (Google was no > help), but how do you define which files go in which package when you > have multiple packages for one tarball. I've got 4 packages, > libweed-dev, libweed0, l

RFS: dict-devil (adopted package)

Dear mentors, I am looking for a sponsor for the new version 1.0-11 of my package "dict-devil". It builds this binary package: dict-devil - The Devil's Dictionary by Ambrose Bierce This package contains The Devil's Dictionary, a satirical, cynical and irreverent dictionary of common words, forma

Re: Can't open man1/optin.so: No such file or directory

George Danchev writes: > There is no easy way for dh_installman to guess that optin.so as found > in source directory is actually a manpage content meant for inclusion, > so you should take the control yourself and install that files in place > from debian/rules either by copying it or by calling

Re: RFS: joystick (updated package fixing a serious bug)

On Tue, 21 Jul 2009 14:44:18 -0400, Barry deFreese wrote: > Uploaded. Thanks! Thank you (belatedly), and also for sponsoring the previous upload! Regards, Stephen -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...

Re: Can't open man1/optin.so: No such file or directory

> George Danchev writes: > > There is no easy way for dh_installman to guess that optin.so as found > > in source directory is actually a manpage content meant for inclusion, > > so you should take the control yourself and install that files in place > > from debian/rules either by copying it or b

Re: UNS: Re: RFS: lshell (3rd try)

On Tue, Jul 28, 2009 at 05:31, Maximiliano Curia wrote: > Hola Ignace Mouzannar! Hola Maximiliano! > There a few ways to check if a group exists, calling sg group_name true is a > creative one, I not against the solution, but using getent group > group_name is probably a more traditional approach

Re: UNS: Re: RFS: lshell (3rd try)

Hola Ignace Mouzannar! El 29/07/2009 a las 01:20 escribiste: > > - It would be great if you document how to use lshell inside a chroot, > > maybe > > even using makejail. > I am planning to work on this in the upcoming release. Ok, a few other things to add to the TODO list: - Upstream chan

Re: Can't open man1/optin.so: No such file or directory

On Tue, 2009-07-28 at 16:10 +0200, Mathieu Malaterre wrote: > Hi there, > > I am working on the dicom3tools package. The dicom3tools is writing > the man page using groff '.so' macro (source) (*). Which leads to the > following lintian warning : > > W: dicom3tools: manpage-has-errors-from-man >