Bug#413249: wrong returnvalue logic in config script

2007-06-15 Thread Frank Küster
Brice Goglin [EMAIL PROTECTED] wrote:

 Hi Frank,

 What's the status of this x11-common bug today? (after fixing or
 ignoring your debconf problems).

It seems no one has addressed it.

 It's kind of hard to understand which
 fixes are needed in x11-common in the end. Do you still need your fix
 from [1]?

What do you mean with need?  The fix in that message didn't solve the
underlying problem which originated in debconf (and has since been
solved in etch).  Instead, it fixed the wrong returnvalue logic in
the config script.

Nobody has anywhere in the bug stated that the logic is not wrong.  So
either you just apply my fix, or you investigate further why it still
works.  I suspect that it works just because if the question is not
shown, it fails to break, but then validates the value in SAFE, which is
0 in this case.

Regards, Frank


-- 
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)



Bug#413249: severity of 413249 is important, tagging 413249

2007-03-05 Thread Frank Küster
Steve Langasek [EMAIL PROTECTED] wrote:

 # Automatically generated email from bts, devscripts version 2.9.27
 severity 413249 important
 tags 413249 unreproducible

It is very well reproducible here, it occurred again today.  This time,
even Ctrl-c wouldn't stop the script, it ate 95% CPU, and ps axf
showed that it had somehow detached from the controlling X terminal.  It
needed a kill $pid to get control of my CPU.

I have added a set -x in config and preinst, and this showed me one
point were there is a bug in the config script.  I am not sure, however,
that this is the root of my problem.  

The bug I found so far is

while :; do
  run db_input low x11-common/xwrapper/nice_value
  # is the question going to be asked?
  if [ $? -eq 30 ]; then
break # no; bail out of validation loop
  fi

Because db_input is wrapped in the run function, the return value of
db_input is no longer in $?, and the script will not break the loop.  It
is in $_retval, though:

run () {
[...]
  $@ || _retval=$?

  if [ ${_retval:-0} -ne 0 ]; then
observe command \$*\ exited with status $_retval
  fi

The patch for this would be

 while :; do
   run db_input low x11-common/xwrapper/nice_value
   # is the question going to be asked?
+  WILL_BE_ASKED=$_retval
-  if [ $? -eq 30 ]; then
+  if [ $WILL_BE_ASKED -eq 30 ]; then
break # no; bail out of validation loop
  fi

However, changing this doesn't fix my problem, and I got sceptical
whether it originates in x11-common, since I get so many internal
debconf errors.

I removed the content of /var/cache/debconf, dpkg-reconfigure'd debconf,
and tried again, but that didn't help.

Somehow still debconf's answers are not what the config script expects.
Upon reinstalling x11-common with set -xv, I get 

# next question requires input validation; assume safe valid value already
# present (possibly the template default)
SAFE=
+ SAFE=
if db_get x11-common/xwrapper/nice_value; then
  SAFE=$RET
fi
+ db_get x11-common/xwrapper/nice_value
+ _db_cmd 'GET x11-common/xwrapper/nice_value'
+ IFS=' '
+ printf '%s\n' 'GET x11-common/xwrapper/nice_value'
debconf (developer): -- GET x11-common/xwrapper/nice_value
debconf (developer): -- 0 0
+ IFS='
'
+ read -r _db_internal_line
+ RET='value set'
+ case ${_db_internal_line%%[   ]*} in
+ return 0
+ SAFE='value set'

Why on earth is $RET now value set, where it should be 0?  Note
that value set was the last answer that debconf communicated about
that template, but not the last answer it communcated in that script
(which was about allowed_users.

What is happening here?  Please remember that this is an etch system
installed on the 10th of February, nothing were the system had time to
degrade into a mess of distribution mixture and local misconfiguration
(though I do not exclude the latter...)

Regards, Frank
-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)



Bug#413249: severity of 413249 is important, tagging 413249

2007-03-05 Thread Frank Küster
clone 413249 -1
retitle 413249 wrong returnvalue logic in config script
tags 413249 -unreproducible
retitle -1 debconf: database communication does not work
reassign -1 debconf
thanks

Frank Küster [EMAIL PROTECTED] wrote:

 It is very well reproducible here, it occurred again today.  
[...]
 The bug I found so far is

(this is going to stay 413249, package x11-common)

 while :; do
   run db_input low x11-common/xwrapper/nice_value
   # is the question going to be asked?
   if [ $? -eq 30 ]; then
 break # no; bail out of validation loop
   fi

 Because db_input is wrapped in the run function, the return value of
 db_input is no longer in $?, and the script will not break the loop.  It
 is in $_retval, though:

 run () {
 [...]
   $@ || _retval=$?

   if [ ${_retval:-0} -ne 0 ]; then
 observe command \$*\ exited with status $_retval
   fi

 The patch for this would be

  while :; do
run db_input low x11-common/xwrapper/nice_value
# is the question going to be asked?
 +  WILL_BE_ASKED=$_retval
 -  if [ $? -eq 30 ]; then
 +  if [ $WILL_BE_ASKED -eq 30 ]; then
 break # no; bail out of validation loop
   fi

 However, changing this doesn't fix my problem, and I got sceptical
 whether it originates in x11-common, since I get so many internal
 debconf errors.

This is why I reassign the other part of this to debconf.  I'm quite
sure that what is going on on my system is not a general breakage of
debconf, but for sure it is something that needs investigation

[work on debconf snipped, see bug log]
 debconf (developer): -- GET x11-common/xwrapper/nice_value
 debconf (developer): -- 0 0
 + IFS='
 '
 + read -r _db_internal_line
[...]
 Why on earth is $RET now value set, where it should be 0?  Note
 that value set was the last answer that debconf communicated about
 that template, but not the last answer it communcated in that script
 (which was about allowed_users.

Now the debug output below adds to the confusion, but it might be easier
to debug.  I have done

# dpkg --purge --force-depends x11-common

and then installed again, with set -xv in the maintainer scripts.
Things to observe:

- db_set returns with exit code 1.  Is this okay?  I think it
  shouldn't, and it's a peculiarity of x11-common to not stop when this
  happens.  However, what does it indicate on the debconf side?

- after the skipped parts, the db_input part is not interesting, but
  shows that that goes without errors

- db_go gives an internal debconf error (I have just apt-get
  --reinstall install'ed the etch version, so the files should be okay) 

- db_get returns *nothing*, although it was set to 0 earlier.

+ run db_set x11-common/xwrapper/nice_value 0
+ '[' 3 -lt 1 ']'
+ db_set x11-common/xwrapper/nice_value 0
+ _db_cmd 'SET x11-common/xwrapper/nice_value' 0
+ IFS=' '
+ printf '%s\n' 'SET x11-common/xwrapper/nice_value 0'
debconf (developer): -- SET x11-common/xwrapper/nice_value 0
debconf (developer): -- 0 value set
+ IFS='
'
+ read -r _db_internal_line
+ RET='value set'
+ case ${_db_internal_line%%[   ]*} in
+ return 0
+ '[' 1 -ne 0 ']'
+ observe 'command db_set x11-common/xwrapper/nice_value 0 exited with status 
1'
+ '[' -n '' ']'

[... some parts skipped ...]

+ run db_input low x11-common/xwrapper/nice_value
+ '[' 3 -lt 1 ']'
+ db_input low x11-common/xwrapper/nice_value
+ _db_cmd 'INPUT low' x11-common/xwrapper/nice_value
+ IFS=' '
+ printf '%s\n' 'INPUT low x11-common/xwrapper/nice_value'
+ IFS='
'
+ read -r _db_internal_line
debconf (developer): -- INPUT low x11-common/xwrapper/nice_value
debconf (developer): -- 30 question skipped
+ RET='30 question skipped'
+ case ${_db_internal_line%%[   ]*} in
+ return 30
+ _retval=30
+ '[' 30 -ne 0 ']'
+ observe 'command db_input low x11-common/xwrapper/nice_value exited with 
status 30'
+ '[' -n '' ']'
+ '[' 0 -eq 30 ']'
+ run db_go
+ '[' 1 -lt 1 ']'
+ db_go
+ _db_cmd 'GO '
+ IFS=' '
+ printf '%s\n' 'GO '
+ IFS='
'
+ read -r _db_internal_line
debconf (developer): -- GO 
Use of uninitialized value in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, GEN1 line 7.
debconf (developer): -- 0 ok
+ RET=ok
+ case ${_db_internal_line%%[   ]*} in
+ return 0
+ '[' 30 -ne 0 ']'
+ observe 'command db_go exited with status 30'
+ '[' -n '' ']'
+ RET=
+ db_get x11-common/xwrapper/nice_value
+ _db_cmd 'GET x11-common/xwrapper/nice_value'
+ IFS=' '
+ printf '%s\n' 'GET x11-common/xwrapper/nice_value'
+ IFS='
'
+ read -r _db_internal_line
debconf (developer): -- GET x11-common/xwrapper/nice_value
debconf (developer): -- 0 
+ RET=

Any idea what's going on?

Regards, Frank

-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)



Bug#413249: x11-common: config script hangs or fails

2007-03-03 Thread Frank Küster
, then cancel, and didn't need to
stop with Ctrl-c.  error.lg is attached, but it seems this could be the
problem:

Setting up x11-common (7.1.0-12) ...
debconf (developer): frontend started
debconf (developer): frontend running, package name is x11-common
debconf (developer): starting /var/lib/dpkg/info/x11-common.config configure 
1:7.1.0-12
debconf (developer): -- SET x11-common/xwrapper/allowed_users Console Users 
Only
debconf (developer): -- 0 value set
debconf (developer): -- SET x11-common/xwrapper/nice_value 0
debconf (developer): -- 0 value set
debconf (developer): -- INPUT low x11-common/xwrapper/allowed_users
debconf (developer): -- 30 question skipped
debconf (developer): -- GO 
Use of uninitialized value in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, GEN1 line 4.
debconf (developer): -- 0 ok
debconf (developer): -- GET x11-common/xwrapper/allowed_users

Regards, Frank




-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages x11-common depends on:
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  debianutils   2.17   Miscellaneous utilities specific t
ii  lsb-base  3.1-23 Linux Standard Base 3.1 init scrip

x11-common recommends no packages.

-- debconf information:
  x11-common/xwrapper/nice_value: 0
  x11-common/xwrapper/allowed_users: Console Users Only
  x11-common/xwrapper/actual_allowed_users: console
  x11-common/xwrapper/nice_value/error:
  x11-common/x11r6_bin_not_empty:
  x11-common/upgrade_issues:

-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)

Setting up x11-common (7.1.0-12) ...
debconf (developer): frontend started
debconf (developer): frontend running, package name is x11-common
debconf (developer): starting /var/lib/dpkg/info/x11-common.config configure 
1:7.1.0-12
debconf (developer): -- SET x11-common/xwrapper/allowed_users Console Users 
Only
debconf (developer): -- 0 value set
debconf (developer): -- SET x11-common/xwrapper/nice_value 0
debconf (developer): -- 0 value set
debconf (developer): -- INPUT low x11-common/xwrapper/allowed_users
debconf (developer): -- 30 question skipped
debconf (developer): -- GO 
Use of uninitialized value in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, GEN1 line 4.
debconf (developer): -- 0 ok
debconf (developer): -- GET x11-common/xwrapper/allowed_users
debconf (developer): -- 0 Console Users Only
debconf (developer): -- SET x11-common/xwrapper/actual_allowed_users console
debconf (developer): -- 0 value set
debconf (developer): -- GET x11-common/xwrapper/nice_value
debconf (developer): -- 0 0
debconf (developer): -- INPUT low x11-common/xwrapper/nice_value
debconf (developer): -- 30 question skipped
debconf (developer): -- GO 
Use of uninitialized value in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, GEN1 line 9.
debconf (developer): -- 0 ok
debconf (developer): -- GET x11-common/xwrapper/nice_value
debconf (developer): -- 0 
debconf (developer): -- SET x11-common/xwrapper/nice_value 0
debconf (developer): -- 0 value set
debconf (developer): -- FSET x11-common/xwrapper/nice_value seen false
debconf (developer): -- 0 false
debconf (developer): -- FSET x11-common/xwrapper/nice_value/error seen false
debconf (developer): -- 0 false
debconf (developer): -- INPUT critical x11-common/xwrapper/nice_value/error
debconf (developer): -- 0 question will be asked
debconf (developer): -- GO 
debconf (developer): -- 0 ok
debconf (developer): -- INPUT low x11-common/xwrapper/nice_value
debconf (developer): -- 30 question skipped
debconf (developer): -- GO 
Use of uninitialized value in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, GEN1 line 17.
debconf (developer): -- 0 ok
debconf (developer): -- GET x11-common/xwrapper/nice_value
debconf (developer): -- 0 
debconf (developer): -- SET x11-common/xwrapper/nice_value 0
debconf (developer): -- 0 value set
debconf (developer): -- FSET x11-common/xwrapper/nice_value seen false
debconf (developer): -- 0 false
debconf (developer): -- FSET x11-common/xwrapper/nice_value/error seen false
debconf (developer): -- 0 false
debconf (developer): -- INPUT critical x11-common/xwrapper/nice_value/error
debconf (developer): -- 0 question will be asked
debconf (developer): -- GO 
debconf (developer): QTF: -- LEAVE EVENTLOOP 
dpkg: error processing x11-common (--configure):
 subprocess post-installation script killed by signal (Segmentation fault)
Setting up udev (0.105-2) ...
/boot/initrd.img-2.6.18-4-686 has been altered. Cannot update.

dpkg: dependency problems prevent configuration of xserver-xorg

Bug#413249: x11-common: config script hangs or fails

2007-03-03 Thread Frank Küster
Frank Küster [EMAIL PROTECTED] wrote:

 debconf (developer): -- INPUT low x11-common/xwrapper/allowed_users
 debconf (developer): -- 30 question skipped
 debconf (developer): -- GO 
 Use of uninitialized value in join or string at 
 /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, GEN1 line 4.

I tried DEBIAN_PRIORITY=low dpkg --configure -a 21 | tee error.log

and it succeeded:

Setting up x11-common (7.1.0-12) ...
debconf (developer): frontend started
debconf (developer): frontend running, package name is x11-common
debconf (developer): starting /var/lib/dpkg/info/x11-common.config configure 
1:7.1.0-12
debconf (developer): -- SET x11-common/xwrapper/allowed_users Console Users 
Only
debconf (developer): -- 0 value set
debconf (developer): -- SET x11-common/xwrapper/nice_value 0
debconf (developer): -- 0 value set
debconf (developer): -- INPUT low x11-common/xwrapper/allowed_users
debconf (developer): -- 0 question will be asked
debconf (developer): -- GO 
debconf (developer): -- 0 ok
debconf (developer): -- GET x11-common/xwrapper/allowed_users
debconf (developer): -- 0 Console Users Only
debconf (developer): -- SET x11-common/xwrapper/actual_allowed_users console
debconf (developer): -- 0 value set
debconf (developer): -- GET x11-common/xwrapper/nice_value
debconf (developer): -- 0 0
debconf (developer): -- INPUT low x11-common/xwrapper/nice_value
debconf (developer): -- 0 question will be asked
debconf (developer): -- GO 
debconf (developer): -- 0 ok
debconf (developer): -- GET x11-common/xwrapper/nice_value
debconf (developer): -- 0 0
debconf (developer): starting /var/lib/dpkg/info/x11-common.postinst configure 
1:7.1.0-12
debconf (developer): -- GET x11-common/xwrapper/actual_allowed_users
debconf (developer): -- 0 console
debconf (developer): -- GET x11-common/xwrapper/nice_value
debconf (developer): -- 0 0

Setting up xserver-xorg-core (1.1.1-19) ...
Setting up xserver-xorg-video-neomagic (1.1.1-5) ...
Setting up xserver-xorg-video-all (7.1.0-13) ...

I'm not sure whether this makes the bug less severe, feel free to
downgrade it.

Regards, Frank
-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)



Bug#410628: xkb-data: Need method (or documentation) to alter existing layouts

2007-02-12 Thread Frank Küster
Package: xkb-data
Version: 0.9-4
Severity: normal

Previously, I was using XOrg backports (6.9.0.dfsg.1-6~bpo.4) on a sarge
system, and I had written my own variant of a US keyboard layout
appropriate for typing lots of german text.  In this version, it was
possible to add new files in /etc/X11/xkb/symbols.

Now files in this directory seem to no longer be read (I'm not 100% sure
that I use the correct command):

(528)[10:00:[EMAIL PROTECTED]:~$ ls /etc/X11/xkb/symbols/pc/
us_DE  us_intl
(529)[10:01:[EMAIL PROTECTED]:~$ strace -o xkb.trace2 setxkbmap \
   -rules xfree86 -model pc104 -layout us_DE -variant intl \
   -option compose:caps
Error loading new keyboard description
(530)[10:01:[EMAIL PROTECTED]:~$ 

The trace shows that it does not at all access files in the symbols
directory, neither below /etc nor /usr/share/X11/xkb/symbols.  The
documentation in /usr/share/doc/xkb-data/README.config.gz also hints
(although unclear IMHO) that using xkb files is obsolete (though still
supported). 

Well, it also says that the new method is supposed to be far more
flexible and intuitive, but I do not agree, at least not without any
hint how to switch single keys.  In particular (just to illustrate), I
want the following changes from the standard intl variant of the us
layout: 

- make ~,  and ' not deadkeys

- move ü from y+Mod3 (AltGr) to u+Mod3, similar for ö, and ä

- Provide § also on p+Mod3 (it's called Paragraph in german)

TIA, Frank





-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (99, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

-- no debconf information

-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)



Bug#403061: xorg-docs: FTBFS if no network is available: tries to fetch DTD from oasis-open.org

2006-12-14 Thread Frank Küster
tags 403061 patch

Lucas Nussbaum [EMAIL PROTECTED] wrote:

 openjade tries to fetch the DTD from www.oasis-open.org, then fails loudly. It
 would be better if your package did not fail to build when no network
 connection is available.

It needs docbookx.xml which is in docbook.xml.  In other words, the
package is missing a Build-Dependency.  Here's the patch:

$ diff -Nur xorg-docs-1.2+git20061105{,.new}/
diff -Nur xorg-docs-1.2+git20061105/debian/changelog 
xorg-docs-1.2+git20061105.new/debian/changelog
--- xorg-docs-1.2+git20061105/debian/changelog  2006-12-14 18:11:02.0 
+0100
+++ xorg-docs-1.2+git20061105.new/debian/changelog  2006-12-14 
17:38:01.0 +0100
@@ -1,3 +1,11 @@
+xorg-docs (1:1.2+git20061105-2.1~1) unstable; urgency=low
+
+  * Added Build-Dependency on docbook-xml to fix FTBFS if no network is
+available.  Thanks to Lucas Nussbaum [EMAIL PROTECTED] and
+the Grid'5000 project (closes: #403061).
+
+ -- Frank KÃŒster [EMAIL PROTECTED]  Thu, 14 Dec 2006 17:38:01 +0100
+
 xorg-docs (1:1.2+git20061105-2) unstable; urgency=low
 
   [ Julien Cristau ]
diff -Nur xorg-docs-1.2+git20061105/debian/control 
xorg-docs-1.2+git20061105.new/debian/control
--- xorg-docs-1.2+git20061105/debian/control2006-12-14 18:11:02.0 
+0100
+++ xorg-docs-1.2+git20061105.new/debian/control2006-12-14 
17:35:50.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian X Strike Force debian-x@lists.debian.org
 Uploaders: David Nusinow [EMAIL PROTECTED], Branden Robinson [EMAIL 
PROTECTED]
-Build-Depends: debhelper (= 5.0.0), pkg-config, docbook-utils, docbook (= 
4.2), xorg-sgml-doctools, quilt
+Build-Depends: debhelper (= 5.0.0), pkg-config, docbook-utils, docbook (= 
4.2), xorg-sgml-doctools, quilt, docbook-xml
 Standards-Version: 3.7.2.2
 
 Package: xorg-docs



Regards, Frank
-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)



Spelling problem (umlauts) in xorg changelog

2006-05-05 Thread Frank Küster
Hi,

xorg (1:7.0.16) unstable; urgency=low

[...]
  * Add xfree86-common transitional package. This package is meant to remove
files that were moved to x11-common, like Xsession. Thanks Frank Kuster.
Thanks to Daniel Stone for the fix. (closes: #354146)

First of all, thanks for fixing this!  

But my name is Küster, and the dots are not just accents as in french
élève.  If you can't type the umlaut, please use the transliteration
Kuester (and likewise ä-ae, ö-oe, ß-ss.  And for other languages
æ-ae, å-aa, ø-oe).

I wouldn't mind if you change that in the old changelog ;-), but anyway
please keep it in mind in the future.

Regards, Frank
-- 
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)



Re: Spelling problem (umlauts) in xorg changelog

2006-05-05 Thread Frank Küster
David Martínez Moreno [EMAIL PROTECTED] wrote:

 El viernes, 5 de mayo de 2006 13:39, Frank Küster escribió:
 But my name is Küster, and the dots are not just accents as in french
 élève.  If you can't type the umlaut, please use the transliteration
 Kuester (and likewise ä-ae, ö-oe, ß-ss.  And for other languages
 æ-ae, å-aa, ø-oe).

 I wouldn't mind if you change that in the old changelog ;-), but anyway
 please keep it in mind in the future.

   Hello, Frank. I fixed your surname in SVN, I hope that it is right now. 
 You 
 can check in 
 http://necrotic.deadbeast.net/svn/xorg-x11/trunk/debian/xorg/debian/changelog.

Yes, it's fine now, thanks.

Regards, Frank
-- 
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)



Bug#365714: emacs21: FTBFS on most architectures, xaw issues.

2006-05-02 Thread Frank Küster
Package: emacs21
Version: 21.4a-1
Severity: serious

Hold on, this is a multistep bugreport which covers a couple of issues
and *might* finally boil down to xaw3dg-dev and/or libxaw.

According to http://buildd.debian.org/build.php?arch=pkg=emacs21,
building of emacs after the last NMU failed on most architectures.  I'm
confused, though, because the NMU was in January according to the
changelog, and makes the package is uninstallable on most architectures.
This is because emacs21-bin-common depends on
emacs21-common=${Source-Version}, and emacs21-common has now the NMU
version number.  But this should have shown up much earlier, it's like
as if the NMU was not in fact in the archive the last months.

As to the actual failure, it doesn't look as if it should be related to
the NMU patch, and this is some other strange thing.  On i386, it fails
with 

i486-linux-gnu-gcc -c -DUSE_LUCID -Demacs -DHAVE_CONFIG_H -DUSE_LUCID  -I. 
-I/build/buildd/emacs21-21.4a/src -D_BSD_SOURCE -DDEBIAN -g -O2 
-DPURESIZE=500 -I../src /build/buildd/emacs21-21.4a/lwlib/lwlib.c
/build/buildd/emacs21-21.4a/lwlib/lwlib.c:52:27: error: X11/Xaw/Paned.h: No 
such file or directory
make[5]: *** [lwlib.o] Error 1

Now Paned.h is in libxaw8-dev, which is installed as an indirect
build-dependency.  Maybe this has to do with the XOrg transition, the
headers have changed there location:

usr/X11R6/include/X11/Xaw/Paned.h   libdevel/libxaw8-dev
usr/include/X11/Xaw/Paned.h x11/libxaw-headers

And maybe the underlying bug is that xaw3dg-dev still depends on
libxaw8-dev | libxaw7-dev | libxaw6-dev but should have dropped
libxaw8-dev? 

Regards, Frank

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (99, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.15-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages emacs21 depends on:
ii  emacs21-bin-common21.4a-1The GNU Emacs editor's shared, arc
ii  libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an
ii  libice6   6.9.0.dfsg.1-5bpo1 Inter-Client Exchange library
ii  libjpeg62 6b-10  The Independent JPEG Group's JPEG 
ii  libncurses5   5.4-4  Shared libraries for terminal hand
ii  libpng12-01.2.8rel-1 PNG library - runtime
ii  libsm66.9.0.dfsg.1-5bpo1 X Window System Session Management
ii  libtiff4  3.7.2-3Tag Image File Format (TIFF) libra
ii  libungif4g4.1.3-2sarge1  shared library for GIF images (run
ii  libx11-6  6.9.0.dfsg.1-5bpo1 X Window System protocol client li
ii  libxext6  6.9.0.dfsg.1-5bpo1 X Window System miscellaneous exte
ii  libxmu6   6.9.0.dfsg.1-5bpo1 X Window System miscellaneous util
ii  libxpm4   6.9.0.dfsg.1-5bpo1 X pixmap library
ii  libxt66.9.0.dfsg.1-5bpo1 X Toolkit Intrinsics
ii  xaw3dg1.5+E-8Xaw3d widget set
ii  xlibs 6.9.0.dfsg.1-5bpo1 X Window System client libraries m
ii  zlib1g1:1.2.2-4.sarge.2  compression library - runtime

-- no debconf information

-- 
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)




tetex-bin dropping xaw8 (was: xaw8)

2006-03-26 Thread Frank Küster
David Nusinow [EMAIL PROTECTED] wrote:

Because xaw8 is functionally equivalent to xaw7 in every way except for
 the xprint suppot, if your app does not need this specific feature then you
 can safely depend on xaw7, leaving us to remove xaw8 from the archive. If
 any of you do specifically need this support, please let us know (M-F-T set
 to debian-x@lists.debian.org) so that we can support you as necessary. If
 you don't need this specific feature though, *please* let us know so we
 are sure we can kill this package without harming anyone.
[...]
 teTeX maintainers debian-tetex-maint@lists.debian.org
tetex-bin

Great news, it makes backporting easier.  We'll drop the build-dep on xaw8.

Regards, Frank
-- 
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)



Bug#354146: x11-common: Cannot upgrade from sarge: file conflict with xfree86-common

2006-03-15 Thread Frank Küster
Hi!

Does really nobody care about this serious bug - it hinders very much
testing of upgrades from sarge to etch.

Frank Küster [EMAIL PROTECTED] wrote:

 Package: x11-common
 Version: 1:7.0.0
 Severity: grave

 After login in a sarge chroot, I installed tetex-bin (probably that can
 be much minimized to only xfree86-common, but I don't have time for
 testing) and then changed sources.list to point to sid.

In fact it's really simple - just install xfree86-common in a sarge
pbuilder chroot, add sid or etch to sources.list, and do the
dist-upgrade. 

 dpkg: error processing 
 /var/cache/apt/archives/x11-common_6.9.0.dfsg.1-4_all.deb (--unpack):
  trying to overwrite `/etc/X11/Xsession', which is also in package 
 xfree86-common
 dpkg-deb: subprocess paste killed by signal (Broken pipe)

The message also sounds as if the fix were particularly easy.

Regards, Frank
-- 
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)




Bug#354146: x11-common: Cannot upgrade from sarge: file conflict with xfree86-common

2006-02-23 Thread Frank Küster
Package: x11-common
Version: 1:7.0.0
Severity: grave

After login in a sarge chroot, I installed tetex-bin (probably that can
be much minimized to only xfree86-common, but I don't have time for
testing) and then changed sources.list to point to sid.

After apt-get update, I get upon apt-get dist-upgrade (everything with
DEBIAN_FRONTEND=noninteractive): 

[...]
Unpacking replacement xfree86-common ...
dpkg: warning - unable to delete old directory `/etc/X11/Xsession.d': Directory 
not empty
dpkg: warning - unable to delete old directory `/etc/X11/Xresources': Directory 
not empty
Selecting previously deselected package x11-common.
Unpacking x11-common (from .../x11-common_6.9.0.dfsg.1-4_all.deb) ...
dpkg: error processing 
/var/cache/apt/archives/x11-common_6.9.0.dfsg.1-4_all.deb (--unpack):
 trying to overwrite `/etc/X11/Xsession', which is also in package 
xfree86-common
dpkg-deb: subprocess paste killed by signal (Broken pipe)




-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (100, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.15-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages x11-common depends on:
ii  debconf [debconf-2.0] 1.4.30.13  Debian configuration management sy
ii  debianutils   2.8.4  Miscellaneous utilities specific t
ii  lsb-base  3.0-11bpo1 Linux Standard Base 3.0 init scrip

-- debconf information:
  x11-common/experimental_packages:

-- 
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)




Re: License of fonts included in X.org sources

2005-10-18 Thread Frank Küster
Hi,

it just occurred to me that the X strike force might be a better place
to ask this:

Frank Küster [EMAIL PROTECTED] wrote:

 Dear debian-legal people,

 Ralf Stubner [EMAIL PROTECTED] wrote:

 It is quite odd that on the one hand Adobe says that all the rights are
 with the X consortion, while on the other hand there is no license
 information what so ever from X.org or Xfree.

 And some person (Han The Thanh) tried to get information from them,
 because he wanted to distribute a modified version, and didn't get a
 response for months.

 Do you know which person we could contact among the X.org people?  

Regards, Frank

-- 
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer



Re: License of fonts included in X.org sources

2005-10-18 Thread Frank Küster
Daniel Stone [EMAIL PROTECTED] wrote:

 On Tue, Oct 18, 2005 at 02:50:32PM +0200, Frank Küster wrote:
  Do you know which person we could contact among the X.org people?  

 More context, please.  Which fonts?

In this special case, it's about the Utopia fonts 

gsfonts-other-6.0/putbi.pfa gsfonts-other-6.0/putb.pfa
gsfonts-other-6.0/putri.pfa gsfonts-other-6.0/putr.pfa

 Fonts are a particularly hairy area of our licensing.  If the licence
 information rests with 'the X consortium', then it may well still be
 tied up deep in the corridors of TOG, or within the old X.Org group.
 In any case, the current X.Org Foundation doesn't have it in any
 official sense, but knowing which font is a good start.

 Try [EMAIL PROTECTED]; some of the people from the old XC
 still hang around there.

Well, the problem was that someone probably already did that:

, Here is an excerpt from Thanh's mail ([EMAIL PROTECTED]):
| 
| However I am not sure that I can modify them to add
| vietnamese support, because I am very ignorant of
| license/copyright issues 
| 
| Concerning Adobe Utopia, I did my best to try to find out
| the answer, but without success: I asked people at Adobe
| first and got a response saying that they have granted the
| font license to X Consortium, so now only X Consortium can
| grant the permission to modify these fonts. I wrote to X.Org
| and got a response saying that  my question is being processed
| and then nothing (it was a few months ago). So I gave it up.
`

This is why I asked whether anybody knows about a specific person we
could contact.  Or at least about a subject that might attract the
people who might know.

TIA, Frank
-- 
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer