Re: Bits from the Debian GNU/kFreeBSD porters

[Joey Schulze]

GNU/kFreeBSD Maintainers wrote:
> Hello, Debian world!

Hello Anonymous,

This is a *very* strange from line that you surely should not use.
| From: GNU/kFreeBSD Maintainers 

Regards,

Joey

-- 
Linux - the choice of a GNU generation.

Please always Cc to me when replying to me on the lists.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bits from the Debian GNU/kFreeBSD porters

[Aurelien Jarno]

Joey Schulze a écrit :
> GNU/kFreeBSD Maintainers wrote:
>> Hello, Debian world!
> 
> Hello Anonymous,
> 
> This is a *very* strange from line that you surely should not use.
> | From: GNU/kFreeBSD Maintainers 

*I* have sent this message. I have choosen this From: line because I am
not *the* GNU/kFreeBSD Maintainer, we are a team. This team is reachable
through this email address. I also haven't actually wrote this message
(only made a few changes to it).

-- 
  .''`.  Aurelien Jarno | GPG: 1024D/F1BCDB73
 : :' :  Debian developer   | Electrical Engineer
 `. `'   [EMAIL PROTECTED] | [EMAIL PROTECTED]
   `-people.debian.org/~aurel32 | www.aurel32.net


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Message header fields (was: Bits from the Debian GNU/kFreeBSD porters)

[Ben Finney]

Aurelien Jarno <[EMAIL PROTECTED]> writes:

> Joey Schulze a écrit :
> > This is a *very* strange from line that you surely should not use.
> > | From: GNU/kFreeBSD Maintainers 
>
> *I* have sent this message.

Then your name, and your email address, belongs in the From field.

> I have choosen this From: line because I am not *the* GNU/kFreeBSD
> Maintainer, we are a team. This team is reachable through this email
> address. I also haven't actually wrote this message (only made a few
> changes to it).

Then that information should be made clear inside the *body* of the
message, along with whatever contact information you feel is
appropriate for the information in the body.

Meanwhile, the message header is about the message *as an email
message*, and the From field is supposed to be about the individual
who sent the message.

-- 
 \  "Smoking cures weight problems. Eventually."  -- Steven Wright |
  `\   |
_o__)  |
Ben Finney


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Message header fields (was: Bits from the Debian GNU/kFreeBSD porters)

[Lars Wirzenius]

On ma, 2007-02-05 at 20:46 +1100, Ben Finney wrote:
> Then your name, and your email address, belongs in the From field.

I agree with this. (And this AOL is the main point of this message. The
titbit below is just filler.)

> Meanwhile, the message header is about the message *as an email
> message*, and the From field is supposed to be about the individual
> who sent the message.

Technically, the From: header allows multiple addresses. I remember Ian
Jackson sending such a mail to a Debian list once and confusing the heck
out of the mailer I was using then. (Don't remember which one, might
have been of my aborted attempts at writing my own.)

-- 
You need fewer comments, if you choose your names carefully.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Message header fields (was: Bits from the Debian GNU/kFreeBSD porters)

[Pierre Habouzit]

On Mon, Feb 05, 2007 at 08:46:54PM +1100, Ben Finney wrote:
> Aurelien Jarno <[EMAIL PROTECTED]> writes:
> > Joey Schulze a écrit :
> > > This is a *very* strange from line that you surely should not use.
> > > | From: GNU/kFreeBSD Maintainers 
> >
> > *I* have sent this message.
> 
> Then your name, and your email address, belongs in the From field.

> > > | [-- PGP output follows (current time: lun 05 fév 2007 10:57:53 CET) --]
> > > | gpg: Signature made lun 05 fév 2007 09:59:01 CET using DSA key ID 
> > > F1BCDB73
> > > | gpg: Good signature from "Aurelien Jarno <[EMAIL PROTECTED]>"
> > > | [-- End of PGP output --]

  Given that Aurélien's message was signed with his key, I really find
that rant pointless.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgpscDJqplXvn.pgp
Description: PGP signature

Re: Message header fields

[Miles Bader]

Ben Finney <[EMAIL PROTECTED]> writes:
> Meanwhile, the message header is about the message *as an email
> message*, and the From field is supposed to be about the individual
> who sent the message.

... unless there's a "Sender:" header, in which case _that's_ the person
who send the email, and the "From:" header names the "true sender" of
the message.

[Every once in a while the Emacs mailing list gets email from Donald
Knuth, who as you may have heard, has sworn off the use of email.
In these messages, "From:" is Knuth himself, and "Sender:" is his
secretary, who is the person that actually sent the message.]

-Miles

p.s. The sig below is from my random sig-generator, which strangely
often seems to pick signatures which are apopos to the message at hand!

-- 
My books focus on timeless truths.  -- Donald Knuth


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bits from the Debian GNU/kFreeBSD porters

[Joey Schulze]

Aurelien Jarno wrote:
> Joey Schulze a écrit :
> > GNU/kFreeBSD Maintainers wrote:
> >> Hello, Debian world!
> > 
> > Hello Anonymous,
> > 
> > This is a *very* strange from line that you surely should not use.
> > | From: GNU/kFreeBSD Maintainers 
> 
> *I* have sent this message. I have choosen this From: line because I am
> not *the* GNU/kFreeBSD Maintainer, we are a team. This team is reachable
> through this email address. I also haven't actually wrote this message
> (only made a few changes to it).

Then you should send the message on behalf of the team but not hide
your identity, or let somebody else send it on behalf of the team.

Regards,

Joey

-- 
Linux - the choice of a GNU generation.

Please always Cc to me when replying to me on the lists.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: nsswitch.conf

[Russell Coker]

On Sunday 04 February 2007 19:48, Loïc Minier <[EMAIL PROTECTED]> wrote:
>  It is one way of seeing it, however you've got to see it from the other
>  way as well: how is it possible to integrate a new type of lookup
>  (mDNS) on desktop machines which want RendezVous / UPnP / mDNS to work?

It could ask via Debconf.

-- 
[EMAIL PROTECTED]
http://etbe.blogspot.com/  My Blog

http://www.coker.com.au/sponsorship.html Sponsoring Free Software development

Re: nsswitch.conf

[Loïc Minier]

On Mon, Feb 05, 2007, Russell Coker wrote:
> >  It is one way of seeing it, however you've got to see it from the other
> >  way as well: how is it possible to integrate a new type of lookup
> >  (mDNS) on desktop machines which want RendezVous / UPnP / mDNS to work?
> It could ask via Debconf.

 Yes, but it would need to be of low priority and the default would need
 to be to add the entries in nsswitch.conf.  I think it would be more
 interesting to address the question of why mdns/avahi didn't disable
 themselves on the system of the OP.

-- 
Loïc Minier <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#409640: ITP: mafft -- Multiple alignment program for amino acid or nucleotide sequences

[Charles Plessy]

Le Sun, Feb 04, 2007 at 11:05:08AM -0600, Ron Johnson a écrit :
> On 02/04/07 08:27, Charles Plessy wrote:
> > 
> > MAFFT is a multiple sequence alignment program for unix-like operating
> > systems.  It offers a range of multiple alignment methods, L-INS-i
> > (accurate; recommended for <200 sequences), FFT-NS-2 (fast; recommended
> > for >2,000 sequences), etc.
> 
> What do you use for nucleotides between 200 and 2000 sequences?

Hi,

thanks for the input. Here is a revised description:

 MAFFT is a multiple sequence alignment program, which offers three
 accuracy-oriented methods:
  * L-INS-i (probably most accurate; recommended for <200 sequences;
iterative refinement method incorporating local pairwise alignment
information),
  * G-INS-i (suitable for sequences of similar lengths; recommended for
<200 sequences; iterative refinement method incorporating global
pairwise alignment information),
  * E-INS-i (suitable for sequences containing large unalignable regions;
   recommended for <200 sequences),
 and five speed-oriented methods:
  * FFT-NS-i (iterative refinement method; two cycles only),
  * FFT-NS-i (iterative refinement method; max. 1000 iterations),
  * FFT-NS-2 (fast; progressive method),
  * FFT-NS-1 (very fast; recommended for >2000 sequences; progressive
method with a rough guide tree),
  * NW-NS-PartTree-1 (recommended for ∼50,000 sequences; progressive
method with the PartTree algorithm).
.
  Homepage: http://align.bmr.kyushu-u.ac.jp/mafft/software/

Have a nice day,

-- 
Charles Plessy
http://charles.plessy.org
Wako, Saitama, Japan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

debian rocks!

[Bruno Buys]

Just count one more happy debian user! Reinstalled yesterday, to switch 
from x86 sarge to amd64 etch. Everything went flawlessly.
Downloaded last netinst, booted it, hardware detected smoothly. The 
machine has two sound cards, both worked as before. I chose manual disk 
editing, reformatted both / and /usr/bin, left /backup and /home 
untouched. The new system was installed in like 15 min or less. Rebooted 
into new system, skipped tasksel completely, apt-get installed kde, 
x-window-system, xorg, and their fellows. No surprises. New kde found 
all my configs, got a desktop just identical to the previous. The only 
catch ins't debian related: vmware seems to not like my 
/usr/src/include/linux, and asks for a new linux/version.h. But i can 
live with that.
So, for now I can only thank the project for such a solid system. In the 
future, when I will be wealthier, I hope to donate regularly.




bruno
debian user and admirer


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: debian rocks!

[paddy]

On Mon, Feb 05, 2007 at 10:34:10AM -0200, Bruno Buys wrote:
> Just count one more happy debian user! Reinstalled yesterday, to switch 
> from x86 sarge to amd64 etch. Everything went flawlessly.
> Downloaded last netinst, booted it, hardware detected smoothly. The 
> machine has two sound cards, both worked as before. I chose manual disk 
> editing, reformatted both / and /usr/bin, left /backup and /home 
> untouched. The new system was installed in like 15 min or less. Rebooted 
> into new system, skipped tasksel completely, apt-get installed kde, 
> x-window-system, xorg, and their fellows. No surprises. New kde found 
> all my configs, got a desktop just identical to the previous. The only 
> catch ins't debian related: vmware seems to not like my 
> /usr/src/include/linux, and asks for a new linux/version.h. But i can 
> live with that.
> So, for now I can only thank the project for such a solid system. In the 
> future, when I will be wealthier, I hope to donate regularly.

Glad you're having an excellent experience! :-)

For extra points, go test the upgrade experience.

Regards,
Paddy


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

use "Sender:", please (Re: Message header fields)

[Oleg Verych]

> From: Miles Bader
> Newsgroups: gmane.linux.debian.devel.general
> Subject: Re: Message header fields
> Date: Mon, 05 Feb 2007 19:08:09 +0900

> Ben Finney <[EMAIL PROTECTED]> writes:
>> Meanwhile, the message header is about the message *as an email
>> message*, and the From field is supposed to be about the individual
>> who sent the message.
>
> ... unless there's a "Sender:" header, in which case _that's_ the person
> who send the email, and the "From:" header names the "true sender" of
> the message.

Yes, and this is stated on various RFCs on E-Mail and E-News...




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: debian rocks!

[Luca Brivio]

Il giorno Mon, 05 Feb 2007 10:34:10 -0200
Bruno Buys <[EMAIL PROTECTED]> ha scritto:

> skipped tasksel completely

That's bad! No idea about related efforts, but I guess one day tasksel
will not be for unexperienced users only.

> So, for now I can only thank the project for such a solid system. In
> the future, when I will be wealthier, I hope to donate regularly.

Good work is being done, I must thank all developers.
--
Luca Brivio


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: debian rocks!

[Shobhit Jindal]

a damm happy user here too :)

On 2/5/07, Bruno Buys <[EMAIL PROTECTED]> wrote:


Just count one more happy debian user! Reinstalled yesterday, to switch
from x86 sarge to amd64 etch. Everything went flawlessly.
Downloaded last netinst, booted it, hardware detected smoothly. The
machine has two sound cards, both worked as before. I chose manual disk
editing, reformatted both / and /usr/bin, left /backup and /home
untouched. The new system was installed in like 15 min or less. Rebooted
into new system, skipped tasksel completely, apt-get installed kde,
x-window-system, xorg, and their fellows. No surprises. New kde found
all my configs, got a desktop just identical to the previous. The only
catch ins't debian related: vmware seems to not like my
/usr/src/include/linux, and asks for a new linux/version.h.



i have been stuck to kernel 2.6.18-1-686 for the very same reason and
not upgrading
have searched a bit but to no avail.

But i can

live with that.
So, for now I can only thank the project for such a solid system. In the
future, when I will be wealthier, I hope to donate regularly.



bruno
debian user and admirer


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]





--
Registerd Linux User #426561
-
Shobhit Jindal
B.Tech. Part-III,
Department Of Electronics Engineering, ITBHU
INDIA

Upgrade Experiences (27 Sarges -> Etch, and counting)

[Maarten Verwijs]

hi,

I took the plunge and upgraded about half of the Lab here to Etch. 
This is about 27 machines to date, catering almost the same amount of
users. 

In totall there are 62 Debian Desktops here. Most of the Sarge-machines
recently upgraded were installed almost 2 years ago. 

All machines are Pentium IV's (2.8 through 3.2 Ghz), with 'round 1GB of
memory. 

A small list of software installed (before upgrade):
 - Gnome
 - KDE
 - XFCE
 - autofs
 - XFree86-4
 - subversion
 - NIS (yp)
 - Firefox
 - XEmacs
 - Emacs
 - Vim
 - Tetex
 - snmp
 - ntp
 - cups
 - openoffice (from backports)
 - Evolution

None of the users have expressed complaints or problems, even after
asking several times. If something was wrong with their XFCE/KDE/GNOME,
they'd let me know. :)

There are 2 things that require me to do some manual labour: 
* Opera. If opera is installed, upgrading from XFree86 to Xorg fails. Xorg
wants to remove a folder that Opera still has a symlink in. No biggy:
  remove opera prior to upgrading. 
  Luckily for Debian, this is not their problem: it's Opera's.

* Autofs and NIS. We still use NIS (yes we do) and NIS starts _after_
  autofs. This means autofs is not aware of the NIS information.
  Therefor: no /home/*
  This is a known bug, that i can work around using rc.local.

So as far as I'm concerned: Etch is ready to go!

Thanks for all the hard work! Debian is still the one and only
distribution for me. It Just Works. Thanks for your efforts.

If you need more details about the installed Sarge machines that were
upgraded, please let me know.


Kindest regards, 

Maarten



-- 
Maarten Verwijs 
Debian Administrator
Netherlands Institute for Space Research (www.sron.nl)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Sponsor needed?

[Rasmus Bøg Hansen]

Hi

I am a Debian user for 5 years and have fiddled a bit with Debian
packaging, though I have mostly only used my packages on my own
systems. I have contributed (though not a lot) to Debian with bug
reports, sometimes with patches.

I'd like to help Debian with a few packages (at first, at least),
though I would need a sponsor to do so.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409187
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408258

sigit (the first one) is already packaged and in my own repository
(http://www.zz9.dk/debian/), I have not started to package ipp2p and
probably won't as long as I don't have a sponsor.

If anyone will sponsor me, I'd be happy :-)

Regards
/Rasmus

-- 
Rasmus Bøg Hansen   || [EMAIL PROTECTED]
Harrestrupvang 13A, 2th || http://www.zz9.dk
2500 Valby  || 

Re: Sponsor needed?

[martin f krafft]

also sprach Rasmus Bøg Hansen <[EMAIL PROTECTED]> [2007.02.05.1622 +]:
> I'd like to help Debian with a few packages (at first, at least),
> though I would need a sponsor to do so.

Please read
http://people.debian.org/~mpalmer/debian-mentors_FAQ.html
and file proper RFS requests to debian-mentors. Debian-devel is not
the right list.

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`.   martin f. krafft <[EMAIL PROTECTED]>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems
 
unix, because rebooting is for adding new hardware.


signature.asc
Description: Digital signature (GPG/PGP)

Re: Bits from the Debian GNU/kFreeBSD porters

[Yavor Doganov]

Instead of arguing about the "From" header and generating traffic that
might be interesting, but not important at all, why don't we express
our warm gratitude and congratulate the Debian GNU/kFreeBSD team for
the *great* work they have done by making yet another variant of GNU a
reality?

Their work indirectly helps the GNU/Hurd port as well and is a solid
foundation for GNU/kNetBSD (which will eventually make using the GNU
system possible on many peculiar and rare machines).

Wonderful job, dear developers!  I thank you wholeheartedly.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Upgrade Experiences (27 Sarges -> Etch, and counting)

[Jon Dowland]

Maarten Verwijs wrote:
There are 2 things that require me to do some manual labour: 
* Opera. If opera is installed, upgrading from XFree86 to Xorg fails. Xorg

wants to remove a folder that Opera still has a symlink in. No biggy:
  remove opera prior to upgrading. 
  Luckily for Debian, this is not their problem: it's Opera's.
I'd forgotten about that migration and how painful it was. Opera is 
certainly not the only package which might cause problems here. It would 
be nice if this transition would be a bit more resistant to packages 
that can't be internally fixed to avoid that path.



--
Jon Dowland


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#409367: ITP: iceape-locales -- language packs for Iceape

[Robert Luberda]

On 2 Feb 2007 at 20:53, Daniel Baumann wrote:

Hi, 

> 
> please use iceape-l10n-* naming scheme like iceweasel locales do.

Yeah, it seems we have in Debian three different ways of naming 
translation packages:
  *-l10n-*  used for iceweasel and openoffice.org locales. 
  *-locale-*used for icedove and enigmail translations.
  *-i18n-*  used by kde packages.

Is there any particular reason for iceape-l10n-*  being a better
name then iceape-locale-*? 


Best Regards,
robert













-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#409367: ITP: iceape-locales -- language packs for Iceape

[Christian Perrier]

Quoting Robert Luberda ([EMAIL PROTECTED]):
> On 2 Feb 2007 at 20:53, Daniel Baumann wrote:
> 
> Hi, 
> 
> > 
> > please use iceape-l10n-* naming scheme like iceweasel locales do.
> 
> Yeah, it seems we have in Debian three different ways of naming 
> translation packages:
>   *-l10n-*used for iceweasel and openoffice.org locales. 
>   *-locale-*  used for icedove and enigmail translations.
>   *-i18n-*used by kde packages.
> 
> Is there any particular reason for iceape-l10n-*  being a better
> name then iceape-locale-*? 


"locale" usually is meant for "a locale", ie the definition of
parameters that characterize a langage/country combination

"l10n" is meant for "localisation" which means the action of
translating an internationalised software in a set of languages (as
well as make it support other locale-related parameters)

"i18n is meant for "internationalisation" which means the actions of
making a given software ready for localisation, but not the action of
localisation itself.


For all these reasons, "l10n" sounds to be the most appropriate to
me. I can guess that KDE packages' "i18n" is mostly here for
historical reasons, but I understand it as slightly incorrect.




signature.asc
Description: Digital signature

Re: Bits from the Debian GNU/kFreeBSD porters

[Darren Salt]

I demand that Aurelien Jarno may or may not have written...

> Joey Schulze a écrit :
>> GNU/kFreeBSD Maintainers wrote:
>>> Hello, Debian world!
>> Hello Anonymous,
>> This is a *very* strange from line that you surely should not use.
>> | From: GNU/kFreeBSD Maintainers 

> *I* have sent this message. I have chosen this From: line because I am not
> *the* GNU/kFreeBSD Maintainer, we are a team. This team is reachable
> through this email address. I also haven't actually written this message
> (only made a few changes to it).

The From header is fine, but you should also have used the Sender header.

-- 
| Darren Salt| linux or ds at  | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Lobby friends, family, business, government.WE'RE KILLING THE PLANET.

And now, excuse me while I interrupt myself.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Upgrade Experiences (27 Sarges -> Etch, and counting)

[Luis Matos]

Seg, 2007-02-05 às 17:23 +0100, Maarten Verwijs escreveu:
> hi,
> 
> I took the plunge and upgraded about half of the Lab here to Etch. 
> This is about 27 machines to date, catering almost the same amount of
> users. 

> In totall there are 62 Debian Desktops here. Most of the Sarge-machines
> recently upgraded were installed almost 2 years ago. 

as debian user ... i just have to say WOW!!! Etch is really in shape :P 

I want to congratulate ALL debian developers, they are doing awesome
work:P


> 
> All machines are Pentium IV's (2.8 through 3.2 Ghz), with 'round 1GB of
> memory. 
> 
> A small list of software installed (before upgrade):
>  - Gnome
>  - KDE
>  - XFCE
>  - autofs
>  - XFree86-4
>  - subversion
>  - NIS (yp)
>  - Firefox
>  - XEmacs
>  - Emacs
>  - Vim
>  - Tetex
>  - snmp
>  - ntp
>  - cups
>  - openoffice (from backports)
>  - Evolution
> 
> None of the users have expressed complaints or problems, even after
> asking several times. If something was wrong with their XFCE/KDE/GNOME,
> they'd let me know. :)
> 
> There are 2 things that require me to do some manual labour: 
> * Opera. If opera is installed, upgrading from XFree86 to Xorg fails. Xorg
>   wants to remove a folder that Opera still has a symlink in.
well ... this is an important move in this version :P

>  No biggy:
>   remove opera prior to upgrading. 
>   Luckily for Debian, this is not their problem: it's Opera's.
> 
> * Autofs and NIS. We still use NIS (yes we do) and NIS starts _after_
>   autofs. This means autofs is not aware of the NIS information.
>   Therefor: no /home/*
>   This is a known bug, that i can work around using rc.local.
> 
> So as far as I'm concerned: Etch is ready to go!
> 
> Thanks for all the hard work! Debian is still the one and only
> distribution for me. It Just Works. Thanks for your efforts.
> 
> If you need more details about the installed Sarge machines that were
> upgraded, please let me know.
> 
> 
> Kindest regards, 
> 
> Maarten
> 
> 
> 
> -- 
> Maarten Verwijs 
> Debian Administrator
> Netherlands Institute for Space Research (www.sron.nl)
> 
> 
-- 
Best Regards,
--
Luis Matos


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Upgrade Experiences (27 Sarges -> Etch, and counting)

[Steinar H. Gunderson]

On Mon, Feb 05, 2007 at 05:23:28PM +0100, Maarten Verwijs wrote:
> * Opera. If opera is installed, upgrading from XFree86 to Xorg fails. Xorg
>   wants to remove a folder that Opera still has a symlink in. No biggy:
>   remove opera prior to upgrading. 
>   Luckily for Debian, this is not their problem: it's Opera's.

FWIW, the latest Opera packages have fixed these issues.

> * Autofs and NIS. We still use NIS (yes we do) and NIS starts _after_
>   autofs. This means autofs is not aware of the NIS information.
>   Therefor: no /home/*
>   This is a known bug, that i can work around using rc.local.

AFAIK the new autofs maintainers are working on this together with the RMs.
The simplest fix should be moving autofs from 19autofs to 200autofs or
19zz_autofs or something to that effect.

/* Steinar */
-- 
Homepage: http://www.sesse.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Archive signing key for 2007?

[Joey Hess]

Seems you have still missed replying to this.

The 2006 key expires on the 7th and is still being used to sign the
archive.

If this is being used as an empirical way to find out what breakas, fine.
So far all I know of is debmirror << 20070123. But I wish you could at
least answer my mails about it.

Joey Hess wrote:
> I think you may have missed replying to this. I'd really like to know
> what's going to happen with the 2006 key expiry.
> 
> Joey Hess wrote:
> > Anthony Towns wrote:
> > > The key we'll be using (and indeed are already using) is available as:
> > > 
> > >   http://ftp-master.debian.org/archive-key-4.0.asc
> > > 
> > > It's expected to be valid until sometime after lenny is released.
> > 
> > I feel that we've been pretty miserable at communicating this stuff to
> > our developers and our users. While I knew about the etch key (hard to
> > miss it, given the ugly behavior it caused in apt when the archive was
> > signed with it, before it reached debian-archive-keyring), it wasn't at
> > all clear that it would be used to sign anything other than etch.
> > 
> > I've tried to update http://wiki.debian.org/SecureApt to reflect what
> > you've said.
> > 
> > I'm still not clear what will happen to the still existing yearly signing
> > key though. It's hard to predict what will happen if we reach
> > 2007-02-07 and 2D230C5F expires. I think that due to #400526, it will at
> > least break debmirror. If we're phasing out the yearly signing key, we
> > should be sure to stop signing the archive with it, before it expires.
> > Obviously, if we're not phasing it out, we have a rapidly shrinking
> > window to create the 2007 key.
> > 
> > -- 
> > see shy jo
> 
> 
> -- 
> see shy jo


-- 
see shy jo


signature.asc
Description: Digital signature

Re: Bug#409367: ITP: iceape-locales -- language packs for Iceape

[Daniel Baumann]

Robert Luberda wrote:
> Yeah, it seems we have in Debian three different ways of naming 
> translation packages:
>   *-l10n-*used for iceweasel and openoffice.org locales. 
>   *-locale-*  used for icedove and enigmail translations.
>   *-i18n-*used by kde packages.

afaik, there are only icedove packages left using *-locale-*, so i'd
like to get rid of the *-locale-* using packages completely now.

> Is there any particular reason for iceape-l10n-*  being a better
> name then iceape-locale-*? 

consistency. end users and dumb people like me like it when they don't
have to learn package naming schemes again and again for every group of
packages.

maybe, we can even have a consistency within all debian packages
for lenny (I don't care so much if it is *-i18n-* or *-l10n-*).

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Archive signing key for 2007?

[Frans Pop]

On Monday 05 February 2007 22:14, Joey Hess wrote:
> If this is being used as an empirical way to find out what breakas,
> fine. So far all I know of is debmirror << 20070123.

Which means all Sarge and Etch boxes running debmirror

This includes my (partial) local mirror. Let's just say that this would 
seriously impact my work on D-I and the release.

Cheers,
FJP


pgp26EGYYk6ke.pgp
Description: PGP signature

Re: Archive signing key for 2007?

[Steve Langasek]

On Mon, Feb 05, 2007 at 04:14:07PM -0500, Joey Hess wrote:
> Seems you have still missed replying to this.

> The 2006 key expires on the 7th and is still being used to sign the
> archive.

> If this is being used as an empirical way to find out what breakas, fine.
> So far all I know of is debmirror << 20070123. But I wish you could at
> least answer my mails about it.

FWIW, an additional problem was brought up on IRC last night -- apparently
the new key is not yet being used to sign the security.d.o archive, only the
old key that will be expiring shortly.

> Joey Hess wrote:
> > I think you may have missed replying to this. I'd really like to know
> > what's going to happen with the 2006 key expiry.
> > 
> > Joey Hess wrote:
> > > Anthony Towns wrote:
> > > > The key we'll be using (and indeed are already using) is available as:
> > > > 
> > > > http://ftp-master.debian.org/archive-key-4.0.asc
> > > > 
> > > > It's expected to be valid until sometime after lenny is released.
> > > 
> > > I feel that we've been pretty miserable at communicating this stuff to
> > > our developers and our users. While I knew about the etch key (hard to
> > > miss it, given the ugly behavior it caused in apt when the archive was
> > > signed with it, before it reached debian-archive-keyring), it wasn't at
> > > all clear that it would be used to sign anything other than etch.
> > > 
> > > I've tried to update http://wiki.debian.org/SecureApt to reflect what
> > > you've said.
> > > 
> > > I'm still not clear what will happen to the still existing yearly signing
> > > key though. It's hard to predict what will happen if we reach
> > > 2007-02-07 and 2D230C5F expires. I think that due to #400526, it will at
> > > least break debmirror. If we're phasing out the yearly signing key, we
> > > should be sure to stop signing the archive with it, before it expires.
> > > Obviously, if we're not phasing it out, we have a rapidly shrinking
> > > window to create the 2007 key.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: /foo has been mounted xx times... check forced

[Jörg Sommer]

Hello,

Evgeni Golov <[EMAIL PROTECTED]> wrote:
> On Sat, 3 Feb 2007 21:45:49 +0100 Nico Golde wrote:
>
>> Acpid doesn't load modules, it only listens to events and 
>> executes programs.
>
> But the init-script does:
>
> # As the name says. If the kernel supports modules, it'll try to load
> # the ones listed in "MODULES".
> load_modules() {
> ...
> }

Maybe checkfs.sh could simply run on_ac_power instead of checking if it
exists. This would enable the user to add a on_ac_power function to
/etc/defaults/rcS which is sourced by checkfs.sh. There you can write the
modprobe and relay the question to /usr/bin/ac_on_power. Or what I as a
PowerPC user would do, write there a piece of code to read the state form
the pmu.

Schöne Grüße, Jörg.
-- 
Unsere Zweifel sind Verräter und oft genug verspielen wir den möglichen
Gewinn, weil wir den Versuch nicht wagen.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#409367: ITP: iceape-locales -- language packs for Iceape

[Mike Hommey]

On Mon, Feb 05, 2007 at 10:20:06PM +0100, Daniel Baumann <[EMAIL PROTECTED]> 
wrote:
> Robert Luberda wrote:
> > Yeah, it seems we have in Debian three different ways of naming 
> > translation packages:
> >   *-l10n-*  used for iceweasel and openoffice.org locales. 
> >   *-locale-*used for icedove and enigmail translations.
> >   *-i18n-*  used by kde packages.
> 
> afaik, there are only icedove packages left using *-locale-*, so i'd
> like to get rid of the *-locale-* using packages completely now.
> 
> > Is there any particular reason for iceape-l10n-*  being a better
> > name then iceape-locale-*? 
> 
> consistency. end users and dumb people like me like it when they don't
> have to learn package naming schemes again and again for every group of
> packages.
> 
> maybe, we can even have a consistency within all debian packages
> for lenny (I don't care so much if it is *-i18n-* or *-l10n-*).

not only for names but for short descriptions[1], or even better,
long descriptions, too

Mike

1. "development files for libfoo", "libfoo -- development files",
"Header files and static libraries for libfoo", "libfoo (development
headers)", "libfoo (development package)", etc.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#409849: ITP: afni -- toolkit for analyzing and visualizing functional MRI data

[Michael Hanke]

Package: wnpp
Severity: wishlist
Owner: Michael Hanke <[EMAIL PROTECTED]>

* Package name: afni
  Version : 2006.12.22.0933
  Upstream Author : Robert Cox et al. <[EMAIL PROTECTED]>
* URL : http://afni.nimh.nih.gov/
* License : GPL (sources might contain some OCL licensed docs)
  Programming Lang: C
  Description : toolkit for analyzing and visualizing functional MRI data

AFNI is an environment for processing and displaying functional MRI data. 
It provides a complete analysis toolchain, including 3D cortical surface models,
and mapping of volumetric data (SUMA).

In addition to its own format AFNI understands the NIfTI format and is
therefore easily usable in combination with FSL and Freesurfer.



The package will be maintained by Yaroslav Halchenko
<[EMAIL PROTECTED]> and me. 

Cheers,

Michael


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (600, 'testing'), (200, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bits from the Debian GNU/kFreeBSD porters

[Gustavo Franco]

On 2/5/07, GNU/kFreeBSD Maintainers  wrote:

Hello, Debian world!

This is a status update for the Debian GNU/FreeBSD port[1]. This port
consists of two architectures: kfreebsd-i386 and kfreebsd-amd64.
(...)


Do you know if there is a way to build Debian GNU/kFreeBSD Live cd
images using live-package's svn tree ?

I hope to see kfreebsd-i386 and kfreebsd-amd64 as real candidates to
be released in parallel with Lenny though. Btw, don't you have a
DD-accessuible kfreebsd-amd64 machine? Are you needing this?

regards,
-- stratus
http://stratusandtheswirl.blogspot.com


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: nsswitch.conf

[Henrique de Moraes Holschuh]

On Mon, 05 Feb 2007, Loïc Minier wrote:
>  Yes, but it would need to be of low priority and the default would need
>  to be to add the entries in nsswitch.conf.  I think it would be more

I think I'd rather have it medium or high, with a default to *disabled*.
Yes, the normal would be "Low", but I do understand the idea behind avahi.

However, a default of enabled for something that is going to be pulled in in
most systems AND that adds itself to nsswitch.conf is NOT ok IMO.  You see,
every crap that gets into nsswitch.conf ends up dynamically linked to
potentially every frigging glibc-using app, and we don't have many apps (if
any) that *don't* link to glibc.  Not all of them will try to use the
resolver, but a damn big ammount of them will.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: nsswitch.conf

[Russ Allbery]

Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:

> However, a default of enabled for something that is going to be pulled
> in in most systems

If mDNS is going to be pulled in on most systems, that is itself a
potential problem.  What's pulling it in?  If it's a desktop task or the
like, that doesn't worry me too much, but I don't want mDNS on my servers.
Its only function there would be a potential security vulnerability.

avahi-daemon got pulled into a few of my systems a while back in the etch
development cycle, but it looks like that bug has since been fixed.
Currently I don't see anything that would cause this package to be
installed unless people are seeking it out, but I haven't done an
exhaustive analysis.

-- 
Russ Allbery ([EMAIL PROTECTED])   


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: nsswitch.conf

[Brian May]

> "Loïc" == Loïc Minier <[EMAIL PROTECTED]> writes:

Loïc>  #406198 is about reverting the changes it does to
Loïc> nsswitch.conf on removal, not about not updating
Loïc> nsswitch.conf, but yes, libnss-mdns edits the conffile of
Loïc> another package.

Packages shouldn't be editing conffiles (as opposed to configuration
files that are not conffiles), period. This is against policy. It
results in conflicts occurring the next time the package updates the
file.

However, it is listed as "obsolete", so I suspect this means it is no
longer a conffile:


Package: base-files
...
Conffiles:
...
 /etc/nsswitch.conf 109e33e2c91d1853b5bc56078a96aa18 obsolete


...which in turn would make your confirmation invalid ;-).

Regardless, I don't feel very strongly on the issues I raised. I think
it might be good if all libnss-* packages were consistent in the way
they handle (or don't handle) automatic updates to /etc/nsswitch.conf.
-- 
Brian May <[EMAIL PROTECTED]>

Re: Upgrade Experiences (27 Sarges -> Etch, and counting)

[Frank Küster]

Maarten Verwijs  farwise.org> writes:

> A small list of software installed (before upgrade):
[...]
>  - Tetex

You could give texlive a try.  It's more up-to-date than teTeX, it's more
comprehensive, and it's going to be the default for lenny, anyway.

Unfortunately, there are still a couple of packages that only depend on teTeX
and cannot be installed with TeXLive - in most cases, there are updated packages
available at tug.org, please read http://www.tug.org/texlive/debian.html

Regards, Frank



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]