Osamu Aoki [EMAIL PROTECTED] wrote:
Hi,
Osamu Aoki [EMAIL PROTECTED] wrote:
...
I think one to ease tension is to make tetex packages to coexist in
archive just like many gcc.
[...]
I should have been clear. I wish them to coexist only in archive but
they can conflict each other to
Hi,
On Tue, Dec 20, 2005 at 01:48:12PM +0100, Frank Küster wrote:
Osamu Aoki [EMAIL PROTECTED] wrote:
...
I think one to ease tension is to make tetex packages to coexist in
archive just like many gcc.
That would be nice - but it would cause even more work, I fear. And it
would be the
Russ Allbery [EMAIL PROTECTED] writes:
Goswin von Brederlow [EMAIL PROTECTED] writes:
Russ Allbery [EMAIL PROTECTED] writes:
Funny, I just did a Google search for
site:www.debian.org cvs repository www.debian.org
and there it was, plain as day.
That implies that you already
Goswin von Brederlow [EMAIL PROTECTED] writes:
You just try to make a point out of buildd.net not having a direct
source link which is completly irelevant imho.
Hey, I don't care if there's a direct link or not. I care if the source
is available for anyone to go download. If it's available
On Wed, Dec 21, 2005 at 10:12:56AM -0800, Russ Allbery wrote:
This may sound heretical to you, but I don't consider software to be
DFSG-free unless there's actually a copy somewhere that people can get to.
If the source is unavailable, the software isn't free, regardless of what
theoretical
Kurt Roeckx [EMAIL PROTECTED] wrote:
On Sun, Dec 18, 2005 at 08:34:04PM +0100, Frank Küster wrote:
Six months is a lot of time; and experimental should provide you with
the space and machine power to handle the rebuilding.
I don't know of any autobuilders that build packages from sid
Anthony Towns aj@azure.humbug.org.au wrote:
A far-east document is typeset in a certain encoding doesn't sound like
an RC bug; and therefore not something that should hold up transitioning
to testing.
The package with the RC bug is debian-reference, which builds documents
in different
Osamu Aoki [EMAIL PROTECTED] wrote:
Hi,
I realize TeX is tough program to maintain. Thanks to Frank.
One quick and easy way to avoid TeX related build issues are to avoid
using TeX related tools during build time. So the results will be
Debian only ships documentations in plain text and
Osamu Aoki [EMAIL PROTECTED] wrote:
I hope situation will be better soon but I am still struggling why
debiandoc-sgml-doc fails to build nicely. (Yes, I know I can get by by
not checking exit code during build process. But that is not a good fix
I want to do.) Any help is appreciated.
The
Thimo: I've uploaded an NMU to fix gnuplot bugs 321967 and 330024; this is
the context.
On Tue, Dec 20, 2005 at 10:07:34AM +0100, Frank Küster wrote:
Anthony Towns aj@azure.humbug.org.au wrote:
A far-east document is typeset in a certain encoding doesn't sound like
an RC bug; and therefore
Anthony Towns aj@azure.humbug.org.au wrote:
Sure, getting tetex-3.0 done would've been quicker; but it wouldn't
necessarily have been quick enough -- after all, it's not ready *now*
and there's been six months since sarge's release. And this isn't just
*you*, everyone's in a similar position.
On Tue, Dec 20, 2005 at 03:41:06PM +0100, Frank Küster wrote:
Sure; but again, look at the broader context: if people aren't fixing
trivial bugs like the gnuplot one, why should anyone else spend time
worrying about the harder ones? Why haven't you done the appropriate
NMU of gnuplot
On Tue, Dec 20, 2005 at 09:54:34AM +0100, Frank Küster wrote:
Kurt Roeckx [EMAIL PROTECTED] wrote:
On Sun, Dec 18, 2005 at 08:34:04PM +0100, Frank Küster wrote:
I don't know of any autobuilders that build packages from sid against
build-dependencies in experimental.
I thought I did
Hi,
I realize TeX is tough program to maintain. Thanks to Frank.
One quick and easy way to avoid TeX related build issues are to avoid
using TeX related tools during build time. So the results will be
Debian only ships documentations in plain text and HTML. (No PS and no
PDF). But is it what
Anthony Towns aj@azure.humbug.org.au wrote:
On Fri, Dec 16, 2005 at 11:24:39AM +0100, Frank Küster wrote:
No, that would be unsuitable for release. Which is a problem that
should either be fixed quickly, or means you're trying to make a big
enough change that you should be working out how
On Sun, Dec 18, 2005 at 08:34:04PM +0100, Frank Küster wrote:
Six months is a lot of time; and experimental should provide you with
the space and machine power to handle the rebuilding.
I don't know of any autobuilders that build packages from sid against
build-dependencies in
On Sun, Dec 18, 2005 at 08:34:04PM +0100, Frank Küster wrote:
I don't know of any autobuilders that build packages from sid against
build-dependencies in experimental.
So that's one problem.
Another (mentioned previously) is the case of two packages, A and B that
often should be installed
On Wed, Dec 14, 2005 at 03:51:06PM -0800, Thomas Bushnell BSG wrote:
Steve Langasek [EMAIL PROTECTED] writes:
Rather, it seems much more likely that we would want to push such packages
*out* of unstable.
Really? So now, unstable should be maintained in a releasable state
*too*?
Not
Goswin von Brederlow [EMAIL PROTECTED] writes:
Russ Allbery [EMAIL PROTECTED] writes:
Funny, I just did a Google search for
site:www.debian.org cvs repository www.debian.org
and there it was, plain as day.
That implies that you already know/suspect it is in cvs.
Goswin, with all due
On Fri, Dec 16, 2005 at 11:24:39AM +0100, Frank Küster wrote:
No, that would be unsuitable for release. Which is a problem that
should either be fixed quickly, or means you're trying to make a big
enough change that you should be working out how to get it done without
breaking other
Wouter Verhelst [EMAIL PROTECTED] writes:
On Wed, Dec 14, 2005 at 03:51:06PM -0800, Thomas Bushnell BSG wrote:
Steve Langasek [EMAIL PROTECTED] writes:
Rather, it seems much more likely that we would want to push such packages
*out* of unstable.
Really? So now, unstable should be
Anthony Towns aj@azure.humbug.org.au writes:
Generally, experimental fits the above role. Unstable's for uploading new
development of packages that will hopefully work, but might turn out not
to. In particular, though, they need to be fixed pretty quickly -- six
months in experimental, and
Anthony Towns aj@azure.humbug.org.au wrote:
On Thu, Dec 15, 2005 at 10:43:05AM +0100, Frank Küster wrote:
Anthony Towns aj@azure.humbug.org.au wrote:
If your package isn't going to be suitable for release; it should probably
be in experimental instead, which is even autobuilt these days.
On Fri, Dec 16, 2005 at 11:24:39AM +0100, Frank Küster wrote:
Much worse, there are a couple of cases where we had to NMU the
packages, either because the maintainers where inactive, or in one case
because he said no time here, just go ahead. Except for this one case
this couldn't have been
Russ Allbery [EMAIL PROTECTED] writes:
Goswin von Brederlow [EMAIL PROTECTED] writes:
Ok, lets take an example: Where is the source thrown at you for
www.debian.org?
It isn't. You have to ask around, get to know or dig deep along the
links to find cvs.debian.org.
Funny, I just did a
Nathanael Nerode [EMAIL PROTECTED] writes:
So for various reasons the buildd.net status code is not considered ready
to be integrated on buildd.debian.org, either by its author or by its
maintainer or by Ryan Murray. Fine, I understand.
Well, after looking at
On Fri, Dec 16, 2005 at 04:02:01PM +0100, Goswin von Brederlow wrote:
(The contact addresses and machine up/down statuses are a valuable part of
buildd.net which *isn't* there, but that's another matter entirely, which
requires different and additional work.)
The graphs are also not
Goswin von Brederlow wrote:
Well, after looking at http://buildd.debian.org/~jeroen/status/ ,
I concur that it's as good a general interface to buildd status as
buildd.net,
and much better than the http://buildd.debian.org/ interface.
Where did you find that url?
In a random mailing list
Anthony Towns aj@azure.humbug.org.au wrote:
On Wed, Dec 14, 2005 at 12:26:50PM -0500, Joe Smith wrote:
It sounds to me like what is needed as a tag for bugs that tells QA (you
post noted that the release team
would ignore RC bugs on packages not in testing) that it can ignore those
bugs.
On Thu, Dec 15, 2005 at 10:43:05AM +0100, Frank Küster wrote:
Anthony Towns aj@azure.humbug.org.au wrote:
If your package isn't going to be suitable for release; it should probably
be in experimental instead, which is even autobuilt these days. There's
almost no reason to have RC bugs that
So for various reasons the buildd.net status code is not considered ready
to be integrated on buildd.debian.org, either by its author or by its
maintainer or by Ryan Murray. Fine, I understand.
Well, after looking at http://buildd.debian.org/~jeroen/status/ ,
I concur that it's as good a
On Wed, Dec 14, 2005 at 05:23:48AM +, Nathanael Nerode wrote:
(The contact addresses and machine up/down statuses are a valuable part of
buildd.net which *isn't* there, but that's another matter entirely, which
requires different and additional work.)
However, even though this is on
Steve Langasek [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
On Sun, Dec 11, 2005 at 03:46:12PM -0800, Thomas Bushnell BSG wrote:
You have failed to detail any particular difficulty that this causes,
I'm pretty sure I saw him do this already, by noting that it increases the
Steve Langasek [EMAIL PROTECTED] writes:
I'm pretty sure I saw him do this already, by noting that it increases the
number of packages that the release and QA teams have to keep track of.
Seems to me that packages which aren't in testing should not occupy
the release team's time at all. Just
On Wed, Dec 14, 2005 at 12:26:50PM -0500, Joe Smith wrote:
It sounds to me like what is needed as a tag for bugs that tells QA (you
post noted that the release team
would ignore RC bugs on packages not in testing) that it can ignore those
bugs.
If your package isn't going to be suitable for
Anthony Towns aj@azure.humbug.org.au writes:
On Wed, Dec 14, 2005 at 12:26:50PM -0500, Joe Smith wrote:
It sounds to me like what is needed as a tag for bugs that tells QA (you
post noted that the release team
would ignore RC bugs on packages not in testing) that it can ignore those
bugs.
On Sun, Dec 11, 2005 at 03:46:12PM -0800, Thomas Bushnell BSG wrote:
Anthony Towns aj@azure.humbug.org.au writes:
On Sat, Dec 10, 2005 at 03:51:36PM -0800, Thomas Bushnell BSG wrote:
Anthony Towns aj@azure.humbug.org.au writes:
(a) seeing if the FTBFS can be fixed immediately, and
Anthony Towns aj@azure.humbug.org.au writes:
On Sat, Dec 10, 2005 at 11:52:22AM +0100, Josselin Mouette wrote:
It got proposed because no one was able to give correct explanations
about why it hadn't been included.
Heh. I'm almost morbidly curious enough to ask what you think the
correct
Anthony Towns aj@azure.humbug.org.au writes:
On Fri, Dec 09, 2005 at 07:24:00PM -0800, Thomas Bushnell BSG wrote:
That sort of information is helpful to tell you when there is a problem,
but that's only the first step. ATM, the corresponding thing would
be to (gosh!) setup a webpage tracking
Russ Allbery [EMAIL PROTECTED] writes:
Goswin von Brederlow [EMAIL PROTECTED] writes:
Russ Allbery [EMAIL PROTECTED] writes:
C'mon, this is a free software project. The obvious first step for
providing better infrastructure would be to make that infrastructure
publically available for
Anthony Towns aj@azure.humbug.org.au writes:
On Fri, Dec 09, 2005 at 09:40:11PM -0800, Thomas Bushnell BSG wrote:
Anthony Towns aj@azure.humbug.org.au writes:
Requeue requests are part of handling logs... You get a failed log, you
analyse it to say oh, that's a transient error due to other
Thiemo Seufer [EMAIL PROTECTED] writes:
Jeroen van Wolffelaar wrote:
[snip]
A similar issue I noted in the past is the big number of build failures
that don't get tagged 'Failed'. I tried working on classifying them, but
got bored so increadibly fast that I gave up, and decided for myself
Hamish Moffatt [EMAIL PROTECTED] writes:
On Fri, Dec 09, 2005 at 06:50:26PM +0100, Goswin von Brederlow wrote:
And when you try you get screamed at and flamed as witnessed in the
huge buildd flame fest the last time. Iirc some 3000 packages were
build outside the official buildd network
Goswin von Brederlow [EMAIL PROTECTED] writes:
Ok, lets take an example: Where is the source thrown at you for
www.debian.org?
It isn't. You have to ask around, get to know or dig deep along the
links to find cvs.debian.org.
Funny, I just did a Google search for
site:www.debian.org cvs
On Mon, Dec 12, 2005 at 10:46:10AM -0800, Russ Allbery wrote:
Even if the current software isn't publically available for whatever
reason (personally, I'm putting my money on hacked into place over time
and not particularly easy to massage into a form someone else could run,
That's one part
Nathanael Nerode wrote:
This is an omnibus reply. Sorry about the thread-breaking, but I'm on
yet *another* computer, and I can't seem to find a mailer which
respects the In-Reply-To headers from the web pages or lets me add my
own.
Off-topic, but Moz Thunderbird in Debian at least does the
Blars Blarson [EMAIL PROTECTED] wrote:
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
- How can I get information from inside a buildd, e.g. temporary files
created during a failed build.
First pass answer: you can't. sbuild (tries to) clean up after builds.
Alternate: try to get
On Fri, Dec 09, 2005 at 06:50:26PM +0100, Goswin von Brederlow wrote:
And when you try you get screamed at and flamed as witnessed in the
huge buildd flame fest the last time. Iirc some 3000 packages were
build outside the official buildd network across the involved archs at
that time.
And
Anthony Towns aj@azure.humbug.org.au writes:
On Sat, Dec 10, 2005 at 03:51:36PM -0800, Thomas Bushnell BSG wrote:
Anthony Towns aj@azure.humbug.org.au writes:
(a) seeing if the FTBFS can be fixed immediately, and finding it can't
(b) documenting (this is the transparent bit, so pay
Anthony Towns aj@azure.humbug.org.au writes:
Then you're not maintaining your packages properly, and you're making
life more difficult for the rest of the project out of spite.
Notice that in disagreeing with your statement, I have also gone out
of my way to answer the specific questions you
On Sat, Dec 10, 2005 at 08:22:24AM +0100, Bernd Eckenfels wrote:
In article [EMAIL PROTECTED] you wrote:
If a package is failing to build or to function on some architecture,
your job as that package's maintainer is see if it can be fixed (talking
to porters and/or upstream if it's beyond
Anthony Towns aj@azure.humbug.org.au writes:
On Fri, Dec 09, 2005 at 04:27:10PM +0100, Michael Banck wrote:
On Thu, Dec 08, 2005 at 04:52:31PM -0500, Nathanael Nerode wrote:
I also see the keyring's been updated earlier this week, including
both a replacement key for Horms from late last
Le samedi 10 décembre 2005 à 11:51 +1000, Anthony Towns a écrit :
On Fri, Dec 09, 2005 at 05:56:24PM +0100, Josselin Mouette wrote:
How many developer resignations will you need to understand inaction
from people at key positions sucks the fun out of things in a worse way?
Yeah,
On Fri, Dec 09, 2005 at 12:47:59PM -0600, Manoj Srivastava wrote:
On Fri, 9 Dec 2005 16:27:10 +0100, Michael Banck [EMAIL PROTECTED] said:
Where should I best complain for your NM application to be
cancelled?
Err, so if a NM candidate speaks as openly as some DD's do,
they get
On Sat, Dec 10, 2005 at 09:18:28AM +0100, Ingo Juergensmann wrote:
On Sat, Dec 10, 2005 at 08:22:24AM +0100, Bernd Eckenfels wrote:
BTW: is there a way to get build failures by mail? especially from the
architectures which are not visible on buildd.debian.org/PTS like hurd and
bsd. Took me
On Sat, 2005-12-10 at 02:40 +, Matthew Garrett wrote:
Thijs Kinkhorst [EMAIL PROTECTED] wrote:
I'm not really convinced that such an approach would have a significant
effect as long as you're not measuring existing DD's to the same
standards. Which, as far as I can see, does not
On Fri, 09 Dec 2005 19:24:00 -0800, Thomas Bushnell BSG
[EMAIL PROTECTED] wrote:
An excellent example of this is the publication of the NEW queue. Now
that everyone can see the NEW queue, I don't see any of the big public
criticism about slow processing.
I have to disagree here. Things have
On Sat, 10 Dec 2005 02:40:11 +, Matthew Garrett
[EMAIL PROTECTED] wrote:
Thijs Kinkhorst [EMAIL PROTECTED] wrote:
I'm not really convinced that such an approach would have a significant
effect as long as you're not measuring existing DD's to the same
standards. Which, as far as I can see,
On Sat, Dec 10, 2005 at 11:52:22AM +0100, Josselin Mouette wrote:
It got proposed because no one was able to give correct explanations
about why it hadn't been included.
Heh. I'm almost morbidly curious enough to ask what you think the
correct explanation of why it hasn't been included is,
Anthony Towns aj@azure.humbug.org.au writes:
Since this point obviously needs to be made clearer, I guess it's time
to have some more rounds of removing packages that have long outstanding
RC bugs. I guess I'll coordinate with the RM team to do this sometime
over Christmas/New Year.
(The
Michael Banck [EMAIL PROTECTED] writes:
There are currently no public build logs for hurd-i386, but we are
working on getting them published on experimentel.ftbfs.de as well.
If you can get them into http://people.debian.org/~igloo/status.php,
that would be wonderful. I read that page
Jeroen van Wolffelaar wrote:
[snip]
A similar issue I noted in the past is the big number of build failures
that don't get tagged 'Failed'. I tried working on classifying them, but
got bored so increadibly fast that I gave up, and decided for myself
this should be something the porters should
This is an omnibus reply. Sorry about the thread-breaking, but I'm on
yet *another* computer, and I can't seem
to find a mailer which respects the In-Reply-To headers from the web
pages or lets me add my own.
==
I would like to note that I have made a practical and *new* suggestion
for
Anthony Towns aj@azure.humbug.org.au writes:
FTBFS issues are the most common though, as well as the easiest to
resolve; your point would carry more weight if you took the time to fix
yours first. (Looking through -private, I saw someone remark that 1000
bugs was too many -- we have got 1400
Anthony Towns aj@azure.humbug.org.au writes:
(a) seeing if the FTBFS can be fixed immediately, and finding it can't
(b) documenting (this is the transparent bit, so pay attention) that
fact by not having s390 incorrectly listed as a supported arch in
the source and ensuring it
Marc Haber [EMAIL PROTECTED] writes:
(BTW, I see #335981 and #336371 haven't received a response since late
October; or has raptor been down that entire time, so that you haven't been
able to diagnose it further -- it certainly seems down now?)
Upstream is working on #335981 and #336371. In
On Sat, Dec 10, 2005 at 03:51:36PM -0800, Thomas Bushnell BSG wrote:
Anthony Towns aj@azure.humbug.org.au writes:
(a) seeing if the FTBFS can be fixed immediately, and finding it can't
(b) documenting (this is the transparent bit, so pay attention) that
fact by not having s390
On Sat, Dec 10, 2005 at 06:29:03PM -0500, Nathanael Nerode wrote:
I would like to note that I have made a practical and *new* suggestion
for dealing with some of these problems
(contrary to suggestions that I'm just flaming), because nobody's picked
up on my idea.
Well, it's hard to
Ingo Juergensmann [EMAIL PROTECTED] wrote:
On Thu, Dec 08, 2005 at 10:32:40PM +0100, Frank Küster wrote:
Feature requests and other things are always welcome! I can't know what you
want until you tell it to me. ;)
Nothing - these the questions I was mainly interested in regarding
On Fri, Dec 09, 2005 at 09:43:36AM +0100, Frank Küster wrote:
Ingo Juergensmann [EMAIL PROTECTED] wrote:
On Thu, Dec 08, 2005 at 10:32:40PM +0100, Frank Küster wrote:
Feature requests and other things are always welcome! I can't know what
you
want until you tell it to me. ;)
Jeroen van Wolffelaar [EMAIL PROTECTED] wrote:
On Fri, Dec 09, 2005 at 09:43:36AM +0100, Frank Küster wrote:
Ingo Juergensmann [EMAIL PROTECTED] wrote:
A buildd admin doesn't see much more than what you can see in the build
logs. Basically the build logs is all a buildd admin see.
But
On Thu, Dec 08, 2005 at 10:16:37PM -0800, Thomas Bushnell BSG wrote:
Anthony Towns aj@azure.humbug.org.au writes:
That's non-sensical. Everything the buildds do is logged pretty much
immediately onto http://buildd.debian.org/, which also provides long
running statistics on how effective the
Anthony Towns aj@azure.humbug.org.au writes:
On Thu, Dec 08, 2005 at 04:52:31PM -0500, Nathanael Nerode wrote:
To respond preemptively to one expected reply: I don't have time to answer
these questions is not a reasonable excuse, because if they don't have
time,
they need to ask for help.
On Fri, Dec 09, 2005 at 11:49:05PM +1000, Anthony Towns wrote:
On Thu, Dec 08, 2005 at 10:16:37PM -0800, Thomas Bushnell BSG wrote:
Anthony Towns aj@azure.humbug.org.au writes:
That's non-sensical. Everything the buildds do is logged pretty much
immediately onto http://buildd.debian.org/,
On Thu, Dec 08, 2005 at 04:52:31PM -0500, Nathanael Nerode wrote:
I also see the keyring's been updated earlier this week, including
both a replacement key for Horms from late last month, and Chip's
requested updates.
Indeed, complaining on debian-devel appears to get results, doesn't
it?
Le vendredi 09 décembre 2005 à 16:27 +0100, Michael Banck a écrit :
On Thu, Dec 08, 2005 at 04:52:31PM -0500, Nathanael Nerode wrote:
Indeed, complaining on debian-devel appears to get results, doesn't
it? At least, that's the conclusion that a rational outside observer
would come to.
Le vendredi 09 décembre 2005 à 12:07 +1000, Anthony Towns a écrit :
That's non-sensical. Everything the buildds do is logged pretty much
immediately onto http://buildd.debian.org/, which also provides long
running statistics on how effective the buildds are, and even a schedule
of what the
Le vendredi 09 décembre 2005 à 23:49 +1000, Anthony Towns a écrit :
How many more years are we going to waste time with this hysteria before
realising it doesn't achieve anything but rapidly sucking the fun out
of things?
How many developer resignations will you need to understand inaction
* Josselin Mouette [EMAIL PROTECTED] [2005:12:09 17:48 +0100]:
Le vendredi 09 d?cembre 2005 ? 12:07 +1000, Anthony Towns a ?crit :
Ingo's burnt a fair number of bridges wrt buildd issues; I'm sorry,
but I don't really care if volunteers decline to work with people who're
obnoxious and
Josselin Mouette [EMAIL PROTECTED] writes:
Le vendredi 09 décembre 2005 à 12:07 +1000, Anthony Towns a écrit :
That's non-sensical. Everything the buildds do is logged pretty much
immediately onto http://buildd.debian.org/, which also provides long
running statistics on how effective the
On Fri, 9 Dec 2005 12:07:11 +1000, Anthony Towns aj@azure.humbug.org.au said:
That's not a productive attitude. If they don't have time to answer
questions, they almost certainly don't have time to ask for help,
either. When that cirucmstance has arisen, the only way out is for
others to
On Fri, 9 Dec 2005 16:27:10 +0100, Michael Banck [EMAIL PROTECTED] said:
On Thu, Dec 08, 2005 at 04:52:31PM -0500, Nathanael Nerode wrote:
I also see the keyring's been updated earlier this week, including
both a replacement key for Horms from late last month, and Chip's
requested updates.
* Manoj Srivastava [EMAIL PROTECTED] [2005:12:09 12:47 -0600]:
Err, so if a NM candidate speaks as openly as some DD's do,
they get threatened with having their applications cancelled because
of them speaking their minds? What is this, a munich beer hall in
1933?
Isn't the point
On Fri, Dec 09, 2005 at 05:48:13PM +0100, Josselin Mouette wrote:
Le vendredi 09 décembre 2005 à 12:07 +1000, Anthony Towns a écrit :
That's non-sensical. Everything the buildds do is logged pretty much
immediately onto http://buildd.debian.org/, which also provides long
running statistics
On Fri, December 9, 2005 20:02, Erinn Clark wrote:
Surely flaming people on mailing lists as a way to get things done
is not something people want to encourage in NMs... right? Wouldn't Debian
want to find people who can think of new and inventive ways to achieve
goals rather than resorting to
On Fri, 9 Dec 2005 14:02:17 -0500, Erinn Clark [EMAIL PROTECTED] said:
* Manoj Srivastava [EMAIL PROTECTED] [2005:12:09 12:47 -0600]:
Err, so if a NM candidate speaks as openly as some DD's do, they
get threatened with having their applications cancelled because of
them speaking their minds?
* Manoj Srivastava [EMAIL PROTECTED] [2005:12:09 13:27 -0600]:
I'm surprised you think raising ones voice civilly in concern
about a problem area in Debian is not playing nicely with others. Is
your contention that some volunteers are so much more equal than
others that no voices
On Fri, 9 Dec 2005 15:06:26 -0500, Erinn Clark [EMAIL PROTECTED] said:
* Manoj Srivastava [EMAIL PROTECTED] [2005:12:09 13:27 -0600]:
I'm surprised you think raising ones voice civilly in concern about
a problem area in Debian is not playing nicely with others. Is your
contention that some
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
- How can I get information from inside a buildd, e.g. temporary files
created during a failed build.
First pass answer: you can't. sbuild (tries to) clean up after builds.
Alternate: try to get a porter to redo the build and give you
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Setting up a buildd system do not require extra privileges from the
Debian project, as far as I know. Any Debian developer with his
public key in the keyring can sign uploads.
and get threats from the current buildd administrator to make
* Erinn Clark [EMAIL PROTECTED] [2005:12:09 12:45 -0500]:
* Josselin Mouette [EMAIL PROTECTED] [2005:12:09 17:48 +0100]:
Le vendredi 09 d?cembre 2005 ? 12:07 +1000, Anthony Towns a ?crit :
Ingo's burnt a fair number of bridges wrt buildd issues; I'm sorry,
but I don't really care if
On Fri, Dec 09, 2005 at 04:08:55PM -0500, Erinn Clark wrote:
Where is the buildd.net software located? I poked around on the site but
I couldn't find it except for the update-buildd.net script.
(Replying to myself after getting an answer on IRC from Ingo...)
The short summary to my answer
Ingo Juergensmann [EMAIL PROTECTED] writes:
Please stop assuming wrong facts.
As I already stated several times before: Ryan was offered to integrate
the buildd.net software. He declined with the argument that all
information is already available on buildd.d.o. That's a clear sign that
he
Erinn Clark writes:
Surely flaming people on mailing lists as a way to get things done is not
something people want to encourage in NMs... right?
Right. After all, as we all know, no DD would ever do such a thing.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Fri, Dec 09, 2005 at 10:19:46AM -0500, Daniel Jacobowitz wrote:
I'm not saying that this all needs to be publicly logged. I don't give
a rat's ass whether it is or not. But please don't stand there saying
that the process is completely transparent.
I don't believe I said that. I don't
On Fri, Dec 09, 2005 at 05:56:24PM +0100, Josselin Mouette wrote:
Le vendredi 09 décembre 2005 à 23:49 +1000, Anthony Towns a écrit :
How many more years are we going to waste time with this hysteria before
realising it doesn't achieve anything but rapidly sucking the fun out
of things?
On Fri, Dec 09, 2005 at 04:27:10PM +0100, Michael Banck wrote:
On Thu, Dec 08, 2005 at 04:52:31PM -0500, Nathanael Nerode wrote:
I also see the keyring's been updated earlier this week, including
both a replacement key for Horms from late last month, and Chip's
requested updates.
Indeed,
On Fri, Dec 09, 2005 at 05:48:13PM +0100, Josselin Mouette wrote:
There is absolutely zero documentation on how the buildd network works.
If the documentation's insufficient, ask politely for help.
buildd.debian.org points you at wanna-build and its svn repo, which has
some reasonably extensive
Josselin Mouette [EMAIL PROTECTED] wrote:
Le vendredi 09 décembre 2005 à 23:49 +1000, Anthony Towns a écrit :
How many more years are we going to waste time with this hysteria before
realising it doesn't achieve anything but rapidly sucking the fun out
of things?
How many developer
Thijs Kinkhorst [EMAIL PROTECTED] wrote:
I'm not really convinced that such an approach would have a significant
effect as long as you're not measuring existing DD's to the same
standards. Which, as far as I can see, does not happen.
A procedure is in place for developers to be ejected from
1 - 100 of 146 matches
Mail list logo
