Bug#495889: ski_1.3.2-4(sparc/unstable): FTBFS, linux/syscall-linux.c:2253: error: 'TIOCGHAYESESP' undeclared (first use in this function)

[Martin Zobel-Helas]

Package: ski
Version: 1.3.2-4
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of ski_1.3.2-4 on spontini by sbuild/sparc 99.99
> Build started at 20080821-0113

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: cdbs (>= 0.4.23-1.1), debhelper (>= 5), dpatch, autoconf, 
> autogen, automake1.9, libtool, bison, flex, gawk, gperf, libelfg0-dev, 
> libncurses5-dev, chrpath, sharutils, libltdl3-dev, pkg-config, libglade2-dev, 
> libgnomeui-dev

[...]

> linux/syscall-linux.c:2253: error: 'TIOCGHAYESESP' undeclared (first use in 
> this function)
> linux/syscall-linux.c:3012: warning: pointer targets in passing argument 2 of 
> 'simroot' differ in signedness
> linux/syscall-linux.c:3681: warning: cast from pointer to integer of 
> different size
> linux/syscall-linux.c:3681: warning: cast from pointer to integer of 
> different size
> make[5]: *** [syscall-linux.lo] Error 1
> make[5]: Leaving directory `/build/buildd/ski-1.3.2/src'
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory `/build/buildd/ski-1.3.2/src'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory `/build/buildd/ski-1.3.2/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/ski-1.3.2'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/ski-1.3.2'
> make: *** [debian/stamp-makefile-build] Error 2
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=sparc&pkg=ski&ver=1.3.2-4




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

Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

[Hamish Moffatt]

On Wed, Aug 20, 2008 at 09:42:21PM -0700, Junichi Uekawa wrote:
> I'm a bit worried that this needs to be fixed for 
> xpdf-chinese-simplified
> xpdf-chinese-traditional
> xpdf-korean
> xpdf-japanese
> 
> packages. The fix would probably be simple. It should probably be
> hardlinks rather than symlinks considering dpkg behavior wrt symlinked
> dirs.

You can't hardlink directories though, so we might as well symlink the
individual files.

> I'd like this fix included in lenny so that we don't see a regression
> in Debian for Japanese users.
> 
> 
> There was a package in the NEW queue 'poppler-data' which should
> really have fixed this bug.
> http://ftp-master.debian.org/new/poppler-data_0.2.0-1.html
> 
> That going into Debian sid would fix this bug also, but not quite sure
> if it's reasonable to expect a new package to enter Debian lenny.

I kinda think it's in poppler's domain to fix this; logically
xpdf-japanese (etc) exists only to enhance xpdf. poppler-data appears to
be a good solution.

thanks,
Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>



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

Processed: severity of 495717 is normal, tagging 495717

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.35
> severity 495717 normal
Bug#495717: heimdal-kdc: Heimdal KDC with LDAP backend not pointing properly to 
slapd socket
Severity set to `normal' from `grave'

> tags 495717 moreinfo unreproducible
Bug#495717: heimdal-kdc: Heimdal KDC with LDAP backend not pointing properly to 
slapd socket
There were no tags set.
Tags added: moreinfo, unreproducible

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

[Junichi Uekawa]

Hi,

I'm a bit worried that this needs to be fixed for 
xpdf-chinese-simplified
xpdf-chinese-traditional
xpdf-korean
xpdf-japanese

packages. The fix would probably be simple. It should probably be
hardlinks rather than symlinks considering dpkg behavior wrt symlinked
dirs.

I'd like this fix included in lenny so that we don't see a regression
in Debian for Japanese users.


There was a package in the NEW queue 'poppler-data' which should
really have fixed this bug.
http://ftp-master.debian.org/new/poppler-data_0.2.0-1.html

That going into Debian sid would fix this bug also, but not quite sure
if it's reasonable to expect a new package to enter Debian lenny.


regards,
junichi


> clone 481134 -1
> reassign 481134 xpdf-japanese
> retitle 481134 xpdf-japanese Should register fonts in fontconfig and/or 
> defoma and/or provide poppler specific symlinks
> retitle -1 poppler doesn't support xpdf config anymore
> severity -1 important
> stop
> 
> Heya,
> 
>  Executive summary: downgrading RC-ness against poppler, the burden of
>  the fix is probably on xpdf-japanese to start with.  Request for
>  comments/help on fontconfig/defoma topics.




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

Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

[Hamish Moffatt]

On Wed, Aug 20, 2008 at 04:06:40PM +0200, Loïc Minier wrote:
>  For the long term, I'd recommend either b), or c) if b) isn't possible;
>  for lenny, either the long term approach or the d) approach would work,
>  but d) would only solve the problem for this particular package.
> 
>  Because b, c), and d) will almost certainly require changes to
>  xpdf-japanese, I'm reassigning the RC counterpart of this bug to this
>  package.  I'm keeping an important bug open against poppler because it
>  can be considered a regression of poppler, but I don't think it should
>  be considered RC for poppler because:
>   * xpdf-japanese is non-free while poppler is free; perhaps this is a
> fallacy, but I don't think support for a non-free package should
> affect the Debian release; if this is considered >= serious
> severity, it shouldn't be release-blocking
>   * it's an upstream design decision that poppler doesn't support xpdf
> config/data and poppler doesn't aim to be compatible with xpdf's
> config/data: xpdf-japanese needs to grow compatibility with poppler
> instead

Patches for xpdf-japanese would be most welcome. I'm not familiar with
the details of fontconfig, defoma etc.

Maybe the relevant data in xpdf-japanese should be moved into
cmap-adobe-japan1 instead. Probably xpdf-japanese's additional CMaps
should move too; I thought I submitted a bug about this years ago but I
don't see it now.

Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>



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

Processed: Re: Bug#495717: heimdal-kdc: Heimdal KDC with LDAP backend not pointing properly to slapd socket

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign #495717 slapd
Bug#495717: heimdal-kdc: Heimdal KDC with LDAP backend not pointing properly to 
slapd socket
Bug reassigned from package `heimdal-kdc' to `slapd'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495806: pam_authenticate segfault results in authentication success (was: Locked screen accepts any password to unlock)

[Steve Langasek]

reassign 495879 pam
found 495879 1.0.1-1
retitle 495879 pam_unix returns success when child process dies with signal
severity 495879 minor
tags 495879 = confirmed upstream
reopen 495879
thanks

On Thu, Aug 21, 2008 at 01:46:40PM +1000, Ben Finney wrote:
> The segfault in pam_authenticate needs to be addressed in the pam 
> package.

> However, screen's behaviour in this instance is also buggy and 
> insecure: i.e., that screen treats "segfault in pam_authenticate" as 
> "successful authentication".

> Cloning and retitling for this screen bug.

No, there is no error in screen that I've found.  I would have done this
clone/reassign myself if I had been able to find one.  The failure is that,
when the child process that was spawned for unix_chkpwd dies with a signal,
pam_unix itself returns PAM_SUCCESS.

Julien Cristau has already worked on a patch for this, which is now in my
possession and will be forwarded upstream when I get a chance.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]



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

Processed: Re: Bug#495806: pam_authenticate segfault results in authentication success (was: Locked screen accepts any password to unlock)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 495879 pam
Bug#495879: pam_authenticate segfault results in authentication success
Bug reassigned from package `screen' to `pam'.

> found 495879 1.0.1-1
Bug#495879: pam_authenticate segfault results in authentication success
Bug marked as found in version 1.0.1-1 and reopened.

> retitle 495879 pam_unix returns success when child process dies with signal
Bug#495879: pam_authenticate segfault results in authentication success
Changed Bug title to `pam_unix returns success when child process dies with 
signal' from `pam_authenticate segfault results in authentication success'.

> severity 495879 minor
Bug#495879: pam_unix returns success when child process dies with signal
Severity set to `minor' from `grave'

> tags 495879 = confirmed upstream
Bug#495879: pam_unix returns success when child process dies with signal
Tags were: security
Tags set to: confirmed, upstream

> reopen 495879
Bug#495879: pam_unix returns success when child process dies with signal
Bug is already open, cannot reopen.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495806: pam_authenticate segfault results in authentication success (was: Locked screen accepts any password to unlock)

[Julien Cristau]

On Thu, Aug 21, 2008 at 13:46:40 +1000, Ben Finney wrote:

> However, screen's behaviour in this instance is also buggy and 
> insecure: i.e., that screen treats "segfault in pam_authenticate" as 
> "successful authentication".
> 
This is wrong.  screen has no way to know that unix_chkpwd segfaulted.
It's indeed a different bug, but it's still in pam.

Cheers,
Julien



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

Bug#495806: pam_authenticate segfault results in authentication success (was: Locked screen accepts any password to unlock)

[Ben Finney]

clone 495806 -1
reassign -1 screen
retitle -1 pam_authenticate segfault results in authentication success
thanks

On 20-Aug-2008, Nico Golde wrote:
> It looks like a pam problem. I couldn't reproduce this with pam 
> 0.99.7.1-7 but can with 1.0.1-2.
> From screen (attacher.c):
> 
> 875 #ifdef USE_PAM
> 876   PAM_conversation.appdata_ptr = cp1;
> 877   pam_error = pam_start("screen", ppp->pw_name, 
> &PAM_conversation, &pamh);
> 878   if (pam_error != PAM_SUCCESS)
> 879 AttacherFinit(SIGARG);  /* goodbye */
> 880   pam_error = pam_authenticate(pamh, 0);
> 881   pam_end(pamh, pam_error);
> 882   PAM_conversation.appdata_ptr = 0;
> 883   if (pam_error == PAM_SUCCESS)
> 884 break;
> 885 #else
> 
> This is done in a loop to check the password.
> A similar piece of code exists in 
> /usr/share/doc/libpam0g-dev/examples/check_user.c.
> 
> [EMAIL PROTECTED]:/tmp$] cp /usr/share/doc/libpam0g-dev/examples/check_user.c 
> .
> [EMAIL PROTECTED]:/tmp$] gcc -lpam -lpam_misc check_user.c -o check_user
> [EMAIL PROTECTED]:/tmp$] ./check_user nion; date; tail -1 /var/log/kern.log
> Authenticated
> Mi 20. Aug 20:01:40 CEST 2008
> Aug 20 20:01:40 coredump kernel: [1073387.605090] check_user[20665]: segfault 
> at 0 ip 7f9a2ebf40f9 sp 7fff37983980 error 4 in pam_unix.so[7f9a2ebea000+c000]
> 
> The segfault happens on the pam_authenticate call as far as I can see.
> 
> Reassigning to pam...

The segfault in pam_authenticate needs to be addressed in the pam 
package.

However, screen's behaviour in this instance is also buggy and 
insecure: i.e., that screen treats "segfault in pam_authenticate" as 
"successful authentication".

Cloning and retitling for this screen bug.

-- 
 \“I used to work in a fire hydrant factory. You couldn't park |
  `\  anywhere near the place.” —Steven Wright |
_o__)  |
Ben Finney <[EMAIL PROTECTED]>


signature.asc
Description: Digital signature

Processed: pam_authenticate segfault results in authentication success (was: Locked screen accepts any password to unlock)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> clone 495806 -1
Bug#495806: segfault in pam_unix.so on pam_authenticate call
Bug 495806 cloned as bug 495879.

> reassign -1 screen
Bug#495879: segfault in pam_unix.so on pam_authenticate call
Bug reassigned from package `pam' to `screen'.

> retitle -1 pam_authenticate segfault results in authentication success
Bug#495879: segfault in pam_unix.so on pam_authenticate call
Changed Bug title to `pam_authenticate segfault results in authentication 
success' from `segfault in pam_unix.so on pam_authenticate call'.
(By the way, that Bug is currently marked as done.)

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495877: [bitlbee] Old account files are still readable by root only

[Mathieu Petit-Clair]

Package: bitlbee
Version: 1.2.1-2
Severity: grave

--- Please enter the report below this line. ---
I upgraded to 1.2.1-2 this morning, and Bitlbee couldn't find my account
file in /var/lib/bitlbee - the xml file was readable only by root, but
Bitlbee is now running as 'bitlbee'.  Bitlbee was saying "The nick is
(probably) not registered".

Using 'chown bitlbee.bitlbee' on the file fixed this.

--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.26-5-generic

Debian Release: lenny/sid
  500 intrepidftp.iinet.net.au
  500 intrepidau.archive.ubuntu.com

--- Package information. ---
Depends (Version) | Installed
=-+-=
libc6(>= 2.7) | 2.8~20080505-0ubuntu6
libevent1   (>= 1.3e) | 1.3e-3
libglib2.0-0  (>= 2.16.0) | 2.17.7-1
libgnutls26  (>= 2.4.0-0) | 2.4.1-1build1
adduser   | 3.108ubuntu1
net-tools | 1.60-19ubuntu3
debconf   (>= 1.2.0)  | 1.5.23
 OR debconf-2.0   |
debianutils (>= 1.16) | 2.29ubuntu1




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

Processed: Re: Bug#495694: openoffice.org-writer2latex: uninstallable

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 495694 important
Bug#495694: installation crashes with JVM error
Severity set to `important' from `grave'

> tag 495694 - moreinfo
Bug#495694: installation crashes with JVM error
Tags were: moreinfo unreproducible
Tags removed: moreinfo

> tag 495694 - unreproducible
Bug#495694: installation crashes with JVM error
Tags were: unreproducible
Tags removed: unreproducible

> reassign 495694 openoffice.org
Bug#495694: installation crashes with JVM error
Bug reassigned from package `openoffice.org-writer2latex' to `openoffice.org'.

> retitle 495694 doesn't work with cacao as JVM
Bug#495694: installation crashes with JVM error
Changed Bug title to `doesn't work with cacao as JVM' from `installation 
crashes with JVM error'.

> clone 495694 -1
Bug#495694: doesn't work with cacao as JVM
Bug 495694 cloned as bug 495876.

> reassign -1 cacao-oj6-jre
Bug#495876: doesn't work with cacao as JVM
Bug reassigned from package `openoffice.org' to `cacao-oj6-jre'.

> retitle -1 Aborts when used by OOo
Bug#495876: doesn't work with cacao as JVM
Changed Bug title to `Aborts when used by OOo' from `doesn't work with cacao as 
JVM'.

> block 495694 by -1
Bug#495876: Aborts when used by OOo
Bug#495694: doesn't work with cacao as JVM
Was not blocked by any bugs.
Blocking bugs of 495694 added: 495876

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495694: openoffice.org-writer2latex: uninstallable

[Rene Engelhard]

severity 495694 important
tag 495694 - moreinfo
tag 495694 - unreproducible
reassign 495694 openoffice.org
retitle 495694 doesn't work with cacao as JVM
clone 495694 -1
reassign -1 cacao-oj6-jre
retitle -1 Aborts when used by OOo
block 495694 by -1
thanks

Hi,

Benoît Dejean wrote:
> Le mercredi 20 août 2008 à 20:29 +0200, Rene Engelhard a écrit :
> > Hi,
> > 
> > Benoît Dejean wrote:
> > > > And why do you think this is a writer2latex problem and not a
> > > > problem in whatever JVM you use?
> > > > Which one did you use (set it Tools-Options in OOo).
> > > 
> > > I haven't set anything. I used to have gcj but switched to cacao because
> > 
> > But what is set in OOos options? Please look.
> 
> At the beginning, nothing was set.
> Setting this option to either openjdk or java-compat-gcj makes 'unopkg
> remove' work and the package installable/removable/etc. unopkg is not
> very broken since with cacao-jvm 'unopkg gui' works.
> 
> So either cacao is broken or OOo doesn't support cacao or both.

Yes...

At least OOo never supported cacao standalone before as a JVM so I am not
sure at all whether it's supposed to work with cacao "disguised" in an
OpenJDK 6 JDK.

Reassigning/Cloning. (And downgrading.)

Regards,

Rene



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

Processed (with 2 errors): your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tag 492333 -unreproducible +confirmed
Unknown tag/s: +confirmed.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid 
help security upstream pending sarge sarge-ignore experimental d-i confirmed 
ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny 
lenny-ignore.

Bug#492333: libpam-mount fails with sudo
Tags were: unreproducible
Tags removed: unreproducible

> tag 492559 -unreproducible +fixed-upstream
Unknown tag/s: +fixed-upstream.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid 
help security upstream pending sarge sarge-ignore experimental d-i confirmed 
ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny 
lenny-ignore.

Bug#492559: libpam-mount 0.43 no longer works with crypted discs
Tags were: unreproducible
Tags removed: unreproducible

> tag 493497 +fixed-upstream
Bug#493497: libpam-mount: volume sgrp=xxx fails in 0.43 for ldap accounts
There were no tags set.
Tags added: fixed-upstream

> tag 493234 +fixed-upstream
Bug#493234: su: double free or corruption
There were no tags set.
Tags added: fixed-upstream

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#493998: marked as done (libpigment0.3-5 should probably Replaces: libpigment0.3-4 (= 0.3.6-1))

[Debian Bug Tracking System]

Your message dated Thu, 21 Aug 2008 00:02:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#493998: fixed in pigment 0.3.6-3
has caused the Debian Bug report #493998,
regarding libpigment0.3-5 should probably Replaces: libpigment0.3-4 (= 0.3.6-1)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
493998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493998
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libpigment0.3-5
Version: 0.3.6-2
Severity: normal


Hello,

While trying to install libpigment0.3-dev (and libpigment0.3-5):

Unpacking libpigment0.3-5 (from .../libpigment0.3-5_0.3.6-2_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libpigment0.3-5_0.3.6-2_i386.deb (--unpack):
Trying to overwrite `/usr/lib/libpigment-0.3.so.5.0.0', which is also in 
libpigment0.3-4

Perhaps a "Replaces: libpigment0.3-4 (= 0.3.6-1)" would fix it?

Thanks,

Anthony Fok

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libpigment0.3-5 depends on:
ii  libatk1.0-01.22.0-1  The ATK accessibility toolkit
ii  libc6  2.7-13GNU C Library: Shared libraries
ii  libcairo2  1.6.4-6   The Cairo 2D vector graphics libra
ii  libgl1-mesa-glx [libgl1]   7.0.3-5   A free implementation of the OpenG
ii  libglib2.0-0   2.16.5-1  The GLib library of C routines
ii  libgstreamer-plugins-base0 0.10.20-1 GStreamer libraries from the "base
ii  libgstreamer0.10-0 0.10.20-1 Core GStreamer libraries and eleme
ii  libgtk2.0-02.12.11-3 The GTK+ graphical user interface 
ii  libpango1.0-0  1.20.5-1  Layout and rendering of internatio
ii  libx11-6   2:1.1.4-2 X11 client-side library
ii  libxml22.6.32.dfsg-2 GNOME XML library

libpigment0.3-5 recommends no packages.

libpigment0.3-5 suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: pigment
Source-Version: 0.3.6-3

We believe that the bug you reported is fixed in the latest version of
pigment, which is due to be installed in the Debian FTP archive:

libpigment-dbg_0.3.6-3_i386.deb
  to pool/main/p/pigment/libpigment-dbg_0.3.6-3_i386.deb
libpigment0.3-5_0.3.6-3_i386.deb
  to pool/main/p/pigment/libpigment0.3-5_0.3.6-3_i386.deb
libpigment0.3-dev_0.3.6-3_i386.deb
  to pool/main/p/pigment/libpigment0.3-dev_0.3.6-3_i386.deb
pigment_0.3.6-3.diff.gz
  to pool/main/p/pigment/pigment_0.3.6-3.diff.gz
pigment_0.3.6-3.dsc
  to pool/main/p/pigment/pigment_0.3.6-3.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Loic Minier <[EMAIL PROTECTED]> (supplier of updated pigment package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 21 Aug 2008 01:40:43 +0200
Source: pigment
Binary: libpigment0.3-5 libpigment0.3-dev libpigment-dbg
Architecture: source i386
Version: 0.3.6-3
Distribution: unstable
Urgency: low
Maintainer: Maintainers of GStreamer packages <[EMAIL PROTECTED]>
Changed-By: Loic Minier <[EMAIL PROTECTED]>
Description: 
 libpigment-dbg - User interfaces with embedded multimedia - with debug symbols
 libpigment0.3-5 - User interfaces with embedded multimedia - shared library
 libpigment0.3-dev - User interfaces with embedded multimedia - development 
files
Closes: 493998
Changes: 
 pigment (0.3.6-3) unstable; urgency=low
 .
   * Let libpigment0.3-5 Replace libpigment0.3-4 (>= 0.3.6~) to fix upgrades
 from the broken 0.3.6-1; closes: #493998.
Checksums-Sha1: 
 5d8b68c39975cfe5850ace373645e432f7bf6785 1569 pigment_0.3.6-3.dsc
 059e12ffb69a101e4799d5f44de77ef702ba021f 3332 pigment_0.3.6-3.diff.gz
 3b966eb88a346956d6842bc6534acc8b5011e6c5 185086 
libpigment0.3-5_0.3.6-3_i386.deb
 e609059a65baca29545655c2f8e958f17a38cb15 218680 
libpigment0.3-dev_0.3.6-3_i38

Processed (with 1 errors): Re: actually, this seems to be the same as the other grave bug

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> unmerge 491308 472624
Unknown command or malformed arguments to command.

> severity 472624 important
Bug#472624: fails to start: elisa silently dies
Bug#491308: elisa doesn't starts
Severity set to `important' from `grave'

> reassign 491308 pigment 0.3.6-1
Bug#491308: elisa doesn't starts
Bug#472624: fails to start: elisa silently dies
Bug reassigned from package `elisa' to `pigment'.

> close 491308 0.3.6-2
Bug#491308: elisa doesn't starts
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug#472624: fails to start: elisa silently dies
Bug marked as fixed in version 0.3.6-2, send any further explanations to 
psycheye <[EMAIL PROTECTED]>

> stop
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#491308: Workaround = removing ~/.elisa

[Loïc Minier]

On Mon, Aug 04, 2008, Andreas Henriksson wrote:
> Removing ~/.elisa/ solved the problem for me, so this seems to be some
> missing backwards-compatability / configuration parsing failure
> handling.

 The submitter has a different issue than yours (see his later message
 in the bug <[EMAIL PROTECTED]>); if you still
 have your old ~/.elisa, please file a separate bug with it attached.

-- 
Loïc Minier



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

Bug#493998: marked as done (libpigment0.3-5 should probably Replaces: libpigment0.3-4 (= 0.3.6-1))

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 22:47:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#493998: fixed in pigment 0.3.7-1
has caused the Debian Bug report #493998,
regarding libpigment0.3-5 should probably Replaces: libpigment0.3-4 (= 0.3.6-1)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
493998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493998
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libpigment0.3-5
Version: 0.3.6-2
Severity: normal


Hello,

While trying to install libpigment0.3-dev (and libpigment0.3-5):

Unpacking libpigment0.3-5 (from .../libpigment0.3-5_0.3.6-2_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libpigment0.3-5_0.3.6-2_i386.deb (--unpack):
Trying to overwrite `/usr/lib/libpigment-0.3.so.5.0.0', which is also in 
libpigment0.3-4

Perhaps a "Replaces: libpigment0.3-4 (= 0.3.6-1)" would fix it?

Thanks,

Anthony Fok

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libpigment0.3-5 depends on:
ii  libatk1.0-01.22.0-1  The ATK accessibility toolkit
ii  libc6  2.7-13GNU C Library: Shared libraries
ii  libcairo2  1.6.4-6   The Cairo 2D vector graphics libra
ii  libgl1-mesa-glx [libgl1]   7.0.3-5   A free implementation of the OpenG
ii  libglib2.0-0   2.16.5-1  The GLib library of C routines
ii  libgstreamer-plugins-base0 0.10.20-1 GStreamer libraries from the "base
ii  libgstreamer0.10-0 0.10.20-1 Core GStreamer libraries and eleme
ii  libgtk2.0-02.12.11-3 The GTK+ graphical user interface 
ii  libpango1.0-0  1.20.5-1  Layout and rendering of internatio
ii  libx11-6   2:1.1.4-2 X11 client-side library
ii  libxml22.6.32.dfsg-2 GNOME XML library

libpigment0.3-5 recommends no packages.

libpigment0.3-5 suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: pigment
Source-Version: 0.3.7-1

We believe that the bug you reported is fixed in the latest version of
pigment, which is due to be installed in the Debian FTP archive:

libpigment-dbg_0.3.7-1_i386.deb
  to pool/main/p/pigment/libpigment-dbg_0.3.7-1_i386.deb
libpigment0.3-5_0.3.7-1_i386.deb
  to pool/main/p/pigment/libpigment0.3-5_0.3.7-1_i386.deb
libpigment0.3-dev_0.3.7-1_i386.deb
  to pool/main/p/pigment/libpigment0.3-dev_0.3.7-1_i386.deb
pigment_0.3.7-1.diff.gz
  to pool/main/p/pigment/pigment_0.3.7-1.diff.gz
pigment_0.3.7-1.dsc
  to pool/main/p/pigment/pigment_0.3.7-1.dsc
pigment_0.3.7.orig.tar.gz
  to pool/main/p/pigment/pigment_0.3.7.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philippe Normand <[EMAIL PROTECTED]> (supplier of updated pigment package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 29 Jul 2008 16:14:23 +0200
Source: pigment
Binary: libpigment0.3-5 libpigment0.3-dev libpigment-dbg
Architecture: source i386
Version: 0.3.7-1
Distribution: experimental
Urgency: low
Maintainer: Maintainers of GStreamer packages <[EMAIL PROTECTED]>
Changed-By: Philippe Normand <[EMAIL PROTECTED]>
Description: 
 libpigment-dbg - User interfaces with embedded multimedia - with debug symbols
 libpigment0.3-5 - User interfaces with embedded multimedia - shared library
 libpigment0.3-dev - User interfaces with embedded multimedia - development 
files
Closes: 493998
Changes: 
 pigment (0.3.7-1) experimental; urgency=low
 .
   [ Philippe Normand ]
   * New upstream release (first one without ABI change!)
 .
   [ Loic Minier ]
   * Bump shlibs to >= 0.3.7 for above upstream release which carries API
 additions.
   * Target experimental for now as the changes are too large for lenny.
   * Let libpigment0.3-5 Replace libpigment0.3-4 (>= 0.3.6~) to fix upgrades
  

Processed: Updates

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 494223 pending
Bug#494223: xorp: FTBFS: ../../../mrt/include/netinet/pim.h:93:1: error: 
"PIM_REGISTER" redefined
Tags were: upstream
Tags added: pending

> forwarded 494223 http://bugzilla.xorp.org/bugzilla/show_bug.cgi?id=767
Bug#494223: xorp: FTBFS: ../../../mrt/include/netinet/pim.h:93:1: error: 
"PIM_REGISTER" redefined
Noted your statement that Bug has been forwarded to 
http://bugzilla.xorp.org/bugzilla/show_bug.cgi?id=767.

> forwarded 494223 YOSHIFUJI Hideaki <[EMAIL PROTECTED]>
Bug#494223: xorp: FTBFS: ../../../mrt/include/netinet/pim.h:93:1: error: 
"PIM_REGISTER" redefined
Forwarded-to-address changed from 
http://bugzilla.xorp.org/bugzilla/show_bug.cgi?id=767 to YOSHIFUJI Hideaki 
<[EMAIL PROTECTED]>.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#494223: Updates

[Jose Calhariz]

tags 494223 pending
forwarded 494223 http://bugzilla.xorp.org/bugzilla/show_bug.cgi?id=767
forwarded 494223 YOSHIFUJI Hideaki <[EMAIL PROTECTED]>
thanks

I have talked with other people at my work place and it seams this bug
is on Linux kernel headers.  So I have sent an email to the person
that possible introduced the problem in Linux kernel 2.6.26, 
YOSHIFUJI Hideaki.

Follow the text I have sent to YOSHIFUJI Hideaki:

==

Hi.

About the new file linux/pim.h and the definitions of PIM in linux
2.6.26.

The "#define PIM_REGISTER 1" was in file mroute.h and was protected by
"#ifdef __KERNEL__" until version 2.5.25.  In version 2.6.26 this
define is in file pim.h but is no longer protected by a "#ifdef
__KERNEL__".

Is this change intentional?

This change breaks the compilation of software from the project
www.xorp.org.  In the file mrt/include/netinet/pim.h for the xorp
software they define PIM messages types and use this code:

/*
 * PIM message types
 */
#define PIM_HELLO   0x0 /* PIM-SM and PIM-DM*/

#define PIM_REGISTER0x1 /* PIM-SM only  */

#define PIM_REGISTER_STOP   0x2 /* PIM-SM only  */
#define PIM_JOIN_PRUNE  0x3 /* PIM-SM and PIM-DM*/
#define PIM_BOOTSTRAP   0x4 /* PIM-SM only  */
#define PIM_ASSERT  0x5 /* PIM-SM and PIM-DM*/
#define PIM_GRAFT   0x6 /* PIM-DM only  */
#define PIM_GRAFT_ACK   0x7 /* PIM-DM only  */
#define PIM_CAND_RP_ADV 0x8 /* PIM-SM only  */
#define PIM_ALL_DF_ELECTION 0xa /* Bidir-PIM-SM only*/

You can see the bug report with more details in:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494223

I am one of the two persons that is packaging xorp for Debian. I am
talking in my personal name, not in the name of Debian, xorp project
or employer.  I am asking this to you because the problematic change
was possible introduced by:

commit 2e8046271f68198dd37451017c1a4a2432e4ec68
Author: YOSHIFUJI Hideaki <[EMAIL PROTECTED]>
Date:   Thu Apr 3 09:22:09 2008 +0900

[IPV4] MROUTE: Move PIM definitions to .

Signed-off-by: YOSHIFUJI Hideaki <[EMAIL PROTECTED]>


I am free to give you more information if you need.  I am sorry if any
of my facts is wrong.

 José Calhariz

==

José Calhariz


-- 
--
Eu quero é morrer em paz, durante o sono, como o meu avô!
E não gritando aterrorizado, como os seus passageiros...


signature.asc
Description: Digital signature

Bug#492627: wget-el: eval-after-load fix

[Peter De Wachter]

Package: wget-el
Tags: patch
Followup-For: Bug #492627

The attached patch should fix this big. It installs the w3m-wget
eval-after-load only when wget-el has already been compiled.
--- 50wget-el.el.orig   2008-08-20 22:47:12.0 +0200
+++ 50wget-el.el2008-08-21 00:27:25.0 +0200
@@ -15,12 +15,15 @@
(symbol-name flavor)
"/site-lisp/wget-el")))
   (when (file-directory-p package-dir)
-(setq load-path (cons package-dir load-path
+(setq load-path (cons package-dir load-path))
+
+(eval-after-load "w3m"
+  '(load "w3m-wget"))
+))
+
 
 (autoload 'wget "wget" "wget interface for Emacsen." t)
 (autoload 'wget-web-page "wget" "wget interface to download whole web page." t)
-(eval-after-load "w3m"
-  '(load "w3m-wget"))
 (autoload 'w3-wget "w3-wget" "wget interface for Emacs/W3." t)
 
 (eval-after-load "wget"

Processed: Bug#491057: linux-image-2.6.25-2-686: Dell Latitude D610 laptop doesn't resume with 2.6.25

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # originally sent to the wrong bug. correcting and sending to #491202
> severity 491057 important
Bug#491057: linux-image-2.6.25-2-686: Dell Latitude D610 laptop doesn't resume 
with 2.6.25
Severity set to `important' from `serious'

> severity 491202 serious
Bug#491202: linux-image-2.6.25-2-686: Dell Latitude D610 laptop doesn't resume 
with 2.6.25
Severity set to `serious' from `important'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495770: marble has rpath to insecure location (/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/)

[peter green]

isn't building with  -DCMAKE_SKIP_RPATH=ON enough to fix it without using 
chrpath ?
adding that to the CMAKE= line in debian/rules does indeed deal with the 
rpath issue




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

Bug#494514: marked as done (insserv: Test suite fail on alpha)

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 21:18:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#494514: fixed in insserv 1.12.0-2
has caused the Debian Bug report #494514,
regarding insserv: Test suite fail on alpha
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
494514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494514
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---

Package: insserv
Version: 1.12.0-1
Severity: serious
Tags: help
User: [EMAIL PROTECTED]
Usertag: incorrect-boot-order 

The build of the latest insserv version fail on alpha, because the
testsuite fail.  The last test fail, the one named "test that a
symlink in /etc/init.d/ to another script does not cause problems".

The build log is available from
http://buildd.debian.org/fetch.cgi?&pkg=insserv&ver=1.12.0-1&arch=alpha&stamp=1217971941&file=log
 >.

We have seen this kind of error before, when using tmpfs.  That was a
bug in tmpfs, see http://lkml.org/lkml/2008/7/26/71 > for the
details.  Perhaps the file system used on goetz.debian.org have the
same problem?

I tried to find a alpha machine to test on, but am unable to log into
albeniz.debian.org, the only alpha machine listed on
http://db.debian.org/machines.cgi > as open for developers.

I have no idea how to debug this.  The program work on all other
architectures where it was built.  Only m68k have an issue with
alignment and fail to build.

Happy hacking,
-- 
Petter Reinholdtsen


--- End Message ---
--- Begin Message ---
Source: insserv
Source-Version: 1.12.0-2

We believe that the bug you reported is fixed in the latest version of
insserv, which is due to be installed in the Debian FTP archive:

insserv_1.12.0-2.diff.gz
  to pool/main/i/insserv/insserv_1.12.0-2.diff.gz
insserv_1.12.0-2.dsc
  to pool/main/i/insserv/insserv_1.12.0-2.dsc
insserv_1.12.0-2_i386.deb
  to pool/main/i/insserv/insserv_1.12.0-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Petter Reinholdtsen <[EMAIL PROTECTED]> (supplier of updated insserv package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 20 Aug 2008 21:08:13 +0200
Source: insserv
Binary: insserv
Architecture: source i386
Version: 1.12.0-2
Distribution: unstable
Urgency: low
Maintainer: Petter Reinholdtsen <[EMAIL PROTECTED]>
Changed-By: Petter Reinholdtsen <[EMAIL PROTECTED]>
Description: 
 insserv- boot sequence organizer using LSB init.d script dependencies
Closes: 494514
Changes: 
 insserv (1.12.0-2) unstable; urgency=low
 .
   [ Kel Modderman ]
   * Make test_duplicate_provides() test case more realistic by placing
 initscripts in init.d dir before registering with insserv. Make sure first
 script is registered.
   * Add test_deterministic_order() test function to make sure that when two or
 more initscripts provide the same facility, the first script actually can
 be registered with insserv reliably.
   * Add 30_deterministic_order.dpatch to defend against the inconsistent
 directory stream sequence returned by readdir(3) under different
 circumstances. (Closes: #494514)
Checksums-Sha1: 
 eb0e14030979ac0d7ac48cae71a71545203f46c8 1146 insserv_1.12.0-2.dsc
 3284e6595d732c78c7e53199f25f58a4d107572c 45314 insserv_1.12.0-2.diff.gz
 bb27fa58584e6d176ee6521960f3d27ff78cd2e1 65234 insserv_1.12.0-2_i386.deb
Checksums-Sha256: 
 1e6e1c99083818f8d6739fd7292f74031bb99cfdc1e0256a827fe0ecdc5ca310 1146 
insserv_1.12.0-2.dsc
 909c79809546d448a91c02c376c7cfe0554d50c76cdf0353acacb3c50585d3f1 45314 
insserv_1.12.0-2.diff.gz
 103d701ec81d9a809244778f6552902bd043bb0c3c11de94668b1e320c0752bd 65234 
insserv_1.12.0-2_i386.deb
Files: 
 92bbdc6e8707dd4d6cd6a763513b0ee3 1146 misc optional insserv_1.12.0-2.dsc
 991efe7f6fbd885c86305908c1b319d1 45314 misc optional insserv_1.12.0-2.diff.gz
 de1c472cad0886e3398f850dc67e0813 65234 misc optional insserv_1.12.0-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFIrHbO20zMSyow1ykRAhflAJ9V30JXkipC0mOXmoAKhHYS0VlDVgCgz+hw
YCc+95lJzKWDQ7YkPbJzkoY=
=jPiR
-END PGP SIGNATURE-


--- End Message ---

Bug#495828: FTBFS: missing armel arch

[Barak A. Pearlmutter]

> Trouble is what do you mean with "32-bit" ? 32-bit memory bus? 32
> bit address space (most likely) ? default size of long ? and so
> on. The amount of combinations can explode to hands.

Well since 95% of the time the issue is pointer size, and since on all
listed architectures sizeof(char *)==sizeof(long int), and since this
is on all listed architectures either 4 or 8, the terrible
combinatorial explosion you bring up seems to be pretty much dealt
with by adding *2* options.

> The reason why not much effort has been done to make
> architecture-exclusion easy is that the better solution is simply to
> make the code more portable.

Works for some programs, but hard with others.  Seems silly to wear
hair shirts instead of cotton in order to remind ourselves that we
need to knit some silk ones...

--Barak.



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

Bug#495785: attal has rpath to insecure location (.:/usr/lib/attal)

[peter green]

tags 495785 +patch
thanks

It seems when adapting the package to work under fhs rather than from a 
single directory a new rpath was added but the old one
was never removed. I have attatched a new version of 05_rpath.diff that 
does so. Just replace the old one in debian/patches.
Index: attal-1.0~rc1+cvs20080318/config.pro
===
--- attal-1.0~rc1+cvs20080318.orig/config.pro	2008-03-01 15:49:24.0 +
+++ attal-1.0~rc1+cvs20080318/config.pro	2008-08-20 21:45:47.0 +
@@ -22,6 +22,7 @@
 	CONFIG += qt
 	CONFIG += warn_on
 	#CONFIG += staticlib
+	LIBS += -Wl,-rpath,/usr/lib/attal
 
 	!isEmpty( ATT_CROSS_COMPILE ) {
 		CONFIG += crosslinwin
Index: attal-1.0~rc1+cvs20080318/ai/ai.pro
===
--- attal-1.0~rc1+cvs20080318.orig/ai/ai.pro	2008-08-20 21:46:44.0 +
+++ attal-1.0~rc1+cvs20080318/ai/ai.pro	2008-08-20 21:47:02.0 +
@@ -34,9 +34,9 @@
 }
 QT +=  xml network
 
-unix:!macx {
-	QMAKE_LFLAGS += -Wl,-rpath,.
-}
+#unix:!macx {
+#	QMAKE_LFLAGS += -Wl,-rpath,.
+#}
 
 unix {
 	target.path = $${ATT_PREFIX}/bin/
Index: attal-1.0~rc1+cvs20080318/campaignEditor/campaignEditor.pro
===
--- attal-1.0~rc1+cvs20080318.orig/campaignEditor/campaignEditor.pro	2008-08-20 21:47:12.0 +
+++ attal-1.0~rc1+cvs20080318/campaignEditor/campaignEditor.pro	2008-08-20 21:47:29.0 +
@@ -38,9 +38,9 @@
 TRANSLATIONS += ../i18n/ru/campaign_editor_ru.ts
 TRANSLATIONS += ../i18n/it/campaign_editor_it.ts
 
-unix:!macx {
-	QMAKE_LFLAGS += -Wl,-rpath,.
-}
+#unix:!macx {
+#	QMAKE_LFLAGS += -Wl,-rpath,.
+#}
 
 unix {
 	target.path = $${ATT_PREFIX}/bin/
Index: attal-1.0~rc1+cvs20080318/client/client.pro
===
--- attal-1.0~rc1+cvs20080318.orig/client/client.pro	2008-08-20 21:48:12.0 +
+++ attal-1.0~rc1+cvs20080318/client/client.pro	2008-08-20 21:48:26.0 +
@@ -47,9 +47,9 @@
 
 TARGET = attal-client
 
-unix:!macx {
-	QMAKE_LFLAGS += -Wl,-rpath,.
-}
+#unix:!macx {
+#	QMAKE_LFLAGS += -Wl,-rpath,.
+#}
 
 unix {
 	target.path = $${ATT_PREFIX}/bin/
Index: attal-1.0~rc1+cvs20080318/scenarioEditor/scenarioEditor.pro
===
--- attal-1.0~rc1+cvs20080318.orig/scenarioEditor/scenarioEditor.pro	2008-08-20 21:48:41.0 +
+++ attal-1.0~rc1+cvs20080318/scenarioEditor/scenarioEditor.pro	2008-08-20 21:48:59.0 +
@@ -72,9 +72,9 @@
 TRANSLATIONS += ../i18n/ru/scenario_editor_ru.ts
 TRANSLATIONS += ../i18n/it/scenario_editor_it.ts
 
-unix:!macx {
-	QMAKE_LFLAGS += -Wl,-rpath,.
-}
+#unix:!macx {
+#	QMAKE_LFLAGS += -Wl,-rpath,.
+#}
 
 unix {
 	target.path = $${ATT_PREFIX}/bin/
Index: attal-1.0~rc1+cvs20080318/server/server.pro
===
--- attal-1.0~rc1+cvs20080318.orig/server/server.pro	2008-08-20 21:49:09.0 +
+++ attal-1.0~rc1+cvs20080318/server/server.pro	2008-08-20 21:49:21.0 +
@@ -40,9 +40,9 @@
 
 TARGET = attal-server
 
-unix:!macx {
-	QMAKE_LFLAGS += -Wl,-rpath,.
-}
+#unix:!macx {
+#	QMAKE_LFLAGS += -Wl,-rpath,.
+#}
 
 unix {
 	target.path = $${ATT_PREFIX}/bin/
Index: attal-1.0~rc1+cvs20080318/themeEditor/themeEditor.pro
===
--- attal-1.0~rc1+cvs20080318.orig/themeEditor/themeEditor.pro	2008-08-20 21:49:29.0 +
+++ attal-1.0~rc1+cvs20080318/themeEditor/themeEditor.pro	2008-08-20 21:49:50.0 +
@@ -81,9 +81,9 @@
 
 TARGET = attal-theme-editor
 
-unix:!macx {
-	QMAKE_LFLAGS += -Wl,-rpath,.
-}
+#unix:!macx {
+#	QMAKE_LFLAGS += -Wl,-rpath,.
+#}
 
 unix {
 	target.path = $${ATT_PREFIX}/bin/

Processed: re: attal has rpath to insecure location (.:/usr/lib/attal)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 495785 +patch
Bug#495785: attal has rpath to insecure location (.:/usr/lib/attal)
Tags were: security
Tags added: patch

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495828: marked as done (FTBFS: missing armel arch)

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 21:19:46 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#495828: fixed in raidutils 0.0.6-8
has caused the Debian Bug report #495828,
regarding FTBFS: missing armel arch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
495828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495828
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: raidutils
Version: 0.0.6-7
Severity: serious

the  armel build log:

raidutils_0.0.6-7.dsc: armel not in arch list: i386 amd64 arm armeb m32r m68k 
mips mipsel powerpc sparc

the changelog:

* target only on 32-bit architectures

armel is 32bit...

Also, s390,hppa and the unofficial sh3 and sh4 ports are missing at least.

See http://wiki.debian.org/ArchitectureSpecificsMemo for some 32/64bit
info (size of data pointer, I presume).

On Wed, Aug 20, 2008 at 05:57:33PM +0300, Build Daemon wrote:
> Automatic build of raidutils_0.0.6-7 on ALL6500 by sbuild/armel 0.56
> Build started at 20080820-1757
> **
> Failed to open ./raidutils_0.0.6-7.dsc
> Checking available source versions...
> Fetching source files...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Need to get 1487kB of source archives.
> Get:1 http://incoming.debian.org  raidutils 0.0.6-7 (dsc) [1158B]
> Get:2 http://incoming.debian.org  raidutils 0.0.6-7 (tar) [1386kB]
> Get:3 http://incoming.debian.org  raidutils 0.0.6-7 (diff) [100.0kB]
> Fetched 1487kB in 1s (764kB/s)
> Download complete and in download only mode
> raidutils_0.0.6-7.dsc: armel not in arch list: i386 amd64 arm armeb m32r m68k 
> mips mipsel powerpc sparc -- skipping
> **
> Finished at 20080820-1757
> Build needed 00:25:29, 16148k disk space


--- End Message ---
--- Begin Message ---
Source: raidutils
Source-Version: 0.0.6-8

We believe that the bug you reported is fixed in the latest version of
raidutils, which is due to be installed in the Debian FTP archive:

dpt-i2o-raidutils_0.0.6-8_i386.deb
  to pool/main/r/raidutils/dpt-i2o-raidutils_0.0.6-8_i386.deb
raidutils_0.0.6-8.diff.gz
  to pool/main/r/raidutils/raidutils_0.0.6-8.diff.gz
raidutils_0.0.6-8.dsc
  to pool/main/r/raidutils/raidutils_0.0.6-8.dsc
raidutils_0.0.6-8_i386.deb
  to pool/main/r/raidutils/raidutils_0.0.6-8_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Barak A. Pearlmutter <[EMAIL PROTECTED]> (supplier of updated raidutils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 20 Aug 2008 20:46:54 +0100
Source: raidutils
Binary: dpt-i2o-raidutils raidutils
Architecture: source i386
Version: 0.0.6-8
Distribution: unstable
Urgency: low
Maintainer: Barak A. Pearlmutter <[EMAIL PROTECTED]>
Changed-By: Barak A. Pearlmutter <[EMAIL PROTECTED]>
Description: 
 dpt-i2o-raidutils - Adaptec I2O hardware RAID management utilities
 raidutils  - Transition Package for raidutils rename to dpt-i2o-raidutils
Closes: 495828
Changes: 
 raidutils (0.0.6-8) unstable; urgency=low
 .
   * Include amd64 plus all 32-bit (4-byte pointer) architectures listed in
 http://wiki.debian.org/ArchitectureSpecificsMemo in debian/control
 architecture field (closes: #495828)
Checksums-Sha1: 
 243ba580005a19581e60ccc490d07b3cc8013a59 1185 raidutils_0.0.6-8.dsc
 3ff7f28e912b522d959592250e7ccc6b4d73d961 100069 raidutils_0.0.6-8.diff.gz
 b1b7a0cac809b64e9a82c8d81f8de2279cfc0abe 222048 
dpt-i2o-raidutils_0.0.6-8_i386.deb
 b3c5d76b69b3e471c79419ed007e12f989c91e8b 4290 raidutils_0.0.6-8_i386.deb
Checksums-Sha256: 
 fcaa6c97716a31b2dcb392e33f40a5bb88779e03d48769012ddbe92f70a80c6e 1185 
raidutils_0.0.6-8.dsc
 e8ab30c4f312f9afa30a136258ee8d20a17341bc9b7620bd22e4a31b619a2555 100069 
raidutils_0.0.6-8.diff.gz
 b6ab1c991b2a228cade39cb4c67f6b73648cb091556fcd6c09b1f27146314223 222048 
dpt-i2o-raidutils_0.0.6-8_i386.deb
 89fdb384dbad8b8451d03bd2f5107547494a289c758cd78deba667d4427d2ca1 4290 
raid

Bug#488300: Perl symbol problem - release critical (Re: Bug#489132)

[Niko Tyni]

On Thu, Jul 03, 2008 at 08:11:05PM +0100, Ian Jackson wrote:
> Raphael Hertzog writes ("Bug#489132: lenny release notes, upgrade dpkg 
> first"):
> > To work-around a problem that can happen in the perl 5.10 upgrade (see
> > #479711), the perl scripts contained in dpkg (update-alternatives,
> > dpkg-divert) have been modified... but for the work-around to be used, the
> > new dpkg must obviously be installed first, before the dist-upgrade.
> 
> I don't think this is the right solution.  To be honest I'm just
> astonished at this situation, which is terrible.  It is the
> consequence of a mistake in the Debian Perl policy - a mistake which
> has caused trouble on every previous upgrade, too.

Revisiting this; #489132 and #488300 are still open and I'm (hopefully)
less confused about the issue now than in my earlier reply to #489132
and others.

Summary: I think making perl-base Pre-Depend on dpkg (>= 1.4.20) is enough
to fix this for lenny. 

> Possible solutions that I see for lenny:

> 2. Find out which modules are used in this way by Essential packages.
>Arrange somehow for those modules to fail at `require' when loaded
>with Perl 5.8 from etch.  This might involve rebuilding only
>those modules.

The only perl scripts provided by Essential packages are

/usr/bin/scriptreplay
/usr/lib/dpkg/mksplit
/usr/sbin/cleanup-info
/usr/sbin/install-info
/usr/sbin/update-alternatives
/usr/sbin/dpkg-statoverride
/usr/sbin/dpkg-divert
/usr/bin/chkdupexe

All but chkdupexe are in the dpkg package. No external modules are used
by scriptreplay, chkdupexe, and mksplit. The only module outside
perl-base that is used by the others is Locale::gettext. 

All but cleanup-info set PERL_DL_NONLAZY in their Lenny versions, which
makes the "eval 'use Locale::gettext'" call fail due to missing symbols
when liblocale-gettext-perl and perl-base are out of sync.

The Lenny version of liblocale-gettext-perl Pre-Depends on 
perl-base (>= 5.10.0-9). This makes it impossible for the Etch version
of /usr/bin/perl to see the Lenny version of Locale::gettext.

The other way around is still possible: unpacking perl-base on an Etch
system (after upgrading libc6 etc.) makes Perl 5.10 see the 5.8 version of
Locale::gettext. This breaks the Etch version of the dpkg utilities. 

The breakage could be prevented by making perl-base Pre-Depend on dpkg
(>= 1.14.20). I think this would be enough to solve the issue for lenny
and fix #488300 (and possibly #489132, but that one includes some concerns
about the need to upgrade apt manually first.)

If /usr/sbin/cleanup-info is considered part of the Essential
functionality of dpkg, it also needs to set PERL_DL_NONLAZY.
Judging by /usr/share/doc/dpkg/README.feature-removal-schedule,
that is probably not the case.

> * Suppressing lazy symbol resolution may work in this case, but it is
>   not correct.  ABI changes may result in random crashes due to
>   different structure sizes and do not necessarily involve missing
>   symbols - so the problem may go undetected.  If we think that we
>   want to fix it in etch->lenny by suppressing lazy symbol resolution,
>   we need to:
> (a) check what the actual ABI differences are and that either
> there aren't any others besides missing symbols, or that
> every module will definitely fail to load

I think it's clear that Locale::gettext fails to load both ways
when PERL_DL_NONLAZY is set:

- when compiled for 5.10.0 it needs Perl_Istack_sp_ptr from perl/libperl,
  which is not present in 5.8.8
- when compiled for 5.8.8  it needs Perl_Tstack_sp_ptr instead,
  which is not present in 5.10.0

> (b) regard this as a workaround and do something sensible next
> time.

Post-lenny, I see two options that don't involve changing the module path:

- mandate that ABI changes in the Perl XS module interface
  will always be accompanied with a symbol rename caught by
  PERL_DL_NONLAZY, and artificially do that for Debian if needed in the
  future. This practically means "just carry on and hope we don't have
  to deviate from perl upstream".

- integrate Locale::gettext in perl-base (#479681) and mandate that
  Essential:yes programs may not load non-Essential XS modules even
  opportunistically (inside an eval block) because PERL_DL_NONLAZY
  can't be trusted.  This seems to be the safer option of the two.

-- 
Niko Tyni   [EMAIL PROTECTED]



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

Bug#495770: marble has rpath to insecure location (/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/)

[Carsten Wolff]

Hi!

On Wednesday 20 August 2008, Bill Allombert wrote:
> the amd64 marble package includes a ELF file
> /usr/lib/marble/plugins/libMarbleStarsPlugin.so with a rpath pointing to
> /tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/.

Thanks for reporting this, I will fix it tomorrow morning.

Carsten



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

Bug#495770: marble has rpath to insecure location (/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/)

[Sune Vuorela]

Hi!

isn't building with  -DCMAKE_SKIP_RPATH=ON enough to fix it without using 
chrpath ?

/Sune
-- 
I cannot open a FPU, how does it work?

You cannot turn on a tool for telnetting to the shell of the Fast jumper over 
a software on the monitor.




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

Bug#495860: SILO FTBFS with kernel headers 2.6.25 and newer

[Jurij Smakov]

Package: silo
Version: 1.4.13a+git20070930-2
Severity: serious

Greetings,

It has been recently reported on the sparclinux mailing list that SILO 
fails to build against the newer kernel headers, confirmed in the 
current pbuilder chroot:

[...]
make[2]: Leaving directory 
`/tmp/buildd/silo-1.4.13a+git20070930/build-tree/first'
make[2]: Entering directory 
`/tmp/buildd/silo-1.4.13a+git20070930/build-tree/second'
gcc-4.3 -m32 -Os -Wall -I. -I../include -fomit-frame-pointer 
-fno-strict-aliasing -DSMALL_RELOC=0x28 -DLARGE_RELOC=0x38 
-fno-stack-protector -c -Wa,-Av9 -DIMGVERSION='"SILO0.99"' crt0.S
gcc-4.3 -m32 -Os -Wall -I. -I../include -fomit-frame-pointer 
-fno-strict-aliasing -DSMALL_RELOC=0x28 -DLARGE_RELOC=0x38 
-fno-stack-protector -DVERSION='"1.4.13"' -c decomp.c
gcc-4.3 -m32 -Os -Wall -I. -I../include -fomit-frame-pointer 
-fno-strict-aliasing -DSMALL_RELOC=0x28 -DLARGE_RELOC=0x38 
-fno-stack-protector -c -o malloc.o ../common/malloc.c
gcc-4.3 -m32 -Os -Wall -I. -I../include -fomit-frame-pointer 
-fno-strict-aliasing -DSMALL_RELOC=0x28 -DLARGE_RELOC=0x38 
-fno-stack-protector -c bmark.S -o bmark.o
gcc-4.3 -m32 -Os -Wall -I. -I../include -fomit-frame-pointer 
-fno-strict-aliasing -DSMALL_RELOC=0x28 -DLARGE_RELOC=0x38 
-fno-stack-protector -c main.c -o main.o
main.c:28:22: error: asm/page.h: No such file or directory
make[2]: *** [main.o] Error 1
make[2]: Leaving directory 
`/tmp/buildd/silo-1.4.13a+git20070930/build-tree/second'
make[1]: *** [all] Error 1
make[1]: Leaving directory 
`/tmp/buildd/silo-1.4.13a+git20070930/build-tree'
make: *** [build-stamp] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 
2

A current patch applied in Gentoo has been posted [1], however it is 
probably better to wait until maintainer reviews it and makes it 
official.

Cheers.

[1] http://marc.info/?t=12191873562&r=1&w=2
-- 
Jurij Smakov   [EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/  KeyID: C99E03CC



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

Bug#495770: marble has rpath to insecure location (/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/)

[peter green]

#introduces a security hole allowing access to the accounts of users who use 
the package
severity 495770 grave

tags 495770 +patch
thanks

I have prepared a patch to debian/rules which fixes the issue by removing the 
rpath from all binaries in that directory.

there is also some code in debian/rules which seems to turn lintain results 
from the previous build into lintain overrides.
This means that afacit if someone builds a package more than once (as is quite 
normal) then every lintain issue will get
overridden! I have diabled this code in my diff.





Only in marble-0.6+svn837399/data/mwdbii: PISLAND.PNT.orig
Only in marble-0.6+svn837399/data/mwdbii: PLAKE.PNT.orig
diff -ur marble-0.6+svn837399/debian/rules marble-0.6+svn837399.new/debian/rules
--- marble-0.6+svn837399/debian/rules	2008-08-20 20:45:30.0 +
+++ marble-0.6+svn837399.new/debian/rules	2008-08-20 20:27:15.0 +
@@ -68,11 +68,14 @@
 common-install-prehook-arch::
 	install -m 644 $(CURDIR)/debian/globe.xpm $(CURDIR)/debian/marble/usr/share/pixmaps/globe.xpm
 	
-common-install-arch::
-	install -D -m 644 $(CURDIR)/debian/marble.lintian $(CURDIR)/debian/marble/usr/share/lintian/overrides/marble
+#common-install-arch::
+#	install -D -m 644 $(CURDIR)/debian/marble.lintian $(CURDIR)/debian/marble/usr/share/lintian/overrides/marble
 
-common-install-indep::
-	install -D -m 644 $(CURDIR)/debian/marble-data.lintian $(CURDIR)/debian/marble-data/usr/share/lintian/overrides/marble-data
+#common-install-indep::
+#	install -D -m 644 $(CURDIR)/debian/marble-data.lintian $(CURDIR)/debian/marble-data/usr/share/lintian/overrides/marble-data
 
 common-binary-post-install-indep::
 	rm -f $(CURDIR)/debian/marble-data/usr/share/marble/data/LICENSE.txt
+
+common-binary-post-install-arch::
+	chrpath -d debian/marble/usr/lib/marble/plugins/*

Processed: re: marble has rpath to insecure location (/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> #introduces a security hole allowing access to the accounts of users who use 
> the package
> severity 495770 grave
Bug#495770: marble has rpath to insecure location 
(/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/)
Severity set to `grave' from `serious'

> tags 495770 +patch
Bug#495770: marble has rpath to insecure location 
(/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/)
Tags were: security
Tags added: patch

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Processed: tagging 495831, severity of 495831 is normal

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.35
> tags 495831 - security
Bug#495831: Entering non-existant username at login prompt causes error message
Tags were: security
Tags removed: security

> severity 495831 normal
Bug#495831: Entering non-existant username at login prompt causes error message
Severity set to `normal' from `grave'

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#494515: libgnome2-ruby1.8: "object allocation during garbage collection phase" fixed in upstream svn

[Peter De Wachter]

Tags: patch
Followup-For: Bug #494515

I found two revision in the upstream SVN that deal with garbage
collection (revisions 3255 and 3263). When I applied these changes to
the Debian package, the script runs without crashing.

(The script doesn't animate properly though, it should use a
GtkDrawingArea. Fixed version attached :)
--- a/glib/ChangeLog
+++ b/glib/ChangeLog
@@ -1,3 +1,17 @@
+2008-06-19  Kouhei Sutou  <[EMAIL PROTECTED]>
+
+	* src/rbgobj_type.c (rbgobj_lookup_class_by_gtype_body): add
+	create_class option.
+
+	* src/rbgobject.h (GTYPE2CINFO_NO_CREATE): add.
+
+	* src/rbgobject.h, src/rbgobj_type.c
+	(rbgobj_lookup_class_by_gtype_full): add.
+
+	* src/rbgobj_typeinstance.c (each_cinfo): don't create object
+	during GC to work with ruby 1.8.7.
+	Reported by Kazuhiro NISHIYAMA. Thanks!!!
+
 2008-05-23  Kouhei Sutou  <[EMAIL PROTECTED]>
 
 	* test/run-test.rb: use which not --version to detect make.
--- a/glib/src/rbgobj_type.c
+++ b/glib/src/rbgobj_type.c
@@ -39,8 +39,9 @@
 } RGObjClassInfoDynamic;
 
 typedef struct {
-  VALUE parent;
-  GType gtype;
+VALUE parent;
+GType gtype;
+gboolean create_class;
 } RGObjClassByGtypeData;
 
 static void
@@ -125,10 +126,14 @@
 return (VALUE)NULL;
 
 c = rb_hash_aref(gtype_to_cinfo, INT2NUM(gtype));
-if (!NIL_P(c)){
+if (!NIL_P(c)) {
 Data_Get_Struct(c, RGObjClassInfo, cinfo);
 return (VALUE)cinfo;
 }
+
+if (!cdata->create_class)
+	return (VALUE)NULL;
+
 c = Data_Make_Struct(rb_cData, RGObjClassInfo, cinfo_mark, NULL, cinfo);
 cinfo->gtype = gtype;
 cinfo->mark  = NULL;
@@ -230,8 +235,19 @@
 const RGObjClassInfo *
 rbgobj_lookup_class_by_gtype(GType gtype, VALUE parent)
 {
+return rbgobj_lookup_class_by_gtype_full(gtype, parent, TRUE);
+}
+
+const RGObjClassInfo *
+rbgobj_lookup_class_by_gtype_full(GType gtype, VALUE parent,
+  gboolean create_class)
+{
 VALUE critical = rb_thread_critical;
-RGObjClassByGtypeData data = { .parent = parent, .gtype = gtype };
+RGObjClassByGtypeData data;
+
+data.gtype = gtype;
+data.parent = parent;
+data.create_class = create_class;
 
 rb_thread_critical = 1;
 
--- a/glib/src/rbgobject.h
+++ b/glib/src/rbgobject.h
@@ -76,6 +76,7 @@
 
 #define CLASS2CINFO(klass) (rbgobj_lookup_class(klass))
 #define GTYPE2CINFO(gtype) (rbgobj_lookup_class_by_gtype(gtype, Qnil))
+#define GTYPE2CINFO_NO_CREATE(gtype) (rbgobj_lookup_class_by_gtype_full(gtype, Qnil, FALSE))
 #define RVAL2CINFO(obj)(rbgobj_lookup_class(CLASS_OF(obj)))
 #define GTYPE2CLASS(gtype) (rbgobj_gtype_to_ruby_class(gtype))
 #define CLASS2GTYPE(klass) (rbgobj_lookup_class(klass)->gtype)
@@ -150,8 +151,11 @@
 
 
 /* rbgobj_type.c */
-extern const RGObjClassInfo* rbgobj_lookup_class(VALUE klass);
-extern const RGObjClassInfo* rbgobj_lookup_class_by_gtype(GType gtype, VALUE parent);
+extern const RGObjClassInfo *rbgobj_lookup_class(VALUE klass);
+extern const RGObjClassInfo *rbgobj_lookup_class_by_gtype(GType gtype, VALUE parent);
+extern const RGObjClassInfo *rbgobj_lookup_class_by_gtype_full(GType gtype,
+			   VALUE parent,
+			   gboolean create_object);
 extern VALUE rbgobj_gtype_to_ruby_class(GType gtype);
 extern VALUE rbgobj_define_class(GType gtype, const gchar* name, VALUE module,
  void* mark, void* free, VALUE parent); 
--- a/glib/src/rbgobj_typeinstance.c
+++ b/glib/src/rbgobj_typeinstance.c
@@ -16,6 +16,10 @@
 
 VALUE cInstantiatable;
 
+typedef void (*ClassInfoCallbackFunc) (gpointer instance,
+   const RGObjClassInfo *class_info,
+   gpointer user_data);
+
 static VALUE
 instantiatable_s_allocate(klass)
  VALUE klass;
@@ -40,9 +44,7 @@
 /**/
 
 static void
-each_cinfo(gpointer instance,
-   void (*func)(gpointer instance, const RGObjClassInfo* cinfo, gpointer user_data),
-   gpointer user_data)
+each_cinfo(gpointer instance, ClassInfoCallbackFunc func, gpointer user_data)
 {
 const GType gtype = G_TYPE_FROM_INSTANCE(instance);
 GType* interfaces;
@@ -51,25 +53,35 @@
 interfaces = g_type_interfaces(gtype, &n_interfaces);
 {
 guint i;
-for (i = 0; i < n_interfaces; i++)
-func(instance, GTYPE2CINFO(interfaces[i]), user_data);
+for (i = 0; i < n_interfaces; i++) {
+	const RGObjClassInfo *info;
+
+	info = GTYPE2CINFO_NO_CREATE(interfaces[i]);
+	if (info)
+		func(instance, info, user_data);
+	}
 }
 
 {
-GType i;
-for (i = gtype; i != G_TYPE_INVALID; i = g_type_parent(i))
-func(instance, GTYPE2CINFO(i), user_data);
+GType type;
+for (type = gtype; type != G_TYPE_INVALID; type = g_type_parent(type)) {
+	const RGObjClassInfo *info;
+
+	info = GTYPE2CINFO_NO_CREATE(type);
+	if (info)
+		func(instance, info, user_data);
+	}
 }
 }
 
 static void
-call_cinfo_free(gpointer instance, const RGO

Bug#495828: FTBFS: missing armel arch

[Riku Voipio]

On Wed, Aug 20, 2008 at 08:41:32PM +0100, Barak A. Pearlmutter wrote:
> Well, this also assumes the relevant hardware RAID system is around;
> it can be on a motherboard or a PCI card.  I'm not sure if s390
> qualifies in that regard.

True, s390 doesn't have PCI. arm/armel/sh3/sh4 have PCI bus
on some systems,

> Is there a definitive chart of Debian architectures anywhere?  I took
> my list from /usr/share/doc/debian-policy/policy.txt.gz.

That list is probably generatad and for some reason hasn't been
regenerated since armel was introduced.

> What I'd really like to say is

>   Architecture: anything-32-bit amd64

Trouble is what do you mean with "32-bit" ? 32-bit memory bus? 32 bit
address space (most likely) ? default size of long ? and so on. The
amount of combinations can explode to hands.

The reason why not much effort has been done to make architecture-exclusion
easy is that the better solution is simply to make the code more
portable.


-- 
"rm -rf" only sounds scary if you don't have backups



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

Bug#495694: openoffice.org-writer2latex: uninstallable

[Benoît Dejean]

Le mercredi 20 août 2008 à 20:29 +0200, Rene Engelhard a écrit :
> Hi,
> 
> Benoît Dejean wrote:
> > > And why do you think this is a writer2latex problem and not a
> > > problem in whatever JVM you use?
> > > Which one did you use (set it Tools-Options in OOo).
> > 
> > I haven't set anything. I used to have gcj but switched to cacao because
> 
> But what is set in OOos options? Please look.

At the beginning, nothing was set.
Setting this option to either openjdk or java-compat-gcj makes 'unopkg
remove' work and the package installable/removable/etc. unopkg is not
very broken since with cacao-jvm 'unopkg gui' works.

So either cacao is broken or OOo doesn't support cacao or both.
-- 
Benoît Dejean
GNOME http://www.gnomefr.org/
LibGTop http://directory.fsf.org/libgtop.html


signature.asc
Description: Ceci est une partie de message	numériquement signée

Bug#495806: marked as done (segfault in pam_unix.so on pam_authenticate call)

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 19:17:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#495806: fixed in pam 1.0.1-3
has caused the Debian Bug report #495806,
regarding segfault in pam_unix.so on pam_authenticate call
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
495806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495806
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: screen
Version: 4.0.3-11
Severity: grave
Tags: security
Justification: user security hole

Hello,

Screen has started accepting any password at all at the locked screen prompt
on my testing box.  I do not know when exactly this behavior started; I just
noticed it today.  A different box running etch works as expected, i.e. only
unlocking when the user's system password is entered.

I have tested this with multiple users on the lenny box.  Searching the
Debian screen bug reports and the screen-users mailing list turns up
nothing.  The only thing I can guess right now is that it might have
something to do with new pam packages in testing.  User error is always a
possibility, too.  ;-)

Thank you,
Troy Davis

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages screen depends on:
ii  libc6 2.7-13 GNU C Library: Shared libraries
ii  libncursesw5  5.6+20080713-1 shared libraries for terminal hand
ii  libpam0g  1.0.1-2Pluggable Authentication Modules l

screen recommends no packages.

screen suggests no packages.

-- debconf information:
  screen/old_upgrade_prompt: false


--- End Message ---
--- Begin Message ---
Source: pam
Source-Version: 1.0.1-3

We believe that the bug you reported is fixed in the latest version of
pam, which is due to be installed in the Debian FTP archive:

libpam-cracklib_1.0.1-3_amd64.deb
  to pool/main/p/pam/libpam-cracklib_1.0.1-3_amd64.deb
libpam-doc_1.0.1-3_all.deb
  to pool/main/p/pam/libpam-doc_1.0.1-3_all.deb
libpam-modules_1.0.1-3_amd64.deb
  to pool/main/p/pam/libpam-modules_1.0.1-3_amd64.deb
libpam-runtime_1.0.1-3_all.deb
  to pool/main/p/pam/libpam-runtime_1.0.1-3_all.deb
libpam0g-dev_1.0.1-3_amd64.deb
  to pool/main/p/pam/libpam0g-dev_1.0.1-3_amd64.deb
libpam0g_1.0.1-3_amd64.deb
  to pool/main/p/pam/libpam0g_1.0.1-3_amd64.deb
pam_1.0.1-3.diff.gz
  to pool/main/p/pam/pam_1.0.1-3.diff.gz
pam_1.0.1-3.dsc
  to pool/main/p/pam/pam_1.0.1-3.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Langasek <[EMAIL PROTECTED]> (supplier of updated pam package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 20 Aug 2008 11:55:47 -0700
Source: pam
Binary: libpam0g libpam-modules libpam-runtime libpam0g-dev libpam-cracklib 
libpam-doc
Architecture: source all amd64
Version: 1.0.1-3
Distribution: unstable
Urgency: high
Maintainer: Steve Langasek <[EMAIL PROTECTED]>
Changed-By: Steve Langasek <[EMAIL PROTECTED]>
Description: 
 libpam-cracklib - PAM module to enable cracklib support
 libpam-doc - Documentation of PAM
 libpam-modules - Pluggable Authentication Modules for PAM
 libpam-runtime - Runtime support for the PAM library
 libpam0g   - Pluggable Authentication Modules library
 libpam0g-dev - Development files for PAM
Closes: 495806
Changes: 
 pam (1.0.1-3) unstable; urgency=high
 .
   * 055_pam_unix_nullok_secure: don't call _pammodutil_tty_secure with a NULL
 tty argument, since this will cause our helper to segfault instead of
 returning a useful value.  Thanks to Troy Davis for the report.
 Closes: #495806.
Checksums-Sha1: 
 b78df3f32cec5e9a28ec67baa12c991be621884e 1457 pam_1.0.1-3.dsc
 b668c3fda42bb60f1c674be0e542786a0fb2b4a5 141199 pam_1.0.1-3.diff.gz
 4c4b5c84769a2ac0a5a2dce886e30f092cea331c 164870 libpam-runtime_1.0.1-3_all.deb
 da299c65162b87d3dac847e13e746b46fdd1379d 286384 libpam-doc_1.0.1-3_all.deb
 9273a621b9cc8b3866ae545c978ffd0b9835e692 107392 libpam0g_1.0.1-3_amd64.deb
 c

Bug#495831: Entering non-existant username at login prompt causes error message

[Tim Rørstrøm]

Package: login
Version: 1:4.1.1-3
Severity: grave
Tags: security
Justification: user security hole

At the console login prompt, entering a username which does not exist on the 
system, will immediately show an error message, thus revealing that the 
username is in fact non-existant on the system. This dramatically reduces the 
time it would take to brute-force your way into a user's account.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26.2-core2 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages login depends on:
ii  libc6 2.7-13 GNU C Library: Shared libraries
ii  libpam-modules1.0.1-2Pluggable Authentication Modules f
ii  libpam-runtime1.0.1-2Runtime support for the PAM librar
ii  libpam0g  1.0.1-2Pluggable Authentication Modules l

login recommends no packages.

login suggests no packages.

-- no debconf information



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

Bug#495828: FTBFS: missing armel arch

[Barak A. Pearlmutter]

Well, this also assumes the relevant hardware RAID system is around;
it can be on a motherboard or a PCI card.  I'm not sure if s390
qualifies in that regard.

Is there a definitive chart of Debian architectures anywhere?  I took
my list from /usr/share/doc/debian-policy/policy.txt.gz.

What I'd really like to say is

  Architecture: anything-32-bit amd64

but Debian seems to have wedged itself into a zero-abstraction kind of
situation with some debian/control fields, this primary among them.

Anyway, will add Architecture: armel s390 hppa sh3 sh4 and re-upload,
unless you have a better suggestion.

--Barak.
--
Barak A. Pearlmutter
 Hamilton Institute, NUI Maynooth, Co. Kildare, Ireland
 http://www.bcl.hamilton.ie/~barak/



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

Bug#494239: marked as done (ogmtools: FTBFS: Nonexistent build-dependency: libdvdread3-dev)

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 22:01:37 +0300
with message-id <[EMAIL PROTECTED]>
and subject line closed already
has caused the Debian Bug report #494239,
regarding ogmtools: FTBFS: Nonexistent build-dependency: libdvdread3-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
494239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494239
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: ogmtools
Version: 1:1.5-2.1
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080807 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on
i386.

Relevant part:
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>> 3.0.0), automake1.7, libvorbis-dev (>= 1.0.0-2), 
> libvorbis0a, libdvdread3-dev, libogg0, dpatch
> Checking for already installed source dependencies...
> W: Unable to locate package libdvdread3-dev
> debhelper: missing
> Using default version 7.0.16
> automake1.7: missing
> libvorbis-dev: missing
> Using default version 1.2.0.dfsg-3.1
> libvorbis0a: missing
> libdvdread3-dev: missing
> libogg0: missing
> dpatch: missing
> Checking for source dependency conflicts...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> E: Couldn't find package libdvdread3-dev

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/08/07

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
fixed in 1:1.5-3 upload

-- 
"rm -rf" only sounds scary if you don't have backups

--- End Message ---

Bug#495806: [Secure-testing-team] Bug#495806: Locked screen accepts any password to unlock

[Julien Cristau]

On Wed, Aug 20, 2008 at 20:03:47 +0200, Nico Golde wrote:

> [EMAIL PROTECTED]:/tmp$] cp /usr/share/doc/libpam0g-dev/examples/check_user.c 
> .
> [EMAIL PROTECTED]:/tmp$] gcc -lpam -lpam_misc check_user.c -o check_user
> [EMAIL PROTECTED]:/tmp$] ./check_user nion; date; tail -1 /var/log/kern.log
> Authenticated
> Mi 20. Aug 20:01:40 CEST 2008
> Aug 20 20:01:40 coredump kernel: [1073387.605090] check_user[20665]: segfault 
> at 0 ip 7f9a2ebf40f9 sp 7fff37983980 error 4 in pam_unix.so[7f9a2ebea000+c000]
> 
> The segfault happens on the pam_authenticate call as far as I can see.
> 
> Reassigning to pam...
> 
(gdb) set follow-fork-mode child 
(gdb) r julien
Starting program: /tmp/check_user julien

Program received signal SIGSEGV, Segmentation fault.
[Switching to process 11347]
0xb7d8cec6 in _pammodutil_tty_secure (pamh=0x924b008, uttyname=0x0)
at tty_secure.c:42
42  if (strncmp(TTY_PREFIX, uttyname, sizeof(TTY_PREFIX)-1)
== 0)

_pammodutil_tty_secure doesn't like a NULL uttyname.

Cheers,
Julien



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

Processed: reassign 495806 to pam

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.35
> reassign 495806 pam
Bug#495806: Locked screen accepts any password to unlock
Bug reassigned from package `screen' to `pam'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Processed: retitle 495806 to segfault in pam_unix.so on pam_authenticate call

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.35
> retitle 495806 segfault in pam_unix.so on pam_authenticate call
Bug#495806: Locked screen accepts any password to unlock
Changed Bug title to `segfault in pam_unix.so on pam_authenticate call' from 
`Locked screen accepts any password to unlock'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495694: openoffice.org-writer2latex: uninstallable

[Rene Engelhard]

Hi,

Benoît Dejean wrote:
> > And why do you think this is a writer2latex problem and not a
> > problem in whatever JVM you use?
> > Which one did you use (set it Tools-Options in OOo).
> 
> I haven't set anything. I used to have gcj but switched to cacao because

But what is set in OOos options? Please look.

> gcj was broken/incomplete and hasn't work with OOo on ppc for some time
> (but used to work #478760). So now i've switched to another vm as you
> asked me, you're telling me that i should get back to gij ?

I am just trying to find out whether the problem is in caco-oj6-jre (which I
do belive - OOo never supported cacao as JVM)

> Then i reinstalled writer2latex, and got this:
> 
> Dépaquetage de openoffice.org-writer2latex (à partir
> de .../openoffice.org-writer2latex_0.5-8_all.deb) ...
> Paramétrage de openoffice.org-writer2latex (0.5-8) ...
> Adding
> extension /usr/lib/openoffice/share/extension/install/writer2latex.uno.pkg...
> unopkg failed.
>  done.
> 
> Is this OK ?

Well, the registration of the extension failed, probably because it didn't
get properly deregistered in your purge/removal attempt.

Try the following:

dpkg -P openoffice.org-writer2latex
/usr/lib/openoffice/program/unopkg remove --shared 
org.openoffice.legacy.writer2latex.uno.pkg

Then try to install it again.

Regards,

Rene



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

Bug#495828: FTBFS: missing armel arch

[Riku Voipio]

Package: raidutils
Version: 0.0.6-7
Severity: serious

the  armel build log:

raidutils_0.0.6-7.dsc: armel not in arch list: i386 amd64 arm armeb m32r m68k 
mips mipsel powerpc sparc

the changelog:

* target only on 32-bit architectures

armel is 32bit...

Also, s390,hppa and the unofficial sh3 and sh4 ports are missing at least.

See http://wiki.debian.org/ArchitectureSpecificsMemo for some 32/64bit
info (size of data pointer, I presume).

On Wed, Aug 20, 2008 at 05:57:33PM +0300, Build Daemon wrote:
> Automatic build of raidutils_0.0.6-7 on ALL6500 by sbuild/armel 0.56
> Build started at 20080820-1757
> **
> Failed to open ./raidutils_0.0.6-7.dsc
> Checking available source versions...
> Fetching source files...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Need to get 1487kB of source archives.
> Get:1 http://incoming.debian.org  raidutils 0.0.6-7 (dsc) [1158B]
> Get:2 http://incoming.debian.org  raidutils 0.0.6-7 (tar) [1386kB]
> Get:3 http://incoming.debian.org  raidutils 0.0.6-7 (diff) [100.0kB]
> Fetched 1487kB in 1s (764kB/s)
> Download complete and in download only mode
> raidutils_0.0.6-7.dsc: armel not in arch list: i386 amd64 arm armeb m32r m68k 
> mips mipsel powerpc sparc -- skipping
> ******
> Finished at 20080820-1757
> Build needed 00:25:29, 16148k disk space



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

Bug#495501: midori: Segfault on some web pages

[Steve Cotton]

> Thread 2 (Thread 0x41e52950 (LWP 28933)):
> #0  0x in ?? ()  
> #1  0x7f89eebe6646 in open_read_async_thread (res=0x80db60, 
> object=0x932950, cancellable=0x0)
> at /build/buildd/glib2.0-2.16.4/gio/gfile.c:4015  
>

One of the diffs between glib2.0-2.16.4-2 and glib2.0-2.16.5-1 is
a null-pointer check in open_read_async_thread that catches this.

With the new glib, midori seems to work, except for this
diagnostic output to the console:

(midori:7962): GLib-GIO-CRITICAL **: g_simple_async_result_set_from_error: 
assertion `error != NULL' failed

(midori:7962): GLib-CRITICAL **: g_error_free: assertion `error != NULL' failed

(midori:7962): GLib-GIO-CRITICAL **: g_simple_async_result_set_from_error: 
assertion `error != NULL' failed

(midori:7962): GLib-CRITICAL **: g_error_free: assertion `error != NULL' failed

(midori:7962): GLib-GIO-WARNING **: 
(/build/buildd/glib2.0-2.16.5/gio/gfileicon.c:256):g_file_icon_load_finish: 
runtime check failed: (g_simple_async_result_get_source_tag (simple) == 
g_file_icon_load_async)

Steve



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

Bug#495806: [Secure-testing-team] Bug#495806: Locked screen accepts any password to unlock

[Nico Golde]

reassign 495806 pam
retitle segfault in pam_unix.so on pam_authenticate call
thanks

Hi Steve,
* Steve Langasek <[EMAIL PROTECTED]> [2008-08-20 19:53]:
> On Wed, Aug 20, 2008 at 10:13:25AM -0500, Troy Davis wrote:
[...] 
> > Screen has started accepting any password at all at the locked screen prompt
> > on my testing box.  I do not know when exactly this behavior started; I just
> > noticed it today.  A different box running etch works as expected, i.e. only
> > unlocking when the user's system password is entered.
> 
> > I have tested this with multiple users on the lenny box.  Searching the
> > Debian screen bug reports and the screen-users mailing list turns up
> > nothing.  The only thing I can guess right now is that it might have
> > something to do with new pam packages in testing.  User error is always a
> > possibility, too.  ;-)
> 
> I've had a look to see if this is reproducible here, and it is.  Poking
> around in the logs, I see:
> 
>   Aug 20 10:13:51 borges kernel: [336995.492721] screen[16067]: segfault at 0 
> ip 7f69c4ff90fa sp 7fffcfcbcc50 error 4 in pam_unix.so[7f69c4fef000+c000]
> 
> So it looks like the auth process is segfaulting, resulting in the unlocking
> of the screen.
> 
> Will continue investigating.

It looks like a pam problem. I couldn't reproduce this with 
pam 0.99.7.1-7 but can with 1.0.1-2.
From screen (attacher.c):

875 #ifdef USE_PAM
876   PAM_conversation.appdata_ptr = cp1;
877   pam_error = pam_start("screen", ppp->pw_name, &PAM_conversation, 
&pamh);
878   if (pam_error != PAM_SUCCESS)
879 AttacherFinit(SIGARG);  /* goodbye */
880   pam_error = pam_authenticate(pamh, 0);
881   pam_end(pamh, pam_error);
882   PAM_conversation.appdata_ptr = 0;
883   if (pam_error == PAM_SUCCESS)
884 break;
885 #else

This is done in a loop to check the password.
A similar piece of code exists in 
/usr/share/doc/libpam0g-dev/examples/check_user.c.

[EMAIL PROTECTED]:/tmp$] cp /usr/share/doc/libpam0g-dev/examples/check_user.c .
[EMAIL PROTECTED]:/tmp$] gcc -lpam -lpam_misc check_user.c -o check_user
[EMAIL PROTECTED]:/tmp$] ./check_user nion; date; tail -1 /var/log/kern.log
Authenticated
Mi 20. Aug 20:01:40 CEST 2008
Aug 20 20:01:40 coredump kernel: [1073387.605090] check_user[20665]: segfault 
at 0 ip 7f9a2ebf40f9 sp 7fff37983980 error 4 in pam_unix.so[7f9a2ebea000+c000]

The segfault happens on the pam_authenticate call as far as I can see.

Reassigning to pam...

HTH,
Nico

-- 
Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.


pgpTSPB52zqVW.pgp
Description: PGP signature

Bug#495694: openoffice.org-writer2latex: uninstallable

[Benoît Dejean]

Le mardi 19 août 2008 à 21:21 +0200, Rene Engelhard a écrit :
> tag 495694 + unreproducible
> tag 495694 + moreinfo
> thanks
> 
> Benoît Dejean wrote:
> > LC_ALL=C sudo dpkg -i 
> > /var/cache/apt/archives/openoffice.org-writer2latex_0.5-8_all.deb 
> > (Reading database ... 239783 files and directories currently installed.)
> > Preparing to replace openoffice.org-writer2latex 0.5-6 (using 
> > .../openoffice.org-writer2latex_0.5-8_all.deb) ...
> > Removing extension org.openoffice.legacy.writer2latex.uno.pkg...LOG: 
> > [0x48103d40] exception thrown while VM is initializing: 
> > LOG: [0x48103d40] NULL: java.lang.Object
> > LOG: [0x48103d40] Aborting...
> 
> And why do you think this is a writer2latex problem and not a
> problem in whatever JVM you use?
> Which one did you use (set it Tools-Options in OOo).

I haven't set anything. I used to have gcj but switched to cacao because
gcj was broken/incomplete and hasn't work with OOo on ppc for some time
(but used to work #478760). So now i've switched to another vm as you
asked me, you're telling me that i should get back to gij ?

> Works for me with java-gcj-compat (thus gij).
> 
> > Versions of packages openoffice.org-writer2latex depends on:
> > ii  openoffice.org-core   1:2.4.0-6  OpenOffice.org office suite 
> > archit
> > pn  openoffice.org-java-common (no description available)
> 
> And htf do you get to this state?

apt-get upgrade
as writer2latex would not install, i've purged it, run again my upgrade
and now i have:

ii  openoffice.org-java-common1:2.4.1-6

> Package: openoffice.org-writer2latex
> Priority: optional
> Section: text
> Installed-Size: 456
> Maintainer: Debian OpenOffice Team <[EMAIL PROTECTED]>
> Architecture: all
> Source: writer2latex
> Version: 0.5-8
> Depends: openoffice.org-core (>= 1:2.3.0~oog680m1), 
> openoffice.org-java-common (>= 1:2.3.0~oog680m1)
> [...]
> 
> I can't help me but I guess either your system is broken or it is 
> a JVM Problem.

Then i reinstalled writer2latex, and got this:

Dépaquetage de openoffice.org-writer2latex (à partir
de .../openoffice.org-writer2latex_0.5-8_all.deb) ...
Paramétrage de openoffice.org-writer2latex (0.5-8) ...
Adding
extension /usr/lib/openoffice/share/extension/install/writer2latex.uno.pkg...
unopkg failed.
 done.

Is this OK ?

Thanks.
-- 
Benoît Dejean
GNOME http://www.gnomefr.org/
LibGTop http://directory.fsf.org/libgtop.html


signature.asc
Description: Ceci est une partie de message	numériquement signée

Bug#495806: [Secure-testing-team] Bug#495806: Locked screen accepts any password to unlock

[Steve Langasek]

On Wed, Aug 20, 2008 at 10:13:25AM -0500, Troy Davis wrote:
> Package: screen
> Version: 4.0.3-11
> Severity: grave
> Tags: security
> Justification: user security hole

> Screen has started accepting any password at all at the locked screen prompt
> on my testing box.  I do not know when exactly this behavior started; I just
> noticed it today.  A different box running etch works as expected, i.e. only
> unlocking when the user's system password is entered.

> I have tested this with multiple users on the lenny box.  Searching the
> Debian screen bug reports and the screen-users mailing list turns up
> nothing.  The only thing I can guess right now is that it might have
> something to do with new pam packages in testing.  User error is always a
> possibility, too.  ;-)

I've had a look to see if this is reproducible here, and it is.  Poking
around in the logs, I see:

  Aug 20 10:13:51 borges kernel: [336995.492721] screen[16067]: segfault at 0 
ip 7f69c4ff90fa sp 7fffcfcbcc50 error 4 in pam_unix.so[7f69c4fef000+c000]

So it looks like the auth process is segfaulting, resulting in the unlocking
of the screen.

Will continue investigating.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]



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

Bug#495122: CVE ids for drupal

[Nico Golde]

Hi,
here are the CVE ids that were assigned to this issue for 
future reference.

> http://drupal.org/node/295053

Use the following, to be filled in later:

CVE-2008-3740 - first XSS

CVE-2008-3741 - second XSS.  This has a different root cause so is SPLIT.

CVE-2008-3742 - BlogAPI file uploads

CVE-2008-3743 - first CSRF, for 6.x only

CVE-2008-3744 - second CSRF, for 6.x/5.x (different affected versions so
SPLIT)

CVE-2008-3745 - Upload module priv escalation


Cheers
Nico
-- 
Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.


pgpCvcQdTVyGd.pgp
Description: PGP signature

Processed: Re: Bug#495792: cdrom: Disk partioner hangs at 52% when manual disk partion option selected

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 495792 installation-reports
Bug#495792: cdrom: Disk partioner hangs at 52% when manual disk partion option 
selected
Bug reassigned from package `cdrom' to `installation-reports'.

> severity 495792 important
Bug#495792: cdrom: Disk partioner hangs at 52% when manual disk partion option 
selected
Severity set to `important' from `grave'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495792: cdrom: Disk partioner hangs at 52% when manual disk partion option selected

[Frans Pop]

reassign 495792 installation-reports
severity 495792 important
thanks

Reassigning to debian-installer team.

On Wednesday 20 August 2008, Stuart Scharf wrote:
> I was trying to install a new lenny system over an existing old-stable
> system
>
> The computer has two disk drives used for a Raid1 configuration
> MD0 is a small boot partition
> MD1 is a LVM with four partitions (/ /home /var /chroot)
>
> I tried both lenny beta-2 disk and the weekly snapshot. (The beta-2
> wouldn't boot on my machine so I went to the snapshot disk)
>
> When I selected the manual partition option, the partitioner would hang
> at 52% and not present the partition map of the system. Pressing 'F4'
> showed a detail screen that had both the raid and LVM partitions
> recognized.
>
> The Stable install disk worked fine.



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

Bug#481762: Confirmed

[Daniel R.]

Hello, 

I confirm that installing gvfs-backends solves the problem.

Thanks




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

Bug#495806: Locked screen accepts any password to unlock

[Troy Davis]

On Wed, Aug 20, 2008 at 05:26:27PM +0200, Jan Christoph Nordholz wrote:
> You are referring to the password prompt that screen shows upon resumption 
> of a screen session that has been locked with the 'lockscreen' command, 
> right?

I press ^A-x and see:

---snip---
Screen used by Troy Davis .
Password:
---snip---

That prompt accepts anything I give it and unlocks the screen.

> tell me if you made any substantial changes to relevant files 
> (/etc/pam.d/*, any personal or system-wide screenrc settings etc.)?

I have not manually edited anything in /etc/pam.d/.

I have not manually edited /etc/screenrc, so this md5sum sum should match 
what comes in the package by default:

12c245238eb8b653625bba27dc81df6a  /etc/screenrc

My .screenrc is nothing special:

---snip---
startup_message off
hardstatus alwayslastline "%{.bW}%-w%{.rW}%n %t%{-}%+w %=%{..G} %H %C%a "
shelltitle '> |-'
termcapinfo xterm ti@:te@
vbell off
---snip---

I have also reinstalled the screen package.  No change.

I have verified that e.g. sshd actually requires a correct password, so I 
don't believe I have been hax0r3d.  ;-)

-- 
Troy



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

Bug#495810: installation-reports: fails to mount installer CD-rom

[Jérémy Bobbio]

severity 495810 normal
thanks

This is not a critical bug, it did not break anyone's system.

On Wed, Aug 20, 2008 at 05:35:39PM +0200, Paul Sundvall wrote:
> Image version:
> http://cdimage.debian.org/debian-cd/4.0_r4a/amd64/iso-cd/debian-40r4a-amd64-CD-1.iso

This image is using the Etch debian-installer and thus uses kernel
2.6.18.

> Everything (boot, language etc) went fine until the cd rom was to be
> detected. It would not be recognized, and impossible to continue.

The controller on which your CD-ROM reader is connected is not supported
in Linux 2.6.18, that why this installation step fails.

You should be able to use the Etch-n-half installer to do an Etch
installation.

Cheers,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Processed: Re: Bug#495810: installation-reports: fails to mount installer CD-rom

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 495810 normal
Bug#495810: installation-reports: fails to mount installer CD-rom
Severity set to `normal' from `critical'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#494212: marked as done (dbus-java: FTBFS: ! LaTeX Error: File `kvoptions.sty' not found.)

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 16:02:06 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#494212: fixed in dbus-java 2.5-4
has caused the Debian Bug report #494212,
regarding dbus-java: FTBFS: ! LaTeX Error: File `kvoptions.sty' not found.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
494212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494212
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: dbus-java
Version: 2.5-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080807 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on
i386.

Relevant part:
> make[1]: Entering directory 
> `/build/user-dbus-java_2.5-3-amd64-jFHBE7/dbus-java-2.5-3'
> echo "#java-format" > translations/en_GB.po
> sed -n '/_(/s/.*_("\([^"]*\)").*/\1/p' org/freedesktop/DBus.java 
> org/freedesktop/dbus/AbstractConnection.java 
> org/freedesktop/dbus/ArrayFrob.java org/freedesktop/dbus/BusAddress.java 
> org/freedesktop/dbus/CallbackHandler.java org/freedesktop/dbus/Container.java 
> org/freedesktop/dbus/DBusAsyncReply.java 
> org/freedesktop/dbus/DBusCallInfo.java 
> org/freedesktop/dbus/DBusConnection.java 
> org/freedesktop/dbus/DBusInterface.java 
> org/freedesktop/dbus/DBusInterfaceName.java org/freedesktop/dbus/DBusMap.java 
> org/freedesktop/dbus/DBusMatchRule.java 
> org/freedesktop/dbus/DBusMemberName.java 
> org/freedesktop/dbus/DBusSerializable.java 
> org/freedesktop/dbus/DBusSigHandler.java org/freedesktop/dbus/DBusSignal.java 
> org/freedesktop/dbus/DirectConnection.java 
> org/freedesktop/dbus/EfficientMap.java 
> org/freedesktop/dbus/EfficientQueue.java org/freedesktop/dbus/Error.java 
> org/freedesktop/dbus/ExportedObject.java org/freedesktop/dbus/Gettext.java 
> org/freedesktop/dbus/InternalSignal.java 
> org/freedesktop/dbus/Marshalling.java org/freedesktop/dbus/Message.java 
> org/freedesktop/dbus/MessageReader.java 
> org/freedesktop/dbus/MessageWriter.java org/freedesktop/dbus/MethodCall.java 
> org/freedesktop/dbus/MethodReturn.java org/freedesktop/dbus/MethodTuple.java 
> org/freedesktop/dbus/ObjectPath.java org/freedesktop/dbus/ObjectTree.java 
> org/freedesktop/dbus/Path.java org/freedesktop/dbus/Position.java 
> org/freedesktop/dbus/RemoteInvocationHandler.java 
> org/freedesktop/dbus/RemoteObject.java org/freedesktop/dbus/SignalTuple.java 
> org/freedesktop/dbus/StrongReference.java org/freedesktop/dbus/Struct.java 
> org/freedesktop/dbus/Transport.java org/freedesktop/dbus/Tuple.java 
> org/freedesktop/dbus/TypeSignature.java org/freedesktop/dbus/UInt16.java 
> org/freedesktop/dbus/UInt32.java org/freedesktop/dbus/UInt64.java 
> org/freedesktop/dbus/Variant.java 
> org/freedesktop/dbus/exceptions/DBusException.java 
> org/freedesktop/dbus/exceptions/DBusExecutionException.java 
> org/freedesktop/dbus/exceptions/FatalDBusException.java 
> org/freedesktop/dbus/exceptions/FatalException.java 
> org/freedesktop/dbus/exceptions/InternalMessageException.java 
> org/freedesktop/dbus/exceptions/MarshallingException.java 
> org/freedesktop/dbus/exceptions/MessageFormatException.java 
> org/freedesktop/dbus/exceptions/MessageProtocolVersionException.java 
> org/freedesktop/dbus/exceptions/MessageTypeException.java 
> org/freedesktop/dbus/exceptions/NonFatalException.java 
> org/freedesktop/dbus/exceptions/NotConnected.java 
> org/freedesktop/dbus/exceptions/UnknownTypeCodeException.java 
> org/freedesktop/dbus/types/DBusListType.java 
> org/freedesktop/dbus/types/DBusMapType.java 
> org/freedesktop/dbus/types/DBusStructType.java 
> org/freedesktop/dbus/bin/Caller.java 
> org/freedesktop/dbus/bin/CreateInterface.java 
> org/freedesktop/dbus/bin/DBusDaemon.java 
> org/freedesktop/dbus/bin/IdentifierMangler.java 
> org/freedesktop/dbus/bin/IterableNodeList.java 
> org/freedesktop/dbus/bin/ListDBus.java 
> org/freedesktop/dbus/bin/NodeListIterator.java 
> org/freedesktop/dbus/bin/StructStruct.java 
> org/freedesktop/dbus/viewer/DBusEntry.java 
> org/freedesktop/dbus/viewer/DBusTableModel.java 
> org/freedesktop/dbus/viewer/DBusViewer.java 
> org/freedesktop/dbus/viewer/FileSaver.java 
> org/freedesktop/dbus/viewer/IntrospectAction.java 
> org/freedesktop/dbus/viewer/SaveAllAction.java 
> org/freedesktop/dbus/viewer/SaveFileAction.java 
> org/freedesktop/dbus/viewer/StringStreamFactory.java 
> org/freedesktop/dbus/viewer/TabbedSaveAction.java 
> org/freedesktop/dbus/viewer/TextFile.java | sort -u | sed 's/\(.*\)/msgid 
> "\1"\nmsgstr "\1"/' >> translations/en_GB.po
> mkdir -p classes
> /usr/lib/jvm/java-6

Processed: Re: Bug#495222: In fact, printing is totally non-functional

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> forwarded 495222 http://bugzilla.gnome.org/show_bug.cgi?id=541168
Bug#495222: epiphany-browser: printing is broken
Noted your statement that Bug has been forwarded to 
http://bugzilla.gnome.org/show_bug.cgi?id=541168.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495222: In fact, printing is totally non-functional

[Sven Arvidsson]

forwarded 495222 http://bugzilla.gnome.org/show_bug.cgi?id=541168
thanks

On Wed, 2008-08-20 at 17:16 +0200, Philipp Sadleder wrote:
> I can confirm that printing works if care is taken to scale to 100,0 %

The fix for this is very simple, 
http://svn.gnome.org/viewvc/epiphany/branches/gnome-2-22/embed/mozilla/GeckoPrintService.cpp?r1=8330&r2=8329&pathrev=8330

I will add it to pkg-gnome svn when I have more time, or someone might
beat me to it...

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22


signature.asc
Description: This is a digitally signed message part

Bug#494622: marked as done (emdebian-rootfs: two suite scripts force installation of conflicting packages)

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 15:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#494622: fixed in emdebian-tools 1.4.3
has caused the Debian Bug report #494622,
regarding emdebian-rootfs: two suite scripts force installation of conflicting 
packages
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
494622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494622
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: emdebian-rootfs
Version: 1.4.1
Severity: serious
Justification: Policy 7.4

emdebian-rootfs includes multiple suite scripts for root filesystem
generation using debootstrap --foreign and two of these suite scripts
(the two related to the smallest installations) have not been updated to
reflect changes in the dependencies in the Emdebian packages.
Specifically, the suite scripts force the installation of two packages
that Conflict, leaving an installed system that cannot be easily
upgraded or fixed.

The conflict relates specifically to update-rc.d which is a perl script
in sysv-rc (and therefore cannot run in Emdebian). To prevent the perl
version overwriting the existing emdebian-rootfs support, busybox
conflicts with sysv-rc in Emdebian.


Building dependency tree... Done
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
  busybox: Conflicts: sysv-rc but 2.86.ds1-60em1.1 is to be installed
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or
  specify a solution).

Removing sysv-rc removes the update-rc.d workaround (the reason for the
conflict in the first place), leaving a system that cannot be upgraded:

dpkg: `update-rc.d' not found on PATH.
dpkg: 1 expected program(s) not found on PATH.
NB: root's PATH should usually contain /usr/local/sbin, /usr/sbin and
/sbin.
E: Sub-process /usr/bin/dpkg returned an error code (2)

A shell replacement for update-rc.d has been designed during DebConf
(with assistance from Phil Hands) and is currently being tested.

However, the problem of forcing the installation of packages that were
subsequently uploaded with a Conflicts: field in debian/control needs to
be fixed for Lenny.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages emdebian-rootfs depends on:
ii  apt 0.7.14+b1Advanced front-end for dpkg
ii  apt-cross   0.12.0   retrieve, build and install librar
ii  binutils-multiarch  2.18.1~cvs20080103-7 Binary utilities that support mult
ii  debconf [debconf-2. 1.5.23   Debian configuration management sy
ii  debootstrap 1.0.10   Bootstrap a basic Debian system
ii  devscripts  2.10.35  scripts to make the life of a Debi
ii  dpkg-cross  2.3.0tools for cross compiling Debian p
ii  edos-debcheck   1.0-6+b2 Checks whether dependencies of deb
ii  emdebian-archive-ke 1.4.3GnuPG archive keys for the emdebia
ii  libemdebian-tools-p 1.4.3emdebian support library
ii  pbuilder0.181personal package builder for Debia
ii  perl5.10.0-13Larry Wall's Practical Extraction 
ii  sudo1.6.9p17-1   Provide limited super user privile
ii  ucf 3.007Update Configuration File: preserv

emdebian-rootfs recommends no packages.

Versions of packages emdebian-rootfs suggests:
ii  deb-gview0.2.2   GNOME viewer for .deb package file
ii  debian-xcontrol  0.0.2~pre1+nmu2 Extended syntax for debian/control
ii  minicom  2.3-1   friendly menu driven serial commun
ii  screen   4.0.3-11terminal multiplexor with VT100/AN

-- debconf information:
* emsource/targetsuite: unstable
* emsource/workdir: /opt/emdebian


--- End Message ---
--- Begin Message ---
Source: emdebian-tools
Source-Version: 1.4.3

We believe that the bug you reported is fixed in the latest version of
emdebian-tools, which is due to be installed in the Debian FTP archive:

emdebian-archive-keyring_1.4.3_all.deb
  to pool/main/e/emdebian-tools/emdebian-archive-keyring_1.4.3_all.deb
emdebian-rootfs_1.4.3_all.deb
  to pool/main/e/emdebian-tools/emdebian-rootfs_1.4.3_all.deb
e

Bug#495810: installation-reports: fails to mount installer CD-rom

[Paul Sundvall]

Package: installation-reports
Severity: critical
Justification: breaks the whole system



-- Package-specific info:

Boot method: CD
Image version:
http://cdimage.debian.org/debian-cd/4.0_r4a/amd64/iso-cd/debian-40r4a-amd64-CD-1.iso
Date: ons aug 20 17:29:26 CEST 2008

Machine: stationary PC, Intel Q6600
Partitions: I guess that is not relevant here?


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ O]
Detect network card:[ O]
Configure network:  [ O]
Detect CD:  [ E]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Everything (boot, language etc) went fine until the cd rom was to be
detected. It would not be recognized, and impossible to continue.

The rest of this report is made on a working install (lenny) made
earlier. The hardware report should be relevant.


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to [EMAIL PROTECTED]

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="lenny (installer build 20071018-22:54)"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
umame -a: Linux quadricepsjr 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59
UTC 2007 x86_64 unknown
lspci -nn: 00:00.0 Host bridge [0600]: Intel Corporation Unknown device
[8086:29c0] (rev 02)
lspci -nn: 00:01.0 PCI bridge [0604]: Intel Corporation Unknown device
[8086:29c1] (rev 02)
lspci -nn: 00:1a.0 USB Controller [0c03]: Intel Corporation Unknown
device [8086:2937] (rev 02)
lspci -nn: 00:1a.1 USB Controller [0c03]: Intel Corporation Unknown
device [8086:2938] (rev 02)
lspci -nn: 00:1a.2 USB Controller [0c03]: Intel Corporation Unknown
device [8086:2939] (rev 02)
lspci -nn: 00:1a.7 USB Controller [0c03]: Intel Corporation Unknown
device [8086:293c] (rev 02)
lspci -nn: 00:1b.0 Audio device [0403]: Intel Corporation Unknown device
[8086:293e] (rev 02)
lspci -nn: 00:1c.0 PCI bridge [0604]: Intel Corporation Unknown device
[8086:2940] (rev 02)
lspci -nn: 00:1c.3 PCI bridge [0604]: Intel Corporation Unknown device
[8086:2946] (rev 02)
lspci -nn: 00:1c.4 PCI bridge [0604]: Intel Corporation Unknown device
[8086:2948] (rev 02)
lspci -nn: 00:1d.0 USB Controller [0c03]: Intel Corporation Unknown
device [8086:2934] (rev 02)
lspci -nn: 00:1d.1 USB Controller [0c03]: Intel Corporation Unknown
device [8086:2935] (rev 02)
lspci -nn: 00:1d.2 USB Controller [0c03]: Intel Corporation Unknown
device [8086:2936] (rev 02)
lspci -nn: 00:1d.7 USB Controller [0c03]: Intel Corporation Unknown
device [8086:293a] (rev 02)
lspci -nn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
[8086:244e] (rev 92)
lspci -nn: 00:1f.0 ISA bridge [0601]: Intel Corporation Unknown device
[8086:2918] (rev 02)
lspci -nn: 00:1f.2 IDE interface [0101]: Intel Corporation Unknown
device [8086:2921] (rev 02)
lspci -nn: 00:1f.3 SMBus [0c05]: Intel Corporation Unknown device
[8086:2930] (rev 02)
lspci -nn: 00:1f.5 IDE interface [0101]: Intel Corporation Unknown
device [8086:2926] (rev 02)
lspci -nn: 01:00.0 VGA compatible controller [0300]: ATI Technologies
Inc Unknown device [1002:94c3]
lspci -nn: 01:00.1 Audio device [0403]: ATI Technologies Inc Unknown
device [1002:aa10]
lspci -nn: 03:00.0 SATA controller [0106]: JMicron Technologies, Inc.
JMicron 20360/20363 AHCI Controller [197b:2363] (rev 02)
lspci -nn: 03:00.1 IDE interface [0101]: JMicron Technologies, Inc.
JMicron 20360/20363 AHCI Controller [197b:2363] (rev 02)
lspci -nn: 04:00.0 Ethernet controller [0200]: Realtek Semiconductor
Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
[10ec:8168] (rev 01)
lspci -vnn: 00:00.0 Host bridge [0600]: Intel Corporation Unknown device
[8086:29c0] (rev 02)
lspci -vnn: Subsystem: Giga-byte Technology Unknown device [1458:5000]
lspci -vnn: Flags: bus master, fast devsel, latency 0
lspci -vnn: Capabilities: [e0] Vendor Specific Information
lspci -vnn:
lspci -vnn: 00:01.0 PCI bridge [0604]: Intel Corporation Unknown device
[8086:29c1] (rev 02)
lspci -vnn: Flags: bus master, fast devsel, latency 0
lspci -vnn: Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
lspci -vnn: I/O behind bridge: b000-bfff
lspci -vnn: Memory behind bridge: f400-f5ff
lspci -vnn: Prefetchable memory behind bridge:
e000-efff
lspci -vnn: Capabilities: [88] Subsystem:

Bug#495806: Locked screen accepts any password to unlock

[Jan Christoph Nordholz]

tags 495806 + unreproducible
thankyou

Hi Troy,

I can't reproduce the problem, no matter which PAM version I have installed
(0.99.7 or 1.0.1). You are referring to the password prompt that screen shows
upon resumption of a screen session that has been locked with the 'lockscreen'
command, right?

I can't come up with any good guesses how this could happen to you... just
to make sure that we're talking about the same thing, could you give me a
detailed list of actions to reproduce that behaviour and tell me if you
made any substantial changes to relevant files (/etc/pam.d/*, any personal
or system-wide screenrc settings etc.)?


Regards,

Jan


signature.asc
Description: Digital signature

Bug#495807: [merkaartor] FTBFS on i386, tries to use uic from QT3

[Giovanni Mascellani]

Package: merkaartor
Version: 0.0.11~svn7913-1
Severity: serious

--- Please enter the report below this line. ---

I'd like to build merkaartor, but dpkg-buildpackage fails a few seconds
after having been launched. Here are the relevant lines printed to the
screen:

/usr/share/qt3/bin/uic AboutDialog.ui -o tmp/AboutDialog.h
uic: File generated with too recent version of Qt Designer (4.0 vs. 3.3.8b)
make[1]: *** [tmp/AboutDialog.h] Error 1
make[1]: Leaving directory 
`/home/giovanni/packages/merkaartor/merkaartor-0.0.11~svn7913'
make: *** [build-stamp] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2

I'm not QT expert, but it seems it's trying to build using uic from QT3
instead of uic from QT4. I tried to install qt4-dev-tools (which is not
required by merkaartor dependencies) and even choosing uic-qt4 as the
alternative of uic, but nothing changes. I'm setting the severity as
serious, because the build is not working as expected.

I can provide more information is you need them. :-)

Thank you, Giovanni.

--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.25-1-686

Debian Release: lenny/sid
  500 unstableftp.it.debian.org 
  500 testing ftp.it.debian.org 
  500 stable  ftp.it.debian.org 

--- Package information. ---
Depends  (Version) | Installed
==-+-
libc6   (>= 2.7-1) | 2.7-13
libgcc1(>= 1:4.1.1-21) | 1:4.3.1-8
libqt4-network  (>= 4.4.0) | 4.4.0-4
libqt4-webkit   (>= 4.4.0) | 4.4.0-4
libqt4-xml  (>= 4.4.0) | 4.4.0-4
libqtcore4  (>= 4.4.0) | 4.4.0-4
libqtgui4   (>= 4.4.0) | 4.4.0-4
libstdc++6   (>= 4.1.1-21) | 4.3.1-8
zlib1g(>= 1:1.1.4) | 1:1.2.3.3.dfsg-12


-- 
Giovanni Mascellani <[EMAIL PROTECTED]>
Pisa, Italy

Web: http://giomasce.altervista.org
SIP: [EMAIL PROTECTED]
Jabber: [EMAIL PROTECTED] / [EMAIL PROTECTED]
GPG: 0x5F1FBF70 (FP: 1EB6 3D43 E201 4DDF 67BD  003F FCB0 BB5C 5F1F BF70)


signature.asc
Description: Questa è una parte del messaggio	firmata digitalmente

Bug#495222: In fact, printing is totally non-functional

[Philipp Sadleder]

I can confirm that printing works if care is taken to scale to 100,0 %

-- 
Philipp Sadleder
http://sadleder.de


signature.asc
Description: Digital signature

Bug#495806: Locked screen accepts any password to unlock

[Troy Davis]

Package: screen
Version: 4.0.3-11
Severity: grave
Tags: security
Justification: user security hole

Hello,

Screen has started accepting any password at all at the locked screen prompt
on my testing box.  I do not know when exactly this behavior started; I just
noticed it today.  A different box running etch works as expected, i.e. only
unlocking when the user's system password is entered.

I have tested this with multiple users on the lenny box.  Searching the
Debian screen bug reports and the screen-users mailing list turns up
nothing.  The only thing I can guess right now is that it might have
something to do with new pam packages in testing.  User error is always a
possibility, too.  ;-)

Thank you,
Troy Davis

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages screen depends on:
ii  libc6 2.7-13 GNU C Library: Shared libraries
ii  libncursesw5  5.6+20080713-1 shared libraries for terminal hand
ii  libpam0g  1.0.1-2Pluggable Authentication Modules l

screen recommends no packages.

screen suggests no packages.

-- debconf information:
  screen/old_upgrade_prompt: false



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

Bug#491655: [Pkg-audacious-maintainers] Bug#491655: how about fixing this in a Debian revision / NMU

[William Pitcock]

It is already pending. I'm waiting on things to slow down and intend to
upload a fix by Friday.

On Wed, 2008-08-20 at 15:59 +0200, Thomas Viehmann wrote:
> Hi,
> 
> apparently the bug is still marked as critical in the Debian BTS.  
> Regardless of the severity, it might be worth asking RMs whether to  
> fix this in Lenny now that we happen to have a well-contained fix.
> If the upload itself is a problem, I'd be happy to help out for  
> anything with a short diff to the version in Lenny.
> 
> Kind regards
> 
> T.
> 
> 
> 
> ___
> Pkg-audacious-maintainers mailing list
> [EMAIL PROTECTED]
> http://lists.alioth.debian.org/mailman/listinfo/pkg-audacious-maintainers
> 


signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> clone 481134 -1
Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and 
fails to parse Japanese PDF files.
Bug 481134 cloned as bug 495800.

> reassign 481134 xpdf-japanese
Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and 
fails to parse Japanese PDF files.
Bug reassigned from package `libpoppler3' to `xpdf-japanese'.

> retitle 481134 xpdf-japanese Should register fonts in fontconfig and/or 
> defoma and/or provide poppler specific symlinks
Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and 
fails to parse Japanese PDF files.
Changed Bug title to `xpdf-japanese Should register fonts in fontconfig and/or 
defoma and/or provide poppler specific symlinks' from `libpoppler does not use 
cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.'.

> retitle -1 poppler doesn't support xpdf config anymore
Bug#495800: libpoppler does not use cmap files from xpdf-{japanese,...}, and 
fails to parse Japanese PDF files.
Changed Bug title to `poppler doesn't support xpdf config anymore' from 
`libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to 
parse Japanese PDF files.'.

> severity -1 important
Bug#495800: poppler doesn't support xpdf config anymore
Severity set to `important' from `grave'

> stop
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#481134: libpoppler does not use cmap files from xpdf-{japanese,...}, and fails to parse Japanese PDF files.

[Loïc Minier]

clone 481134 -1
reassign 481134 xpdf-japanese
retitle 481134 xpdf-japanese Should register fonts in fontconfig and/or defoma 
and/or provide poppler specific symlinks
retitle -1 poppler doesn't support xpdf config anymore
severity -1 important
stop

Heya,

 Executive summary: downgrading RC-ness against poppler, the burden of
 the fix is probably on xpdf-japanese to start with.  Request for
 comments/help on fontconfig/defoma topics.

On Wed, May 14, 2008, Junichi Uekawa wrote:
> xpdf-japanese installs CMAP files in
> /usr/share/fonts/cmap/adobe-japan1 etc, but libpoppler looks at
> /usr/share/poppler.
> I need to install the following symlinks in order to use the adobe
> CMAP files.
> $ ls -l  /usr/share/poppler/cidToUnicode/Adobe-Japan1 
> lrwxrwxrwx 1 root root 34 2008-01-18 19:53 Adobe-Japan1 -> 
> /usr/share/fonts/cmap/adobe-japan1
> $ ls -l  /usr/share/poppler/cMap/
> lrwxrwxrwx 1 root root 50 2008-01-18 19:53 
> /usr/share/poppler/cidToUnicode/Adobe-Japan1 -> 
> /usr/share/xpdf/japanese/Adobe-Japan1.cidToUnicode

 (the symlinks are flipped)

 I confirmed that adding similar symlinks allows display of Japanese PDF
 files with evince (poppler).  I don't think adding the symlinks in
 poppler is a good idea.

 What happens here is that xpdf-japanese installs a xpdfrc config file
 snippet which will properly configure unicodeMap and cMapDir with
 various files for xpdf, see /etc/xpdf/xpdfrc-japanese:
#- begin Japanese support package (2004-jul-27)
cidToUnicodeAdobe-Japan1
/usr/share/xpdf/japanese/Adobe-Japan1.cidToUnicode
unicodeMap  ISO-2022-JP 
/usr/share/xpdf/japanese/ISO-2022-JP.unicodeMap
unicodeMap  EUC-JP  /usr/share/xpdf/japanese/EUC-JP.unicodeMap
unicodeMap  Shift-JIS   
/usr/share/xpdf/japanese/Shift-JIS.unicodeMap
cMapDir Adobe-Japan1/usr/share/fonts/cmap/adobe-japan1
toUnicodeDir/usr/share/fonts/cmap/adobe-japan1
...

 poppler probably used to parse xpdf's config as it was forked from
 xpdf.

 Nowadays, poppler has these /usr/share/poppler/cidToUnicode and /cMap
 dirs (along others) to allow for these mappings; these rely on the
 filenames for the mappings to work, so e.g. if poppler needs
 Adobe-Japan1's mapping, it will look for Adobe-Japan1 in there.  The
 actual data for the Adobe-Japan1 font is available in
 /usr/share/fonts/cmap/adobe-japan1 and
 /usr/share/xpdf/japanese/Adobe-Japan1.cidToUnicode, but there isn't any
 place with the data available with the expected file names
 "Adobe-Japan1".

 My understanding is that xpdf-japanese is very xpdf specific; it does
 install some files below /usr/share/fonts/cmap, but I'm not sure this
 is used by anything except xpdf.  It only calls update-xpdfrc in
 postinst.

 As I see it, the modern way of dealing with fonts is to use fontconfig
 which poppler supports, but I'm not sure fontconfig provides support
 for cMap and cidToUnicode information.  A Debian alternative for
 dealing with fonts is to use defoma which allows for package specific
 scripts to be run when fonts are registered/removed via defoma.  Some
 defoma scripts mention cmap, but I saw no cidToUnicode references there
 either.

 So because the data is not currently available in any place I could
 find / think of or isn't in the proper format, I see the following
 solutions to fix this bug:
 a) make poppler parse xpdf's config again; I'm not too hot on this as
it makes poppler leak that it's xpdf based, diverges from upstream,
and isn't a sustainable long-term option; I'm not even sure it's
still possible
 b) make xpdf-japanese register fonts properly in fontconfig; I don't
have enough fontcp,fog foo to understand whether fontconfig can
carry the relevant information/mappings though; help to write a
/etc/fonts/conf.d/*xpdf-japanese*.conf is welcome; it's not clear to
me whether such mappings are reaching too far for fontconfig's goal;
this might also require poppler patching to lookup the relevant
fontconfig data if poppler doesn't use this part of fontconfig, or
if we had new API for this stuff to fontconfig; probably a good
solution for other packages in the same solution as well
 c) make xpdf-japanese register fonts with defoma and make poppler run a
defoma script to generate appropriate symlinks to the cidToUnicode
and cMap files/dirs; I don't have enough defoma foo to understand
whether it's already possible in defoma, but I would expect it is;
this has the benefit of making it easy to handle other packages in
the same case; help welcome to answer the open issues here
 d) make xpdf-japanese generate /usr/share/poppler/{cMap,cidToUnicode}/*
symlinks; probably dead easy, but makes the solution poppler
specific: other fontconfig or defoma using apps wont benefit from
the fonts/mappings; also leaves open the question of integration:
should it be a new poppler-japanese package?  who should be 

Bug#491655: how about fixing this in a Debian revision / NMU

[Thomas Viehmann]

Hi,

apparently the bug is still marked as critical in the Debian BTS.  
Regardless of the severity, it might be worth asking RMs whether to  
fix this in Lenny now that we happen to have a well-contained fix.
If the upload itself is a problem, I'd be happy to help out for  
anything with a short diff to the version in Lenny.


Kind regards

T.



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

Bug#495655: cpufreqd: uses "energy_full" instead of "charge_full" under /sys/...

[Mattia Dongili]

On Wed, Aug 20, 2008 at 09:19:06AM +0200, alberto maurizi wrote:
> Package: cpufreqd
> Followup-For: Bug #495655
> 
> 
> the error message is:
> cpufreqd: get_class_device_attribute: couldn't open 
> /sys/class/power_supply/BAT0/energy_full (No such file or directory)
> [...]
> kernel: [19344.165939] cpufreqd[24816]: segfault at 40 ip b7e04283 sp 
> bfb30770 error 4 in libc-2.7.so[b7d8e000+155000]
> 
> under /sys/class/power_supply/BAT0/ path I can see a "charge_full"
> rather than "energy_full". Maybe some inconsistency in naming
> convention?

well, apparently both of them are acceptable names.
There is already a patch available attached to this bug report
bus.debian.org/495655

I'm going to upload a new version as soon as possible
-- 
mattia
:wq!



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

Bug#495792: cdrom: Disk partioner hangs at 52% when manual disk partion option selected

[Stuart Scharf]

Package: cdrom
Severity: grave
Justification: renders package unusable


I was trying to install a new lenny system over an existing old-stable system

The computer has two disk drives used for a Raid1 configuration
MD0 is a small boot partition
MD1 is a LVM with four partitions (/ /home /var /chroot)

I tried both lenny beta-2 disk and the weekly snapshot. (The beta-2 wouldn't 
boot on my machine so I 
went to the snapshot disk)

When I selected the manual partition option, the partitioner would hang at 52% 
and not
present the partition map of the system. Pressing 'F4' showed a detail screen 
that
had both the raid and LVM partitions recognized.

The Stable install disk worked fine.

(The following is pulled from the machine I am reporting from and not from the 
machine which
reported the problem)
-- System Information: 
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: from install disk
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



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

Bug#495789: milter-greylist has rpath to insecure location (yes/lib)

[Bill Allombert]

Package: milter-greylist
Version: 3.0-3+b1
Severity: serious
Tags: security

Hello Cord,
milter-greylist includes a binary /usr/sbin/milter-greylist with a rpath
pointing to yes/lib.

chrpath /usr/sbin/milter-greylist
/usr/sbin/milter-greylist: RPATH=yes/lib

This allows an attacker with write access to the current working
directory where /usr/sbin/milter-greylist is started to create a
directory yes/lib and add modified libraries which will be loaded when
someone else run milter-greylist.

Cheers,

-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



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

Processed: bug 495395 is not forwarded, reassign 495395 to xulrunner-1.9, forcibly merging 486744 495395

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.26
> notforwarded 495395
Bug#495395: Epiphany segfaults consistently when changing the text size in 
certain websites
Removed annotation that Bug had been forwarded to 
http://bugzilla.gnome.org/show_bug.cgi?id=525364.

> reassign 495395 xulrunner-1.9
Bug#495395: Epiphany segfaults consistently when changing the text size in 
certain websites
Bug reassigned from package `epiphany-browser' to `xulrunner-1.9'.

> forcemerge 486744 495395
Bug#486744: [epiphany-browser] Carsh when increeasing font size
Bug#495395: Epiphany segfaults consistently when changing the text size in 
certain websites
Bug#492928: xulrunner-1.9: Crash when changing text size in Epiphany
Forcibly Merged 486744 492928 495395.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495785: attal has rpath to insecure location (.:/usr/lib/attal)

[Bill Allombert]

Package: attal
Version: 1.0~rc1+cvs20080318-2
Severity: serious
Tags: security

Hello Debian Games Team,
attal includes a binary /usr/games/attal-theme-editor with a rpath
pointing to .:/usr/lib/attal.

chrpath /usr/games/*
/usr/games/attal-ai: RPATH=.:/usr/lib/attal
/usr/games/attal-campaign-editor: RPATH=.:/usr/lib/attal
/usr/games/attal-client: RPATH=.:/usr/lib/attal
/usr/games/attal-scenario-editor: RPATH=.:/usr/lib/attal
/usr/games/attal-server: RPATH=.:/usr/lib/attal
/usr/games/attal-theme-editor: RPATH=.:/usr/lib/attal

This allows an attacker with write access to the current working directory 
where attal is launched to add modified libraries which will be loaded
when someone else run attal.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



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

Bug#495562: btrfs-tools: immature software not fit for stable release

[Daniel Baumann]

severity 495562 normal
thanks

I beg to differ. btrfs is quite usable now adays and the on-disc format
didn't change for the last releases. the description could be improved
to be less 'agressive', though.

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/



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

Processed: Re: btrfs-tools: immature software not fit for stable release

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 495562 normal
Bug#495562: btrfs-tools: immature software not fit for stable release
Severity set to `normal' from `serious'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495184: wodim: Fails, then asks me to use the option I've already given

[Nigel Horne]

Peter Samuelson wrote:

[Nigel Horne]
  

write(1, "\t1000,2,0 12) 'Optiarc ' 'DVD"..., 72  1000,2,0 12) 'Optiarc 
' 'DVD RW AD-5170A ' '1.52' Removable CD-ROM
) = 72
write(1, "\t1000,3,0 13) *\n"..., 20  1000,3,0 13) *
) = 20
write(1, "\t1000,4,0 14) *\n"..., 20  1000,4,0 14) *
) = 20
write(1, "\t1000,5,0 15) *\n"..., 20  1000,5,0 15) *
) = 20
write(1, "\t1000,6,0 16) *\n"..., 20  1000,6,0 16) *
) = 20
write(1, "\t1000,7,0 17) *\n"..., 20  1000,7,0 17) *
) = 20



I thought you said wodim -scanbus didn't work?  Looks to me like it
worked.
  


It doesn't work:

packard:/home/njh# wodim -scanbus
wodim: No such file or directory.
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.
packard:/home/njh#

-Nigel



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

Bug#485793: marked as done (fglrx module doesn't build with 2.6.26 kernel)

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 11:17:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#485793: fixed in fglrx-driver 1:8-7-2
has caused the Debian Bug report #485793,
regarding fglrx module doesn't build with 2.6.26 kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
485793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485793
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: fglrx-source
Version: 1:8-5-1
Severity: grave
Justification: renders package unusable

The module is built successfully, but when loaded dmseg reports

fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, 
GERMANY' taints kernel.
fglrx: Unknown symbol init_mm
 

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fglrx-source depends on:
ii  bzip2 1.0.5-0.1  high-quality block-sorting file co
ii  debhelper 7.0.10 helper programs for debian/rules
ii  make  3.81-5 The GNU version of the "make" util

Versions of packages fglrx-source recommends:
ii  kernel-package11.001-0.1 A utility for building Linux kerne
ii  module-assistant  0.10.11.0  tool to make module package creati

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: fglrx-driver
Source-Version: 1:8-7-2

We believe that the bug you reported is fixed in the latest version of
fglrx-driver, which is due to be installed in the Debian FTP archive:

fglrx-amdcccle_8-7-2_all.deb
  to pool/non-free/f/fglrx-driver/fglrx-amdcccle_8-7-2_all.deb
fglrx-atieventsd_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-atieventsd_8-7-2_amd64.deb
fglrx-control_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-control_8-7-2_amd64.deb
fglrx-driver_8-7-2.diff.gz
  to pool/non-free/f/fglrx-driver/fglrx-driver_8-7-2.diff.gz
fglrx-driver_8-7-2.dsc
  to pool/non-free/f/fglrx-driver/fglrx-driver_8-7-2.dsc
fglrx-driver_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-driver_8-7-2_amd64.deb
fglrx-glx-ia32_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-glx-ia32_8-7-2_amd64.deb
fglrx-glx_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-glx_8-7-2_amd64.deb
fglrx-kernel-src_8-7-2_all.deb
  to pool/non-free/f/fglrx-driver/fglrx-kernel-src_8-7-2_all.deb
fglrx-source_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-source_8-7-2_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Romain Beauxis <[EMAIL PROTECTED]> (supplier of updated fglrx-driver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 25 Jul 2008 09:56:52 +0200
Source: fglrx-driver
Binary: fglrx-driver fglrx-glx fglrx-glx-ia32 fglrx-source fglrx-kernel-src 
fglrx-control fglrx-amdcccle fglrx-atieventsd
Architecture: source amd64 all
Version: 1:8-7-2
Distribution: unstable
Urgency: low
Maintainer: Fglrx packaging team <[EMAIL PROTECTED]>
Changed-By: Romain Beauxis <[EMAIL PROTECTED]>
Description: 
 fglrx-amdcccle - control panel for the non-free AMD/ATI r5xx, r6xx display 
driver
 fglrx-atieventsd - external events daemon for the non-free AMD/ATI r5xx, r6xx 
displa
 fglrx-control - control panel for the non-free AMD/ATI r5xx, r6xx display 
driver
 fglrx-driver - non-free AMD/ATI r5xx, r6xx display driver
 fglrx-glx  - proprietary libGL for the non-free AMD/ATI r5xx, r6xx display dri
 fglrx-glx-ia32 - proprietary libGL for the non-free AMD/ATI r5xx, r6xx display 
dri
 fglrx-kernel-src - kernel module source for the non-free AMD/ATI r5xx, r6xx 
display 
 fglrx-source - kernel module source for the non-free AMD/ATI r5xx, r6xx 
display 
Closes: 485793
Changes: 
 fglrx-driver (1:8-7-2) unstable; urgency=low
 .
   * Fixed compilation with 2.6.26 kernels,
 thanks to Deng Xiyue for reporting and
 preparing the patch. Closes: #485793
   * Removed last kernel-src bits from fg

Bug#493718: marked as done (fglrx-source: FTBFS with 2.6.26-1)

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 11:17:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#485793: fixed in fglrx-driver 1:8-7-2
has caused the Debian Bug report #485793,
regarding fglrx-source: FTBFS with 2.6.26-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
485793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485793
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: fglrx-source
Severity: serious

em8300 fails to build with 2.6.26-1.

---snip---
[...]
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3860:
warning: initialization from incompatible pointer type
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3867:
error: unknown field 'nopage' specified in initializer
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3867:
warning: initialization from incompatible pointer type
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3874:
error: unknown field 'nopage' specified in initializer
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3874:
warning: initialization from incompatible pointer type
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3881:
error: unknown field 'nopage' specified in initializer
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3881:
warning: initialization from incompatible pointer type
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3888:
error: unknown field 'nopage' specified in initializer
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3888:
warning: initialization from incompatible pointer type
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3897:
error: unknown field 'nopage' specified in initializer
/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.c:3897:
warning: initialization from incompatible pointer type
make[4]: ***
[/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx/firegl_public.o]
Error 1
make[3]: ***
[_module_/home/user/linux-modules-nonfree-2.6/debian/build/build_i386_none_486_fglrx]
Error 2
make[3]: Leaving directory `/usr/src/linux-headers-2.6.26-1-486'
make[2]: *** [debian/stamps/build_i386_none_486_fglrx] Error 2
make[2]: Leaving directory `/home/user/linux-modules-nonfree-2.6'
make[1]: *** [build_i386_none_486_fglrx] Error 2
make[1]: Leaving directory `/home/user/linux-modules-nonfree-2.6'
make: *** [debian/stamps/build-base] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
(sid_i386)[EMAIL PROTECTED]:~/linux-modules-nonfree-2.6$
---snap---

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


--- End Message ---
--- Begin Message ---
Source: fglrx-driver
Source-Version: 1:8-7-2

We believe that the bug you reported is fixed in the latest version of
fglrx-driver, which is due to be installed in the Debian FTP archive:

fglrx-amdcccle_8-7-2_all.deb
  to pool/non-free/f/fglrx-driver/fglrx-amdcccle_8-7-2_all.deb
fglrx-atieventsd_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-atieventsd_8-7-2_amd64.deb
fglrx-control_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-control_8-7-2_amd64.deb
fglrx-driver_8-7-2.diff.gz
  to pool/non-free/f/fglrx-driver/fglrx-driver_8-7-2.diff.gz
fglrx-driver_8-7-2.dsc
  to pool/non-free/f/fglrx-driver/fglrx-driver_8-7-2.dsc
fglrx-driver_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-driver_8-7-2_amd64.deb
fglrx-glx-ia32_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-glx-ia32_8-7-2_amd64.deb
fglrx-glx_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-glx_8-7-2_amd64.deb
fglrx-kernel-src_8-7-2_all.deb
  to pool/non-free/f/fglrx-driver/fglrx-kernel-src_8-7-2_all.deb
fglrx-source_8-7-2_amd64.deb
  to pool/non-free/f/fglrx-driver/fglrx-source_8-7-2_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Romain Beauxis <[EMAIL PROTECTED]> (supplie

Bug#495371: marked as done (fglrx-kernel-src: Does not build against 2.6.26)

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 11:17:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#485793: fixed in fglrx-driver 1:8-7-2
has caused the Debian Bug report #485793,
regarding fglrx-kernel-src: Does not build against 2.6.26
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
485793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485793
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: fglrx-kernel-src
Version: 1:8-6-2
Severity: grave
Justification: renders package unusable

Fails to build against 2.6.26, module assistant log:

/usr/bin/make  -f debian/rules clean
make[1]: Entering directory `/usr/src/modules/fglrx'
dh_testroot
rm -f configure-stamp
rm -f fglrx.ko fglrx.mod.c *.o libfglrx_ip.a
rm -f .version .*.o.flags .*.o.d .*.o.cmd .*.ko.cmd
rm -rf .tmp_versions
rm -rf patch
dh_clean
rm /usr/src/modules/fglrx/debian/control
rm /usr/src/modules/fglrx/debian/dirs
make[1]: Leaving directory `/usr/src/modules/fglrx'
/usr/bin/make  -f debian/rules binary_modules
make[1]: Entering directory `/usr/src/modules/fglrx'
if [ -f /usr/src/modules/fglrx/debian/control.template ]; then \
cat /usr/src/modules/fglrx/debian/control.template > 
/usr/src/modules/fglrx/debian/control; \
fi
dh_testdir
touch configure-stamp
dh_testdir
/usr/bin/make -C /lib/modules/2.6.26-1-686/build SUBDIRS=/usr/src/modules/fglrx 
modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
  CC [M]  /usr/src/modules/fglrx/firegl_public.o
/usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_get_ke_pte’:
/usr/src/modules/fglrx/firegl_public.c:2612: error: ‘NOPAGE_SIGBUS’ undeclared 
(first use in this function)
/usr/src/modules/fglrx/firegl_public.c:2612: error: (Each undeclared identifier 
is reported only once
/usr/src/modules/fglrx/firegl_public.c:2612: error: for each function it 
appears in.)
/usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_get_vm_phys_addr’:
/usr/src/modules/fglrx/firegl_public.c:2640: error: ‘NOPAGE_SIGBUS’ undeclared 
(first use in this function)
/usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_get_vm_page_table’:
/usr/src/modules/fglrx/firegl_public.c:2662: error: ‘NOPAGE_SIGBUS’ undeclared 
(first use in this function)
/usr/src/modules/fglrx/firegl_public.c: In function 
‘KCL_TestAndClearPageDirtyFlag’:
/usr/src/modules/fglrx/firegl_public.c:2790: error: ‘NOPAGE_SIGBUS’ undeclared 
(first use in this function)
/usr/src/modules/fglrx/firegl_public.c: At top level:
/usr/src/modules/fglrx/firegl_public.c:3835: error: unknown field ‘nopage’ 
specified in initializer
/usr/src/modules/fglrx/firegl_public.c:3835: warning: initialization from 
incompatible pointer type
/usr/src/modules/fglrx/firegl_public.c:3853: error: unknown field ‘nopage’ 
specified in initializer
/usr/src/modules/fglrx/firegl_public.c:3853: warning: initialization from 
incompatible pointer type
/usr/src/modules/fglrx/firegl_public.c:3860: error: unknown field ‘nopage’ 
specified in initializer
/usr/src/modules/fglrx/firegl_public.c:3860: warning: initialization from 
incompatible pointer type
/usr/src/modules/fglrx/firegl_public.c:3867: error: unknown field ‘nopage’ 
specified in initializer
/usr/src/modules/fglrx/firegl_public.c:3867: warning: initialization from 
incompatible pointer type
/usr/src/modules/fglrx/firegl_public.c:3874: error: unknown field ‘nopage’ 
specified in initializer
/usr/src/modules/fglrx/firegl_public.c:3874: warning: initialization from 
incompatible pointer type
/usr/src/modules/fglrx/firegl_public.c:3881: error: unknown field ‘nopage’ 
specified in initializer
/usr/src/modules/fglrx/firegl_public.c:3881: warning: initialization from 
incompatible pointer type
/usr/src/modules/fglrx/firegl_public.c:3888: error: unknown field ‘nopage’ 
specified in initializer
/usr/src/modules/fglrx/firegl_public.c:3888: warning: initialization from 
incompatible pointer type
/usr/src/modules/fglrx/firegl_public.c:3897: error: unknown field ‘nopage’ 
specified in initializer
/usr/src/modules/fglrx/firegl_public.c:3897: warning: initialization from 
incompatible pointer type
make[3]: *** [/usr/src/modules/fglrx/firegl_public.o] Error 1
make[2]: *** [_module_/usr/src/modules/fglrx] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/usr/src/modules/fglrx'
make: *** [kdist_image] Error 2




-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SM

Bug#495184: wodim: Fails, then asks me to use the option I've already given

[Sven Joachim]

On 2008-08-20 12:38 +0200, Nigel Horne wrote:

> Strace output attached.

Thanks, it seems that your burner is called /dev/hdc.  Is that correct?

> write(1, "\t1000,2,0 12) 'Optiarc ' 'DVD"..., 72  1000,2,0 12) 
> 'Optiarc ' 'DVD RW AD-5170A ' '1.52' Removable CD-ROM
> ) = 72

Here you go, that is your device.  So `wodim -scanbus' works at least
under strace.  Strange...

Can you try to actually burn a CD?  Use the `-dummy' option if you don't
want to waste a disc.

Sven



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

Bug#495184: wodim: Fails, then asks me to use the option I've already given

[Peter Samuelson]

[Nigel Horne]
> write(1, "\t1000,2,0 12) 'Optiarc ' 'DVD"..., 72  1000,2,0 12) 
> 'Optiarc ' 'DVD RW AD-5170A ' '1.52' Removable CD-ROM
> ) = 72
> write(1, "\t1000,3,0 13) *\n"..., 20  1000,3,0 13) *
> ) = 20
> write(1, "\t1000,4,0 14) *\n"..., 20  1000,4,0 14) *
> ) = 20
> write(1, "\t1000,5,0 15) *\n"..., 20  1000,5,0 15) *
> ) = 20
> write(1, "\t1000,6,0 16) *\n"..., 20  1000,6,0 16) *
> ) = 20
> write(1, "\t1000,7,0 17) *\n"..., 20  1000,7,0 17) *
> ) = 20

I thought you said wodim -scanbus didn't work?  Looks to me like it
worked.

Does 'lsmod' indicate that you have the cdrom or ide_cd or ide_cd_mod
modules loaded?  Also, does 'cat /proc/sys/cdrom/info' show information
about /dev/hdc?
-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/



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

Bug#495184: wodim: Fails, then asks me to use the option I've already given

[Sven Joachim]

On 2008-08-20 12:37 +0200, Nigel Horne wrote:

> packard:/home/njh# ls -l /dev/s[cgr]*
> ls: cannot access /dev/s[cgr]*: No such file or directory

Okay, so you're using the old IDE cdrom driver instead of libata/sr_mod.
Should not be a problem, though.

Sven



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

Bug#494842: marked as done (versatile kernel doesn't boot)

[Debian Bug Tracking System]

Your message dated Wed, 20 Aug 2008 11:09:25 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#494842: fixed in linux-2.6 2.6.26-3
has caused the Debian Bug report #494842,
regarding versatile kernel doesn't boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
494842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494842
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.26-2
Severity: serious

The current versatile kernel doesn't boot in QEMU.  This bug should
not stop 2.6.26 from migrating to testing though since versatile is
not a platform that is used a lot.

Aurelien Jarno looked at the problem and found:

| It's because I have enabled tickless options in the kernel. I don't
| know if it is actually a qemu or a kernel problem, but given we are
| close to the release, the best is simply to disable this options.
| Unfortunately I am afraid this will change the ABI...

I'll disable the option when we change the ABI.

-- 
Martin Michlmayr
http://www.cyrius.com/


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.26-3

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

linux-2.6_2.6.26-3.diff.gz
  to pool/main/l/linux-2.6/linux-2.6_2.6.26-3.diff.gz
linux-2.6_2.6.26-3.dsc
  to pool/main/l/linux-2.6/linux-2.6_2.6.26-3.dsc
linux-doc-2.6.26_2.6.26-3_all.deb
  to pool/main/l/linux-2.6/linux-doc-2.6.26_2.6.26-3_all.deb
linux-headers-2.6.26-1-all-powerpc_2.6.26-3_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-all-powerpc_2.6.26-3_powerpc.deb
linux-headers-2.6.26-1-all_2.6.26-3_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-all_2.6.26-3_powerpc.deb
linux-headers-2.6.26-1-common-vserver_2.6.26-3_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-common-vserver_2.6.26-3_powerpc.deb
linux-headers-2.6.26-1-common_2.6.26-3_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-common_2.6.26-3_powerpc.deb
linux-headers-2.6.26-1-powerpc-smp_2.6.26-3_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc-smp_2.6.26-3_powerpc.deb
linux-headers-2.6.26-1-powerpc64_2.6.26-3_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc64_2.6.26-3_powerpc.deb
linux-headers-2.6.26-1-powerpc_2.6.26-3_powerpc.deb
  to pool/main/l/linux-2.6/linux-headers-2.6.26-1-powerpc_2.6.26-3_powerpc.deb
linux-headers-2.6.26-1-vserver-powerpc64_2.6.26-3_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-vserver-powerpc64_2.6.26-3_powerpc.deb
linux-headers-2.6.26-1-vserver-powerpc_2.6.26-3_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-headers-2.6.26-1-vserver-powerpc_2.6.26-3_powerpc.deb
linux-image-2.6.26-1-powerpc-smp_2.6.26-3_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc-smp_2.6.26-3_powerpc.deb
linux-image-2.6.26-1-powerpc64_2.6.26-3_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc64_2.6.26-3_powerpc.deb
linux-image-2.6.26-1-powerpc_2.6.26-3_powerpc.deb
  to pool/main/l/linux-2.6/linux-image-2.6.26-1-powerpc_2.6.26-3_powerpc.deb
linux-image-2.6.26-1-vserver-powerpc64_2.6.26-3_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.26-1-vserver-powerpc64_2.6.26-3_powerpc.deb
linux-image-2.6.26-1-vserver-powerpc_2.6.26-3_powerpc.deb
  to 
pool/main/l/linux-2.6/linux-image-2.6.26-1-vserver-powerpc_2.6.26-3_powerpc.deb
linux-libc-dev_2.6.26-3_powerpc.deb
  to pool/main/l/linux-2.6/linux-libc-dev_2.6.26-3_powerpc.deb
linux-manual-2.6.26_2.6.26-3_all.deb
  to pool/main/l/linux-2.6/linux-manual-2.6.26_2.6.26-3_all.deb
linux-patch-debian-2.6.26_2.6.26-3_all.deb
  to pool/main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-3_all.deb
linux-source-2.6.26_2.6.26-3_all.deb
  to pool/main/l/linux-2.6/linux-source-2.6.26_2.6.26-3_all.deb
linux-support-2.6.26-1_2.6.26-3_all.deb
  to pool/main/l/linux-2.6/linux-support-2.6.26-1_2.6.26-3_all.deb
linux-tree-2.6.26_2.6.26-3_all.deb
  to pool/main/l/linux-2.6/linux-tree-2.6.26_2.6.26-3_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank <[EMAIL PROTECTED]> (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
a

Processed (with 1 errors): (no subject)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> Severity 495421 important
Bug#495421: fakeroot-ng: does not appear to work any more
Severity set to `important' from `grave'

> Retitle 495421 Fakeroot-ng silently fails when /tmp is mount noexec
Bug#495421: fakeroot-ng: does not appear to work any more
Changed Bug title to `Fakeroot-ng silently fails when /tmp is mount noexec' 
from `fakeroot-ng: does not appear to work any more'.

> 
Unknown command or malformed arguments to command.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495184: wodim: Fails, then asks me to use the option I've already given

[Nigel Horne]

Sven Joachim wrote:

On 2008-08-18 10:28 +0200, Nigel Horne wrote:

  

I was running as root, on a default system. Does Debian include root
in the cdrom
group by default?



No, but root doesn't have to be in the cdrom group.  Can you please post
the output of `ls -l /dev/s[cgr]*' and `strace wodim -scanbus'?
  

packard:/home/njh# ls -l /dev/s[cgr]*
ls: cannot access /dev/s[cgr]*: No such file or directory
packard:/home/njh#



Sven
  



--
Nigel Horne. Adjudicator, Arranger, Band Trainer, Conductor, Composer, Tutor.
NJH Music, Barnsley, UK.  ICQ#20252325
[EMAIL PROTECTED] http://www.bandsman.co.uk




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

Bug#495184: wodim: Fails, then asks me to use the option I've already given

[Sven Joachim]

On 2008-08-18 10:28 +0200, Nigel Horne wrote:

> I was running as root, on a default system. Does Debian include root
> in the cdrom
> group by default?

No, but root doesn't have to be in the cdrom group.  Can you please post
the output of `ls -l /dev/s[cgr]*' and `strace wodim -scanbus'?

Sven



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

Bug#495773: xfmail has rpath to insecure location (/tmp/buildd/xfmail-1.5.5.dfsg.1/debian/xfmail/usr/lib/xfmail:/usr/lib/xfmail)

[Bill Allombert]

Package: xfmail
Version: 1.5.5.dfsg.1-0.1
Severity: serious
Tags: security

Hello Florian,
xfmail includes a binary /usr/bin/xfmail with a rpath pointing to
/tmp/buildd/xfmail-1.5.5.dfsg.1/debian/xfmail/usr/lib/xfmail.

chrpath /usr/bin/xfmail
/usr/bin/xfmail: 
RPATH=/tmp/buildd/xfmail-1.5.5.dfsg.1/debian/xfmail/usr/lib/xfmail:/usr/lib/xfmail

This allows an attacker with write access to that directory to add
modified libraries which will be loaded when someone else run xfmail.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



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

Bug#495770: marble has rpath to insecure location (/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/)

[Bill Allombert]

Package: marble
Version: 0.6+svn837399-1
Severity: serious
Tags: security

Hello Carsten,
the amd64 marble package includes a ELF file
/usr/lib/marble/plugins/libMarbleStarsPlugin.so with a rpath pointing to
/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/.

There are others:

$chrpath /usr/lib/marble/plugins/*
/usr/lib/marble/plugins/libCompassFloatItem.so: 
RPATH=/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/
/usr/lib/marble/plugins/libMapScaleFloatItem.so: 
RPATH=/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/
/usr/lib/marble/plugins/libMarbleOverviewMap.so: 
RPATH=/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/
/usr/lib/marble/plugins/libMarbleStarsPlugin.so: 
RPATH=/tmp/buildd/marble-0.6+svn837399/debian/tmp/usr/

This allows an attacker with write access to that directory to
add modified libraries which will be loaded when someone
else run marble.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



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

Bug#495769: libpam-nufw has rpath to insecure location (/home/pollux/DEBIAN/NUFW/nufw-2.2.15/src/clients/lib/.libs)

[Bill Allombert]

Package: libpam-nufw
Version: 2.2.15-1
Severity: serious
Tags: security

Hello Pierre,
libpam-nufw includes a binary /lib/security/pam_nufw.so with a rpath pointing 
to /home/pollux/DEBIAN/NUFW/nufw-2.2.15/src/clients/lib/.libs.

This allows an attacker with write access to that directory to
add modified libraries which will be loaded when someone
else run libpam-nufw.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



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

Bug#495756: ecl has rpath to insecure location (/tmp/buildd/ecl-0.9j-20080306/build/)

[Bill Allombert]

Package: ecl
Version: 0.9j-20080306-4
Severity: serious
Tags: security

Hello Debian Common Lisp Team,
ecl includes a ELF file /usr/lib/ecl/asdf.fas with a rpath pointing to
/tmp/buildd/ecl-0.9j-20080306/build/.

This allows an attacker with write access to that directory to
add modified libraries which will be loaded when someone
else run ecl.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



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

Bug#495758: kwave has rpath to insecure location (/build/buildd/kwave-0.7.10/build/mt:/build/buildd/kwave-0.7.10/build/libgui:/build/buildd/kwave-0.7.10/build/libkwave)

[Bill Allombert]

Package: kwave
Version: 0.7.10-1.1
Severity: serious
Tags: security

Hello Bertrand,
kwave includes a binary /tmp/kwave//usr/share/apps/kwave/plugins/about
with a rpath pointing to
/build/buildd/kwave-0.7.10/build/mt:/build/buildd/kwave-0.7.10/build/libgui:/build/buildd/kwave-0.7.10/build/libkwave.

This allows an attacker with write access to that directory to
add modified libraries which will be loaded when someone
else run kwave.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



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

Processed: Re: Bug#495738: abiword: Garbled text

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 495738 normal
Bug#495738: abiword: Garbled text
Severity set to `normal' from `grave'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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

Bug#495738: abiword: Garbled text

[Joshua Kwan]

severity 495738 normal
thanks

I haven't seen this and many people that use abiword obviously haven't
either or else I would have been inundated with bug reports. I suggest
you try creating a new user and see if the problem recurs just in case
it has something to do with fontconfig, or your particular window
manager setup.

For now I'm setting the severity to normal. If you can give a
top-to-bottom method for reproducing this bug (considering I can't right
now), I will look in to it and adjust the severity again as required.

-Josh

On Tue, Aug 19, 2008 at 11:54:36PM -0700, BlueSloth wrote:
> Package: abiword
> Version: 2.6.4-4
> Severity: grave
> Justification: renders package unusable
> 
> All the text in a document is garbled and unreadable.
> 
> Hmm.. upon further inspection it looks like it's not so much garbled as 
> mashed together.  Abiword appears to expect the characters to render about 5 
> times smaller than they actually are, and so isn't giving them enough space.  
> The cursor is very small, and only the lower part of a character disappears 
> when I delete it.
> 
> Changing the font, font size, zoom level, and paragraph spacing settings 
> don't help.
> 
> The sample text in the font selection dialog renders perfectly.  The text in 
> the Paragraph dialog is smushed together vertically, but not horizontally.

-- 
Joshua Kwan



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

Bug#495753: chicken-bin has rpath to insecure location (/home/evo/chicken-3.2.7/debian/tmp/usr/lib)

[Bill Allombert]

Package: chicken-bin
Version: 3.2.7-1
Severity: serious
Tags: security

Hello Davide,
chicken-bin includes a binary /usr/bin/chicken with a rpath pointing 
to /home/evo/chicken-3.2.7/debian/tmp/usr/lib

This allows an attacker with write access to that directory to
add modified libraries which will be loaded when someone
else run chicken-bin.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



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

Bug#495501: midori: Segfault on some web pages

[Marcus Better]

severity 495501 grave
thanks

Actually Midori segfaults for me on many, if not all, web pages, including the 
page in the original report and 
www.debian.org (the default start page!).

Here is a stack trace.

~$ gdb midori
GNU gdb 6.8-debian   
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.   
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
and "show warranty" for details. 
This GDB was configured as "x86_64-linux-gnu"... 
(gdb) r  
Starting program: /usr/bin/midori
[Thread debugging using libthread_db enabled]
warning: Lowest section in /usr/lib/libicudata.so.38 is .hash at 
0120
[New Thread 0x7f89eef0d7a0 (LWP 28930)] 
 

(midori:28930): Gtk-WARNING **: Error loading theme icon 'stock_new-tab' for 
stock: Ikonen "stock_new-tab" 
finns inte i temat  
 

(midori:28930): Gtk-WARNING **: Error loading theme icon 'gnome-stock-trash' 
for stock: Ikonen "gnome-stock-
trash" finns inte i temat   


** (midori:28930): WARNING **: Icon 'process-working' couldn't be loaded
[New Thread 0x41e52950 (LWP 28933)] 

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x41e52950 (LWP 28933)]
0x in ?? () 
(gdb) thread apply all bt full  

Thread 2 (Thread 0x41e52950 (LWP 28933)):
#0  0x in ?? ()  
No symbol table info available.  
#1  0x7f89eebe6646 in open_read_async_thread (res=0x80db60, 
object=0x932950, cancellable=0x0)
at /build/buildd/glib2.0-2.16.4/gio/gfile.c:4015
 
stream =   
 
error = (GError *) 0x0  
 
#2  0x7f89eebf9fdf in run_in_thread (job=, c=0x0,  
 
_data=) at 
/build/buildd/glib2.0-2.16.4/gio/gsimpleasyncresult.c:613
data = (RunInThreadData *) 0x9c0f60 
 
simple = (GSimpleAsyncResult *) 0x80db60
 
#3  0x7f89eebf3dc6 in io_job_thread (data=,
 
user_data=) at 
/build/buildd/glib2.0-2.16.4/gio/gioscheduler.c:178  
job = (GIOSchedulerJob *) 0x9c0f80  
 
result = 9431312
 
#4  0x7f89ee318a37 in g_thread_pool_thread_proxy (data=)
at /build/buildd/glib2.0-2.16.4/glib/gthreadpool.c:265  
 
task = (gpointer) 0x9c0f80  
 
pool = (GRealThreadPool *) 0x8ff8d0 
 
#5  0x7f89ee3174a4 in g_thread_create_proxy (data=0x8ff9f0) 
 
at /build/buildd/glib2.0-2.16.4/glib/gthread.c:635  
 
__PRETTY_FUNCTION__ = "g_thread_create_proxy"   
 
#6  0x7f89e77ccfc7 in start_thread () from /lib/libpthread.so.0 
 
No symbol table info available. 
 
#7  0x7f89eb79a7cd in clone () from /lib/libc.so.6  
 
No symbol table info available. 
 
#8  0x in ?? () 
 
No symbol table info available. 
 

Thread 1 (Thread 0x7f89eef0d7a0 (LWP 28930)):
---Type  to continue, or q  to quit---
#0  0x7f89eb793f12 in select () from /lib/libc.so.6
No symbol table info available.
#1  0x7f89e8e079e6 in ?? () from /usr/lib/libxcb.so.1
No symbol table info available.  
#2  0x7f89e8e09575 in xcb_wait_for_reply () from /usr/lib/libxcb.so.1
No symbol table info available.  
#3  0x7f89eafca1ae in _XReply () from /usr/lib/libX11.so.6   
No symbol table info available.  
#4  0x7f89eafbddb3 in XSync () from /u

Bug#495655: cpufreqd: uses "energy_full" instead of "charge_full" under /sys/...

[alberto maurizi]

Package: cpufreqd
Followup-For: Bug #495655


the error message is:
cpufreqd: get_class_device_attribute: couldn't open 
/sys/class/power_supply/BAT0/energy_full (No such file or directory)
[...]
kernel: [19344.165939] cpufreqd[24816]: segfault at 40 ip b7e04283 sp bfb30770 
error 4 in libc-2.7.so[b7d8e000+155000]

under /sys/class/power_supply/BAT0/ path I can see a "charge_full"
rather than "energy_full". Maybe some inconsistency in naming
convention?


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages cpufreqd depends on:
ii  libc6 2.7-13 GNU C Library: Shared libraries
ii  libcpufreq0   004-2  shared library to deal with the cp
ii  libsensors3   1:2.10.7-1 library to read temperature/voltag
ii  libsysfs2 2.1.0-4interface library to sysfs
ii  lsb-base  3.2-19 Linux Standard Base 3.2 init scrip

Versions of packages cpufreqd recommends:
ii  acpid 1.0.6-10   Utilities for using ACPI power man

Versions of packages cpufreqd suggests:
ii  cpufrequtils  004-2  utilities to deal with the cpufreq

-- no debconf information



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