date:20100924

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

 severity 512883 grave
Bug #512883 [gphoto2] gphoto2: Silently fails when unable to retreive files 
from camera
Severity set to 'grave' from 'normal'

 stop
Stopping processing here.

Please contact me if you need assistance.
-- 
512883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#596408: Only segmentation faults when called...

2010-09-24 Thread Anthony Callegaro

On Fri, 2010-09-24 at 07:47 +0200, Joerg Platte wrote:
 Hmmm, on my old pentium 4 box it crashes as well. There is no virtualization 
 involved here but the computer has only 1GB of memory. 
 
 Grüße,
 Jörg

Thanks for the additional input. I can confirm this isn't a memory size
issue in openVZ by dynamically resizing the memory :

r...@amy:~# free -m
 total   used   free sharedbuffers
cached
Mem:  2048248   1799  0  0
0
-/+ buffers/cache:248   1799
Swap:0  0  0
r...@amy:~# unattended-upgrades -d --dry-run
Initial blacklisted packages: 
Starting unattended upgrades script
Allowed origins are: [('Debian', 'testing'), ('Debian',
'squeeze-security'), ('Backports.org archive', 'lenny-backports'),
('Personalized-Software', 'squeeze')]
Checking: bzip2 ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: dictionaries-common ([Origin component:'main'
archive:'testing' origin:'Debian' label:'Debian' site:'mir1.ovh.net'
isTrusted:True])
Checking: libbz2-1.0 ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: libncurses5 ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: libncursesw5 ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: linux-libc-dev ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: ncurses-base ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: ncurses-bin ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
pkgs that look like they should be upgraded: bzip2
dictionaries-common
libbz2-1.0
libncurses5
libncursesw5
linux-libc-dev
ncurses-base
ncurses-bin
Fetched 0B in 0s
(0B/s)  

 
Segmentation fault
r...@amy:~# free -m
 total   used   free sharedbuffers
cached
Mem:  4096248   3847  0  0
0
-/+ buffers/cache:248   3847
Swap:0  0  0
r...@amy:~# unattended-upgrades -d --dry-run
Initial blacklisted packages: 
Starting unattended upgrades script
Allowed origins are: [('Debian', 'testing'), ('Debian',
'squeeze-security'), ('Backports.org archive', 'lenny-backports'),
('Personalized-Software', 'squeeze')]
Checking: bzip2 ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: dictionaries-common ([Origin component:'main'
archive:'testing' origin:'Debian' label:'Debian' site:'mir1.ovh.net'
isTrusted:True])
Checking: libbz2-1.0 ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: libncurses5 ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: libncursesw5 ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: linux-libc-dev ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: ncurses-base ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
Checking: ncurses-bin ([Origin component:'main' archive:'testing'
origin:'Debian' label:'Debian' site:'mir1.ovh.net' isTrusted:True])
pkgs that look like they should be upgraded: bzip2
dictionaries-common
libbz2-1.0
libncurses5
libncursesw5
linux-libc-dev
ncurses-base
ncurses-bin
Fetched 0B in 0s
(0B/s)  

 
Segmentation fault

Hope this help
LeTic


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

Bug#597913: [Pkg-libvirt-maintainers] Bug#597913: virt-manager: Unable to connect to local libvirtd

2010-09-24 Thread Guido Günther

Hi Dominik,
On Fri, Sep 24, 2010 at 09:40:36AM +0200, Dominik Schulz wrote:
 Package: virt-manager
 Version: 0.8.4-7
 Severity: grave
 Justification: renders package unusable
 
 virt-manager is unable to connect to a local QEMU/KVM hypervisor.
 libvirtd is running and the user running virt-manager is in the group
 libvirt which is configured in /etc/libvirt/libvirtd.conf.
 
 virt-manager keeps connection forever without issuing an error
 or any success, it just says: localhost (QEMU) - Connecting 
Please check

http://wiki.debian.org/libvirt#Bugreports.2BAC8-Debugging

for the needed information to look into this.
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: tagging 595103

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

 tags 595103 =
Bug #595103 [linux-2.6] framebuffer gone for intel i915 starting 2.6.32-21
Bug #595511 [linux-2.6] linux-image-2.6.32-5-686: Blacklisting KMS for i8xx 
makes xorg intel driver unusable on these chipsets
Bug #595521 [linux-2.6] i915: system locks up when starting X
Removed tag(s) experimental and moreinfo.
Removed tag(s) experimental and moreinfo.
Removed tag(s) experimental and moreinfo.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
595103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#594472: grub-pc: scary messages and very long boot time after upgrade

2010-09-24 Thread Andreas von Heydwolff


On 2010-09-20 14:48, Alexander Kurtz wrote:

Now we are getting somewhere! Here's what I suspect to be the problem:


[etc.]

Alexander, thank you so much: The system behaved exactly in the way you 
had thought it would, and the problem is solved now. I had to map 
/dev/md1 to vg md1_crypt, and then the rest worked as you suggested in 
your last message. Booting with the newly created initramfs behaved as 
expected. I consider the issue as closed.


Cheers, and thanks once more,

Andreas v. Heydwolff




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

Processed: limit source to libv8, tagging 597856

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

 #libv8 (2.2.24-6) unstable; urgency=low
 #
 #  * CVE-2010-3412 (Closes: #597856)
 #Race condition in the console implementation in Google Chrome before
 #6.0.472.59 has unspecified impact and attack vectors.
 #
 limit source libv8
Limiting to bugs with field 'source' containing at least one of 'libv8'
Limit currently set to 'source':'libv8'

 tags 597856 + pending
Bug #597856 [libv8] CVE-2010-3412: memory overrun issue in CPU profiler
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
597856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#597921: cdo: FTBFS: configure: error: Could not link to jasper library! Required for GRIB_API

Source: cdo
Version: 1.4.6.dfsg.1-2
Severity: serious
Justification: FTBFS

Hi Alastair, again.


 m  #   
 #   #   # mmmmmmmmmmmm  
 #mmm#   ##  # #  # #  # 
 ###  m#   m  # 
 #mm  #mm  mm#  mmm  #mm 
  
  
   
## 
  mmm   # mmmmmmmm   #   m 
 ##  #  #  #  ## m  
 #  #   #  #  #  ##   
 #mm  #   #  #mm  #mm  #  m 
   
   


 m   m   mmm   m   m   m mm 
 m m  # #  #   #   #  
  #m#   #   #  #   #   #
  ##m#  mm#   #
  m
  
 
  #  
 mmmmmm   #   m   mmm   mmm  
 # # #  ## m  #  # #  #  # 
 #   #  m#  #  ##m#  #   #  # 
 ##m#  mm#  #mm  #  m  mm#  #m#  #mm 
 #   m  #
  
  
 #   m  
 #mmmmmm   mm#mm   mmmm mm   mmm  
 # #  #  ### #   #   #  # 
 #   #  ###   #   # # 
 ##m#  #mm##m#   # #mm 
  
  
   
   #  # 
 m   m   # mmmmmmmmm#  mmmm mm 
 #   #  # ### # #  # ###  #  # # 
 #   #  #   ###   #  m#  #   ###   #  #   # 
 mm#  ##m#mm  #m#  mm#  #m##  mm#mm  #   #  #m# 
# m  # 
   


Thanks already.

(https://buildd.debian.org/status/package.php?p=cdosuite=unstable)

Mraw,
KiBi.



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

Bug#594472: grub-pc: scary messages and very long boot time after upgrade

2010-09-24 Thread Alexander Kurtz

So after all this was just mdadm bug #583917 combined with the fact that
you used to wrong name (compared to /etc/cryptsetup) when unlocking the
crypto device manually. This of course caused the cryptsetup initramfs
hook to break when recreating the initramfs. As a consequence, your
cryptroot didn't get unlocked during early boot stage. Correct?

Best regards

Alexander Kurtz

PS: You should revert /etc/cryptab to the state it had before all the
debugging (i.e. with UUID=). You should also revert the change you
made to the cryptsetup initramfs hook, for example like this:
   apt-get --reinstall install cryptsetup


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

Bug#597924: python-apipkg: broken Provides (python2.4?)

2010-09-24 Thread Julien Cristau

Package: python-apipkg
Version: 1.0~b6-4
Severity: serious

Package: python-apipkg
Architecture: all
Source: apipkg
Version: 1.0~b6-4
Provides: python2.4-apipkg, python2.5-apipkg
Depends: python-support (= 0.90.0)

The Provides field seems off, since python2.4 is gone and we have 2.6
now by default.

Cheers,
Julien


signature.asc
Description: Digital signature

Processed: found 595103 in 2.6.32-23

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

 found 595103 2.6.32-23
Bug #595103 [linux-2.6] framebuffer gone for intel i915 starting 2.6.32-21
Bug #595511 [linux-2.6] linux-image-2.6.32-5-686: Blacklisting KMS for i8xx 
makes xorg intel driver unusable on these chipsets
Bug #595521 [linux-2.6] i915: system locks up when starting X
There is no source info for the package 'linux-2.6' at version '2.6.32-23' with 
architecture ''
Unable to make a source version for version '2.6.32-23'
Bug Marked as found in versions 2.6.32-23.
Bug Marked as found in versions 2.6.32-23.
Bug Marked as found in versions 2.6.32-23.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
595103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#594472: grub-pc: scary messages and very long boot time after upgrade

2010-09-24 Thread Alexander Kurtz

reassign 594472 mdadm
forcemerge 583917 594472
thanks

Hi Toni,

Everybody else's problems were definitely caused[1][2] by mdadm bug
#583917[3]. Could you try upgrading to mdadm 3.1.4 (has reached squeeze
already), regenerate your initramfs and report whether this solves your
booting problems?

If your system doesn't currently boot at all, please see my former
mail[4] for instructions.

When doing so, please make sure that you use the right names (compared
to /etc/crypttab) when unlocking your crypto devices. Not doing so was
why Andreas could still not boot after upgrading mdadm[5].

Best regards

Alexander Kurtz

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#119
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#199
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583917
[4] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#164
[5] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#204 


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

Processed: Re: grub-pc: scary messages and very long boot time after upgrade

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

 reassign 594472 mdadm
Bug #594472 [grub-pc] grub-pc: scary messages and very long boot time after 
upgrade
Bug reassigned from package 'grub-pc' to 'mdadm'.
Bug No longer marked as found in versions grub2/1.98+20100804-2.
 forcemerge 583917 594472
Bug#583917: mdadm: long delay (6-200 minutes) during boot (root device 
detection) after upgrade on RAID/LVM/LUKS setup
Bug#594472: grub-pc: scary messages and very long boot time after upgrade
Bug#585015: kernel 2.6.34 fails to boot normally with mdadm  3.1.1-1
Bug#590319: udevadm settle timeout with mdadm 3.1.2
Bug#594418: new mdadm version causes high I/O during boot, boot fails, perhaps 
issue with udev rules
Bug#595061: mdadm: at startup, loads of /sys/devices/virtual/block/md0 (123) on 
the console
Forcibly Merged 583917 585015 590319 594418 594472 595061.

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
590319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590319
594472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472
585015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585015
595061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595061
583917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583917
594418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#597933: Non-free files distributed in sdcc

2010-09-24 Thread Philipp Klaus Krause

Package: sdcc
Version: 2.9.0-5
Severity: serious

Since the 2.9.0 release sdcc is in the process of changing the lbrary
license to GPL+LE. The process is mostly complete. While doing so, some
files of unclear license status were found. Rights holders have been
contacted and, with one exception (), agreed to license their files
under GPL+LE.
This exception is Microchip Technology Inc. They insist on a the file
can be used only with authentic Microchip devices condition, which
clearly violates DFSG §6.

The problem affects the pic and pic16 ports only.

All problematic header files live in the include/pic and include/pic16
directories. In the Debian package these are installed into the
/usr/share/sdcc/include/pic and /usr/share/sdcc/include/pic16 directories.
The problematic source files live in the device/pic and device/pic16.

For the upcoming 3.0.0 release we intend to clearly separate the
problematic files from the rest of sdcc.

Philipp



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

Bug#597932: openocd FTBFS on armel and hurd

2010-09-24 Thread Luca Bruno

Package: openocd
Version: 0.4.0-1
Severity: serious

openocd currently fails to build on hurd and armel, and this fact prevented
0.4.0 from entering squeeze till now. See
https://buildd.debian.org/fetch.cgi?pkg=openocd;ver=0.4.0-1;arch=hurd-i386;stamp=1269698459
and
https://buildd.debian.org/fetch.cgi?pkg=openocd;ver=0.4.0-1;arch=armel;stamp=1283718718

As armel is a release architecture, you may consider temporarily removing
ep93xx and at91rm9200 until a proper patch is out, hoping that release team
would let it in and nothing else is broken.

Cheers, Luca



-- 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.34-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages openocd depends on:
ii  dpkg  1.15.8.5   Debian package management system
ii  install-info  4.13a.dfsg.1-5 Manage installed documentation in 
ii  libc6 2.11.2-6   Embedded GNU C Library: Shared lib
ii  libftdi1  0.18-1 Library to control and program the
ii  libusb-0.1-4  2:0.1.12-16userspace USB programming library

openocd recommends no packages.

openocd suggests no packages.



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

Bug#597434: Fixe for courier IMAP_ULIMITD

2010-09-24 Thread Stefan Hornburg (Racke)


On 09/23/2010 06:54 AM, Thomas Goirand wrote:

Hi,

Here's a patch to fix the issue. Do you agree that is the way to fix it,
and would you accept that I NMU this fix, so that it has a chance to get
into Squeeze soon?

Thomas Goirand (zigo)


I'm going to upload fixed packages myself.

Regards
Racke

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




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

Bug#597542: marked as done (gosa-plugin-ldapmanager: fails to mass-create users)

Your message dated Fri, 24 Sep 2010 13:23:16 +0200
with message-id 201009241323.17355.hol...@layer-acht.org
and subject line fixed by new upstream version
has caused the Debian Bug report #597542,
regarding gosa-plugin-ldapmanager: fails to mass-create users
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.)


-- 
597542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: gosa-plugin-ldapmanager
Version: 2.6.10-2
Severity: grave
Justification: renders package unusable

Hi,

as reported and already fixed upstream, the version of
gosa-plugin-ldapmanager currently targeted for squeeze fails to work: 

   https://oss.gonicus.de/labs/gosa/ticket/1015

As probably almost everybody using GOsa will need to import many users, it
would be a real pitty if squeeze ships with GOsa 2.6.10-2 and not with
current upstream version 2.6.11 wich includes the fix.

Best regards,

Andi

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

Kernel: Linux 2.6.32-5-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


---End Message---
---BeginMessage---
version: 2.6.11-1


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

Bug#589701: ofpath is not compatible with non-builtin disk controllers

2010-09-24 Thread Benjamin Cama

Hi Rick,

I am a bit disappointed about how this is ending, but I just realized
you are using an addon Promise card as disk controller. This is not
supported by ofpath, which just handle IDE controllers using the old ATA
stack or true SCSI controllers. In short, it is hardwired for a list of
disk controllers.

Your bug is a bit different from #572869, even if he's also using a SATA
(so, new ATA stack) controller, but this is the Apple provided one, and
yaboot has a special case for it (even if it seems not to work so well
for now).

I don't really know what to do about that. From what I read (#372186),
ofpathname is better for recent controllers using the new ATA stack, and
it's what grub2 is using. Still, it may lack proper handling of old
controllers, even if we can see (again) people willing to bring that
from ofpath, without much result.

Furthermore, since 2.6.34, benh wrote a new driver (macio) for newworld
Macs (I don't know if it supports /all/ machines) that is based on the
new ATA stack, so ofpath will need to support it soon (well, it's for
after squeeze at least), or we'll need to switch to ofpathname (or grub2
alltogether).

Anyway, thanks for your perseverance, but try to be more specific on
your problems next time ;-)

Regards,
benjamin




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

Bug#597940: wrong debconf usage, not respecting users choice

2010-09-24 Thread Daniel Baumann

Package: apt-dater-host
Severity: serious

apt-dater-host uses debconf wrongly, you should use Choices-C instead of
'translating' booleans into 0 and 1.

currently, it's not remembering the users choice and *always* enabling
automated updates after a reconfigure or update, which is a serious bug.

---snip---
r...@bob:~# dpkg-reconfigure -plow -freadline apt-dater-host
Configuring apt-dater-host
--

If you disable this option, you have to acknowledge every upgrade
process for
all hosts. The pro of it would be, that you will be aware of every
action apt
wants to do. The con is, that you have to attach every host on multiple
upgrades
and acknowledge every single host.

Enable automatic upgrades? no


r...@bob:~# debconf-get-selections | grep apt-dater
apt-dater-host  apt-dater-host/assume_yes   boolean false
r...@bob:~# dpkg-reconfigure -pcritical -freadline apt-dater-host
r...@bob:~# debconf-get-selections | grep apt-dater
apt-dater-host  apt-dater-host/assume_yes   boolean 1
r...@bob:~#
---snap---

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  daniel.baum...@panthera-systems.net
Internet:   http://people.panthera-systems.net/~daniel-baumann/



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

Processed: tagging 597410, tagging 579055

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

 tags 597410 + pending
Bug #597410 [qingy] qingy: install-info installed leads to 
/usr/share/info/dir.gz in built package
Bug #579055 [qingy] qingy: Incorrectly ships /usr/share/info/dir.gz file
Added tag(s) pending.
Added tag(s) pending.
 tags 579055 + pending
Bug #579055 [qingy] qingy: Incorrectly ships /usr/share/info/dir.gz file
Bug #597410 [qingy] qingy: install-info installed leads to 
/usr/share/info/dir.gz in built package
Ignoring request to alter tags of bug #579055 to the same tags previously set
Ignoring request to alter tags of bug #597410 to the same tags previously set
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
579055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579055
597410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

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

 found 597940 0.8.4-1
Bug #597940 [apt-dater-host] wrong debconf usage, not respecting users choice
Bug Marked as found in versions apt-dater/0.8.4-1.
 found 597935 0.8.4-1
Bug #597935 [apt-dater] please mention apt-dater-host in package 
long-description
Bug Marked as found in versions apt-dater/0.8.4-1.
 found 597936 0.8.4-1
Bug #597936 [apt-dater-host] please downgrade sudo depends to recommends
Bug Marked as found in versions apt-dater/0.8.4-1.
 found 597938 0.8.4-1
Bug #597938 [apt-dater-host] please downgrade lsb-release depends to recommends
Bug Marked as found in versions apt-dater/0.8.4-1.
 found 597941 0.8.4-1
Bug #597941 [apt-dater] please downgrade screen depends to recommends
Bug Marked as found in versions apt-dater/0.8.4-1.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
597941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#597943: ed: FTBFS on i386 and mipsel: test failure

2010-09-24 Thread Julien Cristau

Source: ed
Version: 1.4-2
Severity: serious
Justification: fails to build from source

https://buildd.debian.org/pkg.cgi?pkg=ed

[...]
 make -j1 check
 make[1]: Entering directory `/build/buildd-ed_1.4-2-i386-4jHjdE/ed-1.4'
 building test scripts for ed...
 testing ed...
 *** Output e1.o of script e1.ed is incorrect ***
 *** Output r3.o of script r3.ed is incorrect ***
 make[1]: *** [check] Error 127

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#596408: Only segmentation faults when called...


Hi,

On 24/09/10 06:47, Joerg Platte wrote:

Am Thursday, 23. September 2010 schrieb Anthony Callegaro:

On Tue, 2010-09-21 at 13:55 +0200, Soeren Sonnenburg wrote:

The only further info I could provide is that this is a virtual
server with relatively little memory (1G)



Hmmm, on my old pentium 4 box it crashes as well. There is no
virtualization involved here but the computer has only 1GB of
memory.


Also I made an amd64 squeeze VE two weeks ago with only 384MB RAM to see
if I could reproduce this.  But unattended-upgrades has been working
correctly for two weeks now.  It's applied updates almost every day.  So
I don't currently suspect either OpenVZ or limited memory to be the
cause of this.

If I summarise the architectures this has been observed on it seems
there's no pattern there either:

* Soeren -- amd64 I think?  or i686 too?
* Anthony -- OpenVZ VE, not sure which architecture
* Jayen -- i686

So far I haven't been able to reproduce this on native amd64, or on an
amd64 OpenVZ VE.


I don't think the line-by-line python trace is needed now;  from the gdb 
and strace outputs (thanks for those) it is clear the problem is within 
the python-apt implementation:



#2  0x080a49a8 in PyString_FromFormat (format=0xba0ba8 %s object:
Status: %i Complete: %i Local: %i IsTrusted: %i FileSize: %lu
DestFile:'%s' DescURI: '%s' ID:%lu ErrorText: '%s') at
../Objects/stringobject.c:357



#3  0x00b87d63 in acquireitem_repr
(Self=apt_pkg.AcquireItem at remote 0x8735bac) at
python/acquire-item.cc:170


It is supposed to return something like this:


apt_pkg.AcquireItem object: Status: 2 Complete: 1 Local: 1
IsTrusted: 1 FileSize: 107354
DestFile:'/var/cache/apt/archives/libgtk-vnc-1.0-0_0.4.1-3_amd64.deb'
DescURI:
'http://cdn.debian.net/debian/pool/main/g/gtk-vnc/libgtk-vnc-1.0-0_0.4.1-3_amd64.deb'
ID:0 ErrorText: ''


Instead, strlen eventually chokes on one of the string parameters it was 
given.  I guess gdb allows to view the stack frame at depth #2 and that 
may help figure out exactly which string[s] are responsible.  But I 
wouldn't know how.


Regards,
--
Steven Chamberlain
ste...@pyro.eu.org



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

Bug#597315: choqok -- ignores twitter OAuth then doesn't supply user/password to API

2010-09-24 Thread Kumar Appaiah

Dear Noah,

On Fri, Sep 24, 2010 at 03:04:28AM -0400, Noah Meyerhans wrote:
 On Sat, Sep 18, 2010 at 10:59:48AM -0500, Kumar Appaiah wrote:
  If kwallet is not enabled, choqok just fails to log in. To reproduce,
  please do this:
  
  Disable KWallet.
  Create Twitter or Identica account. Do OAuth confirmation
  Tweets/dents visible perfectly
  Close Choqok
  Open Choqok, enter password, and it fails.
 
 Hi.  Can you please test the choqok packages from
 http://people.debian.org/~noahm/choqok/ ?
 
 These packages should address the reported problem in two ways:  
 
 1. They Recommend kwalletmanager, so under normal cicumstances, choqok
 will be able to use the wallet to store credentials.
 
 2. They incorporate upstream's change allowing choqok to store
 credentials in its config file in case the wallet is not available.

This seems to be an acceptable solution. I can confirm that your
packages work for me.

Thanks.

Kumar



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

Bug#597434: marked as done (The /etc/courier/imapd IMAP_ULIMITD is too small)

Your message dated Fri, 24 Sep 2010 12:02:22 +
with message-id e1oz6ys-cs...@franck.debian.org
and subject line Bug#597434: fixed in courier 0.65.0-2
has caused the Debian Bug report #597434,
regarding The /etc/courier/imapd IMAP_ULIMITD is too small
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.)


-- 
597434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: courier-imap
Version: 4.8.0-1
Severity: grave

In the file /etc/courier/imapd, there is the following:
IMAP_ULIMITD=65536

While it doesn't seem so problematic under i386, under amd64 arch, each time
I want to setup a server with courier-imap, it refuses to start because the
limit is reached. Simply setting this limit to 132072 fixes it 100% of the
times.

This issue has been annoying me for all the duration of Lenny. PLEASE, have
it fixed in Squeeze, this is really an annoyance.

Thanks a lot,

Thomas Goirand (zigo)

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

Kernel: Linux 2.6.32-4-xen-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/bash


---End Message---
---BeginMessage---
Source: courier
Source-Version: 0.65.0-2

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

courier-base_0.65.0-2_amd64.deb
  to main/c/courier/courier-base_0.65.0-2_amd64.deb
courier-doc_0.65.0-2_all.deb
  to main/c/courier/courier-doc_0.65.0-2_all.deb
courier-faxmail_0.65.0-2_amd64.deb
  to main/c/courier/courier-faxmail_0.65.0-2_amd64.deb
courier-imap-ssl_4.8.0-2_amd64.deb
  to main/c/courier/courier-imap-ssl_4.8.0-2_amd64.deb
courier-imap_4.8.0-2_amd64.deb
  to main/c/courier/courier-imap_4.8.0-2_amd64.deb
courier-ldap_0.65.0-2_amd64.deb
  to main/c/courier/courier-ldap_0.65.0-2_amd64.deb
courier-maildrop_0.65.0-2_amd64.deb
  to main/c/courier/courier-maildrop_0.65.0-2_amd64.deb
courier-mlm_0.65.0-2_amd64.deb
  to main/c/courier/courier-mlm_0.65.0-2_amd64.deb
courier-mta-ssl_0.65.0-2_amd64.deb
  to main/c/courier/courier-mta-ssl_0.65.0-2_amd64.deb
courier-mta_0.65.0-2_amd64.deb
  to main/c/courier/courier-mta_0.65.0-2_amd64.deb
courier-pcp_0.65.0-2_amd64.deb
  to main/c/courier/courier-pcp_0.65.0-2_amd64.deb
courier-pop-ssl_0.65.0-2_amd64.deb
  to main/c/courier/courier-pop-ssl_0.65.0-2_amd64.deb
courier-pop_0.65.0-2_amd64.deb
  to main/c/courier/courier-pop_0.65.0-2_amd64.deb
courier-ssl_0.65.0-2_amd64.deb
  to main/c/courier/courier-ssl_0.65.0-2_amd64.deb
courier-webadmin_0.65.0-2_amd64.deb
  to main/c/courier/courier-webadmin_0.65.0-2_amd64.deb
courier_0.65.0-2.diff.gz
  to main/c/courier/courier_0.65.0-2.diff.gz
courier_0.65.0-2.dsc
  to main/c/courier/courier_0.65.0-2.dsc
sqwebmail_0.65.0-2_amd64.deb
  to main/c/courier/sqwebmail_0.65.0-2_amd64.deb



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

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

Debian distribution maintenance software
pp.
Stefan Hornburg (Racke) ra...@linuxia.de (supplier of updated courier 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: Fri, 24 Sep 2010 13:32:07 +0200
Source: courier
Binary: courier-base courier-maildrop courier-mlm courier-mta courier-faxmail 
courier-webadmin sqwebmail courier-pcp courier-pop courier-imap courier-ldap 
courier-doc courier-ssl courier-mta-ssl courier-pop-ssl courier-imap-ssl
Architecture: source all amd64
Version: 0.65.0-2
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) ra...@linuxia.de
Changed-By: Stefan Hornburg (Racke) ra...@linuxia.de
Description: 
 courier-base - Courier mail server - base system
 courier-doc - Courier mail server - additional documentation
 courier-faxmail - Courier mail server - Fax-mail gateway
 courier-imap - Courier mail server - IMAP server
 courier-imap-ssl - Courier mail server - IMAP over SSL
 courier-ldap - Courier mail server - LDAP support
 courier-maildrop - Courier mail server - mail delivery agent
 courier-mlm - Courier mail server - mailing list manager
 courier-mta - Courier mail server - ESMTP

Bug#597945: fontforge: Bus error on sparc when building lilypond

2010-09-24 Thread Julien Cristau

Package: fontforge
Version: 0.0.20100501-1
Severity: grave
Justification: renders package unusable

https://buildd.debian.org/fetch.cgi?pkg=lilypond;ver=2.12.3-7;arch=sparc;stamp=1284348159

 cd ./out  /usr/bin/fontforge -script emmentaler-11.pe
 Copyright (c) 2000-2010 by George Williams.
  Executable based on sources from 11:21 GMT 1-May-2010.
  Library based on sources from 03:43 GMT 29-Apr-2010.
 Bus error
 make[2]: *** [out/emmentaler-11.otf] Error 138

This indicates unaligned memory access.

There's a segfault on hppa when building that same file.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#596408: Only segmentation faults when called...

2010-09-24 Thread Soeren Sonnenburg

On Fri, 2010-09-24 at 12:56 +0100, Steven Chamberlain wrote:
 Hi,
 
 On 24/09/10 06:47, Joerg Platte wrote:
  Am Thursday, 23. September 2010 schrieb Anthony Callegaro:
  On Tue, 2010-09-21 at 13:55 +0200, Soeren Sonnenburg wrote:
  The only further info I could provide is that this is a virtual
  server with relatively little memory (1G)
 
  Hmmm, on my old pentium 4 box it crashes as well. There is no
  virtualization involved here but the computer has only 1GB of
  memory.
 
 Also I made an amd64 squeeze VE two weeks ago with only 384MB RAM to see
 if I could reproduce this.  But unattended-upgrades has been working
 correctly for two weeks now.  It's applied updates almost every day.  So
 I don't currently suspect either OpenVZ or limited memory to be the
 cause of this.
 
 If I summarise the architectures this has been observed on it seems
 there's no pattern there either:
 
 * Soeren -- amd64 I think?  or i686 too?

$ uname -m
i686

(but it is some quad-xeon it seems - so I think one could rule out
overly optimized x86 code)

Soeren
-- 
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962


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

Bug#597946: hangs when upgrading hosts

2010-09-24 Thread Daniel Baumann

Package: apt-dater
Version: 0.8.4-1
Severity: serious

i have a standard configuration in .config/apt-dater that gets populated
by calling apt-dater for the first time.

then, i've added my hosts in hosts.conf.

my ssh config is correct, apt-dater properly queries successfully the
hosts, lists the required updates etc.

however, when pressing 'u' for actually doing the upgrade, a screen
session gets started and apt-dater hangs.

disabling screen didn't help, see the previous bug report.

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  daniel.baum...@panthera-systems.net
Internet:   http://people.panthera-systems.net/~daniel-baumann/



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

Processed: severity of 596373 is serious

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

 severity 596373 serious
Bug #596373 [varnish] varnish postinst script fails on GNU/kFreeBSD
Severity set to 'serious' from 'important'

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
596373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#595839: verilog-mode: FTBFS in squeeze: Nonexistent build-dependency: 'emacs22'

On Fri, 17 Sep 2010 11:26:47 -0430, Miguel Landaeta wrote:

  During a rebuild of all packages in a squeeze chroot, your package failed
  to build on amd64.
 I could rebuild verilog-mode under a clean squeeze chroot
 with pbuilder. I attached the build log.

pbuilder and sbuild handle dependencies differently. In this case
sbuild falls over emacs22 | emacs21 | emacsen because emacs22
doesn't exist anymore in squeeze, and it always tries only the first
alternative IIRC (to get consistent results).
pbuilder looks at all alternatives, and if you look in your build log
you see that it chooses emacs23 (via the virtual emacsen package).

Cheers,
gregor, who will now add emacs23
 
-- 
 .''`.   http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4
 : :' :  Debian GNU/Linux user, admin,  developer - http://www.debian.org/
 `. `'   Member of VIBE!AT  SPI, fellow of Free Software Foundation Europe
   `-NP: J.J. Cale: Wish I Had Not Said That


signature.asc
Description: Digital signature

Bug#595839: verilog-mode: diff for NMU version 558-1.1

tags 595839 + patch
tags 595839 + pending
thanks

Dear maintainer,

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

Regards.

-- 
 .''`.   http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4
 : :' :  Debian GNU/Linux user, admin,  developer - http://www.debian.org/
 `. `'   Member of VIBE!AT  SPI, fellow of Free Software Foundation Europe
   `-NP: Janis Joplin: Ball And Chain
diff -u verilog-mode-558/debian/changelog verilog-mode-558/debian/changelog
--- verilog-mode-558/debian/changelog
+++ verilog-mode-558/debian/changelog
@@ -1,3 +1,12 @@
+verilog-mode (558-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix FTBFS in squeeze: Nonexistent build-dependency: 'emacs22':
+add emacs23 as first alternative in Build-Depends-Indep and Depends
+(closes: #595839).
+
+ -- gregor herrmann gre...@debian.org  Fri, 24 Sep 2010 14:34:07 +0200
+
 verilog-mode (558-1) unstable; urgency=low
 
   * New upstream release.
diff -u verilog-mode-558/debian/control verilog-mode-558/debian/control
--- verilog-mode-558/debian/control
+++ verilog-mode-558/debian/control
@@ -2,14 +2,14 @@
 Section: editors
 Priority: optional
 Maintainer: NIIBE Yutaka gni...@fsij.org
-Build-Depends-Indep: texinfo, emacs22 | emacs21 | emacsen
+Build-Depends-Indep: texinfo, emacs23 | emacs22 | emacs21 | emacsen
 Build-Depends: debhelper (= 5)
 Standards-Version: 3.8.4
 Homepage: http://www.verilog.com/verilog-mode.html
 
 Package: verilog-mode
 Architecture: all
-Depends: emacs22 | emacs21 | emacsen, ${misc:Depends}
+Depends: emacs23 | emacs22 | emacs21 | emacsen, ${misc:Depends}
 Description: Emacs mode for editing Verilog HDL
  The emacs major mode for editing code of Verilog HDL.
  Supports syntax highlighting, automatic indentation.


signature.asc
Description: Digital signature

Processed: verilog-mode: diff for NMU version 558-1.1

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

 tags 595839 + patch
Bug #595839 [verilog-mode] verilog-mode: FTBFS in squeeze: Nonexistent 
build-dependency: 'emacs22'
Added tag(s) patch.
 tags 595839 + pending
Bug #595839 [verilog-mode] verilog-mode: FTBFS in squeeze: Nonexistent 
build-dependency: 'emacs22'
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
595839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#597947: libspeechd.so.2 should link to libpthread

2010-09-24 Thread Halim Sahin

Package: libspeechd2
Version: 0.7.1-1
Severity: grave
Tags: squeeze experimental


The provided libspeechd version in debian doesn't link against libpthread.
This will force all client apps to link to libpthread even if they are not
multithreaded.

When building same version of libspeechd from it's homepage 
ldd /usr/lib/libspeechd.so.2
shows a libpthread reference.

This should really be fixed because it would break console screenreader
accessibility in squeeze.
Same problem can be found in the newer speech-dispatcher version from
experimental.
I think it's a problem in the debian build scripts of libspeechd2 package.
Thx a lot for your work

Regards
Halim




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

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

Versions of packages libspeechd2 depends on:
ii  libc6 2.11.2-5   Embedded GNU C Library: Shared lib
ii  libglib2.0-0  2.24.2-1   The GLib library of C routines

libspeechd2 recommends no packages.

libspeechd2 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#591207: marked as done (openacs: does not build swf file from source)

Your message dated Fri, 24 Sep 2010 13:02:23 +
with message-id e1oz7ux-0006jy...@franck.debian.org
and subject line Bug#591207: fixed in openacs 5.5.1+dfsg-1
has caused the Debian Bug report #591207,
regarding openacs: does not build swf file from source
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.)


-- 
591207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: openacs
Version: 5.5.1-4
Severity: serious

Hi,

openacs ships a swf file but does not build it from source.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


---End Message---
---BeginMessage---
Source: openacs
Source-Version: 5.5.1+dfsg-1

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

openacs_5.5.1+dfsg-1.diff.gz
  to main/o/openacs/openacs_5.5.1+dfsg-1.diff.gz
openacs_5.5.1+dfsg-1.dsc
  to main/o/openacs/openacs_5.5.1+dfsg-1.dsc
openacs_5.5.1+dfsg-1_all.deb
  to main/o/openacs/openacs_5.5.1+dfsg-1_all.deb
openacs_5.5.1+dfsg.orig.tar.gz
  to main/o/openacs/openacs_5.5.1+dfsg.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 591...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hector Romojaro hromoj...@dia.uned.es (supplier of updated openacs 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, 05 Sep 2010 00:51:43 +0200
Source: openacs
Binary: openacs
Architecture: source all
Version: 5.5.1+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Hector Romojaro hromoj...@dia.uned.es
Changed-By: Hector Romojaro hromoj...@dia.uned.es
Description: 
 openacs- toolkit for building community-oriented web applications
Closes: 591207
Changes: 
 openacs (5.5.1+dfsg-1) unstable; urgency=high
 .
   * Removed non DFSG files, check README.Debian for details. Closes: #591207
   * Success to install even if postgresql is not installed (this is the same
 fix introduced for #591210 in dotlrn).
   * Added info about PostgreSQL dependency to README.Debian.
   * Fixed postinst script that failed to reload postgresql.
Checksums-Sha1: 
 12bb7950889ee3af5d830eaf470d4d002cc78e0b 1249 openacs_5.5.1+dfsg-1.dsc
 650ea2bc3494c1c27e30c09ccfb3e476b85543b1 10002137 
openacs_5.5.1+dfsg.orig.tar.gz
 aa88bbba074572b47640977c6b6aa236367fe803 46341 openacs_5.5.1+dfsg-1.diff.gz
 102f4e51dffc9a41a733a74edc4e23ce7b6647a8 10065006 openacs_5.5.1+dfsg-1_all.deb
Checksums-Sha256: 
 f168a018fe3e914a3769b56cb77b8313d414758515c60047977d5a5cb59b9195 1249 
openacs_5.5.1+dfsg-1.dsc
 97279476b620f0973d6d378c79e8370564af94cd5a56fd329ccc99db8acb2788 10002137 
openacs_5.5.1+dfsg.orig.tar.gz
 4f9a7ccc75d360b1290845f54348f3e4feae386d2bc5e83ab234140fa6706956 46341 
openacs_5.5.1+dfsg-1.diff.gz
 0f6ed795ad7d293e59ded0d37729464a6fff53e72703c216bd647b4fad317606 10065006 
openacs_5.5.1+dfsg-1_all.deb
Files: 
 4d98d9ebf258be2cfe578c4c1b8ba7e6 1249 web optional openacs_5.5.1+dfsg-1.dsc
 e2983e8555489162eb77b11c48edd788 10002137 web optional 
openacs_5.5.1+dfsg.orig.tar.gz
 a40ed4c599e60f765e91694afda1086d 46341 web optional 
openacs_5.5.1+dfsg-1.diff.gz
 e891b787645425ffcb8e448c248d410a 10065006 web optional 
openacs_5.5.1+dfsg-1_all.deb

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

iEYEARECAAYFAkycn7MACgkQpFNRmenyx0cHDQCgp6Ku7vNyS/YTlywB+R4agVVv
nK4An0ryehBEts9vwis24bV6hLbYC4EP
=wz9v
-END PGP SIGNATURE-


---End Message---

Processed: Not fixed.

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

 unarchive 579483
Bug #579483 {Done: Mathieu Trudel mathieu...@gmail.com} [acct] couldn't open 
file '/var/account/pacct': No such file or directory
Unarchived Bug 579483
 reopen 579483
Bug #579483 {Done: Mathieu Trudel mathieu...@gmail.com} [acct] couldn't open 
file '/var/account/pacct': No such file or directory
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
 found 579483
Bug #579483 [acct] couldn't open file '/var/account/pacct': No such file or 
directory
Ignoring request to alter fixed versions of bug #579483 to the same values 
previously set
 severity 579483 serious
Bug #579483 [acct] couldn't open file '/var/account/pacct': No such file or 
directory
Severity set to 'serious' from 'important'

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
579483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: dibbler: diff for NMU version 0.7.3-1.3

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

 tags 574624 + pending
Bug #574624 [dibbler-client] dibbler-client: after removing package with 
dselect impossible to purge it.
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
574624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#574624: dibbler: diff for NMU version 0.7.3-1.3

tags 574624 + pending
thanks

Dear maintainer,

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

Regards.

-- 
 .''`.   http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4
 : :' :  Debian GNU/Linux user, admin,  developer - http://www.debian.org/
 `. `'   Member of VIBE!AT  SPI, fellow of Free Software Foundation Europe
   `-NP: Bloodhound Gang: The Roof
diff -u dibbler-0.7.3/debian/dibbler-client.init dibbler-0.7.3/debian/dibbler-client.init
--- dibbler-0.7.3/debian/dibbler-client.init
+++ dibbler-0.7.3/debian/dibbler-client.init
@@ -45,7 +45,7 @@
 	;;
   stop)
 	echo -n Stopping $DESC: 
-	($DAEMON stop 21  /dev/null; true)
+	($DAEMON stop 21  /dev/null || true)
 	echo $NAME.
 	;;
   status)
@@ -71,7 +71,7 @@
 	#	just the same as restart.
 	#
 	echo -n Restarting $DESC: 
-	($DAEMON stop 21  /dev/null|| true)
+	($DAEMON stop 21  /dev/null || true)
 	sleep 1
 	$DAEMON start 21  /dev/null
 	echo $NAME.
diff -u dibbler-0.7.3/debian/changelog dibbler-0.7.3/debian/changelog
--- dibbler-0.7.3/debian/changelog
+++ dibbler-0.7.3/debian/changelog
@@ -1,3 +1,12 @@
+dibbler (0.7.3-1.3) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix after removing package with dselect impossible to purge it.:
+also return successfully from 'stop'; patch by Chris Butler
+(closes: #574624).
+
+ -- gregor herrmann gre...@debian.org  Fri, 24 Sep 2010 15:12:28 +0200
+
 dibbler (0.7.3-1.2) unstable; urgency=low
 
   * Non-maintainer upload.


signature.asc
Description: Digital signature

Bug#597783: Fwd: Re: Bug#597783: [Pkg-fglrx-devel] Bug#597783: fglrx-source: fails to build with locally built kernel

2010-09-24 Thread Michel Casabona




 Message original 
Sujet: 	Re: Bug#597783: [Pkg-fglrx-devel] Bug#597783: fglrx-source: 
fails to build with locally built kernel

Date :  Thu, 23 Sep 2010 23:29:08 +0200
De :Michel Casabona michel.casab...@free.fr
Pour :  597...@bugs.debian.org



Le 23/09/2010 03:48, Michael Gilbert a écrit :



 do you have a /lib/modules/$(KERNELRELEASE)/build symlink?


Yes, after the kernel package has been installed first
$ ls -l /lib/modules/2.6.32/build
lrwxrwxrwx 1 root root 28  9 janv.  2010 /lib/modules/2.6.32/build -
/usr/src/linux-source-2.6.32


 are your
 sources originally in /usr/src/linux?


No, the sources are in /usr/src/linux-$(KERNELRELEASE)/
The is no symlink to /usr/src/linux.


 would you mind helping me find a
 consistent path to that file?


The variable $(KSRC) should contain the path to the kernel sources
according to /usr/share/doc/kernel-package/README.modules

I've tested that it works with make-kpkg (kernel-package), ie, the value
is /usr/src/linux-source-2.6.32
and also with module-assistant (/lib/modules/2.6.32/source).
Not sure about others build methods (dkms?)

Bug#597947: libspeechd.so.2 should link to libpthread

2010-09-24 Thread Samuel Thibault

found 597947 7.1-1
tags 597947 - experimental
thanks

This is also the case in unstable, marking the version as such.

Halim Sahin, le Fri 24 Sep 2010 14:45:16 +0200, a écrit :
 When building same version of libspeechd from it's homepage 
 ldd /usr/lib/libspeechd.so.2
 shows a libpthread reference.

It looks like there was a mistake in the 0.7-5 upload indeed:
debian/patches/debian-changes-0.7-5 contains

--- speech-dispatcher-0.7.orig/src/c/api/Makefile.am
+++ speech-dispatcher-0.7/src/c/api/Makefile.am
-libspeechd_la_LDFLAGS = -version-info 
@LIB_SPD_CURRENT@:@LIB_SPD_REVISION@:@LIB_SPD_AGE@ -lpthread
+libspeechd_la_LDFLAGS = -version-info 
@LIB_SPD_CURRENT@:@LIB_SPD_REVISION@:@LIB_SPD_AGE@

which shouldn't be there.

Samuel



-- 
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#597947: libspeechd.so.2 should link to libpthread

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

 found 597947 7.1-1
Bug #597947 [libspeechd2] libspeechd.so.2 should link to libpthread
There is no source info for the package 'libspeechd2' at version '7.1-1' with 
architecture ''
Unable to make a source version for version '7.1-1'
Bug Marked as found in versions 7.1-1.
 tags 597947 - experimental
Bug #597947 [libspeechd2] libspeechd.so.2 should link to libpthread
Removed tag(s) experimental.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
597947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#589582: [pkg-eucalyptus-maintainers] Bug#589582: Bug #589582 eucalyptus: FTBFS with upcoming Hibernate 3.5

On Thu, 29 Jul 2010 13:35:35 +0900, Charles Plessy wrote:

 no news. Given that Eucalyptus in Debian is still in a testing phase, I 
 propose
 to go ahead and upload the patched package, so that more people can test if it
 works well.

With or without the patch, eucalyptus FTBFS in a sid cowbuilder
chroot (i386) with:

ANT_OPTS=-Xmx512m /usr/bin/ant -e build
Buildfile: /tmp/buildd/eucalyptus-1.6.2/clc/build.xml

deps:

download-deps:

untar:

build-msgs:

init:
Created dir: /tmp/buildd/eucalyptus-1.6.2/clc/modules/msgs/build
Created dir: /tmp/buildd/eucalyptus-1.6.2/clc/target

builder:
builder.target=build-jibx

build-jibx:

build-groovy:

BUILD FAILED
/tmp/buildd/eucalyptus-1.6.2/clc/build.xml:88: The following error occurred 
while executing this line:
/tmp/buildd/eucalyptus-1.6.2/clc/modules/module-inc.xml:132: The following 
error occurred while executing this line:
/tmp/buildd/eucalyptus-1.6.2/clc/modules/msgs/build.xml:84: The following error 
occurred while executing this line:
/tmp/buildd/eucalyptus-1.6.2/clc/modules/module-inc.xml:147: taskdef class 
org.codehaus.groovy.ant.Groovyc cannot be found
 using the classloader AntClassLoader[...]

Cheers,
gregor
 
-- 
 .''`.   http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4
 : :' :  Debian GNU/Linux user, admin,  developer - http://www.debian.org/
 `. `'   Member of VIBE!AT  SPI, fellow of Free Software Foundation Europe
   `-NP: Dire Straits: Water Of Love


signature.asc
Description: Digital signature

Bug#589582: [pkg-eucalyptus-maintainers] Bug#589582: Bug#589582: Bug #589582 eucalyptus: FTBFS with upcoming Hibernate 3.5

2010-09-24 Thread Steffen Möller

It also needs the hibernate v 3.3 packages.  Ping me if you want to try
again, I'll place them on an apt repository for you.

Best,
Steffen

On 09/24/2010 03:41 PM, gregor herrmann wrote:
 On Thu, 29 Jul 2010 13:35:35 +0900, Charles Plessy wrote:

   
 no news. Given that Eucalyptus in Debian is still in a testing phase, I 
 propose
 to go ahead and upload the patched package, so that more people can test if 
 it
 works well.
 
 With or without the patch, eucalyptus FTBFS in a sid cowbuilder
 chroot (i386) with:

 ANT_OPTS=-Xmx512m /usr/bin/ant -e build
 Buildfile: /tmp/buildd/eucalyptus-1.6.2/clc/build.xml

 deps:

 download-deps:

 untar:

 build-msgs:

 init:
 Created dir: /tmp/buildd/eucalyptus-1.6.2/clc/modules/msgs/build
 Created dir: /tmp/buildd/eucalyptus-1.6.2/clc/target

 builder:
 builder.target=build-jibx

 build-jibx:

 build-groovy:

 BUILD FAILED
 /tmp/buildd/eucalyptus-1.6.2/clc/build.xml:88: The following error occurred 
 while executing this line:
 /tmp/buildd/eucalyptus-1.6.2/clc/modules/module-inc.xml:132: The following 
 error occurred while executing this line:
 /tmp/buildd/eucalyptus-1.6.2/clc/modules/msgs/build.xml:84: The following 
 error occurred while executing this line:
 /tmp/buildd/eucalyptus-1.6.2/clc/modules/module-inc.xml:147: taskdef class 
 org.codehaus.groovy.ant.Groovyc cannot be found
  using the classloader AntClassLoader[...]

 Cheers,
 gregor
  
   


 ___
 pkg-eucalyptus-maintainers mailing list
 pkg-eucalyptus-maintain...@lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/pkg-eucalyptus-maintainers

Bug#589582: [pkg-eucalyptus-maintainers] Bug#589582: Bug#589582: Bug #589582 eucalyptus: FTBFS with upcoming Hibernate 3.5

2010-09-24 Thread Charles Plessy

Le Fri, Sep 24, 2010 at 03:41:11PM +0200, gregor herrmann a écrit :

BUILD FAILED
/tmp/buildd/eucalyptus-1.6.2/clc/build.xml:88: The following error occurred
while executing this line:
/tmp/buildd/eucalyptus-1.6.2/clc/modules/module-inc.xml:132: The following
error occurred while executing this line:
/tmp/buildd/eucalyptus-1.6.2/clc/modules/msgs/build.xml:84: The following
error occurred while executing this line:
/tmp/buildd/eucalyptus-1.6.2/clc/modules/module-inc.xml:147: taskdef class
org.codehaus.groovy.ant.Groovyc cannot be found
using the classloader AntClassLoader[...]

Hi Gregor,

thank you for the report.

We briefly discussed this problem on the pkg-eucalyptus-maintainers list:

http://lists.alioth.debian.org/pipermail/pkg-eucalyptus-maintainers/2010-August/000114.html

and then in http://bugs.debian.org/593050

But before investing hard work in eucalyptus 1.6.2, we need to consider to
upgrade on 2.0.0 instead. Version 1.6.2 will probably not be supported
throurough the live of Squeeze anyway. The problem of course is that I am not
sure if the upgrade to 2.0.0 can be done in time.

I have not asked for Testing removal because I did not yet discuss this with
the other maintainers, and because the latest release update (September 3rd)
suggested to me that it would be automatic: “Leaf packages with open RC bugs
will be removed in the coming weeks”. But if it is helpful, I can open a
request for removal on the BTS.

I hope that this open RC but has not wasted your time. If your motivation was
more on Eucalyptus itself, I am sure that you are most welcome to join us and
work on the 2.0.0 packages, or 1.6.2 if you prefer.

Cheers,

--
Charles Plessy
Tsurumi, Kanagawa, Japan

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

Bug#589582: [pkg-eucalyptus-maintainers] Bug#589582: Bug#589582: Bug #589582 eucalyptus: FTBFS with upcoming Hibernate 3.5

On Fri, 24 Sep 2010 23:06:19 +0900, Charles Plessy wrote:

  BUILD FAILED
  /tmp/buildd/eucalyptus-1.6.2/clc/build.xml:88: The following error occurred 
  while executing this line:
  /tmp/buildd/eucalyptus-1.6.2/clc/modules/module-inc.xml:132: The following 
  error occurred while executing this line:
  /tmp/buildd/eucalyptus-1.6.2/clc/modules/msgs/build.xml:84: The following 
  error occurred while executing this line:
  /tmp/buildd/eucalyptus-1.6.2/clc/modules/module-inc.xml:147: taskdef class 
  org.codehaus.groovy.ant.Groovyc cannot be found
   using the classloader AntClassLoader[...]
 
 We briefly discussed this problem on the pkg-eucalyptus-maintainers list:
 http://lists.alioth.debian.org/pipermail/pkg-eucalyptus-maintainers/2010-August/000114.html
 and then in http://bugs.debian.org/593050

I see, thanks for the pointers.
 
 I have not asked for Testing removal because I did not yet discuss this with
 the other maintainers, and because the latest release update (September 3rd)
 suggested to me that it would be automatic: “Leaf packages with open RC bugs
 will be removed in the coming weeks”. But if it is helpful, I can open a
 request for removal on the BTS.

Sounds like a good idea from an outsider's point of view.
 
 I hope that this open RC but has not wasted your time. 

No big deal :)

 If your motivation was
 more on Eucalyptus itself, I am sure that you are most welcome to join us and
 work on the 2.0.0 packages, or 1.6.2 if you prefer.

I was only looking at RC bugs, sorry for not offering any
additional help :)


Cheers,
gregor
 
-- 
 .''`.   http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4
 : :' :  Debian GNU/Linux user, admin,  developer - http://www.debian.org/
 `. `'   Member of VIBE!AT  SPI, fellow of Free Software Foundation Europe
   `-NP: Queen: Don't Lose Your Head


signature.asc
Description: Digital signature

Bug#596408: Only segmentation faults when called...

2010-09-24 Thread Anthony Callegaro

On Fri, 2010-09-24 at 12:56 +0100, Steven Chamberlain wrote:
 Also I made an amd64 squeeze VE two weeks ago with only 384MB RAM to see
 if I could reproduce this.  But unattended-upgrades has been working
 correctly for two weeks now.  It's applied updates almost every day.  So
 I don't currently suspect either OpenVZ or limited memory to be the
 cause of this.
 
 If I summarise the architectures this has been observed on it seems
 there's no pattern there either:
 
 * Soeren -- amd64 I think?  or i686 too?
 * Anthony -- OpenVZ VE, not sure which architecture
 * Jayen -- i686
 
 So far I haven't been able to reproduce this on native amd64, or on an
 amd64 OpenVZ VE.

Ok So I did some test and I can confirm that only the i386 version is
segfaulting. All hosts are running a 2.6.24 amd64 kernel. I created the
exact same guest twice (once with squeeze i386 and once with the squeeze
amd64 template) and it only segfault with the i386 version.

Can you try a 32 bits version or do you want me to give you a SSH access
to one test VZ ?

LeTic




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

Bug#597856: marked as done (CVE-2010-3412: memory overrun issue in CPU profiler)

Your message dated Fri, 24 Sep 2010 14:32:46 +
with message-id e1oz9kq-0006vg...@franck.debian.org
and subject line Bug#597856: fixed in libv8 2.2.24-6
has caused the Debian Bug report #597856,
regarding CVE-2010-3412: memory overrun issue in CPU profiler
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.)


-- 
597856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libv8
Severity: serious
Tags: security patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,
the following CVE (Common Vulnerabilities  Exposures) id was
published for libv8.

CVE-2010-3412[0]:
| Race condition in the console implementation in Google Chrome before
| 6.0.472.59 has unspecified impact and attack vectors.

Patch: http://code.google.com/p/v8/source/detail?r=5393

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

For further information see:

[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3412
http://security-tracker.debian.org/tracker/CVE-2010-3412


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

iEYEARECAAYFAkybfD0ACgkQNxpp46476arGqACfcGq98JaVWh6zMTxQG2Uqt8Rc
PjsAn3qbWZlOVz/QwESYUpD/fUd2/RWX
=Bgvv
-END PGP SIGNATURE-


---End Message---
---BeginMessage---
Source: libv8
Source-Version: 2.2.24-6

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

libv8-2.2.24_2.2.24-6_i386.deb
  to main/libv/libv8/libv8-2.2.24_2.2.24-6_i386.deb
libv8-dbg_2.2.24-6_i386.deb
  to main/libv/libv8/libv8-dbg_2.2.24-6_i386.deb
libv8-dev_2.2.24-6_i386.deb
  to main/libv/libv8/libv8-dev_2.2.24-6_i386.deb
libv8_2.2.24-6.debian.tar.gz
  to main/libv/libv8/libv8_2.2.24-6.debian.tar.gz
libv8_2.2.24-6.dsc
  to main/libv/libv8/libv8_2.2.24-6.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 597...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal kapo...@melix.org (supplier of updated libv8 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: Fri, 24 Sep 2010 11:44:57 +0200
Source: libv8
Binary: libv8-dev libv8-2.2.24 libv8-dbg
Architecture: source i386
Version: 2.2.24-6
Distribution: unstable
Urgency: low
Maintainer: Antonio Radici anto...@dyne.org
Changed-By: Jérémy Lal kapo...@melix.org
Description: 
 libv8-2.2.24 - V8 JavaScript Engine
 libv8-dbg  - Development symbols for the V8 JavaScript Engine
 libv8-dev  - Development files for the V8 JavaScript Engine
Closes: 597856
Changes: 
 libv8 (2.2.24-6) unstable; urgency=low
 .
   * CVE-2010-3412 (Closes: #597856)
 Race condition in the console implementation in Google Chrome before
 6.0.472.59 has unspecified impact and attack vectors.
Checksums-Sha1: 
 7cc1d8a418817edcc5d751b8786d9d61c58b3d97 1272 libv8_2.2.24-6.dsc
 3ac3cf2d39c90991bc5f5857470a9c81509825cc 9681 libv8_2.2.24-6.debian.tar.gz
 6146a611c39bf5b5bd654784b9835dca691082f5 56132 libv8-dev_2.2.24-6_i386.deb
 1885c48b576c23d48ad8dd152387328d39c999f6 1013990 libv8-2.2.24_2.2.24-6_i386.deb
 03f4cd57af446aed4a0972c5a8ed93d0e9b5b94e 10951480 libv8-dbg_2.2.24-6_i386.deb
Checksums-Sha256: 
 c9ecadeb371339a69f092db994be10d9b31d624b56fa5cba048cf8cf292ca75f 1272 
libv8_2.2.24-6.dsc
 bf2b0ed96446211d34ce7e0e4859c1aeca38402182afe6de533168175851da2f 9681 
libv8_2.2.24-6.debian.tar.gz
 2c5c8f7ecaf8c8bbb24c784db5b927ee0ad436ce4ca25a2f913760085255b4a2 56132 
libv8-dev_2.2.24-6_i386.deb
 b542e58ca75eec1729a0bd61143a26d732c46f7e45f6863e73fece43f16fc441 1013990 
libv8-2.2.24_2.2.24-6_i386.deb
 2175369bdea35da2e84da9d8bd419808a7fbcbef15340a5dabfa572ee44ca2de 10951480 
libv8-dbg_2.2.24-6_i386.deb
Files: 
 c38286d6c3374fb064322332a9090537 1272 libs optional libv8_2.2.24-6.dsc
 2080aa02ad8a3f9097d45a25aad7dd27 9681 libs optional 
libv8_2.2.24-6.debian.tar.gz
 9523e467ad3498f19fd2df8683f48b13 56132 libdevel optional 
libv8-dev_2.2.24-6_i386.deb
 a479a424a9750b955cdcd03bd5bd09d5 1013990 libs optional 
libv8-2.2.24_2.2.24-6_i386.deb
 3f96f0de7f84767d84d7850bd4ff4d16 10951480 debug extra 
libv8-dbg_2.2.24-6_i386.deb

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

Bug#597921: marked as done (cdo: FTBFS: configure: error: Could not link to jasper library! Required for GRIB_API)

Your message dated Fri, 24 Sep 2010 14:32:16 +
with message-id e1oz9jw-0006n0...@franck.debian.org
and subject line Bug#597921: fixed in cdo 1.4.6.dfsg.1-3
has caused the Debian Bug report #597921,
regarding cdo: FTBFS: configure: error: Could not link to jasper library! 
Required for GRIB_API
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.)


-- 
597921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: cdo
Version: 1.4.6.dfsg.1-2
Severity: serious
Justification: FTBFS

Hi Alastair, again.


 m  #   
 #   #   # mmmmmmmmmmmm  
 #mmm#   ##  # #  # #  # 
 ###  m#   m  # 
 #mm  #mm  mm#  mmm  #mm 
  
  
   
## 
  mmm   # mmmmmmmm   #   m 
 ##  #  #  #  ## m  
 #  #   #  #  #  ##   
 #mm  #   #  #mm  #mm  #  m 
   
   


 m   m   mmm   m   m   m mm 
 m m  # #  #   #   #  
  #m#   #   #  #   #   #
  ##m#  mm#   #
  m
  
 
  #  
 mmmmmm   #   m   mmm   mmm  
 # # #  ## m  #  # #  #  # 
 #   #  m#  #  ##m#  #   #  # 
 ##m#  mm#  #mm  #  m  mm#  #m#  #mm 
 #   m  #
  
  
 #   m  
 #mmmmmm   mm#mm   mmmm mm   mmm  
 # #  #  ### #   #   #  # 
 #   #  ###   #   # # 
 ##m#  #mm##m#   # #mm 
  
  
   
   #  # 
 m   m   # mmmmmmmmm#  mmmm mm 
 #   #  # ### # #  # ###  #  # # 
 #   #  #   ###   #  m#  #   ###   #  #   # 
 mm#  ##m#mm  #m#  mm#  #m##  mm#mm  #   #  #m# 
# m  # 
   


Thanks already.

(https://buildd.debian.org/status/package.php?p=cdosuite=unstable)

Mraw,
KiBi.


---End Message---
---BeginMessage---
Source: cdo
Source-Version: 1.4.6.dfsg.1-3

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

cdo_1.4.6.dfsg.1-3.debian.tar.gz
  to main/c/cdo/cdo_1.4.6.dfsg.1-3.debian.tar.gz
cdo_1.4.6.dfsg.1-3.dsc
  to main/c/cdo/cdo_1.4.6.dfsg.1-3.dsc
cdo_1.4.6.dfsg.1-3_i386.deb
  to main/c/cdo/cdo_1.4.6.dfsg.1-3_i386.deb



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

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

Debian distribution maintenance software
pp.
Alastair McKinstry mckins...@debian.org (supplier of updated cdo 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: Fri, 24 Sep 2010 04:02:29 +0100
Source: cdo
Binary: cdo
Architecture: source i386
Version: 1.4.6.dfsg.1-3
Distribution: unstable
Urgency: low
Maintainer: Alastair McKinstry mckins...@debian.org
Changed-By: Alastair McKinstry mckins...@debian.org
Description: 
 cdo- Climate Data Operators
Closes: 597921
Changes: 
 cdo (1.4.6.dfsg.1-3) unstable; urgency=low
 .
   * grib-api dependency now requires libjasper to build. Closes: #597921.
Checksums-Sha1: 
 b0702c8fc29da4f3289790937967912818312fe8 1231 cdo_1.4.6.dfsg.1-3.dsc
 2c78d9205a7d64896e50706ac7c9fddf40cfa008 145391 
cdo_1.4.6.dfsg.1-3.debian.tar.gz
 332f4948c24fda25b52b497f1c72be06e7852b03 1285674 cdo_1.4.6.dfsg.1-3_i386.deb
Checksums-Sha256: 
 a16e117d6215298c1715fc09930670794df020e7b065b65e9bbe97985fbee898 1231 
cdo_1.4.6.dfsg.1-3.dsc
 7f325d48176ba8f63726dd28194703ebba2d049a3e5253c7bbbc5d076b5bfecd 145391

Processed: severity of 595018 is serious

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

 severity 595018 serious
Bug #595018 [pdns-backend-mysql] pdns-backend-mysql: dependecy loop in init.d 
script (insserv)
Severity set to 'serious' from 'normal'

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
595018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Processed: tagging 597947

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

 tags 597947 - squeeze
Bug #597947 [libspeechd2] libspeechd.so.2 should link to libpthread
Removed tag(s) squeeze.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
597947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#595018: marked as done (pdns-backend-mysql: dependecy loop in init.d script (insserv))

Your message dated Fri, 24 Sep 2010 15:02:13 +
with message-id e1oz9mv-0001kk...@franck.debian.org
and subject line Bug#595018: fixed in pdns 2.9.22-8
has caused the Debian Bug report #595018,
regarding pdns-backend-mysql: dependecy loop in init.d script (insserv)
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.)


-- 
595018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: pdns-backend-mysql
Version: 2.9.22-7
Severity: normal

The init script requires mysql-server to start before pdns.
mysql-server requies $named (- pdns) to start before mysql.
- loop

removing the requirement mysql starting before pdns solves the issue.

Greetings

tilo



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

Kernel: Linux 2.6.29-2-amd64 (SMP w/8 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 pdns-backend-mysql depends on:
ii  libc6   2.11.2-2 Embedded GNU C Library: Shared lib
ii  libgcc1 1:4.4.4-11   GCC support library
ii  libmysqlclient165.1.49-1 MySQL database client library
ii  libstdc++6  4.4.4-11 The GNU Standard C++ Library v3
ii  pdns-server 2.9.22-7 extremely powerful and versatile n
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

pdns-backend-mysql recommends no packages.

pdns-backend-mysql suggests no packages.

-- no debconf information


---End Message---
---BeginMessage---
Source: pdns
Source-Version: 2.9.22-8

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

pdns-backend-geo_2.9.22-8_amd64.deb
  to main/p/pdns/pdns-backend-geo_2.9.22-8_amd64.deb
pdns-backend-ldap_2.9.22-8_amd64.deb
  to main/p/pdns/pdns-backend-ldap_2.9.22-8_amd64.deb
pdns-backend-mysql_2.9.22-8_amd64.deb
  to main/p/pdns/pdns-backend-mysql_2.9.22-8_amd64.deb
pdns-backend-pgsql_2.9.22-8_amd64.deb
  to main/p/pdns/pdns-backend-pgsql_2.9.22-8_amd64.deb
pdns-backend-pipe_2.9.22-8_amd64.deb
  to main/p/pdns/pdns-backend-pipe_2.9.22-8_amd64.deb
pdns-backend-sqlite3_2.9.22-8_amd64.deb
  to main/p/pdns/pdns-backend-sqlite3_2.9.22-8_amd64.deb
pdns-backend-sqlite_2.9.22-8_amd64.deb
  to main/p/pdns/pdns-backend-sqlite_2.9.22-8_amd64.deb
pdns-doc_2.9.22-8_all.deb
  to main/p/pdns/pdns-doc_2.9.22-8_all.deb
pdns-server_2.9.22-8_amd64.deb
  to main/p/pdns/pdns-server_2.9.22-8_amd64.deb
pdns_2.9.22-8.debian.tar.gz
  to main/p/pdns/pdns_2.9.22-8.debian.tar.gz
pdns_2.9.22-8.dsc
  to main/p/pdns/pdns_2.9.22-8.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 595...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthijs Mohlmann matth...@cacholong.nl (supplier of updated pdns 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: Fri, 24 Sep 2010 16:24:04 +0200
Source: pdns
Binary: pdns-server pdns-doc pdns-backend-pipe pdns-backend-ldap 
pdns-backend-geo pdns-backend-mysql pdns-backend-pgsql pdns-backend-sqlite 
pdns-backend-sqlite3
Architecture: source all amd64
Version: 2.9.22-8
Distribution: unstable
Urgency: high
Maintainer: Matthijs Mohlmann matth...@cacholong.nl
Changed-By: Matthijs Mohlmann matth...@cacholong.nl
Description: 
 pdns-backend-geo - geo backend for PowerDNS
 pdns-backend-ldap - LDAP backend for PowerDNS
 pdns-backend-mysql - generic MySQL backend for PowerDNS
 pdns-backend-pgsql - generic PostgreSQL backend for PowerDNS
 pdns-backend-pipe - pipe/coprocess backend for PowerDNS
 pdns-backend-sqlite - sqlite backend for PowerDNS
 pdns-backend-sqlite3 - sqlite backend for PowerDNS
 pdns-doc   - PowerDNS manual
 pdns-server - extremely powerful and versatile nameserver
Closes: 595018
Changes: 
 pdns (2.9.22-8) unstable; urgency=high
 .
   * Update init.d scripts and remove mysql and postgresql from the
 dependencies. The loop between mysql and pdns causes apt to fail hence
 the urgency high. (Closes: #595018)
Checksums-Sha1:

Bug#595499: marked as done (fails to install)

Your message dated Fri, 24 Sep 2010 15:17:47 +
with message-id e1oza1z-0002y6...@franck.debian.org
and subject line Bug#595499: fixed in dotlrn 2.5.0+dfsg-1
has caused the Debian Bug report #595499,
regarding fails to install
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.)


-- 
595499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: dotlrn
Version: 2.5.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts piuparts.d.o

Hi, 

during a test with piuparts I noticed your package failed to install. As per 
definition of the release team this makes the package too buggy for a 
release, thus the severity.

From the attached log (scroll to the bottom...):

0m49.7s ERROR: Command failed (status=100): 
['chroot', '/org/piuparts.debian.org/tmp/tmpmSccD5', 'apt-get', '-y', 
'install', 'dotlrn']
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Suggested packages:
postgresql daemontools daemontools-run
  The following NEW packages will be installed:
dotlrn
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 26.1MB of archives.
  After this operation, 108MB of additional disk space will be used.
  Get:1 http://piatti.debian.org squeeze/main dotlrn 2.5.0-4 [26.1MB]
  debconf: delaying package configuration, since apt-utils is not installed
  Fetched 26.1MB in 0s (26.5MB/s)
  Selecting previously deselected package dotlrn.
  (Reading database ... 9198 files and directories currently installed.)
  Unpacking dotlrn (from .../dotlrn_2.5.0-4_all.deb) ...
  Setting up dotlrn (2.5.0-4) ...
  psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket /var/run/postgresql/.s.PGSQL.5432?
  dpkg: error processing dotlrn (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   dotlrn
  E: Sub-process /usr/bin/dpkg returned an error code (1)


cheers,
Holger
Start: 2010-06-21 06:26:05 UTC

Package: dotlrn
Priority: optional
Section: web
Installed-Size: 105830
Maintainer: Hector Romojaro hromoj...@dia.uned.es
Architecture: all
Version: 2.5.0-4
Depends: debconf (= 0.5) | debconf-2.0, aolserver4-daemon (= 4.5.1-11), aolserver4-nspostgres, aolserver4-nssha1, postgresql-client, adduser, tclthread (= 1:2.6.5-3), tcllib, tcl (= 8.4), wwwconfig-common, debconf, xotcl, aolserver4-xotcl, imagemagick, zip, unzip, tdom (= 0.8.3~20080525)
Suggests: postgresql, daemontools, daemontools-run
Filename: pool/main/d/dotlrn/dotlrn_2.5.0-4_all.deb
Size: 26143266
MD5sum: 302d7e53c44910ee0fbbbe2b4f0f40ed
SHA1: 02252a1ea9cc59b17325f29c4f785b679ac740e1
SHA256: 7b3b543c22698f6ce7f8f9566a2025e2e81c21fc455a3c14f2c078ab8a9b4faf
Description: e-learning portal system based on OpenACS
 dotLRN is a complete Learning Management System that integrates course
 and content administration tools and collaborative tools into a
 sophisticated portal system.
Homepage: http://www.dotlrn.org/

Executing: sudo /org/piuparts.debian.org/sbin/piuparts --warn-symlinks --warn-on-others --warn-on-leftovers-after-purge --skip-logrotatefiles-test --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad squeeze -b squeeze.tar.gz --mirror http://piatti.debian.org/debian/ dotlrn
Guessed: debian
0m0.0s INFO: --
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: --
0m0.0s INFO: piuparts version 0.39~201005220948 starting up.
0m0.0s INFO: Command line arguments: /org/piuparts.debian.org/sbin/piuparts --warn-symlinks --warn-on-others --warn-on-leftovers-after-purge --skip-logrotatefiles-test --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad squeeze -b squeeze.tar.gz --mirror http://piatti.debian.org/debian/ dotlrn
0m0.0s INFO: Running on: Linux piatti 2.6.32.14-dsa-amd64 #1 SMP Thu May 27 15:09:09 CEST 2010 x86_64
0m0.0s DEBUG: Created temporary directory /org/piuparts.debian.org/tmp/tmpmSccD5
0m0.0s DEBUG: Unpacking squeeze.tar.gz into /org/piuparts.debian.org/tmp/tmpmSccD5
0m0.0s DEBUG: Starting command: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmpmSccD5', '-zxf', 'squeeze.tar.gz']
0m1.8s DEBUG: Command ok: ['tar',

Bug#591210: marked as done (dotlrn: does not build swf file from source)

Your message dated Fri, 24 Sep 2010 15:17:47 +
with message-id e1oza1z-0002y0...@franck.debian.org
and subject line Bug#591210: fixed in dotlrn 2.5.0+dfsg-1
has caused the Debian Bug report #591210,
regarding dotlrn: does not build swf file from source
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.)


-- 
591210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: dotlrn
Version: 2.5.0-4
Severiy: serious

Hi,

dotlrn ships a swf file but does not build it from source.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


---End Message---
---BeginMessage---
Source: dotlrn
Source-Version: 2.5.0+dfsg-1

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

dotlrn_2.5.0+dfsg-1.diff.gz
  to main/d/dotlrn/dotlrn_2.5.0+dfsg-1.diff.gz
dotlrn_2.5.0+dfsg-1.dsc
  to main/d/dotlrn/dotlrn_2.5.0+dfsg-1.dsc
dotlrn_2.5.0+dfsg-1_all.deb
  to main/d/dotlrn/dotlrn_2.5.0+dfsg-1_all.deb
dotlrn_2.5.0+dfsg.orig.tar.gz
  to main/d/dotlrn/dotlrn_2.5.0+dfsg.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 591...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hector Romojaro hromoj...@dia.uned.es (supplier of updated dotlrn 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, 05 Sep 2010 01:24:37 +0200
Source: dotlrn
Binary: dotlrn
Architecture: source all
Version: 2.5.0+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Hector Romojaro hromoj...@dia.uned.es
Changed-By: Hector Romojaro hromoj...@dia.uned.es
Description: 
 dotlrn - e-learning portal system based on OpenACS
Closes: 591210 595499
Changes: 
 dotlrn (2.5.0+dfsg-1) unstable; urgency=high
 .
   * Removed non DFSG files, check README.Debian for details. Closes: #591210
   * Fixed postinst script that failed to reload postgresql.
   * Success to install even if postgresql is not installed. Closes: #595499
   * Added info about PostgreSQL dependency to README.Debian.
Checksums-Sha1: 
 034cdefa137e95a168debc4a4484026414920a06 1238 dotlrn_2.5.0+dfsg-1.dsc
 59a9e3c35e5a724a7deb87590021ef786a128fe2 25942122 dotlrn_2.5.0+dfsg.orig.tar.gz
 bbc3bcbb8c527951ebf1b82c38a1ab8fae556956 49634 dotlrn_2.5.0+dfsg-1.diff.gz
 4420e645d4cc011099db2495094bf9af3e68c371 26130894 dotlrn_2.5.0+dfsg-1_all.deb
Checksums-Sha256: 
 bb6350e36557e40d6d20e0d1260c2bd8d583487c8bbdc6475801cfcf50b5e7c7 1238 
dotlrn_2.5.0+dfsg-1.dsc
 11c81b6683c94dd2bb59dfecc8c5a41096ba17e56a6bca9968a10dd6449921c9 25942122 
dotlrn_2.5.0+dfsg.orig.tar.gz
 110ebf71e4b9657654664720c21e851d1ad00277fc868aecac34aefee73d8586 49634 
dotlrn_2.5.0+dfsg-1.diff.gz
 013ab897462077930358184d8aa98c2ba1bbdb014f356e90b3e5e6e9789ff120 26130894 
dotlrn_2.5.0+dfsg-1_all.deb
Files: 
 56a3a8cec653b83fd259cbd3516f838d 1238 web optional dotlrn_2.5.0+dfsg-1.dsc
 85afa2e92b2736c06f3518373f262878 25942122 web optional 
dotlrn_2.5.0+dfsg.orig.tar.gz
 8341e9f542d222342c53533422bb9f86 49634 web optional dotlrn_2.5.0+dfsg-1.diff.gz
 1735bc0d7fe78db325f244a84b426a09 26130894 web optional 
dotlrn_2.5.0+dfsg-1_all.deb

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

iEYEARECAAYFAkycvc4ACgkQpFNRmenyx0durgCg+62cI6XOUQ2i+BL/Xi+yD99J
kUgAnR6ZvM6WC/VmDUmKcBGP+21hfTPj
=1ya7
-END PGP SIGNATURE-


---End Message---

Bug#597962: quodlibet: Error Occurred dialog on playback

2010-09-24 Thread Ian Campbell

Package: quodlibet
Version: 2.2.1-1
Severity: grave
Justification: renders package unusable

This is a reoccurance of #592587 which I failed to reopen because it has been
archived.

I'm now seeing the same issue on a completely up to date Sid system.

Due to the previous issue with holding python-gobject I suspected some sort of
ABI issue with the reversion of python-gobject in 2.21.4+is.2.21.3-1 to an
older upstream so I rebuilt quodlibet and quodlibet-plugins in an up to date
Sid pbuilder environment but that didn't help. (It was a bit of a stab in the
dark to be honest).

I suspect this issue belongs further down the stack but I don't know which way
to direct it.

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

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

Versions of packages quodlibet depends on:
ii  exfalso   2.2.1-1audio tag editor for GTK+
ii  gstreamer0.10-plugins-base0.10.30-1  GStreamer plugins from the base 
ii  gstreamer0.10-plugins-good0.10.24-1  GStreamer plugins from the good 
ii  gstreamer0.10-plugins-ugly0.10.15-1  GStreamer plugins from the ugly 
ii  python2.6.6-3interactive high-level object-orie
ii  python-gst0.100.10.19-2  generic media-playing framework (P

Versions of packages quodlibet recommends:
ii  gstreamer0.10-alsa0.10.30-1  GStreamer plugin for ALSA
pn  gstreamer0.10-gnomevfsnone (no description available)
ii  python-dbus   0.83.1-1   simple interprocess messaging syst
ii  python-feedparser 4.1-14 Universal Feed Parser for Python
ii  python-gpod   0.7.93-0.3 Python bindings for libgpod
ii  quodlibet-ext 2.2.1-1extensions for the Quod Libet audi

Versions of packages quodlibet suggests:
ii  gstreamer0.10-plugins-bad   0.10.19-2+b2 GStreamer plugins from the bad s
ii  quodlibet-plugins   1:2.2.1-1various contributed plugins for Qu

-- no debconf information
=== SYSTEM INFORMATION:
Quod Libet 2.2.1
Mutagen 1.19
Python 2.6.6 (r266:84292, Sep 15 2010, 14:52:42) 
[GCC 4.4.5 20100909 (prerelease)] linux2

=== STACK TRACE
Traceback (most recent call last):

  File /usr/lib/pymodules/python2.6/quodlibet/player/gstbe.py, line 182, in 
do_set_property
self._vol_element.set_property('volume', v)

TypeError: object at 0x55239b0 of type __main__.GstVolume is not initialized



=== LOG: 'General'
Initializing audio backend (gstbe)
Initializing main library (~/.quodlibet/songs)
Supported formats: mod, mp3, mp4, mpc, spc, trueaudio, wav, wavpack, wma, xiph


=== LOG: 'Debug'
D: 970.03: Entering quodlibet.init
D: 970.78: SongFileLibrary object at 0x1b8a5a0 
(quodlibet+library+_library+Library at 0x18fb640)Loading contents of 
'/home/ijc/.quodlibet/songs'.
D: 971.03: SongFileLibrary.load: Done loading contents of 
'/home/ijc/.quodlibet/songs'.
D: 971.04: Initializing debugging extensions
D: 971.04: Finished initialization.
D: 971.37: Initializing device backend.
D: 971.37: Trying 'DeviceKit Disks'
D: 971.37: Trying 'UDisks'
D: 971.38: Device backend initialized.
D: 971.95: SongLibrary object at 0x448ac30 (quodlibet+library+_library+Library 
at 0x1f21680)Loading contents of '/home/ijc/.quodlibet/stations'.
D: 972.27: MainSongList.set_songs: Detaching model.
D: 972.27: PlaylistModel.set: Clearing model.
D: 972.27: PlaylistModel.set: Setting 0 songs.
D: 972.27: PlaylistModel.set: Done filling model.
D: 972.27: MainSongList.set_songs: Attaching model.
D: 972.27: MainSongList.set_songs: Model attached.
D: 973.14: Added copool function bound method SongFileLibrary.rebuild of 
SongFileLibrary object at 0x1b8a5a0 (quodlibet+library+_library+Library at 
0x18fb640) with id 'library'
D: 973.24: Entering quodlibet.main
D: 973.44: Enabling custom exception handler.
D: 973.47: MainSongList.set_songs: Detaching model.
D: 973.47: PlaylistModel.set: Clearing model.
D: 973.47: PlaylistModel.set: Setting 16 songs.
D: 973.47: PlaylistModel.set: Done filling model.
D: 973.47: MainSongList.set_songs: Attaching model.
D: 973.47: MainSongList.set_songs: Model attached.
D: 973.48: GStreamerPlayer.go_to: Going to {'cddb-source': u'0xc30f5110', 
'album': u'Fear Candy 37', '~#playcount': 5, '~#bitrate': 0, 'title': 
u'Strength', '~#length': 155, 'artist': u'Since The Flood', '~#rating': 0.5, 
'compilation_artist': u'Terrorizer', '~#added': 1186172564, '~#lastplayed': 
1285330782, '~#mtime': 1284197651.1572635, 'year': u'2007', 'owner': u'ian', 
'tracknumber': u'7', '~mountpoint': '/storage/music', '~filename': 
'/storage/music/Terrorizer - Fear Candy 37/07-Since The Flood - Strength.flac', 
'~#laststarted': 1285330781, '~#skipcount': 0}
D: 973.48: PlaylistMux.go_to: Told to go to {'cddb-source':

Bug#596408: Only segmentation faults when called...


On 24/09/10 15:29, Anthony Callegaro wrote:

Can you try a 32 bits version or do you want me to give you a SSH access
to one test VZ ?


Hi,

I've made a 32-bit squeeze VE and was able to reproduce this issue 
straight away.


I thought Soeren was experiencing the bug on amd64 because that was 
mentioned in the 'reportbug' output in the initial report.  If this bug 
is really specific to a 32-bit userland then that could be why it hasn't 
affected any of my OpenVZ VE's (which were all amd64).  I don't think 
the kernel's version or architecture will matter in this case.



python-apt 0.7.96.1 works fine, but is only installable with older 
packages apt-utils 0.7.25.3 and apt 0.7.25.3


If I upgrade to python-apt 0.7.97.1, which requires newer apt-utils 
0.8.0 and apt 0.8.0, the segfault happens quite consistently when trying 
to upgrade any package.  An easy way to trigger this is to downgrade 
something older version, eg. tzdata 2010k-1, and then it will try (and 
fail) to upgrade to the latest version from testing.


All of these old package versions can be found on snapshots.debian.org


I'll take a look at the python-apt 0.7.96.1 and 0.7.97.1 sources and 
rebuild each on my own system to see if I can work out where the bug was 
introduced.


There was a 0.7.97 version in between but it seems that FTBFS on i386, 
hence 0.7.97.1 replaced it the same day.  I may take a look at that too 
in case the fix for that issue is somehow related to this segfault.


Regards,
--
Steven Chamberlain
ste...@pyro.eu.org



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

Bug#596408: Only segmentation faults when called...

On Fri, Sep 24, 2010 at 05:05:02PM +0100, Steven Chamberlain wrote:
 On 24/09/10 15:29, Anthony Callegaro wrote:
 Can you try a 32 bits version or do you want me to give you a SSH access
 to one test VZ ?
[..]
 python-apt 0.7.96.1 works fine, but is only installable with older
 packages apt-utils 0.7.25.3 and apt 0.7.25.3
 
 If I upgrade to python-apt 0.7.97.1, which requires newer apt-utils
 0.8.0 and apt 0.8.0, the segfault happens quite consistently when
 trying to upgrade any package.  An easy way to trigger this is to
 downgrade something older version, eg. tzdata 2010k-1, and then it
 will try (and fail) to upgrade to the latest version from testing.
[..]

Let me first say a big THANK YOU (to you and the rest of the people
helping with this report) for the excellent report and the level of
detail. I would appreciate feedback if the different python-apt
version make a difference. I more suspect that its the new apt/libapt
(the amount of changes in python-apt is relatively small), any more
findings/information about that will help.

Thanks,
 Michael



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

Bug#596408: Only segmentation faults when called...


On 24/09/10 17:47, Michael Vogt wrote:

I would appreciate feedback if the different python-apt
version make a difference. I more suspect that its the new apt/libapt
(the amount of changes in python-apt is relatively small), any more
findings/information about that will help.



Hi!

I just finished doing that, and it seems you're right.

I rebuilt python-apt 0.7.96.1, 0.7.96.1build1, 0.7.97 and 0.7.97.1 
against apt/apt-utils 0.8.0 and they all exhibit this bug:



r...@squeeze32:~# dpkg --list python-apt apt apt-utils
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionDescription
+++-==-==-
ii  apt0.8.0  Advanced front-end for dpkg
ii  apt-utils  0.8.0  APT utility programs
ii  python-apt 0.7.96.1   Python interface to libapt-pkg
r...@squeeze32:~# unattended-upgrade --debug
Initial blacklisted packages:
Starting unattended upgrades script
Allowed origins are: [('Debian', 'stable'), ('Debian', 'squeeze-security'), ('Debian', 
'squeeze-updates'), ('Debian', 'testing')]
Checking: python-apt ([Origin component:'main' archive:'testing' origin:'Debian' 
label:'Debian' site:'cdn.debian.net' isTrusted:True])
pkgs that look like they should be upgraded: python-apt
Fetched 0B in 0s (0B/s)
Segmentation fault



So, it seems that python-apt 0.7.96.1 only worked for me due to the 
older apt/apt-utils 0.7.25.3:



r...@squeeze32:~# dpkg --list python-apt apt apt-utils
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionDescription
+++-==-==-
hi  apt0.7.25.3   Advanced front-end for dpkg
hi  apt-utils  0.7.25.3   APT utility programs
hi  python-apt 0.7.96.1   Python interface to libapt-pkg
r...@squeeze32:~# unattended-upgrade --debugInitial blacklisted packages:
Starting unattended upgrades script
Allowed origins are: [('Debian', 'stable'), ('Debian', 'squeeze-security'), ('Debian', 
'squeeze-updates'), ('Debian', 'testing')]
Checking: apt ([Origin component:'main' archive:'testing' origin:'Debian' 
label:'Debian' site:'cdn.debian.net' isTrusted:True])
pkg 'apt' is on hold
sanity check failed
Checking: apt-utils ([Origin component:'main' archive:'testing' origin:'Debian' 
label:'Debian' site:'cdn.debian.net' isTrusted:True])
package 'apt-utils' upgradable but fails to be marked for upgrade (E:Unable to 
correct problems, you have held broken packages.)
Checking: python-apt ([Origin component:'main' archive:'testing' origin:'Debian' 
label:'Debian' site:'cdn.debian.net' isTrusted:True])
package 'python-apt' upgradable but fails to be marked for upgrade (E:Unable to 
correct problems, you have held broken packages.)
Checking: tzdata ([Origin component:'main' archive:'testing' origin:'Debian' 
label:'Debian' site:'cdn.debian.net' isTrusted:True])
pkgs that look like they should be upgraded: tzdata
Get:1 http://cdn.debian.net squeeze/main tzdata 2010l-1 [764kB]
Fetched 764kB in 0s (0B/s)
apt_pkg.AcquireItem object: Status: 2 Complete: 1 Local: 0 IsTrusted: 1 FileSize: 
763772 DestFile:'/var/cache/apt/archives/tzdata_2010l-1_all.deb' DescURI: 
'http://cdn.debian.net/debian/pool/main/t/tzdata/tzdata_2010l-1_all.deb' ID:1 
ErrorText: ''
check_conffile_prompt('/var/cache/apt/archives/tzdata_2010l-1_all.deb')
found pkg: tzdata
blacklist: []
InstCount=1 DelCount=0 BrokenCout=0
Packages that are upgraded: tzdata
Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2010-09-24_18:23:46.527080.log'
All upgrades installed



I noticed this during the build against apt/apt-utils 0.8.0 -- I think 
this is the same Python object that leads PyString_FromFormat to choke:



python/acquire.cc: In function 'PyObject* PkgAcquireNew(PyTypeObject*, 
PyObject*, PyObject*)':
python/acquire.cc:331: warning: 'pkgAcquire::pkgAcquire(pkgAcquireStatus*)' is 
deprecated (declared at /usr/include/apt-pkg/acquire.h:352)


Perhaps there was some incompatible change in that object in APT 0.8.0?

Regards,
--
Steven Chamberlain
ste...@pyro.eu.org



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

Processed: severity of 561203 is important

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

 # hppa-specific bug, therefore not RC
 severity 561203 important
Bug #561203 [linux-2.6] threads and fork on machine with VIPT-WB cache
Severity set to 'important' from 'serious'

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
561203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#559352: marked as done (segfault on startup (mipsel))

Your message dated Fri, 24 Sep 2010 19:55:52 +0200
with message-id 20100924175552.ga16...@bogon.sigxcpu.org
and subject line Fixed in 1.0b1
has caused the Debian Bug report #559352,
regarding segfault on startup (mipsel)
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.)


-- 
559352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: iceowl
Version: 0.8-6
Severity: grave
Justification: completely useless on mipsel
User: debian-m...@lists.debian.org

r...@yeeloong:~$ LANG=C iceowl
/usr/lib/iceowl/run-mozilla.sh: line 131:  3223 Segmentation fault  $prog 
${1+$@}

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: mipsel (mips64)

Kernel: Linux 2.6.31.6-libre1 (PREEMPT)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


---End Message---
---BeginMessage---
Version: iceowl/1.0~b1+dfsg1-1

This is fixed in the above Version. Thanks a lot to Sebastian for
testing.
Cheers,
 -- Guido

---End Message---

Bug#596408: Only segmentation faults when called...


On 24/09/10 18:33, Steven Chamberlain wrote:

python/acquire.cc: In function 'PyObject* PkgAcquireNew(PyTypeObject*,
PyObject*, PyObject*)':
python/acquire.cc:331: warning:
'pkgAcquire::pkgAcquire(pkgAcquireStatus*)' is deprecated (declared at
/usr/include/apt-pkg/acquire.h:352)


Actually, here's our culprint:


python/acquire-item.cc: In function 'PyObject* acquireitem_repr(PyObject*)':
python/acquire-item.cc:170: warning: format '%lu' expects type 'long unsigned 
int', but argument 7 has type 'long long unsigned int'


A 'long unsigned int' became a 'long long unsigned int', but on amd64 
those data types are the same, which is why we only saw an issue on i386.



Please try rebuilding python-apt with my patch to fix this, attached.

$ apt-get source python-apt
$ sudo apt-get build-dep python-apt
$ cd python-apt-0.7.97.1
$ patch -p1  ~/python-apt-bug596408.patch
$ dpkg-buildpackage
$ sudo dpkg -i ../python-apt_0.7.97.1_amd64.deb

You may wish to remove python-apt-dbg if you had that installed.

If you immediately run unattended-upgrades, it should successfully 
upgrade any packages without segfaulting.  It may 'upgrade' the 
python-apt back to the broken version, too, unless you put that package 
on hold.  But that fact that it succeeds in performing an upgrade 
without segfaulting means that the patch worked.


It's working for me on the same 32-bit squeeze OpenVZ VE that I 
reproduced the bug on, and I've also tested this on a native amd64 
system to ensure the patched version still works on that architecture too.


Thank you everyone for your help to reproduce and debug this.

Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--- python-apt-0.7.97.1~orig/python/acquire-item.cc	2010-05-19 11:48:44.0 +0100
+++ python-apt-0.7.97.1/python/acquire-item.cc	2010-09-24 19:07:39.0 +0100
@@ -162,7 +162,7 @@
 return 0;
 return PyString_FromFormat(%s object: 
Status: %i Complete: %i Local: %i IsTrusted: %i 
-   FileSize: %lu DestFile:'%s' 
+   FileSize: %llu DestFile:'%s' 
DescURI: '%s' ID:%lu ErrorText: '%s',
Self-ob_type-tp_name,
Itm-Status, Itm-Complete, Itm-Local, Itm-IsTrusted(),

Bug#584383: Not pending, disappeared from NEW ?

2010-09-24 Thread Javier Fernández-Sanguino Peña

On Wed, Sep 22, 2010 at 06:55:30PM +0200, Luca Falavigna wrote:
 Il 22/09/2010 17:55, Didier 'OdyX' Raboud ha scritto:
  My RSS tells me that titantools 4.0.11-7 left NEW on 04.09.2010 02:00, 
  but I 
  can't get a trace of that anywhere on the packages.qa.d.o, on the buildd or 
  on 
  the archive (CC'ing ftpmaster to get a enlightening on that).
 
 It has been manually rejected, forwarding related message:

I did not get that message (or it didn't go to the proper folder).

I will do as requested by FTP masters.

Regards

Javier


signature.asc
Description: Digital signature

Bug#596408: Only segmentation faults when called...

On Fri, Sep 24, 2010 at 07:28:08PM +0100, Steven Chamberlain wrote:
 On 24/09/10 18:33, Steven Chamberlain wrote:
 python/acquire.cc: In function 'PyObject* PkgAcquireNew(PyTypeObject*,
 PyObject*, PyObject*)':
 python/acquire.cc:331: warning:
 'pkgAcquire::pkgAcquire(pkgAcquireStatus*)' is deprecated (declared at
 /usr/include/apt-pkg/acquire.h:352)
 
 Actually, here's our culprint:
 
 python/acquire-item.cc: In function 'PyObject* acquireitem_repr(PyObject*)':
 python/acquire-item.cc:170: warning: format '%lu' expects type 'long 
 unsigned int', but argument 7 has type 'long long unsigned int'
[..]
 Please try rebuilding python-apt with my patch to fix this, attached.
[..]
 It's working for me on the same 32-bit squeeze OpenVZ VE that I
 reproduced the bug on, and I've also tested this on a native amd64
 system to ensure the patched version still works on that
 architecture too.
 
 Thank you everyone for your help to reproduce and debug this.
[..]

You rock! Thanks a lot for this patch, I commit it to the python-apt
bzr repository now and it will be part of the next upload.

Thanks!
 Michael 



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

Bug#596408: Only segmentation faults when called...

On Fri, Sep 24, 2010 at 07:28:08PM +0100, Steven Chamberlain wrote:
 On 24/09/10 18:33, Steven Chamberlain wrote:
 python/acquire.cc: In function 'PyObject* PkgAcquireNew(PyTypeObject*,
 PyObject*, PyObject*)':
 python/acquire.cc:331: warning:
 'pkgAcquire::pkgAcquire(pkgAcquireStatus*)' is deprecated (declared at
 /usr/include/apt-pkg/acquire.h:352)
 
 Actually, here's our culprint:
 
 python/acquire-item.cc: In function 'PyObject* acquireitem_repr(PyObject*)':
 python/acquire-item.cc:170: warning: format '%lu' expects type 'long 
 unsigned int', but argument 7 has type 'long long unsigned int'
 
 A 'long unsigned int' became a 'long long unsigned int', but on
 amd64 those data types are the same, which is why we only saw an
 issue on i386.
[..]

It turns out that there are two more issues in the code, I attached a
updated patch. Could you please give it a try and see if its good or
causing any issues?

Thanks,
 Michael
=== modified file 'python/acquire-item.cc'
--- python/acquire-item.cc	2010-06-01 15:14:30 +
+++ python/acquire-item.cc	2010-09-24 19:25:37 +
@@ -65,7 +65,7 @@
 static PyObject *acquireitem_get_filesize(PyObject *self, void *closure)
 {
 pkgAcquire::Item *item = acquireitem_tocpp(self);
-return item ? Py_BuildValue(i, item-FileSize) : 0;
+return item ? Py_BuildValue(K, item-FileSize) : 0;
 }
 
 static PyObject *acquireitem_get_id(PyObject *self, void *closure)
@@ -95,7 +95,7 @@
 static PyObject *acquireitem_get_partialsize(PyObject *self, void *closure)
 {
 pkgAcquire::Item *item = acquireitem_tocpp(self);
-return item ? Py_BuildValue(i, item-PartialSize) : 0;
+return item ? Py_BuildValue(K, item-PartialSize) : 0;
 }
 
 static PyObject *acquireitem_get_status(PyObject *self, void *closure)
@@ -162,7 +162,7 @@
 return 0;
 return PyString_FromFormat(%s object: 
Status: %i Complete: %i Local: %i IsTrusted: %i 
-   FileSize: %lu DestFile:'%s' 
+   FileSize: %llu DestFile:'%s' 
DescURI: '%s' ID:%lu ErrorText: '%s',
Self-ob_type-tp_name,
Itm-Status, Itm-Complete, Itm-Local, Itm-IsTrusted(),

Bug#589701: ofpath is not compatible with non-builtin disk controllers

2010-09-24 Thread Rick Thomas


Hi Benjamin,

First, let me apologize for the confusing non-specificity of my bug  
reports to you and everyone else who is following this (and related)  
bug(s).  The only excuse I can offer is that at the time I was  
submitting them, I wasn't sure what was causing the symptoms I was  
seeing.  All I knew was that I couldn't do a squeeze install or an  
upgrade from lenny to squeeze.  And I was frustrated by the total lack  
of response.


That said, and trying to go forward, the question now is Where do we  
stand on getting this fixed?


Can we come up with a list of specific problems -- and a 'todo' list  
of release-critical things that need to be fixed for PowerPC Debian  
Squeeze?


In that line, we need a list of individual folks who are interested in  
contributing to this effort.  Is this bug report (589701) a good one  
to encourage all these folks to subscribe to in the interest of  
centralized record-keeping?


Thanks!

Rick

On Sep 24, 2010, at 7:33 AM, Benjamin Cama wrote:


Hi Rick,

I am a bit disappointed about how this is ending, but I just realized
you are using an addon Promise card as disk controller. This is not
supported by ofpath, which just handle IDE controllers using the old  
ATA
stack or true SCSI controllers. In short, it is hardwired for a list  
of

disk controllers.

Your bug is a bit different from #572869, even if he's also using a  
SATA
(so, new ATA stack) controller, but this is the Apple provided one,  
and

yaboot has a special case for it (even if it seems not to work so well
for now).

I don't really know what to do about that. From what I read (#372186),
ofpathname is better for recent controllers using the new ATA stack,  
and

it's what grub2 is using. Still, it may lack proper handling of old
controllers, even if we can see (again) people willing to bring that
from ofpath, without much result.

Furthermore, since 2.6.34, benh wrote a new driver (macio) for  
newworld

Macs (I don't know if it supports /all/ machines) that is based on the
new ATA stack, so ofpath will need to support it soon (well, it's for
after squeeze at least), or we'll need to switch to ofpathname (or  
grub2

alltogether).

Anyway, thanks for your perseverance, but try to be more specific on
your problems next time ;-)

Regards,
benjamin








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

Bug#597975: cdo: FTBFS on hppa, mips, and sparc

Source: cdo
Version: 1.4.6.dfsg.1-3
Severity: serious
Justification: FTBFS

Hi one more time.

[mips hasn't failed yet due to its suffering from buildd backlog AFAICT]

I'm unsure how (or if?) you're expecting your package to build, but
well, since you're using both of:
 - Build-Depends: […] libjasper-dev [!mips !sparc !hppa]
 - --with-jasper=/usr inconditionally in debian/rules

… surprise surprise:
| checking for library containing nc_open... -lnetcdf
| checking for library containing jas_init... no
| configure: error: Could not link to jasper library! Required for GRIB_API

Full build logs at the usual (!) place:
  https://buildd.debian.org/status/package.php?p=cdo

Mraw,
KiBi.



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

Bug#596086: marked as done (CVE-2010-3072: DoS triggered by internal error in string handling)

Your message dated Fri, 24 Sep 2010 20:00:03 +
with message-id e1ozer9-0005wu...@franck.debian.org
and subject line Bug#596086: fixed in squid3 3.0.STABLE8-3+lenny4
has caused the Debian Bug report #596086,
regarding CVE-2010-3072: DoS triggered by internal error in string handling
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.)


-- 
596086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: squid3
Severity: grave
Tags: security
Justification: user security hole

Please see http://www.squid-cache.org/Advisories/SQUID-2010_3.txt

Cheers,
Moritz

-- System Information:
Debian Release: 5.0.1
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.32-ucs11-amd64
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)


---End Message---
---BeginMessage---
Source: squid3
Source-Version: 3.0.STABLE8-3+lenny4

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

squid3-cgi_3.0.STABLE8-3+lenny4_amd64.deb
  to main/s/squid3/squid3-cgi_3.0.STABLE8-3+lenny4_amd64.deb
squid3-common_3.0.STABLE8-3+lenny4_all.deb
  to main/s/squid3/squid3-common_3.0.STABLE8-3+lenny4_all.deb
squid3_3.0.STABLE8-3+lenny4.diff.gz
  to main/s/squid3/squid3_3.0.STABLE8-3+lenny4.diff.gz
squid3_3.0.STABLE8-3+lenny4.dsc
  to main/s/squid3/squid3_3.0.STABLE8-3+lenny4.dsc
squid3_3.0.STABLE8-3+lenny4_amd64.deb
  to main/s/squid3/squid3_3.0.STABLE8-3+lenny4_amd64.deb
squidclient_3.0.STABLE8-3+lenny4_amd64.deb
  to main/s/squid3/squidclient_3.0.STABLE8-3+lenny4_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 596...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steffen Joeris wh...@debian.org (supplier of updated squid3 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: Sat, 18 Sep 2010 17:34:19 +1000
Source: squid3
Binary: squid3 squid3-common squidclient squid3-cgi
Architecture: source all amd64
Version: 3.0.STABLE8-3+lenny4
Distribution: stable-security
Urgency: high
Maintainer: Luigi Gangitano lu...@debian.org
Changed-By: Steffen Joeris wh...@debian.org
Description: 
 squid3 - A full featured Web Proxy cache (HTTP proxy)
 squid3-cgi - A full featured Web Proxy cache (HTTP proxy) - control CGI
 squid3-common - A full featured Web Proxy cache (HTTP proxy) - common files
 squidclient - A full featured Web Proxy cache (HTTP proxy) - control utility
Closes: 596086
Changes: 
 squid3 (3.0.STABLE8-3+lenny4) stable-security; urgency=high
 .
   * Non-maintainer upload by the security team
   * Fix DoS due to wrong string handling (Closes: #596086)
 Fixes: CVE-2010-3072
Checksums-Sha1: 
 0a1383e3efcfa4d3f6e14e1f6ddfebd79e4ac8ad 1193 squid3_3.0.STABLE8-3+lenny4.dsc
 00660cd64338e172b14a76a1bf1b149a2dd5ab74 20699 
squid3_3.0.STABLE8-3+lenny4.diff.gz
 0c46529de1430e9a5bca4561e8a498d7fb976a20 289406 
squid3-common_3.0.STABLE8-3+lenny4_all.deb
 6de2daa9f14fcc761ccf77e9244b1bb27ce976d8 1008578 
squid3_3.0.STABLE8-3+lenny4_amd64.deb
 338c55b0a18db3025d220a7de18077feba68689d 89072 
squidclient_3.0.STABLE8-3+lenny4_amd64.deb
 d105783ca03c17987b85bac50aa57656f93326d5 92634 
squid3-cgi_3.0.STABLE8-3+lenny4_amd64.deb
Checksums-Sha256: 
 c8951b37df5b1d346fe39bef3a9e7ae948020028fc513b1bf7fa38a51d106408 1193 
squid3_3.0.STABLE8-3+lenny4.dsc
 663b6f6b44faf2e805e8f9a99a59cf02a4ad19fb79b929f8ca940c50a2347de7 20699 
squid3_3.0.STABLE8-3+lenny4.diff.gz
 eecefebd05dccd103a0a45284da64f4a71676583b9f3da9cd3a164d9f4ed2bd1 289406 
squid3-common_3.0.STABLE8-3+lenny4_all.deb
 1d6d0774bc4961955a2c740b4dc0df6945cd0a9ce552400220cfaddb1b8cb389 1008578 
squid3_3.0.STABLE8-3+lenny4_amd64.deb
 16942b87aff2caa0b1a553d0955b8d28ef151f26d96873946e7c117ce4bffea8 89072 
squidclient_3.0.STABLE8-3+lenny4_amd64.deb
 8d9a3792e585a205fa5546d051f3eec94097f78ac6d46646f8aab0a762638ee4 92634 
squid3-cgi_3.0.STABLE8-3+lenny4_amd64.deb
Files: 
 c301ce03c043f892a1dab392b82f5454 1193 web optional 
squid3_3.0.STABLE8-3+lenny4.dsc
 8660e684fab99044d17ee435cd8718d9 20699 web optional 
squid3_3.0.STABLE8-3+lenny4.diff.gz
 954e5536f90c542c1fc7300fc9a6ad0e 289406 web

Processed: severity of 572169 is important

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

 severity 572169 important
Bug #572169 [apt] /usr/bin/apt-get: apt-get breaks on openoffice.org-core 
upgrade
Severity set to 'important' from 'critical'

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
572169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#597977: fluidsynth: FTBFS on kfreebsd-*: fluid_rtkit.c: error: storage size unknown

Source: fluidsynth
Version: 1.1.2-1
Severity: serious
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

your package no longer builds on kfreebsd-*:
| cd 
/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/obj-x86_64-kfreebsd-gnu/src
  /usr/bin/gcc  -Dlibfluidsynth_EXPORTS -DHAVE_LASH -DHAVE_CONFIG_H -g -O2  
-fPIC 
-I/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/obj-x86_64-kfreebsd-gnu
 -I/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src 
-I/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/drivers
 
-I/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/synth
 
-I/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/rvoice
 
-I/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/midi
 
-I/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/utils
 
-I/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/sfloader
 
-I/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/bindings
 -I/build/buildd-fluidsynth_1.1
 .2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/include 
-I/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/obj-x86_64-kfreebsd-gnu/include
 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 
-I/usr/lib/dbus-1.0/include -I/usr/include/lash-1.0   -o 
CMakeFiles/libfluidsynth.dir/bindings/fluid_rtkit.c.o   -c 
/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/bindings/fluid_rtkit.c
| 
/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/bindings/fluid_rtkit.c:
 In function 'fluid_rtkit_make_realtime':
| 
/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/bindings/fluid_rtkit.c:336:
 error: storage size of 'old_limit' isn't known
| 
/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/src/bindings/fluid_rtkit.c:336:
 error: storage size of 'new_limit' isn't known
| make[3]: *** [src/CMakeFiles/libfluidsynth.dir/bindings/fluid_rtkit.c.o] 
Error 1
| make[3]: Leaving directory 
`/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/obj-x86_64-kfreebsd-gnu'
| make[2]: *** [src/CMakeFiles/libfluidsynth.dir/all] Error 2
| make[2]: Leaving directory 
`/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/obj-x86_64-kfreebsd-gnu'
| make[1]: *** [all] Error 2
| make[1]: Leaving directory 
`/build/buildd-fluidsynth_1.1.2-1-kfreebsd-amd64-S6AiKT/fluidsynth-1.1.2/obj-x86_64-kfreebsd-gnu'
| dh_auto_build: make -j1 returned exit code 2

Full build logs:
  https://buildd.debian.org/status/package.php?p=fluidsynthsuite=experimental

Mraw,
KiBi.



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

Processed: severity of 597217 is important

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

 severity 597217 important
Bug #597217 [php5] php5: PHP Startup: Unable to load dynamic library
Severity set to 'important' from 'grave'

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
597217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#597978: lilypond: FTBFS on sparc: Bus errors

Source: lilypond
Version: 2.12.3-7
Severity: serious
Justification: FTBFS
User: debian-sp...@lists.debian.org
Usertags: sparc

Hi,

your package repeatedly FTBFS on sparc. Latest run:
| *** Successfully generated parmesan23.pfb! ***
| cd ./out  /usr/bin/fontforge -script emmentaler-11.pe
| Copyright (c) 2000-2010 by George Williams.
|  Executable based on sources from 11:21 GMT 1-May-2010.
|  Library based on sources from 03:43 GMT 29-Apr-2010.
| Bus error
| make[2]: *** [out/emmentaler-11.otf] Error 138
| make[2]: *** Waiting for unfinished jobs
| 
| *** Successfully generated parmesan26.pfb! ***
| make[2]: Leaving directory 
`/build/buildd-lilypond_2.12.3-7-sparc-g1RkR0/lilypond-2.12.3/mf'
| make[1]: *** [all] Error 2

Full build logs:
  https://buildd.debian.org/status/package.php?p=lilypond

FTBFS on hppa  s390 as well.

Mraw,
KiBi.



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

Bug#596408: Only segmentation faults when called...

On Fri, Sep 24, 2010 at 07:28:08PM +0100, Steven Chamberlain wrote:
 On 24/09/10 18:33, Steven Chamberlain wrote:
 python/acquire.cc: In function 'PyObject* PkgAcquireNew(PyTypeObject*,
 PyObject*, PyObject*)':
 python/acquire.cc:331: warning:
 'pkgAcquire::pkgAcquire(pkgAcquireStatus*)' is deprecated (declared at
 /usr/include/apt-pkg/acquire.h:352)
[..]
 --- python-apt-0.7.97.1~orig/python/acquire-item.cc   2010-05-19 
 11:48:44.0 +0100
 +++ python-apt-0.7.97.1/python/acquire-item.cc2010-09-24 
 19:07:39.0 +0100
 @@ -162,7 +162,7 @@
  return 0;
  return PyString_FromFormat(%s object: 
 Status: %i Complete: %i Local: %i IsTrusted: 
 %i 
 -   FileSize: %lu DestFile:'%s' 
 +   FileSize: %llu DestFile:'%s' 
 DescURI: '%s' ID:%lu ErrorText: '%s',
 Self-ob_type-tp_name,
 Itm-Status, Itm-Complete, Itm-Local, 
 Itm-IsTrusted(),

One more odd thing I discovered is that %llu apparently is only
available in python 2.7+ (see [1]). When it encounters the first
unknown format string it stops. That is what I see in the debug
output, %llu and no further strings. That is rather unfortunate from
python. 

I guess PyString_FromFormat() in 2.6 can not be used for this and a
normal snprintf() is required on older python versions. 

Cheers,
 Michael


[1] http://docs.python.org/c-api/string.html



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

Bug#596408: Only segmentation faults when called...


Oops, my last reply went directly to Michael instead of going to the BTS
as well.

My attached patch is what I'm now using on i386 and amd64 and it seems
to be working well  The debug output now looks like this:


# unattended-upgrade --debug

...

apt_pkg.AcquireItem object: Status: 2 Complete: 1 Local: 1
IsTrusted: 1
DestFile:'/var/cache/apt/archives/python-apt_0.7.97.1_i386.deb'
DescURI:
'http://cdn.debian.net/debian/pool/main/p/python-apt/python-apt_0.7.97.1_i386.deb'
ID:0 ErrorText: '' FileSize: %llu


As Michael just pointed out, the FileSize will show '%llu' in the debug 
output of Python 2.6 unless rewritten to use snprintf() or something.


Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--- python-apt-0.7.97.1~orig/python/acquire-item.cc	2010-05-19 11:48:44.0 +0100
+++ python-apt-0.7.97.1/python/acquire-item.cc	2010-09-24 21:36:33.0 +0100
@@ -65,7 +65,7 @@
 static PyObject *acquireitem_get_filesize(PyObject *self, void *closure)
 {
 pkgAcquire::Item *item = acquireitem_tocpp(self);
-return item ? Py_BuildValue(i, item-FileSize) : 0;
+return item ? Py_BuildValue(K, item-FileSize) : 0;
 }
 
 static PyObject *acquireitem_get_id(PyObject *self, void *closure)
@@ -95,7 +95,7 @@
 static PyObject *acquireitem_get_partialsize(PyObject *self, void *closure)
 {
 pkgAcquire::Item *item = acquireitem_tocpp(self);
-return item ? Py_BuildValue(i, item-PartialSize) : 0;
+return item ? Py_BuildValue(K, item-PartialSize) : 0;
 }
 
 static PyObject *acquireitem_get_status(PyObject *self, void *closure)
@@ -160,14 +160,17 @@
 pkgAcquire::Item *Itm = acquireitem_tocpp(Self);
 if (Itm == 0)
 return 0;
+
+// Display any 'long long' (eg. %llu) parameters last;  Python before 2.7
+// will ignore these as well as any parameters after it.
 return PyString_FromFormat(%s object: 
Status: %i Complete: %i Local: %i IsTrusted: %i 
-   FileSize: %lu DestFile:'%s' 
-   DescURI: '%s' ID:%lu ErrorText: '%s',
+   DestFile:'%s' DescURI: '%s' 
+   ID:%lu ErrorText: '%s' FileSize: %llu,
Self-ob_type-tp_name,
Itm-Status, Itm-Complete, Itm-Local, Itm-IsTrusted(),
-   Itm-FileSize, Itm-DestFile.c_str(),  Itm-DescURI().c_str(),
-   Itm-ID,Itm-ErrorText.c_str());
+   Itm-DestFile.c_str(), Itm-DescURI().c_str(),
+   Itm-ID, Itm-ErrorText.c_str(), Itm-FileSize);
 }
 
 static void acquireitem_dealloc(PyObject *self)

Bug#595521: system locked up even without starting X

2010-09-24 Thread jidanni

severity 595521 critical
thanks
Critical for the same reasons as in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595521
With the addition that X never need to have been started for the problem
to occur. I.e., use this kernel and be prepared for needing as cold
reboot, fscking, etc. shortly:  #595103.



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

Processed: system locked up even without starting X

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

 severity 595521 critical
Bug #595521 [linux-2.6] i915: system locks up when starting X
Bug #595103 [linux-2.6] framebuffer gone for intel i915 starting 2.6.32-21
Bug #595511 [linux-2.6] linux-image-2.6.32-5-686: Blacklisting KMS for i8xx 
makes xorg intel driver unusable on these chipsets
Severity set to 'critical' from 'grave'

Severity set to 'critical' from 'grave'

Severity set to 'critical' from 'grave'

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
595521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#597981: mpich2: FTBFS on kfreebsd-amd64: Fails to connect to mpd

Source: mpich2
Version: 1.2.1.1-5
Severity: serious
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: kfreebsd

Hi,

your package no longer builds on kfreebsd-amd64:
| config.status: executing default-3 commands
| + echo MPD_SECRETWORD=secretword
| + chmod 600 .mpd.conf
| ++ pwd
| + 
MPD_CONF_FILE=/build/buildd-mpich2_1.2.1.1-5-kfreebsd-amd64-smJ83h/mpich2-1.2.1.1/test/mpi/.mpd.conf
| + ../../bin/mpdboot
| mpdboot_fasch (handle_mpd_output 415): failed to connect to mpd on fasch
| make: *** [debian/stamp-makefile-testing] Error 255
| dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build logs:
  https://buildd.debian.org/status/package.php?p=mpich2

Mraw,
KiBi.



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

Bug#597982: gcc-snapshot: FTBFS on sparc: Bootstrap comparison failure!

Source: gcc-snapshot
Version: 20100918-1
Severity: serious
Justification: FTBFS
User: debian-sp...@lists.debian.org
Usertags: sparc

Hi,

your package no longer builds on sparc:
| Comparing stages 2 and 3
| warning: gcc/cc1plus-checksum.o differs
| warning: gcc/cc1objplus-checksum.o differs
| warning: gcc/cc1obj-checksum.o differs
| warning: gcc/cc1-checksum.o differs
| Bootstrap comparison failure!
| gcc/ada/ali.o differs
| make[4]: *** [compare] Error 1

Full build logs:
  https://buildd.debian.org/status/package.php?p=gcc-snapshot

Mraw,
KiBi.



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

Processed: severity of 595521 is important

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

 severity 595521 important
Bug #595521 [linux-2.6] i915: system locks up when starting X
Bug #595103 [linux-2.6] framebuffer gone for intel i915 starting 2.6.32-21
Bug #595511 [linux-2.6] linux-image-2.6.32-5-686: Blacklisting KMS for i8xx 
makes xorg intel driver unusable on these chipsets
Severity set to 'important' from 'critical'

Severity set to 'important' from 'critical'

Severity set to 'important' from 'critical'

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
595521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#597778: [buildd-tools-devel] Bug#597778: schroot: Stupid name restrictions is breaking existing setups for no good reason.

2010-09-24 Thread Roger Leigh

severity 597778 important
thanks

On Wed, Sep 22, 2010 at 05:21:15PM -0400, Len Sorensen wrote:
 Package: schroot
 Version: 1.4.12-1
 Severity: grave
 
 I just upgraded schroot to the current version in testing, and now I
 can't use it anymore because someone got the bright (not) idea that only
 alphanumeric, dashes and underscores should be allowed in chroot names.
 It was annoying enough when a while ago the config files started having
 that (undocumented unless you read the source code and without useful
 error message) restriction.
 
 Put it back to sanity please.
 
 If I want to name a chroot rr2.1.0 because that's what is in it, then
 that's my choice.
 
 While you are at it, let me choose the names of my config files too.
 
 Breaking existing users is NOT acceptable so stop doing that.

While this change is clearly an annoyance to yourself, the severity
is certainly not grave, so I am changing it accordingly.  If the
change was causing irretrievable data loss, then the grave severity
would have been appropriate.

Your comments are also rather aggressive.  Please keep to the facts,
rather than using unnecessarily inflammatory language.  It's not
helpful, and is most certainly *not* appreciated.  Bug reports should
have the goal of improving the software, not abusing its developers.
Please bear that in mind, both in any replies to this email, and in
any future bug reports.


Regarding anything undocumented: if something is undocumented that
you need to know about, that's a bug, and if there's an error
message that's not clear, that's also a bug.  Please do file
(separate) bug reports about any such incidence and I'll be happy to
improve the documentation.  Remember that programs such as schroot
are documented by their authors and we already know every aspect
of the program inside and out.  Quality documentation is of course a
goal we have, but it's an unfortunate reality that it's easy to
inadvertently miss out details, especially when you are writing for
someone who isn't intimately familiar with the program. Making
documentation that is easily accessible to newcomers that contains
exactly what they need to know is a rare skill, and while I have done
a lot of work on the manual pages, I am fully aware that the
documentation could be much better.  But what I really need to do that
is *feedback* about what wasn't there that was needed, and what was
there that was unnecessary, etc..


Now, to the main point of your report.  schroot imposes certain
restrictions upon what it considers to be a permitted filename
when reading files under /etc/schroot/chroot.d and also what
is permitted to be a valid chroot and/or session name.

Since the chroot name is used to create session files bearing
the same name, the rules used to validate filenames therefore
may also have a concomitant restriction upon session names.
Before adding stricter validation of chroot names, it was possible
to create names which could lead to sessions which were not
possible to end, or which might potentially lead to an exploit
(naming your chroot ../../../../etc/xxx/xxx could have some
interesting consequences, as a simple example), so the primary
motivation behind this change was to improve security.  Additional
restrictions are also placed by other components we depend upon
(for example, if LVM logical volumes and Btrfs subvolumes and
snapshots have their own naming restrictions).  The imposed
restrictions do actually prevent breakage and/or security issues in
a number of scenarios.

The second motivation behind the change was to provide a single
validation mechanism for all names, again with the goal of improving
security and reliability.  You can find this function in
sbuild/sbuild-util.cc, called is_valid_filename().  Having made this
change, we have now added a second function called
is_valid_sessionname() which is used in places which only need to
validate names, which has relaxed requirements compared with the
filename checks.

  static regex file_namespace(^[a-zA-Z0-9][a-zA-Z0-9_-]*$);

Now, the intention has always been to further relax this requirement
and allow a wider variety of names.  I am well aware that this is
in some respects a regression.  However, you must understand that
schroot is a suid root executable and the *primary* concern is and
always has been security.  If you wish to fix the naming
restrictions, all you need to do is alter that regular expression.
I will make that change once I have *fully evaluated the security
implications of doing so*, and not before.

It may be that ^[^/]$ is sufficient, but we need to be sure of
that.  The chroot/session name is used in quite a lot of places
and for many different purposes, and each of those needs careful
consideration.


So to summarise:

• this change was entirely intentional
• it was made to prevent session breakage and security exploits
• we have put the infrastructure in place to separately validate
  filenames and sesssion names
• we will allow more permissive

Processed: Re: [buildd-tools-devel] Bug#597778: schroot: Stupid name restrictions is breaking existing setups for no good reason.

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

 severity 597778 important
Bug #597778 [schroot] schroot: Stupid name restrictions is breaking existing 
setups for no good reason.
Severity set to 'important' from 'grave'

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
597778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#590937: mol-source: Simpler patch

2010-09-24 Thread Ivan Vilata i Balaguer

Package: mol-source
Version: 0.9.72.1~dfsg-2.1
Severity: normal


I've been able to build the modules with the following patch (which only
appends two include locations):

--- Makefile.orig   2010-09-25 01:16:37.0 +0200
+++ Makefile2010-09-25 01:14:56.0 +0200
@@ -10,7 +10,9 @@
 
 PERFOBJS   = $(addprefix $(obj)/, $(PERFOBJS_))
 K_FLAGS= -Iinclude -include include/linux/autoconf.h 
-Iarch/ppc -Iarch/ppc/include \
- -I$(src) -I$(src)/../../../include $(INCLUDES) -D__KERNEL__
+ -I$(src) -I$(src)/../../../include $(INCLUDES) -D__KERNEL__ \
+ -I/usr/src/linux-headers-2.6.32-5-common/arch/powerpc/include 
\
+ -I/usr/src/linux-headers-2.6.32-5-common/include
 MOL_ASMFLAGS   = $(CPPFLAGS) $(ASMFLAGS) $(K_FLAGS) -D__ASSEMBLY__
 LDFLAGS_MODULE  = $(LDFLAGS_BUILD_ID)

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

Kernel: Linux 2.6.32-5-powerpc
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages mol-source depends on:
ii  gcc   4:4.4.4-2  The GNU C compiler
ii  libc6-dev 2.11.2-6   Embedded GNU C Library: Developmen
ii  m41.4.14-3   a macro processing language
ii  make  3.81-8 An utility for Directing compilati

Versions of packages mol-source recommends:
ii  bzip2 1.0.5-6high-quality block-sorting file co
ii  debhelper 8.0.0  helper programs for debian/rules
ii  kernel-package12.036 A utility for building Linux kerne

Versions of packages mol-source suggests:
ii  linux-headers-2.6-powerpc [li 2.6.32+28  Header files for Linux 2.6-powerpc
ii  linux-headers-2.6.32-5-powerp 2.6.32-23  Header files for Linux 2.6.32-5-po

-- 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#594472: grub-pc: scary messages and very long boot time after upgrade

2010-09-24 Thread Andreas von Heydwolff


On 2010-09-24 11:50, Alexander Kurtz wrote:

So after all this was just mdadm bug #583917 combined with the fact that
you used to wrong name (compared to /etc/cryptsetup) when unlocking the
crypto device manually. This of course caused the cryptsetup initramfs
hook to break when recreating the initramfs. As a consequence, your
cryptroot didn't get unlocked during early boot stage. Correct?


Correct.


PS: You should revert /etc/cryptab to the state it had before all the
 debugging (i.e. with UUID=). You should also revert the change you
 made to the cryptsetup initramfs hook, for example like this:
apt-get --reinstall install cryptsetup


Thank you, --reinstall is perhaps a safer solution than rolling back the 
manual changes I made.


Now I am only left wondering: Was it just the coincidence of mdadm bug 
#583917 being new and my installing a new system that prevented GRUB to 
be installed properly in said new system, or was I simultaneously hit by 
a GRUB bug that's been resolved as well in the meantime? I recall that 
installing GRUB had to be done manually, and that this had been  awkward.


Best regards,

A.v. Heydwolff



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

Bug#595839: verilog-mode: diff for NMU version 558-1.1

2010-09-24 Thread NIIBE Yutaka

gregor herrmann wrote:
 tags 595839 + patch
 tags 595839 + pending
 thanks
 
 Dear maintainer,
 
 I've prepared an NMU for verilog-mode (versioned as 558-1.1) and
 uploaded it to DELAYED/2. Please feel free to tell me if I
 should delay it longer.

Thanks.

However, I think that verilog-mode should be deleted.  That's because
it has been integrated into GNU Emacs 23 already.  The package is
exactly for older Emacsen such as GNU Emacs 21 / GNU Emacs 22.
-- 



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

Processed: tag update

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

 tags 597315 + pending
Bug #597315 [choqok] choqok -- ignores twitter OAuth then doesn't supply 
user/password to API
Added tag(s) pending.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
597315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


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

Bug#597382: marked as done (unsafe chroot() call)