Re: Maintainers Guide

2006-03-26 Thread Frank Küster
Joerg Jaspert <[EMAIL PROTECTED]> wrote: > On 10605 March 1977, Nico Golde wrote: > >> * Joerg Jaspert <[EMAIL PROTECTED]> [2006-03-26 20:31]: >>> A while ago Peter 'weasel' Palfrader wrote a nice little "How (not) to >>> write copyright files"[1]. Please read that *now*. >>> [1] http://lists.debi

Re: project machine architecture aliases

2006-03-26 Thread Raphael Hertzog
On Mon, 27 Mar 2006, Hamish Moffatt wrote: > > Questions/Proposals like these are not concerning Debian development per > > se and would be better suited for debian-project. > > I disagree. It certainly does concern development. The line is blur, and when don't know really of which side it should

Re: How (not) to write copyright files - take two

2006-03-26 Thread Russ Allbery
Charles Plessy <[EMAIL PROTECTED]> writes: > I am packaging a program for debian, and wrote a manpage and two patches > for making it compile with libwxwindows. I am not very interested in > being the author list: I would be a bit ashamed that my name would > appear more frequently that the author

Re: Maintainers Guide (was: How (not) to write copyright files - take two)

2006-03-26 Thread Yaroslav Halchenko
I just can't locate copyright statement anywhere within the package -- only license file (MPL 1.1/GPL 2.0/LGPL 2.1) is copyright assumed to belong to upstream author? what years then should be mentioned? -- .-. =-- /v\

Re: How (not) to write copyright files - take two

2006-03-26 Thread Charles Plessy
On Sun, Mar 26, 2006 at 08:29:48PM +0200, Joerg Jaspert wrote : > > In many packages there is more than one author, more than one > copyright-holder and more than one license. Do not miss to list them > all, even if that other license is just for one file. Yes, any single > file is important. Dea

Bug#359137: general: Box does not switch of on halt

2006-03-26 Thread Micha Lenk
Hi Andreas, uh, it's not that common to get general linux support using the debian BTS, isn't it? Andreas Tille wrote: > [...] > since about three weeks I observe problems when issuing halt > on three different testing-boxes (two older desktops without ACPI > and one laptop with ACPI). The comp

Re: project machine architecture aliases

2006-03-26 Thread Hamish Moffatt
On Mon, Mar 27, 2006 at 12:59:34AM +0200, Michael Banck wrote: > On Sun, Mar 26, 2006 at 03:09:11PM -0500, Steve M. Robbins wrote: > > Wouldn't it be nice if I could just do: "ssh glooble.dev.debian.org" > > and have that be an alias to some machine of architecture glooble? > > Questions/Proposals

Re: project machine architecture aliases

2006-03-26 Thread Michael Banck
On Sun, Mar 26, 2006 at 03:09:11PM -0500, Steve M. Robbins wrote: > Wouldn't it be nice if I could just do: "ssh glooble.dev.debian.org" > and have that be an alias to some machine of architecture glooble? Questions/Proposals like these are not concerning Debian development per se and would be bet

Re: How (not) to write copyright files - take two

2006-03-26 Thread Christoph Berg
Re: Raphael Hertzog 2006-03-26 <[EMAIL PROTECTED]> > Each package with translations has several dozens of copyright holder, > we don't have to keep that list in the copyright file, do we ? And we ignore any (C) FSF in generated autofoo stuff. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/

Re: project machine architecture aliases

2006-03-26 Thread Thiemo Seufer
On Sun, Mar 26, 2006 at 03:09:11PM -0500, Steve M. Robbins wrote: > Hi, > > I have another "wishful thinking" idea for build machines to float. > > Suppose I get a bug report saying my package has failed to build on > architecture glooble. I don't personally have a globle machine. To > debug th

Re: idea for project machines

2006-03-26 Thread Christoph Berg
Re: Steve M. Robbins 2006-03-25 <[EMAIL PROTECTED]> > Wouldn't it be nice if you could simply "sudo apt-get install " > yourself? Is it feasible to have at least some of the sid chroots > allow this? Alternatively, how about "sudo pbuilder login ..."? I was ranting about that on irc before,

project machine architecture aliases

2006-03-26 Thread Steve M. Robbins
Hi, I have another "wishful thinking" idea for build machines to float. Suppose I get a bug report saying my package has failed to build on architecture glooble. I don't personally have a globle machine. To debug the problem, I need to fire up www.debian.org/devel, find the link to the list of

Bug#359141: ITP: enemylines7 -- first person 3d-shooter game

2006-03-26 Thread Gonéri Le Bouder
Package: wnpp Severity: wishlist Owner: "Gonéri Le Bouder" <[EMAIL PROTECTED]> * Package name: enemylines7 Version : 0.5 Upstream Author : Raphael Pikrin * URL : http://raum1.memebot.com/enemylines/part7.html * License : GPL Description : first person 3d

Bug#359137: general: Box does not switch of on halt

2006-03-26 Thread Andreas Tille
Package: general Severity: important Hi, I tried to clarify in a discussion on debian-devel what package might be responsible for the problem I face on *all* three machines I updated to testing at a date I do not exactly remember in February this year (sorry for the vague description). I just co

Re: Maintainers Guide (was: How (not) to write copyright files - take two)

2006-03-26 Thread Jeremy Stanley
On Sun, Mar 26, 2006 at 08:48:31PM +0200, Nico Golde wrote: > * Joerg Jaspert <[EMAIL PROTECTED]> [2006-03-26 20:31]: > > A while ago Peter 'weasel' Palfrader wrote a nice little "How (not) to > > write copyright files"[1]. Please read that *now*. > > > > [1] http://lists.debian.org/debian-devel-a

Re: When to drop/split/summ changelog files

2006-03-26 Thread Nico Golde
Hallo Antti, * Antti-Juhani Kaijanaho <[EMAIL PROTECTED]> [2006-03-26 20:52]: > Nico Golde wrote: > >I thought about changelogs like: > >2001-04-06 mitch 20:18:29Michael Natterer > ><[EMAIL PROTECTED]> > > This is not a Debian changelog, and your original question > talked about

Re: How (not) to write copyright files - take two

2006-03-26 Thread Raphael Hertzog
On Sun, 26 Mar 2006, Joerg Jaspert wrote: > In many packages there is more than one author, more than one > copyright-holder and more than one license. Do not miss to list them > all, even if that other license is just for one file. Yes, any single > file is important. Each package with translatio

Re: Maintainers Guide

2006-03-26 Thread Joerg Jaspert
On 10605 March 1977, Nico Golde wrote: > * Joerg Jaspert <[EMAIL PROTECTED]> [2006-03-26 20:31]: >> A while ago Peter 'weasel' Palfrader wrote a nice little "How (not) to >> write copyright files"[1]. Please read that *now*. >> [1] http://lists.debian.org/debian-devel-announce/2003/12/msg7.htm

Re: When to drop/split/summ changelog files

2006-03-26 Thread Antti-Juhani Kaijanaho
Nico Golde wrote: I thought about changelogs like: 2001-04-06 mitch 20:18:29Michael Natterer <[EMAIL PROTECTED]> This is not a Debian changelog, and your original question talked about those. Many upstreams split their own changelogs occasionally. If you like, suggest to your

Maintainers Guide (was: How (not) to write copyright files - take two)

2006-03-26 Thread Nico Golde
Hi, * Joerg Jaspert <[EMAIL PROTECTED]> [2006-03-26 20:31]: > A while ago Peter 'weasel' Palfrader wrote a nice little "How (not) to > write copyright files"[1]. Please read that *now*. > > [1] http://lists.debian.org/debian-devel-announce/2003/12/msg7.html [...] Why not add this to the New

Re: When to drop/split/summ changelog files

2006-03-26 Thread Nico Golde
Hi, * Joerg Jaspert <[EMAIL PROTECTED]> [2006-03-26 20:32]: > On 10605 March 1977, Nico Golde wrote: [...] > > Is there a way to handle these changelog entries which bloat > > the package and contain only information which are too old > > to be useful or is it ok if for example a changelog file

Re: How (not) to write copyright files - take two

2006-03-26 Thread Florian Weimer
* Joerg Jaspert: > As *many* rejects out of the NEW-Queue[2] are still due to broken or > incomplete copyright-files - lets refresh that information. Just for clarification, since there seems to be this increased interest in copyright notices: Do developers need to verify that these copyright not

Re: When to drop/split/summ changelog files

2006-03-26 Thread Joerg Jaspert
On 10605 March 1977, Nico Golde wrote: > what would be the appropriate way to handle large and old > debian changelog files. Keep. > Is there a way to handle these changelog entries which bloat > the package and contain only information which are too old > to be useful or is it ok if for exam

When to drop/split/summ changelog files

2006-03-26 Thread Nico Golde
Hi, what would be the appropriate way to handle large and old debian changelog files. I mean there are package with very active upstream and years old changelog which grew and grew over the years. Is there a way to handle these changelog entries which bloat the package and contain only informa

Re: Bug#358003: ITP: ttf-dzongkha -- TrueType fonts for Dzongkha language

2006-03-26 Thread Darren Salt
I demand that Adam Borowski may or may not have written... [snip] > I don't believe that anyone can learn even an alphabet without knowing its > name. I was going to say that you're wrong, but then it occurred to me that the first one that most of us learn is called "the alphabet". ;-) -- | Dar

Re: Bug#358003: ITP: ttf-dzongkha -- TrueType fonts for Dzongkha language

2006-03-26 Thread Lars Wirzenius
su, 2006-03-26 kello 15:07 +0200, Adam Borowski kirjoitti: > Why would viewing the document matter if you don't know the language or > even the script in the first place? To get out of it what I can. Sometimes it is surprisingly much, even when one doesn't understand the language or the script. T

Re: Bug#358003: ITP: ttf-dzongkha -- TrueType fonts for Dzongkha language

2006-03-26 Thread Adam Borowski
On Sun, 26 Mar 2006, Lars Wirzenius wrote: su, 2006-03-26 kello 04:11 -0600, Peter Samuelson kirjoitti: OTOH, if you have no idea what language or what country the font pertains to, why would you want that font? It is not inconceivable that one could stumble on a document from Bhutan, and want

Re: Bug#358003: ITP: ttf-dzongkha -- TrueType fonts for Dzongkha language

2006-03-26 Thread Lars Wirzenius
su, 2006-03-26 kello 13:19 +0200, David Weinehall kirjoitti: > On Sun, Mar 26, 2006 at 02:02:43PM +0300, Lars Wirzenius wrote: > > This is not what I would call a common use case, but it exists. I've > > been in the situation once searching for a "Russian" font, when I > > should've been looking fo

Re: Bug#358003: ITP: ttf-dzongkha -- TrueType fonts for Dzongkha language

2006-03-26 Thread David Weinehall
On Sun, Mar 26, 2006 at 02:02:43PM +0300, Lars Wirzenius wrote: > su, 2006-03-26 kello 04:11 -0600, Peter Samuelson kirjoitti: > > > On Tue, Mar 21, 2006 at 07:08:02AM +0100, Christian Perrier wrote: > > > > Well, I have one very little argument against doing so: why do it > > > > for Dzongkha and

Re: Bug#358003: ITP: ttf-dzongkha -- TrueType fonts for Dzongkha language

2006-03-26 Thread Lars Wirzenius
su, 2006-03-26 kello 04:11 -0600, Peter Samuelson kirjoitti: > > On Tue, Mar 21, 2006 at 07:08:02AM +0100, Christian Perrier wrote: > > > Well, I have one very little argument against doing so: why do it > > > for Dzongkha and why not do it for, say, French...:-) > > [Lionel Elie Mamane] > > Becau

Re: idea for project machines

2006-03-26 Thread Reinhard Tartler
>> Create a new custom chroot with the packages preinstalled on demand. > Sounds like a use-case for combining pbuilder and cowdancer (or lvm > snapshots). No time-consuming tarball extraction, disk usage is reduced > and the original chroot is untouched. Or just plain schroot on lvm snapshots. It

Re: Bug#358003: ITP: ttf-dzongkha -- TrueType fonts for Dzongkha language

2006-03-26 Thread Peter Samuelson
> On Tue, Mar 21, 2006 at 07:08:02AM +0100, Christian Perrier wrote: > > Well, I have one very little argument against doing so: why do it > > for Dzongkha and why not do it for, say, French...:-) [Lionel Elie Mamane] > Because "French" is the adjective in English (the language the > package desc

Re: idea for project machines

2006-03-26 Thread Laszlo Boszormenyi
On Sun, 2006-03-26 at 00:48 -0500, Steve M. Robbins wrote: > Laszlo said: > > I was in this situation some time already. But it isn't a solution to > > get sudo apt-get install rights. Someone who may have a build-conflict > > with your build-depends won't be happy if you install that package(s).