Stephen Gran [EMAIL PROTECTED] schrieb:
This one time, at band camp, Frank Kster said:
Frank Lichtenheld [EMAIL PROTECTED] schrieb:
(I'm confused myself atm if it is /etc/pbuilderrc or
/etc/pbuilder/pbuilderrc...)
The first one works here for me, also according to man pbuilder. But
Quoting http://ftp-master.debian.org/testing/update_excuses.html.gz#glibc
-
# glibc (2.3.1-16 to 2.3.2-5)
* Maintainer: GNU Libc Maintainers
* Too young, only 3 of 10 days old
* locales/hppa unsatisfiable Depends: glibc-2.3.2-5
* out of date on hppa:
On Mon, Sep 08, 2003 at 02:07:23PM +0200, Andreas Metzler wrote:
So the db3-update predepends on a glibc-update, which cannot happen and
should stop db3 3.2.9-19.0.1 from becoming Valid candidate,
shouldn't it?
The script considers if things are a valid candiate on their own merits
but
On Mon, Sep 08, 2003 at 01:45:43PM +0100, Mark Brown wrote:
On Mon, Sep 08, 2003 at 02:07:23PM +0200, Andreas Metzler wrote:
So the db3-update predepends on a glibc-update, which cannot happen and
should stop db3 3.2.9-19.0.1 from becoming Valid candidate,
shouldn't it?
The script
John Buttery [EMAIL PROTECTED] writes:
* Adam Kessel [EMAIL PROTECTED] [2003-09-07 16:35:14 -0700]:
It's definitely a scratch an itch type program.
So's emacs. For that matter, so's the kernel itself. :)
I'm wondering if something relatively simple (the script is about 340
lines of
Re: Re: FAQ for debian-mentors [Matthew Palmer [EMAIL PROTECTED], Mon, Sep 08, 2003
at 02:19:26PM +1000, [EMAIL PROTECTED]]
You have to stress that people actually upload the _source_ package. If
not told, they tend to provide i386 binaries.
Is all of the files (.orig.tar.gz, diff,
I'd like to focus this discussion on my package[1], at least as an
example. It seems to me that although it is simple, it is useful,
nonobvious, and nonredundant with anything in Debian.
Maybe the criteria shouldn't be the length of the script, but something
else like general appeal,
On Mon, Sep 08, 2003 at 11:49:57AM -0500, John Buttery wrote:
* Brian Nelson [EMAIL PROTECTED] [2003-09-08 07:19:08 -0700]:
That is certainly not all that matters. If every script anyone tried
to write was included in Debian, Debian would collapse under its own
weight.
How? I mean, as
I need a sponsor to update two packages and close some bugs:
mantis (0.17.5-7+1) unstable; urgency=low
.
* Only reconfigure if config.php doesn't exists, avoiding overwriting
* it
(Closes: #199985)
* Urlencodes before creating bug and cvs links (Closes: #200336)
* Downgraded
* Sven Luther [EMAIL PROTECTED] [2003-09-08 19:48:09 +0200]:
You are aware that some mirror are already on the very limit of not
having enough place on their 100Go partition for the debian archives
and were asking for near term solutions.
In point of fact I was not aware of that. That's
Hello again.
I need a sponsor to update this package:
Description:
slimp3 - MPEG Layer III Streaming Server
Changes:
slimp3 (4.2.3-0+1) unstable; urgency=low
.
* New upstream version
* Cleaned strings.txt patch as most translations are already on
* upstream
Files:
On Mon, 8 Sep 2003, Sven Luther wrote:
On Mon, Sep 08, 2003 at 05:37:40AM +0200, Adam Borowski wrote:
On Sun, 7 Sep 2003, Adam Kessel wrote:
I've written a fairly simple command-line shuffle music file player.
Despite its simplicity, I find it quite handy, and I don't think there's
any
I started my very first (d)upload of a package to Erlangen, but then my
dog ate my mouse[1] and the transfer was interrupted. Well, actually I
realised that the changes file did not include the original tar ball.
If I now try to dupload again, I get Overwrite permission denied, and
if I fiddle
nobody interestet to fvwm-themes?
http://smilebef.homelinux.org/~smilebef/
Andrei
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Mon, Sep 08, 2003 at 11:59:45PM +0200, Jens Peter Secher wrote:
If I now try to dupload again, I get Overwrite permission denied, and
if I fiddle with *.upload files, I get dsc. already exists.
How do I get back in a sane state?
Well... I do not know if it is a canonical way to solve
On Mon, Sep 08, 2003 at 05:48:28PM +0200, Christoph Berg wrote:
I then went to the Mentors FAQ, searched for source and found nothing.
Upon close inspection, your statement is clear, but I'd change it:
# Provide a publically accessible place where all of the files
(.orig.tar.gz, diff,
On Tue, Sep 09, 2003 at 12:27:53AM +0200, Andrei Mitrofanow wrote:
nobody interestet to fvwm-themes?
It would appear not, if you haven't gotten any private responses. If that's
the case, try asking in other places where developers hang out who might be
interested in your package - FVWM-related
I have a source package that creates multiple binary packages, each of which
requires a different sequence of debhelper programs. To avoid having to
specify the -p option for each command, I do this:
pkg1-stamp: pkg1
pkg2-stamp: pkg2
%-stamp:
$(MAKE) -f debian/rules
On Mon, Sep 08, 2003 at 11:59:45PM +0200, Jens Peter Secher wrote:
I started my very first (d)upload of a package to Erlangen, but then my
dog ate my mouse[1] and the transfer was interrupted. Well, actually I
realised that the changes file did not include the original tar ball.
If I now
On Mon, Sep 08, 2003 at 07:22:02PM -0400, Neil Roeth wrote:
I recently read about target-specific variables in make, so I thought I could
do this:
pkg1-stamp: pkg1
pkg2-stamp: pkg2
%-stamp: $(@:%-stamp=%)
touch $@
pkg1: DH_OPTIONS=-p$@
...
dh_install
hello again.
Another package to be updated,
Description:
libapache-mod-security - Tighten the Web application security for
Apache 1.x
libapache2-mod-security - Tighten the Web application security for
Apache 2.x
mod-security-common - Tighten the Web application security - common
files
On Sep 9, Colin Watson ([EMAIL PROTECTED]) wrote:
On Mon, Sep 08, 2003 at 07:22:02PM -0400, Neil Roeth wrote:
I recently read about target-specific variables in make, so I thought I could
do this:
pkg1-stamp: pkg1
pkg2-stamp: pkg2
%-stamp: $(@:%-stamp=%)
touch $@
Andrei Mitrofanow wrote:
nobody interestet to fvwm-themes?
http://smilebef.homelinux.org/~smilebef/
[Reading my note before sending it I see it sounds harsh. I don't
mean it that way. I mean it constructively so that you will know why
I personally have not tried any of your packages. Please
On Sat, Sep 06, 2003 at 04:44:10PM -0500, Michael Schultheiss wrote:
Matthew Palmer wrote:
To facilitate that, I've put an explicit licence notice at the bottom of the
page if someone wants to incorporate it into another Debian document
(alternate licencing can be arranged if needed).
On Sun, Sep 07, 2003 at 01:03:46PM +0200, Christoph Berg wrote:
Re: Re: FAQ for debian-mentors [Joe Nahmias [EMAIL PROTECTED], Thu, Sep 04,
2003 at 10:49:09AM -0400, [EMAIL PROTECTED]]
4) Same section, there should be a step 3.5 which says something
like: Upload the source package to
On Sun, Sep 07, 2003 at 03:45:04AM -0500, Cam Desautels wrote:
but I haven't yet developed anything worth contributing. Anyway, I'm
not yet familiar with the exact duties of a maintainer but I understand
generally and I am willing to contribute the time to learn and to
conduct a package
* Adam Kessel [EMAIL PROTECTED] [2003-09-07 16:35:14 -0700]:
It's definitely a scratch an itch type program.
So's emacs. For that matter, so's the kernel itself. :)
I'm wondering if something relatively simple (the script is about 340
lines of code) would be worth including in Debian.
Stephen Gran [EMAIL PROTECTED] schrieb:
This one time, at band camp, Frank Küster said:
Frank Lichtenheld [EMAIL PROTECTED] schrieb:
(I'm confused myself atm if it is /etc/pbuilderrc or
/etc/pbuilder/pbuilderrc...)
The first one works here for me, also according to man pbuilder. But
Quoting http://ftp-master.debian.org/testing/update_excuses.html.gz#glibc
-
# glibc (2.3.1-16 to 2.3.2-5)
* Maintainer: GNU Libc Maintainers
* Too young, only 3 of 10 days old
* locales/hppa unsatisfiable Depends: glibc-2.3.2-5
* out of date on hppa:
On Mon, Sep 08, 2003 at 02:07:23PM +0200, Andreas Metzler wrote:
So the db3-update predepends on a glibc-update, which cannot happen and
should stop db3 3.2.9-19.0.1 from becoming Valid candidate,
shouldn't it?
The script considers if things are a valid candiate on their own merits
but
On Mon, Sep 08, 2003 at 01:45:43PM +0100, Mark Brown wrote:
On Mon, Sep 08, 2003 at 02:07:23PM +0200, Andreas Metzler wrote:
So the db3-update predepends on a glibc-update, which cannot happen and
should stop db3 3.2.9-19.0.1 from becoming Valid candidate,
shouldn't it?
The script
On Mon, Sep 08, 2003 at 01:45:43PM +0100, Mark Brown wrote:
On Mon, Sep 08, 2003 at 02:07:23PM +0200, Andreas Metzler wrote:
So the db3-update predepends on a glibc-update, which cannot happen and
should stop db3 3.2.9-19.0.1 from becoming Valid candidate,
shouldn't it?
The script
John Buttery [EMAIL PROTECTED] writes:
* Adam Kessel [EMAIL PROTECTED] [2003-09-07 16:35:14 -0700]:
It's definitely a scratch an itch type program.
So's emacs. For that matter, so's the kernel itself. :)
I'm wondering if something relatively simple (the script is about 340
lines of
Re: Re: FAQ for debian-mentors [Matthew Palmer [EMAIL PROTECTED], Mon, Sep
08, 2003 at 02:19:26PM +1000, [EMAIL PROTECTED]]
You have to stress that people actually upload the _source_ package. If
not told, they tend to provide i386 binaries.
Is all of the files (.orig.tar.gz, diff,
* Brian Nelson [EMAIL PROTECTED] [2003-09-08 07:19:08 -0700]:
That is certainly not all that matters. If every script anyone tried
to write was included in Debian, Debian would collapse under its own
weight.
How? I mean, as long as the package was maintained. Although, if
you're talking
I'd like to focus this discussion on my package[1], at least as an
example. It seems to me that although it is simple, it is useful,
nonobvious, and nonredundant with anything in Debian.
Maybe the criteria shouldn't be the length of the script, but something
else like general appeal,
On Mon, Sep 08, 2003 at 11:49:57AM -0500, John Buttery wrote:
* Brian Nelson [EMAIL PROTECTED] [2003-09-08 07:19:08 -0700]:
That is certainly not all that matters. If every script anyone tried
to write was included in Debian, Debian would collapse under its own
weight.
How? I mean, as
I need a sponsor to update two packages and close some bugs:
mantis (0.17.5-7+1) unstable; urgency=low
.
* Only reconfigure if config.php doesn't exists, avoiding overwriting
* it
(Closes: #199985)
* Urlencodes before creating bug and cvs links (Closes: #200336)
* Downgraded
On Mon, Sep 08, 2003 at 05:37:40AM +0200, Adam Borowski wrote:
On Sun, 7 Sep 2003, Adam Kessel wrote:
I've written a fairly simple command-line shuffle music file player.
Despite its simplicity, I find it quite handy, and I don't think there's
any other package out there (in Debian or not)
On Mon, Sep 08, 2003 at 11:49:57AM -0500, John Buttery wrote:
* Brian Nelson [EMAIL PROTECTED] [2003-09-08 07:19:08 -0700]:
That is certainly not all that matters. If every script anyone tried
to write was included in Debian, Debian would collapse under its own
weight.
How? I mean,
* Sven Luther [EMAIL PROTECTED] [2003-09-08 19:48:09 +0200]:
You are aware that some mirror are already on the very limit of not
having enough place on their 100Go partition for the debian archives
and were asking for near term solutions.
In point of fact I was not aware of that. That's
Hello again.
I need a sponsor to update this package:
Description:
slimp3 - MPEG Layer III Streaming Server
Changes:
slimp3 (4.2.3-0+1) unstable; urgency=low
.
* New upstream version
* Cleaned strings.txt patch as most translations are already on
* upstream
Files:
On Mon, 8 Sep 2003, Sven Luther wrote:
On Mon, Sep 08, 2003 at 05:37:40AM +0200, Adam Borowski wrote:
On Sun, 7 Sep 2003, Adam Kessel wrote:
I've written a fairly simple command-line shuffle music file player.
Despite its simplicity, I find it quite handy, and I don't think there's
any
I started my very first (d)upload of a package to Erlangen, but then my
dog ate my mouse[1] and the transfer was interrupted. Well, actually I
realised that the changes file did not include the original tar ball.
If I now try to dupload again, I get Overwrite permission denied, and
if I fiddle
nobody interestet to fvwm-themes?
http://smilebef.homelinux.org/~smilebef/
Andrei
On Mon, Sep 08, 2003 at 05:48:28PM +0200, Christoph Berg wrote:
I then went to the Mentors FAQ, searched for source and found nothing.
Upon close inspection, your statement is clear, but I'd change it:
# Provide a publically accessible place where all of the files
(.orig.tar.gz, diff,
On Tue, Sep 09, 2003 at 12:27:53AM +0200, Andrei Mitrofanow wrote:
nobody interestet to fvwm-themes?
It would appear not, if you haven't gotten any private responses. If that's
the case, try asking in other places where developers hang out who might be
interested in your package - FVWM-related
I have a source package that creates multiple binary packages, each of which
requires a different sequence of debhelper programs. To avoid having to
specify the -p option for each command, I do this:
pkg1-stamp: pkg1
pkg2-stamp: pkg2
%-stamp:
$(MAKE) -f debian/rules
On Mon, Sep 08, 2003 at 11:59:45PM +0200, Jens Peter Secher wrote:
I started my very first (d)upload of a package to Erlangen, but then my
dog ate my mouse[1] and the transfer was interrupted. Well, actually I
realised that the changes file did not include the original tar ball.
If I now
On Mon, Sep 08, 2003 at 07:22:02PM -0400, Neil Roeth wrote:
I recently read about target-specific variables in make, so I thought I could
do this:
pkg1-stamp: pkg1
pkg2-stamp: pkg2
%-stamp: $(@:%-stamp=%)
touch $@
pkg1: DH_OPTIONS=-p$@
...
dh_install
hello again.
Another package to be updated,
Description:
libapache-mod-security - Tighten the Web application security for
Apache 1.x
libapache2-mod-security - Tighten the Web application security for
Apache 2.x
mod-security-common - Tighten the Web application security - common
files
On Sep 9, Colin Watson ([EMAIL PROTECTED]) wrote:
On Mon, Sep 08, 2003 at 07:22:02PM -0400, Neil Roeth wrote:
I recently read about target-specific variables in make, so I thought I
could
do this:
pkg1-stamp: pkg1
pkg2-stamp: pkg2
%-stamp: $(@:%-stamp=%)
touch
52 matches
Mail list logo
