Re: Newbie question: missing conf file

2005-01-31 Thread Bartosz Fenski aka fEnIo
On Sun, Jan 30, 2005 at 10:27:08PM +0100, [EMAIL PROTECTED] wrote: I take it you are upstream as well? I think the recommended way of doing upstream+debian is to have the .diff include all of ./debian/, such that other distros don't have to deal with it. Also, that way you can do a Debian

Re: Newbie question: missing conf file

2005-01-31 Thread Achim Bohnet
On Sunday 30 January 2005 21:27, Adeodato Simó wrote: * [EMAIL PROTECTED] [Sun, 30 Jan 2005 21:17:56 +0100]: This conf file is present in the DEB files, but after installation, it is not being copied to the /etc/dibbler directory. Try: # dpkg --purge

Re: Newbie question: missing conf file

2005-01-31 Thread Adeodato Simó
* Achim Bohnet [Mon, 31 Jan 2005 13:15:13 +0100]: $ dpkg --force-help | grep confmiss confmiss [!] Always install missing config files So 1.5 points for me. 1 for the why (and 0.5 because it's faster that purge and install ;) Indeed! :) -- Adeodato Simó EM: asp16

RFS(2): autoreply - A safe, rate-limited auto-responder

2005-01-31 Thread Chris Sacca
This is my second attempt at a Request for Sponsor, though admittedly, after being on Debian-mentors a few weeks, I realize how lame my first attempt was ( and thus probably why it merited no replies ). This is a single binary package. It's small, lintian and linda clean, I have the blessing

Re: RFS(2): autoreply - A safe, rate-limited auto-responder

2005-01-31 Thread Bartosz Fenski aka fEnIo
On Mon, Jan 31, 2005 at 10:08:50AM -0500, Chris Sacca wrote: This is a single binary package. It's small, lintian and linda clean, I have the blessing of the upstream maintainer, and have filed and ITP ( #292667 ). You don't close it in your changelog entry. That's wrong. [...]

Re: RFS(2): autoreply - A safe, rate-limited auto-responder

2005-01-31 Thread Chris Sacca
Thank you for your corrections, Bartosz. [...] filed and ITP ( #292667 ). You don't close it in your changelog entry. That's wrong. Sorry, should have read the new maintainers' guide more closely. I fixed this. Hopefully someone will sponsor me, but if not, I would really appreciate

Re: RFS(2): autoreply - A safe, rate-limited auto-responder

2005-01-31 Thread Blars Blarson
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes: At first glance autoreply looks very much like just another vacation clone, but it takes the behavior of vacation and takes it to another lever. The notable differences between autoreply and vacation are: * As opposed to vacation that

Re: RFS(2): autoreply - A safe, rate-limited auto-responder

2005-01-31 Thread Lucas Wall
Blars Blarson wrote, On 01/31/2005 06:40 PM: [...] In other words, this looks like yet another vaction clone by someone who didn't bother to read the vacation man page. At least it sound like it might not be another bad clone of vacation. Does this mean you oppose to the inclusion of autoreply in

Re: RFS(2): autoreply - A safe, rate-limited auto-responder

2005-01-31 Thread Florent Rougon
Blars Blarson [EMAIL PROTECTED] wrote: In other words, this looks like yet another vaction clone by someone who didn't bother to read the vacation man page. IMO, such judgments are not acceptable on public mailing-lists[1]. If the upstream author felt like writing a program similar to

Re: RFS(2): autoreply - A safe, rate-limited auto-responder

2005-01-31 Thread Don Armstrong
On Mon, 31 Jan 2005, Florent Rougon wrote: Blars Blarson [EMAIL PROTECTED] wrote: In other words, this looks like yet another vaction clone by someone who didn't bother to read the vacation man page. IMO, such judgments are not acceptable on public mailing-lists[1]. If the upstream author

Re: Re: RFS(2): autoreply - A safe, rate-limited auto-responder

2005-01-31 Thread Richard A. Hecker
You used a judgement to say judgements are not acceptable. Last time I checked, Debian did not have any opennings in the PC police department ;-) Richard P.S. PC (political correctness) for those hardcore geeks amongst us. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Re: RFS(2): autoreply - A safe, rate-limited auto-responder

2005-01-31 Thread Blars Blarson
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes: Blars Blarson wrote, On 01/31/2005 06:40 PM: [...] In other words, this looks like yet another vaction clone by someone who didn't bother to read the vacation man page. At least it sound like it might not be another bad clone of

Re: RFS(2): autoreply - A safe, rate-limited auto-responder

2005-01-31 Thread Russell Stuart
On Tue, 2005-02-01 at 10:14, Blars Blarson wrote: I do think that it should be objectivly compared with vacation before Debian decides to add it to to their archives. At least this sounds like it won't be one of the poorly done vacation clones that does mailbombs. I have a question. Is

maserver: Dynamic libraries inside a program package

2005-01-31 Thread Miriam Ruiz
Hi, I'm trying to package a program named maserver ( http://www.babichev.info/en/projects/maserver/index.html ), which is an audio streaming server for LAN and internet. The file structure resulting from install (with some tweaks) is right now: Configuration files: etc/maserver/* Binary:

Re: maserver: Dynamic libraries inside a program package

2005-01-31 Thread Steve Langasek
On Tue, Feb 01, 2005 at 02:31:27AM +0100, Miriam Ruiz wrote: I'm trying to package a program named maserver ( http://www.babichev.info/en/projects/maserver/index.html ), which is an audio streaming server for LAN and internet. The file structure resulting from install (with some tweaks) is

Re: maserver: Dynamic libraries inside a program package

2005-01-31 Thread Justin Pryzby
On Tue, Feb 01, 2005 at 02:31:27AM +0100, Miriam Ruiz wrote: Hi, Hiya, Now running lintian... E: maserver: sharedobject-in-library-directory-not-actually-a-shlib usr/lib/libmaserver.so.1.0 Finished running lintian. Try lintian -i: you'll see this type of thing: A shared object was

Re: maserver: Dynamic libraries inside a program package

2005-01-31 Thread Miriam Ruiz
It's true that you usually should not have shared libraries in an application package, but that is not the meaning of this error. This error means that the file that you have placed in /usr/lib is *not a shared library*. If the file does not declare an SONAME, it's not a shared library

Re: maserver: Dynamic libraries inside a program package

2005-01-31 Thread Steve Langasek
On Tue, Feb 01, 2005 at 04:00:00AM +0100, Miriam Ruiz wrote: It's true that you usually should not have shared libraries in an application package, but that is not the meaning of this error. This error means that the file that you have placed in /usr/lib is *not a shared library*.

Re: RFS: Requesting to add new package by non-DD

2005-01-31 Thread Osamu Aoki
On Tue, Feb 01, 2005 at 11:30:27AM +1000, Russell Stuart wrote: On Tue, 2005-02-01 at 10:14, Blars Blarson wrote: I do think that it should be objectivly compared with vacation before Debian decides to add it to to their archives. At least this sounds like it won't be one of the poorly

Re: [Pkg-alsa-devel] RFS: alsa-tools

2005-01-31 Thread Walter Landry
Marco d'Itri [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: Do we have to split the alsa-tools source into two packages, one free and one non-free/contrib? It will make it a bit harder. No. Unfortunately, that is not the case. All of the source for packages in main must satisfy the