Bug#401665: FTBFS on mipsel

[Jérôme Marant]

Le mardi 12 décembre 2006 16:46, Andreas Barth a écrit :

> As described in the developers reference:
> http://www.debian.org/doc/developers-reference/ch-resources.en.html#s-dchroot
> 
> However, apt sources don't seem to be too current there. If there is
> anything I can help you on "my" mipsel-machine, please say so.

Could you please perform a fresh unpacking of the package, and then try:

cd emacs21-21.4a+1
fakeroot debian/rules autofiles-sync

and build the package.

Thanks in advance.

-- 
Jérôme Marant

Bug#402009: libcommoncpp2-dev library transition proposal (Fwd: Bug#402009: Multiple API-incompatible changes in Common C++ 1.5.3)

[Steve Langasek]

Hi Mark,

On Sat, Dec 09, 2006 at 10:24:48AM +, Mark Purcell wrote:
> On Saturday 09 December 2006 10:10, Mark Purcell wrote:
> > The alternative, which is better, is just to back out the library
> > transition.

> Or even better-better, just don't do the library transition at all.

> The current state of libcommoncpp2 (1.5.1) and rdepends in etch is stable and 
> supportable. Thus nothing needs to be done, prior to release.

Is it certain that all the packages in testing that depend on
libcommoncpp2-1.5-0 are using the old 1.5.1 ABI?  Apparently 1.5.3-1 didn't
bump shlibs either, because there are no reverse-deps waiting on it for
propogation...  Since this package was only 7 days old at the time of
freeze, odds are good that nothing built against the new ABI made it into
testing, but that's not a guarantee.

> > Upload the previous ABI stable release 1.5.1 with an epoc and await the
> > release of etch..

> I won't upload to unstable with an epoc..  Also please ignore, or rather just 
> leave in NEW, the last upload (1.5.3) which does correctly carry forward the 
> soname change.. But is not necessary for etch.

There's no reason that it needs to stay in NEW that I can see, but we don't
make that decision anyway. :)

Cheers,
-- 
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/


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

Bug#400215: solution....

[Alex Owen]

From memory of other udev rule installing pkgs the file is installed

into "/etc/udev/nut-usbups.rules" and the symlink is made in
"/etc/udev/rules.d"

Regards
Alex Owen


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

Processed: Elevate severity of Bug#397584 (iproute-dev)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 397584 grave
Bug#397584: iproute-dev: ip_common.h references unknown symbols RTA_TABLE, 
RTA_DATA
Severity set to `grave' from `normal'

> tags 397584 + patch
Bug#397584: iproute-dev: ip_common.h references unknown symbols RTA_TABLE, 
RTA_DATA
There were no tags set.
Tags added: patch

> 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#400215: solution....

[Alex Owen]

tags 400215 + patch
thanks

Attached is a patch that should fix this... [untested I'm afraid].




On 13/12/06, Alex Owen <[EMAIL PROTECTED]> wrote:

From memory of other udev rule installing pkgs the file is installed
into "/etc/udev/nut-usbups.rules" and the symlink is made in
"/etc/udev/rules.d"

Regards
Alex Owen

--- debian/rules.rao.orig	2006-12-13 09:16:11.0 +
+++ debian/rules	2006-12-13 09:19:10.0 +
@@ -91,7 +91,7 @@
 		DESTDIR=$(CURDIR)/debian/nut-usb RUNUID=65534 RUNGID=65534
 	mkdir -p $(CURDIR)/debian/nut-usb/etc/udev/rules.d
 	install -m 644 $(CURDIR)/scripts/hotplug-ng/nut-usbups.rules \
-		$(CURDIR)/debian/nut-usb/etc/udev/rules.d/025_nut-usbups.rules
+		$(CURDIR)/debian/nut-usb/etc/udev/nut-usbups.rules
 	$(MAKE) install-cgi \
 		DESTDIR=$(CURDIR)/debian/nut-cgi RUNUID=65534 RUNGID=65534
 	mv $(CURDIR)/debian/nut/lib/nut/upsdrvctl $(CURDIR)/debian/nut/sbin

Bug#401791: xcdroast: Invalid mkisofs version

[Norbert Schulz]

Package: xcdroast
Version: 0.98+0alpha15-10
Followup-For: Bug #401791

starting xcdroast gives the following error:

$ xcdroast

** (xcdroast:8965): WARNING **: Invalid mkisofs version -unknown- found.
Expecting at least version 1.15a17
Start xcdroast with the -n option to override (not recommended!)

$

starting with the -n option gives the error which is reported on top of this 
report

Norbert Schulz



-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-7-shark.rotorwerk-2
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages xcdroast depends on:
ii  cdda2wav 9:1.1.0-1   Dummy transition package for iceda
ii  debconf [debconf-2.0]1.5.8   Debian configuration management sy
ii  libatk1.0-0  1.12.3-1The ATK accessibility toolkit
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libcairo21.2.4-4 The Cairo 2D vector graphics libra
ii  libfontconfig1   2.4.1-2 generic font configuration library
ii  libglib2.0-0 2.12.4-2The GLib library of C routines
ii  libgtk2.0-0  2.8.20-3The GTK+ graphical user interface 
ii  libpango1.0-01.14.8-2Layout and rendering of internatio
ii  libx11-6 2:1.0.3-4   X11 client-side library
ii  libxcursor1  1.1.7-4 X cursor management library
ii  libxext6 1:1.0.1-2   X11 miscellaneous extension librar
ii  libxfixes3   1:4.0.1-5   X11 miscellaneous 'fixes' extensio
ii  libxi6   1:1.0.1-4   X11 Input extension library
ii  libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library
ii  libxrandr2   2:1.1.0.2-5 X11 RandR extension library
ii  libxrender1  1:0.9.1-3   X Rendering Extension client libra
ii  mkisofs  9:1.1.0-1   Dummy transition package for genis
ii  wodim9:1.1.0-1   command line CD/DVD writing tool

xcdroast recommends no packages.

-- debconf information:
  xcdroast/can_use_normal_user: false


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

Processed: Re: solution....

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 400215 + patch
Bug#400215: 025_nut-usbups.rules is a broken symlink (and that breaks newhidups)
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#401258: Reclose bug

[Peter Palfrader]

On Wed, 13 Dec 2006, Brian May wrote:

> > "Peter" == Peter Palfrader <[EMAIL PROTECTED]> writes:
> 
> Peter> Actually, this is really bad.
> 
> Peter> It means the lines do _not_ get added on iditial
> Peter> installations:
> 
> Yes, as I worked out, too.
> 
> Thanks for letting me know; I have now replaced the -n with a -z in
> version -8.

Now hprop gets disabled again in upgrades from sarge to etch, and when
the package is removed - not purged - the services still are enabled.

Both of these issues would have been fixed with my version of the patch.

Peter
-- 
   |  .''`.  ** Debian GNU/Linux **
  Peter Palfrader  | : :' :  The  universal
 http://www.palfrader.org/ | `. `'  Operating System
   |   `-http://www.debian.org/


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

Bug#402071: marked as done (botan1.4: FTBFS if /proc *is* mounted [amd64])

[Debian Bug Tracking System]

Your message dated Wed, 13 Dec 2006 10:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402071: fixed in botan1.4 1.4.12-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)

--- Begin Message ---
Package: botan1.4
Version: 1.4.12-1
Severity: grave
Justification: fails to build from source

botan1.4 uses a crappy perl code which reads /proc/cpuinfo to detect
host type instead of standard config.guess/config.sub. This result on a
false detection of an athlon instead of an athlon64 when /proc is
mounted. It builds fine however with /proc/ unmounted.

This also explain why this package does not build on mips/mipsel (but
that's not RC).


[EMAIL PROTECTED] a écrit :
> Automatic build of botan1.4_1.4.12-1 on qa by sbuild/amd64 85
> Build started at 20061202-0134
> **
> Checking available source versions...
> Fetching source files...
> Reading package lists...
> Building dependency tree...
> Need to get 1810kB of source archives.
> Get:1 http://debian.aurel32.net etch/main botan1.4 1.4.12-1 (dsc) [641B]
> Get:2 http://debian.aurel32.net etch/main botan1.4 1.4.12-1 (tar) [1801kB]
> Get:3 http://debian.aurel32.net etch/main botan1.4 1.4.12-1 (diff) [7618B]
> Fetched 1810kB in 0s (6789kB/s)
> Download complete and in download only mode
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 4), libbz2-dev, libgmp3-dev, libssl-dev, perl, 
> zlib1g-dev
> Checking for already installed source dependencies...
> debhelper: missing
> Using default version 5.0.42
> libbz2-dev: missing
> libgmp3-dev: missing
> libssl-dev: missing
> perl: already installed (5.8.8-6.1)
> zlib1g-dev: missing
> Checking for source dependency conflicts...
>   /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install 
> debhelper libbz2-dev libgmp3-dev libssl-dev zlib1g-dev
> Reading package lists...
> Building dependency tree...
> The following extra packages will be installed:
>   file gettext gettext-base html2text intltool-debian libgmp3c2 libgmpxx4
>   libmagic1 po-debconf
> Suggested packages:
>   dh-make cvs gettext-doc libgmp3-doc libmpfr-dev
> Recommended packages:
>   curl wget lynx libmail-sendmail-perl libcompress-zlib-perl
> The following NEW packages will be installed:
>   debhelper file gettext gettext-base html2text intltool-debian libbz2-dev
>   libgmp3-dev libgmp3c2 libgmpxx4 libmagic1 libssl-dev po-debconf zlib1g-dev
> 0 upgraded, 14 newly installed, 0 to remove and 2 not upgraded.
> Need to get 0B/6927kB of archives.
> After unpacking 21.1MB of additional disk space will be used.
> WARNING: The following packages cannot be authenticated!
>   gettext-base libmagic1 file html2text gettext intltool-debian po-debconf
>   debhelper libbz2-dev libgmp3c2 libgmpxx4 libgmp3-dev zlib1g-dev libssl-dev
> Authentication warning overridden.
> Selecting previously deselected package gettext-base.
> (Reading database ... 10374 files and directories currently installed.)
> Unpacking gettext-base (from .../gettext-base_0.15-3_amd64.deb) ...
> Selecting previously deselected package libmagic1.
> Unpacking libmagic1 (from .../libmagic1_4.17-4_amd64.deb) ...
> Selecting previously deselected package file.
> Unpacking file (from .../archives/file_4.17-4_amd64.deb) ...
> Selecting previously deselected package html2text.
> Unpacking html2text (from .../html2text_1.3.2a-3_amd64.deb) ...
> Selecting previously deselected package gettext.
> Unpacking gettext (from .../gettext_0.15-3_amd64.deb) ...
> Selecting previously deselected package intltool-debian.
> Unpacking intltool-debian (from 
> .../intltool-debian_0.35.0+20060710.1_all.deb) ...
> Selecting previously deselected package po-debconf.
> Unpacking po-debconf (from .../po-debconf_1.0.7_all.deb) ...
> Selecting previously deselected package debhelper.
> Unpacking debhelper (from .../debhelper_5.0.42_all.deb) ...
> Selecting previously deselected package libbz2-dev.
> Unpacking libbz2-dev (from .../libbz2-dev_1.0.3-6_amd64.deb) ...
> Selecting previously deselected package libgmp3c2.
> Unpacking libgmp3c2 (from .../libgmp3c2_2%3a4.2.1+dfsg-4_amd64.deb) ...
> Selecting previously deselected package libgmpxx4.
> Unpacking libgmpxx4 (from .../libgmpxx4_2%3a4.2.1+dfsg-4_amd64.deb) ...
> Selecting previously deselected package libgmp3-dev.
> Unpacking libgmp3-dev (from .../libgmp3-dev_2%3a4.2.1+dfsg-4_amd64.deb) ...
> Selecting previously deselected package zlib1g-dev.
> Unpacking zlib1g-dev (from .../zlib1g-dev_1%3a1.2.3

Bug#402073: marked as done (Log for failed build of botan1.5_1.5.11-1 (dist=testing))

[Debian Bug Tracking System]

Your message dated Wed, 13 Dec 2006 10:47:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402073: fixed in botan1.5 1.5.13-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)

--- Begin Message ---
Package: botan1.5
Version: 1.5.11-1
Severity: grave
Justification: fails to build from source

botan1.5 uses a crappy perl code which reads /proc/cpuinfo to detect
host type instead of standard config.guess/config.sub. This result on a
false detection of an athlon instead of an athlon64 when /proc is
mounted. It builds fine however with /proc/ unmounted.

This also explain why this package does not build on mips/mipsel (but
that's not RC).


[EMAIL PROTECTED] a écrit :
> Automatic build of botan1.5_1.5.11-1 on qa by sbuild/amd64 85
> Build started at 20061202-0134
> **
> Checking available source versions...
> Fetching source files...
> Reading package lists...
> Building dependency tree...
> Need to get 1381kB of source archives.
> Get:1 http://debian.aurel32.net etch/main botan1.5 1.5.11-1 (dsc) [641B]
> Get:2 http://debian.aurel32.net etch/main botan1.5 1.5.11-1 (tar) [1373kB]
> Get:3 http://debian.aurel32.net etch/main botan1.5 1.5.11-1 (diff) [7265B]
> Fetched 1381kB in 0s (7025kB/s)
> Download complete and in download only mode
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 4), libbz2-dev, libgmp3-dev, libssl-dev, perl, 
> zlib1g-dev
> Checking for already installed source dependencies...
> debhelper: missing
> Using default version 5.0.42
> libbz2-dev: missing
> libgmp3-dev: missing
> libssl-dev: missing
> perl: already installed (5.8.8-6.1)
> zlib1g-dev: missing
> Checking for source dependency conflicts...
>   /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install 
> debhelper libbz2-dev libgmp3-dev libssl-dev zlib1g-dev
> Reading package lists...
> Building dependency tree...
> The following extra packages will be installed:
>   file gettext gettext-base html2text intltool-debian libgmp3c2 libgmpxx4
>   libmagic1 po-debconf
> Suggested packages:
>   dh-make cvs gettext-doc libgmp3-doc libmpfr-dev
> Recommended packages:
>   curl wget lynx libmail-sendmail-perl libcompress-zlib-perl
> The following NEW packages will be installed:
>   debhelper file gettext gettext-base html2text intltool-debian libbz2-dev
>   libgmp3-dev libgmp3c2 libgmpxx4 libmagic1 libssl-dev po-debconf zlib1g-dev
> 0 upgraded, 14 newly installed, 0 to remove and 2 not upgraded.
> Need to get 0B/6927kB of archives.
> After unpacking 21.1MB of additional disk space will be used.
> WARNING: The following packages cannot be authenticated!
>   gettext-base libmagic1 file html2text gettext intltool-debian po-debconf
>   debhelper libbz2-dev libgmp3c2 libgmpxx4 libgmp3-dev zlib1g-dev libssl-dev
> Authentication warning overridden.
> Selecting previously deselected package gettext-base.
> (Reading database ... 10374 files and directories currently installed.)
> Unpacking gettext-base (from .../gettext-base_0.15-3_amd64.deb) ...
> Selecting previously deselected package libmagic1.
> Unpacking libmagic1 (from .../libmagic1_4.17-4_amd64.deb) ...
> Selecting previously deselected package file.
> Unpacking file (from .../archives/file_4.17-4_amd64.deb) ...
> Selecting previously deselected package html2text.
> Unpacking html2text (from .../html2text_1.3.2a-3_amd64.deb) ...
> Selecting previously deselected package gettext.
> Unpacking gettext (from .../gettext_0.15-3_amd64.deb) ...
> Selecting previously deselected package intltool-debian.
> Unpacking intltool-debian (from 
> .../intltool-debian_0.35.0+20060710.1_all.deb) ...
> Selecting previously deselected package po-debconf.
> Unpacking po-debconf (from .../po-debconf_1.0.7_all.deb) ...
> Selecting previously deselected package debhelper.
> Unpacking debhelper (from .../debhelper_5.0.42_all.deb) ...
> Selecting previously deselected package libbz2-dev.
> Unpacking libbz2-dev (from .../libbz2-dev_1.0.3-6_amd64.deb) ...
> Selecting previously deselected package libgmp3c2.
> Unpacking libgmp3c2 (from .../libgmp3c2_2%3a4.2.1+dfsg-4_amd64.deb) ...
> Selecting previously deselected package libgmpxx4.
> Unpacking libgmpxx4 (from .../libgmpxx4_2%3a4.2.1+dfsg-4_amd64.deb) ...
> Selecting previously deselected package libgmp3-dev.
> Unpacking libgmp3-dev (from .../libgmp3-dev_2%3a4.2.1+dfsg-4_amd64.deb) ...
> Selecting previously deselected package zlib1g-dev.
> Unpacking zlib1g-dev (from .../zlib1g-dev_1%3a1.2.3

Bug#402886: icedove has become highly unstable - 2 to 3 hangs per day

[Eric Lavarde]

Package: icedove
Version: 1.5.0.8.dfsg1-1
Severity: grave


Hi,

since upgrade to the dfsg version, I already had to kill and restart
icedove already ~5 times since yesterday.
Phenomens are very different but it always ends with a hang :-/
I already had a few times icedove stopping to show the content of the
emails: I was switching from one folder to the next, and from one
message to the next, but icedove showed always the same email content.
Today, I had icedove hanging while trying to send an email, and I could
capture part of the strace story; I noticed that icedove complained
about files already existing though it created them itself. I then tried to
remove the temporary files while icedove was running. It went a bit
further but continued to hang, at which point I killed it.

I set the severity to grave because it's currently not feasible to work
properly with icedove, and I don't think it should go to stable like it
is.

Thanks, Eric

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

Versions of packages icedove depends on:
ii  debconf [debconf-2.0]  1.5.8 Debian configuration management sy
ii  libatk1.0-01.12.3-1  The ATK accessibility toolkit
ii  libc6  2.3.6.ds1-8   GNU C Library: Shared libraries
ii  libcairo2  1.2.4-4   The Cairo 2D vector graphics libra
ii  libfontconfig1 2.4.1-2   generic font configuration library
ii  libgcc11:4.1.1-19GCC support library
ii  libglib2.0-0   2.12.4-2  The GLib library of C routines
ii  libgtk2.0-02.8.20-3  The GTK+ graphical user interface 
ii  libjpeg62  6b-13 The Independent JPEG Group's JPEG 
ii  libpango1.0-0  1.14.8-2  Layout and rendering of internatio
ii  libpng12-0 1.2.13-4  PNG library - runtime
ii  libstdc++6 4.1.1-19  The GNU Standard C++ Library v3
ii  libx11-6   2:1.0.3-4 X11 client-side library
ii  libxcursor11.1.7-4   X cursor management library
ii  libxext6   1:1.0.1-2 X11 miscellaneous extension librar
ii  libxfixes3 1:4.0.1-5 X11 miscellaneous 'fixes' extensio
ii  libxft22.1.8.2-8 FreeType-based font drawing librar
ii  libxi6 1:1.0.1-4 X11 Input extension library
ii  libxinerama1   1:1.0.1-4.1   X11 Xinerama extension library
ii  libxrandr2 2:1.1.0.2-5   X11 RandR extension library
ii  libxrender11:0.9.1-3 X Rendering Extension client libra
ii  libxt6 1:1.0.2-2 X11 toolkit intrinsics library
ii  myspell-de-de [myspell-dic 20051113-5German dictionary for myspell
ii  myspell-en-gb [myspell-dic 1:2.0.4~rc1-3 English_british dictionary for mys
ii  myspell-en-us [myspell-dic 1:2.0.4~rc1-3 English_american dictionary for my
ii  myspell-fr-gut [myspell-di 1:1.0-18  The French dictionary for myspell 
ii  myspell-pl [myspell-dictio 20060618-1The Polish dictionary for myspell
ii  zlib1g 1:1.2.3-13compression library - runtime

icedove recommends no packages.

-- debconf information:
* icedove/browser: Debian
[... not anymore on the console ...]
1 EEXIST (File exists)
open("/tmp/nscopy-8.tmp", O_WRONLY|O_CREAT|O_TRUNC|O_EXCL|O_LARGEFILE, 0600) = 
-1 EEXIST (File exists)
open("/tmp/nscopy-9.tmp", O_WRONLY|O_CREAT|O_TRUNC|O_EXCL|O_LARGEFILE, 0600) = 
-1 EEXIST (File exists)
open("/tmp/nscopy-10.tmp", O_WRONLY|O_CREAT|O_TRUNC|O_EXCL|O_LARGEFILE, 0600) = 
-1 EEXIST (File exists)
[... always the same going from 11 to 183 ...]
open("/tmp/nscopy-184.tmp", O_WRONLY|O_CREAT|O_TRUNC|O_EXCL|O_LARGEFILE, 0600) 
= -1 EEXIST (File exists)
open("/tmp/nscopy-185.tmp", O_WRONLY|O_CREAT|O_TRUNC|O_EXCL|O_LARGEFILE, 0600) 
= -1 EEXIST (File exists)
open("/tmp/nscopy-186.tmp", O_WRONLY|O_CREAT|O_TRUNC|O_EXCL|O_LARGEFILE, 0600) 
= -1 EEXIST (File exists)
open("/tmp/nscopy-187.tmp", O_WRONLY|O_CREAT|O_TRUNC|O_EXCL|O_LARGEFILE, 0600) 
= 29
close(29)   = 0
open("/tmp/nscopy-187.tmp", O_WRONLY|O_CREAT|O_LARGEFILE, 0600) = 29
lseek(29, 0, SEEK_CUR)  = 0
lseek(29, 0, SEEK_END)  = 0
lseek(29, 0, SEEK_SET)  = 0
open("/tmp/nsmail.eml", O_RDONLY|O_LARGEFILE) = -1 EMFILE (Too many open files)
fsync(29)   = 0
close(29)   = 0
gettimeofday({1166006079, 955338}, NULL) = 0
pipe(0x1b4fdcac)= -1 EMFILE (Too many open files)
open("/home/ericl/.mozilla-thunderbird/91rz7vke.default/extensions.ini", 
O_RDONLY) = 29
fstat64(29, {st_mode=S_IFREG|0644, st_siz

Bug#402887: linux-uvc-source: doesn't build on 2.6.19

[Ritesh Raj Sarraf]

Package: linux-uvc-source
Version: 0.1.0.svn54-3
Severity: serious
Justification: no longer builds from source
X-Debbugs-Cc: [EMAIL PROTECTED]


I'm using vanilla 2.6.19 (2.6.19 is not in Debian yet) and linux-uvc
doesn't build.

Here's the build log:

[EMAIL PROTECTED]:/usr/src/modules/linux-uvc $ sudo debian/rules binary-modules
Password:
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.19-xps/g'` ; \
  done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in} 
${templ%.modules.in}.backup 2>/dev/null || true; \
sed -e 's/##KVERS##/2.6.19-xps/g ;s/#KVERS#/2.6.19-xps/g ; 
s/_KVERS_/2.6.19-xps/g ; s/##KDREV##//g ; s/#KDREV#//g ; s/_KDREV_//g  ' < 
$templ > ${templ%.modules.in}; \
  done
dh_testdir
dh_testroot
dh_clean -k
# Build modules
/usr/bin/make -C /usr/src/modules/linux-uvc uvcvideo \
KERNEL_DIR=/usr/src/linux KERNEL_VERSION=2.6.19-xps 
KERNELCONF=/usr/src/linux/.config
make[1]: Entering directory `/usr/src/modules/linux-uvc'
Building USB Video Class driver...
make[2]: Entering directory `/usr/src/linux-headers-2.6.19-xps'
  CC [M]  /usr/src/modules/linux-uvc/uvcvideo.o
In file included from /usr/src/modules/linux-uvc/uvcvideo.c:49:
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:8: error: nested redefinition 
of ‘enum v4l2_frmsizetypes’
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:8: error: redeclaration of ‘enum 
v4l2_frmsizetypes’
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:9: error: redeclaration of 
enumerator ‘V4L2_FRMSIZE_TYPE_DISCRETE’
include/linux/videodev2.h:286: error: previous definition 
of ‘V4L2_FRMSIZE_TYPE_DISCRETE’ was here
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:10: error: redeclaration of 
enumerator ‘V4L2_FRMSIZE_TYPE_CONTINUOUS’
include/linux/videodev2.h:287: error: previous definition 
of ‘V4L2_FRMSIZE_TYPE_CONTINUOUS’ was here
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:11: error: redeclaration of 
enumerator ‘V4L2_FRMSIZE_TYPE_STEPWISE’
include/linux/videodev2.h:288: error: previous definition 
of ‘V4L2_FRMSIZE_TYPE_STEPWISE’ was here
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:14: error: nested redefinition 
of ‘enum v4l2_frmivaltypes’
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:14: error: redeclaration of ‘enum 
v4l2_frmivaltypes’
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:15: error: redeclaration of 
enumerator ‘V4L2_FRMIVAL_TYPE_DISCRETE’
include/linux/videodev2.h:326: error: previous definition 
of ‘V4L2_FRMIVAL_TYPE_DISCRETE’ was here
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:16: error: redeclaration of 
enumerator ‘V4L2_FRMIVAL_TYPE_CONTINUOUS’
include/linux/videodev2.h:327: error: previous definition 
of ‘V4L2_FRMIVAL_TYPE_CONTINUOUS’ was here
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:17: error: redeclaration of 
enumerator ‘V4L2_FRMIVAL_TYPE_STEPWISE’
include/linux/videodev2.h:328: error: previous definition 
of ‘V4L2_FRMIVAL_TYPE_STEPWISE’ was here
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:24: error: redefinition 
of ‘struct v4l2_frmsize_discrete’
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:32: error: redefinition 
of ‘struct v4l2_frmsize_stepwise’
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:52: error: redefinition 
of ‘struct v4l2_frmsizeenum’
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:73: error: redefinition 
of ‘struct v4l2_frmival_stepwise’
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:84: error: redefinition 
of ‘struct v4l2_frmivalenum’
In file included from /usr/src/modules/linux-uvc/uvcvideo.c:49:
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:116:1: 
warning: "VIDIOC_ENUM_FRAMESIZES" redefined
In file included from include/linux/videodev.h:15,
 from /usr/src/modules/linux-uvc/uvcvideo.c:38:
include/linux/videodev2.h:1329:1: warning: this is the location of the 
previous definition
In file included from /usr/src/modules/linux-uvc/uvcvideo.c:49:
/usr/src/modules/linux-uvc/v4l2_enumfrmfmt.h:117:1: 
warning: "VIDIOC_ENUM_FRAMEINTERVALS" redefined
In file included from include/linux/videodev.h:15,
 from /usr/src/modules/linux-uvc/uvcvideo.c:38:
include/linux/videodev2.h:1330:1: warning: this is the location of the 
previous definition
/usr/src/modules/linux-uvc/uvcvideo.c: In function ‘uvc_init_isoc’:
/usr/src/modules/linux-uvc/uvcvideo.c:1612: warning: assignment from 
incompatible pointer type
/usr/src/modules/linux-uvc/uvcvideo.c: In function ‘uvc_init_status’:
/usr/src/modules/linux-uvc/uvcvideo.c:3814: warning: passing argument 6 
of ‘usb_fill_int_urb’ from incompatible pointer type
make[3]: *** [/usr/src/modules/linux-uvc/uvcvideo.o] Error 1
make[2]: *** [_module_/usr/src/modules/linux-uvc] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.19-xps'
make[1]: *** [uvcvideo] Error 2
make[1]: Leaving directory `/usr/src/modules/linux-uvc'
make: *** [binary-modules] Error 2


Thanks,
Ritesh

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (550, 'unstable'), (500

Processed (with 1 errors): tomcat5.5: blocks on startup until log pipe is read

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> clone 402603 -1 -2
Bug#402603: tomcat5.5: blocks on startup until log pipe is read
Bug 402603 cloned as bugs 402878-402879.

> reassing -1 jsvc
Unknown command or malformed arguments to command.

> retitle -1 jsvc: add option to redirect output to syslog
Bug#402878: tomcat5.5: blocks on startup until log pipe is read
Changed Bug title.

> severity -1 wishlist
Bug#402878: jsvc: add option to redirect output to syslog
Severity set to `wishlist' from `serious'

> retitle -2 tomcat5.5: send catalina's stdout to syslog
Bug#402879: tomcat5.5: blocks on startup until log pipe is read
Changed Bug title.

> severity -2 wishlist
Bug#402879: tomcat5.5: send catalina's stdout to syslog
Severity set to `wishlist' from `serious'

> block -2 by -1
Bug#402879: tomcat5.5: send catalina's stdout to syslog
Was not blocked by any bugs.
Blocking bugs of 402879 added: 402878

> tag 402603 pending
Bug#402603: tomcat5.5: blocks on startup until log pipe is read
Tags were: help
Tags added: pending

> 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#402899: kvm-source doesn't compile with 2.6.19

[Ritesh Raj Sarraf]

Package: kvm-source
Version: 5-2
Severity: serious
Justification: no longer builds from source
X-Debbugs-CC: [EMAIL PROTECTED]

kvm-source doesn't build with linux 2.6.19 (vanilla at the moment).

Thanks,
Ritesh

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (550, 'unstable'), (500, 'stable'), 
(350, 'experimental'), (50, 'feisty')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19-xps
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages kvm-source depends on:
ii  bzip2 1.0.3-6high-quality block-sorting file 
co
ii  debhelper 5.0.42 helper programs for debian/rules
ii  make  3.81-2 The GNU version of the "make" 
util
ii  module-assistant  0.10.8 tool to make module package 
creati

kvm-source recommends no packages.

-- no debconf information

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
"Stealing logic from one person is plagiarism, stealing from many is 
research."
"The great are those who achieve the impossible, the petty are those who 
cannot - rrs"


pgp9HwLJJyBiG.pgp
Description: PGP signature

Processed: Re: Bug#402817: cannot purge twiki

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 402817 serious
Bug#402817: cannot purge twiki
Severity set to `serious' from `normal'

> 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#402898: /etc/bogofilter.cf should define UTF-8 as default charset since it is Debian's default

[Teemu Likonen]

Package: bogofilter
Version: 1.1.3-1
Severity: serious

I report this as "serious" because this _should_ be fixed before Etch is
released. This bug causes bogofilter to work incorrectly in UTF-8
systems (which is Etch's default).

Debian Etch uses UTF-8 locales and charset as default. Bogofilter uses
ISO-8859-1 as the system default. This usually causes garbage words to
user's ~/.bogofilter/wordlist.db since the default charset for
_database_ is Unicode/UTF-8.

To reproduce:


Use UTF-8 locale:

$ locale
LANG=fi_FI.UTF-8
LC_CTYPE="fi_FI.UTF-8"
LC_NUMERIC="fi_FI.UTF-8"
LC_TIME="fi_FI.UTF-8"
LC_COLLATE="fi_FI.UTF-8"
LC_MONETARY="fi_FI.UTF-8"
LC_MESSAGES=en_US.UTF-8
LC_PAPER="fi_FI.UTF-8"
LC_NAME="fi_FI.UTF-8"
LC_ADDRESS="fi_FI.UTF-8"
LC_TELEPHONE="fi_FI.UTF-8"
LC_MEASUREMENT="fi_FI.UTF-8"
LC_IDENTIFICATION="fi_FI.UTF-8"
LC_ALL=


Use Bogofilter's default system charset (or define it to some
other 8 bit charset):
  charset_default=iso-8859-1
Use Bogofilter's default word database charset (Unicode/UTF-8):
  unicode=yes

(These can be defined in /etc/bogofilter.cf or ~/.bogofilter.cf)


Some background information: letter "ä" is U+00E4 LATIN SMALL LETTER
A WITH DIAERESIS and in UTF-8 encoding it takes two bytes: $c3 $a4.


$ mv ~/.bogofilter/wordlist.db ~/wordlist.db-backup
$ echo "äiti" | bogofilter -n
$ bogoutil -d ~/.bogofilter/wordlist.db
head:äiti 0 1 20061213

This example shows that the letter "ä" is encoded _twice_ with UTF-8.
The command "echo" prints letter "ä" encoded with UTF-8, Bogofilter
thinks it is in ISO-8859-1 and encodes both bytes separately: $c3
becomes "Ã" (U+00C3 LATIN CAPITAL LETTER A WITH TILDE) and $a4 becomes
"¤" (U+00A4 CURRENCY SIGN).

Having lines
  charset_default=utf-8
  unicode=yes
in /etc/bogofilter.cf file characters are encoded correctly.


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-3-k7
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)

Versions of packages bogofilter depends on:
ii  bogofilter-bdb1.1.3-1a fast Bayesian spam filter (Berke

bogofilter recommends no packages.

-- no debconf information

Bug#402897: module is not loaded in apache2.2

[Jan Dittberner]

Package: php5-ming
Version: 1:0.3.0-9+b2
Severity: grave
Justification: renders package unusable



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

Versions of packages php5-ming depends on:
ii  libapache2-mod-php5 [phpapi 5.2.0-7  server-side, HTML-embedded
scripti
ii  libc6   2.3.6.ds1-8  GNU C Library: Shared libraries
ii  libming01:0.3.0-9+b2 Library to generate SWF
(Flash) Fi
ii  php5-cli [phpapi-20060613]  5.2.0-7  command-line interpreter for
the p

php5-ming recommends no packages.

-- no debconf information

The apache error log contains the following line:

PHP Warning:  PHP Startup: Unable to load dynamic library
'/usr/lib/php5/20060613/ming.so' - /usr/lib/php5/20060613/ming.so:
undefined symbol: zim_swfmovie_protect in Unknown on line 0


Regards
Jan Dittberner







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

Bug#401265: iceape: Contains trademarked artwork and names

[Alexander Sack]

On Sat, Dec 02, 2006 at 09:55:13AM +0100, Mike Hommey wrote:
> Package: iceape
> Version: 1.0.6-1
> Severity: serious
> 
> The package contains the name and logos for seamonkey in some places. It
> also contains the name and logos for sunbird.

>From the discussion on gnuzilla list, I am not unsure whether you
would be ok with having the sed extended remove.nonfree as a quick
fix for now/etch?

Please comment,

 - Alexander
-- 
 GPG messages preferred.|  .''`.  ** Debian GNU/Linux **
 Alexander Sack | : :' :  The  universal
 [EMAIL PROTECTED]| `. `'  Operating System
 http://www.asoftsite.org/  |   `-http://www.debian.org/


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

Bug#402886: icedove has become highly unstable - 2 to 3 hangs per day

[Alexander Sack - Debian Bugmail]

On Wed, Dec 13, 2006 at 12:52:55PM +0100, Eric Lavarde wrote:
> Package: icedove
> Version: 1.5.0.8.dfsg1-1
> Severity: grave
> 
> 
> Hi,
> 
> since upgrade to the dfsg version, I already had to kill and restart
> icedove already ~5 times since yesterday.
> Phenomens are very different but it always ends with a hang :-/
> I already had a few times icedove stopping to show the content of the
> emails: I was switching from one folder to the next, and from one
> message to the next, but icedove showed always the same email content.
> Today, I had icedove hanging while trying to send an email, and I could
> capture part of the strace story; I noticed that icedove complained
> about files already existing though it created them itself. I then tried to
> remove the temporary files while icedove was running. It went a bit
> further but continued to hang, at which point I killed it.
> 
> I set the severity to grave because it's currently not feasible to work
> properly with icedove, and I don't think it should go to stable like it
> is.
> 

Please backup your .mozilla-thunderbird directory.

If you have done this, please compact your folders (right button on
folder -> Compact ...)  and see if it fixes your problem. If that does
not help, remove the .msf files of the folders that cause the
troubles and see if that helps.

Please be responsive ... otherwise, I will have to downgrade severity
and see if others report the same problem (which I might do anyway).


 - Alexander

 p.s. please take care that the bug is listed as To: or CC: when 
  replying to this mail (e.g. /reply-all/). 
-- 
 GPG messages preferred.   |  .''`.  ** Debian GNU/Linux **
 Alexander Sack| : :' :  The  universal
 [EMAIL PROTECTED]   | `. `'  Operating System
 http://www.asoftsite.org  |   `-http://www.debian.org/


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

Bug#402829: mantis: not supportable by the security team

[Thijs Kinkhorst]

On Wed, 2006-12-13 at 09:49 +0100, "schönfeld / in-medias-res.com"
wrote:
> I quiet understand the etch release policy and I am sure that there are
> cases where 5a matches the case. But in the case of mantis it does *not*
> match. Because there is currently *one* open security issue which where
> just reported and which I'm willing to fix in duration of this day. The
> package *has* a maintainer and it is not out of date or is *too buggy*.

I think I can say something about this issue. I've been the one actually
providing the mantis security updates in the sarge lifetime of the
package.

I've observed the following:
- There were many, many security problems with mantis in the sarge
  release cyle;
- Upstream did not provide significant details of vulnerabilities, or
  patches. Also they did not respond to repeated requests from me for
  that information.

> It makes me somehow angry that i invested so much work in bringing
> mantis back in a good shape, when people can block its release by just
> saying 'hey it had a bad history'.

You did not add here that the first result of this work only entered
Debian a couple of weeks ago. While I do value the fact that you've been
fixing up the package, the few weeks do not give much time to get a
reliable indication of whether the package has made a radical change.

>  Given the information by Moritz that
> it had 21 vulnerabilities it should be worth to mention that almost 50%
> of the bugs I've seen affected almost dusty versions of mantis that are
> *far* away from the current release.

I'm sorry, but I do not buy this. I've fixed a large number of bugs in
the sarge version of Mantis. The sarge version is 1.5 years old. That
can hardly be called "far away" or "dusty", can it?

This is about the same lifetime as expected for etch, so if mantis gets
obsolete that fast, we're better off not packaging it.

> Also most of the bugs has been fixed upstream in a reasonable time
> and i can *not* confirm that mantis developers do hide details of
> bug fixes.

I *can*, having worked on actual sarge security updates.

> In fact they use their own bug tracker to track fixes for bugs and
> the most of the security issues are IMO documented and discussed
> there well enough to backport/implement security fixes into current
> debian packages.

They keep bugs closed and requests to open up or to get more
information, even after an updated version has been released, are met
with absolute silence.

Maybe this attitude has changed radically in the past couple of months.
Do you have concrete evidence that they did in fact change their policy
of handling security issues? And that the code base structurally
improved the last 1.5 years?

Please provide it then. I do not think it's convincing to use arguments
like "it was just dusty" to support your point. Debian had the most
recent version of mantis when sarge released. This didn't seem to be
quite immune from vulnerabilities.

> Lastly i wanted to note that IMO using statistical numbers that are by
> *no way* representative isn't really a good base for arguing with a poor
> user base. And given you do trust that this 40 counted users are a
> representative number: For this 40 counted users mantis might be *very*
> important. And it might be even more. There might be hundred that do not
>  participate in popcon.

But this goes for any other package aswell - the point is that these
numbers can be seen in a relative way: there's a lot of packages that
have way higher numbers. The security team only has a fixed amount of
time available to support them. If a package has an exceptionally high
amount of work compared to a relatively low usage number, this can be a
valid argument.

> I would like to further discuss this topic and hopely we could find a
> con sense.

Sure, I really hope we can get the mantis package in a good shape. I'm
also all for giving a second chance to previously leaky software to
change their habits.

But that *does* require concrete evidence that something has indeed
changed. Especially if you're requesting something like this *very*
shortly before the release, with little time to revert any mistakes.

It's up to you now: show why mantis deserves the second chance, and why
it's essential that it deserves it, at this point, instead of e.g. for
Lenny.

By the way, I cannot stress too much that I really appreciate your work
of getting the sid version in order. I'm just wary to put it in a stable
version just a few weeks after.


Thijs


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

Bug#402545: compiz/terminal bug

[Thierry Reding]

* Christian Müller wrote:
> hello. when i switch back from console to X(.Org 7.1 with nvidia drivers
> 1-0.9631) with compiz (0.2.2-1) it crashes the window decorations, AS
> SOON AS lots of rams are used, i.e. got a browser with 4-5 tabs open,
> plus amarok, plus kopete etc. if only one or no apps are running that
> problem does not happen. on the other hand, beryl (with most plugins
> deactived) does NOT have that issue (i don't consider it stable either
> though). So I guess it's a compiz bug.

I cannot reproduce this bug on my notebook with an Intel graphics chipset, so
it's not necessarily a compiz bug. You could try compiz 0.3.4, which you can
get by running:

$ git-clone http://git.debian.org/git/pkg-xorg/app/compiz.git

That seems to fix the problem partially. You can build debian packages from
that by changing to the 'compiz' directory and running dpkg-buildpackage.
Also it may be necessary to run

$ apt-get build-dep compiz

before trying to build the package.

Thierry



signature.asc
Description: Digital signature

Processed (with 5 errors): Re: [Pkg-xfce-devel] Bug#402708: xfce fails to start

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign #402708 xfce4-session
Bug#402708: xfce fails to start
Bug reassigned from package `xfce4' to `xfce4-session'.

> retitle #402708 xfce4-session doesn't start without xfce4-session.rc
Bug#402708: xfce fails to start
Changed Bug title.

> severity #402708 serious
Bug#402708: xfce4-session doesn't start without xfce4-session.rc
Severity set to `serious' from `normal'

> thanks,
Unknown command or malformed arguments to command.

> Current xfce4-session in sid doesn't ship a xfce4-session.rc. It's
Unknown command or malformed arguments to command.

> required for startup, as it ship the Failsafe Session, which is the
Unknown command or malformed arguments to command.

> default one when no session was previously started.
Unknown command or malformed arguments to command.

> xfce4-session doesn't ship the xfce4-session.rc like before
Unknown command or malformed arguments to command.

Too many unknown commands, stopping 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#400215: nut-usbups.rules being overriden by a symlink

[Arnaud Quette]

2006/12/2, Carlos Rodrigues <[EMAIL PROTECTED]>:

I decided to further investigate this matter, as the nut-usb package
seems to be effectively broken while this remains unfixed.

From looking into the package's diff file
(http://ftp.debian.org/debian/pool/main/n/nut/nut_2.0.4-2.3.diff.gz),
I noticed this two changes:

In "nut-2.0.4/debian/rules":

+   install -m 644 $(CURDIR)/scripts/hotplug-ng/nut-usbups.rules \
+   $(CURDIR)/debian/nut-usb/etc/udev/rules.d/025_nut-usbups.rules

And, in "nut-2.0.4/debian/nut-usb.postinst":

+  configure)
+if [ -d /etc/udev/rules.d/ ] ; then
+cd /etc/udev/rules.d/
+ln -sf ../nut-usbups.rules 025_nut-usbups.rules
+fi

So, it looks to me like the file "025_nut-usbups.rules" is being
installed correctly, but then (in the postinst stage) it is overriden
by a symlink pointing to a nonexistent file.

So, either the file is installed into "/etc/udev/nut-usbups.rules" to
fix the symlink, or the symlink isn't created at all.

Am I correct?


right, I thought I've mentionned this, but the file would better be
installed as /etc/udev/rules.d/025_nut-usbups.rules, removing the
symlink creation in nut-usb.postinst.

@Steinar: while we're at it, would you be interested in co maintaining
these packages? I would be really glad if you accept ;-)

Thanks to you all,
Arnaud (young dady again, still more than busy)
--
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


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

Bug#402817: cannot purge twiki

[svendowideit]

gads!

you're working so fast, i can't keep up!

thankyou again.

Sven

> severity 402817 serious
> thanks
>
> Hi Olivier,
>
> Olivier Berger wrote:
>> I think that code modifying the apache config should probably go into
>> the prerm, and the postrm should then only contain the db_purge,
>> maybe?
>
> Thanks for reporting this. I am increasing the severity as this problem
> should not be included in Etch :)
>
> Expect a fix soon!
>
> --
>   ·''`. If I can't dance to it, it's not my revolution
>  : :' :-- Emma Goldman
>  `. `'   Proudly running Debian GNU/Linux (unstable)
>`- www.amayita.com  www.malapecora.com  www.chicasduras.com
>




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

Processed: tagging 402898

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.26
> tags 402898 + etch
Bug#402898: /etc/bogofilter.cf should define UTF-8 as default charset since it 
is Debian's default
There were no tags set.
Tags added: etch

>
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#400215: nut-usbups.rules being overriden by a symlink

[Steinar H. Gunderson]

On Wed, Dec 13, 2006 at 02:56:33PM +0100, Arnaud Quette wrote:
> @Steinar: while we're at it, would you be interested in co maintaining
> these packages? I would be really glad if you accept ;-)

I do not even have an UPS, so sorry. :-)

/* Steinar */
-- 
Homepage: http://www.sesse.net/


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

Bug#389163: How to handle filename conflict "aleph" (Packages aleph, tetex-bin, texlive-bin)?

[Frank Küster]

Andreas Barth <[EMAIL PROTECTED]> wrote:

> Why is it better than to drop aleph? If a package is way outdated, and
> RC buggy, and also aleph is practically unchanged since Sarge, I think
> that is still grounds for a removal.

I haven't investigated about aleph. I just thought that, since it
doesn't have many bugs, even the current version might be useful, and
better than nothing.

If Thomas packages afnix (together with Paul or separately), that's
probably the best choice.  From a technical point of view, the package
names could also stay the same, so that we don't need to wait for NEW
processing (but you RMs might have a magic wand to speed up that?)

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

Bug#382757: Remove this package (and thats an order! :)

[Paul Davis]

Free - you *CANNOT* distribute this package. Torben and I have made this
very clear. Please remove it ASAP. It is a violation of our intent and
of the GPL to distribute it. 

If and when Steinberg changes the license for the VSTSDK, things will
change. Until then, it has to be removed. Please do it.

--p



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

Bug#402817: cannot purge twiki

[Amaya]

[EMAIL PROTECTED] wrote:
> you're working so fast, i can't keep up!

I am just doing the "paperwork" here.
Please fix this bug, and I will happily sponsor your package ;)

-- 
  ·''`. If I can't dance to it, it's not my revolution
 : :' :-- Emma Goldman
 `. `'   Proudly running Debian GNU/Linux (unstable)
   `- www.amayita.com  www.malapecora.com  www.chicasduras.com

Processed: Re: Bug#402416: 2.6.18-3 fails to boot (failure during root fs mount)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 402416 important
Bug#402416: linux-image-2.6.18-3-686: 2.6.18-3 fails to boot (failure during 
root fs mount)
Severity set to `important' from `critical'

> reassign 402416 mdadm
Bug#402416: linux-image-2.6.18-3-686: 2.6.18-3 fails to boot (failure during 
root fs mount)
Bug reassigned from package `linux-image-2.6.18-3-686' to `mdadm'.

> 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: severity of 374834 is serious

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.26
> # Justification: breaks install/upgrade of all packages that trigger 
> update-menus (on at least three systems)
> severity 374834 serious
Bug#374834: menu: update-menus hangs every once a while
Severity set to `serious' from `normal'

>
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#402917: xterm: Man page is incorrect regarding allowWindowOps

[Kevin L]

Package: xterm
Severity: grave

This is a side effect of bug 384593 regarding allowWindowOps which is now 
closed.  I have listed the severity as grave because bug 384593 was listed as 
grave, and this new bug is a direct continuation of that one.

In bug 384593, the resource allowWindowOps was changed from default value true 
to false to prevent shell exploits.  However the current xterm man page 
indicates that the standard behavior is still true:

  allowWindowOps (class AllowWindowOps)
   Specifies whether extended window control sequences (as used in
   dtterm) for should be allowed.  The default is ``true.''

The man page needs to be changed to reflect the Debian-specific behavior.  I 
suggest changing the text from "The default is ``true.''" to "For security 
reasons, the default in Debian is ``false.''"

As the developer of a console-based terminal emulator that I tend to run 
inside Xterm, this behavior surprised me.  Fortunately, the user can fix it 
and I have added documentation to my project accordingly.

As it stands now, Debian has made a behavior change to Xterm that deviates 
from the "expected" (e.g. what is true most other places) default behavior 
and the man page explicitly contradicts the Debian behavior.  This is also 
not mentioned in /usr/share/doc/xterm/README.Debian, perhaps it should be if 
this will be a departure from upstream for a significant time.

$ dpkg -p xterm
Package: xterm
Priority: optional
Section: x11
Installed-Size: 980
Maintainer: Debian X Strike Force 
Architecture: i386
Version: 222-1
...


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

Bug#393323: marked as done (resolvconf: initscript should be inoperative if package uninstalled)

[Debian Bug Tracking System]

Your message dated Wed, 13 Dec 2006 14:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393323: fixed in resolvconf 1.37
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)

--- Begin Message ---
Package: resolvconf
Version: 1.35
Severity: normal

When booting after a recent update on an etch system, I get the
following message:

Setting up resolvconf...run-parts: /etc/resolvonf/update.d/libc exited
with return code 1
failed.

The last line was in red (ooo!). Looking at
/etc/resolvonf/update.d/libc, I see that the script failed because
/lib/resolvconf/list-records is missing. Since the libc file is in the
resolvconf package, I see two solutions:

1. If /lib/resolvconf/list-records is optional, then the libc script
   should exit with status 0 if the command is missing.

2. If it is required, then the resolveconf package should install
   list-records, or provide the required dependency.

I suppose the output of run-parts should have redirected to /dev/null to
clean up the boot message:

Setting up resolvconf...failed.

Thanks, Thomas. You sure do get around ;-).


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

Versions of packages resolvconf depends on:
ii  coreutils 5.97-5 The GNU core utilities
ii  debconf [debconf-2.0] 1.5.5  Debian configuration management sy
ii  lsb-base  3.1-15 Linux Standard Base 3.1 init scrip

resolvconf recommends no packages.

-- 
Bill Wohler <[EMAIL PROTECTED]>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD

--- End Message ---
--- Begin Message ---
Source: resolvconf
Source-Version: 1.37

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

resolvconf_1.37.dsc
  to pool/main/r/resolvconf/resolvconf_1.37.dsc
resolvconf_1.37.tar.gz
  to pool/main/r/resolvconf/resolvconf_1.37.tar.gz
resolvconf_1.37_all.deb
  to pool/main/r/resolvconf/resolvconf_1.37_all.deb



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

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

Debian distribution maintenance software
pp.
Marco Nenciarini <[EMAIL PROTECTED]> (supplier of updated resolvconf 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: Wed, 13 Dec 2006 15:13:02 +0100
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 1.37
Distribution: unstable
Urgency: high
Maintainer: resolvconf maintainers <[EMAIL PROTECTED]>
Changed-By: Marco Nenciarini <[EMAIL PROTECTED]>
Description: 
 resolvconf - nameserver information handler
Closes: 391953 393323 402678
Changes: 
 resolvconf (1.37) unstable; urgency=high
 .
   [ Thomas Hood ]
   * initscript: Don't do anything if resolvconf is removed
 (Closes: #393323)
   * Update ja.po thanks to Hideki Yamane  (Closes: #391953)
   * Add es.po thanks to Javier Fernández-Sanguino Peña
 (Closes: #402678)
 .
   [ Marco Nenciarini ]
   * Urgency set to high due to RC bug fix.
Files: 
 d95639150dbc76ee97981b20a2deccb1 736 net optional resolvconf_1.37.dsc
 d6aec9e204674de97b272384305eb320 70614 net optional resolvconf_1.37.tar.gz
 72d4ef88dc07c9f70dfe02a2da9cbc6e 62458 net optional resolvconf_1.37_all.deb

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

iD8DBQFFgAxwaGRzDfCV5eQRAs/dAJ4srGR2OskLFeDQQGIRphU9CB9s0gCePthX
8kyatIRS92u472FPzMxZXxU=
=3vsO
-END PGP SIGNATURE-

--- End Message ---

Bug#389163: How to handle filename conflict "aleph" (Packages aleph, tetex-bin, texlive-bin)?

[Paul Cager]

Frank Küster wrote:
> Andreas Barth <[EMAIL PROTECTED]> wrote:
> 
>> Why is it better than to drop aleph? If a package is way outdated, and
>> RC buggy, and also aleph is practically unchanged since Sarge, I think
>> that is still grounds for a removal.
> 
> I haven't investigated about aleph. I just thought that, since it
> doesn't have many bugs, even the current version might be useful, and
> better than nothing.
> 
> If Thomas packages afnix (together with Paul or separately), that's
> probably the best choice.  From a technical point of view, the package
> names could also stay the same, so that we don't need to wait for NEW
> processing (but you RMs might have a magic wand to speed up that?)
> 
> Regards, Frank

It is probably worth pointing out that AFNIX isn't just Aleph with a new
name - the language and system has moved on considerably since the final
Aleph release in 2003 (see http://www.afnix.org/htm/desc.htm). So I
would not expect the upstream author to be too happy with a Debian
version of AFNIX called Aleph, or vice-versa.

I'm very new to Debian packaging and it's likely to take me a lot longer
to package AFNIX than an experienced developer (and the chances of
errors in my packaging is a lot higher). So if you need an AFNIX package
quickly I would be more than happy to stand aside and let an experienced
developer at it - you are welcome to use my work on it so far, or start
from scratch at your discretion.

Having said that, I do not think it is sensible to regard AFNIX as a new
upstream version of Aleph - it is more like a totally new package as so
much of the build system and runtime are different. Would it be wise to
rush it into Etch (even with a competent developer packaging it!)

Just for background information, I chose to package AFNIX partly because
I wanted to take my time and learn more about packaging non-trivial
systems - no-one would be in any rush for the AFNIX package, would they?
Just shows how wrong I can be

Let me know what you think.

Thanks,
Paul

Bug#402926: atlas-dev: missing 'cblas.h'

[Mikkel Ejrnaes]

Package: atlas-dev
Version: atlas3-headers
Severity: grave
Justification: renders package unusable


Compilation using atlas3 fails because there is no cblas.h file 
installed.

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


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

Bug#402922: segfault in mplayer own mpeg2 library

[Pierre Habouzit]

Package: mplayer
Version: 1.0~rc1-2
Severity: grave
Tags: security
Justification: user security hole

  While playing http://madism.org/~madcoder/pub/foobar.mpeg mplayer
segfaults, somewhere in mpeg2_idct_copy_mmx.

  xine and vlc that use debian libpmeg2 instead do not segfault.


  I'm not 100% sure it's a security problem, but it's very likely.




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

Versions of packages mplayer depends on:
ii  debconf1.5.10Debian configuration management sy
ii  libartsc0  1.5.5-1   aRts sound system C support librar
ii  libasound2 1.0.13-1  ALSA library
ii  libatk1.0-01.12.3-1  The ATK accessibility toolkit
ii  libaudio2  1.8-2 The Network Audio System (NAS). (s
ii  libaudiofile0  0.2.6-6   Open-source version of SGI's audio
ii  libc6  2.3.6.ds1-9   GNU C Library: Shared libraries
ii  libcairo2  1.2.4-4   The Cairo 2D vector graphics libra
ii  libcdparanoia0 3.10+debian~pre0-4audio extraction tool for sampling
ii  libconfhelper-perl 0.12.5Library for editing configuration 
ii  libdirectfb-0.9-25 0.9.25.1-5direct frame buffer graphics - sha
ii  libdv4 1.0.0-1   software library for DV format dig
ii  libdvdread30.9.7-2   library for reading DVDs
ii  libesd00.2.36-3  Enlightened Sound Daemon - Shared 
ii  libfontconfig1 2.4.2-1   generic font configuration library
ii  libfreetype6   2.2.1-5   FreeType 2 font engine, shared lib
ii  libglib2.0-0   2.12.4-2  The GLib library of C routines
ii  libgtk2.0-02.8.20-3  The GTK+ graphical user interface 
ii  libjpeg62  6b-13 The Independent JPEG Group's JPEG 
ii  liblircclient0 0.8.0-9   LIRC client library
ii  libmad00.15.1b-2.1   MPEG audio decoder library
ii  libncurses55.5-5 Shared libraries for terminal hand
ii  libogg01.1.3-2   Ogg Bitstream Library
ii  libpango1.0-0  1.14.8-2  Layout and rendering of internatio
ii  libpng12-0 1.2.15~beta5-0PNG library - runtime
ii  libsdl1.2debian1.2.11-7  Simple DirectMedia Layer
ii  libsvga1   1:1.4.3-24console SVGA display libraries
ii  libtheora0 0.0.0.alpha7.dfsg-1.1 The Theora Video Compression Codec
ii  libungif4g 4.1.4-4   shared library for GIF images
ii  libx11-6   2:1.0.3-4 X11 client-side library
ii  libxcursor11.1.7-4   X cursor management library
ii  libxext6   1:1.0.1-2 X11 miscellaneous extension librar
ii  libxfixes3 1:4.0.1-5 X11 miscellaneous 'fixes' extensio
ii  libxi6 1:1.0.1-4 X11 Input extension library
ii  libxinerama1   1:1.0.1-4.1   X11 Xinerama extension library
ii  libxrandr2 2:1.1.0.2-5   X11 RandR extension library
ii  libxrender11:0.9.1-3 X Rendering Extension client libra
ii  libxt6 1:1.0.2-2 X11 toolkit intrinsics library
ii  libxv1 1:1.0.2-1 X11 Video extension library
ii  libxvmc1   1:1.0.2-2 X11 Video extension library
ii  libxxf86dga1   2:1.0.1-2 X11 Direct Graphics Access extensi
ii  libxxf86vm11:1.0.1-2 X11 XFree86 video mode extension l
ii  zlib1g 1:1.2.3-13compression library - runtime

Versions of packages mplayer recommends:
ii  mplayer-skin-blue [mplayer-sk 1.6-1  blue skin for mplayer

-- debconf information:
  mplayer/voutput: autodetect
  mplayer/rtc: false
  mplayer/ttfont: /usr/share/fonts/truetype/ttf-thryomanes/thryi___.ttf 
* mplayer/cfgnote:
  mplayer/replace-existing-files-bail:
  mplayer/replace-existing-files: true
  mplayer/no-ttfont:
  mplayer/install_codecs:
* mplayer/dvd_device: /dev/cdrom


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

Bug#402786: marked as done (xawtv: includes GPL-incompatible code from Open Motif)

[Debian Bug Tracking System]

Your message dated Wed, 13 Dec 2006 15:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402786: fixed in xawtv 3.95.dfsg.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)

--- Begin Message ---
Package: xawtv
Version: 3.95-6
Severity: serious
Tags: patch

common/RegEdit.c, common/RegEdit.h, and common/RegEditI.h come from
Open Motif, and have a GPL-incompatible license:

COPYRIGHT NOTICE
Copyright (c) 1990, 1991, 1992, 1993 Open Software Foundation, Inc.
Copyright (c) 1996, 1997, 1998, 1999, 2000 The Open Group
ALL RIGHTS RESERVED (MOTIF).  See the file named COPYRIGHT.MOTIF for
the full copyright text.

This software is subject to an open license. It may only be
used on, with or for operating systems which are themselves open
source systems. You must contact The Open Group for a license
allowing distribution and sublicensing of this software on, with,
or for operating systems which are not Open Source programs.

See http://www.opengroup.org/openmotif/license for full
details of the license agreement. Any use, reproduction, or
distribution of the program constitutes recipient's acceptance of
this agreement.

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS
PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY
WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT
NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE
EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

Basically, these files consist of a lint-cleaned copy of the X11R5
editres implementation and a single-line wrapper, XmdRegisterEditres.
I'm guessing they were distributed separately because this wasn't
available in X11R4.

Switching to equivalent functionality in libxmu6 comes down to
replacing

#include "RegEdit.h"
...
XmdRegisterEditres(shell_widget);

with code from :

#include 
...
XtAddEventHandler(shell_widget, (EventMask) 0, True,
  (XtEventHandler) _XEditResCheckMessages, NULL);

(plus `-lXmu' on the link line).

In the case of xawtv, the Motif applications that use this (motv, mtt)
have already been separated into a non-free motv package.  xawtv will
build fine if we just repackage xawtv_3.95.orig.tar.gz without
common/RegEdit*.  (I'd do this myself, but I've lost my key.)

Thanks,

Matej

--- End Message ---
--- Begin Message ---
Source: xawtv
Source-Version: 3.95.dfsg.1-1

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

alevtd_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/alevtd_3.95.dfsg.1-1_i386.deb
fbtv_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/fbtv_3.95.dfsg.1-1_i386.deb
pia_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/pia_3.95.dfsg.1-1_i386.deb
radio_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/radio_3.95.dfsg.1-1_i386.deb
scantv_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/scantv_3.95.dfsg.1-1_i386.deb
streamer_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/streamer_3.95.dfsg.1-1_i386.deb
ttv_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/ttv_3.95.dfsg.1-1_i386.deb
v4l-conf_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/v4l-conf_3.95.dfsg.1-1_i386.deb
webcam_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/webcam_3.95.dfsg.1-1_i386.deb
xawtv-plugins_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/xawtv-plugins_3.95.dfsg.1-1_i386.deb
xawtv-tools_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/xawtv-tools_3.95.dfsg.1-1_i386.deb
xawtv_3.95.dfsg.1-1.diff.gz
  to pool/main/x/xawtv/xawtv_3.95.dfsg.1-1.diff.gz
xawtv_3.95.dfsg.1-1.dsc
  to pool/main/x/xawtv/xawtv_3.95.dfsg.1-1.dsc
xawtv_3.95.dfsg.1-1_i386.deb
  to pool/main/x/xawtv/xawtv_3.95.dfsg.1-1_i386.deb
xawtv_3.95.dfsg.1.orig.tar.gz
  to pool/main/x/xawtv/xawtv_3.95.dfsg.1.orig.tar.gz



A summary of the changes between this version and the previo

Bug#402817: cannot purge twiki

[svendowideit]

sweet :) expect a fix tomorrow

Sven

> [EMAIL PROTECTED] wrote:
>> you're working so fast, i can't keep up!
>
> I am just doing the "paperwork" here.
> Please fix this bug, and I will happily sponsor your package ;)
>
> --
>   ·''`. If I can't dance to it, it's not my revolution
>  : :' :-- Emma Goldman
>  `. `'   Proudly running Debian GNU/Linux (unstable)
>`- www.amayita.com  www.malapecora.com  www.chicasduras.com
>




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

Processed: fix severity

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 402917 minor
Bug#402917: xterm: Man page is incorrect regarding allowWindowOps
Severity set to `minor' from `grave'

>
End of message, stopping processing here.

Please contact me if you need assistance.

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


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

Bug#402693: Apollon doesn't start saying that there's no libapollon.so.0

[Anthony Towns]

> The debian/rules script removes libapollon.so.0 during installation
> claiming that it is statically linked. These bug reports suggest that it
> is _not_ statically linked and therefore necessary. I attach a patch
> which just leaves the library file in the apollon package; NMU debs and
> source with this change can be found at [...]

An alternative fix which forces it to be statically linked is to add:

DEB_CONFIGURE_EXTRA_FLAGS = --enable-static --disable-shared

to the debian/rules file. It seems to work for me, fwiw.

Cheers,
aj


signature.asc
Description: Digital signature

Bug#401263: closed by Andreas Barth <[EMAIL PROTECTED]> (Has been fixed)

[Jan Evert van Grootheest]

I confirm that 46.4 fixes the bug.
It seems that the /var/cache/apt/*.bin files are regenerated when 
invalid ones are found.


Many thanks!

Jan Evert



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

Bug#402920: mplayer FTBFS with DEB_BUILD_OPTS=debug

[A Mennucc]

severity 402920 normal
tag 402920 unreproducible
thanks

Pierre Habouzit ha scritto:
> Package: mplayer
> Version: 1.0~rc1-2

your mplayer version is quite old; current one is 1.0~rc1-7

> Severity: serious

why? I checked into debian-policy 10.1 :
http://www.debian.org/doc/debian-policy/ch-files.html
> For this reason, it is recommended to support the 
> standardized environment variable DEB_BUILD_OPTIONS.

DEB_BUILD_OPTIONS is a recommendation of policy, not a requirement.

I also found out that "debug" is not in the list of options.
See http://bugs.debian.org/157131

I will update that to 'noopt'


> 
>   attach is the relevant build log part.
>   the build was done on an x86 box (not the one I report the bug from).
> 

I cannot rerpoduce this (and I tried on AMD64)

a.



signature.asc
Description: OpenPGP digital signature

Bug#402922: segfault in mplayer own mpeg2 library

[A Mennucc]

here is some more info:

$ gdb ./mplayer
This GDB was configured as "x86_64-linux-gnu"...Using host libthread_db
library "/lib/libthread_db.so.1".

(gdb) run ~/mplayer/bench/foobar.mpeg

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47190863550720 (LWP 1368)]
MC_put_o_16_mmxext (dest=0xcb5f00 "", ref=0x0, stride=304, height=16)
at motion_comp_mmx.c:546
546 movq_m2r (*ref, mm0);
(gdb) li
541
542 static inline void MC_put1_16 (int height, uint8_t * dest, const
uint8_t * ref,
543const int stride)
544 {
545 do {
546 movq_m2r (*ref, mm0);
547 movq_m2r (*(ref+8), mm1);
548 ref += stride;
549 movq_r2m (mm0, *dest);
550 movq_r2m (mm1, *(dest+8));

we should understand why  ref==0

anyway I will add an assert

a.



signature.asc
Description: OpenPGP digital signature

Bug#401047: imagemagick: [AMD64] FTBFS with recent libpng.

[Daniel Kobras]

On Wed, Dec 13, 2006 at 12:48:11AM +0100, Daniel Kobras wrote:
> On Tue, Dec 12, 2006 at 11:15:24PM +0100, Kurt Roeckx wrote:
> > What is the status of this bug?
> > 
> > It seems libpng was fixed, but it's now still failing to build
> > and needs the patch.
> 
> I'm currently preparing an NMU and will try to get it uploaded tomorrow.
> (Plus an upload of graphicsmagick that suffers from the same problem.)

See attached the changes in NMU 6.2.4.5.dfsg1-0.13 that I intend to
upload shortly to fix the FTBFS error on amd64.

Regards,

Daniel.

diff -u imagemagick-6.2.4.5.dfsg1/debian/changelog 
imagemagick-6.2.4.5.dfsg1/debian/changelog
--- imagemagick-6.2.4.5.dfsg1/debian/changelog
+++ imagemagick-6.2.4.5.dfsg1/debian/changelog
@@ -1,3 +1,13 @@
+imagemagick (7:6.2.4.5.dfsg1-0.13) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * coders/png.c: Fix amd64 build failure with recent libpng versions.
+Closes: #401047
+  * debian/control: Tighten libpng12-dev build-dependency to exclude versions
+that are known to fail to link even with the above fix in place.
+
+ -- Daniel Kobras <[EMAIL PROTECTED]>  Wed, 13 Dec 2006 11:33:25 +0100
+
 imagemagick (7:6.2.4.5.dfsg1-0.12) unstable; urgency=high
 
   * Non-maintainer upload.
diff -u imagemagick-6.2.4.5.dfsg1/debian/control 
imagemagick-6.2.4.5.dfsg1/debian/control
--- imagemagick-6.2.4.5.dfsg1/debian/control
+++ imagemagick-6.2.4.5.dfsg1/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Ryuichi Arafune <[EMAIL PROTECTED]>
 Standards-Version: 3.7.2
-Build-Depends: libjpeg62-dev, libbz2-dev, libtiff4-dev, libwmf-dev (>= 
0.2.7-1), libz-dev, libpng12-dev, libx11-dev, libxt-dev, libxext-dev, debhelper 
(>> 3.0.5), libxml2-dev, libfreetype6-dev, liblcms1-dev, libexif-dev, perl (>= 
5.8.0-3), libjasper-1.701-dev, libltdl3-dev, graphviz (>= 2.8), gs-gpl, 
pkg-config
+Build-Depends: libjpeg62-dev, libbz2-dev, libtiff4-dev, libwmf-dev (>= 
0.2.7-1), libz-dev, libpng12-dev (<= 1.2.8rel-7) | libpng12-dev (>= 
1.2.15~beta5-0), libx11-dev, libxt-dev, libxext-dev, debhelper (>> 3.0.5), 
libxml2-dev, libfreetype6-dev, liblcms1-dev, libexif-dev, perl (>= 5.8.0-3), 
libjasper-1.701-dev, libltdl3-dev, graphviz (>= 2.8), gs-gpl, pkg-config
 
 Package: imagemagick
 Architecture: any
only in patch2:
unchanged:
--- imagemagick-6.2.4.5.dfsg1.orig/coders/png.c
+++ imagemagick-6.2.4.5.dfsg1/coders/png.c
@@ -1704,7 +1704,7 @@
 #if defined(PNG_USE_PNGGCCRD) && defined(PNG_ASSEMBLER_CODE_SUPPORTED) \
 && (PNG_LIBPNG_VER >= 10200)
   /* Disable thread-unsafe features of pnggccrd */
-  if (png_access_version() >= 10200)
+  if (png_access_version_number() >= 10200)
   {
 png_uint_32 mmx_disable_mask=0;
 png_uint_32 asm_flags;
@@ -1713,8 +1713,8 @@
 | PNG_ASM_FLAG_MMX_READ_FILTER_SUB   \
 | PNG_ASM_FLAG_MMX_READ_FILTER_AVG   \
 | PNG_ASM_FLAG_MMX_READ_FILTER_PAETH );
-asm_flags=png_get_asm_flags(png_ptr);
-png_set_asm_flags(png_ptr, asm_flags & ~mmx_disable_mask);
+asm_flags=png_get_asm_flags(ping);
+png_set_asm_flags(ping, asm_flags & ~mmx_disable_mask);
   }
 #endif
 

Bug#402920: mplayer FTBFS with DEB_BUILD_OPTS=debug

[A Mennucc]

you may download the "debug" version of mplayer from
http://tonelli.sns.it/pub/mplayer/debug

a.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#402920: mplayer FTBFS with DEB_BUILD_OPTS=debug

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 402920 normal
Bug#402920: mplayer FTBFS with DEB_BUILD_OPTS=debug
Severity set to `normal' from `serious'

> tag 402920 unreproducible
Bug#402920: mplayer FTBFS with DEB_BUILD_OPTS=debug
There were no tags set.
Tags added: unreproducible

> 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#401047: marked as done (imagemagick: [AMD64] FTBFS with recent libpng.)

[Debian Bug Tracking System]

Your message dated Wed, 13 Dec 2006 17:02:06 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401047: fixed in imagemagick 7:6.2.4.5.dfsg1-0.13
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)

--- Begin Message ---
Package: imagemagick
Version: 7:6.2.4.5.dfsg1-0.12
Severity: serious
Tags: patch
Justification: no longer builds from source

Recent libpng actived MMX optimisations on amd64, it seems, and a
previously uncompiled code snippet in coders/png.c is now alive. It's
example code from libpng's man page, but contains a few cut&paste errors
that break compiling. Patch for those is attached. Unfortunately,
imagemagick doesn't build on amd64 with these fixes, either because of
linker errors due to a missing symbol in libpng. For Debian's purposes,
it would also be sufficient to simply disable the #if block as a whole,
but I'd prefer libpng to be fixed.

Regards,

Daniel.

--- imagemagick-6.2.4.5.dfsg1.orig/coders/png.c
+++ imagemagick-6.2.4.5.dfsg1/coders/png.c
@@ -1704,7 +1704,7 @@
 #if defined(PNG_USE_PNGGCCRD) && defined(PNG_ASSEMBLER_CODE_SUPPORTED) \
 && (PNG_LIBPNG_VER >= 10200)
   /* Disable thread-unsafe features of pnggccrd */
-  if (png_access_version() >= 10200)
+  if (png_access_version_number() >= 10200)
   {
 png_uint_32 mmx_disable_mask=0;
 png_uint_32 asm_flags;
@@ -1713,8 +1713,8 @@
 | PNG_ASM_FLAG_MMX_READ_FILTER_SUB   \
 | PNG_ASM_FLAG_MMX_READ_FILTER_AVG   \
 | PNG_ASM_FLAG_MMX_READ_FILTER_PAETH );
-asm_flags=png_get_asm_flags(png_ptr);
-png_set_asm_flags(png_ptr, asm_flags & ~mmx_disable_mask);
+asm_flags=png_get_asm_flags(ping);
+png_set_asm_flags(ping, asm_flags & ~mmx_disable_mask);
   }
 #endif
 
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 7:6.2.4.5.dfsg1-0.13

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

imagemagick_6.2.4.5.dfsg1-0.13.diff.gz
  to pool/main/i/imagemagick/imagemagick_6.2.4.5.dfsg1-0.13.diff.gz
imagemagick_6.2.4.5.dfsg1-0.13.dsc
  to pool/main/i/imagemagick/imagemagick_6.2.4.5.dfsg1-0.13.dsc
imagemagick_6.2.4.5.dfsg1-0.13_i386.deb
  to pool/main/i/imagemagick/imagemagick_6.2.4.5.dfsg1-0.13_i386.deb
libmagick++9-dev_6.2.4.5.dfsg1-0.13_i386.deb
  to pool/main/i/imagemagick/libmagick++9-dev_6.2.4.5.dfsg1-0.13_i386.deb
libmagick++9c2a_6.2.4.5.dfsg1-0.13_i386.deb
  to pool/main/i/imagemagick/libmagick++9c2a_6.2.4.5.dfsg1-0.13_i386.deb
libmagick9-dev_6.2.4.5.dfsg1-0.13_i386.deb
  to pool/main/i/imagemagick/libmagick9-dev_6.2.4.5.dfsg1-0.13_i386.deb
libmagick9_6.2.4.5.dfsg1-0.13_i386.deb
  to pool/main/i/imagemagick/libmagick9_6.2.4.5.dfsg1-0.13_i386.deb
perlmagick_6.2.4.5.dfsg1-0.13_i386.deb
  to pool/main/i/imagemagick/perlmagick_6.2.4.5.dfsg1-0.13_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.
Daniel Kobras <[EMAIL PROTECTED]> (supplier of updated imagemagick 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: Wed, 13 Dec 2006 11:33:25 +0100
Source: imagemagick
Binary: perlmagick libmagick9 libmagick9-dev imagemagick libmagick++9-dev 
libmagick++9c2a
Architecture: source i386
Version: 7:6.2.4.5.dfsg1-0.13
Distribution: unstable
Urgency: high
Maintainer: Daniel Kobras <[EMAIL PROTECTED]>
Changed-By: Daniel Kobras <[EMAIL PROTECTED]>
Description: 
 imagemagick - Image manipulation programs
 libmagick++9-dev - The object-oriented C++ API to the ImageMagick 
library--developme
 libmagick++9c2a - The object-oriented C++ API to the ImageMagick library
 libmagick9 - Image manipulation library
 libmagick9-dev - Image manipulation library -- development
 perlmagick - A perl interface to the libMagick graphics routines
Closes: 401047
Changes: 
 imagemagick (7:6.2.4.5.dfsg1-0.13) unstable; urgency=high
 .
   * Non-maintainer upload.
   * coders/png.c: Fix amd64 build failure with recent libpng versions.
 Closes: #401047
   * debian/control: Tighten libpng12-dev build-dependency to exclude versions
 that ar

Bug#402179: tar: FTBFS: race condition in test-suite

[Anthony Towns]

This bug seems to only occur for the posix format tar archives. It's
repeatable outside the tar test suite by doing:


#!/bin/sh

export TAR_OPTIONS="-H posix --pax-option=exthdr.name=%d/PaxHeaders/%f"

echo hello > file1
echo goodbye > file2

while :; do
  tar cf archive.1 file1 file2

  tar cfT archive.2 /dev/null
  tar rf archive.2 file1
  tar rf archive.2 file2

  if cmp archive.1 archive.2 >/dev/null; then
echo -n .
  else
echo -n +
  fi
done


The output should be all dots if the assumptions of the test are correct, but
I get:

+...+..+
..++.++.
.+..
...+
.+..
...+
.+.+

Which is to say it fails about 3% of the time on my system (stable
over about 2000 iterations). I'd say that warrants downgrading this bug
from serious.

The fundamental problem seems to be that the POSIX format tarballs
include the atime of the files in the archive (which may change between
adding the file to the first archive and the second), and the mtime of
the archive itself (which likewise may change). 

I don't see any way to work around that, though -- "--atime-preserve"
helps (by eliminating the atimes), but that still leaves it failing
around 1.7% of the time (when the mtimes don't match, presumably).

If the test is run on a filesystem that preserves timestamps to the
nanosecond (or possibly even the microsecond?), this test will always
fail.

Cheers,
aj



signature.asc
Description: Digital signature

Bug#382757: Remove this package (and thats an order! :)

[Frank Küster]

clone 382757 -1
reassign -1 ftp.debian.org
retitle -1 RM: fst - license violation
thanks

Paul Davis <[EMAIL PROTECTED]> wrote:

> Free - you *CANNOT* distribute this package. Torben and I have made this
> very clear. Please remove it ASAP. It is a violation of our intent and
> of the GPL to distribute it. 
>
> If and when Steinberg changes the license for the VSTSDK, things will
> change. Until then, it has to be removed. Please do it.
>
> --p
>
>
>
>

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

Processed: Re: Remove this package (and thats an order! :)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> clone 382757 -1
Bug#382757: fst - FTBFS: Build depeneds agains unavailable package
Bug 382757 cloned as bug 402945.

> reassign -1 ftp.debian.org
Bug#402945: fst - FTBFS: Build depeneds agains unavailable package
Bug reassigned from package `fst' to `ftp.debian.org'.

> retitle -1 RM: fst - license violation
Bug#402945: fst - FTBFS: Build depeneds agains unavailable package
Changed Bug 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#401570: Processed: Re: Bug#401570: libswt3.2-gtk-jni: apt-get upgrade fails

[Shaun Jackman]

On 12/12/06, Steve Langasek <[EMAIL PROTECTED]> wrote:

> Should libswt-gtk-3.2-java (my package) conflict with
> libswt3.2-gtk-java (the package from Eclipse)? Since Eclipse is not in
> stable or testing (as you noted), I'm unsure if conflicting is
> necessary. Is it sufficient for libswt3.2-gtk-java to conflict with
> libswt-gtk-3.2-java?

Ah, I didn't realize this was a current package from eclipse, I figured
based on the version numbers that it was a package rename.  If both of these
packages are live, that makes this a serious bug after all -- though only
applicable to unstable in this case.

I don't see any conflicts between the -java packages, only the -jni
packages.  I guess the -jni packages do need to conflict with each other
then, if they have file conflicts.


Is it not sufficient for libswt3.2-gtk-jni to conflict with
libswt-gtk-3.2-jni? apt-get seems to behave correctly in the current
situation (see below). Since libswt-gtk-3.2-jni is already in the
stable archive, I would think the onus would be on the new package to
conflict with existing packages.

Cheers,
Shaun

$ sudo apt-get install libswt3.2-gtk-jni
Reading package lists... Done
Building dependency tree... Done
Recommended packages:
 libgnome2-0 libgnomeui-0 libgnomevfs2-0 libnspr4-0d libxul0d
The following packages will be REMOVED
 libswt-gtk-3.2-jni
The following NEW packages will be installed
 libswt3.2-gtk-jni
...
$ sudo apt-get install libswt-gtk-3.2-jni
Reading package lists... Done
Building dependency tree... Done
Suggested packages:
 libswt-gnome-gtk-3.2-jni
The following packages will be REMOVED
 libswt3.2-gtk-jni
The following NEW packages will be installed
 libswt-gtk-3.2-jni
...
$ sudo apt-get install libswt-gtk-3.2-jni libswt3.2-gtk-jni
Reading package lists... Done
Building dependency tree... Done
libswt-gtk-3.2-jni is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 libswt3.2-gtk-jni: Conflicts: libswt-gtk-3.2-jni but 3.2.1-3 is to
be installed
E: Broken packages


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

Bug#402946: linux-image-2.6.18-3-686: wrong harddisk size detected

[Klaus Schneider]

Package: linux-image-2.6.18-3-686
Version: 2.6.18-7
Severity: critical
Justification: breaks the whole system

The kernel 2.6.18-3-686 detects a wrong harddisk size, which leads
to "access beyond end of device" errors and thereby makes the system
unusable. The corresponding partition cannot be mounted. Even cfdisk
does not run, because it detects a corrupted partition table.

System log:
Dec 13 13:35:04 werckmeister kernel: SCSI device sda: 139968963 512-byte hdwr 
sectors (71664 MB)
Dec 13 13:35:04 werckmeister kernel:  sda: p7 exceeds device capacity
Dec 13 13:35:04 werckmeister kernel: attempt to access beyond end of device
Dec 13 13:35:04 werckmeister kernel: sda: rw=0, want=146833964, limit=139968963
and many more of the "attempt to access beyond end of device" errors

The old kernel 2.6.17-2-686 detects the correct size:
Dec 13 17:00:31 werckmeister kernel: SCSI device sda: 156368016 512-byte hdwr 
sectors (80060 MB)

Thus, reinstalling and using the old kernel 2.6.17.2-686 was 
mandatory for me (the old kernel package was difficult to obtain 
though).

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

Versions of packages linux-image-2.6.18-3-686 depends on:
ii  coreutils 5.97-5 The GNU core utilities
ii  debconf [debconf-2.0] 1.5.8  Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85c  tools for generating an initramfs
ii  module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-3-686 recommends:
ii  libc6-i686   2.3.6.ds1-8 GNU C Library: Shared libraries [i

-- debconf information:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686:
  linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/kimage-is-a-directory:
  linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true
  linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false
  linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true
  linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true
  linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true
  linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686:
  linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true
  linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686:
  linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686:
  linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686:
  linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686:
  linux-image-2.6.18-3-686/postinst/old-initrd-link-2.6.18-3-686: true
  linux-image-2.6.18-3-686/postinst/depmod-error-2.6.18-3-686: false
  linux-image-2.6.18-3-686/preinst/failed-to-move-modules-2.6.18-3-686:


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

Processed: Re: Bug#402920: mplayer FTBFS with DEB_BUILD_OPTS=debug

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tag 402920 - unreproducible
Bug#402920: mplayer FTBFS with DEB_BUILD_OPTS=debug
Tags were: unreproducible
Tags removed: unreproducible

> clone 402920 -1
Bug#402920: mplayer FTBFS with DEB_BUILD_OPTS=debug
Bug 402920 cloned as bug 402950.

> severity -1 serious
Bug#402950: mplayer FTBFS with DEB_BUILD_OPTS=debug
Severity set to `serious' from `normal'

> retitle -1 mplayer do not support nostrip/noopt and is in C [violates policy 
> §10.1]
Bug#402950: mplayer FTBFS with DEB_BUILD_OPTS=debug
Changed Bug 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#402949: missing dependency against lsb-base

[Steffen Joeris]

Package: wifi-radar
Severity: serious
Tags: patch

Hi dude

How is your trainee program going, hope you are doing well :)

I am sorry, but I am filling a serious bug against your package, because
it misses a dependency against lsb-base. Though lsb-base is
priority: required you need to depend on all packages which are
non-essential and lsb-base is not essential (which should be changed I
guess, but probably won't for etch).
I think the bug will never be really annoying as lsb-base is installed,
but according to policy it is still a bug, sorry ... you know
bureaucracy.


Cheers
Steffen


--- debian/control.orig 2006-12-13 19:15:23.0 +0100
+++ debian/control  2006-12-13 19:15:35.0 +0100
@@ -7,7 +7,7 @@

 Package: wifi-radar
 Architecture: all
-Depends: ${misc:Depends}, python, python-gtk2 (>= 2.0), dhcp3-client | 
dhcp-client, wireless-tools, menu
+Depends: ${misc:Depends}, python, python-gtk2 (>= 2.0), dhcp3-client | 
dhcp-client, wireless-tools, menu, lsb-base
 Recommends: wpasupplicant
 Description: graphical utility for managing Wi-Fi profiles
  WiFi Radar enables you to scan for available wireless networks and create


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

Bug#402951: libapache-mod-ssl: restart leaves /var/cache/apache/__db.ssl_cache.db there

[Mark Symonds]

Package: libapache-mod-ssl
Version: 2.8.22-1sarge1
Severity: grave
Tags: security
Justification: user security hole



-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libapache-mod-ssl depends on:
ii  apache-common 1.3.33-6sarge3 support files for all Apache webse
ii  libc6 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an
ii  libdb4.2  4.2.52-18  Berkeley v4.2 Database Libraries [
ii  libexpat1 1.95.8-3   XML parsing C library - runtime li
ii  libssl0.9.7   0.9.7e-3sarge4 SSL shared libraries
ii  openssl   0.9.7e-3sarge4 Secure Socket Layer (SSL) binary a

-- no debconf information 

Hi, 

The past week I've had four sarge boxes apache processes lockup.
apachectl restart works without error, but the webservice is still not
responding.  Other methods (killall -9 + invoke-rc.d restart, etc.) are
tried but still, no webservice and nothing in error.log to indicate a
problem. 

Attaching a strace to the apache process, I see that it is in a loop
complaining that /var/cache/apache/__db.ssl_cache.db already exists.
Removing this file and restarting fixes the problem. 

Also I notice in these situations that there are hundreds of ssl.mutex*
files in /var/log/apache. 

Possible DoS attack in the wild?  I wouldn't think so but it's been the same 
thing on four different servers in a week... I'm going to post to some lug 
mailing lists later today to see if anyone else is seeing this.  

Best

Mark


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

Bug#402922: segfault in mplayer own mpeg2 library

[Pierre Habouzit]

On Wed, Dec 13, 2006 at 05:53:03PM +0100, A Mennucc wrote:
> 
> here is some more info:
> 
> $ gdb ./mplayer
> This GDB was configured as "x86_64-linux-gnu"...Using host libthread_db
> library "/lib/libthread_db.so.1".
> 
> (gdb) run ~/mplayer/bench/foobar.mpeg
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 47190863550720 (LWP 1368)]
> MC_put_o_16_mmxext (dest=0xcb5f00 "", ref=0x0, stride=304, height=16)
> at motion_comp_mmx.c:546
> 546 movq_m2r (*ref, mm0);
> (gdb) li
> 541
> 542 static inline void MC_put1_16 (int height, uint8_t * dest, const
> uint8_t * ref,
> 543const int stride)
> 544 {
> 545 do {
> 546 movq_m2r (*ref, mm0);
> 547 movq_m2r (*(ref+8), mm1);
> 548 ref += stride;
> 549 movq_r2m (mm0, *dest);
> 550 movq_r2m (mm1, *(dest+8));
> 
> we should understand why  ref==0
> 
> anyway I will add an assert

  O_o *blink* *blink*

  do you know that assert is a macro that may be disabled if for some
reason the build system defines NDEBUG ?!

  like I said in my report, other software in the debian archive that
use the libmpeg2 do not segfault here, hence I suspect a bug in the
embeded libmpeg2 mplayer ships.

  Statically linked or not, you should link against the debian one,
rather than the embededed one to avoid such problems, and benefit from
the audits debian already do on its own libmpeg2.

  but please, give me a break, an assert is everything but a fix.

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgp7MjQTlNCVc.pgp
Description: PGP signature

Bug#389163: How to handle filename conflict "aleph" (Packages aleph, tetex-bin, texlive-bin)?

[Thomas Bushnell BSG]

From Paul's comments, it seems to me that there is no need for the
current Aleph it's been replaced, and it's three years old.  I have no
opinion about whether it ought to be dropped from Debian.

Paul also explains that AFNIX replaced Aleph, and should not be thought
of as just a new version with a name change.  I had misunderstood.
Given his explanation, we should think of AFNIX and Alpha as two
different entities I think.

That means that Paul should continue with AFNIX, I think, and continue
learning; there isn't any hue and cry I know of asking for AFNIX to be
in Debian right away, so I see no reason he shouldn't just continue as
he has been.

This however does not solve the name clash with Aleph.  So I think there
are three possibilities (repeating here what Frank already said
somewhat):

1) Leave things alone, and ignore the problem.  This, it seems to me,
requires some kind of go-ahead from the release team.

2) Drop aleph.  This would be warranted if it were of no use any longer,
or if it were buggy.  But the *only* bug against Aleph is the name clash
with TeX, so there is no independent reason to prefer this solution.
The question remains, however, whether the current version has any use,
and I simply don't know the answer to that.  If it does, then, as I
said, I'm happy to maintain it.

3) Retain aleph, and change the name of the binary in one package or the
other.  If we don't do (2), and the release team is not happy with (1),
then this is obviously the right course.  I don't care at all which
program's name is changed or what it's changed to.  What are the pros
and cons?

Thomas



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

Processed: retitle 402945 to RM: fst -- RoQA; license issues

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.25
> retitle 402945 RM: fst -- RoQA; license issues
Bug#402945: RM: fst - license violation
Changed Bug title.

>
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: Adjust severity

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Md forgot to CC: control@
> severity 402320 normal
Bug#402320: udev_db_add_device: unable to create db file  '/dev/.udev/db/...'
Severity set to `normal' from `serious'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Bug#402898: New /etc/bogofilter.cf

[Teemu Likonen]

Package: bogofilter
Version: 1.1.3-1
Followup-For: Bug #402898

New /etc/bogofilter.cf is attached. It defines the encoding explicitly:

charset_default=utf-8
unicode=yes
# Comment lines MUST have their hash mark in the leftmost column.
# Comments can be added at the end of any line (after whitespace and a '#').
# Blank lines are allowed.

### General Settings 

 BOGOFILTER_DIR
#
#   directory for wordlists
#
#bogofilter_dir=~/.bogofilter
##bogofilter_dir=/var/spool/bogofilter

 name/location of user config file
#
#user_config_file=~/.bogofilter.cf
##user_config_file=~/.bogofilterrc
##user_config_file=~/.bogofilter/config

 TRANSACTIONS: enable/disable database transactions
#
#   boolean indicating whether transactions
#   should be enabled (yes) or disabled (no)
#
#db_transaction=no  # default
##db_transaction=yes# (alternate)

 WORDLIST: define additional word lists
#
#   char type: 'r' (regular) or 'i' (ignore)
#   char *name: name of list, e.g. "system", "user", "ignore"
#   char *path: absolute path to file or
#   file name (relative to bogofilter_dir)
#   int  order - once found, skip higher numbered lists
#
##wordlist i,ignore,~/ignorelist.db,1
##wordlist r,wordlist,~/wordlist.db,2

 SPAM_HEADER_NAME
#
#   used in reporting spamicity and
#   in removing already existing headers
#
#spam_header_name=X-Bogosity

 SPAM_SUBJECT_TAG
#
#   tag added to "Subject: " line for identifying spam or unsure
#   default is to add nothing.
#
##spam_subject_tag=***SPAM***
##unsure_subject_tag=???UNSURE???

 STATS_IN_HEADER
#
#   non-zero (default):  put spamicity info in message header
#   zero:  put spamicity info in message body
#   can use "bool" values of True, False, Yes, No, 1, or 0
#
#stats_in_header=Yes# default
##stats_in_header=No# (alternate)

 DB_CACHESIZE
#
#   non-zero: set this as DB cache size (in Mbytes)
#   zero: use DB default cache size (.25 Mbyte in 4.0.14)
#
#   note that Berkeley DB increases any buffer size below 500 MB
#   by 25%!
#   This helps most when doing massive changes to the data base that
#   involve a lot of overwrites, such as registering mail boxes,
#   whereas it is mostly a waste of memory for read-only
#   applications such as scoring.
#   WARNING: If you set this too large, bogofilter will fail.
#
#db_cachesize=0 # default
##db_cachesize=16   # (alternate)

 DB_LOG_AUTOREMOVE
#
#   boolean indicating whether auto-removing of
#   logs should be enabled (yes) or disabled (no)
#
#db_log_autoremove=yes  # default
##db_log_autoremove=no  # (alternate)

 TIMESTAMP
#
#   enables or disables token timestamps
#
#timestamp=Yes

 Format of spamicity output
#
# for two-state output the third entry is not needed and not used
#
#spamicity_tags = Spam, Ham, Unsure
#spamicity_formats = %0.6f, %0.6f, %0.6f
#
##spamicity_tags = Yes, No, Unsure
##spamicity_formats = %0.6f, %0.6f, %0.6f

 Format of SPAM_HEADER
#
#   formatting characters:
#
#   h - spam_header_name, e.g. "X-Bogosity"
#
#   c - classification, e.g. Yes/No, Spam/Ham/Unsure, +/-/?
#
#   D - date, fixed ISO-8601 format for Universal Time ("GMT")
#
#   e - spamicity as 'e' format
#   f - spamicity as 'f' format
#   g - spamicity as 'g' format
#
#   A - IP address (from first Received: statement having one)
#   Not guaranteed to be the originating address of the message.
#   I - Message ID
#   Q - Queue ID (from first id tag found in Received: headers)
#
#   l - logging tag (from '-l' option)
#
#   o - spam_cutoff, ex. cutoff=%o
#
#   p - spamicity value
#   d - if ham or unsure, the spamicity
#   if spam, difference of spamicity from 1.0
#
#   r - runtype
#   w - word count
#   m - message count
#
#   u - username - this will either be the login from getlogin(),
#  if that is empty, the pw_name obtained from
#  the password database, or the user id
#  prefixed by #, for instance, #1003
#
#   v - version
#
#customizable messages:
#
#   header_format - the "X-Bogosity" line that '-p' adds to
#   the message header and '-v' outputs.
#   terse_format - an abbreviated form of header_format;
#   selected by command line option '-t'
#   log_header_format - written to syslog by '-u' option
#   when classifying messages.
#   log_update_format - written to syslog by '-u' option
#   when registering messages.
#
#
#header_format = %h: %c, tests=bogofilter, spamicity=%p, version=%v
#terse_format = %1.1c %f
#log_header_format =

Bug#401570: Processed: Re: Bug#401570: libswt3.2-gtk-jni: apt-get upgrade fails

[Shaun Jackman]

On 12/12/06, Steve Langasek <[EMAIL PROTECTED]> wrote:
...

I don't see any conflicts between the -java packages, only the -jni
packages.  I guess the -jni packages do need to conflict with each other
then, if they have file conflicts.


Thank you for bringing to my attention that only the -jni packages
conflict. The fundamental reason the two packages conflict is that
they provide exactly the same libraries. So, to close bug #376672
(libswt-gtk-3.1-java conflicts libswt3.1-gtk-java) it occurred to me
that libswt-gtk-3.1-java could depend on libswt-gtk-3.2-jni |
libswt3.2-gtk-jni.

The catch is that both JNI libraries are somewhat misnamed, because
version 3.2-1 of both packages provided the soname libswt-gtk-3232.so,
whereas version 3.2.1-1 of the packages provide the soname
libswt-gtk-3235.so. If 3.2.2-1 is also released under the package name
libswt3.2-gtk-jni (likely), it will not be suitable to provide the
needed dependency (namely, libswt-gtk-3235.so). So, I need to depend
as an alternative on libswt3.2-gtk-jni (>> 3.2.1 && << 3.2.2). How do
I accomplish this? So far I have...

Package: libswt-gtk-3.2-java
Depends: libswt-gtk-3.2-jni (= ${binary:Version})
 | libswt3.2-gtk-jni (>> 3.2.1)

One solution would be for both libswt-gtk-3.2-jni and
libswt3.2-gtk-jni to provide a pseudo-package libswt-gtk-3235-jni and
depend on that. The only downside is that both SWT packages have to be
modified to support this mechanism.

Cheers,
Shaun


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

Bug#146894: marked as done (nana-trace doesn't work at all: mawk fails to compile scripts)

[Debian Bug Tracking System]

Your message dated Wed, 13 Dec 2006 19:17:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#146894: fixed in nana 2.5-9
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)

--- Begin Message ---
Package: nana
Version: 2.5-8
Severity: important

[EMAIL PROTECTED]:/usr/src/mplayer/mplayer-0.90pre3$ nana-trace mplayer
mawk: line 7: regular expression compile failed (missing operand)
^Breakpoint 1, main()
[EMAIL PROTECTED]:/usr/src/mplayer/mplayer-0.90pre3$ 

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux eppesuig1 2.4.18-686 #1 Thu May 2 18:03:02 CEST 2002 i686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

Versions of packages nana depends on:
ii  gcc  2:2.95.4-14 The GNU C compiler.
ii  libc62.2.5-4 GNU C Library: Shared libraries an
ii  libc6-dev2.2.5-4 GNU C Library: Development Librari


--- End Message ---
--- Begin Message ---
Source: nana
Source-Version: 2.5-9

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

nana_2.5-9.diff.gz
  to pool/main/n/nana/nana_2.5-9.diff.gz
nana_2.5-9.dsc
  to pool/main/n/nana/nana_2.5-9.dsc
nana_2.5-9_i386.deb
  to pool/main/n/nana/nana_2.5-9_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.
Kurt B. Kaiser <[EMAIL PROTECTED]> (supplier of updated nana 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: Tue,  5 Dec 2006 21:40:25 -0500
Source: nana
Binary: nana
Architecture: source i386
Version: 2.5-9
Distribution: unstable
Urgency: low
Maintainer: Kurt B. Kaiser <[EMAIL PROTECTED]>
Changed-By: Kurt B. Kaiser <[EMAIL PROTECTED]>
Description: 
 nana   - GNU Nana -- improved support for assertions and logging
Closes: 58910 109892 109893 122236 146894 190490 299336 342425 398104
Changes: 
 nana (2.5-9) unstable; urgency=low
 .
   * New Maintainer (Closes: #398104)
   * Copy in config.{guess,sub} from autotools-dev during maintainer build
 (Closes: #342425, #299336)
   * Acknowledge NMU 2.5-8.1 (Closes: #190490)
   * Acknowledge NMU 2.5-8.2 (Closes: #146894)
   * Add debhelper compat file, update standards to 3.7.2
   * dpatchify for current and future changes
   * Add gdb examples from upstream gdb directory
   * Add packaging copyright and license
   * Fix unescaped hyphen in nana-run.1
   * Add a watch file
   * nana-run: fix bad path to /usr/share/nana/
   * nana-c++lg: fix bad path to nana-clg (Closes: #122236)
   * nana-sfdir: fix bad path to nana-sfg (Closes: #109892)
   * nana-sfg: mawk: next doesn't work in function (Closes: #109893)
   * nana-trace: gdb output pattern match was failing
   * nana-trace: was not printing the first line of code
   * Set ALWAYS_INCLUDE_MALLOC to 0, apparently not needed anymore,
 breaks g++ code (Closes #101556)
   * Implement user function capability in DL.h (Closes: #58910)
   * Remove superfluous README.debian file
   * Use original upstream ChangeLog instead of maintainer added changelog
Files: 
 747413be7f57adb17dc150a2bd951d44 580 devel extra nana_2.5-9.dsc
 b623dfe288d441e43e18cbc74e863c92 34002 devel extra nana_2.5-9.diff.gz
 407c7800956bc8b4341ffd2356b7e9b8 129250 devel extra nana_2.5-9_i386.deb

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

iD8DBQFFgE4r+C5cwEsrK54RAuefAKCwssJOs7AIArURMkI3QPAVZjbiDQCeI3y0
87zbtDaL4SJrLhhuUtT50F4=
=E+O8
-END PGP SIGNATURE-

--- End Message ---

Bug#401745: sympa: Does not set up correct owner and group

[Stefan Hornburg (Racke)]

Marco Solieri wrote:

Package: sympa
Version: 5.2.1-0.1
Severity: grave
Tags: experimental
Justification: renders package unusable

After a fresh installation lot of important Sympa files are owned by
root:root and are unaccessable. This is because sympa processes run as
sympa user.

The configuration process itself suffers this problem reporting
errors probably due to this. In fact '/etc/sympa/data_structure.version'
is owned by root and this make the configuration process fail.

Moreover the entire '/usr/lib/sympa/' directory is owned (according with
postinst script) by root. I fixed setting up user and group to sympa:sympa
on that subtree.


/usr/lib/sympa is owned by root on purpose, the data directories for sympa
are within /var.

Bye
Racke


--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team



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

Processed: Reduce severity and merge

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 402899 normal
Bug#402899: kvm-source doesn't compile with 2.6.19
Severity set to `normal' from `serious'

> merge 402899 402654
Bug#402654: fails to build against kernel 2.6.19
Bug#402899: kvm-source doesn't compile with 2.6.19
Merged 402654 402899.

> 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#402922: segfault in mplayer own mpeg2 library

[A Mennucc]

Pierre Habouzit ha scritto:
> On Wed, Dec 13, 2006 at 05:53:03PM +0100, A Mennucc wrote:
>> here is some more info:
>>
>> $ gdb ./mplayer
>> This GDB was configured as "x86_64-linux-gnu"...Using host libthread_db
>> library "/lib/libthread_db.so.1".
>>
>> (gdb) run ~/mplayer/bench/foobar.mpeg
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 47190863550720 (LWP 1368)]
>> MC_put_o_16_mmxext (dest=0xcb5f00 "", ref=0x0, stride=304, height=16)
>> at motion_comp_mmx.c:546
>> 546 movq_m2r (*ref, mm0);
>> (gdb) li
>> 541
>> 542 static inline void MC_put1_16 (int height, uint8_t * dest, const
>> uint8_t * ref,
>> 543const int stride)
>> 544 {
>> 545 do {
>> 546 movq_m2r (*ref, mm0);
>> 547 movq_m2r (*(ref+8), mm1);
>> 548 ref += stride;
>> 549 movq_r2m (mm0, *dest);
>> 550 movq_r2m (mm1, *(dest+8));
>>
>> we should understand why  ref==0
>>
>> anyway I will add an assert
> 
>   O_o *blink* *blink*
>
>   do you know that assert is a macro that may be disabled if for some
> reason the build system defines NDEBUG ?!

you are criticizing my way of solving this bug *even before I sit down
and start writing the code*

even supposing that
- I would use assert(ref)
- the code is compiled with NDEBUG
did you consider the fact that I will check my patch against your
foobar.mpeg, in the end, to make sure that it will work?

congratulations! you really know how to go along and collaborate with
other people
(yes that is sarcasm)


a.


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

Processed: your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 401745 normal
Bug#401745: sympa: Does not set up correct owner and group
Severity set to `normal' from `grave'

> --
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#402725: marked as done (rss2email: r2e run does not check for errors on mail submission)

[Debian Bug Tracking System]

Your message dated Wed, 13 Dec 2006 19:47:12 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402725: fixed in rss2email 1:2.60-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)

--- Begin Message ---
Package: rss2email
Version: 1:2.60-1.1
Severity: grave

r2e run does not mind when the MTA does not accept messages. It
happily marks articles as processed, even when it got a non-zero
return from sendmail or a 4xx or 5xx from the SMTP connection.

I'll try to come up with a patch for this issue.

Cheers,
-Hilko

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

Versions of packages rss2email depends on:
ii  python2.4.4-1An interactive high-level object-o
ii  python-feedparser 4.1-6  Universal Feed Parser for Python
ii  python-support0.5.6  automated rebuilding support for p

rss2email recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: rss2email
Source-Version: 1:2.60-3

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

rss2email_2.60-3.diff.gz
  to pool/main/r/rss2email/rss2email_2.60-3.diff.gz
rss2email_2.60-3.dsc
  to pool/main/r/rss2email/rss2email_2.60-3.dsc
rss2email_2.60-3_all.deb
  to pool/main/r/rss2email/rss2email_2.60-3_all.deb



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

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

Debian distribution maintenance software
pp.
Joey Hess <[EMAIL PROTECTED]> (supplier of updated rss2email 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: Wed, 13 Dec 2006 14:34:42 -0500
Source: rss2email
Binary: rss2email
Architecture: source all
Version: 1:2.60-3
Distribution: unstable
Urgency: low
Maintainer: Joey Hess <[EMAIL PROTECTED]>
Changed-By: Joey Hess <[EMAIL PROTECTED]>
Description: 
 rss2email  - receive RSS feeds by email
Closes: 402725
Changes: 
 rss2email (1:2.60-3) unstable; urgency=low
 .
   * Check exit status of sendmail, and die if it fails. Closes: #402725
Files: 
 1fac6e414ce982bc0040a6c8a364064f 678 mail optional rss2email_2.60-3.dsc
 ba9bc5a87c5be82148c39b6d18cf78e6 8084 mail optional rss2email_2.60-3.diff.gz
 f62e88598e6260edb7017f6815b9be17 20356 mail optional rss2email_2.60-3_all.deb

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

iD8DBQFFgFZH2tp5zXiKP0wRAhk7AKCiOq4rd72nn1JlBtZM7XOxXttugQCfa/k7
MCfT591uAKjde2qCsUGO+L4=
=50Eg
-END PGP SIGNATURE-

--- End Message ---

Processed: This is a security issue

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 400624 grave
Bug#400624: dsniff: urlsnarf should sanitize sniffed requests
Severity set to `grave' from `important'

> thank you
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: Re: libcfitsio2: wrong byteswap on arm and mipsel architectures

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # fixing bug information
> reassign 339758 libcfitsio2
Bug#339758: libcfitsio2: wrong byteswap on arm and mipsel architectures
Bug reassigned from package `libcfitsio2' to `libcfitsio2'.

> found 339758
Bug#339758: libcfitsio2: wrong byteswap on arm and mipsel architectures
Bug reopened.

> found 339758 2.510-1
Bug#339758: libcfitsio2: wrong byteswap on arm and mipsel architectures
Bug marked as found in version 2.510-1.

> found 339758 2.510-1.1
Bug#339758: libcfitsio2: wrong byteswap on arm and mipsel architectures
Bug marked as found in version 2.510-1.1.

> close 339758 2.510-1.2
Bug#339758: libcfitsio2: wrong byteswap on arm and mipsel architectures
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.510-1.2, send any further explanations to 
Rafael Laboissiere <[EMAIL PROTECTED]>

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Processed: tagging 402898

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.26
> tags 402898 patch
Bug#402898: /etc/bogofilter.cf should define UTF-8 as default charset since it 
is Debian's default
Tags were: etch
Tags added: patch

>
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#339758: libcfitsio2: wrong byteswap on arm and mipsel architectures

[Niko Tyni]

# fixing bug information
reassign 339758 libcfitsio2
found 339758
found 339758 2.510-1
found 339758 2.510-1.1
close 339758 2.510-1.2
thanks

This bug is still unfixed in etch, but it's not showing up on the RC
bug lists, probably because it was marked as done with another package
(cfitsio3) and my 'reopen' confused the index or something. I'm trying
to fix the effects with 'reassign', we'll see how that goes.

In any case, 2.510-1.3 (which is the current unstable version and the
only non-RC-buggy one) is not yet built on mips and sparc because of
transient-looking buildd errors, so I suppose somebody should requeue
it on those buildds.

Cheers,
-- 
Niko Tyni   [EMAIL PROTECTED]


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

Bug#401873: closed by Stephen Gran <[EMAIL PROTECTED]> (Bug#401873: fixed in clamav 0.90~rc2-1)

[Hendrik Weimer]

The bug is still present in 0.88.7. Files nested deeper than
--max-mail-recursion are not scanned and there is no error returned
(exit code is 0). When using clamscan I get a warning from libclamav,
but the EICAR string still passes.


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

Processed: tagging 402898

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.26
> tags 402898 + patch
Bug#402898: /etc/bogofilter.cf should define UTF-8 as default charset since it 
is Debian's default
Tags were: patch etch
Tags added: patch

>
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#389163: How to handle filename conflict "aleph" (Packages aleph, tetex-bin, texlive-bin)?

[Frank Küster]

Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote:

> 1) Leave things alone, and ignore the problem.  This, it seems to me,
> requires some kind of go-ahead from the release team.
>
> 2) Drop aleph.  This would be warranted if it were of no use any longer,
> or if it were buggy.  But the *only* bug against Aleph is the name clash
> with TeX, so there is no independent reason to prefer this solution.
> The question remains, however, whether the current version has any use,
> and I simply don't know the answer to that.  If it does, then, as I
> said, I'm happy to maintain it.

I don't know an answer, either - but popcon gives some hints:

18170 aleph-emacs   23 0 0 023 (Debian Qa 
Group) 
21858 aleph-doc 12 0 0 012 (Debian Qa 
Group) 
30097 aleph  3 1 2 0 0 (Debian Qa 
Group)
37868 aleph-dev  1 0 1 0 0 (Debian Qa 
Group)

the 3's are the area of the "not in sid" packages, in other words
leftovers that have never been upgraded or removed.

That's not a strong argument to keep it...

> 3) Retain aleph, and change the name of the binary in one package or the
> other.  If we don't do (2), and the release team is not happy with (1),
> then this is obviously the right course.  I don't care at all which
> program's name is changed or what it's changed to.  What are the pros
> and cons?

I'm against changing TeX's aleph.  It would be against the upstream
decision.  And knowing the information Paul gave, I suggest not to
rename to afnix, but to something like aleph-runtime or similar.

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

Bug#402331: FTBFS: "unable to find user alias"

[Thomas Huriaux]

Jon Marler <[EMAIL PROTECTED]> (12/12/2006):
> Quoting Thomas Huriaux <[EMAIL PROTECTED]>:
> 
> > Package: qmail
> > Version: 1.03-40
> > Severity: serious
> >
> > Using pbuilder in an i386 chroot:
> >
> > [...]
> > ( ./auto-uid auto_uida `head -1 conf-users` \
> > &&./auto-uid auto_uidd `head -2 conf-users | tail -1` \
> > &&./auto-uid auto_uidl `head -3 conf-users | tail -1` \
> > &&./auto-uid auto_uido `head -4 conf-users | tail -1` \
> > &&./auto-uid auto_uidp `head -5 conf-users | tail -1` \
> > &&./auto-uid auto_uidq `head -6 conf-users | tail -1` \
> > &&./auto-uid auto_uidr `head -7 conf-users | tail -1` \
> > &&./auto-uid auto_uids `head -8 conf-users | tail -1` \
> > &&./auto-gid auto_gidq `head -1 conf-groups` \
> > &&./auto-gid auto_gidn `head -2 conf-groups | tail -1` \
> > ) > auto_uids.c.tmp && mv auto_uids.c.tmp auto_uids.c
> > fatal: unable to find user alias
> > make[1]: *** [auto_uids.c] Error 111
> > make[1]: Leaving directory `/tmp/buildd/qmail-1.03'
> > make: *** [build] Error 2
> > pbuilder: Failed autobuilding of package
> > [...]
> 
> 
> 
> This pops up now and again ... You have attempted to build the package
> without installing it first.  If you install the package, the install
> scripts will create that user for you.
> 
> If you don't want to do that, feel free to add any missing users
> yourself.
> 
> If you want to know why this is an issue, ask the people than fund
> Debian, as they are the ones that demanded the "qmail users" be
> removed from the default passwd file because qmail is considered
> "non-free"  If you dig through the old bug reports for qmail-src, you
> will see a bug that added in the code to add the users.

?

I was trying to build the qmail-src package from the Debian qmail source
package, not the "real" qmail package from the qmail-src package. I
don't understand why an automated debianization requires existing users
to succeed. Or I may not have understood the purpose of the qmail-src
package.

Note also that if it is a known issue that you don't want to fix, you
should mark the bug as wontfix instead of closing the bugs. I never
parse closed bugs before reporting a current issue (and I don't believe
being the only one acting like that). This will avoid this popping up
now and again.

Cheers,

-- 
Thomas Huriaux


signature.asc
Description: Digital signature

Bug#402545: Nope

[Philippe Perrin]

Using compiz 0.3.4 does not solve my black screen issue...


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

Processed: Re: dsniff: urlsnarf should sanitize sniffed requests

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 400624 important
Bug#400624: dsniff: urlsnarf should sanitize sniffed requests
Severity set to `important' from `grave'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Bug#402665: gnutls13: gnutls and exim work here

[Ross Boylan]

Package: gnutls13
Version: 1.4.4-3
Followup-For: Bug #402665

For what it's worth, I tested for this problem on my setup and did not
encounter it.  I'm running on an Athlon chip, no Xen (2.4 kernel--see
below).

exim4-daemon-heavy4.63-11

The test consisted of sending a message via /usr/sbin/exim4 -t.  The
message went out via TLS and then a copy came back (also via TLS, for
another system of mine also running the same versions of
exim4-daemon-heavy and libgnutls13, but under a 2.6.17 kernel, dual
processor Athlon, stock Debian kernel, no Xen).  The message made the
full round-trip, with the headers showing 
esmtpsa (TLSv1:AES256-SHA:256) going out (it did not go directly to my other
system) and 
esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) coming in.

I hope I continue not to observe it!  I don't have a lot of time to
help trouble-shoot, but the report got me sufficiently concerned to do
the test.  I thought I'd pass it on.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)


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

Bug#400624: dsniff: urlsnarf should sanitize sniffed requests

[Steve Langasek]

severity 400624 important
thanks

> Since urlsnarf is usually used on a terminal to have a look at
> requested URLs in real-time, a malicious attacker could use requests
> with escape sequences to execute arbitrary code.

By this reasoning, cat would have a grave bug for allowing users to send
untrusted files to the terminal without escaping.

If a terminal can be exploited to cause arbitrary code execution through
control sequences in a file being displayed, we should consider this a bug
in the terminal.  I don't see any reason that dsniff should be picked on
here just because the untrusted data it's displaying comes directly from the
network.

-- 
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/


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

Processed: severity of 402946 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.9.26
> severity 402946 important
Bug#402946: linux-image-2.6.18-3-686: wrong harddisk size detected
Severity set to `important' from `critical'

>
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#402897: module is not loaded in apache2.2

[Stuart Anderson]

On Wed, 13 Dec 2006, Jan Dittberner wrote:


The apache error log contains the following line:

PHP Warning:  PHP Startup: Unable to load dynamic library
'/usr/lib/php5/20060613/ming.so' - /usr/lib/php5/20060613/ming.so:
undefined symbol: zim_swfmovie_protect in Unknown on line 0


I found this in the upstream yesterday. Please try the package at

deb http://www4.netsweng.com/~anderson/ming-unstable/ binary/

which contains the fix.


 Stuart

Stuart R. Anderson   [EMAIL PROTECTED]
Network & Software Engineering   http://www.netsweng.com/
1024D/37A79149:  0791 D3B8 9A4C 2CDC A31F
  BD03 0A62 E534 37A7 9149


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

Bug#402829: mantis: not supportable by the security team

[Moritz Muehlenhoff]

Thijs Kinkhorst wrote:
> On Wed, 2006-12-13 at 09:49 +0100, "schönfeld / in-medias-res.com"
> wrote:
> > I quiet understand the etch release policy and I am sure that there are
> > cases where 5a matches the case. But in the case of mantis it does *not*
> > match. Because there is currently *one* open security issue which where
> > just reported and which I'm willing to fix in duration of this day. The
> > package *has* a maintainer and it is not out of date or is *too buggy*.
> 
> I think I can say something about this issue. I've been the one actually
> providing the mantis security updates in the sarge lifetime of the
> package.
> 
> I've observed the following:
> - There were many, many security problems with mantis in the sarge
>   release cyle;
> - Upstream did not provide significant details of vulnerabilities, or
>   patches. Also they did not respond to repeated requests from me for
>   that information.
> 
> > It makes me somehow angry that i invested so much work in bringing
> > mantis back in a good shape, when people can block its release by just
> > saying 'hey it had a bad history'.
> 
> You did not add here that the first result of this work only entered
> Debian a couple of weeks ago. While I do value the fact that you've been
> fixing up the package, the few weeks do not give much time to get a
> reliable indication of whether the package has made a radical change.
> 
> >  Given the information by Moritz that
> > it had 21 vulnerabilities it should be worth to mention that almost 50%
> > of the bugs I've seen affected almost dusty versions of mantis that are
> > *far* away from the current release.
> 
> I'm sorry, but I do not buy this. I've fixed a large number of bugs in
> the sarge version of Mantis. The sarge version is 1.5 years old. That
> can hardly be called "far away" or "dusty", can it?
> 
> This is about the same lifetime as expected for etch, so if mantis gets
> obsolete that fast, we're better off not packaging it.
> 
> > Also most of the bugs has been fixed upstream in a reasonable time
> > and i can *not* confirm that mantis developers do hide details of
> > bug fixes.
> 
> I *can*, having worked on actual sarge security updates.
> 
> > In fact they use their own bug tracker to track fixes for bugs and
> > the most of the security issues are IMO documented and discussed
> > there well enough to backport/implement security fixes into current
> > debian packages.
> 
> They keep bugs closed and requests to open up or to get more
> information, even after an updated version has been released, are met
> with absolute silence.
> 
> Maybe this attitude has changed radically in the past couple of months.
> Do you have concrete evidence that they did in fact change their policy
> of handling security issues? And that the code base structurally
> improved the last 1.5 years?
> 
> Please provide it then. I do not think it's convincing to use arguments
> like "it was just dusty" to support your point. Debian had the most
> recent version of mantis when sarge released. This didn't seem to be
> quite immune from vulnerabilities.
> 
> > Lastly i wanted to note that IMO using statistical numbers that are by
> > *no way* representative isn't really a good base for arguing with a poor
> > user base. And given you do trust that this 40 counted users are a
> > representative number: For this 40 counted users mantis might be *very*
> > important. And it might be even more. There might be hundred that do not
> >  participate in popcon.
> 
> But this goes for any other package aswell - the point is that these
> numbers can be seen in a relative way: there's a lot of packages that
> have way higher numbers. The security team only has a fixed amount of
> time available to support them. If a package has an exceptionally high
> amount of work compared to a relatively low usage number, this can be a
> valid argument.

JFTR, I agree completely with the situation as Thijs has summarised it.

Cheers,
Moritz











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

Processed: Re: Bug#402770: linux-2.6: ip_conntrack module oopses

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 402770 important
Bug#402770: linux-2.6: ip_conntrack module oopses
Severity set to `important' from `critical'

> tags 402770 moreinfo
Bug#402770: linux-2.6: ip_conntrack module oopses
There were no tags set.
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#402770: linux-2.6: ip_conntrack module oopses

[Bastian Blank]

severity 402770 important
tags 402770 moreinfo
thanks

On Tue, Dec 12, 2006 at 04:08:52PM +0100, Martin Zobel-Helas wrote:
> on my mips Indy IP22 the kernel ooopses, when ipconntrack module is
> loaded and i try to ping that machine.

I don't see any other report.

> BUG: warning at kernel/softirq.c:137/local_bh_enable()

This is no Oops.

Bastian

-- 
Those who hate and fight must stop themselves -- otherwise it is not stopped.
-- Spock, "Day of the Dove", stardate unknown


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

Bug#401301: marked as done (lha: LHa Multiple Vulnerabilities)

[Debian Bug Tracking System]

Your message dated Wed, 13 Dec 2006 23:35:27 +0100
with message-id <[EMAIL PROTECTED]>
and subject line 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)

--- Begin Message ---
Package: lha
Version: 1.14i-10
Severity: grave
Tags: security
Justification: user security hole


LHA seems to be affected by 
CVE-2006-4335
CVE-2006-4337
CVE-2006-4338

See 
http://secunia.com/advisories/23153/
for details

--- End Message ---
--- Begin Message ---
Version: 1.14i-10.1
--- End Message ---

Processed: Re: Bug#402979: c2hs: Can't load in ghci (withObject missing)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 402979 serious
Bug#402979: c2hs: Can't load in ghci (withObject missing)
Severity set to `serious' from `normal'

> retitle 402979 used and generated code calls removed 'withObject' function
Bug#402979: c2hs: Can't load in ghci (withObject missing)
Changed Bug 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#402979: marked as done (used and generated code calls removed 'withObject' function)

[Debian Bug Tracking System]

Your message dated Wed, 13 Dec 2006 23:47:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402979: fixed in c2hs 0.14.5-6
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)

--- Begin Message ---
Package: c2hs
Version: 0.14.5-5
Severity: normal

% cd /usr/lib/c2hs-0.14.5
% ghci
  / _ \ /\  /\/ __(_)
 / /_\// /_/ / /  | |  GHC Interactive, version 6.6, for Haskell 98.
/ /_\\/ __  / /___| |  http://www.haskell.org/ghc/
\/\/ /_/\/|_|  Type :? for help.

Loading package base ... linking ... done.
Prelude> :load C2HS.hs
[1 of 1] Compiling C2HS ( C2HS.hs, interpreted )

C2HS.hs:82:17: Not in scope: `withObject'

C2HS.hs:86:17: Not in scope: `withObject'

C2HS.hs:100:12: Not in scope: `withObject'

C2HS.hs:110:12: Not in scope: `withObject'
Failed, modules loaded: none.
Prelude>

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages c2hs depends on:
ii  libc6 2.5-0exp3  GNU C Library: Shared libraries
ii  libgmp3c2 2:4.2.1+dfsg-4 Multiprecision arithmetic library

Versions of packages c2hs recommends:
ii  ghc6  6.6-3  GHC - the Glasgow Haskell Compilat

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: c2hs
Source-Version: 0.14.5-6

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

c2hs-doc_0.14.5-6_all.deb
  to pool/main/c/c2hs/c2hs-doc_0.14.5-6_all.deb
c2hs_0.14.5-6.diff.gz
  to pool/main/c/c2hs/c2hs_0.14.5-6.diff.gz
c2hs_0.14.5-6.dsc
  to pool/main/c/c2hs/c2hs_0.14.5-6.dsc
c2hs_0.14.5-6_i386.deb
  to pool/main/c/c2hs/c2hs_0.14.5-6_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.
Arjan Oosting <[EMAIL PROTECTED]> (supplier of updated c2hs 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, 14 Dec 2006 00:06:12 +0100
Source: c2hs
Binary: c2hs c2hs-doc
Architecture: source i386 all
Version: 0.14.5-6
Distribution: unstable
Urgency: medium
Maintainer: Arjan Oosting <[EMAIL PROTECTED]>
Changed-By: Arjan Oosting <[EMAIL PROTECTED]>
Description: 
 c2hs   - C->Haskell Interface Generator
 c2hs-doc   - C->Haskell Interface Generator -- Documentation package
Closes: 402979
Changes: 
 c2hs (0.14.5-6) unstable; urgency=medium
 .
   * debian/patches/09_replace-deprecated-withObject: Replace all
 occurrences of 'withObject' with 'with' as the deprecated 'withObject'
 was removed with GHC 6.6. (Closes: #402979)
   * Set the urgency to medium as the above bug decreases c2hs usefulness
 with GHC 6.6 dramatically.
Files: 
 a01f78b8eff0ac5fa8a011c4bd82467a 771 devel optional c2hs_0.14.5-6.dsc
 6b9d8472e987ae5caa47309273616c5f 52980 devel optional c2hs_0.14.5-6.diff.gz
 7f93d2456b1d3c4523557981c1cf1982 466098 devel optional c2hs_0.14.5-6_i386.deb
 5261cfc680c8d6f72d7ad9688076b6c9 67542 doc optional c2hs-doc_0.14.5-6_all.deb

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

iD8DBQFFgIwqUALvsZYuOJARAj2gAKDibYRxaFZNV0qE52eCu3eQxkxS3gCglyEP
UVfzLYTEky3JIny2wh1y7jk=
=qXem
-END PGP SIGNATURE-

--- End Message ---

Bug#402922: segfault in mplayer own mpeg2 library

[Pierre Habouzit]

On Wed, Dec 13, 2006 at 08:56:52PM +0100, A Mennucc wrote:
> Pierre Habouzit ha scritto:
> > On Wed, Dec 13, 2006 at 05:53:03PM +0100, A Mennucc wrote:
> >> we should understand why  ref==0
> >>
> >> anyway I will add an assert
> > 
> >   O_o *blink* *blink*
> >
> >   do you know that assert is a macro that may be disabled if for some
> > reason the build system defines NDEBUG ?!
> 
> you are criticizing my way of solving this bug *even before I sit down
> and start writing the code*
> 
> even supposing that
> - I would use assert(ref)
> - the code is compiled with NDEBUG
> did you consider the fact that I will check my patch against your
> foobar.mpeg, in the end, to make sure that it will work?
> 
> congratulations! you really know how to go along and collaborate with
> other people
> (yes that is sarcasm)

  I did not proposed to use assert to fix bugs in the first place.

  FYI, the patch to compile against debian's libmpeg2.a (yes using your
beloved static compiling) is ridiculously small (see attachment). I
won't quote the mail full of hate where you state that you will never
use that, I'm not *that* mean. Though, it seems the problem is not only
there, but also in the sole 270-line long file libmpcodecs/vd_libmpeg2.c
that is the sole one to use the mpeg2 library.

  it has the very very very bad idea to use mpeg2 internals and to deal
with mpeg2dec_t initialization by itself. As a result, even using
debian's libmpeg2 make it fail, so I suppose that the culprit is in
vd_libmpeg2.c. I must reckon I've not enough knowledge to procede with
further tests and debugging. But knowing that the problem *only* lies in
that 211-slocs long file, I've good hope that someone more skilled with
video thingies can fix that for real.


  Cheers,
-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
diff -u mplayer-1.0~rc1/debian/control.in mplayer-1.0~rc1/debian/control.in
--- mplayer-1.0~rc1/debian/control.in
+++ mplayer-1.0~rc1/debian/control.in
@@ -11,7 +11,7 @@
  (>= 0.0.0.alpha3-1), libesd0-dev, libasound2-dev (>= 1.0.6-3),
  libvorbis-dev, liblircclient-dev, libfreetype6-dev, libdvdread3-dev,
  libcdparanoia0-dev, libfontconfig1-dev, libjpeg62-dev, libungif4-dev,
- libgtk2.0-dev, libdirectfb-dev, libcaca-dev, @XLIBS@, @EXTRA_BUILDDEP@
+ libgtk2.0-dev, libdirectfb-dev, libcaca-dev, libmpeg2-4-dev, @XLIBS@, @EXTRA_BUILDDEP@
 
 Package: @MPLAYER@
 Architecture: any
diff -u mplayer-1.0~rc1/debian/control mplayer-1.0~rc1/debian/control
--- mplayer-1.0~rc1/debian/control
+++ mplayer-1.0~rc1/debian/control
@@ -11,7 +11,7 @@
  (>= 0.0.0.alpha3-1), libesd0-dev, libasound2-dev (>= 1.0.6-3),
  libvorbis-dev, liblircclient-dev, libfreetype6-dev, libdvdread3-dev,
  libcdparanoia0-dev, libfontconfig1-dev, libjpeg62-dev, libungif4-dev,
- libgtk2.0-dev, libdirectfb-dev, libcaca-dev, libx11-dev, libxext-dev, libxinerama-dev, libxv-dev, libxvmc-dev, libxxf86dga-dev, libxxf86vm-dev, x-dev, 
+ libgtk2.0-dev, libdirectfb-dev, libcaca-dev, libmpeg2-4-dev, libx11-dev, libxext-dev, libxinerama-dev, libxv-dev, libxvmc-dev, libxxf86dga-dev, libxxf86vm-dev, x-dev, 
 
 Package: mplayer
 Architecture: any
only in patch2:
unchanged:
--- mplayer-1.0~rc1.orig/Makefile
+++ mplayer-1.0~rc1/Makefile
@@ -177,7 +177,7 @@
 PARTS += liba52
 endif
 ifeq ($(LIBMPEG2),yes)
-PARTS += libmpeg2
+#PARTS += libmpeg2
 endif
 ifeq ($(FAAD_INTERNAL),yes)
 COMMON_LIBS += libfaad2/libfaad2.a 
@@ -231,8 +231,8 @@
 COMMON_LIBS += liba52/liba52.a
 endif
 ifeq ($(LIBMPEG2),yes)
-COMMON_DEPS += libmpeg2/libmpeg2.a
-COMMON_LIBS += libmpeg2/libmpeg2.a
+#COMMON_DEPS += libmpeg2/libmpeg2.a
+COMMON_LIBS += /usr/lib/libmpeg2.a
 endif
 ifeq ($(FAAD_INTERNAL),yes)
 COMMON_DEPS += libfaad2/libfaad2.a


pgplokV8FIN61.pgp
Description: PGP signature

Processed: sorry, my bad

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> #> > retitle -1 mplayer do not support nostrip/noopt and is in C [violates 
> policy §10.1]
> #> Bug#402950: mplayer FTBFS with DEB_BUILD_OPTS=debug
> #> Changed Bug title.
> severity 402950 important
Bug#402950: mplayer do not support nostrip/noopt and is in C [violates policy 
§10.1]
Severity set to `important' from `serious'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Bug#401873: closed by Stephen Gran <[EMAIL PROTECTED]> (Bug#401873: fixed in clamav 0.90~rc2-1)

[Stephen Gran]

This one time, at band camp, Hendrik Weimer said:
> The bug is still present in 0.88.7. Files nested deeper than
> --max-mail-recursion are not scanned and there is no error returned
> (exit code is 0). When using clamscan I get a warning from libclamav,
> but the EICAR string still passes.

There were two bugs:
ClamAV would falsely pass an oddly formatted but legitimate MIME encoding.
ClamAV could potentially crash on a deeply nested MIME structure.

Both of these are fixed.  If you would like to open a new bug
reporting that ClamAV allows viral attachments when they are nested
too deeply, please do so.  That was not my understanding of either
of the vulnerabilities addressed in these bug reports.  Of course,
I would like to see a patch that allows ClamAV to efficiently scan
infinitely recursively nested MIME parts, since once you set a limit,
your complaint always holds - it is just a matter of depth.  It could be
implemented such that a message with too much recursion generates a
pseudo virus tag, but there are alreasdy open bugs about other responses
of that type, so I think some will dispute that logic.

Take care,
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :[EMAIL PROTECTED] |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature

Bug#402331: FTBFS: "unable to find user alias"

[Stephen Gran]

This one time, at band camp, Thomas Huriaux said:
> Jon Marler <[EMAIL PROTECTED]> (12/12/2006):
> > Quoting Thomas Huriaux <[EMAIL PROTECTED]>:
> > > fatal: unable to find user alias
> > 
> > This pops up now and again ... You have attempted to build the package
> > without installing it first.  If you install the package, the install
> > scripts will create that user for you.
> > 
> > If you don't want to do that, feel free to add any missing users
> > yourself.

Erm, that seems like it's contrary to the normal way of dealing with
software, but let's let that pass.

> > If you want to know why this is an issue, ask the people than fund
> > Debian, as they are the ones that demanded the "qmail users" be
> > removed from the default passwd file because qmail is considered
> > "non-free"  If you dig through the old bug reports for qmail-src, you
> > will see a bug that added in the code to add the users.

I think you are letting your crankiness interfere with your logic.  The
people arguing that qmail is non-free are a different group than those
that have anything to do with funding anything.  If you can't adequately
maintain the package, say so instead of finding random third parties to
explode at.  Being unable to maintain qmail strikes me as a good thing,
frankly, and nothing to be ashamed of.
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :[EMAIL PROTECTED] |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature

Bug#402331: FTBFS: "unable to find user alias"

[Jon Marler]

Quoting Stephen Gran <[EMAIL PROTECTED]>:

> I think you are letting your crankiness interfere with your logic.  The
> people arguing that qmail is non-free are a different group than those
> that have anything to do with funding anything.  If you can't adequately
> maintain the package, say so instead of finding random third parties to
> explode at.  Being unable to maintain qmail strikes me as a good thing,
> frankly, and nothing to be ashamed of.

Actually, to be exactly precise, it was a board decision to remove the qmail
users  from Debian's default passwd file.  I worked with Wichert Akkerman on
removing these users, and he is the one who told me the decision came from the
board, which funds Debian.  I'm not just making this stuff up ... Don't take my
word for it, ask Wichert.

Also read:
  http://lists.debian.org/debian-devel/1999/11/msg01176.html

http://packages.debian.org/changelogs/pool/main/b/base-passwd/base-passwd_3.4.1/changelog

Again, I can't force them to add the users back in, and I most definitely can't
fix everyone's system.  The compromise made YEARS ago was to add a script that
will add the users when the qmail-src package is installed to save the user the
trouble of doing it themselves.

The way qmail works in Debian is a hack.  It's ugly, and it's not the most
graceful thing, but it works.  You both seem like smart guys, and I'm sure you
can figure out how to add a user.  I'm not the one who wrote qmail such that it
requires specific users to be present before you build, hardcoding the uid/gid's
into the compiled package, that was DJB.  If you install qmail-src, or manually
add the users, the package builds fine.  If you don't like it, feel free to
take it up with DJB, or mark the bug as sent-upstream.  From my experience with
DJB, you have a snowball's chance in hell at getting as much as an email back
from him ... good luck!

Debian and Qmail had a rather ugly parting of ways early on in the life of the
distribution.  At one point in time, all of the official Debian mailsevers were
Qmail servers.  After the unfortunate ugliness (which was before my time) qmail
ended up the non-free red-headed bastard stepchild it is today.  It languished
for a while, and I ended up taking over the package for Phil Hands and got 1.03
hacked in.  I have made 40 releases of qmail since I started managing the
package, and take it quite seriously.

Your childish comments at the end there made me chuckle.  It's very typical of
Debian package maintainers, and the #1 reason I stopped reading -private years
ago.

Cheers!

Jon



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

Bug#362952: xine-ui: similar problem in gnome w/ metacity

[Wim De Smet]

Package: xine-ui
Version: 0.99.4+dfsg+cvs2006-1
Followup-For: Bug #362952

I'm seeing a similar problem in gnome with metacity as window manager.
When I press 'g' in full screen mode the GUI does pop up but I can only
see it when I exit full screen mode.


-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16-2-k7
Locale: LANG=nl_BE.ISO-8859-1, LC_CTYPE=nl_BE.ISO-8859-1 (charmap=ISO-8859-1)

Versions of packages xine-ui depends on:
ii  libc6   2.3.6.ds1-4  GNU C Library: Shared libraries
ii  libcaca00.99.beta11.debian-1 colour ASCII art library
ii  libcomerr2  1.39-1   common error description library
ii  libcucul0   0.99.beta11.debian-1 low-level Unicode character drawin
ii  libcurl3-gnutls 7.15.5-1 Multi-protocol file transfer libra
ii  libfontconfig1  2.4.1-1  generic font configuration library
ii  libgnutls13 1.4.2-1  the GNU TLS library - runtime libr
ii  libidn110.6.5-1  GNU libidn library, implementation
ii  libkrb531.4.4-1  MIT Kerberos runtime libraries
ii  libncurses5 5.5-3Shared libraries for terminal hand
ii  libpng12-0  1.2.8rel-5.2 PNG library - runtime
ii  libreadline55.2-1GNU readline and history libraries
ii  libx11-62:1.0.0-8X11 client-side library
ii  libxext61:1.0.1-2X11 miscellaneous extension librar
ii  libxft2 2.1.8.2-8FreeType-based font drawing librar
ii  libxine11.1.2-6  the xine video/media player librar
ii  libxinerama11:1.0.1-4.1  X11 Xinerama extension library
ii  libxtst61:1.0.1-5X11 Testing -- Resource extension 
ii  libxv1  1:1.0.1-5X11 Video extension library
ii  libxxf86vm1 1:1.0.0-4X11 XFree86 video mode extension l
ii  zlib1g  1:1.2.3-13   compression library - runtime

Versions of packages xine-ui recommends:
ii  libaa11.4p5-30   ascii art library

-- no debconf information


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

Bug#398058: [NFS] nhfsstone license

[Steinar H. Gunderson]

On Mon, Nov 20, 2006 at 05:20:34PM -0500, J. Bruce Fields wrote:
> No modification required if we remove it from upstream too.  Do people
> use it?

It seems like nobody does, judging from the response. Is there any chance of
a relatively quick 1.0.11 without nhfsstone? We have frozen in Debian at the
moment, but fixing such a license bug would probably be allowed past the
freeze.

/* Steinar */
-- 
Homepage: http://www.sesse.net/


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

Bug#402679: backupninja: mysql handler overwrites existing backups, even if mysqldump fails

[Joel Fuster]

Hi,

Thanks for the quick response.

> This only occurs when you specify databases and you have compress=no,
> mysqld isn't running or mysqdump doesn't exist. This is a pretty
> unique combination of events!

Please note that this happened to me (and I tested again) with 
"compress=yes".  I refer to "sql.gz" files in my original report.  But 
yes, it looks like it only happens when you specify databases and one of 
the other two conditions.


> Backupninja is designed with the expectation that the backups that you
> are making of your databases are being backed up to another system or
> another disk using one of the handlers such as rdiff, duplicity, rsnap,
> dup, etc. It is expected that the mysqldumps that are made in your
> backup directory are not the end of the backup, but rather this are
> shipped off in the remainder of the process. Although I agree its a bad
> situation to be in to create a zero-byte mysql dump, I am hesitant to
> agree that this is causes serious data loss. Using that logic, you could
> claim that backupninja causes serious data loss when you delete
> everything from your database and then you do a backup of an empty
> database, or likewise.

According to the guidance provided by "reportbug", "critical", due to 
serious data loss, seems to be the correct choice.  "serious" bugs are 
for data loss of "unimportant" data or data that can be recovered 
*without* resorting to a backup.  If mysql corrupts my database and dies 
(a plausible scenario that in fact was my problem), then the mysql dumps 
are overwritten with empty files, I better hope I did the smart thing 
and have daily backups that allow me to go back at least 1 day before 
the catastrophe.


The scenario above is much different than the *intentional* act of 
deleting all of my data from the database...in that case backupninja 
would just be copying exactly what I put in--garbage in, garbage out.


Thanks again,

Joel





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

Bug#403004: kmail: Kmail does not start after sarge->etch upgrade

[Alexander Litvinov]

Package: kmail
Version: 4:3.5.5.dfsg.1-2
Severity: grave
Justification: renders package unusable

I have updgraded from sarge to etch at 14 dec 2006. After this upgrade
my kmail does not start. Just after starting it shows KDE's crash
window with the text (not exact, translated from russian):
Application kmail has broken with signal 11 (SIGSEGV). Stack trace will
be included later.

When I am running kmail from konsole I saw:
-- konsole start --
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "move_message_to_folder"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "copy_message_to_folder"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "jump_to_folder"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "remove_duplicate_messages"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "cancel"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "inc_current_folder"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "dec_current_folder"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "select_current_folder"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "inc_current_message"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "dec_current_message"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "select_current_message"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "delete"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "edit"
kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action.
kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel 
object already contains an action name "display_message"
ERROR: Communication problem with kmail, it probably crashed.
KCrash: Application 'kmail' crashing...
-- konsole end --

The stack trace is:
-- stack start --
(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1248647488 (LWP 3514)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debug

Bug#402834: Package asks debconf questions for what? :)

[Thomas Goirand]

Steffen Joeris wrote:
> Package: dtc
> Severity: serious
> 
> Hi dude
> 
> Thanks for deactivating the postinst/prerm scripts for now.
> However the current package still has the config script which inputs a
> lot of debconf questions, but by that users only get confused, because
> they answer the questions and nothing really happens (which is good).
> So I recommend removing the config script for now or at least reviewing
> it and only doing the stuff you can do with your package.
> 
> Cheers
> Steffen

Hello,

I'm currently working on it, but I'm a bit busy this week. A new version
of the installer will be released. Just give me the time to work on it.

Thomas


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

Bug#403004: User-specific?

[Filipus Klutiero]

Does this reproduce with a newly-created user?


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

Bug#403022: Non-existent vlcintf.xpt file!

[Arias Hung]

Package: mozilla-plugin-vlc
Version: 0.8.6-svn20061012.debian-1
Severity: grave

The file /usr/lib/mozilla-firefox/components/vlcintf.xpt is apparently 
non-existent since all it is is a relative symbolic link to vlcintf.xpt in the 
/usr/lib/mozilla/components directory which is NOT provided by this package.

e.g.

$ ls -l /usr/lib/mozilla-firefox/components/
total 0
lrwxrwxrwx 1 root root 36 2006-12-13 21:16 vlcintf.xpt -> 
../../mozilla/components/vlcintf.xpt

The above is a broken symbolic link since this package does NOT provide 
vlcintf.xpt in /usr/lib/mozilla/components:


$ dpkg -L  mozilla-plugin-vlc
/.
/usr
/usr/lib
/usr/lib/mozilla
/usr/lib/mozilla/plugins
/usr/lib/mozilla/plugins/libvlcplugin.so
/usr/lib/mozilla-firefox
/usr/lib/mozilla-firefox/plugins
/usr/lib/mozilla-firefox/components
/usr/share
/usr/share/doc
/usr/lib/mozilla-firefox/plugins/libvlcplugin.so
/usr/lib/mozilla-firefox/components/vlcintf.xpt
/usr/share/doc/mozilla-plugin-vlc


This is probably the source of all the outstanding bugs for this package these 
past few months.

-- System Information:
Debian Release: 4.0 by Linux-Systeme
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'edgy'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-emission1-1000hz
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=UTF-8)

Versions of packages mozilla-plugin-vlc depends on:
ii  libc6 2.3.6.ds1-10   GNU C Library: Shared libraries
ii  libgcc1   1:4.2-20060923-1   GCC support library
ii  libice6   1:1.0.1-2  X11 Inter-Client Exchange library
ii  libsm61:1.0.1-3  X11 Session Management library
ii  libstdc++64.2-20060923-1 The GNU Standard C++ Library v3
ii  libvlc0   0.8.6-svn20061012.debian-1 multimedia player and streamer lib
ii  libx11-6  2:1.0.3-4  X11 client-side library
ii  libxt61:1.0.2-2  X11 toolkit intrinsics library
ii  vlc   0.8.6-svn20061012.debian-1 multimedia player and streamer
ii  vlc-nox   0.8.6-svn20061012.debian-1 multimedia player and streamer (wi

mozilla-plugin-vlc recommends no packages.


pgpqc0dzrCbdk.pgp
Description: PGP signature

Bug#401660: #401660 digikam: Crash on startup (sometimes)

[Gregor Hoffleit]

Just for the record, I want to add that I (as the reporter of this
specific bug) can confirm that the specific problem reported in this
Debian bug #401660 really goes away when I compile digikam 0.9.0-rc2 and
exiv2 0.12 from sources.

Whatever that helps for the decision about etch ;-)

Regards,
Gregor


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