Re: Debhelper files w/ meta values

2002-10-18 Thread Junichi Uekawa
On Fri, 18 Oct 2002 12:29:34 -0600 "Joel Baker" <[EMAIL PROTECTED]> wrote: > > You can use variables in debian/rules all right. > > Er. Because it's helpful? Being able to do dh_installdirs, dh_installlinks, > dh_install (etc) and have the lists in sane files of only that is far > easier to manag

Re: How to force porters to rebuild a package

2002-10-18 Thread Drew Parsons
On Thu, Oct 17, 2002 at 11:05:59PM +0200, Stefan Schwandter wrote: > Drew Parsons wrote: > > > And more to the point [ ;) ], how do I force the autobuilder maintainers to > > actually upload my package once it has been autobuilt? > > > The s390 version of xprint-xprintorg has been built for a who

Looking for package sponsor: zope-fle

2002-10-18 Thread Tarmo Toikkanen
Hi all, I'm one of the developers of Fle3, which is a learning environment implemented as a Zope product. We already package the releases in tarballs and debs, and would like to see the software in the Debian archives. Fle3 is GPL'd. The package itself is really simple, so we just need a sponsor

Re: Debhelper files w/ meta values

2002-10-18 Thread Joel Baker
On Fri, Oct 18, 2002 at 05:15:11PM +0900, Junichi Uekawa wrote: > On Thu, 17 Oct 2002 12:59:20 -0600 > "Joel Baker" <[EMAIL PROTECTED]> wrote: > > > Is there a way to specify the following in a Debhelper file (such as > > .dirs or .links)? > > > > usr/include/$(SHELLVARIABLE)/foo.h > > Why bothe

Re: How to force porters to rebuild a package

2002-10-18 Thread Drew Parsons
On Thu, Oct 17, 2002 at 11:05:59PM +0200, Stefan Schwandter wrote: > Drew Parsons wrote: > > > And more to the point [ ;) ], how do I force the autobuilder maintainers to > > actually upload my package once it has been autobuilt? > > > The s390 version of xprint-xprintorg has been built for a who

Looking for package sponsor: zope-fle

2002-10-18 Thread Tarmo Toikkanen
Hi all, I'm one of the developers of Fle3, which is a learning environment implemented as a Zope product. We already package the releases in tarballs and debs, and would like to see the software in the Debian archives. Fle3 is GPL'd. The package itself is really simple, so we just need a sponsor

Re: Debhelper files w/ meta values

2002-10-18 Thread Joel Baker
On Fri, Oct 18, 2002 at 05:15:11PM +0900, Junichi Uekawa wrote: > On Thu, 17 Oct 2002 12:59:20 -0600 > "Joel Baker" <[EMAIL PROTECTED]> wrote: > > > Is there a way to specify the following in a Debhelper file (such as > > .dirs or .links)? > > > > usr/include/$(SHELLVARIABLE)/foo.h > > Why bothe

Re: How to force porters to rebuild a package

2002-10-18 Thread Sven Luther
On Thu, Oct 17, 2002 at 11:32:40PM +1000, Drew Parsons wrote: > On Thu, Oct 17, 2002 at 11:44:14AM +0200, Marco Kuhlmann wrote: > > > > How do I force a rebuild on buildd? > > And more to the point [ ;) ], how do I force the autobuilder maintainers to > actually upload my package once it has been

Re: Debhelper files w/ meta values

2002-10-18 Thread Junichi Uekawa
On Thu, 17 Oct 2002 12:59:20 -0600 "Joel Baker" <[EMAIL PROTECTED]> wrote: > Is there a way to specify the following in a Debhelper file (such as > .dirs or .links)? > > usr/include/$(SHELLVARIABLE)/foo.h Why bother using debhelper at all ? You can use variables in debian/rules all right. reg

Re: How to force porters to rebuild a package

2002-10-18 Thread Michael Banck
On Fri, Oct 18, 2002 at 09:23:19AM +0200, Sven Luther wrote: > Also notice that the s390 is not a released port, so it will not stop > your package from entering testing, so i would not worry too much about > this, just wait it out a bit. > > Thes arches you have to wait for are : > > alpha, arm,

Re: How to force porters to rebuild a package

2002-10-18 Thread Sven Luther
On Fri, Oct 18, 2002 at 08:21:05AM +0100, Jonathan McDowell wrote: > On Fri, Oct 18, 2002 at 09:23:19AM +0200, Sven Luther wrote: > > > Also notice that the s390 is not a released port, so it will not stop > > your package from entering testing, so i would not worry too much about > > this, just

Re: How to force porters to rebuild a package

2002-10-18 Thread Jonathan McDowell
On Fri, Oct 18, 2002 at 09:23:19AM +0200, Sven Luther wrote: > Also notice that the s390 is not a released port, so it will not stop > your package from entering testing, so i would not worry too much about > this, just wait it out a bit. You might want to take a look at http://www.debian.org/po

Re: How to force porters to rebuild a package

2002-10-18 Thread Michael Banck
On Fri, Oct 18, 2002 at 09:23:19AM +0200, Sven Luther wrote: > Also notice that the s390 is not a released port, so it will not stop > your package from entering testing, so i would not worry too much about > this, just wait it out a bit. > > Thes arches you have to wait for are : > > alpha, arm,

Re: How to force porters to rebuild a package

2002-10-18 Thread Sven Luther
On Thu, Oct 17, 2002 at 11:32:40PM +1000, Drew Parsons wrote: > On Thu, Oct 17, 2002 at 11:44:14AM +0200, Marco Kuhlmann wrote: > > > > How do I force a rebuild on buildd? > > And more to the point [ ;) ], how do I force the autobuilder maintainers to > actually upload my package once it has been

Re: Debhelper files w/ meta values

2002-10-18 Thread Junichi Uekawa
On Thu, 17 Oct 2002 12:59:20 -0600 "Joel Baker" <[EMAIL PROTECTED]> wrote: > Is there a way to specify the following in a Debhelper file (such as > .dirs or .links)? > > usr/include/$(SHELLVARIABLE)/foo.h Why bother using debhelper at all ? You can use variables in debian/rules all right. reg

Re: How to force porters to rebuild a package

2002-10-18 Thread Sven Luther
On Fri, Oct 18, 2002 at 08:21:05AM +0100, Jonathan McDowell wrote: > On Fri, Oct 18, 2002 at 09:23:19AM +0200, Sven Luther wrote: > > > Also notice that the s390 is not a released port, so it will not stop > > your package from entering testing, so i would not worry too much about > > this, just

Re: How to force porters to rebuild a package

2002-10-18 Thread Jonathan McDowell
On Fri, Oct 18, 2002 at 09:23:19AM +0200, Sven Luther wrote: > Also notice that the s390 is not a released port, so it will not stop > your package from entering testing, so i would not worry too much about > this, just wait it out a bit. You might want to take a look at http://www.debian.org/po