Processed: tagging 568193

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 568193 - security
Bug #568193 [pypibrowser] pypibrowser: Missing dependencies
Ignoring request to alter tags of bug #568193 to the same tags previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: trying again

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 block 564661 by 561475
Bug #564661 [libgsasl7] libgsasl7: did not work any auth metods
Bug #565134 [libgsasl7] mpop: Does not work with gsasl 1.4
Bug #566104 [libgsasl7] msmtp: unable to use authentication method LOGIN
Was not blocked by any bugs.
Added blocking bug(s) of 564661: 561475
Was not blocked by any bugs.
Added blocking bug(s) of 565134: 561475
Was not blocked by any bugs.
Added blocking bug(s) of 566104: 561475
 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#554790: grub-pc: store grub-pc/install_devices using by-id

[Harald Dunkel]

Colin Watson wrote:
 UUIDs are properties of filesystems, not disks or partitions, and the
 MBR of a hard disk does not have a UUID.

Since MSDOS partitions are limited to 2TByte partitions anyway, it
might be wise to look at alternatives, e.g. GPT. GPT _does_ provide
a UUID in the disk header _and_ in the header of each partition.

Wikipedia provides an excellent overview:

http://en.wikipedia.org/wiki/GUID_Partition_Table

 For disks, the choices for
 stable identifiers are based on either the hardware serial number or the
 bus path taken to reach the disk.

What about block device emulations, e.g. software RAIDs, LVM, etc?


Just my $0.02. Regards

Harri



signature.asc
Description: OpenPGP digital signature

Processed: tagging 568193

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 568193 - security
Bug #568193 [pypibrowser] pypibrowser: Missing dependencies
Ignoring request to alter tags of bug #568193 to the same tags previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568223: hibernate to disk crashes the system

[W. Martin Borgert]

Package: linux-2.6
Version: 2.6.32-5
Severity: critical

Justification for critical: Crashes the complete system,
including unrelated software. If this kind of problem is
typically not considered as critical, please adjust.

With 2.6.30 hibernating to disk worked (most of the time, but
not always). With 2.6.32 the system crashes immediately when
trying to hibernate from Gnome and I have to switch off the
computer. How can I debug the problem? Are there any interesting
log files or useful shell commands?

-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-686 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc 
version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 06:32:16 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-trunk-686 root=/dev/mapper/vg0-lv0 ro quiet

** Not tainted

** Kernel log:
[5.611015] sd 1:0:0:0: [sda] Write Protect is off
[5.611019] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[5.611042] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[5.611180]  sda:
[5.615167] ide-cd driver 5.00
[5.617025] ide-cd: hda: ATAPI 24X DVD-ROM DVD-R/RAM CD-R/RW drive, 2048kB 
Cache
[5.617031] Uniform CD-ROM driver Revision: 3.20
[5.638283]  sda1 sda2 sda3
[5.638551] sd 1:0:0:0: [sda] Attached SCSI disk
[5.839180] device-mapper: uevent: version 1.0.3
[5.839358] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: 
dm-de...@redhat.com
[8.684415] usb-storage: device scan complete
[8.686532] scsi 0:0:0:0: Direct-Access Generic  STORAGE DEVICE   9407 
PQ: 0 ANSI: 0
[8.688396] sd 0:0:0:0: [sdb] Attached SCSI removable disk
[   26.908953] atkbd.c: Unknown key pressed (translated set 2, code 0x83 on 
isa0060/serio0).
[   26.908958] atkbd.c: Use 'setkeycodes e003 keycode' to make it known.
[   51.845837] PM: Starting manual resume from disk
[   51.930463] kjournald starting.  Commit interval 5 seconds
[   51.930470] EXT3-fs: mounted filesystem with ordered data mode.
[   58.069378] udev: starting version 150
[   62.328333] ACPI: SSDT 7f687ee3 0027A (v01  PmRef  Cpu0Ist 3000 INTL 
20050624)
[   62.328878] ACPI: SSDT 7f687874 005EA (v01  PmRef  Cpu0Cst 3001 INTL 
20050624)
[   62.344371] input: PC Speaker as /devices/platform/pcspkr/input/input6
[   62.376259] Monitor-Mwait will be used to enter C-1 state
[   62.376287] Monitor-Mwait will be used to enter C-2 state
[   62.376294] Marking TSC unstable due to TSC halts in idle
[   62.376388] processor LNXCPU:00: registered as cooling_device2
[   62.376857] Switching to clocksource hpet
[   62.392296] ACPI: SSDT 7f68815d 000C8 (v01  PmRef  Cpu1Ist 3000 INTL 
20050624)
[   62.392620] ACPI: SSDT 7f687e5e 00085 (v01  PmRef  Cpu1Cst 3000 INTL 
20050624)
[   62.420363] processor LNXCPU:01: registered as cooling_device3
[   62.452139] ACPI: Battery Slot [BAT0] (battery present)
[   62.468115] ACPI: AC Adapter [ADP1] (on-line)
[   62.492107] ACPI: Battery Slot [BAT1] (battery absent)
[   62.512866] parport_pc 00:09: reported by Plug and Play ACPI
[   62.512928] parport0: PC-style at 0x378, irq 5 [PCSPP,TRISTATE]
[   62.684142] i801_smbus :00:1f.3: PCI INT C - GSI 19 (level, low) - IRQ 
19
[   62.684149] ACPI: I/O resource :00:1f.3 [0x1c00-0x1c1f] conflicts with 
ACPI region SMBI [0x1c00-0x1c0f]
[   62.707028] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   63.296264] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x81a0b1, caps: 
0xa04753/0x20
[   63.329932] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio4/input/input7
[   63.753288] Linux video capture interface: v2.00
[   63.938493] HDA Intel :00:1b.0: enabling device (0104 - 0106)
[   63.938503] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 
16
[   63.938546] HDA Intel :00:1b.0: setting latency timer to 64
[   64.216453] hda_codec: ALC262: BIOS auto-probing.
[   64.217467] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input8
[   64.270869] uvcvideo: Found UVC 1.00 device FO13FF-65-1 PC-CAM (05c8:0103)
[   64.275334] input: FO13FF-65-1 PC-CAM as 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3:1.0/input/input9
[   64.275442] usbcore: registered new interface driver uvcvideo
[   64.275480] USB Video Class driver (v0.1.0)
[   66.411087] EXT3 FS on dm-1, internal journal
[   66.772449] loop: module loaded
[   68.846173] kjournald starting.  Commit interval 5 seconds
[   68.846430] EXT3 FS on sda1, internal journal
[   68.846435] EXT3-fs: mounted filesystem with ordered data mode.
[   68.880327] kjournald starting.  Commit interval 5 seconds
[   68.880692] EXT3 FS on sda3, internal journal
[   68.880696] EXT3-fs: mounted filesystem with ordered data mode.
[   68.942335] Adding 2928632k swap on /dev/mapper/vg0-lv1.  Priority:-1 
extents:1 across:2928632k 
[   71.961054] sky2 eth0: enabling interface
[   71.961266] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   

Bug#568157: marked as done (life: FTBFS on kfreebsd-*: PETSc could not be found.)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 09:37:46 +
with message-id e1ncbga-0005oa...@ries.debian.org
and subject line Bug#568157: fixed in life 0.9.17-1
has caused the Debian Bug report #568157,
regarding life: FTBFS on kfreebsd-*: PETSc could not be found.
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
568157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: life
Version: 0.9.16-1
Severity: serious
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

too bad you uploaded .16-1 so quickly after .15-2, which built
successfully but never had a chance to get accepted. Anyway, back on
topic, FTBFS on kfreebsd-*:
| -- /usr/include/metis
| -- petsc_arch linux-gnu-c-opt
| CMake Error at 
/usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:70 (MESSAGE):
|   PETSc could not be found.  Be sure to set PETSC_DIR and PETSC_ARCH.
|   (missing: PETSC_INCLUDES PETSC_LIBRARIES)
| Call Stack (most recent call first):
|   cmake/FindPETSc.cmake:220 (find_package_handle_standard_args)
|   CMakeLists.txt:111 (FIND_PACKAGE)

Full build logs:
  https://buildd.debian.org/status/package.php?suite=unstablep=life

Mraw,
KiBi.


---End Message---
---BeginMessage---
Source: life
Source-Version: 0.9.17-1

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

liblife-dbg_0.9.17-1_amd64.deb
  to main/l/life/liblife-dbg_0.9.17-1_amd64.deb
liblife-dev_0.9.17-1_amd64.deb
  to main/l/life/liblife-dev_0.9.17-1_amd64.deb
liblife_0.9.17-1_amd64.deb
  to main/l/life/liblife_0.9.17-1_amd64.deb
life-apps_0.9.17-1_amd64.deb
  to main/l/life/life-apps_0.9.17-1_amd64.deb
life-doc_0.9.17-1_all.deb
  to main/l/life/life-doc_0.9.17-1_all.deb
life_0.9.17-1.diff.gz
  to main/l/life/life_0.9.17-1.diff.gz
life_0.9.17-1.dsc
  to main/l/life/life_0.9.17-1.dsc
life_0.9.17.orig.tar.gz
  to main/l/life/life_0.9.17.orig.tar.gz



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 568...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christophe Prud'homme prudh...@debian.org (supplier of updated life 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 03 Feb 2010 07:09:10 +0100
Source: life
Binary: liblife liblife-dev liblife-dbg life-apps life-doc
Architecture: source all amd64
Version: 0.9.17-1
Distribution: unstable
Urgency: low
Maintainer: Debian Scientific Computing Team 
pkg-scicomp-de...@lists.alioth.debian.org
Changed-By: Christophe Prud'homme prudh...@debian.org
Description: 
 liblife- A library for the finite element method
 liblife-dbg - A library for the finite element method
 liblife-dev - A library for the finite element method
 life-apps  - A library for the finite element method
 life-doc   - A library for the finite element method
Closes: 568157
Changes: 
 life (0.9.17-1) unstable; urgency=low
 .
   * New upstream release
   * Bug fix: FTBFS on kfreebsd-*: PETSc could not be found., thanks to
 Cyril Brulebois (Closes: #568157).
Checksums-Sha1: 
 de46a35f61353030e8619beb63b074897eae4c92 1688 life_0.9.17-1.dsc
 bf59737c318c747b2169a6c29bf99323f31d31df 2723924 life_0.9.17.orig.tar.gz
 19830f3ad543b2af1b6a28717674365c7dd0a7a4 8103 life_0.9.17-1.diff.gz
 e9146b0276b8d8dee80f1d514c343f5db1bc5f5e 1445740 life-doc_0.9.17-1_all.deb
 adbd67868afd77b79cf50ca999f0d6c7125a38d9 3140204 liblife_0.9.17-1_amd64.deb
 7dfa4e5ca2c27a4790e4a425df116951e6691a3f 748108 liblife-dev_0.9.17-1_amd64.deb
 a83d5d8d54fa1976882eef9fdf304259357b103d 539454 liblife-dbg_0.9.17-1_amd64.deb
 ce566a391fcee390520a60f3e68638704bd51c0f 38925298 life-apps_0.9.17-1_amd64.deb
Checksums-Sha256: 
 d984b1d5c4333523e565724010ff9e3fd85ab7dc5eabfcda20aa5b37d10a9ba9 1688 
life_0.9.17-1.dsc
 63ee1bc10f1ac3f51a187a8ce3f0c0396dcc20b72bd82753bc66470c7ef1a5a2 2723924 
life_0.9.17.orig.tar.gz
 59521b34e97ce112c677e0c140b35f9e05779cd385208e8c934079b98df99691 8103 
life_0.9.17-1.diff.gz
 eab310eb2a2b776c55d1e8b15a390cac820cd57d9bb274c314678dd73272898c 1445740 
life-doc_0.9.17-1_all.deb
 3e84c3ebf4d4f7a6d0672d6d682d025a949968de13827cd07184ce94230b7c51 3140204 

Bug#519855: marked as done (wwwoffle root CA certificate expiry freezes boot)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 09:41:08 +
with message-id e1ncbjq-00063d...@ries.debian.org
and subject line Bug#519855: fixed in wwwoffle 2.9f-1
has caused the Debian Bug report #519855,
regarding wwwoffle root CA certificate expiry freezes boot
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
519855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: wwwoffle
Version: 2.9d-3
Severity: critical
X-debbugs-Cc: wwwoffle-us...@gedanken.demon.co.uk,a...@gedanken.demon.co.uk

Dear Debian WWWOFFLE maintainer: when wwwoffle's certificate expires,
http://mid.gmane.org/87fxhha9j2@jidanni.org
http://mid.gmane.org/fcaeb9bf0903111614t787a2cd5k362ff3878e2f5...@mail.gmail.com
booting waits for it to be rebuilt, which may take forever, i.e.,
cannot boot, depending on ones system, especially at boot time when
there is little entropy.

The notice The WWWOFFLE root CA files don't exist. Please
stand by while these are generated (this may take very long, depending
on your system). only is seen in the logs, not on the screen. Nor are
there progress indicators. Even on gigahertz systems, minutes go by
with the user staring at frozen boot messages, which may be underneath
a splashscreen, e.g., on a cellphone, where half an hour will go by
with no sign of whenever one might be able to finish booting.

I repeat, there is not enough entropy at boot. You effectively lock
users out of the whole system with this ticking time bomb.

Workaround:
Reboot (CTRL-ALT-DEL) into single user mode.
update-rc.d -f wwwoffle remove
or boot from emergency Knoppix etc. CD and 
rm /etc/rc?.d/S20wwwoffle and reboot.

Later after boot, when it will no longer make the whole system wait,
and there is more entropy, one may try removing the empty
/etc/wwwoffle/certificates/root/root-key.pem and rebuilding it using
/etc/init.d/wwwoffle start.

If after many minutes this never completes, consider copying it from a
machine that has one...?

Then
# update-rc.d wwwoffle default

Another consideration is how to install wwwoffle on smaller devices in
the first place. One can only copy the certificate by hand from
another machine.

Anyway, in the http://news.gmane.org/gmane.network.wwwoffle.user there
is mention about redesigns, as apparently this time bomb has gone off
at about the same time for several people...


---End Message---
---BeginMessage---
Source: wwwoffle
Source-Version: 2.9f-1

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

wwwoffle_2.9f-1.diff.gz
  to main/w/wwwoffle/wwwoffle_2.9f-1.diff.gz
wwwoffle_2.9f-1.dsc
  to main/w/wwwoffle/wwwoffle_2.9f-1.dsc
wwwoffle_2.9f-1_amd64.deb
  to main/w/wwwoffle/wwwoffle_2.9f-1_amd64.deb
wwwoffle_2.9f.orig.tar.gz
  to main/w/wwwoffle/wwwoffle_2.9f.orig.tar.gz



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 519...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Slootman p...@debian.org (supplier of updated wwwoffle 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 25 Jan 2010 19:06:31 +0100
Source: wwwoffle
Binary: wwwoffle
Architecture: source amd64
Version: 2.9f-1
Distribution: unstable
Urgency: low
Maintainer: Paul Slootman p...@debian.org
Changed-By: Paul Slootman p...@debian.org
Description: 
 wwwoffle   - World Wide Web OFFline Explorer
Closes: 242778 384868 504679 506381 510508 519855 527235 529916 530495 535741 
559386 560181 564475 566553
Changes: 
 wwwoffle (2.9f-1) unstable; urgency=low
 .
   * New upstream release.
   * Acknowledge NMU
   * Fix building with gnutls (fix is in new upstream)
 closes:#564475,#529916
   * New upstream contains updated config.{guess,sub}
 closes:#535741
   * init.d script shouldn't fail doing stop if daemon wasn't running.
 That may be the right thing philosophically, but lots of things break.
 closes:#506381,#566553,#560181
   * Updated Standards-Version to 3.8.3.
   * Check during start and restart whether the certificate is to expire within
 a week, and say so. Also use faster certificate generation.
 Also check in cron.daily script 

Bug#560181: marked as done (can't purge wwwoffle (action stop failed))

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 09:41:09 +
with message-id e1ncbjr-000647...@ries.debian.org
and subject line Bug#560181: fixed in wwwoffle 2.9f-1
has caused the Debian Bug report #560181,
regarding can't purge wwwoffle (action stop failed)
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
560181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: wwwoffle
Version: 2.9d-3
Severity: grave
Justification: renders package unusable

I want to purge the package, but it doesn't work, breaking the
packaging system...

# dpkg --purge wwwoffle
(Reading database ... 106391 files and directories currently installed.)
Removing wwwoffle ...
Stopping HTTP cache proxy server: wwwoffled...can't connect to control socket.
Trying to signal daemon process...failed, daemon was not running.
invoke-rc.d: initscript wwwoffle, action stop failed.
dpkg: error processing wwwoffle (--purge):
 subprocess installed pre-removal script returned error exit status 1
Checking for htdig package...
Fixing ownership of spooldirs in the background.
Starting HTTP cache proxy server: wwwoffled notice:
The WWWOFFLE root CA files don't exist. Please stand by while these are
generated (this may take very long, depending on your system).
wwwoffled[2752] Important: WWWOFFLE Demon Version 2.9d (with ipv6,with 
zlib,with gnutls) started.
wwwoffled[2752] Warning: Could not import private key [Base64 unexpected header 
error.].
wwwoffled[2752] Fatal: The WWWOFFLE root CA private key file 
'certificates/root/root-key.pem' cannot be loaded; delete problem file and 
start WWWOFFLE again to recreate it.
invoke-rc.d: initscript wwwoffle, action start failed.
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 wwwoffle

Note: wwwoffle is currently half-installed because the upgrade to
2.9d-3 partially failed, and I currently can't fix that.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (500, 'oldstable'), (200, 
'unstable')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.26-1-powerpc
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages wwwoffle depends on:
ii  coreutils  7.4-2 The GNU core utilities
ii  debconf [debconf-2.0]  1.5.28Debian configuration management sy
ii  debianutils3.2.2 Miscellaneous utilities specific t
ii  libc6  2.10.2-2  GNU C Library: Shared libraries
ii  libgnutls262.8.4-1   the GNU TLS library - runtime libr
ii  zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime

wwwoffle recommends no packages.

Versions of packages wwwoffle suggests:
pn  htdig | namazu | mnogosearch- none (no description available)
ii  logrotate 3.7.8-4Log rotation utility
pn  pdnsd none (no description available)

-- debconf information:
* wwwoffle/string_port_number: 8080
  wwwoffle/ageline_added:
  wwwoffle/use-htdig: false
  wwwoffle/ppp-fetch: false
* wwwoffle/use-ppp-interface: false
  wwwoffle/ageline_lost:
  wwwoffle/text_new_location:
  wwwoffle/conf-perm:
* wwwoffle/passwd: (password omitted)
* wwwoffle/string_parent_proxy: none
* wwwoffle/select_html_lang: fr (French)
  wwwoffle/ipv6defaultnone:
* wwwoffle/fetchfrequency: 30
  wwwoffle/note_upgrade_config_failed:


---End Message---
---BeginMessage---
Source: wwwoffle
Source-Version: 2.9f-1

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

wwwoffle_2.9f-1.diff.gz
  to main/w/wwwoffle/wwwoffle_2.9f-1.diff.gz
wwwoffle_2.9f-1.dsc
  to main/w/wwwoffle/wwwoffle_2.9f-1.dsc
wwwoffle_2.9f-1_amd64.deb
  to main/w/wwwoffle/wwwoffle_2.9f-1_amd64.deb
wwwoffle_2.9f.orig.tar.gz
  to main/w/wwwoffle/wwwoffle_2.9f.orig.tar.gz



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 560...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Slootman p...@debian.org (supplier of updated wwwoffle package)

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

Bug#568217: marked as done (wrong dependencies lead to an uninstallable package)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 09:39:52 +
with message-id e1ncbic-0005h4...@ries.debian.org
and subject line Bug#568217: fixed in qscintilla2 2.4.2-3
has caused the Debian Bug report #568217,
regarding wrong dependencies lead to an uninstallable package
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
568217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libqscintilla2-dev
Version: 2.4.2-2
Severity: grave

Hi,

I assume there went something wrong with the latest packaging updates of 
qscintilla2.
The current -dev package depends on
libqscintilla2 (= 2.4.2), libqscintilla2 ( 2.4.2+1~)
but there is only a libqscintilla2-5 (2.4.2-2) in unstable.

I guess this is related to
- Fixed lintian warning for libqscintilla2-dev dependencies
in 2.4.2-1 changelog?

The easiest solution would be to make the dep something like
libqscintilla2-5 (= 2.4.2)
again, but as this change seems to be intended, you maybe better go with a 
Provides
in the library package?

Regards
Evgeni

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

Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libqscintilla2-dev depends on:
ii  libqscintilla2-5  2.4.2-2The Qt4 port of the Scintilla sour
ii  libqt4-dev4:4.5.3-4  Qt 4 development files

libqscintilla2-dev recommends no packages.

libqscintilla2-dev suggests no packages.

-- no debconf information


---End Message---
---BeginMessage---
Source: qscintilla2
Source-Version: 2.4.2-3

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

libqscintilla2-5_2.4.2-3_amd64.deb
  to main/q/qscintilla2/libqscintilla2-5_2.4.2-3_amd64.deb
libqscintilla2-designer_2.4.2-3_amd64.deb
  to main/q/qscintilla2/libqscintilla2-designer_2.4.2-3_amd64.deb
libqscintilla2-dev_2.4.2-3_all.deb
  to main/q/qscintilla2/libqscintilla2-dev_2.4.2-3_all.deb
libqscintilla2-doc_2.4.2-3_all.deb
  to main/q/qscintilla2/libqscintilla2-doc_2.4.2-3_all.deb
python-qscintilla2_2.4.2-3_amd64.deb
  to main/q/qscintilla2/python-qscintilla2_2.4.2-3_amd64.deb
qscintilla2_2.4.2-3.debian.tar.gz
  to main/q/qscintilla2/qscintilla2_2.4.2-3.debian.tar.gz
qscintilla2_2.4.2-3.dsc
  to main/q/qscintilla2/qscintilla2_2.4.2-3.dsc



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 568...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Torsten Marek shlo...@debian.org (supplier of updated qscintilla2 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 03 Feb 2010 09:01:40 +0100
Source: qscintilla2
Binary: libqscintilla2-5 libqscintilla2-designer libqscintilla2-dev 
libqscintilla2-doc python-qscintilla2
Architecture: source all amd64
Version: 2.4.2-3
Distribution: unstable
Urgency: low
Maintainer: Torsten Marek shlo...@debian.org
Changed-By: Torsten Marek shlo...@debian.org
Description: 
 libqscintilla2-5 - The Qt4 port of the Scintilla source code editing widget
 libqscintilla2-designer - Qt4 Designer plugin for QScintilla 2
 libqscintilla2-dev - The Scintilla source code editing widget for Qt4, 
development fil
 libqscintilla2-doc - API documentation for QScintilla 2
 python-qscintilla2 - Python bindings for QScintilla 2
Closes: 568217
Changes: 
 qscintilla2 (2.4.2-3) unstable; urgency=low
 .
   * Fix dependencies of libqscintilla2-dev (Closes: #568217)
Checksums-Sha1: 
 8ea6f21433583f948587551f65ff7f266af7303c 1345 qscintilla2_2.4.2-3.dsc
 dc3297ea97dc0df1807309f1cdec09c218c6f433 12702 
qscintilla2_2.4.2-3.debian.tar.gz
 edbae73ce46045de89697b2ccf6eed80f56f254e 86434 
libqscintilla2-dev_2.4.2-3_all.deb
 914ed9efdd33f785437e48274cc0270a428a3ca1 912850 
libqscintilla2-doc_2.4.2-3_all.deb
 5a0371add02b180569a7d50cd4fd9a2a88dfa720 736648 
libqscintilla2-5_2.4.2-3_amd64.deb
 322bf3381279365b1d4a7affc78a2e499efb38a6 36708 
libqscintilla2-designer_2.4.2-3_amd64.deb
 

Processed: patch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 560104 patch
Bug #560104 [sofa-framework] FTBFS [hppa] - undefined reference to 
`sofa::helper::Factory...
Added tag(s) 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#560950: marked as done (CVE-2009-3560 and CVE-2009-3720 denial-of-services)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 09:52:21 +
with message-id e1ncbuh-0006vg...@ries.debian.org
and subject line Bug#560950: fixed in xotcl 1.6.5-1.1
has caused the Debian Bug report #560950,
regarding CVE-2009-3560 and CVE-2009-3720 denial-of-services
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
560950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
package: xotcl
severity: serious
tags: security

Hi,

The following CVE (Common Vulnerabilities  Exposures) ids were
published for expat.  I have determined that this package embeds a
vulnerable copy of xmlparse.c and xmltok_impl.c.  However, since this is
a mass bug filing (due to so many packages embedding expat), I have
not had time to determine whether the vulnerable code is actually
present in any of the binary packages derived from this source package.
Please determine whether this is the case. If the binary packages are
not affected, please feel free to close the bug with a message
containing the details of what you did to check.

CVE-2009-3560[0]:
| The big2_toUtf8 function in lib/xmltok.c in libexpat in Expat 2.0.1,
| as used in the XML-Twig module for Perl, allows context-dependent
| attackers to cause a denial of service (application crash) via an XML
| document with malformed UTF-8 sequences that trigger a buffer
| over-read, related to the doProlog function in lib/xmlparse.c, a
| different vulnerability than CVE-2009-2625 and CVE-2009-3720.

CVE-2009-3720[1]:
| The updatePosition function in lib/xmltok_impl.c in libexpat in Expat
| 2.0.1, as used in Python, PyXML, w3c-libwww, and other software,
| allows context-dependent attackers to cause a denial of service
| (application crash) via an XML document with crafted UTF-8 sequences
| that trigger a buffer over-read, a different vulnerability than
| CVE-2009-2625.

These issues also affect old versions of expat, so this package in etch
and lenny is very likely affected.  This is a low-severity security
issue, so DSAs will not be issued to correct these problems.  However,
you can optionally submit a proposed-update to the release team for
inclusion in the next stable point releases.  If you plan to do this, 
please open new bugs and include the security tag so we are aware that
you are working on that.

For further information see [0],[1],[2],[3].  In particular, [2] and [3]
are links to the patches for CVE-2009-3560 and CVE-2009-3720
respectively. Note that the ideal solution would be to make use of the
system expat so only one package will need to be updated for future
security issues. Preferably in your update to unstable, alter your
package to make use of the system expat.

If you fix the vulnerability please also make sure to include the
CVE id in your changelog entry.

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3560
http://security-tracker.debian.org/tracker/CVE-2009-3560
[1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3720
http://security-tracker.debian.org/tracker/CVE-2009-3720
[2]
http://expat.cvs.sourceforge.net/viewvc/expat/expat/lib/xmlparse.c?r1=1.164r2=1.165
[3]
http://expat.cvs.sourceforge.net/viewvc/expat/expat/lib/xmltok_impl.c?r1=1.13r2=1.15view=patch


---End Message---
---BeginMessage---
Source: xotcl
Source-Version: 1.6.5-1.1

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

aolserver4-xotcl_1.6.5-1.1_all.deb
  to main/x/xotcl/aolserver4-xotcl_1.6.5-1.1_all.deb
xotcl-dev_1.6.5-1.1_amd64.deb
  to main/x/xotcl/xotcl-dev_1.6.5-1.1_amd64.deb
xotcl-doc_1.6.5-1.1_all.deb
  to main/x/xotcl/xotcl-doc_1.6.5-1.1_all.deb
xotcl-shells_1.6.5-1.1_amd64.deb
  to main/x/xotcl/xotcl-shells_1.6.5-1.1_amd64.deb
xotcl_1.6.5-1.1.diff.gz
  to main/x/xotcl/xotcl_1.6.5-1.1.diff.gz
xotcl_1.6.5-1.1.dsc
  to main/x/xotcl/xotcl_1.6.5-1.1.dsc
xotcl_1.6.5-1.1_amd64.deb
  to main/x/xotcl/xotcl_1.6.5-1.1_amd64.deb



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 560...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl toli...@debian.org (supplier of updated xotcl 
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 ftpmas...@debian.org)


-BEGIN 

Bug#560104: patch

[Ilya Barygin]

tags 560104 patch
thanks

I don't know what the real problem is here (incorrect code? compiler
bug?), but it can be worked around by compiling with -O1 instead of
-O2. Maybe it is possible to find one specific optimization that leads
to failure and turn it off. Patch from Ubuntu attached.Description: reduce optimization level to -O1 as a workaround for linking
 failure
Author: Ilya Barygin bary...@gmail.com
Bug-Debian: http://bugs.debian.org/560104
--- a/sofa-default.cfg
+++ b/sofa-default.cfg
@@ -110,6 +110,7 @@
   # Choose if you want to compile the debug or release version
 #CONFIG = debug
 CONFIG = release
+QMAKE_CXXFLAGS_RELEASE += -O1
 QMAKE_CXXFLAGS += -W
 QMAKE_CFLAGS += -W
 

Bug#567105: [/debian-unstable] Use python-support for managing python extensions

[Sean Finney]

tag 567105 pending
thanks

Date: Wed Feb 3 11:00:28 2010 +0100
Author: Sean Finney sean...@debian.org
Commit ID: 50a119fbf8fd8a5f5818d1b095abc2d3cf47cce5
Commit URL: 
http://git.debian.org/?p=pkg-xorg/bling/compizconfig-python.git;a=commitdiff;h=50a119fbf8fd8a5f5818d1b095abc2d3cf47cce5
Patch URL: 
http://git.debian.org/?p=pkg-xorg/bling/compizconfig-python.git;a=commitdiff_plain;h=50a119fbf8fd8a5f5818d1b095abc2d3cf47cce5

Use python-support for managing python extensions

Also add Build-Depends on python-support.

Closes: #567105
  



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: [/debian-unstable] Use python-support for managing python extensions

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tag 567105 pending
Bug #567105 [python-compizconfig] python-compizconfig: python2.6-minimal says 
files must not be shipped in /usr/lib/python2.6/site-packages
Bug #567507 [python-compizconfig] Install python2.6-minimal failure
Added tag(s) pending.
Added tag(s) 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#567945: lsh-server: Does not configure on mipsel

[Niels =?UTF-8?Q?M=C3=B6ller]

Magnus Holmgren holmg...@debian.org writes:

 Starting secure shell v2 server: lshdClosed spurious fd 3

I also think this message is suspicious. lshd tries to close all fd:s
between 3 and getdtablesize() (to avoid that any spurious open fd leaks
to user processes it spawns). Expected result is that all these close
calls should fail with EBADF. So what is fd 3, and why is it open?

Regards,
/Niels

-- 
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet email is subject to wholesale government surveillance.



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#568223: hibernate to disk crashes the system

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 severity 568223 important
Bug #568223 [linux-2.6] hibernate to disk crashes the system
Severity set to 'important' from 'critical'

 stop
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568223: hibernate to disk crashes the system

[maximilian attems]

severity 568223 important
stop

On Wed, Feb 03, 2010 at 10:22:03AM +0100, W. Martin Borgert wrote:
 Package: linux-2.6
 Version: 2.6.32-5
 Severity: critical

wrong at several level,
first critical is only ok if it would crash a huge nr of boxes.

also 2.6.32-5 is outdated test against 2.6.32-6 it has ton of fixes.
 



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#556826: marked as done (fai: FTBFS: a2x: ERROR: xmllint --nonet --noout --valid /build/user-fai_3.3.1-amd64-NpfNYt/fai-3.3.1/doc/fai-guide.xml returned non-zero exit status 127)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 11:17:12 +
with message-id e1ncdeo-0005or...@ries.debian.org
and subject line Bug#556826: fixed in fai 3.3.3
has caused the Debian Bug report #556826,
regarding fai: FTBFS: a2x: ERROR: xmllint --nonet --noout --valid 
/build/user-fai_3.3.1-amd64-NpfNYt/fai-3.3.1/doc/fai-guide.xml returned 
non-zero exit status 127
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
556826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: fai
Version: 3.3.1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091117 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
 make[1]: Entering directory `/build/user-fai_3.3.1-amd64-NpfNYt/fai-3.3.1'
 /usr/bin/make -C doc all
 make[2]: Entering directory `/build/user-fai_3.3.1-amd64-NpfNYt/fai-3.3.1/doc'
 a2x --icons -a toc -a toclevels=3 -f text fai-guide.txt
 a2x: ERROR: xmllint --nonet --noout --valid 
 /build/user-fai_3.3.1-amd64-NpfNYt/fai-3.3.1/doc/fai-guide.xml returned 
 non-zero exit status 127
 make[2]: *** [text] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2009/11/17/fai_3.3.1_lsid64.buildlog

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

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

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


---End Message---
---BeginMessage---
Source: fai
Source-Version: 3.3.3

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

fai-client_3.3.3_all.deb
  to main/f/fai/fai-client_3.3.3_all.deb
fai-doc_3.3.3_all.deb
  to main/f/fai/fai-doc_3.3.3_all.deb
fai-nfsroot_3.3.3_all.deb
  to main/f/fai/fai-nfsroot_3.3.3_all.deb
fai-quickstart_3.3.3_all.deb
  to main/f/fai/fai-quickstart_3.3.3_all.deb
fai-server_3.3.3_all.deb
  to main/f/fai/fai-server_3.3.3_all.deb
fai_3.3.3.dsc
  to main/f/fai/fai_3.3.3.dsc
fai_3.3.3.tar.gz
  to main/f/fai/fai_3.3.3.tar.gz



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 556...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Lange la...@debian.org (supplier of updated fai 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 03 Feb 2010 11:05:31 +0100
Source: fai
Binary: fai-client fai-doc fai-server fai-quickstart fai-nfsroot
Architecture: source all
Version: 3.3.3
Distribution: unstable
Urgency: low
Maintainer: Thomas Lange la...@debian.org
Changed-By: Thomas Lange la...@debian.org
Description: 
 fai-client - Fully Automatic Installation client package
 fai-doc- Documentation for FAI
 fai-nfsroot - Fully Automatic Installation nfsroot package
 fai-quickstart - Fully Automatic Installation quickstart package
 fai-server - Fully Automatic Installation server package
Closes: 514160 556082 556168 556826 557082 558139 561489 568203
Changes: 
 fai (3.3.3) unstable; urgency=low
 .
   [ Thomas Lange ]
   * lib/mkramdisk: new script that mounts a ramdisk onto a directory and
 copies its contents to the ramdisk, can also umount the ramdisk and
 put the modified contents back to the hard disks, this script is a
 modified version of mkrw from FAI 3.1.8., use /dev/shm for temp file
   * upstart.conf: fix timing issue (thanks to Waldemar Brodkorb for the
 patch)
   * lib/updatebase, fai-debconf: exit if mktemp fails, for e.g. when
 TMPDIR is set to nonexisting directory (Thanks to Michael Prokop for
 the hint)
   * subroutines: make installation faster by putting /var/lib/dpkg into a
 ramdisk
   * control: add libxml2-utils to Build-dep-indep (closes: #556826),
 add dependency for build on lenny (closes: #556082)
   * install_packages: aptitude-r now uses MAXPACKAGES, thanks to Stefan
 Goetz 

Processed: tagging 552235

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 # in coordination with security team this is considered a non-issue for stable
 tags 552235 + squeeze sid
Bug #552235 {Done: jbo...@debian.org (Jeremy T. Bouse)} [acidbase] acidbase: 
multiple security flaws, needs maintenance or removal?
Added tag(s) sid and squeeze.

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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#567507: marked as done (Install python2.6-minimal failure)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 12:02:07 +
with message-id e1ncdvr-0001e3...@ries.debian.org
and subject line Bug#567105: fixed in compizconfig-python 0.8.4-1
has caused the Debian Bug report #567105,
regarding Install python2.6-minimal failure
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
567105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python2.6-minimal
Version: 2.6.4-4
Severity: grave
Justification: renders package unusable

When I upgrade my Debian testing, the python2.6-minimal will be upgraded to 
2.6.4-4. But it could not be installed. The error message as below.

Unpacking python2.6-minimal (from .../python2.6-minimal_2.6.4-4_amd64.deb) ...
new installation of python2.6-minimal; /usr/lib/python2.6/site-packages is a 
directory
which is expected a symlink to /usr/local/lib/python2.6/dist-packages.
please find the package shipping files in /usr/lib/python2.6/site-packages and
file a bug report to ship these in /usr/lib/python2.6/dist-packages instead
aborting installation of python2.6-minimal
dpkg: error processing 
/var/cache/apt/archives/python2.6-minimal_2.6.4-4_amd64.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/python2.6-minimal_2.6.4-4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

Kernel: Linux 2.6.32-athena.12 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages python2.6-minimal depends on:
ii  libc6   2.10.2-2 GNU C Library: Shared libraries
ii  libssl0.9.8 0.9.8k-8 SSL shared libraries
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages python2.6-minimal recommends:
pn  python2.6 none (no description available)

Versions of packages python2.6-minimal suggests:
pn  binfmt-supportnone (no description available)


---End Message---
---BeginMessage---
Source: compizconfig-python
Source-Version: 0.8.4-1

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

compizconfig-python_0.8.4-1.diff.gz
  to main/c/compizconfig-python/compizconfig-python_0.8.4-1.diff.gz
compizconfig-python_0.8.4-1.dsc
  to main/c/compizconfig-python/compizconfig-python_0.8.4-1.dsc
compizconfig-python_0.8.4.orig.tar.gz
  to main/c/compizconfig-python/compizconfig-python_0.8.4.orig.tar.gz
python-compizconfig_0.8.4-1_amd64.deb
  to main/c/compizconfig-python/python-compizconfig_0.8.4-1_amd64.deb



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 567...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sean Finney sean...@debian.org (supplier of updated compizconfig-python 
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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 03 Feb 2010 11:14:16 +0100
Source: compizconfig-python
Binary: python-compizconfig
Architecture: source amd64
Version: 0.8.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force debia...@lists.debian.org
Changed-By: Sean Finney sean...@debian.org
Description: 
 python-compizconfig - Compizconfig bindings for python
Closes: 567105
Changes: 
 compizconfig-python (0.8.4-1) unstable; urgency=medium
 .
   * New upstream release.
 .
   [ Sean Finney ]
   * Use python-support for managing python extensions (Closes: #567105)
 - Thanks: Kumar Appaiah
   * RC bugfix, bumped severity.
Checksums-Sha1: 
 bcfe0a8fdf10a3d6db4988ec4d63318c1cbc9bd4 1467 compizconfig-python_0.8.4-1.dsc
 9c1c69e26f4a6c0766ffb4ca90addf607a421d06 17509 
compizconfig-python_0.8.4.orig.tar.gz
 23416d32abe4e7497465847ec11448d8e8951462 2972 
compizconfig-python_0.8.4-1.diff.gz
 51d6d20bb62be45eee3a074853e65217c083fa39 93286 
python-compizconfig_0.8.4-1_amd64.deb
Checksums-Sha256: 
 

Processed: reopening bug, 2nd try

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 unarchive 505609
Bug #505609 {Done: Bastian Blank wa...@debian.org} 
[linux-image-2.6.26-1-amd64] Unbootable after kernel upgrade: Lilo can't load 
kernel
Warning: Unknown package 'linux-image-2.6.26-1-amd64'
Unarchived Bug 505609
Warning: Unknown package 'linux-image-2.6.26-1-amd64'
 reopen 505609
Bug #505609 {Done: Bastian Blank wa...@debian.org} 
[linux-image-2.6.26-1-amd64] Unbootable after kernel upgrade: Lilo can't load 
kernel
Warning: Unknown package 'linux-image-2.6.26-1-amd64'
Warning: Unknown package 'linux-image-2.6.26-1-amd64'
 reassign 505609 lilo
Bug #505609 [linux-image-2.6.26-1-amd64] Unbootable after kernel upgrade: Lilo 
can't load kernel
Warning: Unknown package 'linux-image-2.6.26-1-amd64'
Bug reassigned from package 'linux-image-2.6.26-1-amd64' to 'lilo'.
Bug No longer marked as found in versions linux-2.6/2.6.26-10.
 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#567105: marked as done (python-compizconfig: python2.6-minimal says files must not be shipped in /usr/lib/python2.6/site-packages)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 12:02:07 +
with message-id e1ncdvr-0001e3...@ries.debian.org
and subject line Bug#567105: fixed in compizconfig-python 0.8.4-1
has caused the Debian Bug report #567105,
regarding python-compizconfig: python2.6-minimal says files must not be shipped 
in /usr/lib/python2.6/site-packages
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
567105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-compizconfig
Version: 0.8.2-2+b1
Severity: important

Hello,

When installing python2.6-minimal package, it claims to report bug
to package shipping files to /usr/lib/python2.6/dist-packages.

Was standard of file layout changed?

s...@tempest:~% LANG=en_US sudo apt-get install python2.6-minimal
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  python2.6-minimal
0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded.
5 not fully installed or removed.
Need to get 0B/1,358kB of archives.
After this operation, 4,788kB of additional disk space will be used.
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
(Reading database ... 464104 files and directories currently
installed.)
Unpacking python2.6-minimal (from .../python2.6-minimal_2.6.4-4_i386.deb) ...
new installation of python2.6-minimal; /usr/lib/python2.6/site-packages is a 
directory
which is expected a symlink to /usr/local/lib/python2.6/dist-packages.
please find the package shipping files in /usr/lib/python2.6/site-packages and
file a bug report to ship these in /usr/lib/python2.6/dist-packages instead
aborting installation of python2.6-minimal
dpkg: error processing 
/var/cache/apt/archives/python2.6-minimal_2.6.4-4_i386.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/python2.6-minimal_2.6.4-4_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
s...@tempest:~% LANG=C ls -l /usr/lib/python2.6/site-packages
total 108
-rw-r--r-- 1 root root 105728 Jan 26 16:21 compizconfig.so
s...@tempest:~% dpkg -S /usr/lib/python2.6/site-packages/compizconfig.so 
python-compizconfig: /usr/lib/python2.6/site-packages/compizconfig.so


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

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages python-compizconfig depends on:
ii  libc62.10.2-5Embedded GNU C Library: Shared lib
ii  libcompizconfig0 0.8.2-2+b1  Configuration settings library for
ii  libglib2.0-0 2.22.4-1The GLib library of C routines
ii  libice6  2:1.0.6-1   X11 Inter-Client Exchange library
ii  libsm6   2:1.1.1-1   X11 Session Management library
ii  libstartup-notification0 0.10-1  library for program launch feedbac
ii  libx11-6 2:1.3.3-1   X11 client-side library
ii  libxcomposite1   1:0.4.1-1   X11 Composite extension library
ii  libxcursor1  1:1.1.10-1  X cursor management library
ii  libxdamage1  1:1.1.2-1   X11 damaged region extension libra
ii  libxfixes3   1:4.0.4-1   X11 miscellaneous 'fixes' extensio
ii  libxinerama1 2:1.1-2 X11 Xinerama extension library
ii  libxml2  2.7.6.dfsg-2+b1 GNOME XML library
ii  libxrandr2   2:1.3.0-2   X11 RandR extension library
ii  libxslt1.1   1.1.26-1+b1 XSLT processing library - runtime 

python-compizconfig recommends no packages.

python-compizconfig suggests no packages.

-- no debconf information


---End Message---
---BeginMessage---
Source: compizconfig-python
Source-Version: 0.8.4-1

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

compizconfig-python_0.8.4-1.diff.gz
  to main/c/compizconfig-python/compizconfig-python_0.8.4-1.diff.gz
compizconfig-python_0.8.4-1.dsc
  to main/c/compizconfig-python/compizconfig-python_0.8.4-1.dsc
compizconfig-python_0.8.4.orig.tar.gz
  to 

Bug#505609: more on the lilo boot failure

[Tomas Pospisek]

After a standard security/stability upgrade of lenny I witnessed the same 
problem as Xavier, namely that lilo would stop with:


  liloLoading LinuxEBDA is big; kernel setup stack overlaps LILO second
  stage

(I am not sure whether there were any points after lilo. I think not,
 but if there were, then there were only very few - i.e. not a line or
 half a line or such)

What I did exactly was upgrading from linux-image-2.6.26-2-686 
2.6.26-19lenny1 to 2.6.26-21 inside aptitude and *at the same time* 
deinstalling the old linux-image-2.6.18-6-686 2.6.18.dfsg.1-26etch1.


Aptitude did what I told it to do and did not complain, and ended without 
error. The only thing indicating a problem were the following lines (from 
/var/log/apt.log - since I did not catch them during the down/upgrade, 
and translated from czech, since that's how the locale is set):


  Preparing to replace linux-image-2.6.26-2-686 2.6.26-19lenny1 (with
  .../linux-image-2.6.26-2-686_2.6.26-21_i386.deb) ...
  The directory /lib/modules/2.6.26-2-686 still exists. Continuing as
  directed.
  Done.
  Unpacking replacement linux-image-2.6.26-2-686 ...
  ...
  Configuring package linux-image-2.6.26-2-686 (2.6.26-21) ...
  Running depmod.
  Running mkinitramfs-kpkg.
  Not updating initrd symbolic links since we are being updated/reinstalled
  (2.6.26-19lenny1 was configured last, according to dpkg)
  Not updating image symbolic links since we are being updated/reinstalled
  (2.6.26-19lenny1 was configured last, according to dpkg)
  ...
  Removing package linux-image-2.6.18-6-686
  The link /vmlinuz.old is a damaged link
  Removing symbolic link vmlinuz.old
  Unless you used the optional flag in lilo,
   you may need to re-run your boot loader[lilo]
  The link /initrd.img.ol is a damaged link
  Removing symbolic link initrd.img.ol
  Unless you used the optional flag in lilo,
   you may need to re-run your boot loader[lilo]
  Removing configuration directory of package linux-image-2.6.18-6-686 ...
  ...

And that's it, no errors anywhere.

After upgrading I rebooted and ended up with the lilo error reported by 
Xavier and repeated above.


Strangely enough (!!!) I could *still* boot into the removed (!) 2.6.18-6 
kernel and allthough the bootprocess complained about a lot of missing 
kernel modules (or modules.dep ? I don't know, I can't find it anywhere 
in the logs), but somehow miraculously (!) it was able to install the 
networking stack... Then, from the shell I issued:


  # lilo
  Fatal: open /boot/vmlinuz-2.6.18-6-686

After that I reinstalled the old linux-image-2.6.18-6-686 
2.6.18.dfsg.1-26etch1 package and rebooted.


Now everything was fine and I could boot into the new 2.6.26 kernel 
without lilo complaining.


Running lilo from the command line would show me the bootable kernels:

  # lilo
  Added 2618-6-hda5
  Added 2626-hda5
  Added windows

  # ls -l /
  [...]
  initrd.img - boot/initrd.img-2.6.18-6-686
  initrd.img.old - boot/initrd.img-2.6.26-2-686
  [...]
  vmlinuz - boot/vmlinuz-2.6.18-6-686
  vmlinuz.old - boot/vmlinuz-2.6.26-2-686

It seems that even if lilo.conf is half broken - i.e. it's missing some of 
the kernels, the install process will nevertheless install the new kernel 
but somehow break halfway through the process and not properly install the 
new kernel.


*t




--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#567039: trac-git: Arbitrary command execution

[Jonny Lamb]

Hi.

On Tue, Jan 26, 21:49:42 +0100, Stefan Göbel wrote:
 The trac-git package in Debian Lenny - if enabled in Trac - allows a
 remote attacker to execute arbitrary commands on the system with the
 rights of the user running Trac. The attacker must have the rights to
 browse the repository in order to exploit this issue, other parts of
 Trac are most likely not affected.
 
 The attached patch fixes the problem, it is not thoroughly tested,
 though, but seems to work fine on my test system with a few Git
 repositories.

Sorry for the delay in responding, I've been away from my emails for a
few days, but I'm back now.

Anyway, thanks for this and the patch. I just wanted to note that I'd
not ignored this and I'll try and get something out today.

Cheerio,

-- 
Jonny Lamb, UK
jo...@debian.org



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#560186: The bug is still there...

[Micha vor dem Berge]

Hi,

 I'd just fixed this bug on SF - it was triggered when a (Debian) host 
 didn't have a stock Debian kernel installed. SVN HEAD contains a 
 apt-dater-host script which fixes this issue.

it works for me with the recent svn version of apt-dater-host and
apt-dater 0.8.1+svn450-1 from debian sid.
Thanks for your work!

 The packages in sid are missing some bugfixes and we are going to do a 
 bugfix release 0.8.2 very soon.

Looking forward for the realease...

Cheers,
Micha vor dem Berge




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568249: xulrunner-1.9.1: [FTBFS] Test suite fails on mips

[Mike Hommey]

Package: xulrunner-1.9.1
Version: 1.9.1.6-2
Severity: grave
Justification: renders package unusable

That the test suite fails (by crashing) basically means iceweasel and
other packages using xulrunner-1.9.1 are not likely to work properly on
these architectures.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#567633: marked as done (race condition in fusermount)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 13:52:40 +
with message-id e1ncfeq-0001ud...@ries.debian.org
and subject line Bug#567633: fixed in fuse 2.7.4-1.1+lenny1
has caused the Debian Bug report #567633,
regarding race condition in fusermount
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
567633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: fuse-utils
Severity: grave
Tags: security

fuse 2.8.2 fixes a race condition if two fusermount -u instances
are run in paralell, which allows local privilege escalation.

This issue was discovered by Dan Rosenberg.

Cheers,
Moritz


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

Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=C, lc_ctype=de_de.iso-8859...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages fuse-utils depends on:
ii  adduser   3.112  add and remove users and groups
ii  libc6 2.10.2-5   Embedded GNU C Library: Shared lib
pn  libfuse2  none (no description available)
ii  makedev   2.3.1-89   creates device files in /dev
ii  sed   4.2.1-6The GNU sed stream editor
ii  udev  150-2  /dev/ and hotplug management daemo

fuse-utils recommends no packages.

fuse-utils suggests no packages.


---End Message---
---BeginMessage---
Source: fuse
Source-Version: 2.7.4-1.1+lenny1

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

fuse-utils_2.7.4-1.1+lenny1_i386.deb
  to main/f/fuse/fuse-utils_2.7.4-1.1+lenny1_i386.deb
fuse_2.7.4-1.1+lenny1.diff.gz
  to main/f/fuse/fuse_2.7.4-1.1+lenny1.diff.gz
fuse_2.7.4-1.1+lenny1.dsc
  to main/f/fuse/fuse_2.7.4-1.1+lenny1.dsc
libfuse-dev_2.7.4-1.1+lenny1_i386.deb
  to main/f/fuse/libfuse-dev_2.7.4-1.1+lenny1_i386.deb
libfuse2_2.7.4-1.1+lenny1_i386.deb
  to main/f/fuse/libfuse2_2.7.4-1.1+lenny1_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 567...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Giuseppe Iuculano iucul...@debian.org (supplier of updated fuse 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 31 Jan 2010 23:12:19 +0100
Source: fuse
Binary: fuse-utils libfuse-dev libfuse2
Architecture: source i386
Version: 2.7.4-1.1+lenny1
Distribution: stable-security
Urgency: high
Maintainer: Bartosz Fenski fe...@debian.org
Changed-By: Giuseppe Iuculano iucul...@debian.org
Description: 
 fuse-utils - Filesystem in USErspace (utilities)
 libfuse-dev - Filesystem in USErspace (development files)
 libfuse2   - Filesystem in USErspace library
Closes: 567633
Changes: 
 fuse (2.7.4-1.1+lenny1) stable-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fixed CVE-2009-3297: race condition in fusermount (Closes: #567633)
Checksums-Sha1: 
 a894c7aa5d1e2add5729fb51b99f476fab34a63d 1171 fuse_2.7.4-1.1+lenny1.dsc
 7a86f5cf39f38e64ccbae093599d64a895b950ba 506658 fuse_2.7.4.orig.tar.gz
 75d3afb85eec0665b50dd2794d166598d06850c4 16066 fuse_2.7.4-1.1+lenny1.diff.gz
 ec95e23e06cc7d996d7ae5994064fcf505601a5d 17894 
fuse-utils_2.7.4-1.1+lenny1_i386.deb
 68079e2527c4b4fde7e4f9866ab883e69576 155244 
libfuse-dev_2.7.4-1.1+lenny1_i386.deb
 5c9a4729ddbb2540d255210648f6205e1f78d7c0 124622 
libfuse2_2.7.4-1.1+lenny1_i386.deb
Checksums-Sha256: 
 e9a52d51a75aba25788075ba6f4267cd9590e984d50d28d47d620f6b68b58e66 1171 
fuse_2.7.4-1.1+lenny1.dsc
 c8b070ece5d4e09bd06eea6c28818c718f803d93a4b85bacb9982deb8ded49e6 506658 
fuse_2.7.4.orig.tar.gz
 9b3bf867995f76438a157d33d2f12ce25daa1365b0d08d2f360223eb7d54c428 16066 
fuse_2.7.4-1.1+lenny1.diff.gz
 355ac7c0c258f1035cfe19d01b62a0f916af8341d8b6b8e5288f997e096d1f0f 17894 
fuse-utils_2.7.4-1.1+lenny1_i386.deb
 202cdafb6b40048bcaa85c8bf789696758497300aabffeaeaf6625fe37b000c1 155244 
libfuse-dev_2.7.4-1.1+lenny1_i386.deb
 e85fda37a49c7a05d9363d04d18a87d9bbc6d6f67372a8d9d05fe04ad75f0c31 124622 

Bug#567214: backuppc: Changing archive directory not working correctly

[Adam Goryachev]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

It looks like everything you did was correct, up to the last step
(hopefully you have worked this out by now, or it was a copy and paste
error to the bug report).

sudo cp -dpR /var/lib/backuppc/. /media/raid/backup
sudo rm -rf /var/lib/backuppc
sudo ln -s /media/raid/backup /var/lib/backup

That last one should have been:
sudo ln -s /media/raid/backup /var/lib/backuppc

Regards,
Adam
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAktpfcEACgkQGyoxogrTyiWytwCeLHzwtyXBvX5+RsiJn5h5xENZ
7mQAoKothpKd3MmFCzrrfRX9iCY/mljk
=pcRf
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568255: procps: /bin/kill leaked into procps binary package on GNU/kFreeBSD

[Petr Salinger]

Package: procps
Version: 1:3.2.8-5
Severity: serious
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

the current version contains /bin/kill, which should come on GNU/kFreeBSD 
from coreutils. It is regression w.r.t 1:3.2.8-2, it is due to changed 
debian/rules.


The file debian/procps.install.kfreebsd is not effective
as currently DEBROOT=$(CURDIR)/debian/procps.
It should be DEBROOT=$(CURDIR)/debian/tmp and debian/procps.install* files
should contain all files, not only binaries/libraries.

Petr




--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568256: unable to start program

[Piotr Lewandowski]

Package: awn-manager
Version: 0.3.2.1-4
Severity: serious

I'm unable to start awn-manager (in clean sid chroot).

#v+
$ [ -d ~/.gnome2/ ]  echo $? 
0
$ awn-manager 

(awn-manager:16432): libgnomevfs-WARNING **: Unable to create ~/.gnome2 
directory: No such file or directory
process 16432: D-Bus library appears to be incorrectly set up; failed to read 
machine uuid: Failed to open /var/lib/dbus/machine-id: No such file or 
directory
See the manual page for dbus-uuidgen to correct this issue.
gconfd-2(2349): Operation not permitted
/usr/share/avant-window-navigator/awn-manager/awnPreferences.py:268: 
DeprecationWarning: raising a string exception is deprecated
  raise \nKey: [%s]%s isn't set.\nRestarting AWN usually solves this issue\n 
% (group, key)
Traceback (most recent call last):
  File /usr/bin/awn-manager, line 220, in module
awnmanager = AwnManager()
  File /usr/bin/awn-manager, line 136, in __init__
self.prefManager = awnPreferences(self.wTree)
  File /usr/share/avant-window-navigator/awn-manager/awnPreferences.py, line 
100, in __init__
self.setup_chooser(defs.APP, defs.ACTIVE_PNG, 
self.wTree.get_widget(activefilechooser))
  File /usr/share/avant-window-navigator/awn-manager/awnPreferences.py, line 
254, in setup_chooser
self.load_chooser(group, key, chooser)
  File /usr/share/avant-window-navigator/awn-manager/awnPreferences.py, line 
268, in load_chooser
raise \nKey: [%s]%s isn't set.\nRestarting AWN usually solves this 
issue\n % (group, key)

Key: [app]active_png isn't set.
Restarting AWN usually solves this issue
#v-

Restarting AWN doesn't solve the issue.

-- 
Piotr Lewandowski



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#567197: not considered elegant by many

[Barak A. Pearlmutter]

sed s/many/any/

(thanks; will dput shortly)

--Barak.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#567925: marked as done (gdbserver: File conflict with gdb; need Replaces)

[Debian Bug Tracking System]

Your message dated Wed, 3 Feb 2010 09:29:39 -0500
with message-id 20100203142939.ga30...@caradoc.them.org
and subject line Re: Bug#567925: Conflict with old version
has caused the Debian Bug report #567925,
regarding gdbserver: File conflict with gdb; need Replaces
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
567925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: gdbserver
Version: 7.0.1-1
Severity: serious
Justification: Policy 7.6

Unpacking gdbserver (from .../gdbserver_7.0.1-1_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/gdbserver_7.0.1-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man1/gdbserver.1.gz', which is also in 
package gdb 0:7.0-1

- Josh Triplett

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

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gdbserver depends on:
ii  libc6 2.10.2-5   Embedded GNU C Library: Shared lib

gdbserver recommends no packages.

gdbserver suggests no packages.


---End Message---
---BeginMessage---
Version: 7.0.1-2

On Tue, Feb 02, 2010 at 09:57:30PM +0100, Artur R. Czechowski wrote:
 Package: gdbserver
 Version: 7.0.1-1
 Severity: normal
 
 Conflicts: gdb  7.0.1 will be sufficient to prevent reported behavior.

Already fixed in unstable.

-- 
Daniel Jacobowitz
CodeSourcery

---End Message---

Bug#561924: gdb: FTBFS on kfreebsd-amd64 with 8.x kernel headers

[Daniel Jacobowitz]

On Wed, Feb 03, 2010 at 09:20:23AM +0100, Petr Salinger wrote:
 They have been removed somehere during 8.0 development,
 it started with 80, the 8.0 release have 800107.
 I did'n know the exact version, so please change the check to
 
 #if (__FreeBSD_version  800075)  (__FreeBSD_kernel_version  800075)

So the issue is checking __FreeBSD_version and not
__FreeBSD_kernel_version?  Does normal FreeBSD define both?

 Please, do you have some hints how to teach gdb,
 that on GNU/kFreeBSD is thread handling the same as
 in linuxthreads (pre-NPTL) implementation (#550361).

Sorry, I don't know how to do that.  You'd need to bring in
linux-thread-db.c and bits of linux-nat.c somehow.  I doubt
it's really the same at the level GDB sees it.

-- 
Daniel Jacobowitz
CodeSourcery



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: [Pkg-net-snmp-devel] Bug#565635: Crashes when queried

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 severity 565635 important
Bug #565635 [snmpd] Crashes when queried
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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#567039: trac-git: Arbitrary command execution

[Florian Weimer]

* Stefan Göbel:

 Package: trac-git
 Version: 0.0.20080710-3
 Severity: grave
 Tags: patch security
 Justification: user security hole


 The trac-git package in Debian Lenny - if enabled in Trac - allows a
 remote attacker to execute arbitrary commands on the system with the
 rights of the user running Trac. The attacker must have the rights to
 browse the repository in order to exploit this issue, other parts of
 Trac are most likely not affected.

Thanks.  I have assigned CVE-2010-0394 to this issue.



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#565635: [Pkg-net-snmp-devel] Bug#565635: Crashes when queried

[Simon Richter]

severity 565635 important
thanks

Hi,

On Mon, Feb 01, 2010 at 06:22:34PM +0100, Jochen Friedrich wrote:

 since the last upgrade, about any GETNEXT request makes snmpd crash,
 first logging an assertion failure, then stumbling over what looks like
 a null pointer dereference (address 0x20c).
 
 ii  libsnmp15 5.4.2.1~dfsg-4 SNMP (Simple Network Management 
 Pr

 Does this still happen with libsnmp15 5.4.2.1~dfsg-5?

Yes.

I've narrowed it down a bit hence the severity adjustment.

First of all, my example is not quite correct. While 1.3.6.1.2.1.4.34.1
does give me the first row, first column of the ipAddressTable,
1.3.6.1.2.1.4.34.2 does not refer to the second column; rather, I should
be using .1.3.6.1.2.1.4.34.1.1 and .1.3.6.1.2.1.4.34.1.2; snmpd does not
crash then (these columns appear to be entirely virtual, and snmpd
returns the first element of the third row for both; the results for
the first two rows can be deduced from the OID returned for the third
row however, so this is not a problem).

The issue of the crash still remains, however: asking for both
1.3.6.1.2.1.4.34.1 and 1.3.6.1.2.1.4.34.2 in the same request leads to a
crash, while individually, they are handled fine (the first returning
the third column, first row of ipAddressTable, the second returning
what is apparently fourth column, first row of ipNetToPhysicalTable).

So it is the combination of the requests that is problematic.

   Simon



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#561924: gdb: FTBFS on kfreebsd-amd64 with 8.x kernel headers

[Petr Salinger]

#if (__FreeBSD_version  800075)  (__FreeBSD_kernel_version  800075)


So the issue is checking __FreeBSD_version and not
__FreeBSD_kernel_version?


Yes.


Does normal FreeBSD define both?


No.

The assumption is that either both are defined to the same value,
or only one is defined and the other one is undefined, which is evaluated as 
zero.

Therefore the right thing to do is

#if (__FreeBSD_version  800075)  (__FreeBSD_kernel_version  800075)


Please, do you have some hints how to teach gdb,
that on GNU/kFreeBSD is thread handling the same as
in linuxthreads (pre-NPTL) implementation (#550361).


Sorry, I don't know how to do that.  You'd need to bring in
linux-thread-db.c and bits of linux-nat.c somehow.  I doubt
it's really the same at the level GDB sees it.


It might be very close. The most needed is a way
to access __thread variables, namely errno.
TLS implementation is the same, only the way to set-up
fs/gs base is a different.

Petr



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#567197: marked as done (FTBFS: make[2]: *** No rule to make target `bbdb.pdf'. Stop.)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 15:33:30 +
with message-id e1ncheq-000342...@ries.debian.org
and subject line Bug#567197: fixed in bbdb 2.35.cvs20080316-3
has caused the Debian Bug report #567197,
regarding FTBFS: make[2]: *** No rule to make target `bbdb.pdf'.  Stop.
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
567197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: bbdb
Version: 2.35.cvs20080316-2
Severity: serious
Justification: FTBFS


While trying to build your package on sid/amd64:

dpkg-buildpackage: set CFLAGS to default value: -g -O2
dpkg-buildpackage: set CPPFLAGS to default value:
dpkg-buildpackage: set LDFLAGS to default value:
dpkg-buildpackage: set FFLAGS to default value: -g -O2
dpkg-buildpackage: set CXXFLAGS to default value: -g -O2
dpkg-buildpackage: source package bbdb
dpkg-buildpackage: source version 2.35.cvs20080316-2
dpkg-buildpackage: source changed by Barak A. Pearlmutter b...@debian.org
dpkg-buildpackage: host architecture amd64
 /usr/bin/fakeroot debian/rules clean
dh clean
   dh_testdir
   dh_auto_clean
   dh_clean
 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory 
`/build/rt-bbdb_2.35.cvs20080316-2-amd64-PtMocT/bbdb-2.35.cvs20080316'
tar -czf bits.tar.gz bits/
/usr/bin/make -C texinfo bbdb.info bbdb.pdf
make[2]: Entering directory 
`/build/rt-bbdb_2.35.cvs20080316-2-amd64-PtMocT/bbdb-2.35.cvs20080316/texinfo'
makeinfo  bbdb.texinfo -o bbdb.info
make[2]: *** No rule to make target `bbdb.pdf'.  Stop.
make[2]: Leaving directory 
`/build/rt-bbdb_2.35.cvs20080316-2-amd64-PtMocT/bbdb-2.35.cvs20080316/texinfo'
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory 
`/build/rt-bbdb_2.35.cvs20080316-2-amd64-PtMocT/bbdb-2.35.cvs20080316'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-openvz-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


---End Message---
---BeginMessage---
Source: bbdb
Source-Version: 2.35.cvs20080316-3

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

bbdb_2.35.cvs20080316-3.diff.gz
  to main/b/bbdb/bbdb_2.35.cvs20080316-3.diff.gz
bbdb_2.35.cvs20080316-3.dsc
  to main/b/bbdb/bbdb_2.35.cvs20080316-3.dsc
bbdb_2.35.cvs20080316-3_all.deb
  to main/b/bbdb/bbdb_2.35.cvs20080316-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 567...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Barak A. Pearlmutter b...@debian.org (supplier of updated bbdb 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 03 Feb 2010 13:43:30 +
Source: bbdb
Binary: bbdb
Architecture: source all
Version: 2.35.cvs20080316-3
Distribution: unstable
Urgency: low
Maintainer: Joerg Jaspert jo...@debian.org
Changed-By: Barak A. Pearlmutter b...@debian.org
Description: 
 bbdb   - The Insidious Big Brother Database (email rolodex) for Emacs
Closes: 567197
Changes: 
 bbdb (2.35.cvs20080316-3) unstable; urgency=low
 .
   * chmod +x configure patch, thanks to Kumar Appaiah (closes: #567197)
Checksums-Sha1: 
 b5c23caf5e6c13259660fc8d129d013d3cfe18ad 1238 bbdb_2.35.cvs20080316-3.dsc
 15d86d9b27ef50159a7c136d9e8cc66b32f0b0c4 83091 bbdb_2.35.cvs20080316-3.diff.gz
 8b2a90b3d64322736fdf28501d2e57f9b9ebe272 746400 bbdb_2.35.cvs20080316-3_all.deb
Checksums-Sha256: 
 f817e3db78266c722d79be4f9572c9bbaacd0e92f48d69bc2b5ae42742bd2b90 1238 
bbdb_2.35.cvs20080316-3.dsc
 40939ccb01f0a1687228945cf514d90fa546e0a5180cf473fed04bf92633030e 83091 
bbdb_2.35.cvs20080316-3.diff.gz
 6a66bcebe044f18a90bbb2bf60dccdfc061482f7db33d616cf0eaad0eacab002 746400 
bbdb_2.35.cvs20080316-3_all.deb
Files: 
 992a451d45e5430a73f691afdb7a5d1f 1238 mail optional bbdb_2.35.cvs20080316-3.dsc
 737747f30a568a7956aa91261aef1b68 83091 mail optional 

Processed: Re: tags

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 # tweaking tags back
 tags 505356 - lenny
Bug #505356 [apertium] FTBFS with GCC 4.4: missing #include
Removed tag(s) lenny.
 tags 505356 + sid squeeze
Bug #505356 [apertium] FTBFS with GCC 4.4: missing #include
Added tag(s) squeeze and sid.
 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#557054: marked as done (tulip-doc and libmesh-doc: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 15:43:55 +
with message-id e1nchov-0006hx...@ries.debian.org
and subject line Bug#558473: fixed in tulip 3.1.2-2.3
has caused the Debian Bug report #558473,
regarding tulip-doc and libmesh-doc: error when trying to install together
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
558473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libmesh-doc,tulip-doc
Version: libmesh-doc/0.6.4.dfsg-1
Version: tulip-doc/3.1.2-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2009-11-19
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  tulip-doc libmesh-doc
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package tulip-doc.
(Reading database ... 10432 files and directories currently installed.)
Unpacking tulip-doc (from .../tulip-doc_3.1.2-2_all.deb) ...
Selecting previously deselected package libmesh-doc.
Unpacking libmesh-doc (from .../libmesh-doc_0.6.4.dfsg-1_all.deb) ...
dpkg: error processing /var/cache/apt/archives/libmesh-doc_0.6.4.dfsg-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man3/Point.3.gz', which is also in package 
tulip-doc 0:3.1.2-2
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/libmesh-doc_0.6.4.dfsg-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
cow-shell unlink .ilist: No such file or directory


This is a serious bug as it makes installation fail, and violate
section 7.6.1 of the policy. Possible solutions are to have the two
packages conflict, to rename the common file in one of the two
packages, or to remove the file from one package and have this package
depend on the other package. File diversions or a Replace relation are
another possibility.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):


  usr/share/man/man3/Point.3.gz
  usr/share/man/man3/Sphere.3.gz
  usr/share/man/man3/Triangle.3.gz
  usr/share/man/man3/std.3.gz
  

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


---End Message---
---BeginMessage---
Source: tulip
Source-Version: 3.1.2-2.3

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

libtulip-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-3.1_3.1.2-2.3_amd64.deb
libtulip-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-dev_3.1.2-2.3_amd64.deb
libtulip-ogl-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-ogl-3.1_3.1.2-2.3_amd64.deb
libtulip-ogl-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-ogl-dev_3.1.2-2.3_amd64.deb
libtulip-pluginsmanager-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-pluginsmanager-3.1_3.1.2-2.3_amd64.deb
libtulip-pluginsmanager-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-pluginsmanager-dev_3.1.2-2.3_amd64.deb
libtulip-qt4-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-qt4-3.1_3.1.2-2.3_amd64.deb
libtulip-qt4-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-qt4-dev_3.1.2-2.3_amd64.deb
tlprender_3.1.2-2.3_amd64.deb
  to main/t/tulip/tlprender_3.1.2-2.3_amd64.deb
tulip-doc_3.1.2-2.3_all.deb
  to main/t/tulip/tulip-doc_3.1.2-2.3_all.deb
tulip_3.1.2-2.3.diff.gz
  to main/t/tulip/tulip_3.1.2-2.3.diff.gz
tulip_3.1.2-2.3.dsc
  to main/t/tulip/tulip_3.1.2-2.3.dsc
tulip_3.1.2-2.3_amd64.deb
  to main/t/tulip/tulip_3.1.2-2.3_amd64.deb



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 558...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl toli...@debian.org (supplier of updated tulip 
package)

(This message was generated 

Bug#567490: marked as done (subvertpy: nondeterministically FTBFS: FAIL: test_write (subvertpy.tests.test_repos.StreamTests))

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 15:42:23 +
with message-id e1nchn1-0005gn...@ries.debian.org
and subject line Bug#567490: fixed in subvertpy 0.7.2-2
has caused the Debian Bug report #567490,
regarding subvertpy: nondeterministically FTBFS: FAIL: test_write 
(subvertpy.tests.test_repos.StreamTests)
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
567490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Source: subvertpy
Version: 0.7.2-1
Severity: serious

It appears that subvertpy tests nondeterministically fail on (some?) 
64-bit architectures:


* on alpha:

FAIL: test_write (subvertpy.tests.test_repos.StreamTests)
--
Traceback (most recent call last):
  File 
/build/buildd-subvertpy_0.7.2-1-alpha-2cLMPE/subvertpy-0.7.2/subvertpy/tests/test_repos.py,
 line 87, in test_write
self.assertEquals(0, s.write())
AssertionError: 0 != 4294967296

https://buildd.debian.org/fetch.cgi?pkg=subvertpyarch=alphaver=0.7.2-1stamp=1262697643

* on ia64:

FAIL: test_write (subvertpy.tests.test_repos.StreamTests)
--
Traceback (most recent call last):
  File /build/buildd/subvertpy-0.7.2/subvertpy/tests/test_repos.py, line 87, 
in test_write
self.assertEquals(0, s.write())
AssertionError: 0 != 6917529027641081856

https://buildd.debian.org/fetch.cgi?pkg=subvertpyarch=ia64ver=0.7.2-1%2Bb1stamp=1264569166

--
Jakub Wilk


signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: subvertpy
Source-Version: 0.7.2-2

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

python-subvertpy_0.7.2-2_amd64.deb
  to main/s/subvertpy/python-subvertpy_0.7.2-2_amd64.deb
subvertpy_0.7.2-2.debian.tar.gz
  to main/s/subvertpy/subvertpy_0.7.2-2.debian.tar.gz
subvertpy_0.7.2-2.dsc
  to main/s/subvertpy/subvertpy_0.7.2-2.dsc



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 567...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jelmer Vernooij jel...@debian.org (supplier of updated subvertpy 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 03 Feb 2010 15:13:51 +0100
Source: subvertpy
Binary: python-subvertpy
Architecture: source amd64
Version: 0.7.2-2
Distribution: unstable
Urgency: low
Maintainer: Jelmer Vernooij jel...@debian.org
Changed-By: Jelmer Vernooij jel...@debian.org
Description: 
 python-subvertpy - Alternative Python bindings for Subversion
Closes: 567490
Changes: 
 subvertpy (0.7.2-2) unstable; urgency=low
 .
   * Cope with type size changes on different platforms. Closes: #567490
   * Bump standards version to 3.8.4.
   * Switch to dpkg-source 3.0 (quilt) format
Checksums-Sha1: 
 d118808bab60509e6b2b65602ac2e0d9d2b11bb8 1218 subvertpy_0.7.2-2.dsc
 e20f399be11cceb9fcaec4994f418d1b2635589e 2727 subvertpy_0.7.2-2.debian.tar.gz
 53ddce9d4bb0651d36d8e86888acd89cd2248350 232368 
python-subvertpy_0.7.2-2_amd64.deb
Checksums-Sha256: 
 1cb0566639a4680d859e7e4ca9130726ef1c6e19ca0b0c046b0c76cbfbdb7f55 1218 
subvertpy_0.7.2-2.dsc
 61f6ff231ad46c2f8b7e36c4b7c037041e93898508fc2c9f84bcf8c31889ef37 2727 
subvertpy_0.7.2-2.debian.tar.gz
 513175730fb92b0b230db53fdeb68c0279e42425ef941bf12603692e3fcc5c22 232368 
python-subvertpy_0.7.2-2_amd64.deb
Files: 
 a2c51eb47e03cbbc45c88381f1a3d319 1218 python optional subvertpy_0.7.2-2.dsc
 fa3f7bee63377f5610ae5041a8fa8271 2727 python optional 
subvertpy_0.7.2-2.debian.tar.gz
 8c3b7ea16fc311f4b6d26b9e9565d072 232368 python optional 
python-subvertpy_0.7.2-2_amd64.deb

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

iEYEARECAAYFAktphPkACgkQPa9Uoh7vUnZq6gCfaDRHicJLTMX9hxd2Z1tECBx6
iXQAnRJ+4OtXDioTYTuty1HIaBc+TIRs
=Y9zb
-END PGP SIGNATURE-


---End Message---

Bug#557054: marked as done (tulip-doc and libmesh-doc: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 15:43:55 +
with message-id e1nchov-0006hr...@ries.debian.org
and subject line Bug#557054: fixed in tulip 3.1.2-2.3
has caused the Debian Bug report #557054,
regarding tulip-doc and libmesh-doc: error when trying to install together
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
557054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libmesh-doc,tulip-doc
Version: libmesh-doc/0.6.4.dfsg-1
Version: tulip-doc/3.1.2-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2009-11-19
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  tulip-doc libmesh-doc
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package tulip-doc.
(Reading database ... 10432 files and directories currently installed.)
Unpacking tulip-doc (from .../tulip-doc_3.1.2-2_all.deb) ...
Selecting previously deselected package libmesh-doc.
Unpacking libmesh-doc (from .../libmesh-doc_0.6.4.dfsg-1_all.deb) ...
dpkg: error processing /var/cache/apt/archives/libmesh-doc_0.6.4.dfsg-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man3/Point.3.gz', which is also in package 
tulip-doc 0:3.1.2-2
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/libmesh-doc_0.6.4.dfsg-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
cow-shell unlink .ilist: No such file or directory


This is a serious bug as it makes installation fail, and violate
section 7.6.1 of the policy. Possible solutions are to have the two
packages conflict, to rename the common file in one of the two
packages, or to remove the file from one package and have this package
depend on the other package. File diversions or a Replace relation are
another possibility.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):


  usr/share/man/man3/Point.3.gz
  usr/share/man/man3/Sphere.3.gz
  usr/share/man/man3/Triangle.3.gz
  usr/share/man/man3/std.3.gz
  

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


---End Message---
---BeginMessage---
Source: tulip
Source-Version: 3.1.2-2.3

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

libtulip-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-3.1_3.1.2-2.3_amd64.deb
libtulip-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-dev_3.1.2-2.3_amd64.deb
libtulip-ogl-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-ogl-3.1_3.1.2-2.3_amd64.deb
libtulip-ogl-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-ogl-dev_3.1.2-2.3_amd64.deb
libtulip-pluginsmanager-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-pluginsmanager-3.1_3.1.2-2.3_amd64.deb
libtulip-pluginsmanager-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-pluginsmanager-dev_3.1.2-2.3_amd64.deb
libtulip-qt4-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-qt4-3.1_3.1.2-2.3_amd64.deb
libtulip-qt4-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-qt4-dev_3.1.2-2.3_amd64.deb
tlprender_3.1.2-2.3_amd64.deb
  to main/t/tulip/tlprender_3.1.2-2.3_amd64.deb
tulip-doc_3.1.2-2.3_all.deb
  to main/t/tulip/tulip-doc_3.1.2-2.3_all.deb
tulip_3.1.2-2.3.diff.gz
  to main/t/tulip/tulip_3.1.2-2.3.diff.gz
tulip_3.1.2-2.3.dsc
  to main/t/tulip/tulip_3.1.2-2.3.dsc
tulip_3.1.2-2.3_amd64.deb
  to main/t/tulip/tulip_3.1.2-2.3_amd64.deb



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 557...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl toli...@debian.org (supplier of updated tulip 
package)

(This message was generated 

Bug#558473: marked as done (tulip-doc and libmesh-doc: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 15:43:55 +
with message-id e1nchov-0006hr...@ries.debian.org
and subject line Bug#557054: fixed in tulip 3.1.2-2.3
has caused the Debian Bug report #557054,
regarding tulip-doc and libmesh-doc: error when trying to install together
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
557054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libmesh-doc,tulip-doc
Version: libmesh-doc/0.6.4.dfsg-1
Version: tulip-doc'3.1@all, tulip-doc/3.1.2-2.1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2009-11-29
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  tulip-doc libmesh-doc
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package tulip-doc.
(Reading database ... 10433 files and directories currently installed.)
Unpacking tulip-doc (from .../tulip-doc_3.1.2-2.1_all.deb) ...
Selecting previously deselected package libmesh-doc.
Unpacking libmesh-doc (from .../libmesh-doc_0.6.4.dfsg-1_all.deb) ...
dpkg: error processing /var/cache/apt/archives/libmesh-doc_0.6.4.dfsg-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man3/Point.3.gz', which is also in package 
tulip-doc 0:3.1.2-2.1
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/libmesh-doc_0.6.4.dfsg-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
cow-shell unlink .ilist: No such file or directory


This is a serious bug as it makes installation fail, and violate
section 7.6.1 of the policy. Possible solutions are to have the two
packages conflict, to rename the common file in one of the two
packages, or to remove the file from one package and have this package
depend on the other package. File diversions or a Replace relation are
another possibility.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):


  usr/share/man/man3/Point.3.gz
  usr/share/man/man3/Sphere.3.gz
  usr/share/man/man3/Triangle.3.gz
  usr/share/man/man3/std.3.gz
  

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


---End Message---
---BeginMessage---
Source: tulip
Source-Version: 3.1.2-2.3

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

libtulip-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-3.1_3.1.2-2.3_amd64.deb
libtulip-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-dev_3.1.2-2.3_amd64.deb
libtulip-ogl-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-ogl-3.1_3.1.2-2.3_amd64.deb
libtulip-ogl-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-ogl-dev_3.1.2-2.3_amd64.deb
libtulip-pluginsmanager-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-pluginsmanager-3.1_3.1.2-2.3_amd64.deb
libtulip-pluginsmanager-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-pluginsmanager-dev_3.1.2-2.3_amd64.deb
libtulip-qt4-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-qt4-3.1_3.1.2-2.3_amd64.deb
libtulip-qt4-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-qt4-dev_3.1.2-2.3_amd64.deb
tlprender_3.1.2-2.3_amd64.deb
  to main/t/tulip/tlprender_3.1.2-2.3_amd64.deb
tulip-doc_3.1.2-2.3_all.deb
  to main/t/tulip/tulip-doc_3.1.2-2.3_all.deb
tulip_3.1.2-2.3.diff.gz
  to main/t/tulip/tulip_3.1.2-2.3.diff.gz
tulip_3.1.2-2.3.dsc
  to main/t/tulip/tulip_3.1.2-2.3.dsc
tulip_3.1.2-2.3_amd64.deb
  to main/t/tulip/tulip_3.1.2-2.3_amd64.deb



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 557...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl toli...@debian.org (supplier of updated tulip 
package)

(This 

Bug#558473: marked as done (tulip-doc and libmesh-doc: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 15:43:55 +
with message-id e1nchov-0006hx...@ries.debian.org
and subject line Bug#558473: fixed in tulip 3.1.2-2.3
has caused the Debian Bug report #558473,
regarding tulip-doc and libmesh-doc: error when trying to install together
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
558473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libmesh-doc,tulip-doc
Version: libmesh-doc/0.6.4.dfsg-1
Version: tulip-doc'3.1@all, tulip-doc/3.1.2-2.1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2009-11-29
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  tulip-doc libmesh-doc
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package tulip-doc.
(Reading database ... 10433 files and directories currently installed.)
Unpacking tulip-doc (from .../tulip-doc_3.1.2-2.1_all.deb) ...
Selecting previously deselected package libmesh-doc.
Unpacking libmesh-doc (from .../libmesh-doc_0.6.4.dfsg-1_all.deb) ...
dpkg: error processing /var/cache/apt/archives/libmesh-doc_0.6.4.dfsg-1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/man/man3/Point.3.gz', which is also in package 
tulip-doc 0:3.1.2-2.1
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/libmesh-doc_0.6.4.dfsg-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
cow-shell unlink .ilist: No such file or directory


This is a serious bug as it makes installation fail, and violate
section 7.6.1 of the policy. Possible solutions are to have the two
packages conflict, to rename the common file in one of the two
packages, or to remove the file from one package and have this package
depend on the other package. File diversions or a Replace relation are
another possibility.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):


  usr/share/man/man3/Point.3.gz
  usr/share/man/man3/Sphere.3.gz
  usr/share/man/man3/Triangle.3.gz
  usr/share/man/man3/std.3.gz
  

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


---End Message---
---BeginMessage---
Source: tulip
Source-Version: 3.1.2-2.3

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

libtulip-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-3.1_3.1.2-2.3_amd64.deb
libtulip-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-dev_3.1.2-2.3_amd64.deb
libtulip-ogl-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-ogl-3.1_3.1.2-2.3_amd64.deb
libtulip-ogl-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-ogl-dev_3.1.2-2.3_amd64.deb
libtulip-pluginsmanager-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-pluginsmanager-3.1_3.1.2-2.3_amd64.deb
libtulip-pluginsmanager-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-pluginsmanager-dev_3.1.2-2.3_amd64.deb
libtulip-qt4-3.1_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-qt4-3.1_3.1.2-2.3_amd64.deb
libtulip-qt4-dev_3.1.2-2.3_amd64.deb
  to main/t/tulip/libtulip-qt4-dev_3.1.2-2.3_amd64.deb
tlprender_3.1.2-2.3_amd64.deb
  to main/t/tulip/tlprender_3.1.2-2.3_amd64.deb
tulip-doc_3.1.2-2.3_all.deb
  to main/t/tulip/tulip-doc_3.1.2-2.3_all.deb
tulip_3.1.2-2.3.diff.gz
  to main/t/tulip/tulip_3.1.2-2.3.diff.gz
tulip_3.1.2-2.3.dsc
  to main/t/tulip/tulip_3.1.2-2.3.dsc
tulip_3.1.2-2.3_amd64.deb
  to main/t/tulip/tulip_3.1.2-2.3_amd64.deb



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 558...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Reichle-Schmehl toli...@debian.org (supplier of updated tulip 
package)

(This 

Processed: non-stable RCs

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 # bug doesn't really affect stable or oldstable
 tags 463296 + squeeze sid
Bug #463296 [ssed] ssed: non-standard gcc/g++ used for build (gcc-4.1)
Added tag(s) sid and squeeze.
 tags 533783 + squeeze sid
Bug #533783 {Done: Barry deFreese bdefre...@debian.org} [libcomplearn] 
libcomplearn: non-standard gcc/g++ used for build (gcc-4.2)
Added tag(s) sid and squeeze.
 tags 533788 + squeeze sid
Bug #533788 {Done: Daniel Baumann dan...@debian.org} [squashfs] squashfs: 
non-standard gcc/g++ used for build (gcc-4.2)
Added tag(s) sid and squeeze.
 tags 533793 + squeeze sid
Bug #533793 {Done: Enrico Zini enr...@debian.org} [libept] libept: 
non-standard gcc/g++ used for build (gcc-4.2)
Added tag(s) sid and squeeze.
 tags 533794 + squeeze sid
Bug #533794 {Done: Michael Banck mba...@debian.org} [pymol] pymol: 
non-standard gcc/g++ used for build (gcc-4.2)
Added tag(s) sid and squeeze.
 tags 533803 + squeeze sid
Bug #533803 {Done: Thomas Weber thomas.weber.m...@gmail.com} [octave3.0] 
octave3.0: non-standard gcc/g++ used for build (gcc-4.1)
Added tag(s) sid and squeeze.
 tags 533806 + squeeze sid
Bug #533806 [plplot] plplot: non-standard gcc/g++ used for build (gcc-4.1)
Added tag(s) sid and squeeze.
 tags 533809 + squeeze sid
Bug #533809 {Done: Floris Bruynooghe floris.bruynoo...@gmail.com} [omniorb4] 
omniorb4: non-standard gcc/g++ used for build (gcc-4.1)
Added tag(s) sid and squeeze.
 tags 566259 + squeeze sid
Bug #566259 [qt4-x11] g++-4.4: FTBFS because of mangled std::va_list
Added tag(s) sid and squeeze.

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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#549759: marked as done (libxmpp-php: FTBFS: Fatal error: Cannot redeclare class PHPUnit_Framework_TestCase in /usr/share/php/PHPUnit/Framework/TestCase.php on line 117)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 15:38:13 +
with message-id e1nchiz-0004c0...@ries.debian.org
and subject line Bug#549759: fixed in libxmpp-php 0~svn53-1.1
has caused the Debian Bug report #549759,
regarding libxmpp-php: FTBFS: Fatal error: Cannot redeclare class 
PHPUnit_Framework_TestCase in /usr/share/php/PHPUnit/Framework/TestCase.php on 
line 117
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
549759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libxmpp-php
Version: 0~svn53-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091005 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
  /usr/bin/fakeroot debian/rules binary
 test -d debian/patched || install -d debian/patched
 dpatch  apply-all  
 applying patch 01-line-endings to ./ ... ok.
 applying patch 02-fix-tests to ./ ... ok.
 applying patch 03-remove-unwanted-test to ./ ... ok.
 dpatch  cat-all  patch-stampT
 mv -f patch-stampT patch-stamp
 php tests/AllTests.php
 
 Fatal error: Cannot redeclare class PHPUnit_Framework_TestCase in 
 /usr/share/php/PHPUnit/Framework/TestCase.php on line 117
 make: *** [install] Error 255

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/10/05/libxmpp-php_0~svn53-1_lsid64.buildlog

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

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

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


---End Message---
---BeginMessage---
Source: libxmpp-php
Source-Version: 0~svn53-1.1

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

libxmpp-php_0~svn53-1.1.diff.gz
  to main/libx/libxmpp-php/libxmpp-php_0~svn53-1.1.diff.gz
libxmpp-php_0~svn53-1.1.dsc
  to main/libx/libxmpp-php/libxmpp-php_0~svn53-1.1.dsc
libxmpp-php_0~svn53-1.1_all.deb
  to main/libx/libxmpp-php/libxmpp-php_0~svn53-1.1_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 549...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marcelo Jorge Vieira (metal) me...@debian.org (supplier of updated 
libxmpp-php 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 01 Feb 2010 11:33:20 -0200
Source: libxmpp-php
Binary: libxmpp-php
Architecture: source all
Version: 0~svn53-1.1
Distribution: unstable
Urgency: high
Maintainer: Daniel Watkins dan...@daniel-watkins.co.uk
Changed-By: Marcelo Jorge Vieira (metal) me...@debian.org
Description: 
 libxmpp-php - PHP library allowing communication with XMPP servers
Closes: 549759
Changes: 
 libxmpp-php (0~svn53-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Fixed FTBFS (Closes: #549759)
 - Wrong way to run tests
Checksums-Sha1: 
 8de69908a3ca020e292aa8f777ac56319dbe7bb1 1145 libxmpp-php_0~svn53-1.1.dsc
 7e30cf15125acb598c7396d9b33128b8be95921e 16769 libxmpp-php_0~svn53.orig.tar.gz
 2c6821719c38c43a8d1693a7667cdfb9a50f4ef6 2613 libxmpp-php_0~svn53-1.1.diff.gz
 58291f5e6036417616ccc5d85b5b84ed3423a868 10954 libxmpp-php_0~svn53-1.1_all.deb
Checksums-Sha256: 
 b819020f82d1f396f579035662916cdc21a975f511f3ba596f3107096e43192e 1145 
libxmpp-php_0~svn53-1.1.dsc
 a59f4750d58b89db263302af4ba14d2daee8578096d1540745a959ba7f9317aa 16769 
libxmpp-php_0~svn53.orig.tar.gz
 835376ebb58f6d1433603514149f428d0fb240d34a12b23f5cea926124dcd1c8 2613 
libxmpp-php_0~svn53-1.1.diff.gz
 0427e00dbf8bd62f6af303d92dce2d9d092870b216780e460334c40e165a0c84 10954 
libxmpp-php_0~svn53-1.1_all.deb
Files: 
 8c20d14b8f002bb1bff5e1ad446819de 1145 web optional libxmpp-php_0~svn53-1.1.dsc
 4ea7904cf3577bf97a4014ac9c05a005 16769 web optional 
libxmpp-php_0~svn53.orig.tar.gz
 fb237aef8ba5dcc38bda477060359327 2613 web optional 

Processed: tagging 534721

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 534721 + patch
Bug #534721 [libhpricot-ruby1.8] libhpricot-ruby1.8: Hpricot's XML parser fails 
to parse simple, valid XML
Added tag(s) 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568272: mplayer: Overwrites configuration file it generated itself

[Josselin Mouette]

Package: mplayer
Version: 1.0~rc3+svn20090405-1+b1
Severity: serious

After an upgrade from lenny, mplayer asked for a conffile replacement,
in /etc/mplayer.conf. However I never touched this file, it was
generated by mplayer itself using the debconf configuration.

This package probably needs to use ucf to detect whether this file was
changed from the debconf-generated one.

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

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mplayer depends on:
ii  debconf [debconf-2.0 1.5.28  Debian configuration management sy
ii  libasound2   1.0.21a-1   shared library for ALSA applicatio
ii  libatk1.0-0  1.28.0-1The ATK accessibility toolkit
ii  libaudio21.9.2-3 Network Audio System - shared libr
ii  libavcodec52 4:0.5+svn20090706-5 ffmpeg codec library
ii  libavformat524:0.5+svn20090706-5 ffmpeg file format library
ii  libavutil49  4:0.5+svn20090706-5 ffmpeg utility library
ii  libc62.10.2-2GNU C Library: Shared libraries
ii  libcaca0 0.99.beta16-3   colour ASCII art library
ii  libcairo21.8.8-2 The Cairo 2D vector graphics libra
ii  libcdparanoia0   3.10.2+debian-9 audio extraction tool for sampling
ii  libdirectfb-1.2-01.2.8-5 direct frame buffer graphics - sha
ii  libesd0  0.2.41-6Enlightened Sound Daemon - Shared 
ii  libfontconfig1   2.8.0-2 generic font configuration library
ii  libfreetype6 2.3.11-1FreeType 2 font engine, shared lib
ii  libfribidi0  0.10.9-1+b1 Free Implementation of the Unicode
ii  libgcc1  1:4.4.2-9   GCC support library
ii  libgif4  4.1.6-9 library for GIF images (library)
ii  libgl1-mesa-glx [lib 7.6.1-1 A free implementation of the OpenG
ii  libglib2.0-0 2.22.4-1The GLib library of C routines
ii  libgtk2.0-0  2.18.6-1The GTK+ graphical user interface 
ii  libjack0 0.118+svn3796-2 JACK Audio Connection Kit (librari
ii  libjpeg626b-15   The Independent JPEG Group's JPEG 
ii  liblircclient0   0.8.3-5 infra-red remote control support -
ii  liblzo2-22.03-2  data compression library
ii  libncurses5  5.7+20090803-2  shared libraries for terminal hand
ii  libogg0  1.1.4~dfsg-2Ogg bitstream library
ii  libopenal1   1:1.10.622-1Software implementation of the Ope
ii  libpango1.0-01.26.2-1Layout and rendering of internatio
ii  libpng12-0   1.2.42-1PNG library - runtime
ii  libpostproc514:0.5+svn20090706-5 ffmpeg video postprocessing librar
ii  libpulse00.9.21-1PulseAudio client libraries
ii  libsdl1.2debian  1.2.13-5Simple DirectMedia Layer
ii  libsmbclient 2:3.4.5~dfsg-1  shared library for communication w
ii  libspeex11.2~rc1-1   The Speex codec runtime library
ii  libstdc++6   4.4.2-9 The GNU Standard C++ Library v3
ii  libsvga1 1:1.4.3-29  console SVGA display libraries
ii  libswscale0  4:0.5+svn20090706-5 ffmpeg video scaling library
ii  libtheora0   1.1.1+dfsg.1-3  The Theora Video Compression Codec
ii  libx11-6 2:1.3.3-1   X11 client-side library
ii  libxext6 2:1.1.1-2   X11 miscellaneous extension librar
ii  libxinerama1 2:1.1-2 X11 Xinerama extension library
ii  libxt6   1:1.0.7-1   X11 toolkit intrinsics library
ii  libxv1   2:1.0.5-1   X11 Video extension library
ii  libxvmc1 2:1.0.5-1   X11 Video extension library
ii  libxxf86dga1 2:1.1.1-2   X11 Direct Graphics Access extensi
ii  libxxf86vm1  1:1.1.0-2   X11 XFree86 video mode extension l
ii  mplayer-skin-blue [m 1.6-2   blue skin for mplayer
ii  zlib1g   1:1.2.3.4.dfsg-3compression library - runtime

mplayer recommends no packages.

Versions of packages mplayer suggests:
ii  bzip2 1.0.5-4high-quality block-sorting file co
ii  fontconfig2.8.0-2generic font configuration library
pn  mplayer-doc   none (no description available)
pn  netselect | fping none (no description available)
ii  ttf-freefont  20090104-5 Freefont Serif, Sans and Mono True

-- debconf information:
  mplayer/voutput: autodetect
  mplayer/ttfont: Sans
  mplayer/cfgnote:
  

Processed: tagging 489901

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 # wrong analysis, does build fine in lenny which has gcc-4.3
 tags 489901 + squeeze sid
Bug #489901 {Done: Cyril Brulebois k...@debian.org} [chiark-tcl] chiark-tcl: 
Missing include of limits.h when build with gcc-4.3
Added tag(s) sid and squeeze.

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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: closing 505356

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 close 505356
Bug#505356: FTBFS with GCC 4.4: missing #include
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Martin Michlmayr t...@cyrius.com


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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#568078: Multiple apps fail to start after using /usr/lib/gconv/ISO8859-1.so

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 reassign 568078 libenchant1c2a
Bug #568078 [libc6] Multiple apps fail to start after using 
/usr/lib/gconv/ISO8859-1.so
Bug reassigned from package 'libc6' to 'libenchant1c2a'.
Bug No longer marked as found in versions eglibc/2.10.2-5.
 forcemerge 568129 568078
Bug#568129: libenchant1c2a: terminates in libenchant_ispell
Bug#568078: Multiple apps fail to start after using /usr/lib/gconv/ISO8859-1.so
Forcibly Merged 568078 568129.

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#547011: open-iscsi: diff for NMU version 2.0.870~rc3-0.6

[Stefano Zacchiroli]

On Sat, Jan 23, 2010 at 06:12:19PM +0100, Guido Günther wrote:
 I've prepared an NMU for open-iscsi (versioned as 2.0.870~rc3-0.6) and
 uploaded it to DELAYED/05. Please feel free to tell me if I
 should delay it longer.

Heya Guido,
  what happened to this NMU? I can't see it in DELAYED [1], and while it
should have expired about a week ago, it has not yet hit the archive:

  z...@usha:~$ rmadison open-iscsi
  open-iscsi |  2.0.730-1 | etch-m68k | source, m68k
  open-iscsi | 2.0.730-1etch1 | oldstable | source, alpha, amd64, arm, 
hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc
  open-iscsi | 2.0.870~rc3-0.4 |stable | source, alpha, amd64, arm, 
armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc
  open-iscsi | 2.0.870~rc3-0.5 |   testing | source, amd64, armel, hppa, 
i386, ia64, mips, mipsel, powerpc, s390, sparc
  open-iscsi | 2.0.870~rc3-0.5 |  unstable | source, alpha, amd64, armel, 
hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc

nor it is in NEW.

Did you perhaps forget to upload? In that case let us know, so that
someone else with catch up, thanks to your patch :-)

Cheers.

[1] http://ftp-master.debian.org/deferred.html


-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#547011: open-iscsi: diff for NMU version 2.0.870~rc3-0.6

[Guido Günther]

On Wed, Feb 03, 2010 at 05:25:46PM +0100, Stefano Zacchiroli wrote:
 On Sat, Jan 23, 2010 at 06:12:19PM +0100, Guido Günther wrote:
  I've prepared an NMU for open-iscsi (versioned as 2.0.870~rc3-0.6) and
  uploaded it to DELAYED/05. Please feel free to tell me if I
  should delay it longer.
 
 Heya Guido,
   what happened to this NMU? I can't see it in DELAYED [1], and while it
 should have expired about a week ago, it has not yet hit the archive:
 
   z...@usha:~$ rmadison open-iscsi
   open-iscsi |  2.0.730-1 | etch-m68k | source, m68k
   open-iscsi | 2.0.730-1etch1 | oldstable | source, alpha, amd64, arm, 
 hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc
   open-iscsi | 2.0.870~rc3-0.4 |stable | source, alpha, amd64, arm, 
 armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc
   open-iscsi | 2.0.870~rc3-0.5 |   testing | source, amd64, armel, hppa, 
 i386, ia64, mips, mipsel, powerpc, s390, sparc
   open-iscsi | 2.0.870~rc3-0.5 |  unstable | source, alpha, amd64, armel, 
 hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc
 
 nor it is in NEW.
 
 Did you perhaps forget to upload? In that case let us know, so that
 someone else with catch up, thanks to your patch :-)
It got lintian autorejected due to a statically linked binary. We're
currently preparing a new upload including a new upstream version and a
new maintainer:
http://git.debian.org/?p=pkg-iscsi/open-iscsi.git;a=summary
Should be done in a couple of days.
Cheers,
 -- Guido



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed (with 1 errors): duplicate

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 forcemerge 475279 555233
Bug#475279: mediatomb-common: Don't embedd prototype.js
Bug#555233: mediatomb: embeds prototype.js
Mismatch - only Bugs in the same package can be forcibly merged:
Bug 555233 is not in the same package as 475279
 severity 555233 serious
Bug #555233 [mediatomb] mediatomb: embeds prototype.js
Severity set to 'serious' from 'important'

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568291: possible buffer overflows

[Steffen Joeris]

Package: libgmime-2.0-2a
Severity: grave
Tags: security patch

Hi

GMime upstream has released latest 2.4.15 [1] version of the
library fixing one security issue. From 2.4.15-changes [2] file:

2010-01-31  Jeffrey Stedfast  f...@novell.com

* gmime/gmime-encodings.h (GMIME_UUENCODE_LEN): Fixed to prevent
possible buffer overflows.

The vulnerable code seems to be in gmime/gmime-utils.h, I've attached
upstream's patch for your convenience, but I did not have a deeper look
at the buffer sizes, so it is unchecked.

stable is also affected and would need to be fixed as well I guess.
Please contact the secuirty team (t...@security.debian.org), if you've
checked the patch and have packages ready for lenny.
Thanks in advance.

Cheers
Steffen


References:

[1] http://ftp.gnome.org/pub/GNOME/sources/gmime/2.4/
[2] http://ftp.gnome.org/pub/GNOME/sources/gmime/2.4/gmime-2.4.15.changes
[3] http://ftp.gnome.org/pub/GNOME/sources/gmime/2.4/gmime-2.4.14-2.4.15.diff.gz
[4] http://secunia.com/advisories/38459/
diff -Nru -x '*.gmo' -x '*.mo' --speed-large-files --minimal gmime-2.4.14/ChangeLog gmime-2.4.15/ChangeLog
--- gmime-2.4.14/ChangeLog	2010-01-30 17:28:48.0 +
+++ gmime-2.4.15/ChangeLog	2010-02-02 13:51:02.0 +
@@ -1,3 +1,16 @@
+2010-02-02  Jeffrey Stedfast  f...@novell.com
+
+	* README: Bumped version
+
+	* configure.in: Bumped version to 2.4.15
+
+	* build/vs2008/gmime.vcproj: Bumped version.
+
+2010-01-31  Jeffrey Stedfast  f...@novell.com
+
+	* gmime/gmime-encodings.h (GMIME_UUENCODE_LEN): Fixed to prevent
+	possible buffer overflows.
+
 2010-01-30  Jeffrey Stedfast  f...@novell.com
 
 	* README: Bumped version
diff -Nru -x '*.gmo' -x '*.mo' --speed-large-files --minimal gmime-2.4.14/docs/reference/xml/gmime-encodings.xml gmime-2.4.15/docs/reference/xml/gmime-encodings.xml
--- gmime-2.4.14/docs/reference/xml/gmime-encodings.xml	2010-01-30 17:30:37.0 +
+++ gmime-2.4.15/docs/reference/xml/gmime-encodings.xml	2010-02-02 13:53:42.0 +
@@ -488,7 +488,7 @@
 /para/refsect2
 refsect2 id=GMIME-UUENCODE-LEN--CAPS role=macro
 titleGMIME_UUENCODE_LEN()/title
-indexterm zone=GMIME-UUENCODE-LEN--CAPSprimary sortas=GMIME_UUENCODE_LENGMIME_UUENCODE_LEN/primary/indextermprogramlisting#define GMIME_UUENCODE_LEN(x)  ((size_t) (x) + 2) / 45) * 62) + 62))
+indexterm zone=GMIME-UUENCODE-LEN--CAPSprimary sortas=GMIME_UUENCODE_LENGMIME_UUENCODE_LEN/primary/indextermprogramlisting#define GMIME_UUENCODE_LEN(x)  ((size_t) (x) + 2) / 45) * 62) + 64))
 /programlisting
 para
 Calculates the maximum number of bytes needed to uuencode the full
diff -Nru -x '*.gmo' -x '*.mo' --speed-large-files --minimal gmime-2.4.14/gmime/gmime-encodings.h gmime-2.4.15/gmime/gmime-encodings.h
--- gmime-2.4.14/gmime/gmime-encodings.h	2009-04-24 02:04:47.0 +
+++ gmime-2.4.15/gmime/gmime-encodings.h	2010-02-01 13:32:53.0 +
@@ -91,7 +91,7 @@
  * Returns: the number of output bytes needed to uuencode an input
  * buffer of size @x.
  **/
-#define GMIME_UUENCODE_LEN(x)  ((size_t) (x) + 2) / 45) * 62) + 62))
+#define GMIME_UUENCODE_LEN(x)  ((size_t) (x) + 2) / 45) * 62) + 64))
 
 
 /**

Processed: Fix typo in Severity line of submitter

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 severity 565961 serious
Bug #565961 [src:jlint] jlint: FTBFS: cp: cannot stat `manual.pdf': No such 
file or directory
Severity set to 'serious' from 'normal'

 --
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568066: marked as done (ftp.debian.org: apt has gone AWOL on i386 in sid)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 19:05:37 +0100
with message-id 87y6ja5h5a@turtle.gmx.de
and subject line Re: Bug#568066: ftp.debian.org: apt has gone AWOL on i386 in 
sid
has caused the Debian Bug report #568066,
regarding ftp.debian.org: apt has gone AWOL on i386 in sid
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
568066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: ftp.debian.org
Severity: important

I ran aptitude update and was informed that there are 4 new obsolete
packages: apt, apt-doc, apt-utils, libapt-pkg-dev.  Huh?!

The PTS shows that apt 0.7.25.3 was uploaded yesterday evening¹ but
neither the source nor the i386 packages are in incoming², although
binary packages for alpha and amd64 are there.


¹ http://packages.qa.debian.org/a/apt/news/20100201T213401Z.html
² http://incoming.debian.org/


---End Message---
---BeginMessage---
On 2010-02-02 07:10 +0100, Sven Joachim wrote:

 Package: ftp.debian.org
 Severity: important

 I ran aptitude update and was informed that there are 4 new obsolete
 packages: apt, apt-doc, apt-utils, libapt-pkg-dev.  Huh?!

 The PTS shows that apt 0.7.25.3 was uploaded yesterday evening¹ but
 neither the source nor the i386 packages are in incoming², although
 binary packages for alpha and amd64 are there.

All right, source and i386 binary packages of apt 0.7.25.3 are now
available on my mirror, so closing the bug.

Sven

---End Message---

Bug#561475: marked as done (libgcrypt11/mips(el): FTBFS with gcc-4.4)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 18:39:41 +
with message-id e1nck8b-0007rt...@ries.debian.org
and subject line Bug#561475: fixed in libgcrypt11 1.4.5-2
has caused the Debian Bug report #561475,
regarding libgcrypt11/mips(el): FTBFS with gcc-4.4
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
561475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libgcrypt11
Version: 1.4.1-1
Severity: serious
Tags: patch
Justification: fails to build from source

mpfr fails to build on mips(el) with gcc-4.4. A full build log can be
found here:
https://buildd.debian.org/fetch.cgi?pkg=libgcrypt11arch=mipselver=1.4.5-1stamp=1260977092file=logas=raw

This is due to a change in GCC 4.4, the h asm constraint is not 
supported anymore on mips. For more details please have a look at:
http://gcc.gnu.org/gcc-4.4/changes.html

The patch below fixes the problem by implementing the solution
recommended by the previous web page. With it libgcrypt11 builds 
successfully.

--- libgcrypt11-1.4.5.orig/mpi/longlong.h
+++ libgcrypt11-1.4.5/mpi/longlong.h
@@ -714,7 +714,15 @@ extern USItype __udiv_qrnnd ();
  **  MIPS  *
  ***/
 #if defined (__mips__)  W_TYPE_SIZE == 32
-#if __GNUC__  2 || __GNUC_MINOR__ = 7
+#if (__GNUC__ = 5) || (__GNUC__ == 4  __GNUC_MINOR__ = 4)
+#define umul_ppmm(w1, w0, u, v) \
+  do {  \
+UDItype _r; \
+_r = (UDItype) u * v;   \
+(w1) = _r  32;\
+(w0) = (USItype) _r;\
+  } while (0)
+#elif __GNUC__  2 || __GNUC_MINOR__ = 7
 #define umul_ppmm(w1, w0, u, v) \
   __asm__ (multu %2,%3\
   : =l ((USItype)(w0)),  \
@@ -739,7 +747,16 @@ extern USItype __udiv_qrnnd ();
  **  MIPS/64  **
  ***/
 #if (defined (__mips)  __mips = 3)  W_TYPE_SIZE == 64
-#if __GNUC__  2 || __GNUC_MINOR__ = 7
+#if (__GNUC__ = 5) || (__GNUC__ == 4  __GNUC_MINOR__ = 4)
+typedef unsigned int UTItype __attribute__ ((mode (TI)));
+#define umul_ppmm(w1, w0, u, v) \
+  do { \
+UTItype _r;\
+_r = (UTItype) u * v;  \
+(w1) = _r  64;   \
+(w0) = (UDItype) _r;   \
+  } while (0)
+#elif __GNUC__  2 || __GNUC_MINOR__ = 7
 #define umul_ppmm(w1, w0, u, v) \
   __asm__ (dmultu %2,%3   \
   : =l ((UDItype)(w0)),  \


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: mipsel (mips64)

Kernel: Linux 2.6.26-2-5kc-malta
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


---End Message---
---BeginMessage---
Source: libgcrypt11
Source-Version: 1.4.5-2

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

libgcrypt11-dbg_1.4.5-2_i386.deb
  to main/libg/libgcrypt11/libgcrypt11-dbg_1.4.5-2_i386.deb
libgcrypt11-dev_1.4.5-2_i386.deb
  to main/libg/libgcrypt11/libgcrypt11-dev_1.4.5-2_i386.deb
libgcrypt11-doc_1.4.5-2_all.deb
  to main/libg/libgcrypt11/libgcrypt11-doc_1.4.5-2_all.deb
libgcrypt11_1.4.5-2.debian.tar.gz
  to main/libg/libgcrypt11/libgcrypt11_1.4.5-2.debian.tar.gz
libgcrypt11_1.4.5-2.dsc
  to main/libg/libgcrypt11/libgcrypt11_1.4.5-2.dsc
libgcrypt11_1.4.5-2_i386.deb
  to main/libg/libgcrypt11/libgcrypt11_1.4.5-2_i386.deb



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 561...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Metzler ametz...@debian.org (supplier of updated libgcrypt11 package)

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

Processed: tagging as pending bugs that are closed by packages in NEW

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 # Wed Feb  3 19:03:38 UTC 2010
 # Tagging as pending bugs that are closed by packages in NEW
 # http://ftp-master.debian.org/new.html
 #
 # Source package in NEW: mapserver
 tags 565831 + pending
Bug #565831 [libmapscript-ruby1.9] libmapscript-ruby1.9: Please drop the 
dependency on ruby 1.9.0
Added tag(s) pending.
 # Source package in NEW: clojure-contrib
 tags 566962 + pending
Bug #566962 [wnpp] ITP: clojure-contrib -- extensions and enhancements to 
clojure libraries
Added tag(s) pending.
 # Source package in NEW: freehep-graphicsio
 tags 564756 + pending
Bug #564756 [wnpp] ITP: freehep-graphicsio -- FreeHEP GraphicsIO Base Library
Added tag(s) pending.

End of message, stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#553430: marked as done (Copyright file does not contain verbatim copy of the license or a pointer to one)

[Debian Bug Tracking System]

Your message dated Wed, 3 Feb 2010 20:40:46 +0100
with message-id 8b2d7b4d1002031140q381d464fg548fb579334b9...@mail.gmail.com
and subject line Package removed from Debian unstable
has caused the Debian Bug report #553430,
regarding Copyright file does not contain verbatim copy of the license or a 
pointer to one
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
553430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: aish
Version: 1.13-5
Severity: serious

Hi,

The copyright file should either have a verbatim copy of the
 license, or a statement that the license can be found in
 /usr/share/common-licenses on a Debian machine (and the FSF's address
 if they want toget the license from there.

An email excerpt does not meet policy requirements.

manoj



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

Kernel: Linux 2.6.31.4-anzu-2 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aish depends on:
ii  libc6 2.10.1-3   GNU C Library: Shared libraries

aish recommends no packages.

aish suggests no packages.


---End Message---
---BeginMessage---
Version: 1.13-5+rm

Package removed from Debian unstable: http://bugs.debian.org/559921

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

---End Message---

Bug#568304: breaks touchpad

[Christoph Anton Mitterer]

Package: gpointing-device-settings
Version: 1.5.0-1
Justification: breaks unrelated software
Severity: critical

Hi.

Upgrading to the 1.5.0-1 breaks the touchpad.
On the login-screen (gdm) the touchpad still works. As soon as logon  
happened the touchpad stops working.

Downgrading to 1.3 from testing solves the problem.
(btw: toucpad was not disabled in the settings dialog)

Breaks one of the main X input devices (mouse), thus severity=ciritical.

Cheers,
Chris.


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

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

Versions of packages gpointing-device-settings depends on:
ii  gconf22.28.0-1   GNOME configuration  
database syste

ii  libatk1.0-0   1.28.0-1   The ATK accessibility toolkit
ii  libc6 2.10.2-5   Embedded GNU C Library:  
Shared lib
ii  libcairo2 1.8.8-2The Cairo 2D vector  
graphics libra
ii  libfontconfig12.8.0-2generic font  
configuration library
ii  libfreetype6  2.3.11-1   FreeType 2 font engine,  
shared lib
ii  libgconf2-4   2.28.0-1   GNOME configuration  
database syste

ii  libglib2.0-0  2.22.4-1   The GLib library of C routines
ii  libgpds0  1.5.0-1library for configuration  
of point

ii  libgtk2.0-0   2.18.6-1   The GTK+ graphical user interface
ii  libpango1.0-0 1.26.2-1   Layout and rendering of  
internatio

ii  libxi62:1.3-2X11 Input extension library

gpointing-device-settings recommends no packages.

gpointing-device-settings suggests no packages.

-- no debconf information


This message was sent using IMP, the Internet Messaging Program.




--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#548648: grub-pc jumps straight to rescue and prints error: no such disk / file not found

[Josip Rodin]

On Sat, Jan 02, 2010 at 03:00:39PM +0100, Josip Rodin wrote:
 On Sat, Jan 02, 2010 at 02:29:36PM +0100, Josip Rodin wrote:
  I've got two disks and a software RAID setup on the partition that holds
  the /boot directory. I have several Linux software RAID partitions, based
  on this scheme:
  
  sda2+sdb2   - Linux amd64 /
  sda3+sdb3   - Linux i386 /
  sda5+sdb5   - Linux swap
  sda6+sdb6   - Linux /home
  
  The first two become md0, differentiated by old GRUB menu entries -
  Linux parameters raid=noautodetect and md0=first,second ... settings.
  The second two become md1 and md2, respectively, and the fourth array
  is simply left unassembled on the non-applicable architecture.
 
 my autogenerated menu entry for the amd64 root partition seemed to have
 the wrong UUID in the 'search' command. That sounds like a userland issue,
 because:
 
 % sudo grub-probe -d /dev/sda1 -t fs_uuid
 1460509560508002
 % sudo grub-probe -d /dev/sda2 -t fs_uuid
 18515dea-973e-473b-bddf-74d1cb58e15a
 % sudo grub-probe -d /dev/sda3 -t fs_uuid
 7e6cdce7-8136-41f0-8a66-997b89ea00fe
 
 And yet after running the update-grub command on the amd64 machine
 I still get:
 
 % grep search /boot/grub/grub.cfg | sort -u
 search --no-floppy --fs-uuid --set 1460509560508002
 search --no-floppy --fs-uuid --set 
 7e6cdce7-8136-41f0-8a66-997b89ea00fe
 
 It's supposed to detect the amd64 partition (sda2) at least once :)
 but it seems to be fixating on the i386 one (sda3).

This behaviour seems to be a problem with grub-probe and its usage by the
default config scripts, because the simple most straightforward test fails
for one of the RAID devices:

% sudo tune2fs -l /dev/md0 | grep UUID
Filesystem UUID:  18515dea-973e-473b-bddf-74d1cb58e15a
% sudo grub-probe --device /dev/md0 --target=fs_uuid
7e6cdce7-8136-41f0-8a66-997b89ea00fe

% sudo tune2fs -l /dev/md2 | grep UUID
Filesystem UUID:  222e0fc1-800d-4be4-89fa-96a876aca441
% sudo grub-probe --device /dev/md2 --target=fs_uuid
222e0fc1-800d-4be4-89fa-96a876aca441

What it thinks to be /dev/md0 isn't actually what the rest of the system
knows to be /dev/md0 (nor is it actually what grub sees as md0 on boot time,
as it happens).

The --device option is used by /usr/lib/grub/grub-mkconfig_lib's
prepare_grub_to_access_device() function, invoked in turn by
/etc/grub.d/10_linux's linux_entry() function.
When I omit that parameter, I get:

% sudo grub-probe /dev/md0 --target=fs_uuid
grub-probe: error: cannot find a device for /dev/md0.

I'm not really sure what to make of util/grub-probe.c's usage of
util/getroot.c' grub_guess_root_device() at least under Linux...
is it supposed to resolve canonical names out of input device names?

-- 
 2. That which causes joy or happiness.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568304: breaks touchpad

[Michal Čihař]

Hi

Dne Wed, 03 Feb 2010 20:45:20 +0100
Christoph Anton Mitterer
christoph.anton.mitte...@physik.uni-muenchen.de napsal(a):

 Upgrading to the 1.5.0-1 breaks the touchpad.
 On the login-screen (gdm) the touchpad still works. As soon as logon  
 happened the touchpad stops working.
 Downgrading to 1.3 from testing solves the problem.
 (btw: toucpad was not disabled in the settings dialog)
 
 Breaks one of the main X input devices (mouse), thus severity=ciritical.

What exactly you mean by breaks?

Can you please provide output of 'synclient -l'?

-- 
Michal Čihař | http://cihar.com | http://blog.cihar.com


signature.asc
Description: PGP signature

Bug#499076: CVE-2009-4411: Physical walk no longer ignores all symlinks

[Moritz Muehlenhoff]

Markus Steinborn wrote:
 Just for your information:
 
 version 2.2.49 improves the situation, that's right. But it does not fix 
 the bug.
 
 For a test case that does not work and a working patch that I 
 contributed see
 
 https://savannah.nongnu.org/bugs/?28131
 
 Additional information is on:
 
 https://bugzilla.redhat.com/show_bug.cgi?id=488674

Anibal, please fix this bug through a stable point update for
Lenny.

Cheers,
Moritz



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#568049: gnumail.app: GNUMail systematically segfaults at startup

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 clone 568049 -1
Bug#568049: gnumail.app: GNUMail systematically segfaults at startup
Bug 568049 cloned as bug 568307.

 reassign -1 gnustep-back-common 0.16.0-3
Bug #568307 [gnumail.app] gnumail.app: GNUMail systematically segfaults at 
startup
Bug reassigned from package 'gnumail.app' to 'gnustep-back-common'.
Bug No longer marked as found in versions gnumail/1.2.0~pre3+snap20071004-4.
Bug #568307 [gnustep-back-common] gnumail.app: GNUMail systematically segfaults 
at startup
Bug Marked as found in versions gnustep-back/0.16.0-3.
 severity -1 serious
Bug #568307 [gnustep-back-common] gnumail.app: GNUMail systematically segfaults 
at startup
Severity set to 'serious' from 'important'

 retitle -1 Generates incomplete nfont bundles which makes the art backend 
 unusable
Bug #568307 [gnustep-back-common] gnumail.app: GNUMail systematically segfaults 
at startup
Changed Bug title to 'Generates incomplete nfont bundles which makes the art 
backend unusable' from 'gnumail.app: GNUMail systematically segfaults at 
startup'
 fixed -1 0.17.1-1
Bug #568307 [gnustep-back-common] Generates incomplete nfont bundles which 
makes the art backend unusable
Bug Marked as fixed in versions gnustep-back/0.17.1-1.
 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568304: touchpad

[Kai Weber]

Package: gpointing-device-settings
Version: 1.5.0-1
Severity: normal

I can confirm this bug and behaviour. The touchpad does not work
anymore.

Output of synclient -l attached but seems to be ok.

Regards, Kai

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gpointing-device-settings depends on:
ii  gconf22.28.0-1   GNOME configuration database syste
ii  libatk1.0-0   1.28.0-1   The ATK accessibility toolkit
ii  libc6 2.10.2-5   Embedded GNU C Library: Shared lib
ii  libcairo2 1.8.8-2The Cairo 2D vector graphics libra
ii  libdbus-1-3   1.2.16-2   simple interprocess messaging syst
ii  libdbus-glib-1-2  0.84-1 simple interprocess messaging syst
ii  libfontconfig12.8.0-2generic font configuration library
ii  libfreetype6  2.3.11-1   FreeType 2 font engine, shared lib
ii  libgconf2-4   2.28.0-1   GNOME configuration database syste
ii  libglib2.0-0  2.22.4-1   The GLib library of C routines
ii  libgpds0  1.5.0-1library for configuration of point
ii  libgtk2.0-0   2.18.6-1   The GTK+ graphical user interface 
ii  libpango1.0-0 1.26.2-1   Layout and rendering of internatio
ii  libxi62:1.3-2X11 Input extension library

gpointing-device-settings recommends no packages.

gpointing-device-settings suggests no packages.

-- no debconf information
Parameter settings:
LeftEdge= 1752
RightEdge   = 5192
TopEdge = 1620
BottomEdge  = 4236
FingerLow   = 24
FingerHigh  = 29
FingerPress = 255
MaxTapTime  = 180
MaxTapMove  = 221
MaxDoubleTapTime= 180
SingleTapTimeout= 180
ClickTime   = 100
FastTaps= 0
EmulateMidButtonTime= 75
EmulateTwoFingerMinZ= 280
EmulateTwoFingerMinW= 7
VertScrollDelta = 100
HorizScrollDelta= 100
VertEdgeScroll  = 1
HorizEdgeScroll = 1
CornerCoasting  = 0
VertTwoFingerScroll = 0
HorizTwoFingerScroll= 0
MinSpeed= 0
MaxSpeed= 0
AccelFactor = 4.48416e-44
TrackstickSpeed = 4.62428e-44
EdgeMotionMinZ  = 29
EdgeMotionMaxZ  = 159
EdgeMotionMinSpeed  = 1
EdgeMotionMaxSpeed  = 401
EdgeMotionUseAlways = 0
UpDownScrolling = 1
LeftRightScrolling  = 1
UpDownScrollRepeat  = 1
LeftRightScrollRepeat   = 1
ScrollButtonRepeat  = 100
TouchpadOff = 0
GuestMouseOff   = 0
LockedDrags = 0
LockedDragTimeout   = 5000
RTCornerButton  = 0
RBCornerButton  = 0
LTCornerButton  = 0
LBCornerButton  = 0
TapButton1  = 0
TapButton2  = 0
TapButton3  = 0
ClickFinger1= -48
ClickFinger2= 0
ClickFinger3= -68
CircularScrolling   = 0
CircScrollDelta = 0.1
CircScrollTrigger   = 0
CircularPad = 0
PalmDetect  = 0
PalmMinWidth= 10
PalmMinZ= 199
CoastingSpeed   = 0
PressureMotionMinZ  = 29
PressureMotionMaxZ  = 159
PressureMotionMinFactor = 1
PressureMotionMaxFactor = 1
GrabEventDevice = 1
TapAndDragGesture   = 1
AreaLeftEdge= 0
AreaRightEdge   = 0
AreaTopEdge = 0
AreaBottomEdge  = 0

Processed: severity of 475279 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 severity 475279 serious
Bug #475279 [mediatomb-common] mediatomb-common: Don't embedd prototype.js
Severity set to 'serious' from 'important'

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#554790: grub-pc: store grub-pc/install_devices using by-id

[Colin Watson]

On Sat, Jan 30, 2010 at 05:24:06PM +0100, Harald Dunkel wrote:
 Colin Watson wrote:
  UUIDs are properties of filesystems, not disks or partitions, and the
  MBR of a hard disk does not have a UUID.
 
 Since MSDOS partitions are limited to 2TByte partitions anyway, it
 might be wise to look at alternatives, e.g. GPT. GPT _does_ provide
 a UUID in the disk header _and_ in the header of each partition.
 
 Wikipedia provides an excellent overview:
 
   http://en.wikipedia.org/wiki/GUID_Partition_Table

I am already familiar with GPT, but I do not consider it appropriate to
implement a fix only for one partition table type.  It's not remotely
trivial for users to migrate to GPT, and there are many users affected
by this problem right now on MS-DOS partitions.  We should not tie this
bug in with semi-blue-sky partition table migration plans, especially
since there is no need whatsoever to do so.  by-id is perfectly
sufficient for our needs.

  For disks, the choices for stable identifiers are based on either
  the hardware serial number or the bus path taken to reach the disk.
 
 What about block device emulations, e.g. software RAIDs, LVM, etc?

Let's let Linux worry about how to represent those in by-id, eh?  We
don't need to second-guess it.

Anyway, LVM doesn't matter here because you don't install GRUB to an LVM
(you might have /boot on an LVM, but that's a different matter); RAID
also doesn't matter very much in practice because right now the effect
of installing GRUB to a RAID volume is to install to the boot sectors of
all the constituent disks.  I've tested both scenarios.

-- 
Colin Watson   [cjwat...@debian.org]



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#475279: Fwd: Bug#475279: mediatomb-common: Don't embedd prototype.js

[Mehdi]

On  0, Andres Mejia mcita...@gmail.com wrote:
 Hello Jin,
 
 I'm not sure if Leo already told you this, but here's a bug asking for 
 mediatomb not to use an embedded prototype.js.
 
 I've already tried using the prototype.js delivered in Debian (version 
 1.6.0.2). It's giving me problems with the web UI where I can't click over 
 to Filesystem to browse my computer. The prototype.js embedded in mediatomb 
 is version 1.5.1.1.
 

I've just test mediatomb with debian-shipped prototype 1.6.1 but got
no issues.  The UI is working fine, and I'm able to click over
Filesystem to browse my computer. Do you think that 1.6.1 fixed the
problems encoutered while using 1.6.0? 

If you still have the same issues, please provide us the steps you
followed to reproduce the problem.

Regards,

-- 
Mehdi Dogguy



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568312: libgmime-2.0-2a: needs -fno-strict-aliasing

[Lionel Elie Mamane]

Package: libgmime-2.0-2a
Version: 2.2.22-5
Severity: grave
Tags: patch

After upgrading from version 2.2.22-4 to 2.2.22-5, pan ceased to send
email correctly at all. It behaves exactly as if no email recipient is
set. I presume that the problem is that
g_mime_message_add_recipients_from_string fails to do its job.

This is corrected by recompiling libgmime-2.0-2a with
-fno-strict-aliasing added to CFLAGS. Upstream released version 2.2.25
with just that change (compared to 2.2.24):

* configure.in: Disabled strict-aliasing to work around subtle
bugs generated by gcc 4.4 when optimizations are enabled.

Please either upgrade to upstream version 2.2.25 or at least apply
this patch in the meantime (and rerun autoconf):

diff --recursive -uN gmime-2.2.24/configure.in gmime-2.2.25/configure.in
--- gmime-2.2.24/configure.in   2009-08-12 19:54:29.0 +0200
+++ gmime-2.2.25/configure.in   2010-01-30 18:53:51.0 +0100
@@ -498,6 +498,7 @@
EXTRA_LIBS=$EXTRA_LIBS $LIBICONV
 fi
 
+CFLAGS=$CFLAGS -fno-strict-aliasing
 AC_SUBST(CFLAGS)
 
 LIBS=$LIBS $EXTRA_LIBS



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

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libgmime-2.0-2a depends on:
ii  libc6   2.10.2-3 Embedded GNU C Library: Shared lib
ii  libglib2.0-02.22.3-2 The GLib library of C routines
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

libgmime-2.0-2a recommends no packages.

libgmime-2.0-2a suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568304: touchpad

[Michal Čihař]

Hi

Dne Wed, 03 Feb 2010 22:03:52 +0100
Kai Weber kai.we...@glorybox.de napsal(a):

 Package: gpointing-device-settings
 Version: 1.5.0-1
 Severity: normal
 
 I can confirm this bug and behaviour. The touchpad does not work
 anymore.
 
 Output of synclient -l attached but seems to be ok.

These two seems to be low:

AccelFactor = 4.48416e-44
TrackstickSpeed = 4.62428e-44

Can you set them to something more reasonable (eg. by using synclient)?

My values are
AccelFactor = 0.01
TrackstickSpeed = 40

-- 
Michal Čihař | http://cihar.com | http://blog.cihar.com


signature.asc
Description: PGP signature

Bug#560644: clxclient: diff for NMU version 3.6.1-1.1

[Mehdi]

tag 560644 + pending
thanks

Dear maintainer,

I've prepared an NMU for clxclient (versioned as 3.6.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Mehdi Dogguy
diff -u clxclient-3.6.1/debian/changelog clxclient-3.6.1/debian/changelog
--- clxclient-3.6.1/debian/changelog
+++ clxclient-3.6.1/debian/changelog
@@ -1,3 +1,11 @@
+clxclient (3.6.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove 'x_map' from debian/libclxclient3.symbols.*, thanks to Kamal Mostafa
+(Closes: #560644)
+
+ -- Mehdi Dogguy me...@debian.org  Wed, 03 Feb 2010 22:18:48 +0100
+
 clxclient (3.6.1-1) unstable; urgency=low
 
   * New upstream release
@@ -41 +48,0 @@
-
diff -u clxclient-3.6.1/debian/libclxclient3.symbols.amd64 clxclient-3.6.1/debian/libclxclient3.symbols.amd64
--- clxclient-3.6.1/debian/libclxclient3.symbols.amd64
+++ clxclient-3.6.1/debian/libclxclient3.symbols.amd64
@@ -296,7 +296,6 @@
  _znk8x_window12x_set_attribemp20xsetwindowattribu...@base 3.6.1-1~
  _znk8x_window17x_set_bit_gravit...@base 3.6.1-1~
  _znk8x_window17x_set_win_gravit...@base 3.6.1-1~
- _znk8x_window5x_ma...@base 3.6.1-1~
  _znk8x_window6x_move...@base 3.6.1-1~
  _znk8x_window8x_resize...@base 3.6.1-1~
  _zti10x_callb...@base 3.6.1-1~
diff -u clxclient-3.6.1/debian/libclxclient3.symbols.i386 clxclient-3.6.1/debian/libclxclient3.symbols.i386
--- clxclient-3.6.1/debian/libclxclient3.symbols.i386
+++ clxclient-3.6.1/debian/libclxclient3.symbols.i386
@@ -296,7 +296,6 @@
  _znk8x_window12x_set_attribemp20xsetwindowattribu...@base 3.6.1-1~
  _znk8x_window17x_set_bit_gravit...@base 3.6.1-1~
  _znk8x_window17x_set_win_gravit...@base 3.6.1-1~
- _znk8x_window5x_ma...@base 3.6.1-1~
  _znk8x_window6x_move...@base 3.6.1-1~
  _znk8x_window8x_resize...@base 3.6.1-1~
  _zti10x_callb...@base 3.6.1-1~

Processed: clxclient: diff for NMU version 3.6.1-1.1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tag 560644 + pending
Bug #560644 [src:clxclient] clxclient: FTBFS: dpkg-gensymbols fails
Added tag(s) 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568309: xserver-xorg: starts but displays blank screen responds to ctrl alt f1

[Brice Goglin]

reassign 568309 xserver-xorg-video-radeon 1:6.12.4-3
thank you



Ben Whyte wrote:
 Package: xserver-xorg
 Version: 1:7.5+3
 Severity: grave
 Justification: renders package unusable


 My system fails to display the KDM boot manager but does respond to swapping 
 to terminal.

 Using the VESA driver with the virtual directive removed I can get a login 
 box but not suitable as it limits me to single screen and 1280x1024.

 Radeonhd, radeon or ati driver produce the same result.
   

Can you try xserver-xorg-video-radeon from experimental ?

Brice




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#564415: Closing

[Guido Günther]

Hi Bastian,
thanks for reporting back. Closing this as fixed in 3.0.1-1.
Cheers,
 -- Guido



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: closing 564415

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 close 564415 3.0.1-1
Bug#564415: [icedove-3.0] Does not start anymore (strace attached)
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 3.0.1-1, send any further explanations to 
Bastian Venthur vent...@debian.org

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#568309: xserver-xorg: starts but displays blank screen responds to ctrl alt f1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 reassign 568309 xserver-xorg-video-radeon 1:6.12.4-3
Bug #568309 [xserver-xorg] xserver-xorg: starts but displays blank screen 
responds to ctrl alt f1
Bug reassigned from package 'xserver-xorg' to 'xserver-xorg-video-radeon'.
Bug No longer marked as found in versions xorg/1:7.5+3.
Bug #568309 [xserver-xorg-video-radeon] xserver-xorg: starts but displays blank 
screen responds to ctrl alt f1
Bug Marked as found in versions xserver-xorg-video-ati/1:6.12.4-3.
 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: fixed 555313 in 3.0.1-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 fixed 555313 3.0.1-1
Bug #555313 [src:icedove] iceweasel: CVE-2009-3371 user-after-free possibly 
leading to arbitrary code execution
Bug Marked as fixed in versions icedove/3.0.1-1.
 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#557672: traceroute-nanog: FHS violation: root-only program in /usr/bin

[Daniel Kobras]

block 557672 with 568314
thanks

On Mon, Jan 25, 2010 at 09:19:01AM +0100, Daniel Baumann wrote:
 Daniel Kobras wrote:
  Are you aware of any relevant features still missing?
 
 not that i'm aware of.

I've just filed a removal request for traceroute-nanog, which will
eventually resolve this bug.

Regards,

Daniel.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#557672: traceroute-nanog: FHS violation: root-only program in /usr/bin

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 block 557672 with 568314
Bug #557672 [traceroute-nanog] traceroute-nanog: FHS violation: root-only 
program in /usr/bin
Was not blocked by any bugs.
Added blocking bug(s) of 557672: 568314
 thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568319: esniper: Version 2.22 reports as 2.21

[Sebastian Niehaus]

Package: esniper
Version: 2.22.0-1
Severity: grave


| nieh...@ceramic:/tmp$ esniper  -v
| esniper version 2.21.0
| 
|The newest version is 2.22.0, you should upgrade.


The installed version does not work any more with ebay in germany 
(it worked some days ago)...

Its version number is 2.22.0-1 bit it states to be 2.21.0. Strange.

Sebastian 



-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages esniper depends on:
ii  ca-certificates   20080809   Common CA certificates
ii  libc6 2.7-18lenny2   GNU C Library: Shared libraries
ii  libcurl3  7.18.2-8lenny3 Multi-protocol file transfer libra

esniper recommends no packages.

esniper suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: libpcscada0.6 and libpcscada0: error when trying to install together

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 reassign 566096 libpcscada0.6
Bug #566096 [libpcscada0,libpcscada0.6] libpcscada0.6 and libpcscada0: error 
when trying to install together
Warning: Unknown package 'libpcscada0'
Bug reassigned from package 'libpcscada0,libpcscada0.6' to 'libpcscada0.6'.

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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: vkeybd: diff for NMU version 1:0.1.18d-1.1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tag 560556 + pending
Bug #560556 [src:vkeybd] vkeybd: FTBFS: install: cannot stat 
`/build/user-vkeybd_0.1.18d-1-amd64-bONnrx/vkeybd-0.1.18d/vkeybd.xpm': No such 
file or directory
Added tag(s) 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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#475279: Fwd: Bug#475279: mediatomb-common: Don't embedd prototype.js

[Sergey 'Jin' Bostandzhyan]

Hi,

On Wed, Feb 03, 2010 at 10:12:08PM +0100, Mehdi wrote:
  I'm not sure if Leo already told you this, but here's a bug asking for 
  mediatomb not to use an embedded prototype.js.
  
  I've already tried using the prototype.js delivered in Debian (version 
  1.6.0.2). It's giving me problems with the web UI where I can't click over 
  to Filesystem to browse my computer. The prototype.js embedded in 
  mediatomb 
  is version 1.5.1.1.
  
 
 I've just test mediatomb with debian-shipped prototype 1.6.1 but got
 no issues.  The UI is working fine, and I'm able to click over
 Filesystem to browse my computer. Do you think that 1.6.1 fixed the
 problems encoutered while using 1.6.0? 

we have prototype 1.6.1 in SVN now and the web UI works fine with it. We are
still embedding it, because prototype updates can break functionality, at least
it did happen in the past a couple of times.

You could patch it out in the .deb package so that the system wide prototype
is used, however care should be takaen when it is being updated, i.e. it will
need testing to be sure that a newer prototype version does not break the UI.

Kind regards,
Jin




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#554197: bacula: usr-share-doc-symlink-without-dependency

[Stephen Kitt]

Package: bacula
Severity: normal


Hi,

This bug is actually fixed in version 3.0.3-1.

Regards,

Stephen

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

Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bacula depends on:
ii  bacula-client 3.0.3-1.1  network backup, recovery and verif
ii  bacula-common 3.0.3-1.1  network backup, recovery and verif
ii  bacula-server 3.0.3-1.1  network backup, recovery and verif

bacula recommends no packages.

Versions of packages bacula suggests:
ii  bacula-doc2.4.4-1Documentation for Bacula

-- no debconf information

-- debsums errors found:
debsums: no md5sums for bacula



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#560556: vkeybd: diff for NMU version 1:0.1.18d-1.1

[Mehdi]

tag 560556 + pending
thanks

Dear maintainer,

I've prepared an NMU for vkeybd (versioned as 1:0.1.18d-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Mehdi Dogguy
diff -u vkeybd-0.1.18d/debian/changelog vkeybd-0.1.18d/debian/changelog
--- vkeybd-0.1.18d/debian/changelog
+++ vkeybd-0.1.18d/debian/changelog
@@ -1,3 +1,11 @@
+vkeybd (1:0.1.18d-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix headers for vkeybd_xpm_fix.dpatch, thanks to Ilya Barygin for
+the patch (Closes: #560556)
+
+ -- Mehdi Dogguy me...@debian.org  Wed, 03 Feb 2010 22:49:23 +0100
+
 vkeybd (1:0.1.18d-1) unstable; urgency=low
 
   * New upstream version, thanks to Jean-Michel Philippe (Closes: #527942, #527943)
@@ -66 +73,0 @@
-
diff -u vkeybd-0.1.18d/debian/patches/vkeybd_xpm_fix.dpatch vkeybd-0.1.18d/debian/patches/vkeybd_xpm_fix.dpatch
--- vkeybd-0.1.18d/debian/patches/vkeybd_xpm_fix.dpatch
+++ vkeybd-0.1.18d/debian/patches/vkeybd_xpm_fix.dpatch
@@ -6,8 +6,8 @@
 
 @DPATCH@
 diff -urNad vkeybd-0.1.17/vkeybd.xpm /tmp/dpep.ufyHue/vkeybd-0.1.17/vkeybd.xpm
 vkeybd-0.1.17/vkeybd.xpm	1970-01-01 01:00:00.0 +0100
-+++ /tmp/dpep.ufyHue/vkeybd-0.1.17/vkeybd.xpm	2005-05-10 00:10:52.0 +0200
+--- vkeybd-0.1.17.old/vkeybd.xpm	1970-01-01 01:00:00.0 +0100
 vkeybd-0.1.17.new/vkeybd.xpm	2005-05-10 00:10:52.0 +0200
 @@ -0,0 +1,294 @@
 +/* XPM */
 +static char *vkeybd[] = {

Bug#567095: [Pkg-samba-maint] Bug#567095: Samba does not correctly set named ACL for owning group and user

[Christian PERRIER]

 I'm staring to code a simple script to run at night that will add a
 'named default acl' for every folder as a temporary countermeasure, but
 this seems really a grave functionality bugs and i hope debian samba
 team will backport and apply the fix to 3.2.


I'm suspecting that I went on this bug on a major server of mine, that
recently got upgraded from etch to lenny.

Actually, that bug seems to be coupled with upstream #4308 on our
server, leading to a very messy situation with ACLs when Excel files
are involved.

However, while #4308 has a straightforward fix that we could consider
backporting to 3.2.5 (the fix was done in 3.2.8), #6878 patch seems to
be less obvious.

If someone comes up with such backported fix, I think we should
consider including it.




signature.asc
Description: Digital signature

Bug#475279: Fwd: Bug#475279: mediatomb-common: Don't embedd prototype.js

[Mehdi Dogguy]

Sergey 'Jin' Bostandzhyan wrote:
 Hi,
 
 On Wed, Feb 03, 2010 at 10:12:08PM +0100, Mehdi wrote:
 I'm not sure if Leo already told you this, but here's a bug asking for 
 mediatomb not to use an embedded prototype.js.

 I've already tried using the prototype.js delivered in Debian (version 
 1.6.0.2). It's giving me problems with the web UI where I can't click over 
 to Filesystem to browse my computer. The prototype.js embedded in 
 mediatomb 
 is version 1.5.1.1.

 I've just test mediatomb with debian-shipped prototype 1.6.1 but got
 no issues.  The UI is working fine, and I'm able to click over
 Filesystem to browse my computer. Do you think that 1.6.1 fixed the
 problems encoutered while using 1.6.0? 
 
 we have prototype 1.6.1 in SVN now and the web UI works fine with it. We are
 still embedding it, because prototype updates can break functionality, at 
 least
 it did happen in the past a couple of times.
 

thanks for the fast answer!

 You could patch it out in the .deb package so that the system wide prototype
 is used, however care should be takaen when it is being updated, i.e. it will
 need testing to be sure that a newer prototype version does not break the UI.
 

That could be coordinated with the usual libjs-prototype maintainer
(CC'ed) when updates happen. At least, maintainers of software using
prototypejs should be warned before a new version is being uploaded so
that they can test their packages and detect possible breakage.

Kind regards,

-- 
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568291: possible buffer overflows

[Mirco Bauer]

On Wed, 03 Feb 2010 18:12:45 +0100
Steffen Joeris steffen.joe...@skolelinux.de wrote:

 Package: libgmime-2.0-2a
 Severity: grave
 Tags: security patch
 
 Hi
 
 GMime upstream has released latest 2.4.15 [1] version of the
 library fixing one security issue. From 2.4.15-changes [2] file:
 
 2010-01-31  Jeffrey Stedfast  f...@novell.com
 
 * gmime/gmime-encodings.h (GMIME_UUENCODE_LEN): Fixed to
 prevent possible buffer overflows.
 
 The vulnerable code seems to be in gmime/gmime-utils.h, I've attached
 upstream's patch for your convenience, but I did not have a deeper
 look at the buffer sizes, so it is unchecked.
 
 stable is also affected and would need to be fixed as well I guess.
 Please contact the secuirty team (t...@security.debian.org), if you've
 checked the patch and have packages ready for lenny.

Upstream contacted me already and said that gmime2.2 is not
affected, only gmime2.4 is.

 Thanks in advance.

Thanks for having on eye on this!

 
 Cheers
 Steffen
 
 
 References:
 
 [1] http://ftp.gnome.org/pub/GNOME/sources/gmime/2.4/
 [2]
 http://ftp.gnome.org/pub/GNOME/sources/gmime/2.4/gmime-2.4.15.changes
 [3]
 http://ftp.gnome.org/pub/GNOME/sources/gmime/2.4/gmime-2.4.14-2.4.15.diff.gz
 [4] http://secunia.com/advisories/38459/


-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developermee...@meebey.net  http://www.meebey.net/
PEAR Developermee...@php.net http://pear.php.net/
Debian Developer  mee...@debian.org  http://www.debian.org/



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#560463: marked as done (libcommoncpp2: FTBFS: cidr.cpp:205: error: invalid conversion from 'const char*' to 'char*')

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 22:20:19 +
with message-id e1ncna7-0003r6...@ries.debian.org
and subject line Bug#560463: fixed in libcommoncpp2 1.7.3-1.1
has caused the Debian Bug report #560463,
regarding libcommoncpp2: FTBFS: cidr.cpp:205: error: invalid conversion from 
'const char*' to 'char*'
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
560463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libcommoncpp2
Version: 1.7.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091210 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
 /bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
 -I../inc-I../src -DCCXX_EXPORT_LIBRARY  -D_GNU_SOURCE -I../inc  -g -O2 -g 
 -Wall -O2 -c -o cidr.lo cidr.cpp
 libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../inc -I../src 
 -DCCXX_EXPORT_LIBRARY -D_GNU_SOURCE -I../inc -g -O2 -g -Wall -O2 -c cidr.cpp  
 -fPIC -DPIC -o .libs/cidr.o
 cidr.cpp: In member function 'void ost::IPV4Cidr::set(const char*)':
 cidr.cpp:205: error: invalid conversion from 'const char*' to 'char*'
 cidr.cpp: In member function 'void ost::IPV6Cidr::set(const char*)':
 cidr.cpp:335: error: invalid conversion from 'const char*' to 'char*'
 make[3]: *** [cidr.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/12/10/libcommoncpp2_1.7.3-1_lsid64.buildlog

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

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

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


---End Message---
---BeginMessage---
Source: libcommoncpp2
Source-Version: 1.7.3-1.1

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

libccgnu2-1.7-0_1.7.3-1.1_i386.deb
  to main/libc/libcommoncpp2/libccgnu2-1.7-0_1.7.3-1.1_i386.deb
libcommoncpp2-dev_1.7.3-1.1_i386.deb
  to main/libc/libcommoncpp2/libcommoncpp2-dev_1.7.3-1.1_i386.deb
libcommoncpp2-doc_1.7.3-1.1_all.deb
  to main/libc/libcommoncpp2/libcommoncpp2-doc_1.7.3-1.1_all.deb
libcommoncpp2_1.7.3-1.1.diff.gz
  to main/libc/libcommoncpp2/libcommoncpp2_1.7.3-1.1.diff.gz
libcommoncpp2_1.7.3-1.1.dsc
  to main/libc/libcommoncpp2/libcommoncpp2_1.7.3-1.1.dsc



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 560...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mehdi Dogguy me...@debian.org (supplier of updated libcommoncpp2 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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Feb 2010 15:16:29 +0100
Source: libcommoncpp2
Binary: libcommoncpp2-dev libccgnu2-1.7-0 libcommoncpp2-doc
Architecture: source all i386
Version: 1.7.3-1.1
Distribution: unstable
Urgency: low
Maintainer: Debian VoIP Team pkg-voip-maintain...@lists.alioth.debian.org
Changed-By: Mehdi Dogguy me...@debian.org
Description: 
 libccgnu2-1.7-0 - A GNU package for creating portable C++ programs
 libcommoncpp2-dev - Header files and static libraries for Common C++ 2
 libcommoncpp2-doc - Documentation files for Common C++ 2
Closes: 560463
Changes: 
 libcommoncpp2 (1.7.3-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix FTBFS due to invalid constant string to char* conversion in
 src/cidr.cpp (added const_cast_conversion.dpatch) (Closes: #560463)
Checksums-Sha1: 
 61a786afb2e23ebd11ab0be414d4c19302fa8358 2108 libcommoncpp2_1.7.3-1.1.dsc
 c03ace13d6d94a8aba47f2b6893317b819319867 8639 libcommoncpp2_1.7.3-1.1.diff.gz
 83ac4547e29af62dc57ec59ed8646842baf15f5d 1525442 
libcommoncpp2-doc_1.7.3-1.1_all.deb
 da8b9d466a7368ff07fd5466ca73f4671a630085 373320 
libcommoncpp2-dev_1.7.3-1.1_i386.deb
 ab2c4835d4db9f48ba26a2d6b622ffd86f7f7a5f 249096 

Bug#560644: clxclient: diff for NMU version 3.6.1-1.1

[Jaromír Mikeš]

 Od: Mehdi me...@dogguy.org

 tag 560644 + pending
 thanks
 
 Dear maintainer,
 
 I've prepared an NMU for clxclient (versioned as 3.6.1-1.1) and
 uploaded it to DELAYED/2. Please feel free to tell me if I
 should delay it longer.

Hi,

thank you a lot for your help
Please don't delay it longer

best regards

mira



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

 tags 566584 pending
Bug #566584 [libtokyotyrant-dev] libtokyotyrant-dev: missing dependency on 
libtokyocabinet-dev
Added tag(s) pending.
 tags 566246 pending
Bug #566246 [tokyotyrant] tokyotyrant: unclear package description
Added tag(s) pending.
 tags 566573 confirmed upstream
Bug #566573 [tokyotyrant] tokyotyrant: bad error handling
Added tag(s) upstream and confirmed.

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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#526760: root-tail: Don't display anything at all since X.org update

[Francesco Poli]

On Sat, 30 Jan 2010 12:57:03 + Stephen Gran wrote:

 This one time, at band camp, Francesco Poli said:
[...]
  Stephen, what do you think?
  Should this bug be downgraded to important?
  Could you please help Andreas in solving his problem?
 
 I think that a package that non-deterministically doesn't work probably
 doesn't belong in a stable release.

Wait, who said that the bug shows up non-deterministically?

What I know is that I use root-tail without experiencing any major
issue.
Moreover, I know other people that use root-tail without any big
problem.

On the other hand, I take notice that Andreas reported his problem: he
is apparently experiencing a bug in a given environment (WindowMaker,
etc.), *unless* he has solved his issue in the meanwhile...

I don't see any evidence of non-deterministic behavior in root-tail.
The program seems to work for a number of people, while it does not
seem to work for some other people (at least one), in a different
environment.

This situation does not look like the definition of a severity 'grave'
bug: the bug does not seem to make the package unusable or mostly so.
I would say the severity of this bug is more like 'important' or even
'normal'.

 I unfortunately don't have enough
 knowledge about the X api to make any good guesses as to what the
 problem might be.

I think there are tags for this kind of situation (e.g.: help).

[...]
 If Andreas has any additional information, that would be great

I would be interested in reading an update from Andreas, too.


-- 
 http://www.inventati.org/frx/progs/scripts/pdebuild-hooks.html
 Need some pdebuild hook scripts?
. Francesco Poli .
 GnuPG key fpr == C979 F34B 27CE 5CD8 DC12  31B5 78F4 279B DD6D FCF4


pgpcMpKUbtk8k.pgp
Description: PGP signature

Bug#515283: gtk2 release

[Riccardo Stagni]

Hello Radu and other developers!

Last time I wrote Radu said that a gtk2 version could be released in any
time... I preferred to wait, to see if indi and dslr support would improve,
but now I need that release: currently gcx isn't present in debian
testing, so we risk not having gcx in the next stable (called squeeze).
And I need some time to make the debian upload and test it.

Riccardo


signature.asc
Description: Digital signature

Bug#568327: zoneminder: latest update kills swf streaming

[Len Padilla]

Package: zoneminder
Version: 1.24.2-2+b1
Severity: grave
Justification: renders package unusable



Hello. I just updated zoneminder to 1.24.2-2+b1 and swf streaming no longer
works. I suspect that this is related to the following error message:

/home/htdocs/zoneminder-cgi/nph-zms: symbol av_init_packet, version
LIBAVFORMAT_52 not defined in file libavformat.so.52 with link time
reference, referer: http://zm.local/?view=watchmid=8


-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (990, 'stable'), (300, 'testing'), (200, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages zoneminder depends on:
ii  apache2   2.2.9-10+lenny6Apache HTTP Server metapackage
ii  apache2-mpm-prefo 2.2.9-10+lenny6Apache HTTP Server - traditional n
ii  ffmpeg5:0.5+svn20100126-0.0  audio/video encoder, streaming ser
ii  libapache2-mod-ph 5.2.6.dfsg.1-1+lenny4  server-side, HTML-embedded scripti
pn  libarchive-tar-pe none (no description available)
ii  libarchive-zip-pe 1.18-1 Module for manipulation of ZIP arc
ii  libavcodec52  5:0.5+svn20100126-0.0  library to encode decode multimedi
ii  libavformat52 5:0.5+svn20100126-0.0  ffmpeg file format library
ii  libavutil49   4:0.5+svn20090706-5ffmpeg utility library
ii  libc6 2.7-18lenny2   GNU C Library: Shared libraries
ii  libdate-manip-per 5.54-1 a perl library for manipulating da
ii  libdevice-serialp 1.04-2+b1  emulation of Win32::SerialPort for
ii  libdirac-encoder0 1.0.2-2open and royalty free high quality
ii  libgcc1   1:4.4.2-9  GCC support library
ii  libgnutls26   2.8.5-2the GNU TLS library - runtime libr
ii  libjpeg62 6b-14  The Independent JPEG Group's JPEG 
ii  libmime-lite-perl 3.021-3Perl5 module for convenient genera
ii  libmime-perl  5.427-1transitional dummy package
ii  libmime-tools-per 5.427-1Perl5 modules for MIME-compliant m
ii  libmysqlclient16  5.1.41-3   MySQL database client library
ii  libpcre3  7.8-3  Perl 5 Compatible Regular Expressi
ii  libphp-serializat 0.27-1 Serialize/Deserialize structs in P
ii  libstdc++64.4.2-9The GNU Standard C++ Library v3
ii  libswscale0   5:0.5+svn20100126-0.0  ffmpeg video scaling library
ii  libwww-perl   5.813-1WWW client/server library for Perl
ii  mysql-client  5.0.51a-24+lenny2+spu1 MySQL database client (metapackage
ii  mysql-client-5.0  5.0.51a-24+lenny2+spu1 MySQL database client binaries
ii  mysql-server  5.0.51a-24+lenny2+spu1 MySQL database server (metapackage
ii  mysql-server-5.0  5.0.51a-24+lenny2+spu1 MySQL database server binaries
ii  perl-modules [lib 5.10.0-19lenny2Core Perl modules
ii  php5  5.2.6.dfsg.1-1+lenny4  server-side, HTML-embedded scripti
ii  php5-mysql5.2.6.dfsg.1-1+lenny4  MySQL module for php5
ii  sysklogd [system- 1.5-5  System Logging Daemon
ii  zlib1g1:1.2.3.3.dfsg-12  compression library - runtime

zoneminder recommends no packages.

zoneminder suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568309: starts but displays blank screen responds to ctrl alt f1

[Brice Goglin]

Ben Whyte wrote:
 Section Device
   Identifier  Configured Video Device
   Option  UseFBDev  true
   

Why do you have FBDev here ? It's ignored according to the log.

 [  795.019218] [drm] Setting GART location based on new memory map
 [  795.019224] [drm] Can't use AGP base @0xf000, won't fit
 [  795.019284] [drm] Loading RV670 CP Microcode
 [  795.059544] [drm] Resetting GPU
 [  795.186801] [drm] writeback test failed
 [  807.512112] [drm] Resetting GPU
 [  867.789081] [drm] Module unloaded
   

This might be related to your problem.

By the way, maybe you should try KMS, see
http://bgoglin.livejournal.com/19346.html to enable it.

Brice




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568329: dict installed in wrong dir

[Rene Engelhard]

Package: hunspell-de-med
Version: 20091008-1
Severity: grave
Justification: renders package unusable

Hi,

$ dpkg -L hunspell-de-med
/.
/usr
/usr/share
/usr/share/myspell
/usr/share/myspell/dicts
/usr/share/hunspell
/usr/share/hunspell/dicts
/usr/share/hunspell/dicts/de_med.dic
^^
[...]

This is wrong; the new path is without dicts/ (there was no dicts/
there in #541909 either)

Regards,

Rene

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

Kernel: Linux 2.6.32-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#553534: marked as done (durep: dir-or-file-in-var-www /var/www/durep/bar.png and two others)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2010 23:32:08 +
with message-id e1ncohc-00024d...@ries.debian.org
and subject line Bug#553534: fixed in durep 0.9-2
has caused the Debian Bug report #553534,
regarding durep: dir-or-file-in-var-www /var/www/durep/bar.png and two others
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
553534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: durep
Version: 0.9-1
Severity: serious
User: lintian-ma...@debian.org
Usertags: dir-or-file-in-var-www

Debian packages should not install files under /var/www. This is not
one of the /var directories in the File Hierarchy Standard and is
under the control of the local administrator. Packages should not
assume that it is the document root for a web server; it is very
common for users to change the default document root and packages
should not assume that users will keep any particular setting. 

Packages that want to make files available via an installed web server
should instead put instructions for the local administrator in a
README.Debian file and ideally include configuration fragments for
common web servers such as Apache.

As an exception, packages are permitted to create the /var/www
directory due to its past history as the default document root, but
should at most copy over a default file in postinst for a new install.

Refer to Filesystem Hierarchy Standard (The /var Hierarchy) for
details.

One solution that works is to put configuration files into
/etc/package_name, put static content, if any, into
/usr/{share,lib}/package_name, then create /var/lib/package name
as home for the package, and symlink the files from /etc and /usr/
into the /var/lib/package_name. Then create a simple set of
configuration snippets for popular web servers (for example, files one
may link into /etc/apache2/conf.d) and put them into
/etc/package_name. This way user modifiable files stil live in /etc,
and a simple operation can make the package go live.

Filed as serious, since this is a violation of the FHS (which is part
of policy), and also since a package with these files will currently
get this package rejected. See
  http://lists.debian.org/debian-devel-announce/2009/10/msg4.html
for details. This means the package has been deemed too buggy to be in
Debian.

manoj


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

Kernel: Linux 2.6.31.4-anzu-2 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages durep depends on:
ii  cdebconf [debconf-2.0]0.145  Debian Configuration Management Sy
ii  debconf [debconf-2.0] 1.5.28 Debian configuration management sy
ii  perl  5.10.1-6   Larry Wall's Practical Extraction 

Versions of packages durep recommends:
ii  libmldbm-perl 2.01-3 Store multidimensional hash struct

durep suggests no packages.


---End Message---
---BeginMessage---
Source: durep
Source-Version: 0.9-2

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

durep_0.9-2.diff.gz
  to main/d/durep/durep_0.9-2.diff.gz
durep_0.9-2.dsc
  to main/d/durep/durep_0.9-2.dsc
durep_0.9-2_all.deb
  to main/d/durep/durep_0.9-2_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 553...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mats Erik Andersson mats.anders...@gisladisker.se (supplier of updated durep 
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 ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 03 Feb 2010 17:13:46 +0100
Source: durep
Binary: durep
Architecture: source all
Version: 0.9-2
Distribution: unstable
Urgency: low
Maintainer: Eduard Bloch bl...@debian.org
Changed-By: Mats Erik Andersson mats.anders...@gisladisker.se
Description: 
 durep  - create disk usage reports
Closes: 482061 553534
Changes: 
 durep (0.9-2) unstable; urgency=low
 .
   [Mats Erik Andersson]
 .
   * Migrate 

Bug#567618: error: unknown filesystem.

[Dieter Hametner]

I want to second the last error report.

With grub-pc 1.98~20100128-1
the installation of a new kernel fails because of the error message

/usr/sbin/grub-probe: error: unknown filesystem.

while building the /boot/grub/grub.cfg


Downgrading to grub-common and grub-pc to version 1.98~20100126-1 allowed me 
to install a new kernel.

$ sudo fdisk -l /dev/hda

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x9dc96e9e

   Device Boot  Start End  Blocks   Id  System
/dev/hda1   *   1195815727603+   7  HPFS/NTFS
/dev/hda219592089 1052257+  82  Linux swap / Solaris
/dev/hda32090404815735667+  83  Linux
/dev/hda44049972945632632+   c  W95 FAT32 (LBA)

-- 
Dieter Hametner
mailto: dh+deb...@mittelstation.de



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#526760: root-tail: Don't display anything at all since X.org update

[Stephen Gran]

This one time, at band camp, Francesco Poli said:
 On Sat, 30 Jan 2010 12:57:03 + Stephen Gran wrote:
 
  This one time, at band camp, Francesco Poli said:
 [...]
   Stephen, what do you think?  Should this bug be downgraded to
   important?  Could you please help Andreas in solving his problem?
  
  I think that a package that non-deterministically doesn't work
  probably doesn't belong in a stable release.
 
 Wait, who said that the bug shows up non-deterministically?

The fact that this user sees this behavior and that user doesn't it
sort of the definition?  This isn't the first report I've had, although
it is the only BTS report.  I've also managed to reproduce it once in
enlightenment, and then failed to reproduce it the next time I tried.

 This situation does not look like the definition of a severity 'grave'
 bug: the bug does not seem to make the package unusable or mostly so.
 I would say the severity of this bug is more like 'important' or even
 'normal'.

I am under the impression that there is probably some serious misbehavior
in the package.  It works for some people perfectly fine, but may
accidentally go wrong and kill your kittens.

I think we have different definitions of what should go in a stable
release.  If this was more important than a leaf package of relatively
niche interest, I would of course invest more time and effort in
figuring out what was going wrong.  Since it is just an edge package
with a relatively low popcon score, it seems to me my effort is better
spent elsewhere, and my feeling is that, in the meantime, software that
only sometimes works doesn't belong in a stable release.  If you want to
look after it, you can of course make different decisions about where
your time is best spent and what you want to support through a release
cycle (and what quality of software is useful to release in Debian in
general).

  I unfortunately don't have enough knowledge about the X api to make
  any good guesses as to what the problem might be.
 
 I think there are tags for this kind of situation (e.g.: help).

I believe you're allowed to tag the bug report that way if you want ..

Cheers,
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :sg...@debian.org |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature