Bug#637805: general: can't mount a usb drive as a non-root user

2011-08-15 Thread Christian PERRIER
reassign 637805 ntfs-3g thanks This either belongs to btfs-3gor some local problem that would make /dev/sdc* devices to not have the right permissions Reassigning. At least, please provide more information. Output from "ls -l /dev/sdc*" as well as "id" is imho the minimum. signature.

Processed: Re: Bug#637805: general: can't mount a usb drive as a non-root user

2011-08-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 637805 ntfs-3g Bug #637805 [general] general: can't mount a usb drive as a non-root user Bug reassigned from package 'general' to 'ntfs-3g'. > thanks Stopping processing here. Please contact me if you need assistance. -- 637805: http://

Re: Inactive maintainer for teamspeak packages

2011-08-15 Thread Jan Hauke Rahm
On Sat, Aug 13, 2011 at 10:27:08AM +0200, Stephan Windmüller wrote: > For more than a half year I am monitoring the state of the non-free > teamspeak packages. A new upstream version is available for more than a > year (bug #594318) and there is also a grave bug with an attached patch > (bug #59830

Re: The archive now supports xz compression

2011-08-15 Thread Charles Plessy
Le Mon, Aug 15, 2011 at 01:48:50AM +0200, Adam Borowski a écrit : > > * A year ago, I repacked CD1, .xz took 66% space needed by .gz. This time, > on the whole archive, gains are somewhat smaller: 72%. I guess that CD1 > is code-heavy while packages of lower priorities tend to have more data

Re: The archive now supports xz compression

2011-08-15 Thread Bálint Réczey
Hi, 2011/8/15 Eduard Bloch : > #include > * Roger Leigh [Sun, Aug 14 2011, 11:01:11PM]: >> On Sun, Aug 14, 2011 at 09:19:02PM +0200, Lucas Nussbaum wrote: >> > On 11/08/11 at 19:52 +, Philipp Kern wrote: > >> > Wouldn't it be better to get more buildds for those archs, then? >> > That would be

Re: The archive now supports xz compression

2011-08-15 Thread Adam Borowski
On Mon, Aug 15, 2011 at 06:38:28AM +0200, Tollef Fog Heen wrote: > ]] Adam Borowski > > | Does someone have an estimate how many core-hours would an archive rebuild > | on such a machine take? Folks on IRC quoted numbers like "340", "240 on a > | very fast box", "more like 1500" -- too div

Re: The archive now supports xz compression

2011-08-15 Thread Luca Capello
Hi there! On Mon, 15 Aug 2011 10:16:55 +0200, Charles Plessy wrote: > Also, many files in /usr/share/doc are gzipped as per §12.3; [...] > - Most systems have enough space to keep them uncompressed, Which alone is not a good reason to not compress them. > Perhaps we could consider allowing xz c

Bug#637862: ITP: mp3fs -- FUSE filesystem for transcoding FLAC to MP3 on the fly

2011-08-15 Thread Alessio Treglia
Package: wnpp Severity: wishlist Owner: Alessio Treglia * Package name: mp3fs Version : 0.30 Upstream Author : Kristofer Henriksson * URL : http://mp3fs.sourceforge.net * License : GPL Programming Lang: C Description : FUSE filesystem for transcoding FL

Re: The archive now supports xz compression

2011-08-15 Thread Andrey Rahmatullin
On Mon, Aug 15, 2011 at 11:25:42AM +0200, Luca Capello wrote: > What about zless & Co.? Are they available for xz as well? xz-utils contains xzless, xzcat etc. -- WBR, wRAR signature.asc Description: Digital signature

Re: use flags? (was: Re: Introducing Build-Recommends / Build-Core-Depends?)

2011-08-15 Thread Steve McIntyre
Eugene V. Lyubimkin wrote: > >If we accept the idea there's now more than one way to build the >package, I would like us do not limit the number of ways to '2' but >rather extend the prospoal to set up something similar to Gentoo's USE >flags. The advantages of that idea: > >- porters/buildds/loca

Bug#637866: ITP: rastertosag-gdi -- printer driver for Ricoh Aficio SP1100s/SP1100

2011-08-15 Thread Didier Raboud
Package: wnpp Severity: wishlist Owner: Didier Raboud Package name: rastertosag-gdi Version : 0.1 Upstream Author : palz URL : http://www.openprinting.org/driver/rastertosag-gdi/ License : GPL Programming Lang: Python Description : printer driver

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Steve McIntyre
Andreas Barth wrote: >* Colin Watson (cjwat...@debian.org) [110813 15:27]: >> On Sat, Aug 13, 2011 at 01:28:36PM +0200, Andreas Barth wrote: >> > During bootstraping a new architecture, there are sometimes ugly >> > build-dependency-loops (usually involving generating documentation >> > for the cor

mentors.debian.net: login problems

2011-08-15 Thread Andrew O. Shadoura
Hello, Since mentors.d.n was upgraded, I can't log in. Even if I reset my password, I can't log in with a temporary one. Any ideas what can it be? -- WBR, Andrew signature.asc Description: PGP signature

Re: mentors.debian.net: login problems

2011-08-15 Thread Jonathan Wiltshire
On Mon, Aug 15, 2011 at 01:49:04PM +0300, Andrew O. Shadoura wrote: > Since mentors.d.n was upgraded, I can't log in. Even if I reset my > password, I can't log in with a temporary one. > > Any ideas what can it be? Please contact the service maintainers directly: http://mentors.debian.net/contac

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Carsten Hey
* Andreas Barth [2011-08-13 13:28 +0200]: > Also, the binary packages in the debian/control template could have > Build-Depends specified which means that they should only be built if > those packages are actually installed ... An optional "Build-Depends:" field per binary package as you described

Re: use flags? (was: Re: Introducing Build-Recommends / Build-Core-Depends?)

2011-08-15 Thread Andreas Barth
* Steve McIntyre (st...@einval.com) [110815 12:27]: > Eugene V. Lyubimkin wrote: > >Source: fbreader > >Build-Depends-Core: debhelper (>= 7), libbz2-dev > >Build-Depends-Qt3: libqt3-mt-dev > >Build-Depends-Qt4: libqt4-dev > >Build-Depends-Gtk2: libgtk2.0-dev > I can see this turning into a large m

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Andreas Barth
* Steve McIntyre (st...@einval.com) [110815 12:30]: > Andreas Barth wrote: > >Generic options are usually better IMHO, but well - YMMV. > > Often, yes. But also often at extra cost. No doubt about that. > Where is the added benefit > here - i.e. what are the use cases? I'm not sure I could sp

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Carsten Hey
* Steve McIntyre [2011-08-15 11:12 +0100]: > Andreas Barth wrote: > >Generic options are usually better IMHO, but well - YMMV. > > Often, yes. But also often at extra cost. Where is the added benefit > here - i.e. what are the use cases? I'm 100% behind making the > bootstrap phase more simple, but

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Andreas Barth
* Carsten Hey (cars...@debian.org) [110815 13:36]: > An optional "Build-Depends:" field per binary package as you described > is essentially the same as the following, with the notable difference, > that the below could appear as it is in the output of, i.e., apt-cache > showsrc without requiring m

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Carsten Hey
* Andreas Barth [2011-08-15 13:46 +0200]: > * Carsten Hey (cars...@debian.org) [110815 13:36]: > > An optional "Build-Depends:" field per binary package as you described > > is essentially the same as the following, with the notable difference, > > that the below could appear as it is in the output

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Andreas Barth
* Carsten Hey (cars...@debian.org) [110815 14:36]: > * Andreas Barth [2011-08-15 13:46 +0200]: > > * Carsten Hey (cars...@debian.org) [110815 13:36]: > > > An optional "Build-Depends:" field per binary package as you described > > > is essentially the same as the following, with the notable differe

Re: mentors.debian.net: login problems

2011-08-15 Thread Asheesh Laroia
Excerpts from Jonathan Wiltshire's message of Mon Aug 15 06:54:21 -0400 2011: > On Mon, Aug 15, 2011 at 01:49:04PM +0300, Andrew O. Shadoura wrote: > > Since mentors.d.n was upgraded, I can't log in. Even if I reset my > > password, I can't log in with a temporary one. > > > > Any ideas what can i

Re: The archive now supports xz compression

2011-08-15 Thread Hideki Yamane
Hi, I'm happy to hear xz support. Some font packages can get huge profit with this (e.g. fonts-vlgothic: 4924KB -> 2132KB (half! :) On Thu, 11 Aug 2011 19:52:46 + (UTC) Philipp Kern wrote: > It takes a lot longer to compress on slower architectures (i.e. on the > buildds), though. If t

Bug#637887: ITP: pkg-printing-tools -- various packaging tools for the Debian Printing Team

2011-08-15 Thread Didier Raboud
Package: wnpp Severity: wishlist Owner: Didier Raboud Package name: pkg-printing-tools Version : 0.1 Upstream Author : Didier Raboud License : GPL-3+ Programming Lang: Perl, etc. Description : various packaging tools for the Debian Printing Team This native p

Introduction of a "lock" group

2011-08-15 Thread Roger Leigh
Hi folks, Fedora has moved to having /var/lock (now /run/lock) owned by root:lock 0775 rather than root:root 01777. This has the advantage of making a system directory writable only by root or setgid lock programs, rather than the whole world. However, due to the potential for privilege escalati

Bug#637892: ITP: python-formalchemy -- auto-generation and customizable form

2011-08-15 Thread XuZhiXiang
Package: wnpp Severity: wishlist Owner: XuZhiXiang I'm a new packager in debian, and I wanna make this package * Package name: python-formalchemy Version : 1.4.1 Upstream Author : Alexandre Conrad, Jonathan Ellis, Gaël Pasgrimaud * URL : http://docs.formalchemy.or

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Julien Cristau
On Mon, Aug 15, 2011 at 13:42:20 +0200, Andreas Barth wrote: > I'm not sure I could speak about "cases", but an obvious use case > aside from bootstrapping is backporting, where I could just drop off > dependencies I'm not going to use instead of looking at the code and > figuring out if it's easi

Re: Introduction of a "lock" group

2011-08-15 Thread Andreas Barth
* Roger Leigh (rle...@codelibre.net) [110815 17:12]: > Are these any other downsides we need to consider? One issue is the > existence of badly broken programs³, which make stupid assumptions > about lockfiles. This will break all existing programms on an partial upgrades. There are three ways to

Re: Introduction of a "lock" group

2011-08-15 Thread Iustin Pop
On Mon, Aug 15, 2011 at 04:11:49PM +0100, Roger Leigh wrote: > Hi folks, > > Fedora has moved to having /var/lock (now /run/lock) owned by > root:lock 0775 rather than root:root 01777. This has the advantage > of making a system directory writable only by root or setgid lock > programs, rather th

Re: Introduction of a "lock" group

2011-08-15 Thread Roger Leigh
On Mon, Aug 15, 2011 at 06:03:59PM +0200, Iustin Pop wrote: > On Mon, Aug 15, 2011 at 04:11:49PM +0100, Roger Leigh wrote: > > Hi folks, > > > > Fedora has moved to having /var/lock (now /run/lock) owned by > > root:lock 0775 rather than root:root 01777. This has the advantage > > of making a sys

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Joey Hess
Andreas Barth wrote: > Also, the binary packages in the debian/control template could have > Build-Depends specified which means that they should only be built if > those packages are actually installed (so we could do an automated > graph analyis, and also dh and cdbs could just drop them, so that

Re: Introduction of a "lock" group

2011-08-15 Thread Colin Watson
On Mon, Aug 15, 2011 at 04:11:49PM +0100, Roger Leigh wrote: > Fedora has moved to having /var/lock (now /run/lock) owned by > root:lock 0775 rather than root:root 01777. This has the advantage > of making a system directory writable only by root or setgid lock > programs, rather than the whole wo

Re: Introduction of a "lock" group

2011-08-15 Thread Roger Leigh
On Mon, Aug 15, 2011 at 05:35:54PM +0100, Colin Watson wrote: > On Mon, Aug 15, 2011 at 04:11:49PM +0100, Roger Leigh wrote: > > Fedora has moved to having /var/lock (now /run/lock) owned by > > root:lock 0775 rather than root:root 01777. This has the advantage > > of making a system directory wri

/usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Lars Wirzenius
On Mon, Aug 15, 2011 at 05:16:55PM +0900, Charles Plessy wrote: > Le Mon, Aug 15, 2011 at 01:48:50AM +0200, Adam Borowski a écrit : > > > > * A year ago, I repacked CD1, .xz took 66% space needed by .gz. This time, > > on the whole archive, gains are somewhat smaller: 72%. I guess that CD1 > >

Re: Introduction of a "lock" group

2011-08-15 Thread Iustin Pop
On Mon, Aug 15, 2011 at 06:00:50PM +0100, Roger Leigh wrote: > On Mon, Aug 15, 2011 at 05:35:54PM +0100, Colin Watson wrote: > > On Mon, Aug 15, 2011 at 04:11:49PM +0100, Roger Leigh wrote: > > > Are these any other downsides we need to consider? One issue is the > > > existence of badly broken pr

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Andreas Barth
* Joey Hess (jo...@debian.org) [110815 18:32]: > Andreas Barth wrote: > > Also, the binary packages in the debian/control template could have > > Build-Depends specified which means that they should only be built if > > those packages are actually installed (so we could do an automated > > graph an

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Andreas Barth
* Lars Wirzenius (l...@liw.fi) [110815 19:36]: > 584163 134 file sizes (MiB) Thanks for comparing these numbers. That tells me that at least in the average case we just can continue with gz, and not care much about the relativly small difference to xz. Andi -- To UNSUBSCRIBE,

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Lucas Nussbaum
On 15/08/11 at 19:41 +0200, Andreas Barth wrote: > * Lars Wirzenius (l...@liw.fi) [110815 19:36]: > > 584163 134 file sizes (MiB) > > Thanks for comparing these numbers. That tells me that at least in the > average case we just can continue with gz, and not care much about the > r

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Carsten Hey
* Lars Wirzenius [2011-08-15 18:33 +0100]: > raw gz xz > 584163 134 file sizes (MiB) >0421 450 savings compared to raw (MiB) > -421 0 29 savings compared to current gz (MiB) Years ago I compared sizes of compressed files in /usr/

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Lars Wirzenius
On Mon, Aug 15, 2011 at 11:04:51PM +0200, Carsten Hey wrote: > * Lars Wirzenius [2011-08-15 18:33 +0100]: > > raw gz xz > > 584163 134 file sizes (MiB) > >0421 450 savings compared to raw (MiB) > > -421 0 29 savings compared to cu

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Andreas Barth
* Lars Wirzenius (l...@liw.fi) [110815 23:27]: > On Mon, Aug 15, 2011 at 11:04:51PM +0200, Carsten Hey wrote: > > * Lars Wirzenius [2011-08-15 18:33 +0100]: > > > raw gz xz > > > 584163 134 file sizes (MiB) > > >0421 450 savings compared to raw (Mi

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Iustin Pop
On Mon, Aug 15, 2011 at 11:59:07PM +0200, Andreas Barth wrote: > * Lars Wirzenius (l...@liw.fi) [110815 23:27]: > > On Mon, Aug 15, 2011 at 11:04:51PM +0200, Carsten Hey wrote: > > > * Lars Wirzenius [2011-08-15 18:33 +0100]: > > > > raw gz xz > > > > 584163 134 file

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Carsten Hey
* Andreas Barth [2011-08-15 23:59 +0200]: > * Lars Wirzenius (l...@liw.fi) [110815 23:27]: > > On Mon, Aug 15, 2011 at 11:04:51PM +0200, Carsten Hey wrote: > > > * Lars Wirzenius [2011-08-15 18:33 +0100]: > > > > raw gz xz > > > > 584163 134 file sizes (MiB) > > > >

Re: Introducing Build-Recommends / Build-Core-Depends?

2011-08-15 Thread Charles Plessy
Le Mon, Aug 15, 2011 at 11:12:36AM +0100, Steve McIntyre a écrit : > Andreas Barth wrote: > > > >Generic options are usually better IMHO, but well - YMMV. > > Often, yes. But also often at extra cost. Where is the added benefit > here - i.e. what are the use cases? I'm 100% behind making the > boo

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Russell Coker
On Tue, 16 Aug 2011, Iustin Pop wrote: > There is also information on Wikipedia about various compression > benchmarks, but IMHO if we want to switch from gzip then bzip2 > doesn't make sense for /usr/share/doc. I'd like to see zless work transparently with bzip and xz compressed files. There's

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Ben Hutchings
On Tue, 2011-08-16 at 10:43 +1000, Russell Coker wrote: > On Tue, 16 Aug 2011, Iustin Pop wrote: > > There is also information on Wikipedia about various compression > > benchmarks, but IMHO if we want to switch from gzip then bzip2 > > doesn't make sense for /usr/share/doc. > > I'd like to see z

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Chris Knadle
On Monday, August 15, 2011, Ben Hutchings wrote: > On Tue, 2011-08-16 at 10:43 +1000, Russell Coker wrote: > > On Tue, 16 Aug 2011, Iustin Pop wrote: > > > There is also information on Wikipedia about various > > > compression benchmarks, but IMHO if we want to switch from > > > gzip then bzip2 do

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Russell Coker
On Tue, 16 Aug 2011, Chris Knadle wrote: > > After all, it isn't called gzless. > > Actually, that's not far off. Right now these functions are spread > across 4 different binaries, each of which is in a different package. Probably the best thing to do would be to just incorporate the function

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread James Vega
On Tue, Aug 16, 2011 at 01:06:34PM +1000, Russell Coker wrote: > On Tue, 16 Aug 2011, Chris Knadle wrote: > > > After all, it isn't called gzless. > > > > Actually, that's not far off. Right now these functions are spread > > across 4 different binaries, each of which is in a different package.

Re: /usr/share/doc/ files and gzip/xz/no compression

2011-08-15 Thread Chris Knadle
On Monday, August 15, 2011, Russell Coker wrote: > On Tue, 16 Aug 2011, Chris Knadle wrote: > > > After all, it isn't called gzless. > > > > Actually, that's not far off. Right now these functions are > > spread across 4 different binaries, each of which is in a > > different package. > > Proba

Re: Anonymous read-only access and Vcs-* [Re: Alioth status update, take 3]

2011-08-15 Thread Ben Finney
Tollef Fog Heen writes: > ]] Sven Hoexter > > | On the other hand there are all these packages in stable with broken > | Vcs fields now. Still not nice but assuming that most contributions > | will be based on what's in unstable that might be bearable. > > What VCS fields are broken? The VCS br

Re: Anonymous read-only access and Vcs-* [Re: Alioth status update, take 3]

2011-08-15 Thread Tollef Fog Heen
]] Ben Finney | The VCS browser link for ‘python-coverage’ used to work before the | changes this year. Now it leads to a 404 response. | | http://bzr.debian.org/loggerhead/collab-maint/python-coverage/python-coverage.debian/> Fixed. -- Tollef Fog Heen UNIX is user friendly, it's just pi

Re: Anonymous read-only access and Vcs-* [Re: Alioth status update, take 3]

2011-08-15 Thread Ben Finney
Tollef Fog Heen writes: > ]] Ben Finney > > | The VCS browser link for ‘python-coverage’ used to work before the > | changes this year. Now it leads to a 404 response. > > Fixed. Confirmed fixed, thank you. -- \ “Roll dice!” “Why?” “Shut up! I don't need your fucking | `\ *