Bug#383555: udev/initramfs-tools/...

[Osamu Aoki]

I also suffered this boot problem.

Thanks to (not so well documented) feature in update-initramfs, postinst
of udev only updates the latest kernel.  Thus I was able to boot with
older kernel.

The latest initramfs-tools seems to solved the issue for booting and
starting with latest udev.

If anyone is reruning to create initramfs, please do following:
(I am assuming few kernels to be there.)

1. Boot with older kernel (like 2.6.16 ones)
2. Install latest unstable versions of packages
initramfs-tools 0.75   tools for generating an initramfs
3. run update-initramfs -u to get the latest kernel initramfs updated.
4. Reboot to confirm the latest kernel works.
5. If there is other kernel which suffered the same issue, run
   update-initramfs -k all -u and hope all kernels to work fine.

This manual update is needed since udev.postinst has only 
update-initramfs -u which only works on the latest kernel version.

See more on:

   http://bugs.debian.org/360281
   http://bugs.debian.org/383600

Osamu
-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki [EMAIL PROTECTED]  Yokohama Japan, GPG-key: A8061F32
 .''`.  Debian Reference: post-installation user's guide for non-developers
 : :' : http://qref.sf.net and http://people.debian.org/~osamu
 `. `'  Our Priorities are Our Users and Free Software --- Social Contract



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

Bug#380466: #380466 - kazehakase: quits when going to any HTTP AUTH page

[Mike Hommey]

On Sun, Aug 20, 2006 at 02:34:47AM +0200, Alexander Sack [EMAIL PROTECTED] 
wrote:
 
 Mike, can you take a look? Appears to be related with xulrunner
 transition. So maybe you have an idea what the reason might be.

I didn't try to reproduce the bug and see the backtrace to verify my
assumptions, but I think it is the same bug as #376323, which I wanted
to fix in next upload of xulrunner at the time I wrote to the bug but
with the security update of 1.8.0.5, I forgot to apply the patches from
the BTS. It will be fixed in 1.8.0.5-2 anyway. I'm just waiting for
1.8.0.5-1 to migrate to testing.

I'll take a look at kazehakase to see if it's the same bug.

Mike


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

Bug#380466: #380466 - kazehakase: quits when going to any HTTP AUTH page

[Mike Hommey]

On Sun, Aug 20, 2006 at 08:53:27AM +0200, Mike Hommey [EMAIL PROTECTED] wrote:
 On Sun, Aug 20, 2006 at 02:34:47AM +0200, Alexander Sack [EMAIL PROTECTED] 
 wrote:
  
  Mike, can you take a look? Appears to be related with xulrunner
  transition. So maybe you have an idea what the reason might be.
 
 I didn't try to reproduce the bug and see the backtrace to verify my
 assumptions, but I think it is the same bug as #376323, which I wanted
 to fix in next upload of xulrunner at the time I wrote to the bug but
 with the security update of 1.8.0.5, I forgot to apply the patches from
 the BTS. It will be fixed in 1.8.0.5-2 anyway. I'm just waiting for
 1.8.0.5-1 to migrate to testing.
 
 I'll take a look at kazehakase to see if it's the same bug.

M, sadly, i can't even reproduce the bug. Is the password manager
enabled by default ? I see kazehakase has indeed a user profile for the
underlying gecko, which means it may not be #376323, but i'd like to at
least be able to reproduce the bug...

Gerfried, could you provide detailed steps to be able to reproduce for a
non kazehakase user (meaning with no $HOME/.kazehakase) in the first
place ?

Alternatively, it would be nice to have a full backtrace after segfault
(preferably install libxul0d-dbg before getting the backtrace). Maybe an
strace would be helpful, too.

Mike


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

Bug#376771: remove unused 2.4 images

[Sven Luther]

On Sun, Aug 20, 2006 at 04:12:06AM +0200, Jeroen van Wolffelaar wrote:
 And I have no idea about:
 kernel-patch-2.4.27-apus

This one can go too. Actually, i believe it is part of the
kernel-source-2.4.27-powerpc or whatever its name was source package, which
can go also.

Friendly,

Sven Luther


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

Processed: Re: Bug#383859: Failed to install nullmailer 1:1.0.3-2

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 tags 383859 +unreproducible
Bug#383859: Failed to install nullmailer 1:1.0.3-2
There were no tags set.
Tags added: unreproducible

 tags 383859 +moreinfo
Bug#383859: Failed to install nullmailer 1:1.0.3-2
Tags were: unreproducible
Tags added: moreinfo

 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#383859: Failed to install nullmailer 1:1.0.3-2

[Kanru Chen]

On Sun, Aug 20, 2006 at 10:00:57AM +0200, Norbert Tretkowski wrote:
 I'm unable to reproduce this problem. Could you please replace the
 
 set -e
 
 in /var/lib/dpkg/info/nullmailer.postinst with
 
 set -x 
 
 and send me the complete output when processing the package again?
 
 Norbert

+ . /usr/share/debconf/confmodule
++ '[' '!' '' ']'
++ PERL_DL_NONLAZY=1
++ export PERL_DL_NONLAZY
++ '[' '' ']'
++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/nullmailer.postinst 
configure 1:1.02-8
dpkg: error processing nullmailer (--configure):
 subprocess post-installation script returned error exit status 128
Errors were encountered while processing:
 nullmailer

-- 
~Kanru Chen [EMAIL PROTECTED]
   'v'   http://stu.csie.ncnu.edu.tw/~kanru.96/
  // \\  GnuPG-Key ID: 365CC7A2
 /(   )\ Fingerprint: 3278 DFB4 BB28 6E8C 9E1F  1ECB B1B7 5B5F 365C C7A2
  ^`~'^


signature.asc
Description: Digital signature

Bug#383859: Failed to install nullmailer 1:1.0.3-2

[Norbert Tretkowski]

tags 383859 +unreproducible
tags 383859 +moreinfo
thanks

* Kanru Chen wrote:
 Errors were encountered while processing:
  nullmailer
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 A package failed to install.  Trying to recover:
 Setting up nullmailer (1.03-2) ...
 dpkg: error processing nullmailer (--configure):
  subprocess post-installation script returned error exit status 20
 Errors were encountered while processing:
  nullmailer

I'm unable to reproduce this problem. Could you please replace the

set -e

in /var/lib/dpkg/info/nullmailer.postinst with

set -x 

and send me the complete output when processing the package again?

Norbert


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

Bug#383304: bin-NMU scheduling for python transition

[Steve Langasek]

Oi Gustavo,

On Fri, Aug 18, 2006 at 12:20:29AM -0300, Gustavo Noronha Silva wrote:

 Some of my Python packages should simply require a binNMU to be in
 shape with the new python package which is 2.4:

 ruledispatch (python-dispatch)
 pyprotocols (python-protocols)
 turbojson (python-turbojson)
 turbogears (python-turbogears)

 This last one is in experimental, so I'm not sure a binNMU scheduled by
 the Release Team is possible, so if a different action on my part (such
 as a manual binNMU or a sourceful upload) is required, please let me
 know.

turbojson and turbogears are arch: all packages and cannot be binNMUed.  It
also doesn't look like they need to be -- they depend on python (= 2.4) |
python2.4, which is satisfied just fine.

The other two packages are arch: any and so can be binNMUed, but I'm puzzled
why they build-depend on python-all-dev if they only build for the current
version of python.  Perhaps this is something you would like to fix with a
sourceful upload?

FWIW, I remain pretty unimpressed with the decision to make the control
fields optional in the python policy.  The pycentral-using packages which
are binNMUable for the transition have all already been binNMUed using only
the information in the Packages and Sources files, but hunting down the list
of binNMUable packages that aren't using these fields will require a full,
current source mirror and a lot of unpacking and rooting around in source
packages.

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


signature.asc
Description: Digital signature

Processed: Re: gst-plugins-base0.10: FTBFS on arm (segfault) due to buildd or package error?

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 retitle 383147 [arm] doc doesn't build on arm
Bug#383147: gst-plugins-base0.10 (arm/unstable): FTBFS: Segmentation fault
Changed Bug title.

 severity 383147 minor
Bug#383147: [arm] doc doesn't build on arm
Severity set to `minor' from `serious'

 tags 383147 + help upstream confirmed
Bug#383147: [arm] doc doesn't build on arm
There were no tags set.
Tags added: help, upstream, confirmed

 tags 383147 + arm
Unknown tag/s: arm.
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.

Bug#383147: [arm] doc doesn't build on arm
Tags were: confirmed upstream help
Tags added: 

 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#381386: marked as done (gs-esp: doesn't render accents in accented polish letters using truetype fonts)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 01:32:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381386: fixed in gs-esp 8.15.2.dfsg.1-2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: gs-esp
Version: 8.15.2.dfsg.1-1
Severity: important

I've observed it when I've tried to print document from OpenOffice Writer
with Arial font using CUPS Kyocera FS-1000 Foomatic/pxlmono backend.
Using 600 DPI quality, only two letters (small and big slashed L) has been
printed. Later I've tried to change backend to CUPS+Gutenprint also in
600 DPI and result was the same, but in 150 DPI accented small letter e was
printed additionally - letters 'a c s z' still didn't have their accents.
Next I've exported document to pdf and tried to print from kpdf - no luck
also - on screen everything looks ok, but on paper fails. So I've checked
what happens when importing pdf version to GIMP using 600 DPI and final
picture was without accents. Next I've checked other fonts in document
FreeSans and FreeSerif - didn't helped - same error. So finally I've
downgraded 8.15.1.dfsg.1-2 from 'testing' and with this version everything
works fine.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)

Versions of packages gs-esp depends on:
ii  gs-common   0.3.9Common files for different Ghostsc
ii  libc6   2.3.6-16 GNU C Library: Shared libraries
ii  libcupsimage2   1.2.2-1  Common UNIX Printing System(tm) - 
ii  libcupsys2  1.2.2-1  Common UNIX Printing System(tm) - 
ii  libice6 1:1.0.0-3X11 Inter-Client Exchange library
ii  libjpeg62   6b-13The Independent JPEG Group's JPEG 
ii  libpaper1   1.1.19   Library for handling paper charact
ii  libpng12-0  1.2.8rel-5.2 PNG library - runtime
ii  libsm6  1:1.0.0-4X11 Session Management library
ii  libstdc++6  4.1.1-10 The GNU Standard C++ Library v3
ii  libtiff43.8.2-6  Tag Image File Format (TIFF) libra
ii  libx11-62:1.0.0-7X11 client-side library
ii  libxext61:1.0.0-4X11 miscellaneous extension librar
ii  libxt6  1:1.0.0-5X11 toolkit intrinsics library
ii  zlib1g  1:1.2.3-13   compression library - runtime

Versions of packages gs-esp recommends:
ii  gsfonts   8.14+v8.11+urw-0.2 Fonts for the Ghostscript interpre
ii  psfontmgr 0.11.10PostScript font manager -- part of

-- no debconf information

---End Message---
---BeginMessage---
Source: gs-esp
Source-Version: 8.15.2.dfsg.1-2

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

gs-esp_8.15.2.dfsg.1-2.diff.gz
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-2.diff.gz
gs-esp_8.15.2.dfsg.1-2.dsc
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-2.dsc
gs-esp_8.15.2.dfsg.1-2_i386.deb
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-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.
Kenshi Muto [EMAIL PROTECTED] (supplier of updated gs-esp 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.7
Date: Thu, 10 Aug 2006 18:33:07 +0900
Source: gs-esp
Binary: gs-esp
Architecture: source i386
Version: 8.15.2.dfsg.1-2
Distribution: unstable
Urgency: medium
Maintainer: Masayuki Hatta (mhatta) [EMAIL PROTECTED]
Changed-By: Kenshi Muto [EMAIL PROTECTED]
Description: 
 gs-esp - The Ghostscript PostScript interpreter - ESP version
Closes: 381386 382250
Changes: 
 gs-esp (8.15.2.dfsg.1-2) unstable; urgency=medium
 .
   [Kenshi Muto]
   * gs-cjk-resource still needs for CJK people.
 Revert a dependency.
   * Apply revert patch 166:164. Upsream CJK patch broke umlaute.

Bug#382250: marked as done (gs-esp doesn't print german umlauts)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 01:32:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381386: fixed in gs-esp 8.15.2.dfsg.1-2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: gs-esp
Version: 8.15.2.dfsg.1-2

I updated gs-esp from 8.15.1.dfsg.1.1 to 8.15.2.dfsg.1-2. After that I 
discovered printing problems when using german umlauts in fonts supplied 
through msttcorefonts. I saw the same behaviour when looking at the 
postscript-files with gv.

I had a look at system configuration and all the encoding files but I couldn't 
find any apparent configuration error. After downgrading gs-esp everything 
works well again. 

Find attached a small postscript-File with an example. You may not have a 
german setup ;)

The dependencies have the following versions:

gs-common: 0.3.9
libfontconfig: 2.3.2-7
libc6; 2.3.6-6
libcupsimage2: 1.2.2-1
libcupsys2: 1.2.2-1
libgnutls13: 1.4.1-1
libice6: 1.0.0-2
libjpeg62: 6b-10
libpaper1: 1.1.14-3
libpng12-0: 1.2.8rel-5
libsm6: 1.0.0-3
libstdc++: 4.1.0-1
libtiff4: 3.7.1-3
libx11-6: 2:1.0.0-6
libxext6: 1:1.0.0-3
libxt6: 1:1.0.0-3
zliblg: 1:1.2.3-9

The system is based on Debian Unstable running kernel 2.6.17 on a Sempron 
2800+



ps.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: gs-esp
Source-Version: 8.15.2.dfsg.1-2

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

gs-esp_8.15.2.dfsg.1-2.diff.gz
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-2.diff.gz
gs-esp_8.15.2.dfsg.1-2.dsc
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-2.dsc
gs-esp_8.15.2.dfsg.1-2_i386.deb
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-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.
Kenshi Muto [EMAIL PROTECTED] (supplier of updated gs-esp 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.7
Date: Thu, 10 Aug 2006 18:33:07 +0900
Source: gs-esp
Binary: gs-esp
Architecture: source i386
Version: 8.15.2.dfsg.1-2
Distribution: unstable
Urgency: medium
Maintainer: Masayuki Hatta (mhatta) [EMAIL PROTECTED]
Changed-By: Kenshi Muto [EMAIL PROTECTED]
Description: 
 gs-esp - The Ghostscript PostScript interpreter - ESP version
Closes: 381386 382250
Changes: 
 gs-esp (8.15.2.dfsg.1-2) unstable; urgency=medium
 .
   [Kenshi Muto]
   * gs-cjk-resource still needs for CJK people.
 Revert a dependency.
   * Apply revert patch 166:164. Upsream CJK patch broke umlaute.
 (closes: #381386, #382250)
Files: 
 9f493570797b85ce6320afb639423f09 851 text optional gs-esp_8.15.2.dfsg.1-2.dsc
 fdfa0996ea0691a35c9004ad6d64416d 166912 text optional 
gs-esp_8.15.2.dfsg.1-2.diff.gz
 6687cb5892ff34120ae5080cfdfeb884 3000740 text optional 
gs-esp_8.15.2.dfsg.1-2_i386.deb

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

iEYEARECAAYFAkToGr8ACgkQQKW+7XLQPLFB9QCgu5sBd9dACm2iK+csUPqgOyv5
9wQAnjALRDRueRjrl1pf90quzxDjgUlY
=JlRZ
-END PGP SIGNATURE-

---End Message---

Bug#383147: gst-plugins-base0.10: FTBFS on arm (segfault) due to buildd or package error?

[Loïc Minier]

retitle 383147 [arm] doc doesn't build on arm
severity 383147 minor
tags 383147 + help upstream confirmed
tags 383147 + arm
stop

Hi,

On Sun, Aug 13, 2006, Luk Claes wrote:
 Can you please look into the FTBFS on arm [1] and either fix the problem
 if it's a problem in the package or contact the [EMAIL PROTECTED]

 (Luk, sorry for not responding earlier, I thought this was a reminder
 bug report, but it was a real mail.)

 Steve, thanks for the reminder.

 I've uploaded a package which stops building the doc under arm and
 m68k.


 I'm not interested in investigating the issue of building the
 documentation under arm because:
 - upstream have made local changes to the gtk-doc infrastructure after
   the bootstrapping instead of fixing gtk-doc to suite their needs, I'm
   not interested in chasing bugs they might have introduced under arm
   in this process
 - the doc is arch: all, so it would only matter for people preparing
   uploads under arm
 - the doc is painfully slow to build anyway, so it makes sense to not
   build it under arm, even if it would work
 - I'm not even sure the HTML files are not a form of modification
   convenient enough for us; the doc build system has caused too much
   headache in the past (an infinite loop in jade comes to mind)

   Bye,
-- 
Loïc Minier [EMAIL PROTECTED]

Bug#382250: marked as done (gs-esp doesn't print german umlauts)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 01:32:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382250: fixed in gs-esp 8.15.2.dfsg.1-2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: gs-esp
Version: 8.15.2.dfsg.1-2

I updated gs-esp from 8.15.1.dfsg.1.1 to 8.15.2.dfsg.1-2. After that I 
discovered printing problems when using german umlauts in fonts supplied 
through msttcorefonts. I saw the same behaviour when looking at the 
postscript-files with gv.

I had a look at system configuration and all the encoding files but I couldn't 
find any apparent configuration error. After downgrading gs-esp everything 
works well again. 

Find attached a small postscript-File with an example. You may not have a 
german setup ;)

The dependencies have the following versions:

gs-common: 0.3.9
libfontconfig: 2.3.2-7
libc6; 2.3.6-6
libcupsimage2: 1.2.2-1
libcupsys2: 1.2.2-1
libgnutls13: 1.4.1-1
libice6: 1.0.0-2
libjpeg62: 6b-10
libpaper1: 1.1.14-3
libpng12-0: 1.2.8rel-5
libsm6: 1.0.0-3
libstdc++: 4.1.0-1
libtiff4: 3.7.1-3
libx11-6: 2:1.0.0-6
libxext6: 1:1.0.0-3
libxt6: 1:1.0.0-3
zliblg: 1:1.2.3-9

The system is based on Debian Unstable running kernel 2.6.17 on a Sempron 
2800+



ps.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: gs-esp
Source-Version: 8.15.2.dfsg.1-2

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

gs-esp_8.15.2.dfsg.1-2.diff.gz
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-2.diff.gz
gs-esp_8.15.2.dfsg.1-2.dsc
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-2.dsc
gs-esp_8.15.2.dfsg.1-2_i386.deb
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-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.
Kenshi Muto [EMAIL PROTECTED] (supplier of updated gs-esp 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.7
Date: Thu, 10 Aug 2006 18:33:07 +0900
Source: gs-esp
Binary: gs-esp
Architecture: source i386
Version: 8.15.2.dfsg.1-2
Distribution: unstable
Urgency: medium
Maintainer: Masayuki Hatta (mhatta) [EMAIL PROTECTED]
Changed-By: Kenshi Muto [EMAIL PROTECTED]
Description: 
 gs-esp - The Ghostscript PostScript interpreter - ESP version
Closes: 381386 382250
Changes: 
 gs-esp (8.15.2.dfsg.1-2) unstable; urgency=medium
 .
   [Kenshi Muto]
   * gs-cjk-resource still needs for CJK people.
 Revert a dependency.
   * Apply revert patch 166:164. Upsream CJK patch broke umlaute.
 (closes: #381386, #382250)
Files: 
 9f493570797b85ce6320afb639423f09 851 text optional gs-esp_8.15.2.dfsg.1-2.dsc
 fdfa0996ea0691a35c9004ad6d64416d 166912 text optional 
gs-esp_8.15.2.dfsg.1-2.diff.gz
 6687cb5892ff34120ae5080cfdfeb884 3000740 text optional 
gs-esp_8.15.2.dfsg.1-2_i386.deb

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

iEYEARECAAYFAkToGr8ACgkQQKW+7XLQPLFB9QCgu5sBd9dACm2iK+csUPqgOyv5
9wQAnjALRDRueRjrl1pf90quzxDjgUlY
=JlRZ
-END PGP SIGNATURE-

---End Message---

Bug#381386: marked as done (gs-esp: doesn't render accents in accented polish letters using truetype fonts)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 01:32:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382250: fixed in gs-esp 8.15.2.dfsg.1-2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: gs-esp
Version: 8.15.2.dfsg.1-1
Severity: important

I've observed it when I've tried to print document from OpenOffice Writer
with Arial font using CUPS Kyocera FS-1000 Foomatic/pxlmono backend.
Using 600 DPI quality, only two letters (small and big slashed L) has been
printed. Later I've tried to change backend to CUPS+Gutenprint also in
600 DPI and result was the same, but in 150 DPI accented small letter e was
printed additionally - letters 'a c s z' still didn't have their accents.
Next I've exported document to pdf and tried to print from kpdf - no luck
also - on screen everything looks ok, but on paper fails. So I've checked
what happens when importing pdf version to GIMP using 600 DPI and final
picture was without accents. Next I've checked other fonts in document
FreeSans and FreeSerif - didn't helped - same error. So finally I've
downgraded 8.15.1.dfsg.1-2 from 'testing' and with this version everything
works fine.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)

Versions of packages gs-esp depends on:
ii  gs-common   0.3.9Common files for different Ghostsc
ii  libc6   2.3.6-16 GNU C Library: Shared libraries
ii  libcupsimage2   1.2.2-1  Common UNIX Printing System(tm) - 
ii  libcupsys2  1.2.2-1  Common UNIX Printing System(tm) - 
ii  libice6 1:1.0.0-3X11 Inter-Client Exchange library
ii  libjpeg62   6b-13The Independent JPEG Group's JPEG 
ii  libpaper1   1.1.19   Library for handling paper charact
ii  libpng12-0  1.2.8rel-5.2 PNG library - runtime
ii  libsm6  1:1.0.0-4X11 Session Management library
ii  libstdc++6  4.1.1-10 The GNU Standard C++ Library v3
ii  libtiff43.8.2-6  Tag Image File Format (TIFF) libra
ii  libx11-62:1.0.0-7X11 client-side library
ii  libxext61:1.0.0-4X11 miscellaneous extension librar
ii  libxt6  1:1.0.0-5X11 toolkit intrinsics library
ii  zlib1g  1:1.2.3-13   compression library - runtime

Versions of packages gs-esp recommends:
ii  gsfonts   8.14+v8.11+urw-0.2 Fonts for the Ghostscript interpre
ii  psfontmgr 0.11.10PostScript font manager -- part of

-- no debconf information

---End Message---
---BeginMessage---
Source: gs-esp
Source-Version: 8.15.2.dfsg.1-2

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

gs-esp_8.15.2.dfsg.1-2.diff.gz
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-2.diff.gz
gs-esp_8.15.2.dfsg.1-2.dsc
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-2.dsc
gs-esp_8.15.2.dfsg.1-2_i386.deb
  to pool/main/g/gs-esp/gs-esp_8.15.2.dfsg.1-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.
Kenshi Muto [EMAIL PROTECTED] (supplier of updated gs-esp 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.7
Date: Thu, 10 Aug 2006 18:33:07 +0900
Source: gs-esp
Binary: gs-esp
Architecture: source i386
Version: 8.15.2.dfsg.1-2
Distribution: unstable
Urgency: medium
Maintainer: Masayuki Hatta (mhatta) [EMAIL PROTECTED]
Changed-By: Kenshi Muto [EMAIL PROTECTED]
Description: 
 gs-esp - The Ghostscript PostScript interpreter - ESP version
Closes: 381386 382250
Changes: 
 gs-esp (8.15.2.dfsg.1-2) unstable; urgency=medium
 .
   [Kenshi Muto]
   * gs-cjk-resource still needs for CJK people.
 Revert a dependency.
   * Apply revert patch 166:164. Upsream CJK patch broke umlaute.

Bug#383859: Failed to install nullmailer 1:1.0.3-2

[Norbert Tretkowski]

* Kanru Chen wrote:
 ++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/nullmailer.postinst 
 configure 1:1.02-8
 dpkg: error processing nullmailer (--configure):
  subprocess post-installation script returned error exit status 128
 Errors were encountered while processing:
  nullmailer

So it's /usr/share/debconf/frontend which fails, but I have no idea
why.

Norbert


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

Processed: tagging 383304

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 tags 383304 sid
Bug#383304: python-dispatch: Must be updated for python 2.4
There were no tags set.
Tags added: sid


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: tagging 383331

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 tags 383331 sid
Bug#383331: omniidl4 uninstallable due to python transition
There were no tags set.
Tags added: sid


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: tagging 381818

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 tags 381818 sid
Bug#381818: Uninstallable due to unmet dep on pike7.6-core (= 7.6.75-99)
There were no tags set.
Tags added: sid


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: tagging 383830

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 tags 383830 sid
Bug#383830: mapserver: FTBFS: build-dep on missing libgdal1-1.3.2-dev
There were no tags set.
Tags added: sid


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#383449: marked as done (acpi-support: Missing dependency on libc6)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 03:02:08 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383449: fixed in acpi-support 0.86-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: acpi-support
Version: 0.84-1
Severity: serious
Justification: Policy 3.5
Tags: patch

acpi-support ships a dynamically linked binary (acpi_fakekey) which
needs libc6 to run, but the package is missing a proper dependency on
libc6.

This happens because dh_shlibdeps and ${shlibs:Depends} are not used
in debian/rules and debian/control.

The attached patch fixes this.

Cheers,
Christian Aichinger
diff -Nur acpi-support-0.84.orig/debian/control acpi-support-0.84/debian/control
--- acpi-support-0.84.orig/debian/control   2006-08-17 12:34:20.0 
+0200
+++ acpi-support-0.84/debian/control2006-08-17 12:33:18.0 +0200
@@ -7,7 +7,7 @@
 
 Package: acpi-support
 Architecture: i386 amd64 ia64
-Depends: xbase-clients, acpid (= 1.0.4), hdparm, lsb-base (= 1.3-9), 
${arch:Depends}, finger, powermgmt-base, laptop-detect, dmidecode (= 2.7-1)
+Depends: xbase-clients, acpid (= 1.0.4), hdparm, lsb-base (= 1.3-9), 
${arch:Depends}, finger, powermgmt-base, laptop-detect, dmidecode (= 2.7-1), 
${shlibs:Depends}
 Recommends: laptop-mode-tools
 Description: a collection of useful events for acpi
  The scripts included in acpi-support include events for lid closure
diff -Nur acpi-support-0.84.orig/debian/rules acpi-support-0.84/debian/rules
--- acpi-support-0.84.orig/debian/rules 2006-08-17 12:34:20.0 +0200
+++ acpi-support-0.84/debian/rules  2006-08-17 12:33:41.0 +0200
@@ -57,6 +57,7 @@
dh_compress
dh_fixperms
dh_installdeb
+   dh_shlibdeps
dh_gencontrol -- $(arch-depends)
dh_md5sums
dh_builddeb


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: acpi-support
Source-Version: 0.86-1

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

acpi-support_0.86-1.diff.gz
  to pool/main/a/acpi-support/acpi-support_0.86-1.diff.gz
acpi-support_0.86-1.dsc
  to pool/main/a/acpi-support/acpi-support_0.86-1.dsc
acpi-support_0.86-1_i386.deb
  to pool/main/a/acpi-support/acpi-support_0.86-1_i386.deb
acpi-support_0.86.orig.tar.gz
  to pool/main/a/acpi-support/acpi-support_0.86.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.
Raphael Hertzog [EMAIL PROTECTED] (supplier of updated acpi-support 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.7
Date: Sun, 20 Aug 2006 10:43:59 +0200
Source: acpi-support
Binary: acpi-support
Architecture: source i386
Version: 0.86-1
Distribution: unstable
Urgency: low
Maintainer: Raphael Hertzog [EMAIL PROTECTED]
Changed-By: Raphael Hertzog [EMAIL PROTECTED]
Description: 
 acpi-support - scripts for handling many ACPI events
Closes: 381219 383326 383449 383691
Changes: 
 acpi-support (0.86-1) unstable; urgency=low
 .
   * New upstream version (from Ubuntu Edgy).
 * 0.86: Remove stop links from rc0 and rc6
 * 0.85: Don't unload nsc-ircc on suspend
   * Add ${shlibs:Depends} and call to dh_shlibdeps. Closes: #383449
   * 855resolution is no more in Debian, replaced by 915resolution.
 Closes: #381219
   * Improved description, thanks to Clément Stenac. Closes: #383691
   * Removed README.toshiba which doesn't apply to Debian (or which doesn't
 apply any more, the toshiba_acpi option indicated doesn't exist in
 2.6.17.7). Closes: #383326
Files: 
 2bd5fe6ec15966c050a28cce595b33d0 657 admin optional acpi-support_0.86-1.dsc
 cc35bcf88fc772d5636227cf236c749b 26859 admin optional 
acpi-support_0.86.orig.tar.gz
 ffba467dd70d72ad8b65022ae5f053ab 10302 admin optional 
acpi-support_0.86-1.diff.gz
 fea04965c19919d85a7e1cdb79118483 31076 admin optional 
acpi-support_0.86-1_i386.deb

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

iD8DBQFE6C6fvPbGD26BadIRAo2UAJ4g60mXEMAyZF385Xqan2f21/dY4ACdF3G+
xwcrolYYq/gPqiMS6I0GYL4=
=wWvA
-END PGP 

Processed: reassign 383426 to omniidl4, merging 383331 383426

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 reassign 383426 omniidl4
Bug#383426: omnievents: FTBFS: build-depends on python  2.4
Bug reassigned from package `omnievents' to `omniidl4'.

 merge 383331 383426
Bug#383331: omniidl4 uninstallable due to python transition
Bug#383426: omnievents: FTBFS: build-depends on python  2.4
Mismatch - only Bugs in same state can be merged:
Values for `severity' don't match:
 #383331 has `grave';
 #383426 has `serious'
Values for `blocks' don't match:
 #383331 has `380084';
 #383426 has `'


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: tagging 383279

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 tags 383279 sid
Bug#383279: depends: python2.3
There were no tags set.
Tags added: sid


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#376771: remove unused 2.4 images

[maximilian attems]

On Sun, Aug 20, 2006 at 04:12:06AM +0200, Jeroen van Wolffelaar wrote:
 On Fri, Aug 18, 2006 at 06:55:26PM +0200, maximilian attems wrote:
  retitle 376771 RM: kernel-image-2.4.27-2-* -- RoM
  thanks
  
  in accordance with the d-i team any 2.4 kernel-image package
  can be removed from unstable for all archs except
  i386 and m68k (both legacy archs :-P)
  
  this includes the following list of kernel-images:
  Package kernel-image-2.4.27-2-s390
  Package kernel-image-2.4.27-2-s390-di
  Package kernel-image-2.4.27-2-s390-tape
  Package kernel-image-2.4.27-2-s390-tape-di
  Package kernel-image-2.4.27-2-s390x
  Package kernel-image-2.4.27-2-sparc32
  Package kernel-image-2.4.27-2-sparc32-di
  Package kernel-image-2.4.27-2-sparc32-smp
  Package kernel-image-2.4.27-2-sparc64
  Package kernel-image-2.4.27-2-sparc64-di
  Package kernel-image-2.4.27-2-sparc64-smp
  Package kernel-image-2.4.27-bast
  Package kernel-image-2.4.27-bast-di
  Package kernel-image-2.4.27-lart
  Package kernel-image-2.4.27-lart-di
  Package kernel-image-2.4.27-netwinder
  Package kernel-image-2.4.27-netwinder-di
  Package kernel-image-2.4.27-r3k-kn02
  Package kernel-image-2.4.27-r3k-kn02-di
  Package kernel-image-2.4.27-r4k-ip22
  Package kernel-image-2.4.27-r4k-ip22-di
  Package kernel-image-2.4.27-r4k-kn04
  Package kernel-image-2.4.27-r4k-kn04-di
  Package kernel-image-2.4.27-r5k-cobalt
  Package kernel-image-2.4.27-r5k-cobalt-di
  Package kernel-image-2.4.27-r5k-ip22
  Package kernel-image-2.4.27-r5k-ip22-di
  Package kernel-image-2.4.27-r5k-lasat
  Package kernel-image-2.4.27-riscpc
  Package kernel-image-2.4.27-riscstation
  Package kernel-image-2.4.27-sb1-swarm-bn
  Package kernel-image-2.4.27-sb1-swarm-bn-di
  Package kernel-image-2.4.27-xxs1500
  
  
  the following meta packages:
  Package kernel-image-2.4-generic
  Package kernel-image-2.4-s390
  Package kernel-image-2.4-s390x
  Package kernel-image-2.4-smp
  Package kernel-image-2.4-sparc32
  Package kernel-image-2.4-sparc32-smp
  Package kernel-image-2.4-sparc64
  Package kernel-image-2.4-sparc64-smp
 
 I assume this also includes:
 
 kernel-patch-2.4.27-s390 |   2.4.27-2 |  unstable | source, all
 
 the -di packages were already included in #383546, the arm image in
 #383553, and so was the, here unmentioned, arm patch.
 kernel-patch-2.4.27-mips is also not mentioned? And what to do with
 kernel-patch-2.4.27-apus, kernel-patch-2.4-fasttraks150,
 kernel-patch-2.4-grsecurity and kernel-patch-2.4-lowlatency?
 
 
 So, you mention (excluding those packages already removed),
 source-package based:
 kernel-image-2.4.27-s390
 kernel-image-2.4.27-sparc
 kernel-latest-2.4-alpha
 kernel-latest-2.4-s390
 kernel-latest-2.4-sparc
 kernel-patch-2.4.27-mips
 
 I assume you also mean:
 kernel-patch-2.4.27-s390
 kernel-patch-2.4.27-mips 

agreed.
 
 And I have no idea about:
 kernel-patch-2.4.27-apus
ack

 kernel-patch-2.4-fasttraks150
 kernel-patch-2.4-grsecurity
 kernel-patch-2.4-lowlatency
not managed by the kernel team,
will have to go once all 2.4 are gone,
if not agreed by the maintainer as the -grsec flavour.
 
 
 Can you please provide a complete list, or if the original list *was*
 complete, confirm that?

confirming your list,
thanks

-- 
maks


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

Bug#383870: fetchmail: Fetchmail duplicates my SPAM every 10 minutes - ARGH!

[Helge Hafting]

Package: fetchmail
Version: 6.3.4-4
Severity: grave
Justification: renders package unusable

I have been using fetchmail for many years - it runs every 10 minutes
fetching from a few accounts.  The mail is then fed into a local
exim, because I used to have several users on this machine.

Yesterday, I discovered a hundred-doubling of my spam folder,
which was surprising.  Spam tend to increase, but not so abruptly.

Looking at the spam, the same messages repeated over and over.
Completely identical headers, even the message id. At first   
I thought someone had made new spam software with some sort   
of fault in it, but the same messages kept coming back
after I deleted them.

Then I had a look at what fetchmail was doing:


fetchmail -c showed  893 messages waiting for me at the ISP.
Fetchmail started collecting and delivering,
then one of the messages got an error
response because of a malformed address
with spaces in it.  Example:

reading message [EMAIL PROTECTED]:76 of 893 (1523 octets)
..fetchmail: SMTP error: 501 Denver [EMAIL PROTECTED]: @ or .
expected after Denver

There were many of these in addition to normal mail/spam, and after a while
I got:

reading message [EMAIL PROTECTED]:115 of 893 (1672 octets)
fetchmail: SMTP error: 501 Too many syntax or protocol errors
.. flushed
reading message [EMAIL PROTECTED]:116 of 893 (1800 octets)
..fetchmail: SIGPIPE thrown from an MDA or a stream socket error
fetchmail: socket error while fetching from [EMAIL PROTECTED]
fetchmail: Query status=2 (SOCKET)


Fetchmail gave up.  Fine, I tried a
fetchmail -c
and noticed - still 893 messages left!  But I now have many of
them in my spambox.  Every 10 minutes, fetchmail get me 115   
copies of the _same_ spam, then gives up.


Now, I understand that fetchmail don't want to destroy
the faulty messages - there could be something important.

But it _really_ should remove from the server all those
messages that were delivered successfully!  I should not get
the same (successful) spam messages delivered over and over and over!

I have never seen anything like this before, and it is very annoying.
Now, I can set up a client to access that ISP account directly, and  
delete messages on the server.  But that won't help, for surely
I will get more spam with spaces in the TO: field
that will trip up fetchmail again and again.

Is there a solution for this, or will there
be one soon? I'll try other versions of fetchmail
available from debian, of course.

As it is - fetchmail is unuseable because it both fail to fetch 90%
of my mail, _and_ it fills up the disk slowly threatening the system
with a full disk.  Incoming mail service is denied.


Feel free to yell if I am running fetchmail in a stupid way -
there isn't much thought in this setup, but it worked flawlessly
for many years now.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-rc4-mm1
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)

Versions of packages fetchmail depends on:
ii  adduser   3.96   Add and remove users and groups
ii  debianutils   2.17   Miscellaneous utilities specific t
ii  gettext   0.14.6-1   GNU Internationalization utilities
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libssl0.9.8   0.9.8b-2   SSL shared libraries

Versions of packages fetchmail recommends:
ii  ca-certificates   20050804   Common CA Certificates PEM files

-- debconf-show failed


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

Processed: security hole in freetype

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 severity 379920 grave
Bug#379920: freetype: buffer overflow [CVE-2006-3467]
Severity set to `grave' from `important'

 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#383759: Another backtrace

[Robert Millan]

On Sun, Aug 20, 2006 at 01:33:10AM +0300, Yavor Doganov wrote:
 I rebuilt mysql-dfsg-5.0 5.0.22-4 with DEB_BUILD_OPTIONS=nostrip on a
 Pentium IV and installed the unstripped libmysqlclient15off library.
 The backtrace is different:
 
 (gdb) r -C /dev/null -bV
 Starting program: /usr/sbin/exim4 -C /dev/null -bV
 [Thread debugging using libthread_db enabled]
 [New Thread -1486513856 (LWP 7626)]
 
 Program received signal SIGILL, Illegal instruction.
 [Switching to Thread -1486513856 (LWP 7626)]
 0xa7c8bbb0 in TaoCrypt::CpuId () from /usr/lib/libmysqlclient.so.15
 (gdb) bt
 #0  0xa7c8bbb0 in TaoCrypt::CpuId () from /usr/lib/libmysqlclient.so.15
 #1  0xa7c8c82c in TaoCrypt::SetPentiumFunctionPointers ()
from /usr/lib/libmysqlclient.so.15
 #2  0xa7c8c8d5 in __static_initialization_and_destruction_0 ()
from /usr/lib/libmysqlclient.so.15
 #3  0xa7c9a4e2 in __do_global_ctors_aux () from /usr/lib/libmysqlclient.so.15
 #4  0xa7c25e11 in _init () from /usr/lib/libmysqlclient.so.15
 #5  0xa7fa2bd4 in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
 #6  0xa7fa2d11 in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
 #7  0xa7f977ef in ?? () from /lib/ld-linux.so.2
 
 But it really has to be something related to the CPU. The file
 extra/yassl/taocrypt/src/integer.cpp contains some logic about it, but
 I'm not a programmer so I can't figure it out.

It seems that DEB_BUILD_OPTIONS=nostrip didn't suffice.  Perhaps debian/rules
doesn't export a CFLAGS with -g ?

-- 
Robert Millan

My spam trap is [EMAIL PROTECTED]  Note: this address is only intended for
spam harvesters.  Writing to it will get you added to my black list.


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

Bug#383779: marked as done (FTBFS on amd64: not creating PIC code?)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 04:02:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383779: fixed in slang-slirp 1.9.0-1-2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: slang-slirp
Version: 1.9.0-1-1
Severity: serious

slang-slirp doesn't build on amd64, probably because you're not
building PIC code (see policy for more information on this requirement).

| Testing examples/vec ...
| /usr/bin/ld: fvec.o: relocation R_X86_64_32S against `a local symbol'
| can not be used when making a shared object; recompile with -fPIC
| fvec.o: could not read symbols: Bad value
| collect2: ld returned 1 exit status

http://buildd.debian.org/fetch.php?pkg=slang-slirpver=1.9.0-1-1arch=amd64stamp=1155677704file=logas=raw

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

---End Message---
---BeginMessage---
Source: slang-slirp
Source-Version: 1.9.0-1-2

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

slang-slirp_1.9.0-1-2.diff.gz
  to pool/main/s/slang-slirp/slang-slirp_1.9.0-1-2.diff.gz
slang-slirp_1.9.0-1-2.dsc
  to pool/main/s/slang-slirp/slang-slirp_1.9.0-1-2.dsc
slang-slirp_1.9.0-1-2_i386.deb
  to pool/main/s/slang-slirp/slang-slirp_1.9.0-1-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.
Rafael Laboissiere [EMAIL PROTECTED] (supplier of updated slang-slirp 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.7
Date: Sat, 19 Aug 2006 17:11:52 +0200
Source: slang-slirp
Binary: slang-slirp
Architecture: source i386
Version: 1.9.0-1-2
Distribution: unstable
Urgency: low
Maintainer: Debian JED Group [EMAIL PROTECTED]
Changed-By: Rafael Laboissiere [EMAIL PROTECTED]
Description: 
 slang-slirp - C code generator for the S-Lang scripting language
Closes: 383777 383779
Changes: 
 slang-slirp (1.9.0-1-2) unstable; urgency=low
 .
   * debian/rules: Build PIC code (closes: #383777, closes: #383779)
   * debian/patches/clean-config-log.patch: Clean config.log produced by
 configure
Files: 
 dc41d6a3d4748d05adc3636ba9df25fd 726 interpreters optional 
slang-slirp_1.9.0-1-2.dsc
 d96beef2a5526c8baa1e8aac2013264a 5456 interpreters optional 
slang-slirp_1.9.0-1-2.diff.gz
 b513e3c436a82e0b71c4c3f4c8e78c91 234612 interpreters optional 
slang-slirp_1.9.0-1-2_i386.deb

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

iD8DBQFE5y5ck3oga0pdcv4RAsLPAJ90HrDrXrCtu0NcuR/LYKkIbrPhqQCgkCto
PV1PxXaZD0LXx3012yHUNGs=
=shZr
-END PGP SIGNATURE-

---End Message---

Bug#383777: marked as done (FTBFS on 64-bit: Segmentation fault ../../safe_slsh)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 04:02:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383777: fixed in slang-slirp 1.9.0-1-2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: slang-slirp
Version: 1.9.0-1-1
Severity: serious

slang-slirp fails to build on ia64 and alpha with:

Testing examples/vec ...
/bin/sh: line 1: 31862 Segmentation fault  ../../safe_slsh ../../slsh -n 
./test.sl test.out 21
make[4]: *** [test.out] Error 139

http://buildd.debian.org/fetch.php?pkg=slang-slirpver=1.9.0-1-1arch=alphastamp=1155678958file=logas=raw
http://buildd.debian.org/fetch.php?pkg=slang-slirpver=1.9.0-1-1arch=ia64stamp=1155678057file=logas=raw

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

---End Message---
---BeginMessage---
Source: slang-slirp
Source-Version: 1.9.0-1-2

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

slang-slirp_1.9.0-1-2.diff.gz
  to pool/main/s/slang-slirp/slang-slirp_1.9.0-1-2.diff.gz
slang-slirp_1.9.0-1-2.dsc
  to pool/main/s/slang-slirp/slang-slirp_1.9.0-1-2.dsc
slang-slirp_1.9.0-1-2_i386.deb
  to pool/main/s/slang-slirp/slang-slirp_1.9.0-1-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.
Rafael Laboissiere [EMAIL PROTECTED] (supplier of updated slang-slirp 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.7
Date: Sat, 19 Aug 2006 17:11:52 +0200
Source: slang-slirp
Binary: slang-slirp
Architecture: source i386
Version: 1.9.0-1-2
Distribution: unstable
Urgency: low
Maintainer: Debian JED Group [EMAIL PROTECTED]
Changed-By: Rafael Laboissiere [EMAIL PROTECTED]
Description: 
 slang-slirp - C code generator for the S-Lang scripting language
Closes: 383777 383779
Changes: 
 slang-slirp (1.9.0-1-2) unstable; urgency=low
 .
   * debian/rules: Build PIC code (closes: #383777, closes: #383779)
   * debian/patches/clean-config-log.patch: Clean config.log produced by
 configure
Files: 
 dc41d6a3d4748d05adc3636ba9df25fd 726 interpreters optional 
slang-slirp_1.9.0-1-2.dsc
 d96beef2a5526c8baa1e8aac2013264a 5456 interpreters optional 
slang-slirp_1.9.0-1-2.diff.gz
 b513e3c436a82e0b71c4c3f4c8e78c91 234612 interpreters optional 
slang-slirp_1.9.0-1-2_i386.deb

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

iD8DBQFE5y5ck3oga0pdcv4RAsLPAJ90HrDrXrCtu0NcuR/LYKkIbrPhqQCgkCto
PV1PxXaZD0LXx3012yHUNGs=
=shZr
-END PGP SIGNATURE-

---End Message---

Bug#383859: Failed to install nullmailer 1:1.0.3-2

[Kanru Chen]

On Sun, Aug 20, 2006 at 11:16:11AM +0200, Norbert Tretkowski wrote:
 * Kanru Chen wrote:
  ++ exec /usr/share/debconf/frontend /var/lib/dpkg/info/nullmailer.postinst 
  configure 1:1.02-8
  dpkg: error processing nullmailer (--configure):
   subprocess post-installation script returned error exit status 128
  Errors were encountered while processing:
   nullmailer
 
 So it's /usr/share/debconf/frontend which fails, but I have no idea
 why.
 
 Norbert

I found the problem. Actually I have two smarthosts in
/etc/nullmailer/remotes, separated by newlines.

If I remove one of them, the --configure goes without any problem.
According to remotes(5), each line of the file can contain a remote
host.

Regards,
Kanru
-- 
~Kanru Chen [EMAIL PROTECTED]
   'v'   http://stu.csie.ncnu.edu.tw/~kanru.96/
  // \\  GnuPG-Key ID: 365CC7A2
 /(   )\ Fingerprint: 3278 DFB4 BB28 6E8C 9E1F  1ECB B1B7 5B5F 365C C7A2
  ^`~'^


signature.asc
Description: Digital signature

Bug#383493: Please create /usr/local/etc directory in base-files postinst

[Santiago Vila]

This will be fixed in base-files 3.1.15.

Thanks a lot for the report.


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

Bug#383779: FTBFS on amd64: not creating PIC code?

[Kurt Roeckx]

found 383779 1.9.0-1-3
thanks

It's still failing to build with the same error.


Kurt



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

Bug#383555: Not working

[Patrick Matthäi]

I tried your tips with update-initramfs, now the modules will be loaded 
at booting my system, but I still get this warnings/errors.



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

Processed: Re: FTBFS on amd64: not creating PIC code?

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 found 383779 1.9.0-1-3
Bug#383779: FTBFS on amd64: not creating PIC code?
Bug marked as found in version 1.9.0-1-3.

 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#383493: marked as done (Please create /usr/local/etc directory in base-files postinst)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 04:17:03 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383493: fixed in base-files 3.1.15
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: base-files
Version: 3.1.14
Severity: important

Hello,

The FHS seems to require the existence of a directory /usr/local/etc - see
http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#USRLOCALLOCALHIERARCHY
(N.B. this is also permitted to be a symlink to a directory /etc/local
but I wouldn't recommend this because it might conceivably confuse GNU
stow, and people can always make this modification on their own systems
if they wish.)

Since base-files is responsible for creating all the other subdirs of
/usr/local in its postinst, it stands to reason that it should create
this one as well.

This has been requested in the real world, not just as an FHS
compatibility nitpick - see
http://lists.debian.org/debian-devel/2006/08/msg00796.html

A strict reading of the bug severity definitions would make this a
severity serious bug since it's an FHS must, but I don't want to
interfere with any release plans so I'm filing it as important.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-3-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages base-files depends on:
ii  base-passwd   3.5.11 Debian base system master password
ii  mawk [awk]1.3.3-11   a pattern scanning and text proces

base-files recommends no packages.

-- no debconf information

best regards,

-- 
Kevin B. McCarty [EMAIL PROTECTED]   Physics Department
WWW: http://www.princeton.edu/~kmccarty/Princeton University
GPG: public key ID 4F83C751 Princeton, NJ 08544

---End Message---
---BeginMessage---
Source: base-files
Source-Version: 3.1.15

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

base-files_3.1.15.dsc
  to pool/main/b/base-files/base-files_3.1.15.dsc
base-files_3.1.15.tar.gz
  to pool/main/b/base-files/base-files_3.1.15.tar.gz
base-files_3.1.15_powerpc.deb
  to pool/main/b/base-files/base-files_3.1.15_powerpc.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.
Santiago Vila [EMAIL PROTECTED] (supplier of updated base-files 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.7
Date: Sun, 20 Aug 2006 12:44:00 +0200
Source: base-files
Binary: base-files
Architecture: source powerpc
Version: 3.1.15
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila [EMAIL PROTECTED]
Changed-By: Santiago Vila [EMAIL PROTECTED]
Description: 
 base-files - Debian base system miscellaneous files
Closes: 383493
Changes: 
 base-files (3.1.15) unstable; urgency=low
 .
   * Added /usr/local/etc, required by FHS (Closes: #383493).
 [ As usual, please note that this will only affect new installs ].
 This directory is also allowed to be a symlink to /etc/local, but that's
 a decision to be made by the end user after installing the system.
   * Standards-Version: 3.7.2.
Files: 
 2c5d77e100114f806bc32e115e097b70 466 admin required base-files_3.1.15.dsc
 cb7e4c9e81433c27c681a27581f41956 35548 admin required base-files_3.1.15.tar.gz
 59ced4577ec24f44ac7d76dbfbe9557d 34306 admin required 
base-files_3.1.15_powerpc.deb

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

iD8DBQFE6EBHd9Uuvj7yPNYRApMEAKCRcYiACpsqz2bJPrLQzKdEOqSfFQCfUAbs
CZwHP46l7Yr31QxFbff/KVw=
=ClUr
-END PGP SIGNATURE-

---End Message---

Processed: Re: Bug#383859: Failed to install nullmailer 1:1.0.3-2

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 tags 383859 -unreproducible
Bug#383859: Failed to install nullmailer 1:1.0.3-2
Tags were: moreinfo unreproducible
Tags removed: unreproducible

 tags 383859 -moreinfo
Bug#383859: Failed to install nullmailer 1:1.0.3-2
Tags were: moreinfo
Tags removed: moreinfo

 tags 383859 +confirmed
Bug#383859: Failed to install nullmailer 1:1.0.3-2
There were no tags set.
Tags added: confirmed

 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#383859: Failed to install nullmailer 1:1.0.3-2

[Norbert Tretkowski]

tags 383859 -unreproducible
tags 383859 -moreinfo
tags 383859 +confirmed
thanks

* Kanru Chen wrote:
 I found the problem. Actually I have two smarthosts in
 /etc/nullmailer/remotes, separated by newlines.
 
 If I remove one of them, the --configure goes without any problem.
 According to remotes(5), each line of the file can contain a remote
 host.

Okay, then we have indeed a bug in the debconf configuration of
nullmailer. I hope I'll find time to fix it within the next two days
before going on vacation until the rest of the month.

Thanks!

Norbert


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

Bug#379200: marked as done (bluez-utils: FTBFS because sudo clears the environment)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 05:47:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#379200: fixed in bluez-utils 3.1-4
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: bluez-utils
Version: 3.1-2
Severity: serious
Tags: patch

Hello.

Some of our autobuilders do use sudo instead of fakeroot to build the
package. For some months now, the sudo package clears the environment,
so you can't use variables from the environment in debian/rules anymore.

PWD is such as environment variable; the common solution to this (common
;-) problem is to use CURDIR instead, which is a make var, not an env
var.

I'm pretty confident the attached patch will solve the issue, but it'd
be great if you can test yourself, by reproducing the problem first, and
applying the patch afterwards.

BTW, please use urgency=high for the following bluez-utils uploads that
fix RC bugs.

Thanks,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
Listening to: Estopa - Exiliado en el lavabo
--- rules~  2006-07-22 07:09:20.0 +0200
+++ rules   2006-07-22 07:09:13.0 +0200
@@ -12,7 +12,7 @@
 # FIXME test --enable-alsa
 # removed --enable-pcmcia --enable-dbus
 DEB_CONFIGURE_EXTRA_FLAGS := --disable-initscripts --enable-obex --enable-cups 
--enable-hid2hci --enable-bcm203x
-DEB_DESTDIR := $(PWD)/debian/tmp
+DEB_DESTDIR := $(CURDIR)/debian/tmp
 
 install/bluez-utils::
# modutils config file
@@ -32,7 +32,7 @@
install -D -m 0644 debian/lintian-overrides \
$(DEB_DESTDIR)/usr/share/lintian/overrides/bluez-utils

-   install -m 0644 $(PWD)/hcid/passkey-agent 
$(DEB_DESTDIR)/usr/bin/passkey-agent
+   install -m 0644 $(CURDIR)/hcid/passkey-agent 
$(DEB_DESTDIR)/usr/bin/passkey-agent
 
# have a sensible pin default, the upstream one 'BlueZ'
# cannot be typed on a phone keypad!
@@ -40,7 +40,7 @@
 
 binary-install/bluez-pcmcia-support::
#chmod a+x $(DEB_DESTDIR)/etc/pcmcia/bluetooth
-   chmod a+x $(PWD)/debian/bluez-pcmcia-support/lib/udev/bluetooth.sh
+   chmod a+x $(CURDIR)/debian/bluez-pcmcia-support/lib/udev/bluetooth.sh
 
 install/bluez-bcm203x::
mkdir -p $(DEB_DESTDIR)/usr/lib/bluez-bcm203x
---End Message---
---BeginMessage---
Source: bluez-utils
Source-Version: 3.1-4

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

bluetooth_3.1-4_all.deb
  to pool/main/b/bluez-utils/bluetooth_3.1-4_all.deb
bluez-bcm203x_3.1-4_powerpc.deb
  to pool/contrib/b/bluez-utils/bluez-bcm203x_3.1-4_powerpc.deb
bluez-cups_3.1-4_powerpc.deb
  to pool/main/b/bluez-utils/bluez-cups_3.1-4_powerpc.deb
bluez-pcmcia-support_3.1-4_powerpc.deb
  to pool/main/b/bluez-utils/bluez-pcmcia-support_3.1-4_powerpc.deb
bluez-utils_3.1-4.diff.gz
  to pool/main/b/bluez-utils/bluez-utils_3.1-4.diff.gz
bluez-utils_3.1-4.dsc
  to pool/main/b/bluez-utils/bluez-utils_3.1-4.dsc
bluez-utils_3.1-4_powerpc.deb
  to pool/main/b/bluez-utils/bluez-utils_3.1-4_powerpc.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.
Filippo Giunchedi [EMAIL PROTECTED] (supplier of updated bluez-utils 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.7
Date: Sun, 20 Aug 2006 14:18:19 +0200
Source: bluez-utils
Binary: bluez-pcmcia-support bluetooth bluez-bcm203x bluez-cups bluez-utils
Architecture: source powerpc all
Version: 3.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Bluetooth Maintainers [EMAIL PROTECTED]
Changed-By: Filippo Giunchedi [EMAIL PROTECTED]
Description: 
 bluetooth  - Bluetooth stack utilities
 bluez-bcm203x - Firmware loader for Broadcom 203x based Bluetooth devices
 bluez-cups - Bluetooth printer driver for CUPS
 bluez-pcmcia-support - PCMCIA support files for BlueZ 2.0 Bluetooth tools
 bluez-utils - Bluetooth tools and daemons
Closes: 379200 380283 380452 381582 382791 383188 383783
Changes: 
 

Bug#383498: marked as done (totem: Eats up all available memory(!))

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 14:02:29 +0100
with message-id [EMAIL PROTECTED]
and subject line Fixed in experimental
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: totem
Version: 1.4.4-1
Severity: serious

 1. Play an audio file with totem
 2. Press 0 or 1 on the keyboard, or pick one of the 'view - fit window to
movie' options
 3. Although the audio continues to play, Totem stops responding to input and
starts guzzling memory. top reports its RSS as 1.3 GB before X gets
swapped out and the screen stops updating.

I hope this is reproducible on your machines. :)

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages totem depends on:
ii  totem-xine1.4.4-1A simple media player for the Gnom

totem recommends no packages.

-- debconf information:
* totem/thumbnailer: true

---End Message---
---BeginMessage---
version: 1.5.91-2

Seems to be fixed in the 1.5 series.
---End Message---

Processed: Patch to use python-central in memaid-pyqt

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 severity 380869 serious
Bug#380869: Python transition (#2): you are building a private python module !
Severity set to `serious' from `important'

 tags 380869 + patch
Bug#380869: Python transition (#2): you are building a private python module !
There were no tags set.
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#383555: marked as done (udev 0.097 broken by klibc-utils nuke = 1.4.19-1)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 06:17:31 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383555: fixed in udev 0.097-2
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: udev
Version: 0.097-1
Severity: grave

I use a initrd enabled kernel. After the upgrade I get the following
error messages during bootup (when the initrd is loaded and started):

udevd[...]: lookup_group error resolving group 'audio': Illegal seek
- there are lots of these messages for all sorts of groups and users -
vol_id[...]: lookup_group error resolving group nogroup: No such file or
directory
vol_id[...]: lookup_user error resolving group nobody: No such file or
directory
- These message are also repeated several times -

udevd fails to start and I get a static /dev with some other warnings
(iirc /dev/shm being ro)

If I boot the same system with a non-initrd kernel, everything works
fine.

As the standard Debian kernel is an initrd-kernel I set the severity to
grave as the majority of the users will be affected by this bug.
If you need additional infos please let me know.

Cheers,
Michael


-- Package-specific info:
-- /etc/udev/rules.d/:
/etc/udev/rules.d/:
insgesamt 8
lrwxrwxrwx 1 root root  20 2005-04-10 20:48 020_permissions.rules - 
../permissions.rules
lrwxrwxrwx 1 root root  19 2005-10-12 03:00 025_libgphoto2.rules - 
../libgphoto2.rules
lrwxrwxrwx 1 root root  16 2006-08-04 03:22 025_libsane.rules - 
../libsane.rules
lrwxrwxrwx 1 root root  22 2005-11-18 03:39 025_logitechmouse.rules - 
../logitechmouse.rules
lrwxrwxrwx 1 root root  13 2005-11-07 03:11 030_capi.rules - ../capi.rules
lrwxrwxrwx 1 root root  24 2006-07-17 02:49 030_sl-modem-daemon.rules - 
../sl-modem-daemon.rules
lrwxrwxrwx 1 root root  15 2006-01-26 01:46 85-pcmcia.rules - ../pcmcia.rules
lrwxrwxrwx 1 root root  15 2006-07-17 02:45 libnjb.rules - ../libnjb.rules
lrwxrwxrwx 1 root root  13 2004-04-01 00:34 udev.rules - ../udev.rules
lrwxrwxrwx 1 root root  13 2006-06-13 18:18 z10_icdu.rules - ../icdu.rules
lrwxrwxrwx 1 root root  25 2006-03-28 01:38 z20_persistent-input.rules - 
../persistent-input.rules
lrwxrwxrwx 1 root root  19 2005-08-15 01:04 z20_persistent.rules - 
../persistent.rules
-rw-r--r-- 1 root root 543 2006-08-18 01:11 z25_persistent-cd.rules
-rw-r--r-- 1 root root 450 2006-04-22 04:13 z25_persistent-net.rules
lrwxrwxrwx 1 root root  33 2006-04-20 00:35 z45_persistent-net-generator.rules 
- ../persistent-net-generator.rules
lrwxrwxrwx 1 root root  12 2005-07-03 22:39 z50_run.rules - ../run.rules
lrwxrwxrwx 1 root root  16 2005-10-09 21:27 z55_hotplug.rules - 
../hotplug.rules
lrwxrwxrwx 1 root root  19 2005-08-02 22:57 z60_alsa-utils.rules - 
../alsa-utils.rules
lrwxrwxrwx 1 root root  15 2005-09-20 00:37 z60_hdparm.rules - ../hdparm.rules
lrwxrwxrwx 1 root root  33 2006-05-06 01:19 z60_xserver-xorg-input-wacom.rules 
- ../xserver-xorg-input-wacom.rules
lrwxrwxrwx 1 root root  29 2006-08-18 00:59 z75_cd-aliases-generator.rules - 
../cd-aliases-generator.rules
lrwxrwxrwx 1 root root  12 2006-08-16 11:58 z99_hal.rules - ../hal.rules

-- /sys/:
/sys/block/hda/dev
/sys/block/hda/hda10/dev
/sys/block/hda/hda1/dev
/sys/block/hda/hda2/dev
/sys/block/hda/hda3/dev
/sys/block/hda/hda5/dev
/sys/block/hda/hda6/dev
/sys/block/hda/hda7/dev
/sys/block/hda/hda8/dev
/sys/block/hda/hda9/dev
/sys/block/hdc/dev
/sys/block/ram0/dev
/sys/block/ram10/dev
/sys/block/ram11/dev
/sys/block/ram12/dev
/sys/block/ram13/dev
/sys/block/ram14/dev
/sys/block/ram15/dev
/sys/block/ram1/dev
/sys/block/ram2/dev
/sys/block/ram3/dev
/sys/block/ram4/dev
/sys/block/ram5/dev
/sys/block/ram6/dev
/sys/block/ram7/dev
/sys/block/ram8/dev
/sys/block/ram9/dev
/sys/class/capi/capi/dev
/sys/class/drm/card0/dev
/sys/class/graphics/fb0/dev
/sys/class/input/input0/event0/dev
/sys/class/input/input1/event1/dev
/sys/class/input/input2/event2/dev
/sys/class/input/input2/mouse0/dev
/sys/class/input/input2/ts0/dev
/sys/class/input/input3/event3/dev
/sys/class/input/input3/mouse1/dev
/sys/class/input/input3/ts1/dev
/sys/class/input/mice/dev
/sys/class/misc/agpgart/dev
/sys/class/misc/device-mapper/dev
/sys/class/misc/psaux/dev
/sys/class/misc/snapshot/dev
/sys/class/ppdev/parport0/dev
/sys/class/ppp/ppp/dev
/sys/class/printer/lp0/dev
/sys/class/sound/adsp/dev
/sys/class/sound/audio/dev
/sys/class/sound/controlC0/dev
/sys/class/sound/dsp/dev
/sys/class/sound/mixer/dev
/sys/class/sound/pcmC0D0c/dev
/sys/class/sound/pcmC0D0p/dev
/sys/class/sound/pcmC0D1c/dev
/sys/class/sound/pcmC0D2c/dev

Processed: Re: [Pkg-jed-sl-modules] Bug#383779: FTBFS on amd64: not creating PIC code?

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 package slang-slirp
Ignoring bugs not assigned to: slang-slirp

 tags 383779 confirmed
Bug#383779: FTBFS on amd64: not creating PIC code?
There were no tags set.
Tags added: confirmed

 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#383888: vtk failed to build from sources

[xavier . gnata]

Subject: vtk failed to build from sources
Package: vtk
Severity: serious

*** Please type your report below this line ***

debuild fails after apt-get source vtk on a up to date sid (whereas 
/usr/lib/pbuilder/pbuilder-satisfydepends says all the build dependances are
installed.)
Here is debuild log :

-- Found JPEG: /usr/lib/libjpeg.so
CMake Error: Attempt to add link target vtkCommonPython of type: MODULE_LIBRARY
to target vtkFilteringPython. You can only link to STATIC or SHARED libraries.
To allow linking of modules set CMAKE_BACKWARDS_COMPATIBILITY to 2.2 or lower

CMake Error: Attempt to add link target vtkFilteringPython of type:
MODULE_LIBRARY
to target vtkImagingPython. You can only link to STATIC or SHARED libraries.
To allow linking of modules set CMAKE_BACKWARDS_COMPATIBILITY to 2.2 or lower

CMake Error: Attempt to add link target vtkFilteringPython of type:
MODULE_LIBRARY
to target vtkGraphicsPython. You can only link to STATIC or SHARED libraries.
To allow linking of modules set CMAKE_BACKWARDS_COMPATIBILITY to 2.2 or lower

CMake Error: Attempt to add link target vtkFilteringPython of type:
MODULE_LIBRARY
to target vtkIOPython. You can only link to STATIC or SHARED libraries.
To allow linking of modules set CMAKE_BACKWARDS_COMPATIBILITY to 2.2 or lower

CMake Error: Attempt to add link target vtkGraphicsPython of type:
MODULE_LIBRARY
to target vtkRenderingPython. You can only link to STATIC or SHARED libraries.
To allow linking of modules set CMAKE_BACKWARDS_COMPATIBILITY to 2.2 or lower

CMake Error: Attempt to add link target vtkImagingPython of type: MODULE_LIBRARY
to target vtkRenderingPython. You can only link to STATIC or SHARED libraries.
To allow linking of modules set CMAKE_BACKWARDS_COMPATIBILITY to 2.2 or lower

CMake Error: Attempt to add link target vtkRenderingPython of type:
MODULE_LIBRARY
to target vtkHybridPython. You can only link to STATIC or SHARED libraries.
To allow linking of modules set CMAKE_BACKWARDS_COMPATIBILITY to 2.2 or lower

CMake Error: Attempt to add link target vtkIOPython of type: MODULE_LIBRARY
to target vtkHybridPython. You can only link to STATIC or SHARED libraries.
To allow linking of modules set CMAKE_BACKWARDS_COMPATIBILITY to 2.2 or lower

CMake Error: Attempt to add link target vtkRenderingPython of type:
MODULE_LIBRARY
to target vtkParallelPython. You can only link to STATIC or SHARED libraries.
To allow linking of modules set CMAKE_BACKWARDS_COMPATIBILITY to 2.2 or lower

CMake Error: Attempt to add link target vtkIOPython of type: MODULE_LIBRARY
to target vtkParallelPython. You can only link to STATIC or SHARED libraries.
To allow linking of modules set CMAKE_BACKWARDS_COMPATIBILITY to 2.2 or lower

-- Configuring done
make: *** [configure-stamp] Error 255
debuild: fatal error at line 1224:
debian/rules build failed


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-rc4-2
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Bug#367221: marked as done (quodlibet: fails to find module pygst)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 06:32:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#367221: fixed in quodlibet 0.23-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: quodlibet
Version: 0.18-3
Severity: grave
Justification: renders package unusable

The package, installed with aptitude on a etch system,  fails to start with 
the following message :

$ quodlibet 
Traceback (most recent call last):
  File /usr/bin/quodlibet, line 310, in ?
import pygst
ImportError: No module named pygst


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages quodlibet depends on:
ii  exfalso   0.18-3 audio tag editor for GTK+
ii  gstreamer0.10-plugins-base0.10.5-1   GStreamer plugins from the base 
ii  gstreamer0.10-plugins-good0.10.2-1   GStreamer plugins from the good 
ii  gstreamer0.10-plugins-ugly0.10.3-1   GStreamer plugins from the ugly 
ii  python2.3.5-5An interactive high-level object-o
ii  python-gst0.100.10.2-1   generic media-playing framework (P

Versions of packages quodlibet recommends:
ii  gstreamer0.10-alsa0.10.5-1   GStreamer plugin for ALSA
ii  gstreamer0.10-gnomevfs0.10.5-1   GStreamer plugin for GnomeVFS
ii  python-feedparser 4.1-2  Universal Feed Parser for Python
ii  quodlibet-ext 0.18-3 extensions for the Quod Libet audi

-- no debconf information

---End Message---
---BeginMessage---
Source: quodlibet
Source-Version: 0.23-1

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

exfalso_0.23-1_all.deb
  to pool/main/q/quodlibet/exfalso_0.23-1_all.deb
quodlibet-ext_0.23-1_amd64.deb
  to pool/main/q/quodlibet/quodlibet-ext_0.23-1_amd64.deb
quodlibet_0.23-1.diff.gz
  to pool/main/q/quodlibet/quodlibet_0.23-1.diff.gz
quodlibet_0.23-1.dsc
  to pool/main/q/quodlibet/quodlibet_0.23-1.dsc
quodlibet_0.23-1_all.deb
  to pool/main/q/quodlibet/quodlibet_0.23-1_all.deb
quodlibet_0.23.orig.tar.gz
  to pool/main/q/quodlibet/quodlibet_0.23.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.
Tristan Seligmann [EMAIL PROTECTED] (supplier of updated quodlibet 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.7
Date: Fri, 18 Aug 2006 01:30:25 +0200
Source: quodlibet
Binary: quodlibet exfalso quodlibet-ext
Architecture: source amd64 all
Version: 0.23-1
Distribution: unstable
Urgency: low
Maintainer: Tristan Seligmann [EMAIL PROTECTED]
Changed-By: Tristan Seligmann [EMAIL PROTECTED]
Description: 
 exfalso- audio tag editor for GTK+
 quodlibet  - audio library manager and player for GTK+
 quodlibet-ext - extensions for the Quod Libet audio player
Closes: 367221 381393
Changes: 
 quodlibet (0.23-1) unstable; urgency=low
 .
   * New upstream release.
 - Version number is correct (closes: #381393).
   * Change dependencies to use python2.4-foo, as we are using a non-default
 python version (closes: #367221).
Files: 
 9002afd04952514d746aff7aef5179b5 775 sound optional quodlibet_0.23-1.dsc
 195c39433b4e2a5bf930af7570b61f3e 551773 sound optional 
quodlibet_0.23.orig.tar.gz
 ae3bc8575a248ab1accd50c3cb81c701 6766 sound optional quodlibet_0.23-1.diff.gz
 079823663f545409b9248fd922723318 458650 sound optional exfalso_0.23-1_all.deb
 b1e49e3c442764a2336f8687607e2e73 30970 sound optional quodlibet_0.23-1_all.deb
 f2507509fd73f992e6f048f9a695ac0d 24860 sound optional 
quodlibet-ext_0.23-1_amd64.deb

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

iD8DBQFE6GHTvJtHM4T7RtYRAspKAKCGPzuFUb0Fu52z2ptqmGaT1xT6FwCgq+WU
Dp57dcjV+6buNPm9xL/gBU0=
=k/Ri
-END PGP SIGNATURE-

---End Message---

Bug#383779: [Pkg-jed-sl-modules] Bug#383779: FTBFS on amd64: not creating PIC code?

[Rafael Laboissiere]

package slang-slirp
tags 383779 confirmed
thanks

* Kurt Roeckx [EMAIL PROTECTED] [2006-08-20 13:32]:

 found 383779 1.9.0-1-3
 thanks
 
 It's still failing to build with the same error.

Indeed.  I thought that #383777 and #383779 were related to each other
and closed both of them in slang-slirp_1.9.0-1-2.  I will investigate the
problem.

-- 
Rafael


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

Bug#383829: This is a cmake bug

[Damián Viano]

reassign 383829 cmake 2.4.3-1
# set severity to critical since it brake others package(s?)
severity 383829 critical
notfound 383829 2.2.3-1
thanks, control, you are my reassigning bitch ;-p

This is a bug/regression in cmake, as this package compiles fine with
cmake 2.2.3-1. I'll be looking into it and report later today.

Hope to help,

-- 
Damián Viano(Des)  ¯ ¯ - _   _ - ¯ ¯
GPG: 0x6EB95A6F Debian ¯-_GNU_-¯ Linux
Web: http://damianv.com.ar/   ¯-¯


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

Processed: This is a cmake bug

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 reassign 383829 cmake 2.4.3-1
Bug#383829: libapache2-mod-xmlrpc2: FTBFS: missing build-dep ?
Bug reassigned from package `libapache2-mod-xmlrpc2' to `cmake'.

 # set severity to critical since it brake others package(s?)
 severity 383829 critical
Bug#383829: libapache2-mod-xmlrpc2: FTBFS: missing build-dep ?
Severity set to `critical' from `serious'

 notfound 383829 2.2.3-1
Bug#383829: libapache2-mod-xmlrpc2: FTBFS: missing build-dep ?
Bug marked as not found in version 2.2.3-1.

 thanks, control, you are my reassigning bitch ;-p
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#376602: marked as done (RM: g++3-4, libstdc++6-{,4.0-}{dbg,dev,pic}, g++4.0 [hppa] -- RoM; ANAIS)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 07:53:30 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#376602: fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: ftp.debian.org

Please remove the binary packages on hppa, not built anymore because
of a ABI change betweend 4.0 and 4.1.

g++-3.4 libstdc++6-dev libstdc++6-pic libstdc++6-dbg
libstdc++6-4.0-dbg libstdc++6-4.0-pic libstdc++6-4.0-dev g++-4.0

---End Message---
---BeginMessage---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   g++-3.4 |3.4.6-1 | hppa
   g++-4.0 |4.0.3-3 | hppa
libstdc++6-4.0-dbg |4.0.3-3 | hppa
libstdc++6-4.0-dev |4.0.3-3 | hppa
libstdc++6-4.0-pic |4.0.3-3 | hppa
libstdc++6-dbg |3.4.6-1 | hppa
libstdc++6-dev |3.4.6-1 | hppa
libstdc++6-pic |3.4.6-1 | hppa

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

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

Debian distribution maintenance software
pp.
Jeroen van Wolffelaar (the ftpmaster behind the curtain)
---End Message---

Processed: Correct severity/tags

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 tags 378712 =
Bug#378712: RM: zope-ttwtype -- RoM; obsolete
Tags were: patch
Tags set to: 

 severity 378712 normal
Bug#378712: RM: zope-ttwtype -- RoM; obsolete
Severity set to `normal' from `serious'

 severity 382907 normal
Bug#382907: RM: mozilla-locale-fr -- RoM
Severity set to `normal' from `serious'

 --
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#381919: Uploaded

[Margarita Manterola]

I took the liberty of uploading your package, so that the RC bug would be
fixed.

Please, keep an eye on the other important bugs you have.  Some of them
look like they should actually be RC as well

-- 
Love,
Marga


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

Bug#383888: vtk failed to build from sources

[A. Maitland Bottoms]

What version of cmake was pbuilder using?
(Maybe I need to bump up the versioned depends upon cmake.)

I'll try to duplicate this result...

-Maitland


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

Bug#381919: marked as done (segfaults on startup)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 08:17:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381919: fixed in qgo 1.5.1-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: qgo
Version: 1.5-r1-2
Severity: grave

On amd64:

(gdb) r
Starting program: /usr/games/qgo
[Thread debugging using libthread_db enabled]
[New Thread 47153582413040 (LWP 11823)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47153582413040 (LWP 11823)]
0x00483bc0 in myMessageHandler (type=QtDebugMsg,
msg=0x7fffe10446e0 Qt: gdb: -nograb added to command-line options.\n\t Use 
the -dograb option to enforce grabbing.)
at msg_handler.cpp:12
12  case QtDebugMsg:view-append((QString) Debug: 
 + (QString) msg + (QString) \n);
(gdb) bt
#0  0x00483bc0 in myMessageHandler (type=QtDebugMsg,
msg=0x7fffe10446e0 Qt: gdb: -nograb added to command-line options.\n\t Use 
the -dograb option to enforce grabbing.)
at msg_handler.cpp:12
#1  0x2ae2ca37ebd8 in qDebug (
msg=0x2ae2ca449fd8 Qt: gdb: -nograb added to command-line options.\n\t Use 
the -dograb option to enforce grabbing.)
at tools/qglobal.cpp:486
#2  0x2ae2c9fc3802 in qt_init_internal (argcptr=0x7fffe1046d2c, 
argv=0x7fffe1047158, display=0x0, visual=0, colormap=0)
at kernel/qapplication_x11.cpp:1758
#3  0x2ae2c9fc5940 in qt_init (argcptr=0x7fffe1046d2c, argv=0x7fffe1047158) 
at kernel/qapplication_x11.cpp:2385
#4  0x2ae2ca039ed1 in QApplication::construct (this=0x7fffe1046d30, [EMAIL 
PROTECTED], argv=0x7fffe1047158,
type=QApplication::GuiClient) at kernel/qapplication.cpp:813
#5  0x2ae2ca03a1f6 in QApplication (this=0x7fffe1046d30, [EMAIL PROTECTED], 
argv=0x7fffe1047158)
at kernel/qapplication.cpp:728
#6  0x00445725 in main (argc=1, argv=0x7fffe1047158) at main.cpp:94
(gdb)

main.cpp:94 reads:

QApplication myapp(argc, argv);

and AFAICS, argc and argv are perfectly sane.  Perhaps argv[] should be copied
rather than passed as a pointer?

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-amd64-k8
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)

Versions of packages qgo depends on:
ii  libaudio2   1.8-1The Network Audio System (NAS). (s
ii  libc6   2.3.6-15 GNU C Library: Shared libraries
ii  libfontconfig1  2.3.2-7  generic font configuration library
ii  libfreetype62.2.1-2  FreeType 2 font engine, shared lib
ii  libgcc1 1:4.1.1-5GCC support library
ii  libice6 1:1.0.0-3X11 Inter-Client Exchange library
ii  libjpeg62   6b-13The Independent JPEG Group's JPEG 
ii  libpng12-0  1.2.8rel-5.2 PNG library - runtime
ii  libqt3-mt   3:3.3.6-2Qt GUI Library (Threaded runtime v
ii  libsm6  1:1.0.0-4X11 Session Management library
ii  libstdc++6  4.1.1-5  The GNU Standard C++ Library v3
ii  libx11-62:1.0.0-7X11 client-side library
ii  libxcursor1 1.1.5.2-5X cursor management library
ii  libxext61:1.0.0-4X11 miscellaneous extension librar
ii  libxft2 2.1.8.2-8FreeType-based font drawing librar
ii  libxi6  1:1.0.0-5X11 Input extension library
ii  libxinerama11:1.0.1-4X11 Xinerama extension library
ii  libxrandr2  2:1.1.0.2-4  X11 RandR extension library
ii  libxrender1 1:0.9.0.2-4  X Rendering Extension client libra
ii  libxt6  1:1.0.0-5X11 toolkit intrinsics library
ii  zlib1g  1:1.2.3-13   compression library - runtime

qgo recommends no packages.

-- no debconf information

---End Message---
---BeginMessage---
Source: qgo
Source-Version: 1.5.1-1

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

qgo_1.5.1-1.diff.gz
  to pool/main/q/qgo/qgo_1.5.1-1.diff.gz
qgo_1.5.1-1.dsc
  to pool/main/q/qgo/qgo_1.5.1-1.dsc
qgo_1.5.1-1_i386.deb
  to pool/main/q/qgo/qgo_1.5.1-1_i386.deb
qgo_1.5.1.orig.tar.gz
  to pool/main/q/qgo/qgo_1.5.1.orig.tar.gz



A 

Bug#381185: marked as done (RM: amap -- RoM; non-free)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 09:00:17 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#381185: fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: ftp.debian.org
Severity: serious 

Please see bug #346313

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-ck1
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

---End Message---
---BeginMessage---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  amap |4.8-1.1 | source, alpha, amd64, arm, hppa, hurd-i386, i386, 
ia64, m68k, mips, mipsel, powerpc, s390, sparc

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

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

Debian distribution maintenance software
pp.
Jeroen van Wolffelaar (the ftpmaster behind the curtain)
---End Message---

Bug#383772: marked as done (openjade: FTBFS: cmp error, License is not GPL-2)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 10:04:04 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383772: fixed in openjade 1.4devel1-17
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: openjade
Version: 1.4devel1-16
Severity: serious

Hello,

There was a problem while autobuilding your package:

 Automatic build of openjade_1.4devel1-16 on avidan by sbuild/i386 0.49
 Build started at 20060819-1338
 **
...
 make[1]: Leaving directory `/build/buildd/openjade-1.4devel1'
 touch install-stamp
 cmp -s COPYING /usr/share/common-licenses/GPL-2 || \
   (echo License is not GPL-2  false)
 License is not GPL-2
 make: *** [debian/copyright] Error 1
 **
 Build finished at 20060819-1350
 FAILED [dpkg-buildpackage died]
 --

Kinda funny.

-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: openjade
Source-Version: 1.4devel1-17

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

libostyle-dev_1.4devel1-17_i386.deb
  to pool/main/o/openjade/libostyle-dev_1.4devel1-17_i386.deb
libostyle1c2_1.4devel1-17_i386.deb
  to pool/main/o/openjade/libostyle1c2_1.4devel1-17_i386.deb
openjade_1.4devel1-17.diff.gz
  to pool/main/o/openjade/openjade_1.4devel1-17.diff.gz
openjade_1.4devel1-17.dsc
  to pool/main/o/openjade/openjade_1.4devel1-17.dsc
openjade_1.4devel1-17_i386.deb
  to pool/main/o/openjade/openjade_1.4devel1-17_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.
Neil Roeth [EMAIL PROTECTED] (supplier of updated openjade 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.7
Date: Sat, 19 Aug 2006 13:18:11 -0400
Source: openjade
Binary: libostyle-dev libostyle1c2 openjade
Architecture: source i386
Version: 1.4devel1-17
Distribution: unstable
Urgency: low
Maintainer: Neil Roeth [EMAIL PROTECTED]
Changed-By: Neil Roeth [EMAIL PROTECTED]
Description: 
 libostyle-dev - OpenJade libraries, developer support
 libostyle1c2 - Runtime libraries for OpenJade
 openjade   - Implementation of the DSSSL language
Closes: 383772
Changes: 
 openjade (1.4devel1-17) unstable; urgency=low
 .
   * debian/rules: Fix FTBFS, thanks to Julien Danjou (closes: #383772)
Files: 
 9921e35d63299f04c94eb98eb8cb5ec7 673 text optional openjade_1.4devel1-17.dsc
 528a78d9abadbf722a0e878b8a4d73fd 648601 text optional 
openjade_1.4devel1-17.diff.gz
 ea2ffa2220d885b579e486905066080c 344152 text optional 
openjade_1.4devel1-17_i386.deb
 a4a2c422266048e32d34767b71f23c14 786898 libs optional 
libostyle1c2_1.4devel1-17_i386.deb
 053f1072ac2eb6649b43dfeda4e79e53 1030064 libdevel optional 
libostyle-dev_1.4devel1-17_i386.deb

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

iD8DBQFE6EZD6j+skPrutKkRAgo0AJ96wTQK4w0PIO5rvue/BTa2DHhMbgCguV1m
XaXu9B+djOmAuokdmZYCCxw=
=9Stb
-END PGP SIGNATURE-

---End Message---

Bug#383915: libchm-bin: installs binaries into /usr/bin/bin/

[Jirka Novosad]

Package: libchm-bin
Version: 0.38-2
Severity: serious
Justification: Policy 9.1.1

$ dpkg-query --listfiles libchm-bin
/.
/usr
/usr/bin
/usr/bin/bin
/usr/bin/bin/chm_http
/usr/bin/bin/enum_chmLib
/usr/bin/bin/enumdir_chmLib
/usr/bin/bin/extract_chmLib
/usr/bin/bin/test_chmLib
/usr/share
/usr/share/doc
/usr/share/doc/libchm-bin
/usr/share/doc/libchm-bin/copyright
/usr/share/doc/libchm-bin/changelog.Debian.gz
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/chm_http.1.gz
/usr/share/man/man1/enumdir_chmLib.1.gz
/usr/share/man/man1/test_chmLib.1.gz
/usr/share/man/man1/enum_chmLib.1.gz
/usr/share/man/man1/extract_chmLib.1.gz


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-debhome02
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)

Versions of packages libchm-bin depends on:
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libchm1   0.38-2 library for dealing with Microsoft

libchm-bin recommends no packages.

-- no debconf information


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

Bug#382618: marked as done (slat: FTBFS: error: 'perm_datum_t' has no member named 'value')

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 10:47:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382618: fixed in slat 2.0-3
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: slat
Version: 2.0-2
Severity: serious

Hello,

There was a problem while autobuilding your package:

 Automatic build of slat_2.0-2 on avidan by sbuild/i386 0.49
 Build started at 20060812-0518
 **
...
   then mv -f .deps/scanner.Tpo .deps/scanner.Po; else rm -f 
 .deps/scanner.Tpo; exit 1; fi
 if cc -DPACKAGE_NAME=\slat\ -DPACKAGE_TARNAME=\slat\ 
 -DPACKAGE_VERSION=\2.0\ -DPACKAGE_STRING=\slat\ 2.0\ 
 -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\slat\ -DVERSION=\2.0\ 
 -DYYTEXT_POINTER=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
 -DHAVE_SEPOL_POLICYDB_H=1 -DHAVE_POLICYDB_READ=1  -I. -I.-I../../include 
 -O2 -g -MT slat.o -MD -MP -MF .deps/slat.Tpo -c -o slat.o slat.c; \
   then mv -f .deps/slat.Tpo .deps/slat.Po; else rm -f 
 .deps/slat.Tpo; exit 1; fi
 slat.c: In function 'security_contexts':
 slat.c:226: warning: passing argument 1 of 'role_set' from incompatible 
 pointer type
 slat.c:241: warning: passing argument 1 of 'type_set' from incompatible 
 pointer type
 slat.c: In function 'perm_flow_fun':
 slat.c:327: error: 'perm_datum_t' has no member named 'value'
 slat.c: In function 'flow_in_class':
 slat.c:373: error: 'common_datum_t' has no member named 'value'
 slat.c: In function 'constrain':
 slat.c:573: error: 'class_datum_t' has no member named 'value'
 slat.c: In function 'gencommap':
 slat.c:716: error: 'common_datum_t' has no member named 'value'
 slat.c: In function 'genclsmap':
 slat.c:734: error: 'class_datum_t' has no member named 'value'
 slat.c:739: error: 'common_datum_t' has no member named 'value'
 slat.c: In function 'initcom':
 slat.c:834: error: 'common_datum_t' has no member named 'value'
 slat.c: In function 'action':
 slat.c:904: error: 'common_datum_t' has no member named 'value'
 slat.c:918: error: 'class_datum_t' has no member named 'value'
 slat.c:923: error: 'common_datum_t' has no member named 'value'
 slat.c:925: error: 'common_datum_t' has no member named 'value'
 make[4]: *** [slat.o] Error 1
 make[4]: Leaving directory `/build/buildd/slat-2.0/src/slat'
 make[3]: *** [all] Error 2
 make[3]: Leaving directory `/build/buildd/slat-2.0/src/slat'
 make[2]: *** [all-recursive] Error 1
 make[2]: Leaving directory `/build/buildd/slat-2.0/src'
 make[1]: *** [all-recursive] Error 1
 make[1]: Leaving directory `/build/buildd/slat-2.0'
 make: *** [build/slat] Error 2
 **
 Build finished at 20060812-0519
 FAILED [dpkg-buildpackage died]
 --

-- 
Julien Danjou
.''`.  Debian Developer
: :' : http://julien.danjou.info
`. `'  http://people.debian.org/~acid
  `-   9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: slat
Source-Version: 2.0-3

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

slat_2.0-3.diff.gz
  to pool/main/s/slat/slat_2.0-3.diff.gz
slat_2.0-3.dsc
  to pool/main/s/slat/slat_2.0-3.dsc
slat_2.0-3_i386.deb
  to pool/main/s/slat/slat_2.0-3_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.
Manoj Srivastava [EMAIL PROTECTED] (supplier of updated slat 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.7
Date: Sun, 20 Aug 2006 12:32:30 -0500
Source: slat
Binary: slat
Architecture: source i386
Version: 2.0-3
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava [EMAIL PROTECTED]
Changed-By: Manoj Srivastava [EMAIL PROTECTED]
Description: 
 slat   - Tools for information flow analysis of 

Bug#382146: Patch for the second FTBFS

[Margarita Manterola]

The second FTBFS is due to a bashism in syscheck.sh which upstream is
already aware of.

I'm attaching a patch that fixes that problem.

-- 
Love
Marga
--- spl-0.9i/syscheck.sh2006-05-28 10:36:41.0 -0300
+++ spl-marga/syscheck.sh   2006-08-20 14:44:21.07690 -0300
@@ -141,19 +141,43 @@
;;
extra_cflags)
for dir in \
-   /usr/include/{kde,qt3}  \
-   /opt/{kde*,qt3*,mysql}/include  \
-   /usr/lib{,32,64}/qt*/include\
-   /{usr,opt}/local/include
+   /usr/include/kde\
+   /usr/include/qt3\
+   /opt/kde*/include   \
+   /opt/qt3*/include   \
+   /opt/mysql/include  \
+   /usr/lib/qt*/include\
+   /usr/lib32/qt*/include  \
+   /usr/lib64/qt*/include  \
+   /usr/local/include  \
+   /opt/local/include
do
[ -d $dir ]  echo -I$dir
done
;;
extra_ldflags)
for dir in \
-   /opt/{kde*,qt*,mysql}/lib{,32,64}   \
-   /usr/lib{,32,64}/{qt*/lib,mysql}\
-   /{usr,opt}/local/lib{,32,64}
+   /opt/kde*/lib   \
+   /opt/kde*/lib32 \
+   /opt/kde*/lib64 \
+   /opt/qt*/lib\
+   /opt/qt*/lib32  \
+   /opt/qt*/lib64  \
+   /opt/mysql/lib  \
+   /opt/mysql/lib32\
+   /opt/mysql/lib64\
+   /usr/lib/qt*/lib\
+   /usr/lib32/qt*/lib  \
+   /usr/lib64/qt*/lib  \
+   /usr/lib/mysql  \
+   /usr/lib32/mysql\
+   /usr/lib64/mysql\
+   /usr/local/lib  \
+   /usr/local/lib32\
+   /usr/local/lib64\
+   /opt/local/lib  \
+   /opt/local/lib32\
+   /opt/local/lib64
do
[ -d $dir ]  echo -L$dir
done

Processed: This bug was fixed

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 tags 381646 fixed
Bug#381646: Uninstallable since binNMU
Tags were: patch
Tags added: fixed

 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#382146: Second patch

[Margarita Manterola]

So, the first FTBFS was due to /proc not being mounted, or /dev/fd not
symliking to where it should.

The problem was the use of ( ... ), that required creating a file in
/dev/fd.  I changed the script so that this is not necessary (by using a
pipe instead of a temporary file).

I tested this in my local computer, unmounting /proc, and everything worked
fine. 

--
Love,
Marga.
--- spl-0.9i/make-deps.sh   2006-06-07 09:49:39.0 -0300
+++ spl-marga/make-deps.sh  2006-08-20 15:21:09.615533886 -0300
@@ -2,7 +2,12 @@
 
 echo ** $* -MM -MG -xc 2
 
-while read trg srclist; do
+(
+   eval $* -DMAKEDEPS -MM -MG -xc compiler.y *.c examples/*.c 
spl_modules/*.c |
+   sed s|^mod_|spl_modules/mod_|; s|^c-api-test|examples/|; s| $(pwd 
-P)/| |g; |
+   tr '\n' '|' | sed 's,\\| *,,g' | tr '|' '\n' | grep -v '^#' |
+   egrep -v '^(moddir|moc_mod_qt)\.o:' | sed 's| \./| |g' | sed 's| /[^ 
]*||g';
+) |  while read trg srclist; do
echo -n $trg
for src in $srclist; do
case $src in
@@ -15,12 +20,7 @@
esac
done
echo
-done  (
-   eval $* -DMAKEDEPS -MM -MG -xc compiler.y *.c examples/*.c 
spl_modules/*.c |
-   sed s|^mod_|spl_modules/mod_|; s|^c-api-test|examples/|; s| $(pwd 
-P)/| |g; |
-   tr '\n' '|' | sed 's,\\| *,,g' | tr '|' '\n' | grep -v '^#' |
-   egrep -v '^(moddir|moc_mod_qt)\.o:' | sed 's| \./| |g' | sed 's| /[^ 
]*||g';
-)  GNUmakefile.deps.new
+done  GNUmakefile.deps.new
 
 echo 'spl_modules/mod_fann.o: spl_modules/mod_fann.c spl.h compat.h'  
GNUmakefile.deps.new
 echo 'spl_modules/mod_gl.o: spl_modules/mod_gl.c spl.h compat.h'  
GNUmakefile.deps.new

Bug#380869: where is the patch?

[Ana Guerrero]

Hi Martin,

You forgot attach the patch :)

Ana


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

Bug#380869: where is the patch?

[Jarno Elonen]

Yes, please the missing patch! I'd really appreciate it.

- Jarno


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

Processed: Re: Bug#379657: tcpreplay_2.99+3.0.beta9-1(ia64/unstable): FTBFS: compile errors (no field ipbuff)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 forwarded 379657 http://tcpreplay.synfin.net/trac/ticket/81
Bug#379657: tcpreplay_2.99+3.0.beta9-1(ia64/unstable): FTBFS: compile errors 
(no field ipbuff)
Noted your statement that Bug has been forwarded to 
http://tcpreplay.synfin.net/trac/ticket/81.

 tags 379657 + upstream confirmed
Bug#379657: tcpreplay_2.99+3.0.beta9-1(ia64/unstable): FTBFS: compile errors 
(no field ipbuff)
There were no tags set.
Tags added: upstream, confirmed

 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#369517: linux-image-2.6.16-1-alpha-smp: undefined scsi symbols; fails to allocate percpu data

[Norbert Tretkowski]

* Norbert Tretkowski wrote:
 * Andras Horvath wrote:
  but the -smp is still suffering from the same SCSI problems..
 
 Confirmed, I'll investigate next weekend.

I think I have a patch which fixes this problem, building a new kernel
currently...

Norbert


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

Bug#379657: tcpreplay_2.99+3.0.beta9-1(ia64/unstable): FTBFS: compile errors (no field ipbuff)

[Noèl Köthe]

forwarded 379657 http://tcpreplay.synfin.net/trac/ticket/81
tags 379657 + upstream confirmed
thanks

Am Sonntag, den 20.08.2006, 02:12 +0200 schrieb Tobias Klauser:

Hello Tobias,

 This seems to be caused by code enclosed in #ifdef FORCE_ALIGN which,
 according to configure.in is defined on ia64. Though this code doesn't
 seem to be maintained. Upstream's lack of the architectures in question
 maybe?
 
 FORCE_ALIGN is also defined on alpha, arm*, hp*, mips* and sparc*. Does
 the error also show up on these architectures?

Yes. The build daemons had these problems, too.

 I'm trying to investigate this further, but the lack of an ia64 machine makes
 it a bit hard. :-/

Thx for your feedback.
I reported it upstream some days ago:
http://tcpreplay.synfin.net/trac/ticket/81

-- 
Noèl Köthe noel debian.org
Debian GNU/Linux, www.debian.org


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

Processed: Clone

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 severity 382907 serious
Bug#382907: RM: mozilla-locale-fr -- RoM
Severity set to `serious' from `normal'

 clone 382907 -1
Bug#382907: RM: mozilla-locale-fr -- RoM
Bug 382907 cloned as bug 383935.

 reassign -1 mozilla-locale-fr
Bug#383935: RM: mozilla-locale-fr -- RoM
Bug reassigned from package `ftp.debian.org' to `mozilla-locale-fr'.

 retitle -1 mozilla-locale-fr: depends on mozilla
Bug#383935: RM: mozilla-locale-fr -- RoM
Changed Bug title.

 retitle 382907 RM: mozilla-locale-fr -- RoM; RC-buggy
Bug#382907: RM: mozilla-locale-fr -- RoM
Changed Bug title.

 tags -1 + wontfix
Bug#383935: mozilla-locale-fr: depends on mozilla
There were no tags set.
Tags added: wontfix


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#383937: tulip: Package needs to be recompiled

[Colin Alston]

Package: tulip
Version: tulip
Severity: grave
Justification: renders package unusable


This package is completely broken I just wanted to put that in
1) The package requires libOSMesa but does not have it as a dependency
2) The package is linked against the wrong libOSMesa.so.6, this should 
be either libOSMesa16.so.6 or libOSMesa32.so.6
tlprender does not run without this impossible dependency.
symlinking libOSMesa32.so.6 makes the package execute, however it segfaults 

jupiter:/home/colin# tlprender --type=dot (graphviz) --output=peerZA 
--width=2560 --height=2048 -l GEM (Frick) graph.dot
Loading Sizes plugins: [Metric Mapping][Fit to label][Auto_sizing]

Loading Int plugins:

Loading Layout plugins: [3-Connected (Tutte)][Hierarchical Tree (R-T 
Extended)][Tree Radial][Tree Map (Shneiderman)][Tree Leaf][Squarified Tree 
Map][Spring_Electrical][Scatter Plot][Random][Mixed 
Model][ImprovedWalker][Hierarchical Graph][Hierarchical Graph 3D][GEM3D][GEM 
(Frick)][Embedder (HDE)][Dendrogram][Connected Componnent Packing][Cone 
Tree][Circular][Bubble Tree]

Loading Colors plugins: [Metric Mapping]

Loading Metric plugins: [TreeArityMax][Strongly Connected 
Component][Strength][Strahler][Segment][Random][Path 
Length][Node][Leaf][Id][Betweenness 
Centrality][Eccentricity][Depth][DagLevel][Connected Component][Connected_Tree 
Component][Cluster][Biconnected Componnent][Degree]

Loading String plugins:

Loading Selection plugins: [Spanning 
Forest][SpanningDag][ReachableSubGraph][Multiple edge][Loop 
Selection][Kruskal][Induced sub-graph]

Loading Cluster plugins: [Strength][QuotientClustering][Hierarchical][Equal 
Value][Convolution]

Loading Import Module plugins: [tlp][Grid approximation][Random General 
Tree][Uniform Random Binary Tree][Random Simple Graph][Random General 
Graph][Planar Graph][Grid][GML import][FileSystem][dot (graphviz)][Complete 
Tree][Complete General Graph][Adjacency Matrix]

Loading Export Module plugins: [tlp][GML]

Segmentation fault

QED: This package is totaly broken, this is a Grave bug, this is reproducable.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


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

Bug#379388: License of pgapack and Debian GNU/Linux

[Andreas Franzen]

Dear Mr Lusk,

your public-genetic-algorithms library pgapack is since many years part of
the Debian GNU/Linux distribution.

It was found recently that the license of pgapack means that pgapack is not
really free software. The license of pgapack restricts the selling of
derivative works.

The license of mpich does not contain such restrictions. Thus, would it be
possible to change the license of pgapack to the license of mpich?

Best Regards,

Andreas Franzen [EMAIL PROTECTED]

PS: I already sent a similar message but there seemed to have been some
delivery problems.


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

Bug#380869: where is the patch?

[Martin Orr]

On 20/08/06 19:24, Ana Guerrero wrote:
 You forgot attach the patch :)

Oops!  There's really very little to be done as cdbs does all the work.

-- 
Martin Orr
diff -NbarU2 memaid-pyqt-0.2.5.orig/debian/control 
memaid-pyqt-0.2.5/debian/control
--- memaid-pyqt-0.2.5.orig/debian/control   2006-08-20 13:57:49.0 
+0100
+++ memaid-pyqt-0.2.5/debian/control2006-08-20 12:49:41.0 +0100
@@ -3,10 +3,12 @@
 Priority: optional
 Maintainer: Jarno Elonen [EMAIL PROTECTED]
-Build-Depends: cdbs, debhelper (= 4.1.0), pyqt-tools, python (= 2.3), 
python-dev (= 2.3)
+Build-Depends: cdbs (= 0.4.43), debhelper (= 5.0.37.2), pyqt-tools, python 
(= 2.3), python-dev (= 2.3), python-central (= 0.5)
 Standards-Version: 3.6.1
+XS-Python-Version: current
 
 Package: memaid-pyqt
 Architecture: any
 Depends: python-qt3, python-xml, ${shlibs:Depends}, ${python:Depends}
+XB-Python-Version: ${python:Versions}
 Description: memorization tool with optimal question scheduling
  MemAid is like a traditional flash-card program to help you memorize
diff -NbarU2 memaid-pyqt-0.2.5.orig/debian/pycompat 
memaid-pyqt-0.2.5/debian/pycompat
--- memaid-pyqt-0.2.5.orig/debian/pycompat  1970-01-01 01:00:00.0 
+0100
+++ memaid-pyqt-0.2.5/debian/pycompat   2006-08-20 13:57:10.0 +0100
@@ -0,0 +1 @@
+2
diff -NbarU2 memaid-pyqt-0.2.5.orig/debian/rules memaid-pyqt-0.2.5/debian/rules
--- memaid-pyqt-0.2.5.orig/debian/rules 2006-08-20 13:57:49.0 +0100
+++ memaid-pyqt-0.2.5/debian/rules  2006-08-20 13:38:12.0 +0100
@@ -4,4 +4,6 @@
 #export DH_VERBOSE=1
 
+DEB_PYTHON_SYSTEM := pycentral
+
 include /usr/share/cdbs/1/rules/simple-patchsys.mk
 include /usr/share/cdbs/1/rules/debhelper.mk


signature.asc
Description: OpenPGP digital signature

Processed: bizarre effect from bootstrap.sh

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 reopen 378608
Bug#378608: nss-mdns - FTBFS: error: tag name CXX already exists
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug reopened, originator not changed.

 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: Merge

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 reassign 381182 nvidia-glx-legacy
Bug#381182: apt continue in th instaltion script altru the packages was not 
installed.
Bug reassigned from package `nvidia-glx,nvidia-glx-legacy' to 
`nvidia-glx-legacy'.

 forcemerge 372252 381182
Bug#372252: nvidia-glx-legacy: purge does not remove all diversions.
Bug#381182: apt continue in th instaltion script altru the packages was not 
installed.
Forcibly Merged 372252 381182.


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: setting package to mdadm mdadm-udeb, tagging 381057, tagging 381303, tagging 382263, tagging 382450 ... ... ...

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 package mdadm mdadm-udeb
Ignoring bugs not assigned to: mdadm mdadm-udeb

 tags 381057 + pending
Bug#381057: make mdadm use homehost for initramfs
Tags were: confirmed
Tags added: pending

 tags 381303 + pending
Bug#381303: UUID-based root-partition setup
Tags were: confirmed
Tags added: pending

 tags 382263 + pending
Bug#382263: missing dev nodes when RAID brought up before init
Tags were: confirmed
Bug#382450: Root on (lvm-)crypto-md doesn't work
Bug#383688: udev: /dev/md? missing
Tags added: pending

 tags 382450 + pending
Bug#382450: Root on (lvm-)crypto-md doesn't work
Tags were: pending confirmed
Bug#382263: missing dev nodes when RAID brought up before init
Bug#383688: udev: /dev/md? missing
Tags added: pending

 tags 383688 + pending
Bug#383688: udev: /dev/md? missing
Tags were: pending confirmed
Bug#382263: missing dev nodes when RAID brought up before init
Bug#382450: Root on (lvm-)crypto-md doesn't work
Tags added: pending

 tags 383806 + pending
Bug#383806: mdadm: Fails to upgrade: Attempts to create udev-specific symlink 
on yaird is used
Tags were: patch
Tags added: pending

 tags 383891 + pending
Bug#383891: mdadm: fix for 381181 prevents udev creating /dev/disk/* links
There were no tags set.
Tags added: pending


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#362064: udev: udev tries to write to an installed, working initrd without asking

[Andres Salomon]

Hi,

Here's a use case where having initramfs-tools unconditionally update
initramfs images is a bad thing (at the very least, violating the
principal of least surprise).

I had a machine that was had a poorly supported sata_mv chipset; dapper
nor sarge w/ 2.6.15/2.6.16 images would install onto it.  I had to make
a custom cd w/ backported libata and sata_mv drivers.  Needless to say,
it was a pain in the ass to get installed.

After installation, I backported etch versions of busybox and
initramfs-tools (uploading the latter to backports.org) in order to do
some testing to see if I could get some installation and boot bugs
fixed.  I installed both backports, then I backed up the existing
initramfs image and created a new image.  The intent was to pull new
busybox binaries into the new initramfs, and keep the old initramfs
around in order to recover the system.  I did not realize that during
the package's postinst, existing images would be updated; so, the
backup initramfs image that I had copied also had the new version of
busybox in it.  As it turns out, the busybox backport was broken (not
sure if it was the build, or some interaction w/ the rest of the
system).  Booting using either image would not work, and I had no way to
recover the system (due to bugs in my custom installer cd, recovery
didn't seem to work).

I ended up having to reinstall the system using the custom installer cd.
I was not pleased.  I expect that if I have a working initramfs image
in /boot, it should remain untouched until I explicitly give permission
for it to be touched.  



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

Bug#383777: FTBFS on 64-bit: Segmentation fault ../../safe_slsh

[Kurt Roeckx]

found 383777 1.9.0-1-5
thanks

Hi,

We're still seeing this error in 1.9.0-1-5.


Kurt



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

Bug#378608: bizarre effect from bootstrap.sh

[Sam Morris]

reopen 378608
thanks

The problem's not caused by CDBS... it's caused by however you are
regenerating the build system.

$ tar --list -v -zf nss-mdns_0.8.orig.tar.gz | grep configure$
-rwxrwxr-x 1000/1027709706 2006-04-30 00:36 nss-mdns-0.8/configure

$ ls -l nss-mdns-0.8/configure
-rwxr-xr-x 1 sam sam 1419412 2006-08-20 21:19 nss-mdns-0.8/configure

$ grep 'Generated by GNU Autoconf' nss-mdns-0.8/configure | wc -l
2

Instead of altering the existing files, your .diff.gz just prepends the
new file to the old one. The same seems to be true for the other files
touched by bootstrap.sh.

Goddamn autotools!

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078


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

Processed: Re: FTBFS on 64-bit: Segmentation fault ../../safe_slsh

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 found 383777 1.9.0-1-5
Bug#383777: FTBFS on 64-bit: Segmentation fault ../../safe_slsh
Bug marked as found in version 1.9.0-1-5.

 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#381919: Uploaded

[Cyril Chaboisseau]

 Le 20 août vers 12:05, Margarita Manterola écrivait:
 I took the liberty of uploading your package, so that the RC bug would be
 fixed.

thanks a lot for the NAU (non advocate upload) !!
;-)

 Please, keep an eye on the other important bugs you have.  Some of them
 look like they should actually be RC as well

indeed,
you're right and I've just changed the severity of one of those bugs

I just hope the other one will be addresed by the upstream authors soon


thanks

-- 
Cyril Chaboisseau

Bug#362064: udev: udev tries to write to an installed, working initrd without asking

[maximilian attems]

On Sun, Aug 20, 2006 at 04:25:53PM -0400, Andres Salomon wrote:
 
 Here's a use case where having initramfs-tools unconditionally update
 initramfs images is a bad thing (at the very least, violating the
 principal of least surprise).

you use an plural, which is wrong.
initramfs-tools updates the newest one only.
it has been doing so since day 1 in the archive.
 
 I had a machine that was had a poorly supported sata_mv chipset; dapper
 nor sarge w/ 2.6.15/2.6.16 images would install onto it.  I had to make
 a custom cd w/ backported libata and sata_mv drivers.  Needless to say,
 it was a pain in the ass to get installed.

aren't tomorrow dailies based on 2.6.17, but that is offtopic..
 
 After installation, I backported etch versions of busybox and
 initramfs-tools (uploading the latter to backports.org) in order to do
 some testing to see if I could get some installation and boot bugs
 fixed.  I installed both backports, then I backed up the existing
 initramfs image and created a new image.  The intent was to pull new
 busybox binaries into the new initramfs, and keep the old initramfs
 around in order to recover the system.  I did not realize that during
 the package's postinst, existing images would be updated; so, the
 backup initramfs image that I had copied also had the new version of
 busybox in it.  As it turns out, the busybox backport was broken (not
 sure if it was the build, or some interaction w/ the rest of the
 system).  Booting using either image would not work, and I had no way to
 recover the system (due to bugs in my custom installer cd, recovery
 didn't seem to work).

the package postinstall explicitly tells what it does:
# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-2.6.17-2-686

so it can only have been overlooked.
 
 I ended up having to reinstall the system using the custom installer cd.
 I was not pleased.  I expect that if I have a working initramfs image
 in /boot, it should remain untouched until I explicitly give permission
 for it to be touched.  

oldstyle initrd-tools and yaird do this,
but they don't have any possiblity to have hooks for other packages.


-- 
maks


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

Bug#383777: [Pkg-jed-sl-modules] Bug#383777: FTBFS on 64-bit: Segmentation fault ../../safe_slsh

[Rafael Laboissiere]

* Kurt Roeckx [EMAIL PROTECTED] [2006-08-20 23:01]:

 found 383777 1.9.0-1-5
 thanks
 
 Hi,
 
 We're still seeing this error in 1.9.0-1-5.

Thanks, I have already noticed it.  I reached a point now that I cannot
debug further by uploading new versions of the package and looking at the
autobuilder log.  I think I need access to an amd64 system.  Do you now
the simplest way of getting this?

-- 
Rafael


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

Bug#382429: samba: Naive fix for the issue

[Erich Schubert]

Package: samba
Version: 3.0.23b-2
Followup-For: Bug #382429

Here's a very naive approach at resolving the issue with the
autobuilders:
---
--- source/lib/interfaces.c 2005-07-28 15:19:45.0 +0200
+++ interfaces.c.naive-fix  2006-08-20 23:58:41.0 +0200
@@ -397,7 +397,7 @@
int i;

printf(got %d interfaces:\n, total);
-   if (total = 0) exit(1);
+   if (total  0) exit(1);

for (i=0;itotal;i++) {
printf(%-10s , ifaces[i].name);
---
This should do the job; according to the buildd logs posted, one method (the
correct one?) returns 0, the other one returns -1 interfaces.

The interface enumeraion methods should return -1 on error (e.g. ioctl doesn't
work). Maybe ask upstream if this diff makes sense.
On the vserver buildds, a total of 0 is perfectly valid, after all.

That should be the easiest fix...

Regards,
Erich


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

Bug#362064: udev: udev tries to write to an installed, working initrd without asking

[Jonas Smedegaard]

On Sun, 20 Aug 2006 23:26:32 +0200 maximilian attems wrote:

 On Sun, Aug 20, 2006 at 04:25:53PM -0400, Andres Salomon wrote:

  I had a machine that was had a poorly supported sata_mv chipset;
  dapper nor sarge w/ 2.6.15/2.6.16 images would install onto it.  I
  had to make a custom cd w/ backported libata and sata_mv drivers.

  I ended up having to reinstall the system using the custom
  installer cd. I was not pleased.  I expect that if I have a working
  initramfs image in /boot, it should remain untouched until I
  explicitly give permission for it to be touched.  
 
 oldstyle initrd-tools and yaird do this,
 but they don't have any possiblity to have hooks for other packages.

And hooks seems irrelevant for this case.


 - Jonas

-- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm


pgpO6wqDXOk8w.pgp
Description: PGP signature

Bug#373406: Python policy transition

[A. Maitland Bottoms]

vtk 5.0.1-1 is making use of dh_python, and
it and mayavi_1.5-2 have been seen running
correctly with python2.4 as the default python.

There may be additional refinements to improve
python policy compliance, but I have uploaded
vtk_5.0.1-1 and mayavi_1.5-2 to support the
transition to python2.4 as default.

-Maitland


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

Bug#383888: vtk failed to build from sources

[A. Maitland Bottoms]

OK,
I have just successfully built vtk 5.0.1
in a pbuilder environment.

Perhaps you were trying vtk 4.4.2 and filed
a duplicate of bug #379240? Your bug report
doesn't say, but since 5.0.1 is still new,
I am guessing that you saw the bug on version
4.4.2-10.

-Maitland


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

Processed: notfound 330890 in 0.94.0-15

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.20
 notfound 330890 0.94.0-15
Bug#330890: dia: Arbitrary code execution when importing a .svg file
Bug marked as not found in version 0.94.0-15.
(By the way, this Bug is currently marked as done.)


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: FTBFS: vtk_4.4.2-10

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 merge 383888 379240
Bug#379240: FTBFS: Attempt to add link library vtkCommonPython which is not a 
library target
Bug#383888: vtk failed to build from sources
Merged 379240 383888.


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: More RCs!

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 retitle 383829 cmake: broke compatibility between 2.2 and 2.4
Bug#383829: libapache2-mod-xmlrpc2: FTBFS: missing build-dep ?
Changed Bug title.

 clone 383829 -1 -2
Bug#383829: cmake: broke compatibility between 2.2 and 2.4
Bug 383829 cloned as bugs 383955-383956.

 reassign -1 libapache2-mod-xmlrpc2
Bug#383955: cmake: broke compatibility between 2.2 and 2.4
Bug reassigned from package `cmake' to `libapache2-mod-xmlrpc2'.

 retitle -1 FTBFS: Shouldn't use shell expansions in variable assignments
Bug#383955: cmake: broke compatibility between 2.2 and 2.4
Changed Bug title.

 severity -1 important
Bug#383955: FTBFS: Shouldn't use shell expansions in variable assignments
Severity set to `important' from `critical'

 tags -1 +patch
Bug#383955: FTBFS: Shouldn't use shell expansions in variable assignments
There were no tags set.
Tags added: patch

 reassign -2 strigi
Bug#383956: cmake: broke compatibility between 2.2 and 2.4
Bug reassigned from package `cmake' to `strigi'.

 retitle -2 FTBFS: Typo in build system
Bug#383956: cmake: broke compatibility between 2.2 and 2.4
Changed Bug title.

 severity -2 important
Bug#383956: FTBFS: Typo in build system
Severity set to `important' from `critical'

 tags -2 +patch
Bug#383956: FTBFS: Typo in build system
There were no tags set.
Tags added: patch

 thanks, control lots of work today eh?
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#383829: moreinfo

[Damián Viano]

Ok, I've been looking this for a while now and I'm not sure what to do.
The problem is that cmake changed the way it links binaries between 2.2
and 2.4, before the linking line was directly included in the Makefiles,
like: 

mod_xmlrpc.so: CMakeFiles/mod_xmlrpc.dir/build.make
@echo Linking C shared library mod_xmlrpc.so
$(CMAKE_COMMAND) -E remove -f libmod_xmlrpc.a mod_xmlrpc.so
gcc -fPIC  `/usr/bin/xmlrpc-c-config --libs` `/usr/bin/apr-config 
--libs` `/usr/bin/apxs2 -q LDFLAGS` -lpthread -ldl -lcrypt -lm   -lc -lruby1.8 
-shared -Wl,-soname,mod_xmlrpc.so -o mod_xmlrpc.so $(mod_xmlrpc_OBJECTS) 
$(mod_xmlrpc_EXTERNAL_OBJECTS)

while 2.4 does it like: 

mod_xmlrpc.so: CMakeFiles/mod_xmlrpc.dir/build.make
@$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --red --bold 
Linking C shared library mod_xmlrpc.so
$(CMAKE_COMMAND) -P CMakeFiles/mod_xmlrpc.dir/cmake_clean_target.cmake
$(CMAKE_COMMAND) -E cmake_link_script 
CMakeFiles/mod_xmlrpc.dir/link.txt --verbose=$(VERBOSE)

and link.txt contains:

/usr/bin/gcc  -fPIC   -DSUPPORT_C `/usr/bin/xmlrpc-c-config --cflags` 
`/usr/bin/apr-config --cflags` -I`/usr/bin/apr-config --includedir` 
`/usr/bin/apxs2 -q CFLAGS` -I`/usr/bin/apxs2 -q INCLUDEDIR` -Wall -g 
-fno-strict-aliasing -O2  -fPIC -I/usr/lib/ruby/1.8/i486-linux -DSUPPORT_RUBY  
`/usr/bin/xmlrpc-c-config --libs` `/usr/bin/apr-config --libs` `/usr/bin/apxs2 
-q LDFLAGS` -lpthread -ldl -lcrypt -lm   -lc -lruby1.8 -shared 
-Wl,-soname,mod_xmlrpc.so -o mod_xmlrpc.so 
CMakeFiles/mod_xmlrpc.dir/mod_xmlrpc.o 
CMakeFiles/mod_xmlrpc.dir/mod_xmlrpc_c.o 
CMakeFiles/mod_xmlrpc.dir/mod_xmlrpc_rb.o 
CMakeFiles/mod_xmlrpc.dir/mod_xmlrpc_server.o

The problem lays in that Makefile lines are interpreted by a shell while cmake
directly exec them. Wether this change in the behaviour of cmake is a bug or
not I'll leave it to the maintainer to figure it out, because you probably
shouldn't depend on that on rules of a 'cross-platform make'.

Meanwhile I tested to compile every cmake build-rdep with 2.4 and found 
this:
boson 0
cableswig 0
gccxml 0
libapache2-mod-xmlrpc2 100
octaviz 0
strigi 100
strigiapplet 0
vtk 100
yodl 0

Both strigi and libapache2-mod-xmlrpc2 seems broken by this change, the vtk
problem doesn't seem related. I have patches for those two bugs and will be
filling bugs with patches for them.

Damián(Des).


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

Bug#383870: fetchmail: Fetchmail duplicates my SPAM every 10 minutes - ARGH!

[Matthias Andree]

Well, Exim's error before it just drops the connection isn't selling
fetchmail a hint that there's no progress beyond that point.

The question is: why does fetchmail not skip over the offending
messages? It may or may not try to bounce them, depending on your
configuration, but should mark them refused - as seen in ..flushed.

But what exactly happens is a matter of your configuration.

Please show your fetchmailrc file and the output of 
/etc/init.d/fetchmail debug-run
up to the error.

Remember to restart fetchmail afterwards with /etc/init.d/fetchmail start

-- 
Matthias Andree


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

Bug#382450: marked as done (Root on (lvm-)crypto-md doesn't work)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382263: fixed in mdadm 2.5.3.git200608202239-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: cryptsetup
Version: 1.0.3-3

I'm interested in running an encrypted root partition, specifically
where root is a logical volume on dm-crypt on raid1 md.  The nightly
build of the Debian installer (2006-08-09) is willing to build this
setup without complaint.  However, when booting into the new system, the
cryptroot script fails to properly open the encrypted md partition.

Here's the system layout since it's a little confusing:

/dev/hda2, /dev/hda3= /dev/md0   (raid1) (testing only)
/dev/md0= /dev/mapper/crypt0 (dm-crypt)
/dev/mapper/crypt0  = ep.root(volume group)
/dev/mapper/ep.root-ep.root = /  (jfs formatted logical volume)

I've read through some of the other bug reports (#371846 and others) and
there seems to be some discussion on properly determining device
dependencies, but as far as I can tell a general solution hasn't been
developed yet.  Is this the right answer?  Or is it possible to hack md
support into cryptroot as was done for lvm?

Here's a console dump of the machine attempting to boot for the first
time, the bottom four lines repeat indefinitely:

Linux version 2.6.17-1-686 (Debian 2.6.17-5) ([EMAIL PROTECTED]) (gcc version 
4.1.2 20060715 (prerelease) (Debian 4.1.1-9)) #1 SMP Sat Jul 29 15:32:47 UTC 
2006
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f000 (usable)
 BIOS-e820: 0009f000 - 000a (reserved)
 BIOS-e820: 0010 - 1ffae000 (usable)
 BIOS-e820: 1ffae000 - 2000 (reserved)
 BIOS-e820: feda - fee0 (reserved)
 BIOS-e820: ffb0 - 0001 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
DMI 2.3 present.
ACPI: PM-Timer IO Port: 0x808
Allocating PCI resources starting at 3000 (gap: 2000:deda)
Built 1 zonelists
Kernel command line: root=/dev/mapper/ep.root-ep.root ro console=ttyS0
Local APIC disabled by BIOS -- you can enable it with lapic
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Detected 1295.994 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 511036k/523960k available (1478k kernel code, 12380k reserved, 540k 
data, 164k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2594.25 BogoMIPS (lpj=5188501)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 1024K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 16k freed
ACPI: setting ELCR to 0200 (from 0800)
CPU0: Intel(R) Pentium(R) M processor 1300MHz stepping 05
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 5337k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfc96e, last bus=2
Setting up standard PCI resources
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (:00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 0880-08bf claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller :00:1f.1
PCI: Transparent bridge - :00:1e.0
PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
PCI: Bus #07 (-#0a) is hidden behind transparent bridge #02 (-#02) (try 
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *11
ACPI: PCI 

Processed: punt

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 # command block for Debian BTS control
 package fetchmail
Ignoring bugs not assigned to: fetchmail

 tags 383870 upstream
Bug#383870: fetchmail: Fetchmail duplicates my SPAM every 10 minutes - ARGH!
There were no tags set.
Tags added: upstream

 # claim bug for upstream
 severity 383870 serious
Bug#383870: fetchmail: Fetchmail duplicates my SPAM every 10 minutes - ARGH!
Severity set to `serious' from `grave'

 # fetchmail is neither unusable for most users nor causing data loss
 # nor allowing access to the user's account
 retitle 383870 fetchmail: no POP3 QUIT after SIGPIPE from SMTP listener
Bug#383870: fetchmail: Fetchmail duplicates my SPAM every 10 minutes - ARGH!
Changed Bug title.

 # more accurate title
 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#382450: marked as done (Root on (lvm-)crypto-md doesn't work)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383688: fixed in mdadm 2.5.3.git200608202239-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: cryptsetup
Version: 1.0.3-3

I'm interested in running an encrypted root partition, specifically
where root is a logical volume on dm-crypt on raid1 md.  The nightly
build of the Debian installer (2006-08-09) is willing to build this
setup without complaint.  However, when booting into the new system, the
cryptroot script fails to properly open the encrypted md partition.

Here's the system layout since it's a little confusing:

/dev/hda2, /dev/hda3= /dev/md0   (raid1) (testing only)
/dev/md0= /dev/mapper/crypt0 (dm-crypt)
/dev/mapper/crypt0  = ep.root(volume group)
/dev/mapper/ep.root-ep.root = /  (jfs formatted logical volume)

I've read through some of the other bug reports (#371846 and others) and
there seems to be some discussion on properly determining device
dependencies, but as far as I can tell a general solution hasn't been
developed yet.  Is this the right answer?  Or is it possible to hack md
support into cryptroot as was done for lvm?

Here's a console dump of the machine attempting to boot for the first
time, the bottom four lines repeat indefinitely:

Linux version 2.6.17-1-686 (Debian 2.6.17-5) ([EMAIL PROTECTED]) (gcc version 
4.1.2 20060715 (prerelease) (Debian 4.1.1-9)) #1 SMP Sat Jul 29 15:32:47 UTC 
2006
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f000 (usable)
 BIOS-e820: 0009f000 - 000a (reserved)
 BIOS-e820: 0010 - 1ffae000 (usable)
 BIOS-e820: 1ffae000 - 2000 (reserved)
 BIOS-e820: feda - fee0 (reserved)
 BIOS-e820: ffb0 - 0001 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
DMI 2.3 present.
ACPI: PM-Timer IO Port: 0x808
Allocating PCI resources starting at 3000 (gap: 2000:deda)
Built 1 zonelists
Kernel command line: root=/dev/mapper/ep.root-ep.root ro console=ttyS0
Local APIC disabled by BIOS -- you can enable it with lapic
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Detected 1295.994 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 511036k/523960k available (1478k kernel code, 12380k reserved, 540k 
data, 164k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2594.25 BogoMIPS (lpj=5188501)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 1024K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 16k freed
ACPI: setting ELCR to 0200 (from 0800)
CPU0: Intel(R) Pentium(R) M processor 1300MHz stepping 05
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 5337k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfc96e, last bus=2
Setting up standard PCI resources
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (:00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 0880-08bf claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller :00:1f.1
PCI: Transparent bridge - :00:1e.0
PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
PCI: Bus #07 (-#0a) is hidden behind transparent bridge #02 (-#02) (try 
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *11
ACPI: PCI 

Bug#383688: marked as done (udev: /dev/md? missing)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383688: fixed in mdadm 2.5.3.git200608202239-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: udev
Version: 0.097-1
Severity: critical
Justification: breaks the whole system

device nodes for kernel autoconfigured raid arrays are not created.
This causes my LVM volume group to not be found and thus all my
filesystems (such as /usr /var /home) are nto availible.
I believe this bug will also affect systems where /usr and friends
have their own md device (i.e. lvm not involved)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages udev depends on:
ii  initscripts  2.86.ds1-15 Scripts for initializing and 
shutt
ii  libc62.3.6-19GNU C Library: Shared libraries
ii  libselinux1  1.30.26-2   SELinux shared libraries
pn  libvolume-id0none  (no description available)
ii  lsb-base 3.1-14  Linux Standard Base 3.1 init 
scrip

udev recommends no packages.

---End Message---
---BeginMessage---
Source: mdadm
Source-Version: 2.5.3.git200608202239-1

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

mdadm-udeb_2.5.3.git200608202239-1_i386.udeb
  to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-1_i386.udeb
mdadm_2.5.3.git200608202239-1.diff.gz
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.diff.gz
mdadm_2.5.3.git200608202239-1.dsc
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.dsc
mdadm_2.5.3.git200608202239-1_i386.deb
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1_i386.deb
mdadm_2.5.3.git200608202239.orig.tar.gz
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239.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.
martin f. krafft [EMAIL PROTECTED] (supplier of updated mdadm 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.7
Date: Mon, 21 Aug 2006 00:25:22 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 2.5.3.git200608202239-1
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers [EMAIL PROTECTED]
Changed-By: martin f. krafft [EMAIL PROTECTED]
Description: 
 mdadm  - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 381057 381303 382263 382389 382450 382480 382876 383688 383806 383891
Changes: 
 mdadm (2.5.3.git200608202239-1) unstable; urgency=low
 .
   * Tracking upstream git releases.
 - now the --run switch behaves as stated in the manpage. This properly
   fixes #287415
 - new version-1 partitionable arrays are now named X instead of _dX (e.g.
   0 instead of _d0) for device names like md_dX. I actually think this is
   a bug and hope upstream will use dX (e.g. d0) instead in a future
   version.
 - we specify --symlink=no and thus disable the new feature to create
   /dev/mdX symlinks to /dev/md/X devices until the entire device node mess
   is cleared up. No need to introduce yet another complicating factor at
   this stage.
   * Instead of trying to do a whole lot of magic with respect to detecting
 RAID devices to start, mdadm from now on requires a valid mdadm.conf file
 to be installed. It still tries to do what it can, but there are no
 heuristics anymore. See /usr/share/doc/mdadm/README.upgrading-2.5.3 .
   * Removed the zero-superblock warning because we require the user to sign
 off the configuration file anyway.
   * This also enables us to use mdadm.conf from the initial ramdisk and thus
 closes: #381303.
   * In case the user chooses to assemble all arrays from the initial ramdisk,
 use the new homehost feature of mdadm (closes: 

Bug#382263: marked as done (missing dev nodes when RAID brought up before init)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382450: fixed in mdadm 2.5.3.git200608202239-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: mdadm
Version: 2.5.2-10
Severity: normal

Hi Martin, 

I am running a LVM on RAID setup for some time now and never had any 
problems. Yesterday I upgraded mdadm and today my system would not 
boot anymore. 

After some research I found out that /dev/md0 and /dev/md1 magically 
disappeared which was the reason why lvm could not activate my 
volume group called raid which is located there. 

The system still locates md0 and md1 fine during boot (I am booting from
md0, which is also a raid1). However, according to lvmdiskscan it does
not see md1 anymore. 

I know that it would probably work fine if mdadm would activate the 
arrays but I think my setup is just as valid. In it, mdadm is used 
exclusively for checking if anything is wrong with the arrays.

Looking at #381181, I'd say that this is really a bug in initramfs 
as it should compare devices via the major and minor numbers and 
not just using theirs paths. Your mileage may vary ;)

Greetings, Torsten

-- Package-specific info:
--- mount output
/dev/md0 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/mapper/raid-usr on /usr type xfs (rw)
/dev/mapper/raid-var on /var type ext3 (rw)
/dev/mapper/raid-cache on /var/cache type ext3 (rw)
/dev/mapper/raid-home on /home type xfs (rw)
/dev/mapper/raid-backup on /backup type xfs (rw)
/dev/mapper/raid-mirror on /home/torsten/mirror type ext3 (rw)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
stargate:/home on /mnt/stargate type nfs (rw,addr=192.168.2.1)
stargate:/music on /music type nfs (rw,addr=192.168.2.1)
nfsd on /proc/fs/nfsd type nfsd (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

--- mdadm.conf
DEVICE partitions
ARRAY /dev/.static/dev/md0 level=raid1 num-devices=2 
UUID=3e30ef63:0c27f545:cd3840a6:d20fc5b6
ARRAY /dev/.static/dev/md1 level=raid1 num-devices=2 
UUID=c0bf03b8:63dd5a05:9fa2ce57:c2b0ec92
MAILADDR root

--- /proc/mdstat:
Personalities : [raid1] 
md1 : active raid1 sdc4[1] sdb4[0]
  280326144 blocks [2/2] [UU]
  
md0 : active raid1 sdc1[1] sdb1[0]
  2931712 blocks [2/2] [UU]
  
unused devices: none

--- /proc/partitions:
major minor  #blocks  name

   3 0   40209120 hda
   3 1261 hda1
   3 2292 hda2
   3 3   36202477 hda3
   816  312567413 sdb
   8172931831 sdb1
   818   14651280 sdb2
   819   14651280 sdb3
   820  280326217 sdb4
   832  312567413 sdc
   8332931831 sdc1
   834   14651280 sdc2
   835   14651280 sdc3
   836  280326217 sdc4
   9 02931712 md0
   9 1  280326144 md1
 253 0   26214400 dm-0
 253 13145728 dm-1
 253 22097152 dm-2
 253 3 409600 dm-3
 253 4 409600 dm-4
 253 51048576 dm-5
 253 6   10485760 dm-6
 253 73145728 dm-7
 253 85242880 dm-8
 253 9   73400320 dm-9
 25310   78643200 dm-10
 253112097152 dm-11
 25312   52428800 dm-12

--- initrd.img-2.6.18-rc3:

--- /proc/modules:

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-rc3
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0] 1.5.3  Debian configuration management sy
ii  libc6 2.3.6-18   GNU C Library: Shared libraries
ii  lsb-base  3.1-12 Linux Standard Base 3.1 init scrip
ii  makedev   2.3.1-82   creates device files in /dev

Versions of packages mdadm recommends:
ii  exim [mail-transport-agent]   3.36-18.1  An obsolete MTA (Mail Transport Ag

-- debconf information:
* mdadm/autostart: true
  mdadm/initrdstart: /dev/md0
* mdadm/warning:
  mdadm/start_daemon: true
  mdadm/mail_to: root
  mdadm/autocheck: true


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: mdadm
Source-Version: 2.5.3.git200608202239-1

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

Bug#382263: marked as done (missing dev nodes when RAID brought up before init)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#383688: fixed in mdadm 2.5.3.git200608202239-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: mdadm
Version: 2.5.2-10
Severity: normal

Hi Martin, 

I am running a LVM on RAID setup for some time now and never had any 
problems. Yesterday I upgraded mdadm and today my system would not 
boot anymore. 

After some research I found out that /dev/md0 and /dev/md1 magically 
disappeared which was the reason why lvm could not activate my 
volume group called raid which is located there. 

The system still locates md0 and md1 fine during boot (I am booting from
md0, which is also a raid1). However, according to lvmdiskscan it does
not see md1 anymore. 

I know that it would probably work fine if mdadm would activate the 
arrays but I think my setup is just as valid. In it, mdadm is used 
exclusively for checking if anything is wrong with the arrays.

Looking at #381181, I'd say that this is really a bug in initramfs 
as it should compare devices via the major and minor numbers and 
not just using theirs paths. Your mileage may vary ;)

Greetings, Torsten

-- Package-specific info:
--- mount output
/dev/md0 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/mapper/raid-usr on /usr type xfs (rw)
/dev/mapper/raid-var on /var type ext3 (rw)
/dev/mapper/raid-cache on /var/cache type ext3 (rw)
/dev/mapper/raid-home on /home type xfs (rw)
/dev/mapper/raid-backup on /backup type xfs (rw)
/dev/mapper/raid-mirror on /home/torsten/mirror type ext3 (rw)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
stargate:/home on /mnt/stargate type nfs (rw,addr=192.168.2.1)
stargate:/music on /music type nfs (rw,addr=192.168.2.1)
nfsd on /proc/fs/nfsd type nfsd (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

--- mdadm.conf
DEVICE partitions
ARRAY /dev/.static/dev/md0 level=raid1 num-devices=2 
UUID=3e30ef63:0c27f545:cd3840a6:d20fc5b6
ARRAY /dev/.static/dev/md1 level=raid1 num-devices=2 
UUID=c0bf03b8:63dd5a05:9fa2ce57:c2b0ec92
MAILADDR root

--- /proc/mdstat:
Personalities : [raid1] 
md1 : active raid1 sdc4[1] sdb4[0]
  280326144 blocks [2/2] [UU]
  
md0 : active raid1 sdc1[1] sdb1[0]
  2931712 blocks [2/2] [UU]
  
unused devices: none

--- /proc/partitions:
major minor  #blocks  name

   3 0   40209120 hda
   3 1261 hda1
   3 2292 hda2
   3 3   36202477 hda3
   816  312567413 sdb
   8172931831 sdb1
   818   14651280 sdb2
   819   14651280 sdb3
   820  280326217 sdb4
   832  312567413 sdc
   8332931831 sdc1
   834   14651280 sdc2
   835   14651280 sdc3
   836  280326217 sdc4
   9 02931712 md0
   9 1  280326144 md1
 253 0   26214400 dm-0
 253 13145728 dm-1
 253 22097152 dm-2
 253 3 409600 dm-3
 253 4 409600 dm-4
 253 51048576 dm-5
 253 6   10485760 dm-6
 253 73145728 dm-7
 253 85242880 dm-8
 253 9   73400320 dm-9
 25310   78643200 dm-10
 253112097152 dm-11
 25312   52428800 dm-12

--- initrd.img-2.6.18-rc3:

--- /proc/modules:

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-rc3
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0] 1.5.3  Debian configuration management sy
ii  libc6 2.3.6-18   GNU C Library: Shared libraries
ii  lsb-base  3.1-12 Linux Standard Base 3.1 init scrip
ii  makedev   2.3.1-82   creates device files in /dev

Versions of packages mdadm recommends:
ii  exim [mail-transport-agent]   3.36-18.1  An obsolete MTA (Mail Transport Ag

-- debconf information:
* mdadm/autostart: true
  mdadm/initrdstart: /dev/md0
* mdadm/warning:
  mdadm/start_daemon: true
  mdadm/mail_to: root
  mdadm/autocheck: true


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: mdadm
Source-Version: 2.5.3.git200608202239-1

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

Bug#383688: marked as done (udev: /dev/md? missing)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382263: fixed in mdadm 2.5.3.git200608202239-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: udev
Version: 0.097-1
Severity: critical
Justification: breaks the whole system

device nodes for kernel autoconfigured raid arrays are not created.
This causes my LVM volume group to not be found and thus all my
filesystems (such as /usr /var /home) are nto availible.
I believe this bug will also affect systems where /usr and friends
have their own md device (i.e. lvm not involved)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages udev depends on:
ii  initscripts  2.86.ds1-15 Scripts for initializing and 
shutt
ii  libc62.3.6-19GNU C Library: Shared libraries
ii  libselinux1  1.30.26-2   SELinux shared libraries
pn  libvolume-id0none  (no description available)
ii  lsb-base 3.1-14  Linux Standard Base 3.1 init 
scrip

udev recommends no packages.

---End Message---
---BeginMessage---
Source: mdadm
Source-Version: 2.5.3.git200608202239-1

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

mdadm-udeb_2.5.3.git200608202239-1_i386.udeb
  to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-1_i386.udeb
mdadm_2.5.3.git200608202239-1.diff.gz
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.diff.gz
mdadm_2.5.3.git200608202239-1.dsc
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.dsc
mdadm_2.5.3.git200608202239-1_i386.deb
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1_i386.deb
mdadm_2.5.3.git200608202239.orig.tar.gz
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239.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.
martin f. krafft [EMAIL PROTECTED] (supplier of updated mdadm 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.7
Date: Mon, 21 Aug 2006 00:25:22 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 2.5.3.git200608202239-1
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers [EMAIL PROTECTED]
Changed-By: martin f. krafft [EMAIL PROTECTED]
Description: 
 mdadm  - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 381057 381303 382263 382389 382450 382480 382876 383688 383806 383891
Changes: 
 mdadm (2.5.3.git200608202239-1) unstable; urgency=low
 .
   * Tracking upstream git releases.
 - now the --run switch behaves as stated in the manpage. This properly
   fixes #287415
 - new version-1 partitionable arrays are now named X instead of _dX (e.g.
   0 instead of _d0) for device names like md_dX. I actually think this is
   a bug and hope upstream will use dX (e.g. d0) instead in a future
   version.
 - we specify --symlink=no and thus disable the new feature to create
   /dev/mdX symlinks to /dev/md/X devices until the entire device node mess
   is cleared up. No need to introduce yet another complicating factor at
   this stage.
   * Instead of trying to do a whole lot of magic with respect to detecting
 RAID devices to start, mdadm from now on requires a valid mdadm.conf file
 to be installed. It still tries to do what it can, but there are no
 heuristics anymore. See /usr/share/doc/mdadm/README.upgrading-2.5.3 .
   * Removed the zero-superblock warning because we require the user to sign
 off the configuration file anyway.
   * This also enables us to use mdadm.conf from the initial ramdisk and thus
 closes: #381303.
   * In case the user chooses to assemble all arrays from the initial ramdisk,
 use the new homehost feature of mdadm (closes: 

Bug#382263: marked as done (missing dev nodes when RAID brought up before init)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382263: fixed in mdadm 2.5.3.git200608202239-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: mdadm
Version: 2.5.2-10
Severity: normal

Hi Martin, 

I am running a LVM on RAID setup for some time now and never had any 
problems. Yesterday I upgraded mdadm and today my system would not 
boot anymore. 

After some research I found out that /dev/md0 and /dev/md1 magically 
disappeared which was the reason why lvm could not activate my 
volume group called raid which is located there. 

The system still locates md0 and md1 fine during boot (I am booting from
md0, which is also a raid1). However, according to lvmdiskscan it does
not see md1 anymore. 

I know that it would probably work fine if mdadm would activate the 
arrays but I think my setup is just as valid. In it, mdadm is used 
exclusively for checking if anything is wrong with the arrays.

Looking at #381181, I'd say that this is really a bug in initramfs 
as it should compare devices via the major and minor numbers and 
not just using theirs paths. Your mileage may vary ;)

Greetings, Torsten

-- Package-specific info:
--- mount output
/dev/md0 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/mapper/raid-usr on /usr type xfs (rw)
/dev/mapper/raid-var on /var type ext3 (rw)
/dev/mapper/raid-cache on /var/cache type ext3 (rw)
/dev/mapper/raid-home on /home type xfs (rw)
/dev/mapper/raid-backup on /backup type xfs (rw)
/dev/mapper/raid-mirror on /home/torsten/mirror type ext3 (rw)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
stargate:/home on /mnt/stargate type nfs (rw,addr=192.168.2.1)
stargate:/music on /music type nfs (rw,addr=192.168.2.1)
nfsd on /proc/fs/nfsd type nfsd (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

--- mdadm.conf
DEVICE partitions
ARRAY /dev/.static/dev/md0 level=raid1 num-devices=2 
UUID=3e30ef63:0c27f545:cd3840a6:d20fc5b6
ARRAY /dev/.static/dev/md1 level=raid1 num-devices=2 
UUID=c0bf03b8:63dd5a05:9fa2ce57:c2b0ec92
MAILADDR root

--- /proc/mdstat:
Personalities : [raid1] 
md1 : active raid1 sdc4[1] sdb4[0]
  280326144 blocks [2/2] [UU]
  
md0 : active raid1 sdc1[1] sdb1[0]
  2931712 blocks [2/2] [UU]
  
unused devices: none

--- /proc/partitions:
major minor  #blocks  name

   3 0   40209120 hda
   3 1261 hda1
   3 2292 hda2
   3 3   36202477 hda3
   816  312567413 sdb
   8172931831 sdb1
   818   14651280 sdb2
   819   14651280 sdb3
   820  280326217 sdb4
   832  312567413 sdc
   8332931831 sdc1
   834   14651280 sdc2
   835   14651280 sdc3
   836  280326217 sdc4
   9 02931712 md0
   9 1  280326144 md1
 253 0   26214400 dm-0
 253 13145728 dm-1
 253 22097152 dm-2
 253 3 409600 dm-3
 253 4 409600 dm-4
 253 51048576 dm-5
 253 6   10485760 dm-6
 253 73145728 dm-7
 253 85242880 dm-8
 253 9   73400320 dm-9
 25310   78643200 dm-10
 253112097152 dm-11
 25312   52428800 dm-12

--- initrd.img-2.6.18-rc3:

--- /proc/modules:

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-rc3
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0] 1.5.3  Debian configuration management sy
ii  libc6 2.3.6-18   GNU C Library: Shared libraries
ii  lsb-base  3.1-12 Linux Standard Base 3.1 init scrip
ii  makedev   2.3.1-82   creates device files in /dev

Versions of packages mdadm recommends:
ii  exim [mail-transport-agent]   3.36-18.1  An obsolete MTA (Mail Transport Ag

-- debconf information:
* mdadm/autostart: true
  mdadm/initrdstart: /dev/md0
* mdadm/warning:
  mdadm/start_daemon: true
  mdadm/mail_to: root
  mdadm/autocheck: true


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: mdadm
Source-Version: 2.5.3.git200608202239-1

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

Bug#383835: The package seems usable

[Marco Milanesi]

 Why do you consider this package unusable? I'm testing it and it seems
 to work fine.

ok, you are right. I'm not so experienced on python.

it could be interesting to have a 'python2.3' version, I copied manually

 Please notice that the directory that you mention is not needed in the actual 
 version, and I believe it's a bug: the directory should not be in the 
 package.

yeah, that's the real bug

 In Debian, the python modules are now managed by the python-support package, 
 you can see the python files of this particular package 
 in /usr/share/python-support/gnome-osd, and the compiled version of those 
 in /var/lib/python-support/python2.4.

discovered from you, thanks :)

ciao,
Marco

-- 
 ,= ,-_-. =.  --- +
((_/)o o(\_)) jabber:[EMAIL PROTECTED]/msn:[EMAIL PROTECTED] |
 `-'(. .)`-[EMAIL PROTECTED]   |
 \_/If it works, it's obsolete|


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

Bug#383870: fetchmail: Fetchmail duplicates my SPAM every 10 minutes - ARGH!

[Matthias Andree]

(demoting to serious, tagging upstream, retitling)

Additional info:

fetchmail 6.3.4 and older do NOT log out of the upstream server after
SIGPIPE (I don't know the rationale behind this - it's not in the
comments), which prevents the deletions from happening properly.
Retitling the bug accordingly.

Workarounds:

- have your upstream reject spam with improperly formatted envelopes,
  these should be rejected in the first SMTP dialogue

- do not use multidrop with wildcard (*), but list allowed local
  accounts explicitly (since the bogus address will not match, the
  message will be forwarded to the postmaster address, which is under
  your control, and can also be empty to discard the message - this will
  prevent Exim from hanging up).

- set expunge 10  (fetchmail will send QUIT after 10 messages and
   reconnect, to make deletions effective and limit
   the amount of refetching).

Fix: block SIGPIPE; the SIGPIPE handler was wrong from the moment it was
coded as it uses longjmp() which isn't safe in signal handlers.
Functions that write to broken pipes will still report errors, but
fetchmail won't corrupt internal state or defeat the logout.

Patch attached. BEWARE: it is NOT run-time tested,
I'm not fetching from multidrop accounts.

Nico/Héctor, can we provide an inofficial package to Helge with the
patch below to ask feedback if the fix is complete? It shouldn't matter
if it's i386 rather than x86_64.

Rationale for severity demotion: Since the breakage is partially induced
by configuration and for instance works properly for singledrop, I don't
think grave is justified. Perhaps further demotion to important is
in order, but I'm not the Debian maintainer to remove the unsuitable
for release tag that is attached to critical/grave/serious severities.

-- 
Matthias Andree
--- ./fetchmail.c.orig	2006-08-21 01:39:54.0 +0200
+++ ./fetchmail.c	2006-08-21 01:37:47.0 +0200
@@ -577,7 +577,7 @@
 set_signal_handler(SIGINT, terminate_run);
 set_signal_handler(SIGTERM, terminate_run);
 set_signal_handler(SIGALRM, terminate_run);
-set_signal_handler(SIGPIPE, terminate_run);
+set_signal_handler(SIGPIPE, SIG_IGN);
 set_signal_handler(SIGQUIT, terminate_run);
 
 /* here's the exclusion lock */
--- ./driver.c.orig	2006-08-21 01:37:09.0 +0200
+++ ./driver.c	2006-08-21 01:40:41.0 +0200
@@ -55,7 +55,6 @@
 
 /* throw types for runtime errors */
 #define THROW_TIMEOUT	1		/* server timed out */
-#define THROW_SIGPIPE	2		/* SIGPIPE on stream socket */
 
 /* magic values for the message length array */
 #define MSGLEN_UNKNOWN	0		/* length unknown (0 is impossible) */
@@ -113,13 +112,6 @@
 	idletimeout = 1;
 }
 
-static RETSIGTYPE sigpipe_handler (int signal)
-/* handle SIGPIPE signal indicating a broken stream socket */
-{
-(void)signal;
-longjmp(restart, THROW_SIGPIPE);
-}
-
 #define CLEANUP_TIMEOUT 60 /* maximum timeout during cleanup */
 
 static int cleanupSockClose (int fd)
@@ -856,9 +848,6 @@
 alrmsave = set_signal_handler(SIGALRM, timeout_handler);
 mytimeout = ctl-server.timeout;
 
-/* set up the broken-pipe timeout */
-pipesave = set_signal_handler(SIGPIPE, sigpipe_handler);
-
 if ((js = setjmp(restart)))
 {
 	/* exception caught */
@@ -878,14 +867,7 @@
 	sigprocmask(SIG_UNBLOCK, allsigs, NULL);
 #endif /* HAVE_SIGPROCMASK */
 	
-	if (js == THROW_SIGPIPE)
-	{
-	set_signal_handler(SIGPIPE, SIG_IGN);
-	report(stdout,
-		   GT_(SIGPIPE thrown from an MDA or a stream socket error\n));
-	wait(0);
-	}
-	else if (js == THROW_TIMEOUT)
+	if (js == THROW_TIMEOUT)
 	{
 	if (phase == OPEN_WAIT)
 		report(stdout,
@@ -1581,7 +1563,6 @@
 
 set_timeout(0); /* cancel any pending alarm */
 set_signal_handler(SIGALRM, alrmsave);
-set_signal_handler(SIGPIPE, pipesave);
 return(err);
 }
 

Bug#382450: marked as done (Root on (lvm-)crypto-md doesn't work)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382450: fixed in mdadm 2.5.3.git200608202239-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: cryptsetup
Version: 1.0.3-3

I'm interested in running an encrypted root partition, specifically
where root is a logical volume on dm-crypt on raid1 md.  The nightly
build of the Debian installer (2006-08-09) is willing to build this
setup without complaint.  However, when booting into the new system, the
cryptroot script fails to properly open the encrypted md partition.

Here's the system layout since it's a little confusing:

/dev/hda2, /dev/hda3= /dev/md0   (raid1) (testing only)
/dev/md0= /dev/mapper/crypt0 (dm-crypt)
/dev/mapper/crypt0  = ep.root(volume group)
/dev/mapper/ep.root-ep.root = /  (jfs formatted logical volume)

I've read through some of the other bug reports (#371846 and others) and
there seems to be some discussion on properly determining device
dependencies, but as far as I can tell a general solution hasn't been
developed yet.  Is this the right answer?  Or is it possible to hack md
support into cryptroot as was done for lvm?

Here's a console dump of the machine attempting to boot for the first
time, the bottom four lines repeat indefinitely:

Linux version 2.6.17-1-686 (Debian 2.6.17-5) ([EMAIL PROTECTED]) (gcc version 
4.1.2 20060715 (prerelease) (Debian 4.1.1-9)) #1 SMP Sat Jul 29 15:32:47 UTC 
2006
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f000 (usable)
 BIOS-e820: 0009f000 - 000a (reserved)
 BIOS-e820: 0010 - 1ffae000 (usable)
 BIOS-e820: 1ffae000 - 2000 (reserved)
 BIOS-e820: feda - fee0 (reserved)
 BIOS-e820: ffb0 - 0001 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
DMI 2.3 present.
ACPI: PM-Timer IO Port: 0x808
Allocating PCI resources starting at 3000 (gap: 2000:deda)
Built 1 zonelists
Kernel command line: root=/dev/mapper/ep.root-ep.root ro console=ttyS0
Local APIC disabled by BIOS -- you can enable it with lapic
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Detected 1295.994 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 511036k/523960k available (1478k kernel code, 12380k reserved, 540k 
data, 164k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2594.25 BogoMIPS (lpj=5188501)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 1024K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 16k freed
ACPI: setting ELCR to 0200 (from 0800)
CPU0: Intel(R) Pentium(R) M processor 1300MHz stepping 05
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 5337k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfc96e, last bus=2
Setting up standard PCI resources
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (:00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 0880-08bf claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller :00:1f.1
PCI: Transparent bridge - :00:1e.0
PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
PCI: Bus #07 (-#0a) is hidden behind transparent bridge #02 (-#02) (try 
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *11
ACPI: PCI 

Processed: downgrading severity

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 severity 383935 important
Bug#383935: mozilla-locale-fr: depends on mozilla
Severity set to `important' from `serious'

 block 383935 by 382907
Bug#383935: mozilla-locale-fr: depends on mozilla
Was not blocked by any bugs.
Blocking bugs of 383935 added: 382907

 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#382480: marked as done (FTBFS: dh-installudev only in recent debhelper)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382480: fixed in mdadm 2.5.3.git200608202239-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: mdadm
Version: 2.5.2-10
Severity: serious
Justification: Policy 4.2

As subject says, dh-installudev is only available with most recent versions of 
debhelper, so 
requires a tightened build-dependency on debhelper.

According to debhelper changelog, dh-installudev was introduced in version 
5.0.24, and improved 
in version 5.0.32. So the degree of tightening of the versioned 
build-dependency depends on 
wether that later improvement is crucial for mdadm.


Thanks for maintaining this important tool!


 - Jonas

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-powerpc
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)

---End Message---
---BeginMessage---
Source: mdadm
Source-Version: 2.5.3.git200608202239-1

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

mdadm-udeb_2.5.3.git200608202239-1_i386.udeb
  to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-1_i386.udeb
mdadm_2.5.3.git200608202239-1.diff.gz
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.diff.gz
mdadm_2.5.3.git200608202239-1.dsc
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.dsc
mdadm_2.5.3.git200608202239-1_i386.deb
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1_i386.deb
mdadm_2.5.3.git200608202239.orig.tar.gz
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239.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.
martin f. krafft [EMAIL PROTECTED] (supplier of updated mdadm 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.7
Date: Mon, 21 Aug 2006 00:25:22 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 2.5.3.git200608202239-1
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers [EMAIL PROTECTED]
Changed-By: martin f. krafft [EMAIL PROTECTED]
Description: 
 mdadm  - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 381057 381303 382263 382389 382450 382480 382876 383688 383806 383891
Changes: 
 mdadm (2.5.3.git200608202239-1) unstable; urgency=low
 .
   * Tracking upstream git releases.
 - now the --run switch behaves as stated in the manpage. This properly
   fixes #287415
 - new version-1 partitionable arrays are now named X instead of _dX (e.g.
   0 instead of _d0) for device names like md_dX. I actually think this is
   a bug and hope upstream will use dX (e.g. d0) instead in a future
   version.
 - we specify --symlink=no and thus disable the new feature to create
   /dev/mdX symlinks to /dev/md/X devices until the entire device node mess
   is cleared up. No need to introduce yet another complicating factor at
   this stage.
   * Instead of trying to do a whole lot of magic with respect to detecting
 RAID devices to start, mdadm from now on requires a valid mdadm.conf file
 to be installed. It still tries to do what it can, but there are no
 heuristics anymore. See /usr/share/doc/mdadm/README.upgrading-2.5.3 .
   * Removed the zero-superblock warning because we require the user to sign
 off the configuration file anyway.
   * This also enables us to use mdadm.conf from the initial ramdisk and thus
 closes: #381303.
   * In case the user chooses to assemble all arrays from the initial ramdisk,
 use the new homehost feature of mdadm (closes: #381057). This will start
 only those arrays belonging to the local system, unless it is the first
 run on a system, in which case it will start all arrays and mark them as
 belonging to the local system.
   * Improved the debconf control script: integrated error messages into the
   

Bug#383688: marked as done (udev: /dev/md? missing)

[Debian Bug Tracking System]

Your message dated Sun, 20 Aug 2006 17:02:13 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382450: fixed in mdadm 2.5.3.git200608202239-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

---BeginMessage---
Package: udev
Version: 0.097-1
Severity: critical
Justification: breaks the whole system

device nodes for kernel autoconfigured raid arrays are not created.
This causes my LVM volume group to not be found and thus all my
filesystems (such as /usr /var /home) are nto availible.
I believe this bug will also affect systems where /usr and friends
have their own md device (i.e. lvm not involved)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages udev depends on:
ii  initscripts  2.86.ds1-15 Scripts for initializing and 
shutt
ii  libc62.3.6-19GNU C Library: Shared libraries
ii  libselinux1  1.30.26-2   SELinux shared libraries
pn  libvolume-id0none  (no description available)
ii  lsb-base 3.1-14  Linux Standard Base 3.1 init 
scrip

udev recommends no packages.

---End Message---
---BeginMessage---
Source: mdadm
Source-Version: 2.5.3.git200608202239-1

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

mdadm-udeb_2.5.3.git200608202239-1_i386.udeb
  to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-1_i386.udeb
mdadm_2.5.3.git200608202239-1.diff.gz
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.diff.gz
mdadm_2.5.3.git200608202239-1.dsc
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.dsc
mdadm_2.5.3.git200608202239-1_i386.deb
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1_i386.deb
mdadm_2.5.3.git200608202239.orig.tar.gz
  to pool/main/m/mdadm/mdadm_2.5.3.git200608202239.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.
martin f. krafft [EMAIL PROTECTED] (supplier of updated mdadm 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.7
Date: Mon, 21 Aug 2006 00:25:22 +0100
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source i386
Version: 2.5.3.git200608202239-1
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers [EMAIL PROTECTED]
Changed-By: martin f. krafft [EMAIL PROTECTED]
Description: 
 mdadm  - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 381057 381303 382263 382389 382450 382480 382876 383688 383806 383891
Changes: 
 mdadm (2.5.3.git200608202239-1) unstable; urgency=low
 .
   * Tracking upstream git releases.
 - now the --run switch behaves as stated in the manpage. This properly
   fixes #287415
 - new version-1 partitionable arrays are now named X instead of _dX (e.g.
   0 instead of _d0) for device names like md_dX. I actually think this is
   a bug and hope upstream will use dX (e.g. d0) instead in a future
   version.
 - we specify --symlink=no and thus disable the new feature to create
   /dev/mdX symlinks to /dev/md/X devices until the entire device node mess
   is cleared up. No need to introduce yet another complicating factor at
   this stage.
   * Instead of trying to do a whole lot of magic with respect to detecting
 RAID devices to start, mdadm from now on requires a valid mdadm.conf file
 to be installed. It still tries to do what it can, but there are no
 heuristics anymore. See /usr/share/doc/mdadm/README.upgrading-2.5.3 .
   * Removed the zero-superblock warning because we require the user to sign
 off the configuration file anyway.
   * This also enables us to use mdadm.conf from the initial ramdisk and thus
 closes: #381303.
   * In case the user chooses to assemble all arrays from the initial ramdisk,
 use the new homehost feature of mdadm (closes: