Re: Copyright question
Hi Jean! You wrote: > I intend to package HPL benchmarks. Copyright file contains the > following statements: > -- > 1. Redistributions of source code must retain the above copyright > notice, this list of conditions and the following disclaimer. > > 2. Redistributions in binary form must reproduce the above copyright > notice, this list of conditions, and the following disclaimer in the > documentation and/or other materials provided with the distribution. > > 3. All advertising materials mentioning features or use of this > software must display the following acknowledgement: > This product includes software developed at the University of > Tennessee, Knoxville, Innovative Computing Laboratories. > > 4. The name of the University, the name of the Laboratory, or the > names of its contributors may not be used to endorse or promote > products derived from this software without specific written > permission. > > > I've read DFSG and I'm not sure if items 3 and 4 are problematic. Can > someone help me ? If it's not ok, may it be in contrib ? Why is that probematic? It seems like a default 4-clause BSD license to me. Should be fine, unless you intend to link it against GPL code. Kind regards, Bas. -- +--+ | Bas Zoetekouw | Sweet day, so cool, so calm, so bright, | || The bridall of the earth and skie: | | [EMAIL PROTECTED] | The dew shall weep thy fall tonight;| +|For thou must die. | +-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: arCHMage - CHM(Compiled HTML) Decompressor
Hi Paul! You wrote: > You need to add build-depends on chmlib-dev and cdbs. There is no > python-pychm package in debian at the moment, so perhaps you could > include that code until there is. I'm sponsoring the python-chm package for Carlos Z.F. Liu, and I will probably upload today or tomorrow. In the mean time, his package can be found at mentors.debian.net (the source package is called pychm). -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Stupid shebang tricks
Hi martin! You wrote: > True. But before it will even be considered to make env standard, > the parameter problem would have to be solved. perl -w and /bin/sh > -e are just necessary. Just put "use warnings;" or "set -e" in the script. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CERN root
Hi Adam! You wrote: > The license is at http://root.cern.ch/root/License.html. I'm assuming the > specific cause of concern is: > > "Additionally, the authors grant permission to modify this software and its > documentation for any purpose, provided that such modifications are not > distributed without the explicit consent of the authors" Even worse, it apparently links against Xclass (LGPL) and Cernlib (GPL) libraries[1], while the above license it clearly GPL- (and possibly(?) LGPL-) incompatible. Theredore, it cannot even be legally distributed. [1] http://www.princeton.edu/~kmccarty/physics-software-rant.html -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: rlplot - generate publication quality graphs
Hi Don! You wrote: > Presumably it does postscript or svg output... (R does the former, and > you can trivially convert to the later.) How? gs doesn't seem to have a svg output driver. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: RFS: rlplot - generate publication quality graphs
Hi Don! You wrote: > Presumably it does postscript or svg output... (R does the former, and > you can trivially convert to the later.) How? gs doesn't seem to have a svg output driver. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Long double alignment test
Hi Brett! You wrote: > Anyone know if this works? Could someone please run this on each of > the archs we support (particularly ia64) and report the results to me? Ok. alpha: your code: sizeof(foo)=16 sizeof(align)=8 sizeof(f2)=32 union may be aligned on 8 byte boundaries. Neal's code: char: 1 short: 2 int: 4 long: 8 long long: 8 void*: 8 float: 4 double: 8 long double: 8 ia64: your code: sizeof(foo)=16 sizeof(align)=8 sizeof(f2)=32 union may be aligned on 8 byte boundaries. Neal's: char: 1 short: 2 int: 4 long: 8 long long: 8 void*: 8 float: 4 double: 8 long double: 16 -- Kind regards, +----+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: Long double alignment test
Hi Brett! You wrote: > Anyone know if this works? Could someone please run this on each of > the archs we support (particularly ia64) and report the results to me? Ok. alpha: your code: sizeof(foo)=16 sizeof(align)=8 sizeof(f2)=32 union may be aligned on 8 byte boundaries. Neal's code: char: 1 short: 2 int: 4 long: 8 long long: 8 void*: 8 float: 4 double: 8 long double: 8 ia64: your code: sizeof(foo)=16 sizeof(align)=8 sizeof(f2)=32 union may be aligned on 8 byte boundaries. Neal's: char: 1 short: 2 int: 4 long: 8 long long: 8 void*: 8 float: 4 double: 8 long double: 16 -- Kind regards, +----+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to access cvs.debian.org with ssh/rsa keys?
Hi Frank! You wrote: > I have set CVS_RSH=ssh, and I try to access the cvs with > > cvs -d :pserver:[EMAIL PROTECTED]:/cvs/tetex login > Logging in to :pserver:[EMAIL PROTECTED]:2401/cvs/tetex > CVS password: > > This doesn't look like ssh authentication. What am I doing wrong (or > what should I have read)? You should use [EMAIL PROTECTED]:/cvs/tetex as cvsroot. The onnections will then be built using ssh instead of pserver. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: How to access cvs.debian.org with ssh/rsa keys?
Hi Frank! You wrote: > I have set CVS_RSH=ssh, and I try to access the cvs with > > cvs -d :pserver:[EMAIL PROTECTED]:/cvs/tetex login > Logging in to :pserver:[EMAIL PROTECTED]:2401/cvs/tetex > CVS password: > > This doesn't look like ssh authentication. What am I doing wrong (or > what should I have read)? You should use [EMAIL PROTECTED]:/cvs/tetex as cvsroot. The onnections will then be built using ssh instead of pserver. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS (3): aap
Hi Cory! You wrote: > A-A-P is an astoundingly powerful replacement for make that keeps the good > ideas, cleans up the syntax and adds important features like Python > scripting. > Upstream is Bram Moolenaar, whom you may know as the author of ViM. It: > * has autoconf/make features > * supports pluggable "tools" for network features such as retrieving build > dependencies from the net with scp or wget or publishing files > * integrates with several flavors of source control systems and offers > facilities for extending it with your own favorite > * can bend bars with the power of its mind. This looks quite useful indeed. If no one else volonteers, I'd be happy to sponsor you. I don't have a lot of time though, so it will probably take a little while (a week or so) before I can check the package. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS (3): aap
Hi Cory! You wrote: > A-A-P is an astoundingly powerful replacement for make that keeps the good > ideas, cleans up the syntax and adds important features like Python > scripting. > Upstream is Bram Moolenaar, whom you may know as the author of ViM. It: > * has autoconf/make features > * supports pluggable "tools" for network features such as retrieving build > dependencies from the net with scp or wget or publishing files > * integrates with several flavors of source control systems and offers > facilities for extending it with your own favorite > * can bend bars with the power of its mind. This looks quite useful indeed. If no one else volonteers, I'd be happy to sponsor you. I don't have a lot of time though, so it will probably take a little while (a week or so) before I can check the package. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: Build-Recommends?
Hi Michel! You wrote: > Build-Depends: libcurl2-dev | curl | wget > might serve as a workaround? I guees he would need something like (Build-Depends: libcurl2-dev) | (Depends: curl | wget) which isn't possible. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: Build-Recommends?
Hi Michel! You wrote: > Build-Depends: libcurl2-dev | curl | wget > might serve as a workaround? I guees he would need something like (Build-Depends: libcurl2-dev) | (Depends: curl | wget) which isn't possible. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to change the applicant email address
Hi Manfred! You wrote: > could someone please tell me what to do to have my Debian email address > changed? Just send a mail to the Frontdesk. -- Kind regards, +----+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: How to change the applicant email address
Hi Manfred! You wrote: > could someone please tell me what to do to have my Debian email address > changed? Just send a mail to the Frontdesk. -- Kind regards, +----+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sponsor for minido
Hi francesco! You wrote: > it is also multi user because profiles are stored in /usr/share so every > system user can access it, while it stores information in a home > subdirectory. User profiles should not be stored in /usr, but probably in /var (if the data changes, that is). -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: sponsor for minido
Hi francesco! You wrote: > it is also multi user because profiles are stored in /usr/share so every > system user can access it, while it stores information in a home > subdirectory. User profiles should not be stored in /usr, but probably in /var (if the data changes, that is). -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What to do if $PACKAGE needs $ACCOUNT to _build_
Hi Marc! You wrote: > On Sun, 8 Jun 2003 15:11:59 -0700, Sean 'Shaleh' Perry > <[EMAIL PROTECTED]> wrote: > >Well, you could do the chown at install time inside the postinst. That > >should > >solve the problem nicely. > > Which is what my package already does, but it does not even build with > the account not present. I am very unsure about handling this. So, fix the build system and send your changes upstream. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: What to do if $PACKAGE needs $ACCOUNT to _build_
Hi Marc! You wrote: > On Sun, 8 Jun 2003 15:11:59 -0700, Sean 'Shaleh' Perry > <[EMAIL PROTECTED]> wrote: > >Well, you could do the chown at install time inside the postinst. That should > >solve the problem nicely. > > Which is what my package already does, but it does not even build with > the account not present. I am very unsure about handling this. So, fix the build system and send your changes upstream. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Querying what packages are installed in postinst
Hi Alan! You wrote: > For the next version of a package which I currently have sponsored in > Debian (mozilla-mozgest) I want to add support for mozilla-firebird > (preliminary packages are avalible from > http://people.debian.org/~eric/debian/i386) and mozilla-snapshot. The > problem is that in order to do this I need to do different things for > each of the browsers in postinst and postrm. Basicaly what I'd like to > know is if theres a nicer way to test if a package is installed than > just testing the existance of files that the package would create if it > was installed? Uhm, I don't think you should do these kinds of tricks anyway. For example, your package wouldn't work correctly if I first install mozilla, then mosgest, and last firebird, because your package's postinst would only do stuff for mozilla. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: Moving packages from "Requested" to "Can't be packaged"
Hi andy.grafham! You wrote: > Is there any way of requesting the BTS to move a package from > "Requested" to "Can't be packaged"? I was investigating packaging > "VisualBoyAdvance" a gameboy advance emulator, but it looks like > license problems will make it impossible to include in debian. AFAIK, there is no automatic way of doing this. What about adding a new tag, something like CBP (cannot be packaged), to the wnpp? -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: Building stable packages
Hi Holger! You wrote: > When I use pbuilder, I get a package that could be installed on woody. The > problem is, that the files are not signed. You can use debsign to sign the package after building. -- Kind regards, +----+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: removing entire directories from original source
Hi Carlo! You wrote: > I have two packages, 'atoms' and 'horae'. horae depends on atoms and > perl-tk and in the original tarball, it contains perl module > subdirectories which generate installed perl modules and man pages which > would overwrite the ones in the perl-tk and atoms packages. > > I can fix the overwrite errors in the deb packages by simply removing the > module subdirectories in horae but I am not sure if that is the proper way > to do it. Sure, anything you don't need or want, you can just remove in debian/tmp (or debian/horae). -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: removing entire directories from original source
Hi Carlo! You wrote: > I have two packages, 'atoms' and 'horae'. horae depends on atoms and > perl-tk and in the original tarball, it contains perl module > subdirectories which generate installed perl modules and man pages which > would overwrite the ones in the perl-tk and atoms packages. > > I can fix the overwrite errors in the deb packages by simply removing the > module subdirectories in horae but I am not sure if that is the proper way > to do it. Sure, anything you don't need or want, you can just remove in debian/tmp (or debian/horae). -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packaging Perl programs
Hi Carlo! You wrote: > Is there a simple way to generate the contents of debian/ for such > programs or is the best thing to do to look at similar package and copy > and modify the control files? IIRC, the debian/ dir is simply copied from /usr/share/debhelper/dh_make -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: Packaging Perl programs
Hi Carlo! You wrote: > Is there a simple way to generate the contents of debian/ for such > programs or is the best thing to do to look at similar package and copy > and modify the control files? IIRC, the debian/ dir is simply copied from /usr/share/debhelper/dh_make -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upstream debian/ dir.
Hi Jonathan! You wrote: > I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been > asked by upstream if I want to maintain the debian/ directory in the > project's CVS. The RPM .spec file is already done this way. Is there any > good reason not to do this? I see very few problems with this, if you do it The Right Way[1]. > It will make things a lot easier for people > pulling running CVS builds. The only drawback I can see is changes in > the packaging between releases leads to a whole new src tarball to > upload to the archive rather than just a new diff, but hopefully this > shouldn't happen too often. That shouldn't be necessary, since you could just run a cvs up on the debian/ dir alone. [1] The Right Way, IMHO, is using tags and branches. For each upstream release, you could have a debian branch, containing only changes to the debian/ dir. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: Upstream debian/ dir.
Hi Jonathan! You wrote: > I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been > asked by upstream if I want to maintain the debian/ directory in the > project's CVS. The RPM .spec file is already done this way. Is there any > good reason not to do this? I see very few problems with this, if you do it The Right Way[1]. > It will make things a lot easier for people > pulling running CVS builds. The only drawback I can see is changes in > the packaging between releases leads to a whole new src tarball to > upload to the archive rather than just a new diff, but hopefully this > shouldn't happen too often. That shouldn't be necessary, since you could just run a cvs up on the debian/ dir alone. [1] The Right Way, IMHO, is using tags and branches. For each upstream release, you could have a debian branch, containing only changes to the debian/ dir. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: need help with bug #178837 (automake)
Hi Frank!
You wrote:
> Makefile.am now says
[...]
> CFLAGS = -Wall -O3 `freetype-config --cflags` ${SDL_CFLAGS}
> ${BUMPREF_CFLAGS} `
> What do I have to change to be able to add -mieee on alpha, preferably
> from debian/rules, or configure ?
If you change the above line in Makefile.am to
| CFLAGS += -Wall -O3 `freetype-config --cflags` ${SDL_CFLAGS}
${BUMPREF_CFLAGS} `
you can set CFLAGS=-mieee in the environment, and it will get
picked up by the Makefile. You could then simply put the Alpha test in
debian/rules.
--
Kind regards,
+--------+
| Bas Zoetekouw | GPG key: 0644fab7 |
|| Fingerprint: c1f5 f24c d514 3fec 8bf6 |
| [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 |
++
Re: need help with bug #178837 (automake)
Hi Frank!
You wrote:
> Makefile.am now says
[...]
> CFLAGS = -Wall -O3 `freetype-config --cflags` ${SDL_CFLAGS} ${BUMPREF_CFLAGS} `
> What do I have to change to be able to add -mieee on alpha, preferably
> from debian/rules, or configure ?
If you change the above line in Makefile.am to
| CFLAGS += -Wall -O3 `freetype-config --cflags` ${SDL_CFLAGS} ${BUMPREF_CFLAGS} `
you can set CFLAGS=-mieee in the environment, and it will get
picked up by the Makefile. You could then simply put the Alpha test in
debian/rules.
--
Kind regards,
+----+
| Bas Zoetekouw | GPG key: 0644fab7 |
|| Fingerprint: c1f5 f24c d514 3fec 8bf6 |
| [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 |
++
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: unITPing
Hi Jonas! You wrote: > Should I just file an RFP bug somehow or what should I do ? Just retitle the existing bug to an RFP. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: unITPing
Hi Jonas! You wrote: > Should I just file an RFP bug somehow or what should I do ? Just retitle the existing bug to an RFP. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to be a great Debian Developer
Hi Russell! You wrote: > One thing you could do is write a script that searches for a man page for > every binary on your system. /usr/bin and /bin binaries deserve man pages in > section 1, /usr/sbin and /sbin binaries deserve man pages in section 8. If > you write a Perl script to search for such man pages you will should find > hundreds of them to be missing on a typical system (there's more than a few > missing from my packages). Then start writing some man pages! There is already such a script, see http://qa.debian.org/man-pages.html -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: How to be a great Debian Developer
Hi Russell! You wrote: > One thing you could do is write a script that searches for a man page for > every binary on your system. /usr/bin and /bin binaries deserve man pages in > section 1, /usr/sbin and /sbin binaries deserve man pages in section 8. If > you write a Perl script to search for such man pages you will should find > hundreds of them to be missing on a typical system (there's more than a few > missing from my packages). Then start writing some man pages! There is already such a script, see http://qa.debian.org/man-pages.html -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: questions on packaging
Hi Tommaso! You wrote: > Should I wait for my application to be approved or look for a sponsor? No, just go ahead and find a sponsor. > Should I report an ITP even if I'm not a Debian Developer? Yes, definately. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: questions on packaging
Hi Tommaso! You wrote: > Should I wait for my application to be approved or look for a sponsor? No, just go ahead and find a sponsor. > Should I report an ITP even if I'm not a Debian Developer? Yes, definately. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: fetchmail on master.debian.org
Hi Andrea! You wrote: > I would prefer to get my e-mail from master.debian.org > using fetchmail (instead of having a forward in the db db.debian.org) > how can I do it? I don't think it is possible atm. Master runs no pop and no imap servers. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: fetchmail on master.debian.org
Hi Andrea! You wrote: > I would prefer to get my e-mail from master.debian.org > using fetchmail (instead of having a forward in the db db.debian.org) > how can I do it? I don't think it is possible atm. Master runs no pop and no imap servers. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Intent To Package (heatload)
Hi Malte! You wrote: > I have build a debian-package and now I'm locking for a sponsor. > From the Package-Description of 'heatload': > Graphical and nummerical ACPI- and CPU-load-monitor applett for X11 > This Gtk utility produces nice looking realtime graphs for the > current CPU-load and some ACPI-values (eg. temperature, battery) of your > Linux machine. It is nice for monitoring the direct relation of > the former to the latter. Please file an ITP bug against the wnpp package, as described on http://www.debian.org/devel/wnpp/ -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: Intent To Package (heatload)
Hi Malte! You wrote: > I have build a debian-package and now I'm locking for a sponsor. > From the Package-Description of 'heatload': > Graphical and nummerical ACPI- and CPU-load-monitor applett for X11 > This Gtk utility produces nice looking realtime graphs for the > current CPU-load and some ACPI-values (eg. temperature, battery) of your > Linux machine. It is nice for monitoring the direct relation of > the former to the latter. Please file an ITP bug against the wnpp package, as described on http://www.debian.org/devel/wnpp/ -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Which compiler
Hi Bob! You wrote: > For the 1386 architecture, sid has gcc 2:2.95.4-17 and gcc-3.0 > 1:3.0.4-13. Which compiler should be used for an Architecture: any > package? The default one for the architecture in question. > If the answer is gcc-3.0, should that be included in the > build-depends? No, and neither should any other build-essential packages be included in the build-depends. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: Which compiler
Hi Bob! You wrote: > For the 1386 architecture, sid has gcc 2:2.95.4-17 and gcc-3.0 > 1:3.0.4-13. Which compiler should be used for an Architecture: any > package? The default one for the architecture in question. > If the answer is gcc-3.0, should that be included in the > build-depends? No, and neither should any other build-essential packages be included in the build-depends. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: C++ help please
Hi Allen! You wrote: > I hope i am not trobleing you by askin for your help. > i was asked to do this, and i have no idea how its > done, i dont know c++ at all and cant get out of doing > this, i was wondering if any one can help me. I think you should do your own homework. -- Kind regards, +----+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: C++ help please
Hi Allen! You wrote: > I hope i am not trobleing you by askin for your help. > i was asked to do this, and i have no idea how its > done, i dont know c++ at all and cant get out of doing > this, i was wondering if any one can help me. I think you should do your own homework. -- Kind regards, +----+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to force porters to rebuild a package
Hi Sven! You wrote: > > Sorry, I did not make myself clear: I did not upload a new > > package -- I want to trigger a new build attempt for an old > > package of mine now that debhelper has been fixed. > > The autobuilder retry old packages that failed on a regular basis, just > wait some time for them to do it. Some will try daily, other weekly and > other will retry when they have time for it. > > You could wait a week or so, and if the situation doesn't improve, > contact the autobuilder maintainer. > > Alternatively, you could login on a debian paroject machine, and build > the program yourself. Or just upload a new version. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: How to force porters to rebuild a package
Hi Sven! You wrote: > > Sorry, I did not make myself clear: I did not upload a new > > package -- I want to trigger a new build attempt for an old > > package of mine now that debhelper has been fixed. > > The autobuilder retry old packages that failed on a regular basis, just > wait some time for them to do it. Some will try daily, other weekly and > other will retry when they have time for it. > > You could wait a week or so, and if the situation doesn't improve, > contact the autobuilder maintainer. > > Alternatively, you could login on a debian paroject machine, and build > the program yourself. Or just upload a new version. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to force porters to rebuild a package
Hi Marco! You wrote: > How do I force a rebuild on buildd? One of my package could not > be built due to a bug in debhelper which is now solved. Two of > the architectures have already built the package successfully now > that the new version is available; can I trigger the other > architectures to try a new build as well? If you uploaded a new package, the buildds will automagically build it. I could take some time, though. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: How to force porters to rebuild a package
Hi Marco! You wrote: > How do I force a rebuild on buildd? One of my package could not > be built due to a bug in debhelper which is now solved. Two of > the architectures have already built the package successfully now > that the new version is available; can I trigger the other > architectures to try a new build as well? If you uploaded a new package, the buildds will automagically build it. I could take some time, though. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: stripping binaries...must we?
Hi Drew! You wrote: > Why does policy ask us to strip binaries anyway? Is it merely to reduce > storage and bandwidth costs? Yes, afaik this is the only reason. > Could someone please clarify if it's appropriate to respect upstream's > wishes to leave the symbols in? Sure. It's only a "should" in policy, not a "must", so it's ok not to strip. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++
Re: stripping binaries...must we?
Hi Drew! You wrote: > Why does policy ask us to strip binaries anyway? Is it merely to reduce > storage and bandwidth costs? Yes, afaik this is the only reason. > Could someone please clarify if it's appropriate to respect upstream's > wishes to leave the symbols in? Sure. It's only a "should" in policy, not a "must", so it's ok not to strip. -- Kind regards, +--------+ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: building packages on unstable for stable
Hi Holger! You wrote: Please be aware that your mail was tagged as spam by spamassassin: > SPAM: Start SpamAssassin results > SPAM: 5.10 hits, 4.6 required; > SPAM: * 0.6 -- BODY: Spam phrases score is 00 to 01 (low) > SPAM: * 4.5 -- RBL: Received via a relay in bl.spamcop.net > SPAM: [RBL check: found 214.224.20.195.bl.spamcop.net.] > SPAM: > SPAM: End of SpamAssassin results > > I want to build a package on my computer for several other hosts at work. > I use unstable but on some other hosts there is stable. My problem is: > Building packages with debhelper causes a dependency (expanded from > shlibs:Depends) of the package libc6 at least at the version used on my > unstable. This package cannot be installed on stable, because the > libc6/stable is too old. > > Does anyone know how to build this package with other dependencies? > > Greetings > Holger > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Kind regards, +---+ | Bas Zoetekouw | Het belangrijkste gereedschap| || van de theoretisch fysicus | | [EMAIL PROTECTED] | is de prullenbak.| | [EMAIL PROTECTED] | J.J. Lodder| +---+
Re: building packages on unstable for stable
Hi Holger! You wrote: Please be aware that your mail was tagged as spam by spamassassin: > SPAM: Start SpamAssassin results > SPAM: 5.10 hits, 4.6 required; > SPAM: * 0.6 -- BODY: Spam phrases score is 00 to 01 (low) > SPAM: * 4.5 -- RBL: Received via a relay in bl.spamcop.net > SPAM: [RBL check: found 214.224.20.195.bl.spamcop.net.] > SPAM: > SPAM: End of SpamAssassin results > > I want to build a package on my computer for several other hosts at work. > I use unstable but on some other hosts there is stable. My problem is: > Building packages with debhelper causes a dependency (expanded from > shlibs:Depends) of the package libc6 at least at the version used on my > unstable. This package cannot be installed on stable, because the > libc6/stable is too old. > > Does anyone know how to build this package with other dependencies? > > Greetings > Holger > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Kind regards, +---+ | Bas Zoetekouw | Het belangrijkste gereedschap| || van de theoretisch fysicus | | [EMAIL PROTECTED] | is de prullenbak.| | [EMAIL PROTECTED] | J.J. Lodder| +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sponsor request: quelcom
Hi Devin! You wrote: > I've packaged David Many'e's "Quelcom" suite of MP3 and WAV editing and > utility apps; I'm interested in finding a sponsor for them. I'd be happy to sponsor you, if you are in the NM queue (or plan to enter soon). The copyright of the program is a bit unclear though. There is no mention of copyright or license at all, except for a copy of the GPL being in the upstream source. There is no mention that the software is actually licensed under the GPL. -- Kind regards, +-------+ | Bas Zoetekouw | Het belangrijkste gereedschap| || van de theoretisch fysicus | | [EMAIL PROTECTED] | is de prullenbak.| | [EMAIL PROTECTED] | J.J. Lodder| +---+
Re: Sponsor request: quelcom
Hi Devin! You wrote: > I've packaged David Many'e's "Quelcom" suite of MP3 and WAV editing and > utility apps; I'm interested in finding a sponsor for them. I'd be happy to sponsor you, if you are in the NM queue (or plan to enter soon). The copyright of the program is a bit unclear though. There is no mention of copyright or license at all, except for a copy of the GPL being in the upstream source. There is no mention that the software is actually licensed under the GPL. -- Kind regards, +-------+ | Bas Zoetekouw | Het belangrijkste gereedschap| || van de theoretisch fysicus | | [EMAIL PROTECTED] | is de prullenbak.| | [EMAIL PROTECTED] | J.J. Lodder| +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mldonkey needs sponsor
Hi Moritz! You wrote: > With the release of a GPLed Windows Edonkey client (emule) and its > reveal of the protocol mldonkey's upstream decided to do the same. > I don't see any obstacle wrt mldonkey's level of freedom now. Great! This really is good news. -- Kind regards, +-----------+ | Bas Zoetekouw | Het belangrijkste gereedschap| || van de theoretisch fysicus | | [EMAIL PROTECTED] | is de prullenbak.| | [EMAIL PROTECTED] | J.J. Lodder| +---+
Re: mldonkey needs sponsor
Hi Moritz! You wrote: > With the release of a GPLed Windows Edonkey client (emule) and its > reveal of the protocol mldonkey's upstream decided to do the same. > I don't see any obstacle wrt mldonkey's level of freedom now. Great! This really is good news. -- Kind regards, +-----------+ | Bas Zoetekouw | Het belangrijkste gereedschap| || van de theoretisch fysicus | | [EMAIL PROTECTED] | is de prullenbak.| | [EMAIL PROTECTED] | J.J. Lodder| +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: config.* in the diff?
Hi Ross!
You wrote:
> clean:
> dh_testdir
> dh_testroot
> rm -f build-stamp
> -$(MAKE) distclean
> -test -r /usr/share/misc/config.sub && \
> cp -f /usr/share/misc/config.sub config.sub
> -test -r /usr/share/misc/config.guess && \
> cp -f /usr/share/misc/config.guess config.guess
> dh_clean
This doesn't really make much sense. In my packages, I copy the new
config.{sub,guess} over the old ones in one of the build targets,
and put a backup of the original ones back in the clean target. That
way, the packages always use an up-to-date config.{sub,guess}, but the
diff isn't clobbered in any way because of this.
> For the moment I commented these the cp lines out, and restored the
> original files from the tarball. However, what is the "proper" solution
> to this?
The best solution is of course to get upstream include up-to-date
config.{sub,guess}. But just letting the clean target do what it's
supposed to do (i.e. clean the source tree).
--
Kind regards,
+---+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] | Pablo Picasso |
+---+
Re: config.* in the diff?
Hi Ross!
You wrote:
> clean:
> dh_testdir
> dh_testroot
> rm -f build-stamp
> -$(MAKE) distclean
> -test -r /usr/share/misc/config.sub && \
> cp -f /usr/share/misc/config.sub config.sub
> -test -r /usr/share/misc/config.guess && \
> cp -f /usr/share/misc/config.guess config.guess
> dh_clean
This doesn't really make much sense. In my packages, I copy the new
config.{sub,guess} over the old ones in one of the build targets,
and put a backup of the original ones back in the clean target. That
way, the packages always use an up-to-date config.{sub,guess}, but the
diff isn't clobbered in any way because of this.
> For the moment I commented these the cp lines out, and restored the
> original files from the tarball. However, what is the "proper" solution
> to this?
The best solution is of course to get upstream include up-to-date
config.{sub,guess}. But just letting the clean target do what it's
supposed to do (i.e. clean the source tree).
--
Kind regards,
+---+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] | Pablo Picasso |
+---+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new debs, itp process
Hi Michael! You wrote: > So, I looked at the wnpp list and found limewire, which is a good fit > for me because I've worked on gnutella a lot. I have a deb package > made for it, which can be found on my website, hyperpoem.net, in the > right hand side bar. IIRC, limewire was already ITPed a few days ago. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new debs, itp process
Hi Michael! You wrote: > So, I looked at the wnpp list and found limewire, which is a good fit > for me because I've worked on gnutella a lot. I have a deb package > made for it, which can be found on my website, hyperpoem.net, in the > right hand side bar. IIRC, limewire was already ITPed a few days ago. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sponsor request for cernlib
Hi Kevin! You wrote: > I know Cernlib is hardly a suitable project for someone who hopes to > become a new Debian developer; it includes shared libraries, data files, > and all sorts of good stuff. (Even getting it to compile with shared > instead of static libraries took a good deal of work.) But what can I say > -- I needed it :) So if there are any physicists who would be interested > in sponsoring me for these packages, please take a look. I'd like to see this in Debian, so I'll sponsor you. I'll take a look at your packages later this week. It would be nice if, in the mean time, you could get your key signed. I think there are a lot of develoepr sin your area, so it shouldn't be much of a problem to arrange a meeting. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ pgptWrXQLwe9U.pgp Description: PGP signature
Re: Sponsor request for cernlib
Hi Kevin! You wrote: > I know Cernlib is hardly a suitable project for someone who hopes to > become a new Debian developer; it includes shared libraries, data files, > and all sorts of good stuff. (Even getting it to compile with shared > instead of static libraries took a good deal of work.) But what can I say > -- I needed it :) So if there are any physicists who would be interested > in sponsoring me for these packages, please take a look. I'd like to see this in Debian, so I'll sponsor you. I'll take a look at your packages later this week. It would be nice if, in the mean time, you could get your key signed. I think there are a lot of develoepr sin your area, so it shouldn't be much of a problem to arrange a meeting. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ msg06429/pgp0.pgp Description: PGP signature
Re: Unidentified subject!
Hi Wei! (Note that debian-project is not the right mailinglist for this subject. I've changed the Cc to debian-mentors, where it is more on-topic). You wrote: >My name is Wei Gao, I am an international student > at an American University. I took a course on Network > TCP/IP this spring, and I used the linux for the first > time in my life. I really liked it, it's very robust, > and efficient. I was just wondering if you can let me > become an volunteer for the debian project and work on > some projects. Well, of course. Debian is actually run by volunteers only, and anyone is welcomed to join the project. > I am totally free this summer and I > know how to program in C,C++, java, and I am also an > computer science major. My main problem like other > inernational students is I don't have much working > experience. Therefore, if you have to let me show you > an resume, I can't show it because I don't working > experience. To join Debian, there's no need for a resume. We have a New-Maintainer process, in which you are appointed a so-called Application Manager. He will check your knowledge of the Debian system and policy, as well as your packaging and/or programming skills. More information about how to join and what to do before you sign up, can be found at http://www.debian.org/devel/join/newmaint and http://www.debian.org/devel/join. The most important thing you should keep in mind, is that you should create a GPG key pair, and that you should get your key signed by a Debian developer. In order for a key to be signed, you must meet in person with the developer, so you should find a developer that lives near you. Also, it is advisable to read the Debian Policy Manual, the developers reference and the New Maintainer's Guide before you sign up. All of those can be found at http://www.debian.org/devel. it would be usefull to subscribe yourself to the debian-devel and debian-mentors mailinglists, too, so you might get an idea of what is being done in Debian. Information on how to subscribe and on what mailing lists are available, can be found at http://lists.debian.org/. I hope you find this information useful, and I hope you decide to join Debian. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ pgpx1muLqxp47.pgp Description: PGP signature
Re: Unidentified subject!
Hi Wei! (Note that debian-project is not the right mailinglist for this subject. I've changed the Cc to debian-mentors, where it is more on-topic). You wrote: >My name is Wei Gao, I am an international student > at an American University. I took a course on Network > TCP/IP this spring, and I used the linux for the first > time in my life. I really liked it, it's very robust, > and efficient. I was just wondering if you can let me > become an volunteer for the debian project and work on > some projects. Well, of course. Debian is actually run by volunteers only, and anyone is welcomed to join the project. > I am totally free this summer and I > know how to program in C,C++, java, and I am also an > computer science major. My main problem like other > inernational students is I don't have much working > experience. Therefore, if you have to let me show you > an resume, I can't show it because I don't working > experience. To join Debian, there's no need for a resume. We have a New-Maintainer process, in which you are appointed a so-called Application Manager. He will check your knowledge of the Debian system and policy, as well as your packaging and/or programming skills. More information about how to join and what to do before you sign up, can be found at http://www.debian.org/devel/join/newmaint and http://www.debian.org/devel/join. The most important thing you should keep in mind, is that you should create a GPG key pair, and that you should get your key signed by a Debian developer. In order for a key to be signed, you must meet in person with the developer, so you should find a developer that lives near you. Also, it is advisable to read the Debian Policy Manual, the developers reference and the New Maintainer's Guide before you sign up. All of those can be found at http://www.debian.org/devel. it would be usefull to subscribe yourself to the debian-devel and debian-mentors mailinglists, too, so you might get an idea of what is being done in Debian. Information on how to subscribe and on what mailing lists are available, can be found at http://lists.debian.org/. I hope you find this information useful, and I hope you decide to join Debian. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ msg06402/pgp0.pgp Description: PGP signature
Re: fixing permissions
Hi Magnus! You wrote: > extracting original source code > patching original code using ketm_0.0.6-1.diff.gz > trying to run ./configure > /bin/sh: ./configure: /bin/sh: bad interpreter: Permission denied > > I could fix the problem by manually by adding a chmod +x ./configure > somewhere in the rules section. But manually adding a diff seems somewhat > clumsy. The easiest way is probably just running "sh ./configure" from debian/rules instead of just "./configure". -- Kind regards, +-----------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: fixing permissions
Hi Magnus! You wrote: > extracting original source code > patching original code using ketm_0.0.6-1.diff.gz > trying to run ./configure > /bin/sh: ./configure: /bin/sh: bad interpreter: Permission denied > > I could fix the problem by manually by adding a chmod +x ./configure > somewhere in the rules section. But manually adding a diff seems somewhat > clumsy. The easiest way is probably just running "sh ./configure" from debian/rules instead of just "./configure". -- Kind regards, +-----------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dupload with openssh
Hi Jérôme! You wrote: > > [Orthogonally, ] Consider using anonymous ftp instead; both ftp-master > > and non-US have anonymous-ftp upload queues. > > Does this mean that some anonymous people are allowed to feed our > upload queues with some undesirable trash? Yes, but I guess nothing is processed without checking the signature. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: dupload with openssh
Hi Jérôme! You wrote: > > [Orthogonally, ] Consider using anonymous ftp instead; both ftp-master > > and non-US have anonymous-ftp upload queues. > > Does this mean that some anonymous people are allowed to feed our > upload queues with some undesirable trash? Yes, but I guess nothing is processed without checking the signature. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libc6 on IA-64
Hi debian-mentors! You wrote: > Hi Lukasz! > > You wrote: > > > libc6 does not exist on alpha, ia64 (libc6.1) or hurd-i386 (libc0.2). > > [...] > > | ** Using build dependencies supplied by package: > > > > | Build-Depends: debhelper, libc6 (>= 2.2.3-7), libsdl-mixer1.2-dev > > (>=1.2.0), libsdl1.2-dev > > > > [...] > > Is there an "universal library name" I should use instead of libc6? > > You should include libc in your build-dependencies precisely for this ^^ Oops, I meant shouldn't, of course. > reason. There's a list somewhere on www.debian.org iwth the package you > may/must assume to be installed on a system when building packages. > > -- > Kind regards, > +---+ > | Bas Zoetekouw | Si l'on sait exactement ce | > || que l'on va faire, a quoi| > | [EMAIL PROTECTED] | bon le faire?| > |[EMAIL PROTECTED] | Pablo Picasso | > +---+ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: libc6 on IA-64
Hi debian-mentors! You wrote: > Hi Lukasz! > > You wrote: > > > libc6 does not exist on alpha, ia64 (libc6.1) or hurd-i386 (libc0.2). > > [...] > > | ** Using build dependencies supplied by package: > > > > | Build-Depends: debhelper, libc6 (>= 2.2.3-7), libsdl-mixer1.2-dev > > (>=1.2.0), libsdl1.2-dev > > > > [...] > > Is there an "universal library name" I should use instead of libc6? > > You should include libc in your build-dependencies precisely for this ^^ Oops, I meant shouldn't, of course. > reason. There's a list somewhere on www.debian.org iwth the package you > may/must assume to be installed on a system when building packages. > > -- > Kind regards, > +---+ > | Bas Zoetekouw | Si l'on sait exactement ce | > || que l'on va faire, a quoi| > | [EMAIL PROTECTED] | bon le faire?| > |[EMAIL PROTECTED] | Pablo Picasso | > +---+ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libc6 on IA-64
Hi Lukasz! You wrote: > libc6 does not exist on alpha, ia64 (libc6.1) or hurd-i386 (libc0.2). > [...] > | ** Using build dependencies supplied by package: > > | Build-Depends: debhelper, libc6 (>= 2.2.3-7), libsdl-mixer1.2-dev > (>=1.2.0), libsdl1.2-dev > > [...] > Is there an "universal library name" I should use instead of libc6? You should include libc in your build-dependencies precisely for this reason. There's a list somewhere on www.debian.org iwth the package you may/must assume to be installed on a system when building packages. -- Kind regards, +-----------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: libc6 on IA-64
Hi Lukasz! You wrote: > libc6 does not exist on alpha, ia64 (libc6.1) or hurd-i386 (libc0.2). > [...] > | ** Using build dependencies supplied by package: > > | Build-Depends: debhelper, libc6 (>= 2.2.3-7), libsdl-mixer1.2-dev > (>=1.2.0), libsdl1.2-dev > > [...] > Is there an "universal library name" I should use instead of libc6? You should include libc in your build-dependencies precisely for this reason. There's a list somewhere on www.debian.org iwth the package you may/must assume to be installed on a system when building packages. -- Kind regards, +-----------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lintian goes wild?
Hi Christian! You wrote: > Operator or semicolon missing before &supported at (eval 115) line 1. > Ambiguous use of & resolved as operator & at (eval 115) line 1. > Unquoted string "supported" may clash with future reserved word at (eval > 112) line 1. Looks like a bug in lintian to me. Have you tried contacting the lintian maintainers? -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: lintian goes wild?
Hi Christian! You wrote: > Operator or semicolon missing before &supported at (eval 115) line 1. > Ambiguous use of & resolved as operator & at (eval 115) line 1. > Unquoted string "supported" may clash with future reserved word at (eval > 112) line 1. Looks like a bug in lintian to me. Have you tried contacting the lintian maintainers? -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question on a licence
Hi Noel! You wrote: > But I don't know if the licence is free for the Debian Free Software > Guidelines ( http://www.de.debian.org/social_contract.html#guidelines ). > * Permission is granted to anyone to use this software for any purpose on > * any computer system, and to alter it and redistribute it freely,subject > * to the following restrictions: > * 1. The author and the University of Manitoba are not responsible > *for the consequences of use of this software, no matter how awful, > *even if they arise from flaws in it. > * 2. The origin of this software must not be misrepresented, either by > *explicit claim or by omission. Since few users ever read sources, > *credits must appear in the documentation. > * 3. Altered versions must be plainly marked as such, and must not be > *misrepresented as being the original software. Since few users > *ever read sources, credits must appear in the documentation. > * 4. This notice may not be removed or altered. Looks like a BSD-ish licence to me, so you should be ok. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: question on a licence
Hi Noel! You wrote: > But I don't know if the licence is free for the Debian Free Software > Guidelines ( http://www.de.debian.org/social_contract.html#guidelines ). > * Permission is granted to anyone to use this software for any purpose on > * any computer system, and to alter it and redistribute it freely,subject > * to the following restrictions: > * 1. The author and the University of Manitoba are not responsible > *for the consequences of use of this software, no matter how awful, > *even if they arise from flaws in it. > * 2. The origin of this software must not be misrepresented, either by > *explicit claim or by omission. Since few users ever read sources, > *credits must appear in the documentation. > * 3. Altered versions must be plainly marked as such, and must not be > *misrepresented as being the original software. Since few users > *ever read sources, credits must appear in the documentation. > * 4. This notice may not be removed or altered. Looks like a BSD-ish licence to me, so you should be ok. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Making package.
Hi Tommy! You wrote: > Hi guys. I'm trying to put together a package that contains a single > binary program and have followed all the steps in the New Maintainor's > guide and have managed to form the binary package. For some reason when I > do: > dpkg-buildpackage -rfakeroot it compiles fine and asks me for my gpg > password which works fine, but for some reason it says that source package > will not be included. You probably don't have a ../package_version.orig.tar.gz file. > One thing that I notice when I run lintian -i it tells me that the program > should have a man page. What do I do if this program didn't shop with > one. This program has its documentation in different files. The best thing is to write your own man page. It's not that hard, and since the package does have documentation, it's probably just cut'n'past work. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: Making package.
Hi Tommy! You wrote: > Hi guys. I'm trying to put together a package that contains a single > binary program and have followed all the steps in the New Maintainor's > guide and have managed to form the binary package. For some reason when I > do: > dpkg-buildpackage -rfakeroot it compiles fine and asks me for my gpg > password which works fine, but for some reason it says that source package > will not be included. You probably don't have a ../package_version.orig.tar.gz file. > One thing that I notice when I run lintian -i it tells me that the program > should have a man page. What do I do if this program didn't shop with > one. This program has its documentation in different files. The best thing is to write your own man page. It's not that hard, and since the package does have documentation, it's probably just cut'n'past work. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: variable path names in manpages
Hi Manfred! You wrote: > I'm currently writing a manpage which is to be used in a Debian package, > but not exclusively. To be most flexible I want to use variables for path > names that are expanded at build time. Is there any standard or > recommended way implement this? Well, you could just run sed over the man page before installing it. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: variable path names in manpages
Hi Manfred! You wrote: > I'm currently writing a manpage which is to be used in a Debian package, > but not exclusively. To be most flexible I want to use variables for path > names that are expanded at build time. Is there any standard or > recommended way implement this? Well, you could just run sed over the man page before installing it. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: diversions
Hi Wolfgang! You wrote: > In my case the lpr provided by gfax is a wrapper to provide the lpr > -Pfax command line. Should I contact both the LPRng and BSD lpr > managers ? Also, I would like to know why it should be done, so that I > can understand further. Wouldn't it be a lot nicer to just add a "fax" entry to /etc/printcap? I know that at least lprng can handle printing to pipes (I use it to `print' mp3's to mpg123). -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: diversions
Hi Wolfgang! You wrote: > In my case the lpr provided by gfax is a wrapper to provide the lpr > -Pfax command line. Should I contact both the LPRng and BSD lpr > managers ? Also, I would like to know why it should be done, so that I > can understand further. Wouldn't it be a lot nicer to just add a "fax" entry to /etc/printcap? I know that at least lprng can handle printing to pipes (I use it to `print' mp3's to mpg123). -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Non-free question
Hi Peter! You wrote: > > I'm considering packaging BET, a 128-bit blowfish-encrypted talk daemon. > > However, it relies on a non-DFSG complian library, even though the program > > itself is GPL. > > The license needs to have an exemption for the GPL-incompatible > library it uses. Indeed. If there's no such exception, we cannot distribute it (just like KDE in the past). -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: Non-free question
Hi Peter! You wrote: > > I'm considering packaging BET, a 128-bit blowfish-encrypted talk daemon. > > However, it relies on a non-DFSG complian library, even though the program > > itself is GPL. > > The license needs to have an exemption for the GPL-incompatible > library it uses. Indeed. If there's no such exception, we cannot distribute it (just like KDE in the past). -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gpg keyrings.
Hi Timshel!
You wrote:
> I note that the debian-keyring package is horribly outdated
> (2000.08.30), how often is it updated? I've reverted to downloading the
> keyring manually from auric.d.o ...
The sid package should be up to date, I think. Since my system still
runs potato however, I get new keyrings from auric every 2 days
automatically:
0 6 */2 * * cd $HOME/.gnupg; scp -q -C
auric.debian.org:/org/keyring.debian.org/keyrings/debian-keyring.{gpg,pgp} .
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] | Pablo Picasso |
+---+
Re: gpg keyrings.
Hi Timshel!
You wrote:
> I note that the debian-keyring package is horribly outdated
> (2000.08.30), how often is it updated? I've reverted to downloading the
> keyring manually from auric.d.o ...
The sid package should be up to date, I think. Since my system still
runs potato however, I get new keyrings from auric every 2 days
automatically:
0 6 */2 * * cd $HOME/.gnupg; scp -q -C
auric.debian.org:/org/keyring.debian.org/keyrings/debian-keyring.{gpg,pgp} .
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] | Pablo Picasso |
+---+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Package Ready, Need Sponsor
Hi Jimmy! You wrote: > Could someone from debian-mentors please take a look at my package and sponsor > it for inclusion in the distribution? If it gets in, I will seek to become an > official Debian developer so I can handle this myself. I have fixed all the > errors and warnings given by lintian, so that now lintian gives no messages. I'll sponsor you. I'll take a look at the package tonight. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ PGP signature
Re: Debian Package Ready, Need Sponsor
Hi Jimmy! You wrote: > Could someone from debian-mentors please take a look at my package and sponsor > it for inclusion in the distribution? If it gets in, I will seek to become an > official Debian developer so I can handle this myself. I have fixed all the > errors and warnings given by lintian, so that now lintian gives no messages. I'll sponsor you. I'll take a look at the package tonight. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ pgplcQDuSdefH.pgp Description: PGP signature
Re: Help for an ITA
Hi David! You wrote: > Hello everybody. I want to send a mail to [EMAIL PROTECTED] for doing a > retitle > of a RFA bug. But the new title is too long and my mail client wraps the line > and puts the final piece in a new line: Weel, the easiest way tyo do this is probably: echo "retitle etc" | mail [EMAIL PROTECTED] -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: Help for an ITA
Hi David! You wrote: > Hello everybody. I want to send a mail to [EMAIL PROTECTED] for doing a retitle > of a RFA bug. But the new title is too long and my mail client wraps the line > and puts the final piece in a new line: Weel, the easiest way tyo do this is probably: echo "retitle etc" | mail [EMAIL PROTECTED] -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: (long reply) Re: NM saga (all of it - Joey, this means you)
Hi Daniel! You wrote: > I think Craig (Sanders) summed it up beautifully in his email where he said > that the DAM was a servant-type job, not a master. How would you like it if > a submarine captain just vanished on holiday without telling anyone because > he couldn't be stuffed going on his next mission? The president? You get the > picture. Joey, you've been given responsibility. You've been trusted. Your > job as DAM is to take NM's, look at the AM's recommendations, and, > eventually, assign accounts. > > See those last 2 words? ASSIGN. ACCOUNTS. This isn't happening! And, if you > ARE on holiday, why did you not see fit to tell anyone? (I know I'm not on > -private, but several of those who are have verified he hasn't said a word). You evidently don't know what you're talking about. 1) James did post on -private about this 2) The DAM is the one who DECIDES whether you are accepted as a developer or not. He is not just someone who creates accounts. As a delegate of the project leader (e.g. Wichert), he may "may make certain decisions which the Leader may not make directly, including approving or expelling Developers or designating people as Developers who do not maintain packages. " (Debian Constitution). > Enter Debian, 2001. Democracy. (Yeah, my arse). NMs aren't allowed to speak > a non-positive word against so-called "senior developers" because they're > just little, unimportant NMs. They _are_ allowed to speak, of course. They are not allowed to flame. > Nor are they allowed emails. Or machine > access. There has been exactly one person who said this. Please don't generalise. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: (long reply) Re: NM saga (all of it - Joey, this means you)
Hi Daniel! You wrote: > I think Craig (Sanders) summed it up beautifully in his email where he said > that the DAM was a servant-type job, not a master. How would you like it if > a submarine captain just vanished on holiday without telling anyone because > he couldn't be stuffed going on his next mission? The president? You get the > picture. Joey, you've been given responsibility. You've been trusted. Your > job as DAM is to take NM's, look at the AM's recommendations, and, > eventually, assign accounts. > > See those last 2 words? ASSIGN. ACCOUNTS. This isn't happening! And, if you > ARE on holiday, why did you not see fit to tell anyone? (I know I'm not on > -private, but several of those who are have verified he hasn't said a word). You evidently don't know what you're talking about. 1) James did post on -private about this 2) The DAM is the one who DECIDES whether you are accepted as a developer or not. He is not just someone who creates accounts. As a delegate of the project leader (e.g. Wichert), he may "may make certain decisions which the Leader may not make directly, including approving or expelling Developers or designating people as Developers who do not maintain packages. " (Debian Constitution). > Enter Debian, 2001. Democracy. (Yeah, my arse). NMs aren't allowed to speak > a non-positive word against so-called "senior developers" because they're > just little, unimportant NMs. They _are_ allowed to speak, of course. They are not allowed to flame. > Nor are they allowed emails. Or machine > access. There has been exactly one person who said this. Please don't generalise. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: testing vs. unstable
Hi peter! You wrote: > Well, what I'm curious about is why only 1.2 is in testing, 1.4 was in > woody since a couple of months before testing was introduced. I was wondering how this works. Suppose a package foo version 1.0-1 is in sid (for ar archs) without rc bugs for 13 days and on the 13th day a package 1.0-2 is uploaded to sid. Will then still 1.0-1 go into woody the next day, or won't 1.0-1 be considered now that 1.0-2 is available? Furthermore, I wonder what - out of date on alpha: freesci (from 0.3.0.cvs2914-2) - there are up to date bins in alpha also means. Does it mean that the version in sid is newer than the version in woody (first line) and that there are bins available for alpha to go into woody (second line)? If that is true, then why isn't my package (freesci) considered for woody? the update_excuses say: freesci 0.3.0.cvs20001212-1 (new) (low) - Maintainer: Bas Zoetekouw <[EMAIL PROTECTED]> - freesci is 21 days out of date! - out of date on alpha: freesci (from 0.3.0.cvs2914-2) - there are up to date bins in alpha also - out of date on arm: freesci (from 0.3.0.cvs2914-2) - there are up to date bins in arm also - out of date on powerpc: freesci (from 0.3.0-1) - there are up to date bins in powerpc also - out of date on sparc: freesci (from 0.3.0-1) - there are up to date bins in sparc also - not considered -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: testing vs. unstable
Hi peter! You wrote: > Well, what I'm curious about is why only 1.2 is in testing, 1.4 was in > woody since a couple of months before testing was introduced. I was wondering how this works. Suppose a package foo version 1.0-1 is in sid (for ar archs) without rc bugs for 13 days and on the 13th day a package 1.0-2 is uploaded to sid. Will then still 1.0-1 go into woody the next day, or won't 1.0-1 be considered now that 1.0-2 is available? Furthermore, I wonder what - out of date on alpha: freesci (from 0.3.0.cvs2914-2) - there are up to date bins in alpha also means. Does it mean that the version in sid is newer than the version in woody (first line) and that there are bins available for alpha to go into woody (second line)? If that is true, then why isn't my package (freesci) considered for woody? the update_excuses say: freesci 0.3.0.cvs20001212-1 (new) (low) - Maintainer: Bas Zoetekouw <[EMAIL PROTECTED]> - freesci is 21 days out of date! - out of date on alpha: freesci (from 0.3.0.cvs2914-2) - there are up to date bins in alpha also - out of date on arm: freesci (from 0.3.0.cvs2914-2) - there are up to date bins in arm also - out of date on powerpc: freesci (from 0.3.0-1) - there are up to date bins in powerpc also - out of date on sparc: freesci (from 0.3.0-1) - there are up to date bins in sparc also - not considered -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: modernising old packages
Hi Drew! You wrote: > What is the appropriate way of bringing meschach into the 21st Century? > Are there any tools for handling this, or do the changes need to be made > manually? You'll have to do it manually. The file /usr/share/doc/debian-policy/upgrading-checklist.text.gz contains all chanes between subsequent policy versions. Using this file, you can easily figure out what exacly you'll have to change. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: modernising old packages
Hi Drew! You wrote: > What is the appropriate way of bringing meschach into the 21st Century? > Are there any tools for handling this, or do the changes need to be made > manually? You'll have to do it manually. The file /usr/share/doc/debian-policy/upgrading-checklist.text.gz contains all chanes between subsequent policy versions. Using this file, you can easily figure out what exacly you'll have to change. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: seperate dependencies for architectures
Hi Goswin!
You wrote:
> You can set whatever depends during build, just like the
> ${shlibs:Depends} does.
Ah, that's a solution that I didn't think about. Thanks!
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] | Pablo Picasso |
+---+
Re: seperate dependencies for architectures
Hi Goswin!
You wrote:
> You can set whatever depends during build, just like the
> ${shlibs:Depends} does.
Ah, that's a solution that I didn't think about. Thanks!
--
Kind regards,
+-------+
| Bas Zoetekouw | Si l'on sait exactement ce |
|| que l'on va faire, a quoi|
| [EMAIL PROTECTED] | bon le faire?|
|[EMAIL PROTECTED] | Pablo Picasso |
+---+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: seperate dependencies for architectures
Hi Goswin! You wrote: > Yes its possible and its covered. Try the web pages, I saw it there > yesterday. You are mistaken. It is only desribed for build time relationships (Build-Depends, etc). And no, the same procedure doesn't work for an ordinary Depends relation. -- Kind regards, +-------+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
