On Thu, Sep 07, 2006 at 10:18:29PM -0500, Luis Rodrigo Gallardo Cruz wrote:
> On Fri, Sep 08, 2006 at 10:01:47AM +1000, Matthew Palmer wrote:
> > On Thu, Sep 07, 2006 at 05:26:53PM -0500, Luis Rodrigo Gallardo Cruz wrote:
> > > On Thu, Sep 07, 2006 at 08:27:43PM +0200, kku wrote:
> > > > Now to det
On Fri, Sep 08, 2006 at 10:01:47AM +1000, Matthew Palmer wrote:
> On Thu, Sep 07, 2006 at 05:26:53PM -0500, Luis Rodrigo Gallardo Cruz wrote:
> > On Thu, Sep 07, 2006 at 08:27:43PM +0200, kku wrote:
> > > Now to detect that the user did (not) change the conf file, I check the
> > > md5sum of the c
On Thursday 07 September 2006 23:43, Andrew Donnellan wrote:
> On 9/8/06, George Danchev <[EMAIL PROTECTED]> wrote:
> > Upstream Author : [fill in]
> > * URL : [fill in]
> > * License : [fill in]
>
> It would be nice to actually fill these in.
Oh, sure. Copy&paste nuisancies
On Friday 08 September 2006 00:05, tony mancill wrote:
> Hello George,
Hello,
> I'm looking at this package. Here are a couple of comments so far:
Thanks for looking at the package and your comments.
> debian/control:
>
> * The package Architecture should be "all" instead of "any" - this will
On Wed, 06 Sep 2006 13:29:37 +0200, "Adam Cécile (Le_Vert)" <[EMAIL PROTECTED]>
wrote:
> Dear mentors,
>
> I am looking for a sponsor for the new version 1.0.2-2
> of my package "cobalt-panel-utils".
>
> It builds these binary packages:
> cobalt-panel-utils - System utilities for Sun Cobalt's LC
On Thu, Sep 07, 2006 at 05:26:53PM -0500, Luis Rodrigo Gallardo Cruz wrote:
> On Thu, Sep 07, 2006 at 08:27:43PM +0200, kku wrote:
> > >You are programaticaly managing a configuration file in /etc. You
> > >should look into using ucf, that already handles this.
> >
> > I've had a look at ucf, but
On Thu, Sep 07, 2006 at 08:27:43PM +0200, kku wrote:
> >You are programaticaly managing a configuration file in /etc. You
> >should look into using ucf, that already handles this.
>
> I've had a look at ucf, but I do not think it fits my need (unless I have
> overlooked something).
>
> I have a
Dear mentors,
I am looking for a sponsor for my package "personalbackup".
IANADD, so I can't sponsor. But my comments, anyways:
You should not depend in postgresql, since that is just a transitional
package. Depend on an specific version, or on several.
In a related note, should you depend on
Hello George,
I'm looking at this package. Here are a couple of comments so far:
debian/control:
* The package Architecture should be "all" instead of "any" - this will
prevent the (identical) package from being built for every Debian architecture.
* You can remove ${shlibs:Depends} from Depen
On 9/8/06, George Danchev <[EMAIL PROTECTED]> wrote:
Upstream Author : [fill in]
* URL : [fill in]
* License : [fill in]
It would be nice to actually fill these in.
--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
GPG -
Bas Wijnen <[EMAIL PROTECTED]> wrote:
> Also, someone noted that this script is vulnerable to a symlink attack in
> /tmp. I haven't found a good solution for that though, because I want to have
> a reachable build tree under a "normal" name, where I can see what all the
> files look like.
If you
Interesting thread. I've never thought about generating the tarball this
way, though I do have a lot of native packages that probably shouldn't
be.
If one general-purpose tool to handle this rises to the top and is
usable by many people, it would be a good candidate for addition to
devscripts.
--
Dear mentors,
I am looking for a sponsor for my package "c++-annotations".
* Package name: c++-annotations
Version : 6.4.0f-1
Upstream Author : Frank B. Brokken
* URL : ftp://ftp.rug.nl/contrib/frank/documents/annotations/
* License : GPL
Section : de
Dear mentors,
I am looking for a sponsor for my package "bisonc++".
* Package name: bisonc++
Version : 1.4.0-1
Upstream Author : [fill in]
* URL : [fill in]
* License : [fill in]
Section : devel
It builds these binary packages:
bisonc++ - Bison-sty
On Friday 01 September 2006 15:38, George Danchev wrote:
> Dear mentors,
>
> I am looking for a sponsor for the new version 1.10.2-1
> of my package "bobcat".
>
> It builds these binary packages:
> libbobcat1 - run-time (shared) Bobcat library
> libbobcat1-dev - headers and documentation for the Bo
I've uploaded it again. I've fixed some bugs (mkspecs was wrongly named
mkspects) and made a clearer rules design using dpatch.
By the way ¿are you an uploader? Would you sponsor the package or I have to
keep searching?
El Miércoles, 6 de Septiembre de 2006 18:03, Adam Cecile escribió:
> Ok some
On 9/7/06, Thibaut Paumard <[EMAIL PROTECTED]> wrote:
PS: I have no clue what the RCS package is (I did have a look on google,
it does have a co command), or what this well-named "missing" file is
supposed to do.
RCS is the Revision Control System, think along the lines of CVS, SVN,
etc. It's g
Le mardi 05 septembre 2006 à 18:46 +0200, Michelle Konzack a écrit :
> Hello Mentors,
>
> Currently I try to pack the "swhoisd" and make the german localization.
>
Just my 2 cents...
[...]
>
> ./configure works fine with the exception of the beginning and the
> "missing" error:
>
> 8<-
> True. Have a look at how to deal with lintian's overrides:
> file:/usr/share/doc/lintian/lintian.html/ch2.html#s2.4
> (tip: you want to override 3 binary type packages)
I will check this thanks.
> As long as you are reachible via these addresses it is not a big deal. Of
> course it would be ni
(sorry, forgot to CC: debian-mentors@)
Hi Michelle,
> Hello Mentors,
>
> Currently I try to pack the "swhoisd" and make the german localization.
[...]
> co RCS/swhoisd,v swhoisd
> make[2]: co: Kommando nicht gefunden
You will find the co program in the rcs package.
HTH,
Thomas
--
To UNSU
On Thursday 07 September 2006 11:51, [EMAIL PROTECTED] wrote:
> Hello
Hello,
> > * lintian errors:
> > E: lisaac-doc: copyright-should-refer-to-common-license-file-for-gpl
> > E: lisaac-common: copyright-should-refer-to-common-license-file-for-gpl
> > E: lisaac: copyright-should-refer-to-common-l
Hello Mentors,
Currently I try to pack the "swhoisd" and make the german localization.
Now I have problems with some things like autoconf, automake and such,
since I do not know what to do (never used it).
I have allready compiled swhoisd for arround 3 years (!!!) but do not
know anymore how, be
Am 2006-09-01 15:07:08, schrieb Eddy Petrisor:
> On 31/08/06, Michelle Konzack <[EMAIL PROTECTED]> wrote:
> >But unfortunatly it can not rename files while using dh_install and
> >I like to see a dh_installpo like the dh_installman which put the
> >.CC.N in the right CountryCode section...
> >
> >S
Hello
> * lintian errors:
> E: lisaac-doc: copyright-should-refer-to-common-license-file-for-gpl
> E: lisaac-common: copyright-should-refer-to-common-license-file-for-gpl
> E: lisaac: copyright-should-refer-to-common-license-file-for-gpl
For thoses errors. In fact the text of the Cecillv2 licence
also sprach Ben Finney <[EMAIL PROTECTED]> [2006.09.07.0803 +0200]:
> Unfortunately, Debian doesn't yet have a 'bzr-buildpackage' package.
James (and I) are working on it:
http://wiki.debian.org/BzrBuildpackage
--
Please do not send copies of list mail to me; I read the list!
.''`. martin
also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.09.07.0714 +0200]:
> That's what I do for releases as well. For normal testing builds though
> (that's to see if the package builds and works without planning a release),
> creating a tarball and unpacking it first is too much work IMO. So I wrote
Hi Ben,
if you create yourself the orig.tar.gz, the building tools from debian
don't try to create it themselves.
i.e. something like:
tar cvzf foo_X.Y.orig.tar.gz --exclude=foo-X.Y/debian foo-X.Y
before actually building the package should solve your problem.
Hope this helps, Eric
--
You don't
On Thursday 07 September 2006 09:42, Russ Allbery wrote:
> Bas Wijnen <[EMAIL PROTECTED]> writes:
> > That's what I do for releases as well. For normal testing builds though
> > (that's to see if the package builds and works without planning a
> > release), creating a tarball and unpacking it firs
28 matches
Mail list logo
