date:20060423

Bug#364397: amarok fails to start

2006-04-23 Thread prosolutions

Package: amarok
Version: 1.3.8-1+b1


fails to launch with the following output:

$ amarok
amaroK: [Loader] Starting amarokapp..
amaroK: [Loader] Don't run gdb, valgrind, etc. against this binary! Use
amarokapp.
amaroK: [Loader] amarokapp probably crashed!



ran an strace, below is some partial output:

i notice a lot of lines similar to these:

12631 gettimeofday({1145770549, 925402}, NULL) = 0
12631 select(14, [3 4 5 12 13], [], [], {0, 8088}) = 0 (Timeout)


and then:

12631 select(14, [3 4 5 12 13], [], [], {0, 8048} unfinished ...
12719 set_thread_area({entry_number:-1 - 6, base_addr:0xb554bae0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, l
imit_in_pages:1, seg_not_present:0, useable:1}) = 0
12719 munmap(0xb7edf000, 79860) = 0
12719 set_tid_address(0xb554bb28)   = 12719
12719 rt_sigaction(SIGRTMIN, {0xb71813c0, [], SA_SIGINFO}, NULL, 8) = 0
12719 rt_sigaction(SIGRT_1, {0xb7181440, [], SA_RESTART|SA_SIGINFO},
NULL, 8) = 0
12719 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
12719 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024,
rlim_max=RLIM_INFINITY}) = 0
12719 _sysctl({{CTL_KERN, KERN_VERSION, 0, 20649, 1991, 0, 2, 0,
2e18, 0, 1990, 0, de48b80, 0, 2e18, 2e, 1993, 0, 13abff00, 0,
3230, 65642d30, 6e6f6362, 75732d66, 69702d62, 2e6c6578, 666e6f63, 0,
37a2, 0, 15881600, 0, 3530, 6e652d30, 656c6261, 7265742d, 756e696d,
6f632e73, 666e, 0, 50f1e, 0, 16b8c400, 0, 7528, 6e69686e, 2e646574,
666e6f63, 0, 0, 50f1f, 0, 1a572380, 0, 6128, 686f7475, 2e746e69,
666e6f63, 0, 0, 525f2, 0, 1dd0a080, 0, 7328, 702d6275, 6c657869,
6e6f632e, 66, 0, 5525b, 0, 43c84280, 0, 7928, 622d7365, 616d7469,
632e7370, 666e6f, 0, 21805, 0, 59e1bc80, 0, 3128, 65642d30,
616d6f66, 6e6f632e, 66, 0, 1992, 0, 5c091e80, 0, 3130, 65642d30,
6e6f6362, 75612d66, 69686f74, 632e746e, 666e6f, 0, 5d930, 0, 7da5f500,
0, 6e28, 75732d6f, 69702d62, 2e6c6578, 666e6f63, 0, 5d931, 0,
7da5f501, 0, 6e28, 69622d6f, 70616d74, 6f632e73, 666e, 0, 0, 20469,
0, 0, 0, 0}, 2, 0xbfd07d90, 35, (nil), 0}) = 0
12719 futex(0xb6f6c4dc, FUTEX_WAKE, 2147483647) = 0
12719 brk(0)= 0x82eb000
12719 brk(0x830c000)= 0x830c000
12719 rt_sigaction(SIGILL, {0xb6cd2010, [ILL], SA_RESTART}, {SIG_DFL},
8) = 0
12719 rt_sigaction(SIGILL, {SIG_DFL}, {0xb6cd2010, [ILL], SA_RESTART},
8) = 0
12719 futex(0xb64a3058, FUTEX_WAKE, 2147483647) = 0
12719 open(/dev/zero, O_RDWR) = 3
12719 mmap2(NULL, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE, 3,
0) = 0xb7ef1000
12719 close(3)  = 0
12719 mmap2(NULL, 397312, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb54ea000
12719 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
12631 ... select resumed )= 0 (Timeout)





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

Bug#364398: crash when starting xorg using nvidia driver

2006-04-23 Thread prosolutions

Package: nvidia-kernel-source
Version: 1.0.8756-4


not sure under what package to file this, so will file here.  starting
xorg with nvdia driver screen goes blank.  ctrl-alt-backspace has no
effect.  machine must be hard-reset.  card it:

nVidia Corporation NV34M [GeForce FX Go5200] (rev a1)


options in xorg.conf:

Section Device
Identifier  NVIDIA Corporation NV34M [GeForce FX Go5200]
   Driver  nvidia
   Option  NoLogoTrue
Option RenderAccel   True
BusID   PCI:1:0:0
EndSection



switching to the nv driver everything is fine...






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

Bug#364400: proftpd: [INTL:fr] French debconf templates translation

2006-04-23 Thread Christian Perrier

Package: proftpd
Version: N/A
Severity: wishlist
Tags: patch l10n

Please find attached the french debconf templates update, proofread by the
debian-l10n-french mailing list contributors.

If you do not already use it, please remember about the
podebconf-report-po utility, which helps warning translators about
changes when you modify some debconf templates in your packages. See
its man page for details.

The usual policy when using it is sending a warning to translators when
you plan to upload a version of your package with debconf templates
changes (EVEN TYPO CORRECTIONS). Then leave about one week for them to
update their files (several translation teams have a QA process which
requires time).

podebconf-report-po will take care of sending the translators the
needed material as well as getting the translators adresses from the
PO files. All you have to do is just using the utility..:-)

If you apply this policy, please forget about these remarks, of
courseThis message is generic..:-)


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
# translation of fr.po to French
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
#Translators, please read /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
# Christian Perrier [EMAIL PROTECTED], 2006.
msgid 
msgstr 
Project-Id-Version: fr\n
Report-Msgid-Bugs-To: [EMAIL PROTECTED]
POT-Creation-Date: 2006-03-29 16:05+0200\n
PO-Revision-Date: 2006-04-19 18:41+0200\n
Last-Translator: Christian Perrier [EMAIL PROTECTED]\n
Language-Team: French debian-l10n-french@lists.debian.org\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=ISO-8859-15\n
Content-Transfer-Encoding: 8bit\n
X-Generator: KBabel 1.11.2\n

#. Type: select
#. Choices
#: ../proftpd.templates:3
msgid inetd, standalone
msgstr inetd, indépendamment

#. Type: select
#. Description
#: ../proftpd.templates:5
msgid Run proftpd from inetd or standalone?
msgstr Méthode de lancement de proftpd :

#. Type: select
#. Description
#: ../proftpd.templates:5
msgid 
ProFTPd can be run either as a service from inetd, or as a standalone 
server. Each choice has its own benefits. If you have only a few ftp 
connections per day, it is probably better to run proftp from inetd in order 
to save resources.
msgstr 
ProFTPd peut être lancé soit à partir d'inetd, soit comme un serveur 
indépendant. Chaque méthode a ses avantages. Pour quelques connexions par 
jour, il n'est peut-être pas nécessaire de laisser proftpd fonctionner en 
permanence.

#. Type: select
#. Description
#: ../proftpd.templates:5
msgid 
On the other hand, if your ftp site is visited frequently, you should rather 
run proftp as a standalone server (because with inetd, each time a 
connection is opened, a new process is spawned).
msgstr 
Par contre, si votre site FTP est assez fréquenté, inetd n'est pas un choix 
judicieux, car chaque ouverture de connexion lance un nouveau processus.

#. Type: note
#. Description
#: ../proftpd.templates:17
msgid Warning on syntax changes in ProFTPd configuration.
msgstr Changement de syntaxe dans la configuration de ProFTPd

#. Type: note
#. Description
#: ../proftpd.templates:17
msgid 
You are upgrading from a pre-1.3.0 version. Probably you will need to revise 
your previous configuration to be compliant with current directives. Please, 
consult documentation and how-tos available in proftpd-doc and change /etc/
proftpd/proftpd.conf as needed.
msgstr 
Vous effectuez une mise à jour depuis une version inférieure à 1.3.0. Il 
vous sera probablement nécessaire de revoir votre configuration antérieure 
afin d'être conforme aux nouvelles directives. Veuillez consulter la 
documentation disponible dans le paquet proftpd-doc et modifier /etc/proftpd/
proftpd.conf en conséquence.

#. Type: note
#. Description
#: ../proftpd.templates:17
msgid 
Unfortunately, it is nearly impossible currently to convert your setup 
automatically, but for some basic issues. You will have to do  it yourself. 
ProFTPd could also be unable to use the resulting  configuration, and it 
would not restart after upgrading.
msgstr 
Malheureusement, il est à peu près impossible de convertir votre 
configuration automatiquement, sauf pour des points particulièrement 
simples. Vous devrez le faire vous-même. ProFTPd pourrait être incapable 
d'utiliser le fichier de configuration résultant et ne redémarrera donc pas 
après la mise à jour.

#. Type: note
#. Description
#: ../proftpd.templates:17
msgid 
Note also that starting from 1.3.0 version, dynamic modules are used and 
configuration should be splitted, keeping modules loading instructions 
within the new

Bug#364401: mysql-dfsg-5.0: [INTL:fr] French debconf templates translation

2006-04-23 Thread Christian Perrier

Package: mysql-dfsg-5.0
Version: N/A
Severity: wishlist
Tags: patch l10n

Please find attached the french debconf templates update, proofread by the
debian-l10n-french mailing list contributors.

If you do not already use it, please remember about the
podebconf-report-po utility, which helps warning translators about
changes when you modify some debconf templates in your packages. See
its man page for details.

The usual policy when using it is sending a warning to translators when
you plan to upload a version of your package with debconf templates
changes (EVEN TYPO CORRECTIONS). Then leave about one week for them to
update their files (several translation teams have a QA process which
requires time).

podebconf-report-po will take care of sending the translators the
needed material as well as getting the translators adresses from the
PO files. All you have to do is just using the utility..:-)

If you apply this policy, please forget about these remarks, of
courseThis message is generic..:-)


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
# translation of fr.po to French
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections dedicated to
#this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
#Some information specific to po-debconf are available at
#/usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
#Developers do not need to manually edit POT or PO files.
#
# Christian Perrier [EMAIL PROTECTED], 2004, 2006.
msgid 
msgstr 
Project-Id-Version: fr\n
Report-Msgid-Bugs-To: [EMAIL PROTECTED]
POT-Creation-Date: 2006-04-14 19:00+0200\n
PO-Revision-Date: 2006-04-17 17:12+0200\n
Last-Translator: Christian Perrier [EMAIL PROTECTED]\n
Language-Team: French debian-l10n-french@lists.debian.org\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=ISO-8859-15\n
Content-Transfer-Encoding: 8bit\n
debian.org\n
X-Generator: KBabel 1.11.2\n
Plural-Forms: Plural-Forms: nplurals=2; plural=n1;\n

#. Type: boolean
#. Description
#: ../mysql-server-5.0.templates:4
msgid Do you really want to downgrade?
msgstr Voulez-vous vraiment revenir à la version précédente ?

#. Type: boolean
#. Description
#: ../mysql-server-5.0.templates:4
msgid 
WARNING: The file /var/lib/mysql/debian-*.flag exists. This indicates that a 
mysql-server package with a higher version has been installed before. It can 
not be guaranteed that this version can use its data.
msgstr 
Un fichier /var/lib/mysql/debian-*.flag est présent. Cela indique qu'une 
version plus récente du paquet mysql-server a été précédemment installée. Il 
n'est pas garanti que cette version puisse en utiliser les données.

#. Type: note
#. Description
#: ../mysql-server-5.0.templates:11
msgid Important note for NIS/YP users!
msgstr Note importante pour les utilisateurs NIS/YP

#. Type: note
#. Description
#: ../mysql-server-5.0.templates:11
msgid 
To use mysql you must install an equivalent user and group to the following 
and ensure yourself that /var/lib/mysql has the right permissions (the uid/
gid may be different).
msgstr 
Pour utiliser MySQL, vous devez créer un utilisateur et un groupe similaires 
à ce qui suit et vérifier que /var/lib/mysql possède les permissions 
appropriées (les identifiants numériques de groupe et d'utilisateur, uid et 
gid, peuvent être différents).

#. Type: note
#. Description
#: ../mysql-server-5.0.templates:11
msgid 
/etc/passwd:  mysql:x:100:101:MySQL Server:/var/lib/mysql:/bin/false
msgstr 
/etc/passwd : mysql:x:100:101:MySQL Server:/var/lib/mysql:/bin/false

#. Type: note
#. Description
#: ../mysql-server-5.0.templates:11
msgid /etc/group:   mysql:x:101:
msgstr /etc/group :  mysql:x:101:

#. Type: note
#. Description
#: ../mysql-server-5.0.templates:11
msgid /var/lib/mysql:   drwxr-xr-x   mysqlmysql
msgstr /var/lib/mysql :  drwxr-xr-x   mysqlmysql

#. Type: note
#. Description
#: ../mysql-server-5.0.templates:24
msgid Update Hints
msgstr Informations sur les mises à jour

#. Type: note
#. Description
#: ../mysql-server-5.0.templates:24
msgid 
You have to run \mysql_upgrade\ after the upgrade, else tables can be  
corrupted! This script also enhances the privilege tables but is not  
supposed to give any user more rights that he had before,
msgstr 
Vous devez exécuter la commande « mysql_upgrade » après la mise à jour sinon 
les tables pourraient être corrompues. Ce script améliore également les 
tables de privilèges, sans toutefois donner à aucun utilisateur plus de 
droits qu'il n'en n'avait auparavant.

#. Type: note
#. Description
#:

Bug#208344: Argh, locking...

2006-04-23 Thread Adam Porter

severity 208344 important
thanks

Well, I looked at the e-mail logcheck just sent me, and I found this:

gconfd (me-19567): Failed to get lock for daemon, exiting: Failed to 
lock '/tmp/gconfd-me/lock/ior': probably another process has the lock, or 
your operating system has NFS file locking misconfigured (Resource 
temporarily unavailable)

I killall-9'ed gconfd-2 and removed that lock file, and now Newton's working.  
So I'm downgrading it back to important.

The problem is, those crazy CORBA errors gave _no indication_ of the actual 
problem.

The only way I discovered it was by logcheck notifying me of those entries in 
the logs,  I was going to try rebooting today if I couldn't figure it out 
otherwise, and that would most likely have fixed it (the PID in the lockfile 
was the same as the running gconfd-2 process), and then the real problem 
might still not be known.  Remember that I looked for those lock files that 
were listed in the earlier reports, but I'm guessing that the location of the 
gconf lockfile has changed since then.


pgp9x3xebdjGr.pgp
Description: PGP signature

Bug#364399: openswan: [INTL:fr] French debconf templates translation

2006-04-23 Thread Christian Perrier

Package: openswan
Version: N/A
Severity: wishlist
Tags: patch l10n

Please find attached the french debconf templates update, proofread by the
debian-l10n-french mailing list contributors.

If you do not already use it, please remember about the
podebconf-report-po utility, which helps warning translators about
changes when you modify some debconf templates in your packages. See
its man page for details.

The usual policy when using it is sending a warning to translators when
you plan to upload a version of your package with debconf templates
changes (EVEN TYPO CORRECTIONS). Then leave about one week for them to
update their files (several translation teams have a QA process which
requires time).

podebconf-report-po will take care of sending the translators the
needed material as well as getting the translators adresses from the
PO files. All you have to do is just using the utility..:-)

If you apply this policy, please forget about these remarks, of
courseThis message is generic..:-)


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
# translation of fr.po to French
#
#
#
#
# Christian Perrier [EMAIL PROTECTED], 2004, 2006.
msgid 
msgstr 
Project-Id-Version: fr\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2006-04-17 05:04-0600\n
PO-Revision-Date: 2006-04-17 18:59+0200\n
Last-Translator: Christian Perrier [EMAIL PROTECTED]\n
Language-Team: French debian-l10n-french@lists.debian.org\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=ISO-8859-15\n
Content-Transfer-Encoding: 8bit\n
X-Generator: KBabel 1.11.2\n
Plural-Forms: Plural-Forms: nplurals=2; plural=n1;\n

#. Type: select
#. Choices
#: ../openswan.templates.master:3
msgid earliest, \after NFS\, \after PCMCIA\
msgstr Le plus tôt possible, Après NFS, Après PCMCIA

#. Type: select
#. Description
#: ../openswan.templates.master:5
msgid At which level do you wish to start Openswan ?
msgstr Étape de lancement d'Openswan :

#. Type: select
#. Description
#: ../openswan.templates.master:5
msgid 
With the current Debian startup levels (nearly everything starting in level 
20), it is impossible for Openswan to always start at the correct time. 
There are three possibilities when Openswan can start: before or after the 
NFS services and after the PCMCIA services. The correct answer depends on 
your specific setup.
msgstr 
Avec les niveaux de démarrage actuellement utilisés par Debian (presque tout 
démarre au niveau 20), il est impossible de faire en sorte qu'Openswan 
démarre toujours au moment approprié. Il existe trois moments où il est 
opportun de le démarrer : avant ou après les services NFS, ou après les 
services PCMCIA. La réponse appropriée dépend de vos réglages spécifiques.

#. Type: select
#. Description
#: ../openswan.templates.master:5
msgid 
If you do not have your /usr tree mounted via NFS (either you only mount 
other, less vital trees via NFS or don't use NFS mounted trees at all) and 
don't use a PCMCIA network card, then it's best to start Openswan at the 
earliest possible time, thus allowing the NFS mounts to be secured by IPSec. 
In this case (or if you don't understand or care about this issue), answer 
\earliest\ to this question (the default).
msgstr 
Si votre arborescence /usr n'est pas un montage NFS (soit parce que vos 
montages NFS sont à d'autres endroits, moins critiques, soit parce que vous 
n'utilisez pas du tout de montage NFS) et si vous n'utilisez pas de carte 
réseau PCMCIA, il est préférable de démarrer Openswan le plus tôt possible, 
ce qui permettra de sécuriser les montages NFS avec IPSec. Dans ce cas (ou 
bien si vous ne comprenez pas l'objet de la question ou qu'elle ne vous 
concerne pas), choisissez « le plus tôt possible », qui est le choix par 
défaut.

#. Type: select
#. Description
#: ../openswan.templates.master:5
msgid 
If you have your /usr tree mounted via NFS and don't use a PCMCIA network 
card, then you will need to start Openswan after NFS so that all necessary 
files are available. In this case, answer \after NFS\ to this question. 
Please note that the NFS mount of /usr can not be secured by IPSec in this 
case.
msgstr 
Si /usr est un montage NFS et que vous n'utilisez pas de carte réseau 
PCMCIA, vous devrez alors démarrer Openswan après les services NFS afin que 
tous les fichiers nécessaires soient disponibles. Dans ce cas, choisissez 
« Après NFS ». Veuillez noter que le montage NFS de /usr n'est alors pas 
sécurisé par IPSec.

#. Type: select
#. Description
#: ../openswan.templates.master:5
msgid 
If you use a PCMCIA network card for your IPSec connections, then you only 
have to choose to start it after the PCMCIA services. Answer \after PCMCIA
\ in this case. This is also the correct answer if you want to fetch keys 
from a locally running

Bug#335867: libglew1: Newer upstream version is available

2006-04-23 Thread Joost Yervante Damad

On Saturday 22 April 2006 21:54, Arnaud Quette wrote:
 2006/4/22, Marcelo E. Magallón [EMAIL PROTECTED]:
  On 4/22/06, Joost Yervante Damad [EMAIL PROTECTED] wrote:
   An 1.3.4 package is about to be uploaded by Marcello.
 
  Actually I did upload it on Friday morning... didn't it make to the
  archive? *sigh*

 seems not!

 I've quickly done some work yesterday on 1.3.4. If you whish to take a
 look at the diff, tell me so and I'll send you privatly.

 Arnaud

Hi Arnaud,

FYI, my updated package can be found at 
http://mentors.debian.net/debian/pool/main/g/glew/ 

Greetings, Joost 


-- 
The planet Andete is famous for it's killer edible poets.


pgpCKHzy29EAv.pgp
Description: PGP signature

Bug#363250: general: Custom PAGER gives error on sid, but works on sarge

2006-04-23 Thread Manoj Srivastava

On 22 Apr 2006, Loïc Minier outgrape:

 On Sat, Apr 22, 2006, Manoj Srivastava wrote:
 There are two use cases that any pager directive must address:
 1) The program is going to generate output which must be piped to
 a pager
 2) The program want to send a file to the user.

 I agree that these use cases need to be supported.

 But perhaps the policy for Debian should be for programs to ignore
 PAGER and just use sensible pager, where all the logic for dealing
 with pager goes in. I still don't see how sensible pager can handle
 the pipeline vs the non-pipeline case, though.

 Yes, I believe the policy should be changed in this way, and as I
 proposed.

Hmm.  This could be a potentially disruptive change -- since a
 lot of programs may need to be changed in non-trivial ways.

 Look at the code of sensible-pager, it will call $PAGER if
 sensible-pager is called without any argument, and $PAGER
 filename if it's called as sensible-pager filename.  This
 seems good enough for me; if people set $PAGER to a pipeline, they
 might suffer from problems for the second case, but we can work on
 that.

Err, so we can't make this policy (allowing $PAGER to be a
 pipeline) until we have a solution for this, given that we have
 agreed that the two use cases for $PAGER must be  feasible.


 Barring that, policy would have to be that programs can' t user
 PAGER to work with use case 2, and must be guilty of an useless
 use of cat to pipe data to STDIN for PAGER.

 Yes, if you mean that permitting pipelines forbids programs to call
 $PAGER $file, I agree with you.  There are multiple ways to solve
 this, but I think that whatever way is chosen should be implemented
 in sensible-pager, and we can even change our mind later, and fix
 only sensible-pager.  The contract of sensible-pager with respect to
 Debian programs should be to offer two modes of operation, the pipe
 of data on stdin mode, and the pass a file on the command line mode
 (matching your use cases 1 and 2).

 PAGER has the benefit of being long standardized, and if we do
 not use PAGER, we are breaking user expectations.
 What is the benefit of creating a PAGER clone?

 sensible-pager is not a PAGER clone, it permits us to enhance the
 handling of $PAGER in a single place instead of changing every
 program in Debian that wants to send something to $PAGER.

The point is that lots of programs already respect $PAGER,
 with varying semantics (most support $PAGER being less or more or
 something, but not all support arbitary pipelines.


 B/ user configuration of the pager When defined, $PAGER is a sh
 pipeline which reads its data from stdin.
 How do programs present a text file to the user using a PAGER,
 then? cat file.txt | $PAGER?

 That's a question for sensible-pager to solve, but one way is to use
 cat $@ | $PAGER indeed.

Umm. If we are talking about making policy, we can't just make
 policy and say things are a problem for some package or the other to
 solve.

 In other words, ignore $PAGER, use sensible-pager all over,
 and let that handle it?

 Yes.

 Not, unless these questions are answered, and we actually have
 a working implementation.

 Well the current implementation works, except for pipelines.  :)

Since allowing pipelines seems to be the motivating factor
 here, we do need to solve that, I think.

manoj
-- 
I am here by the will of the people and I won't leave until I get my
raincoat back.- a slogan of the anarchists in Richard Kadrey's
Metrophage
Manoj Srivastava   [EMAIL PROTECTED]  http://www.debian.org/%7Esrivasta/
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Bug#364385: localechooser almost tripled in size...

2006-04-23 Thread Christian Perrier

 Breakdown on size increase since 1.03 is:
 
 - 30k added to templates file
 - 1k added to /usr/bin/localechooser
 - 1k added to /usr/lib/post-base-installer.d/05localechooser
 - 1k removed from languagelist
 
 I don't see how this could sum to the 230k indicated by what you pasted
 though.


In 1.06, I introduced a bug when I removed the crafted intltool-merge
which allowed partial translations for country names.

I unfortunately ommited the document this properly because it was
discovered while working on something else (beat me) but then it got
fixed and localechooser got the country names translations back...and
its huge size back

In the meantime, some languages were added, which explains the
templates file size increase noticed by Joey.

Of course, the size of this templates file is a problem but I fail to
see how to do differently if we want to have the country names
translated.

The scripts in localechooser are heavily commented. One way to grab
some bytes back could be filtering these comments during the package
build. This would of course make debugging a little more complicated
when working in the installer itself but that could be worth it. This
saves about 5k in /usr/bin/localechooser







signature.asc
Description: Digital signature

Bug#364386: texmacs: Segmentation fault at startup

2006-04-23 Thread René van Bevern

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Michael Ekstrand [EMAIL PROTECTED] writes:

Hello Michael,

 TeXmacs (both 1.0.6-5 from unstable and 1.0.6-3 from testing) segfaults
 at starup, both when a TeXmacs file is specified on the command line
 and when one is not.

Hm, I don't see this. :-/

Could you please try if it works when you move your TeXmacs
directory out of the way? I.e. move ~/.TeXmacs somewhere else and
try start it.

 A core dump file can be provided upon request.

Since I am unable to make it crash, a core dump file would be really
nice. Upload it somewhere or send it to my E-Mail address directly.

Along with a core file, your configuration might be interesting to
me. (the scm files in .TeXmacs/system)

René

- -- 
0662 B928 E386 E2EF 0E8A  E2EE C26D 3034 7C71 4C78
http://progn.org  http://www.debian.org  http://www.pro-linux.de
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)

iQCVAwUBREse/GXAXAFwWYizAQJxIgQAqspNlCw80uXTE/YgWm3f8Y1bUR9SMfb0
x7TssW6lKNshArYuhVKiczcOp+RfEMpc1aYxSMnhjYBPmJxPjozwHFj0k9Od40fS
Jb0NcSBJgOFuwleX5HqsrXCN2jW9WMnsOX2aZXp9tZt5CXlctOKS4nF4wuSmkycQ
VuVpmAXiVyw=
=p9dh
-END PGP SIGNATURE-

Bug#364385: localechooser almost tripled in size...

2006-04-23 Thread Christian Perrier

 A check against an older image shows that the main culprit is 
 localechooser:
108758 B - 136 blocks - 10 files from localechooser.udeb (version 1.06)
344544 B - 360 blocks - 10 files from localechooser.udeb (version 1.12)
 
 Is it possible to bring that down again a bit please?

Don't we already drop translations in floppy builds. Which means that
the main culprit, ie the templates file, should be shorten down.

-- 




signature.asc
Description: Digital signature

Bug#364402: libapr0: please move its section to libs, instead of net

2006-04-23 Thread Rogerio Brito

Package: libapr0
Version: 2.0.55-4
Severity: wishlist

While auditing the installation of my systems, I noticed that libapr0 is 
packaged
under section net. My naïve impression would be that its proper place would be 
in
section libs, instead.

I know that changing the section and priority of packages may be troublesome, 
since
they have to be approved by the ftpmasters, but I just wanted to file this 
whishlist
bug in case you happen to agree.


Thanks.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-rc1-5
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Bug#364403: [INTL:nl] New dutch po-debconf translation

2006-04-23 Thread Esther Hanko

Package: gpm
version: 1.19
Severity: wishlist
Tags: patch l10n

Please find attached the dutch po-debconf translation. This translation
has been vetted by the review process of the debian-l10n-dutch team.
Please add it to your next package revision, it should be inserted in
your package build-tree as debian/po/nl.po, TIA.

Feel free to mail me if this file needs updating at some future date.

Thanks and regards,

Esther Hanko
# translation of nl.po to
#
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections dedicated to
#this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#Some information specific to po-debconf are available at
#/usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans#
#Developers do not need to manually edit POT or PO files.
#
# Esther Hanko [EMAIL PROTECTED], 2006.
msgid
msgstr
Project-Id-Version: nl\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2005-04-16 01:20-0500\n
PO-Revision-Date: 2006-03-30 16:43+0200\n
Last-Translator: Esther Hanko [EMAIL PROTECTED]\n
language-team: Nederlandse debian-l10n-dutch@lists.debian.org\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
Language-Team: debian-l10n-dutch@lists.debian.org\n
X-Generator: KBabel 1.11.1\n

#. Type: boolean
#. Description
#: ../gpm.templates:4
msgid Do you want to start or restart GPM while X is running?
msgstr Wilt u GPM starten of herstarten terwijl X actief is?

#. Type: boolean
#. Description
#: ../gpm.templates:4
msgid
Usually, GPM should be started or restarted when it is installed or
upgraded. But when X is running and trying to use the same mouse device,
this can sometimes cause a problem with the X mouse cursor. Switching to the
console and then back to X will usually fix it.
msgstr Normaal gesproken zou GPM moeten worden gestart of herstart wanneer het geÃ¯nstalleerd of opgewaardeerd wordt. Echter, als X ook actief is en de muis op hetzelfde muisapparaat probeert te gebruiken, zou dit een probleem kunnen vormen met de X muiscursor. Wisselen naar een console en dan terug naar X zal dit meestal oplossen.

#. Type: string
#. Description
#: ../gpm.templates:12
msgid Which mouse device should gpm use?
msgstr Welk muisapparaat moet gpm gebruiken?

#. Type: string
#. Description
#: ../gpm.templates:12
msgid
Where is your mouse device? If you have a regular PS/2 mouse, you probably
want /dev/psaux. If you have a serial mouse, it may be something like /dev/
ttyS0. If you have a usb mouse (make sure you have the modules loaded),
it's /dev/input/mice. If you're on a Sun machine, it's probably /dev/
sunmouse. If you're on an 68k Macintosh, it's probably /dev/mouse.
msgstr Waar staat het muisapparaat? Als u een reguliere PS/2-muis heeft, is dat waarschijnlijk /dev/psaux. As u een seriÃ«le muis heeft, zou het iets kunnen zijn als /dev/ttyS0. Als u een usb-muis heeft (zorg er dan ook voor dat u de juiste modules geladen heeft), is het /dev/input/mice. Als dit een Sun-machine is, is het waarschijnlijk /dev/sunmouse. Als u op een 68k Macintosh werkt, is het waarschijnlijk /dev/mouse.

#. Type: string
#. Description
#: ../gpm.templates:21
msgid What type is your mouse?
msgstr Wat voor soort muis heeft u?

#. Type: string
#. Description
#: ../gpm.templates:21
msgid Available mouse types are:
msgstr Beschikbare muistypes zijn:

#. Type: string
#. Description
#: ../gpm.templates:21
msgid Name Description
msgstr NaamOmschrijving

#. Type: string
#. Description
#: ../gpm.templates:21
msgid
PS/2 mice: round 6-pin connector\n
autops2Most PS/2 mice; specific protocol will be auto-detected.\n
Also use this for USB and ADB mice.\n
ps2Standard PS/2 mice, 2 or 3 buttons\n
imps2 Microsoft IntelliMouse and compatibles; PS/2 mice with\n
3 buttons and a scroll wheel\n
exps2 Newer Microsoft IntelliMouse and compatible, may have\n
more than 3 buttons. Most newer PS/2 mice are this type.\n
synps2 Synaptics PS/2 TouchPad, found on many laptops\n
netmouse Genius NetMouse, 2 normal buttons plus an \Up/Down\ button\n
fups2 Same as \ps2\ but may be needed for certain broken\n
mice or KVM switches\n
fuimps2Same as \imps2\ but may be needed for certain broken\n
mice or KVM switches
msgstr
PS/2-muizen: ronde zespinsconnector\n
autops2Voor de meeste PS/2-muizen zal het precieze protocol\n
automatisch gedetecteerd worden.\n
Gebruik dit ook voor USB- en ADB-muizen.\n
ps2Standaard PS/2-muis, met twee of drie muisknoppen\n
imps2 Microsoft IntelliMouse en dergelijke; PS/2 muizen met\n
3 knoppen en een muiswiel\n
exps2 Recente Microsoft IntelliMouse en dergelijke, mogelijk met\n
meer dan 3 knoppen; meer recente

1 2 3 4 >

1 - 100 of 387 matches

Mail list logo