Bug#699077: ITP: isenkram -- Suggest packages to install when inserting new hardware

2013-01-27 Thread Petter Reinholdtsen
Package: wnpp Owner: Petter Reinholdtsen Severity: wishlist * Package name: isenkram Version : 0.2 Upstream Author : Petter Reinholdtsen * URL : http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git * License : GPL Programming Lang: Python, Perl, s

Re: screen says "Bad tty" if /dev/console is a symlink

2013-01-27 Thread Guillem Jover
On Sun, 2013-01-27 at 01:30:54 +0400, Игорь Пашев wrote: > Did I break anything? > Too paranoid? Given the “intention” of the previous code, not enough I'd say. :) About the question of removing the pathname checks, that's something the maintainers would have to answer. > Index: screen/tty.sh >

Re: screen says "Bad tty" if /dev/console is a symlink

2013-01-27 Thread Игорь Пашев
> I guess you meant PATH_MAX here, in any case POSIX does not guarantee > MAX variables to be defined, it would be better to use the POSIX.1-2008 > variant of realpath(3) that allocates when passed a NULL (by checking > if it's available at configure time). I thought my libc did not support it, bu

Re: screen says "Bad tty" if /dev/console is a symlink

2013-01-27 Thread Игорь Пашев
So, do you mean it is good to do realpath() and only then stat() etc.? CheckTtyname (tty) { ; ; } ? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CALL-Q8yg12W

Re: screen says "Bad tty" if /dev/console is a symlink

2013-01-27 Thread Adam Borowski
On Sun, Jan 27, 2013 at 02:25:56PM +0100, Guillem Jover wrote: > > + char real[MAX_PATH]; > > I guess you meant PATH_MAX here, in any case POSIX does not guarantee > MAX variables to be defined, it would be better to use the POSIX.1-2008 > variant of realpath(3) that allocates when passed a NULL

Re: screen says "Bad tty" if /dev/console is a symlink

2013-01-27 Thread Roger Leigh
On Sun, Jan 27, 2013 at 04:26:00PM +0100, Adam Borowski wrote: > On Sun, Jan 27, 2013 at 02:25:56PM +0100, Guillem Jover wrote: > > > + char real[MAX_PATH]; > > > > I guess you meant PATH_MAX here, in any case POSIX does not guarantee > > MAX variables to be defined, it would be better to use the

No native packages?

2013-01-27 Thread Jakub Wilk
Dmitrijs Ledkovs wrote on his blog[0]: Generally if software is useful in Debian Project it can be useful for other debian-like and unlike projects. In particular native packages do not offer the same patching flexibility as 3.0 (quilt), thus forcing downstream distributions to inline modify p

Re: No native packages?

2013-01-27 Thread Gergely Nagy
Jakub Wilk writes: > Dmitrijs Ledkovs wrote on his blog[0]: > >> Generally if software is useful in Debian Project it can be useful >> for other debian-like and unlike projects. In particular native >> packages do not offer the same patching flexibility as 3.0 (quilt), >> thus forcing downstream

Re: No native packages?

2013-01-27 Thread Arno Töll
Hi, On 27.01.2013 19:32, Gergely Nagy wrote: > There are two native packages I maintain, and I've yet to hear a good > reason for making either of them non-native. Not knowing your use cases in particular, it would often be good enough if we could restrict native packages to use cases, where the

Go (golang) packaging, part 2

2013-01-27 Thread Michael Stapelberg
Hi, I have been in contact with a few Go people and we have worked out the following: Go libraries (not binaries!) should be present in Debian _only_ for the purpose of building Debian binary packages. They should not be used directly for Go development¹. Go library Debian packages such as golan

Re: No native packages?

2013-01-27 Thread Gergely Nagy
Arno Töll writes: > Hi, > > On 27.01.2013 19:32, Gergely Nagy wrote: >> There are two native packages I maintain, and I've yet to hear a good >> reason for making either of them non-native. > > Not knowing your use cases in particular, it would often be good enough > if we could restrict native

Re: No native packages?

2013-01-27 Thread Wouter Verhelst
On Sun, Jan 27, 2013 at 07:16:44PM +0100, Jakub Wilk wrote: > Dmitrijs Ledkovs wrote on his blog[0]: > > >Generally if software is useful in Debian Project it can be useful > >for other debian-like and unlike projects. In particular native > >packages do not offer the same patching flexibility as

Bug#699138: general: Tor, opera, chrom(ium), others lock up gnome on Acer 722. Can not access other CLI terminals.

2013-01-27 Thread Tim G.
Package: general Severity: important Dear Maintainer, I have recently installed Debian Wheezy on an Acer AspireOne 722. This hardware required installing firmware-linux-nonfree to get full gnome3 functionality. Wheezy locks up frequently on this machine. The lock-up is complete. Neither keys nor

Bug#699138: general: Tor, opera, chrom(ium), others lock up gnome on Acer 722. Can not access other CLI terminals.

2013-01-27 Thread Ben Hutchings
Control: reassign -1 src:linux 3.2.35-2 On Sun, 2013-01-27 at 20:00 -0500, Tim G. wrote: > Package: general > Severity: important > > Dear Maintainer, > > I have recently installed Debian Wheezy on an Acer AspireOne 722. This > hardware > required installing firmware-linux-nonfree to get full g

Processed: Re: Bug#699138: general: Tor, opera, chrom(ium), others lock up gnome on Acer 722. Can not access other CLI terminals.

2013-01-27 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:linux 3.2.35-2 Bug #699138 [general] general: Tor, opera, chrom(ium), others lock up gnome on Acer 722. Can not access other CLI terminals. Bug reassigned from package 'general' to 'src:linux'. Ignoring request to alter found versions of bug #699138