dle and shouldn't be idled out without warning.
>
> Well, I've no strong objection on that.
>
> Still, I'd prefer not to have to write such specific details on the
> text we are going to vote on. I propose to leave such details to DAM /
> DSA, would you be fine wit
t many DDs (and no DM
so far) in the TeX team, I guess the existence of a second DD in the
team is of value for the project too.
Therfore, I would have appreciated a note about loosing upload rights if
the rules discussed here would have already been in place.
Regards, Frank
--
Dr. Frank Küster
pecial header needs to be included,
and look up which in the developer's reference.
Regards, Frank
--
Dr. Frank Küster
Debian Developer (TeXLive)
VCD Aschaffenburg-Miltenberg, ADFC Miltenberg
B90/Grüne KV Miltenberg
--
To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org
ld be kind of aware
of it...
How can I find out if my key is v3 or v4?
Regards, Frank
--
Dr. Frank Küster
Debian Developer (TeXLive)
VCD Aschaffenburg-Miltenberg, ADFC Miltenberg
B90/Grüne KV Miltenberg
--
To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org
with a subject of
ns that the
package is orphaned and doesn't have a maintainer. It's just not buggy
or useless enough to delete it from the archive straight away.
If you expect someone to care for the package other than fixing RC bugs,
I think you're wrong. If someone from the QA team actually offe
orking: Orthodox Debian which never
releases, and a derived or related distribution which would be
comparable to Debian as it is.
Regards, Frank
--
Frank Küster
Debian Developer (TeXLive)
VCD Aschaffenburg-Miltenberg, ADFC Miltenberg
B90/Grüne KV Miltenberg
--
To UNSUBSCRIBE, email to
Solaris doesn't currently nor has previously used the Linux
> kernel: Solaris is not Linux.
Of course, but if all you know is Windows, getting a course on Solaris
(or Irix as in my case) helps a lot for your first Linux experience.
Regards, Frank
--
Frank Küster
Debian Developer (teT
even that for a week. And we've already been
NMUed, with good effects on the quality of the distribution.
Regards, Frank
--
Frank Küster
Debian Developer (teTeX/TeXLive)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
t;.
> The current wording requires a notification (by sending a mail to the
> BTS). I don't think that it's a good idea to additionally require that
> this mail should be sent to the maintainer's private email address,
> because that doesn't work well with co-maintai
uot;improving
> signal:noise".
Or "melting pot to a common culture" vs. "different cultures in
different parts of the project".
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
considered is by selecting a committee that has a group with
> diverse backgrounds.
Which should be taken into account when designing the election and vote
evaluation method.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
which I think is approximately what you
have expressed much better as cultural differences.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
or sure not exclude merit completely
from their considerations, and - by the nature of their task - are
probable to consider power, too. And maybe that's not even a bad
thing. I think this shows that the separation is more important here.
Regards, Frank
--
Frank Küster
Single Molecule Spec
taken.
The real problem in a production environment is checking your conffiles,
verifying that everything still works etc.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
een discussed or are obviously needed.
It would be a pity if these people were able to upload texlive-base, but
not texlive-bin because of a never-changing library in it.
Other teams might face less extreme situations, but I think it's up to
the team to decide which DM get Uploader statu
le changes, and the rest is as stable (and old) as I'm used
to.
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
one. live with the decision, and quit
> whining.
To me it seems it's you who is whining about how bad backports is, no
one else...
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
the
> same...but in practice, they're not. practice trumps theory every time,
> because it's what actually happens rather than what someone thinks might
> happen.
If you're so keen on practice, can you show any examples of breakages in
backports, and explain how they would ha
Craig Sanders <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 20, 2007 at 12:21:39PM +0200, Frank Küster wrote:
>> > 1. why is this allegedly a 'benefit'? what's so special about libraries?
>> > why is a new libc6 or libssl etc more scary than a new apache o
lease comes around.
As far as the TeX packages are concerned, I can tell you at least that
one of the major TeX maintainers actually used the sarge-backports (me),
and that we did get feedback from backports users, but no bug reports
that wouldn't have also been in testing (and most b
ject, and coordinate with people in
other roles if needed.
By the way, I think the release team is a really good example how one
can do that.
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
Steve Langasek <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 02, 2007 at 06:22:01PM +0200, Frank Küster wrote:
>> Amaya <[EMAIL PROTECTED]> wrote:
>
>> > Sven Luther wrote:
>> >> Hi, please read the following, and this may give you more of an
>> >
the impression I got back
then. I didn't mean to contribute it, but it seems people are not
understanding.
Or maybe the DAMs want to teach us how to use a killfile?
Regards, Frank
[1] for being insubordinate to Frans?
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
quot; parties who decide internally whom they
nominate.
I do not want political parties in Debian.
> PS: Feel free to copy my part to a public list...
Done.
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
already led to drastic measures on behalf of
> the project)
What measures? Can you provide any links?
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
> you out, you shouldn't keep wasting your time.
Like, trying to get packages built that fail in a way that seems to
depend on the buildd environment, about which I know nothing?
I should go a way and have a cup of coffee now, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
ld someone please look into the buildd chroot on $foo and
tell me whether ...", and the people who I asked and are able to do that
will not do it, *nobody* will do it.
The case of buildds also seems to prove the opposite, but I'm not going
into that since too much issues are mixed there
nfrastructure teams? If no,
I cannot understand how you can answer like you did above.
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
Steve Langasek <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 15, 2007 at 10:00:25AM +0100, Frank Küster wrote:
>> Are you so overworked, or are you deliberately "forgetting"? It has
>> been suggested multiple times in the past to use existing or new
>> hardw
s for
i386 at all AFAIK. Moreover, the current buildd admin's apparently
don't have adequate time to communicate, which could be ameliorated by
adding people. Even if nobody had asked so far, we should ask people
who seem capable of doing it.
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
ome way to demonstrate
> you're right first.
That doesn't sound like a reason for prohibiting a particular persons
upload rights for binary-only uploads, just like a reason for
source-only uploads.
>> I mean, how dare he try to help the project in this way.
>
> There's not
happened to". It's for sale now, labeled "sarge".
No, it isn't labelled "sarge".
> Sorry to say such things and possibly raise conflictual feelings, but do you
> really feel this is *right*?
Even if it is not, it's off-topic on -legal. Please continue
ctual
text of the manual (in file emacs.texi) does not say that the manual
is under GPL, but still sounds DFSG free to me.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Thank you all for the many answers, also in private Mails!
Regards, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
stion, but also companies from Switzerland or
northeast France.
Thanks in advance, Frank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
35 matches
Mail list logo
