Processed: Re: Bug#606323: gnome-panel: Upper panel doesnt show running aplications
Processing commands for cont...@bugs.debian.org: severity 606323 important Bug #606323 [gnome-panel] gnome-panel: Upper panel doesnt show running aplications Severity set to 'important' from 'critical' tag 606323 + moreinfo Bug #606323 [gnome-panel] gnome-panel: Upper panel doesnt show running aplications Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 606323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606323 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#606323: gnome-panel: Upper panel doesnt show running aplications
severity 606323 important tag 606323 + moreinfo thanks * missing kernel module for TDA18218 dvb-t tuner ks...@seznam.cz [2010-12-08 12:34:53 CET]: Before, when i started aplication (Twinkle, skype, knotes) it appeared in right end of upper panel (left to the clocks/calendar). Now it does not. But process only appears in list of processes as sleeping. Major problem is, that i cant get to my old notes in knotes program. Old notes are access right end of upper panel. (this is reason, why i think that this bug is critical, i hope my older important notes are deleted due of this bug). Please right-click on the panel and add to the panel the notification area. This is where these icons would appear. It seems like you accidently removed it. Unless you can reproduce it to get missing repeatedly it rather seems to be a one-time hickup, and (re)adding the notification area should get you back on tracks again. So if you are not able to reproduce it again, feel free to close this bugreport by sending a mail to 606323-d...@bugs.debian.org stating so. Enjoy! Rhonda -- Mission: Cleaning up the BTS http://flattr.com/thing/47066/Debian-BTS-cleaning-up -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572869: marked as done (installation-reports: PowerMac G5 installation report: ofpath doesn't work in the absence of /proc/scsi/scsi)
Your message dated Thu, 09 Dec 2010 09:17:04 + with message-id e1pqcca-0007yk...@franck.debian.org and subject line Bug#572869: fixed in yaboot 1.3.13a-1squeeze1 has caused the Debian Bug report #572869, regarding installation-reports: PowerMac G5 installation report: ofpath doesn't work in the absence of /proc/scsi/scsi 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.) -- 572869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: important -- Package-specific info: Boot method: CD Image version: Debian installer 6.0alpha1 Date: The 2 days preceding Sun Mar 7 08:26:32 UTC 2010 Machine: PowerMac G5 Quad (M9592) Partitions: df -Tl will do; the raw partition table is preferred FilesystemType 1K-blocks Used Available Use% Mounted on /dev/sdb4 ext3 922517820 4569404 871087188 1% / tmpfstmpfs 8121084 0 8121084 0% /lib/init/rw udev tmpfs 10240 188 10052 2% /dev tmpfstmpfs 8121084 0 8121084 0% /dev/shm /dev/sdb #type name length base ( size ) system /dev/sdb1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/sdb2 Apple_Bootstrap bootstrap1600 @ 64 (800.0k) NewWorld bootblock /dev/sdb3 Apple_Free Extra 354 @ 1664 (177.0k) Free space /dev/sdb4 Apple_UNIX_SVR2 root 1874449219 @ 2018 (893.8G) Linux native /dev/sdb5 Apple_UNIX_SVR2 swap 79073931 @ 1874451237 ( 37.7G) Linux swap Block size=512, Number of Blocks=1953525168 DeviceType=0x0, DeviceId=0x0 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] Comments/Problems: Installation worked beautifully with the major exception of yaboot getting hopelessly confused. Evidently the ofpath utility has not been updated to handle the state of the world now that /proc/scsi/scsi is deprecated. I had to dredge out old OpenFirmware references and manually edit /etc/yaboot.conf, then run mkofboot. This generation of PowerMacs (the very last :-( ) uses SATA drives on a PCI-E bus. Once I stuffed OpenFirware device-tree magic into yaboot.conf, things sprinted to a finish. Even X worked on this foul NVidia device. Oddly, in rescue mode, the installer told me that installing yaboot failed, then told me it succeeded with the very next dialog. Its first guess was correct; I had to implement the fix myself at a shell prompt. Here is my /etc/yaboot.conf in case other poor miserable G5 users suffer my SATAnic fate. I had to add ofboot, and correct partition and root (which were 3 instead of 4). At some point I managed to create an over-sized blank area for the hfs bootblock partition, wasting 177kB of precious space. N.B.: I'm booting from the second SATA drive, not the first, because I stupidly installed the drives in the wrong order. People using sda will probably want: ofboot=/ht/p...@9/k2-sata-root/k2-s...@0/d...@0:2 ## yaboot.conf generated by debian-installer ## ## run: man yaboot.conf for details. Do not make changes until you have!! ## see also: /usr/share/doc/yaboot/examples for example configurations. ## ## For a dual-boot menu, add one or more of: ## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ boot=/dev/sdb2 ofboot=/ht/p...@9/k2-sata-root/k2-s...@1/d...@0:2 partition=4 root=/dev/sdb4 timeout=50 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot enablecdboot image=/boot/vmlinux label=Linux read-only initrd=/boot/initrd.img image=/boot/vmlinux.old label=old read-only initrd=/boot/initrd.img.old -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. *** I can't find these logs. Where did they go? Here's lspci: :00:0b.0 PCI bridge: Apple Computer Inc. CPC945 PCIe Bridge :0a:00.0 VGA compatible controller:
Bug#605933: marked as done (mkofboot couldn't find /proc/scsi)
Your message dated Thu, 09 Dec 2010 09:17:04 + with message-id e1pqcca-0007yk...@franck.debian.org and subject line Bug#572869: fixed in yaboot 1.3.13a-1squeeze1 has caused the Debian Bug report #572869, regarding mkofboot couldn't find /proc/scsi 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.) -- 572869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/weekly-builds/powerpc/iso-cd/debian-testing-powerpc-xfce+lxde-CD-1.iso 29-Nov-2010 11:07 648M Date: 3-Dec-2010 21:00 Machine: PowerMac G3 (BW) Processor: PowerPC G3 Memory: 512M Partitions: /dev/sdc #type name length base ( size ) system /dev/sdc1 Apple_partition_map Apple63 @ 1 ( 31.5k) Partition map /dev/sdc2 Apple_Driver43 Macintosh56 @ 64 ( 28.0k) Driver 4.3 /dev/sdc3 Apple_Driver43 Macintosh56 @ 120 ( 28.0k) Driver 4.3 /dev/sdc4Apple_Driver_ATA Macintosh56 @ 176 ( 28.0k) Unknown /dev/sdc5Apple_Driver_ATA Macintosh56 @ 232 ( 28.0k) Unknown /dev/sdc6 Apple_FWDriver Macintosh 512 @ 288 (256.0k) Unknown /dev/sdc7 Apple_Driver_IOKit Macintosh 512 @ 800 (256.0k) Unknown /dev/sdc8 Apple_Patches Patch Partition 512 @ 1312 (256.0k) Unknown /dev/sdc9 Apple_Bootstrap boot 1600 @ 1824 (800.0k) NewWorld bootblock /dev/sdc10Apple_UNIX_SVR2 root 17519256 @ 263968 ( 8.4G) Linux native /dev/sdc11Apple_UNIX_SVR2 swap 260544 @ 3424 (127.2M) Linux swap /dev/sdc12 Apple_Free Extra16 @ 17783224 ( 8.0k) Free space Block size=512, Number of Blocks=17783240 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 120 for 36, type=0x 3: @ 176 for 21, type=0x701 4: @ 232 for 34, type=0xf8ff Output of lspci -knn: 00:00.0 Host bridge [0600]: Motorola MPC106 [Grackle] [1057:0002] (rev 40) 00:0d.0 PCI bridge [0604]: Digital Equipment Corporation DECchip 21154 [1011:0026] (rev 02) 00:10.0 VGA compatible controller [0300]: ATI Technologies Inc Rage 128 RE/SG [1002:5245] Subsystem: Device [b530:0408] Kernel driver in use: aty128fb 01:00.0 FireWire (IEEE 1394) [0c00]: Texas Instruments PCILynx/PCILynx2 IEEE 1394 Link Layer Controller [104c:8000] (rev 02) Subsystem: Apple Computer Inc. Device [106b:001c] 01:01.0 IDE interface [0101]: Silicon Image, Inc. PCI0646 [1095:0646] (rev 07) Subsystem: Silicon Image, Inc. PCI0646 [1095:0646] Kernel driver in use: pata_cmd64x 01:03.0 SCSI storage controller [0100]: Adaptec AIC-7850 [9004:5078] (rev 03) Subsystem: Adaptec AHA-2904/Integrated AIC-7850 [9004:7850] Kernel driver in use: aic7xxx 01:05.0 Unassigned class [ff00]: Apple Computer Inc. Paddington Mac I/O [106b:0017] Kernel driver in use: macio 01:06.0 USB Controller [0c03]: OPTi Inc. 82C861 [1045:c861] (rev 10) Subsystem: OPTi Inc. 82C861 [1045:c861] Kernel driver in use: ohci_hcd Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] (DHCP) Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] (manual) Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] Comments/Problems: boot loader: mkofboot couldn't find /proc/scsi (existing Bug #572869). After manually editing /etc/yaboot.conf, I was facing another problem on boot: the disk drives seem to be detected in undefined order, and this makes it difficult to guess correct /dev/sd letter (and yaboot doesn't accept LABEL= syntax). I have two IDE disks (pata_cmd64x) and one SCSI disk (the one used here) (aic7xxx). Third problem was with X. It was running wild and filling the disk with its log file. The salvation came with package firmware-linux-nonfree containing the file r128_cce.bin. Still, I'm unable to log out and in again, as this makes X hang. ---End Message--- ---BeginMessage--- Source: yaboot Source-Version: 1.3.13a-1squeeze1 We believe that the bug you reported is fixed in the latest version of
Bug#594715: marked as done (installation-reports: successful install but yaboot problem)
Your message dated Thu, 09 Dec 2010 09:17:04 + with message-id e1pqcca-0007yk...@franck.debian.org and subject line Bug#572869: fixed in yaboot 1.3.13a-1squeeze1 has caused the Debian Bug report #572869, regarding installation-reports: successful install but yaboot problem 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.) -- 572869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: normal -- Package-specific info: Boot method: cdrom with netinst Image version: http://cdimage.debian.org/cdimage/daily-builds/squeeze_d-i/current/powerpc/jigdo-cd/debian-testing-powerpc-netinst.jigdo from 20100827 Date: Sat Aug 28 15:00:00 UTC 2010 Machine: Power Mac G5 Partitions: df -Tl will do; the raw partition table is preferred # df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/sda5 ext310312504754644 9034008 8% / tmpfstmpfs 609728 0609728 0% /lib/init/rw udev tmpfs 604464 184604280 1% /dev tmpfstmpfs 609728 0609728 0% /dev/shm # fdisk -l /dev/sda #type name length base ( size ) system /dev/sda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/sda2 Apple_Bootstrap eXternal booter17408 @ 64 ( 8.5M) NewWorld bootblock /dev/sda3 Apple_UNIX_SVR2 swap 4176896 @ 17472 ( 2.0G) Linux swap /dev/sda4 Apple_Boot eXternal booter17408 @ 4194368 ( 8.5M) Unknown /dev/sda5 Apple_UNIX_SVR2 debian 20954112 @ 4211776 ( 10.0G) Linux native /dev/sda6 Apple_Free Extra 262144 @ 25165888 (128.0M) Free space /dev/sda7 Apple_HFS Apple_HFS_Untitled_3 99416240 @ 25428032 ( 47.4G) HFS /dev/sda8 Apple_Free Extra 262144 @ 124844272 (128.0M) Free space /dev/sda9 Apple_HFS Apple_HFS_Untitled_4 31195056 @ 125106416 ( 14.9G) HFS /dev/sda10 Apple_Free Extra 16 @ 156301472 ( 8.0k) Free space Block size=512, Number of Blocks=156301488 DeviceType=0x0, DeviceId=0x0 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[O] Comments/Problems: There were some errors during install boot loader yaboot: ybin: Finding OpenFirmware device path to `/dev/sda2'... ofpath: /proc/scsi/scsi does not exist ofpath: Make sure you compiled your kernel with CONFIG_SCSI_PROC_FS=y ybin: Unable to find OpenFirmware path for boot=/dev/sda2 ybin: Please add ofboot=path where path is the OpenFirmware path to /dev/sda2 to /etc/yaboot.conf ybin: Finding OpenFirmware device path to `/dev/sda9'... ofpath: /proc/scsi/scsi does not exist ofpath: Make sure you compiled your kernel with CONFIG_SCSI_PROC_FS=y ybin: Unable to determine OpenFirmware path for macosx=/dev/sda9 ybin: Try specifying the real OpenFirmware path for macosx=/dev/sda9 in /etc/yaboot.conf But after reboot system boots correctly. May be it's because I have lenny on it before squeeze installation (and may be not reformat partition with bootloader). -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20100722 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux 10 2.6.32-5-powerpc64 #1 SMP Tue Jun 1 15:09:03 UTC 2010 ppc64 GNU/Linux lspci -knn: :f0:0b.0 Host bridge [0600]: Apple Computer Inc. U3 AGP [106b:004b] lspci -knn: Kernel driver in use: agpgart-uninorth lspci -knn:
Bug#580455: marked as done (lastest Sid upgrade breakes yaboot.conf and (maybe) ybin)
Your message dated Thu, 09 Dec 2010 09:17:04 + with message-id e1pqcca-0007yn...@franck.debian.org and subject line Bug#580455: fixed in yaboot 1.3.13a-1squeeze1 has caused the Debian Bug report #580455, regarding lastest Sid upgrade breakes yaboot.conf and (maybe) ybin 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.) -- 580455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: yaboot Version: 1.3.13a-1 Severity: important The latest kernel upgrade modifies yaboot.conf in bad ways. 1) It puts spaces around the = and quotes the argument, which confuses ybin. # diff /etc/yaboot.conf.old /etc/yaboot.conf 9c9,12 boot=/dev/hda2 --- # boot = /dev/hda2 boot = /dev/disk/by-label/bootstrap 12c15,18 root=/dev/hda6 --- # root = /dev/hda6 root = UUID=88a47bea-8c36-4a09-b418-747e2396feb2 ybin thinks the space between the = and the RHS and the quotes-marks are part of the RHS. It then says that the file /dev/disk/by-label/bootstrap (including the quote-marks) doesn't exist. If I remove the quote-marks, it still fails, beacuse it thinks the leading space is part of the file name. If I remove the leading space *and* the quote marks, it gets further... But... 2) Later on, ofpath gets called on /dev/disk/by-label/bootstrap which ofpath is unable to parse. It says ofpath: Device: /dev/bootstrap is not supported. This could probably be fixed by running $boot thru readlink -f to canonicalize it, but that part of ybin is complicated enough that I decided it should be done by an expert. Hope this helps! Rick -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.32-5-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages yaboot depends on: ii libc6 2.10.2-7 Embedded GNU C Library: Shared lib Versions of packages yaboot recommends: ii hfsutils 3.2.6-11 Tools for reading and writing Maci ii powerpc-utils 1.1.3-24 Various utilities for Linux/PowerP yaboot suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: yaboot Source-Version: 1.3.13a-1squeeze1 We believe that the bug you reported is fixed in the latest version of yaboot, which is due to be installed in the Debian FTP archive: yaboot_1.3.13a-1squeeze1.diff.gz to main/y/yaboot/yaboot_1.3.13a-1squeeze1.diff.gz yaboot_1.3.13a-1squeeze1.dsc to main/y/yaboot/yaboot_1.3.13a-1squeeze1.dsc yaboot_1.3.13a-1squeeze1_powerpc.deb to main/y/yaboot/yaboot_1.3.13a-1squeeze1_powerpc.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 580...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Milan Kupcevic mi...@physics.harvard.edu (supplier of updated yaboot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 05 Dec 2010 10:34:50 -0500 Source: yaboot Binary: yaboot Architecture: source powerpc Version: 1.3.13a-1squeeze1 Distribution: testing-proposed-updates Urgency: low Maintainer: Debootloaders Yaboot Maintainers Team debootloaders-yab...@lists.alioth.debian.org Changed-By: Milan Kupcevic mi...@physics.harvard.edu Description: yaboot - Yet Another Bootloader Closes: 289201 342833 377097 572869 580455 Changes: yaboot (1.3.13a-1squeeze1) testing-proposed-updates; urgency=low . * Team upload. * Get scsi, sata, and firewire drive info from sysfs as legacy /proc/scsi interface does not exist anymore. (Closes: #572869, #377097, #342833, #289201) * Use persistent device naming symlinks, UUID and LABEL tags instead of unix block device names. (Closes: #580455) * debian/copyright: Add copyright notice from ofpath. Checksums-Sha1: 0cba98166cd23e26d083674feeffb29f5f5759b6 1469 yaboot_1.3.13a-1squeeze1.dsc 9aa43b08c6fcaeac8333d9193801568cca4b46a4 17679 yaboot_1.3.13a-1squeeze1.diff.gz
Bug#587290: marked as done (initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab)
Your message dated Thu, 09 Dec 2010 09:17:04 + with message-id e1pqcca-0007yn...@franck.debian.org and subject line Bug#580455: fixed in yaboot 1.3.13a-1squeeze1 has caused the Debian Bug report #580455, regarding initramfs-tools: malformed yaboot.conf created when alternate partitions use UUID= in fstab 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.) -- 580455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.97 Severity: important The generated /etc/yaboot.conf contains lines append=root=UUID ro for partitions that have their /etc/fstab root line using UUID=... . This makes it impossible to boot into those partitions: the boot progresses to the point of trying to mount the root filesystem and dies with Begin: Running /scripts/local-premount ... done Mount: mounting UUID on /root failed: No such directory then a few more errors obviously caused by not having a mounted root and eventually dropping into the (initrd) BusyBox shell. When I went back and changed the offending line to append=root=/dev/hda6 ro and reran ybin, everything was fine. See bug # 580455 for another aspect of the switch to UUID naming being broken on powerPC. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 9.8M Jun 26 23:48 /boot/initrd.img-2.6.32-5-powerpc -rw-r--r-- 1 root root 9.9M Jun 27 00:06 /boot/initrd.img-2.6.32-5-powerpc-smp -- /proc/cmdline root=/p...@f200/mac...@17/at...@1f000/d...@0:4 root=/dev/hda4 ro -- resume RESUME=UUID=e672ba0d-2c2e-4b03-9e4e-7a71f39c44b9 -- /proc/filesystems ext3 -- lsmod Module Size Used by uinput 10475 2 loop 16273 0 firewire_sbp2 16232 0 snd_aoa_codec_tas 13079 2 snd_aoa_fabric_layout12091 0 snd_aoa15620 2 snd_aoa_codec_tas,snd_aoa_fabric_layout snd_aoa_i2sbus 20933 1 snd_pcm67233 1 snd_aoa_i2sbus snd_timer 21510 1 snd_pcm snd_page_alloc 9053 1 snd_pcm snd53564 6 snd_aoa_codec_tas,snd_aoa_fabric_layout,snd_aoa,snd_aoa_i2sbus,snd_pcm,snd_timer soundcore 8335 1 snd snd_aoa_soundbus6669 2 snd_aoa_fabric_layout,snd_aoa_i2sbus evdev 12021 12 ext3 126551 1 jbd46110 1 ext3 mbcache 8870 1 ext3 usbhid 40424 0 hid68369 1 usbhid raid1 24559 1 md_mod 89657 1 raid1 ata_generic 5947 0 libata143752 1 ata_generic scsi_mod 128326 2 firewire_sbp2,libata ide_pci_generic 5580 0 ohci_hcd 35644 0 firewire_ohci 26292 0 ehci_hcd 43274 0 ide_cd_mod 28609 0 sungem 31621 0 firewire_core 44766 2 firewire_sbp2,firewire_ohci cdrom 36707 1 ide_cd_mod sungem_phy 12982 1 sungem crc_itu_t 4495 1 firewire_core usbcore 133556 4 usbhid,ohci_hcd,ehci_hcd i2c_powermac6651 0 nls_base8937 1 usbcore siimage 9538 2 -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip BOOT=local DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /proc/mdstat Personalities : [raid1] md127 : active (auto-read-only) raid1 hdg2[0] hdi2[1] 244198464 blocks [2/2] [UU] unused devices: none -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.32-5-powerpc-smp (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11-4 GNU cpio -- a program to manage ar ii findutils4.4.2-1 utilities for finding files--find, ii klibc-utils 1.5.18-1small utilities built with klibc f ii module-init-tools3.12~pre2-3 tools for managing Linux kernel mo ii udev 157-1 /dev/ and hotplug management daemo Versions of
Bug#606442: vimhelp-de: Doesn't work with vim 7.3
Package: vimhelp-de Version: 7.2.090923-1 Severity: serious Tags: patch Justification: Renders package unusable Hi! It seems this package doesn't work with vim 7.3, as vim 7.3 changed it's searchpath for documentation. A trivial fix seems to be changing the installation location from /usr/share/vim/vim72/doc/ to /usr/share/vim/vim73/doc/. Best regards, Alexander -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash vimhelp-de depends on no packages. Versions of packages vimhelp-de recommends: ii vim-gtk [vim 2:7.3.035+hg~8fdc1210-1 Vi IMproved - enhanced vi editor - vimhelp-de 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#600374: mokomaze: diff for NMU version 0.5.5+git8+dfsg0-0.1
tags 600374 + pending thanks Dear maintainer, I've prepared an NMU for mokomaze (versioned as 0.5.5+git8+dfsg0-0.1) and got it uploaded by Xavier Oswald (xoswald) to DELAYED/2. Please feel free to tell me if I get it delayed any longer. Regards, OdyX N.B. The debdiff being huge, I compressed it… -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens did...@raboud.com mokomaze_0.5.5+git8+dfsg0-0.1.debdiff.bz2 Description: application/bzip signature.asc Description: This is a digitally signed message part.
Processed: mokomaze: diff for NMU version 0.5.5+git8+dfsg0-0.1
Processing commands for cont...@bugs.debian.org: tags 600374 + pending Bug #600374 [mokomaze] mokomaze: uses non-free, possibly non-distributable icons Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 600374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600374 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#603427: probable fix for rc bug #603427
Hi! * Jan Wagner w...@cyconet.org [101121 12:58]: i was going through your hints and did modify the package to not introduce a new pre-depend and not using debconf to migrate the configuration and did some other improvements ... here comes the diff against the package in squeeze and a summarization: As jcristeau mentioned, you didn't had the time reviewing this patch, I gave it a shot yesterday evening and today morning and reviewed the proposed patch. While surely not being small, it addresses the core issue of the problem, and is as elegant as possible. I guess, if I would have needed to address this issue, I would have done it similar. I also tested various upgrad szenarios to verify, that the patch solves the issue. And didnt found any problems; all problems I could think of during upgrades seem to be addressed. Hope that helps, Alexander -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606048: Perdition package upgrade removes and does not regenerate .db files
I just upgraded to the latest lenny perdition package. The upgrade resulted in the /etc/perdition/popmap.*.db files being removed and not regenerated. I confirm this too. Today i upgraded from 1.17.1-2 to 1.17.1-2+lenny2 and after a reboot for a kernel upgrade, some user started complaining about authentication errors. So i observed what Tim reported. Cesare. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): tagging 588643, tagging 588443, tagging 588073
Processing commands for cont...@bugs.debian.org:
# not affecting/relevant for lenny
https://flattr.com/thing/47066/Debian-BTS-cleaning-up
Unknown command or malformed arguments to command.
tags 588643 + squeeze sid
Bug #588643 {Done: Martin Pitt mp...@debian.org} [cups] cupsd fails at launch
with symbol lookup error
Added tag(s) sid and squeeze.
tags 588443 + squeeze sid
Bug #588443 {Done: Varun Hiremath va...@debian.org} [model-builder] Fails to
start
Added tag(s) sid and squeeze.
tags 588073 + squeeze sid
Bug #588073 [src:openverse] openverse: should this package be removed?
Added tag(s) sid and squeeze.
End of message, stopping processing here.
Please contact me if you need assistance.
--
588073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588073
588443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588443
588643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588643
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#566139: libasyncns: diff for NMU version 0.3-1.1
Dear maintainer,
I've prepared an NMU for libasyncns (versioned as 0.3-1.1) and
uploaded it to unstable. Sorry for not sending the diff earlier.
Regards.
--
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~
diff -u libasyncns-0.3/debian/changelog libasyncns-0.3/debian/changelog
--- libasyncns-0.3/debian/changelog
+++ libasyncns-0.3/debian/changelog
@@ -1,3 +1,11 @@
+libasyncns (0.3-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * libasyncns/asyncns.c: Fix data alignment issue on armel, backported from
+upstream. (Closes: #566139)
+
+ -- Tanguy Ortolo tanguy+deb...@ortolo.eu Thu, 25 Nov 2010 20:55:54 +0100
+
libasyncns (0.3-1) unstable; urgency=low
* New upstream release.
only in patch2:
unchanged:
--- libasyncns-0.3.orig/libasyncns/asyncns.c
+++ libasyncns-0.3/libasyncns/asyncns.c
@@ -646,7 +646,7 @@
}
static void *unserialize_addrinfo(void *p, struct addrinfo **ret_ai, size_t *length) {
-addrinfo_serialization_t *s = p;
+addrinfo_serialization_t s;
size_t l;
struct addrinfo *ai;
assert(p);
@@ -656,7 +656,9 @@
if (*length sizeof(addrinfo_serialization_t))
return NULL;
-l = sizeof(addrinfo_serialization_t) + s-ai_addrlen + s-canonname_len;
+memcpy(s, p, sizeof(s));
+
+l = sizeof(addrinfo_serialization_t) + s.ai_addrlen + s.canonname_len;
if (*length l)
return NULL;
@@ -667,23 +669,23 @@
ai-ai_canonname = NULL;
ai-ai_next = NULL;
-if (s-ai_addrlen !(ai-ai_addr = malloc(s-ai_addrlen)))
+if (s.ai_addrlen !(ai-ai_addr = malloc(s.ai_addrlen)))
goto fail;
-if (s-canonname_len !(ai-ai_canonname = malloc(s-canonname_len)))
+if (s.canonname_len !(ai-ai_canonname = malloc(s.canonname_len)))
goto fail;
-ai-ai_flags = s-ai_flags;
-ai-ai_family = s-ai_family;
-ai-ai_socktype = s-ai_socktype;
-ai-ai_protocol = s-ai_protocol;
-ai-ai_addrlen = s-ai_addrlen;
+ai-ai_flags = s.ai_flags;
+ai-ai_family = s.ai_family;
+ai-ai_socktype = s.ai_socktype;
+ai-ai_protocol = s.ai_protocol;
+ai-ai_addrlen = s.ai_addrlen;
if (ai-ai_addr)
-memcpy(ai-ai_addr, (uint8_t*) p + sizeof(addrinfo_serialization_t), s-ai_addrlen);
+memcpy(ai-ai_addr, (uint8_t*) p + sizeof(addrinfo_serialization_t), s.ai_addrlen);
if (ai-ai_canonname)
-memcpy(ai-ai_canonname, (uint8_t*) p + sizeof(addrinfo_serialization_t) + s-ai_addrlen, s-canonname_len);
+memcpy(ai-ai_canonname, (uint8_t*) p + sizeof(addrinfo_serialization_t) + s.ai_addrlen, s.canonname_len);
*length -= l;
*ret_ai = ai;
signature.asc
Description: Digital signature
Processed: Re: IOError: failed to write data
Processing commands for cont...@bugs.debian.org: tag 598143 moreinfo unreproducible Bug #598143 [libapache2-mod-wsgi] IOError: failed to write data Added tag(s) unreproducible and moreinfo. severity 598143 important Bug #598143 [libapache2-mod-wsgi] IOError: failed to write data Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 598143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598143 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#606442: vimhelp-de: Doesn't work with vim 7.3
On 2010-12-09 10:37 +0100, Alexander Reichle-Schmehl wrote: Package: vimhelp-de Version: 7.2.090923-1 Severity: serious Tags: patch Justification: Renders package unusable It seems this package doesn't work with vim 7.3, as vim 7.3 changed it's searchpath for documentation. A trivial fix seems to be changing the installation location from /usr/share/vim/vim72/doc/ to /usr/share/vim/vim73/doc/. Which will break with the vim packages in squeeze, since they are still at 7.2, as well as with future vim 7.4/8.0/whatever releases. Some versioned dependency seems to be in order, but for squeeze the bug could probably be ignored (e.g. by adding a 'sid' tag). Regards, Sven -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598463: Alive
Never-mind, there has already been a potential patch emailed in that thread (that Soren linked to). -- 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#603427: probable fix for rc bug #603427
Processing commands for cont...@bugs.debian.org:
retitle 603427 unblock: ipplan/4.92a-2
Bug #603427 {Done: Jan Wagner w...@cyconet.org} [ipplan] ipplan: prompting
due to modified conffiles which where not modified by the user
Changed Bug title to 'unblock: ipplan/4.92a-2' from 'ipplan: prompting due to
modified conffiles which where not modified by the user'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
603427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603427
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#603427: probable fix for rc bug #603427
retitle 603427 unblock: ipplan/4.92a-2 thanks On Thursday 09 December 2010 11:10:09 Alexander Reichle-Schmehl wrote: While surely not being small, it addresses the core issue of the problem, and is as elegant as possible. I guess, if I would have needed to address this issue, I would have done it similar. I also tested various upgrad szenarios to verify, that the patch solves the issue. And didnt found any problems; all problems I could think of during upgrades seem to be addressed. I uploaded the package some minutes ago, please unblock it. * Implement proper configuration handling (Closes: #603427) - Add ucf to Depends - Write database settings from old config file into /etc/ipplan/db.php - Register /etc/ipplan/db.php via ucf in postinst - Deregister /etc/ipplan/db.php via ucf and remove variants in postrm on purge - Migrate /etc/ipplan/config.php to /etc/ipplan/local_conf.php, if user has modified the file - Adjust README.Debian related to our new way to configure ipplan * Add 11_user_config.dpatch to patch shipped config to also read our config files * Add 05_fix_config_syntax.dpatch to fix broken default config * Only call postinst and config if we install the package or on dpkg-reconfigure * Copy template of local_conf.php to /etc/ipplan/ via postinst if there isn't one yet * Remove /etc/ipplan/local_conf.php on purge -- Jan Wagner w...@cyconet.org Thu, 09 Dec 2010 11:56:13 +0100 Thanks in advance. unblock: ipplan/4.92a-2 -- Never write mail to w...@spamfalle.info, you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y --END GEEK CODE BLOCK-- signature.asc Description: This is a digitally signed message part.
Bug#605731: rsync client can no longer handle rsync:// targets
Hi, The problem resolved down to rsync 3.0.3-2 accepting the following: rsync rsync://server::module and 3.0.7-2 does not. That 3.0.3-2 accepted that syntax was an undocumented feature. How about adding it to NEWS.Debian? If someone has already installed apt-listchanges, it helps him/her. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606327: vmmemctl missing in squeeze
On 08/12/2010 23:49, Daniel Baumann wrote: On 12/08/2010 10:14 PM, Mehdi Dogguy wrote: Could you please provide a reasonable fix for this bug? the correct fix is to upload open-vm-tools 8.4.2-261024. will you accept this new-old upstream release for squeeze? Yes. Go ahead. If you want to apply some backported fixes, please let us know first. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 588017, tagging 587668, tagging 587664, tagging 587482
Processing commands for cont...@bugs.debian.org: tags 588017 + lenny-ignore Bug #588017 [perl] perl: current directory in @INC potentially harmful Added tag(s) lenny-ignore. # not relevant for squeeze, not relevant for lenny; approved by release team tags 587668 + lenny-ignore Bug #587668 [desktop-base] The Debian open logo with Debian is not compliant to the Debian policy Added tag(s) lenny-ignore. tags 587664 + lenny-ignore Bug #587664 [gdm] The Debian open logo with Debian is not compliant to the Debian policy Added tag(s) lenny-ignore. tags 587482 + lenny-ignore Bug #587482 [gdm-themes] The Debian open logo with Debian is not compliant to the Debian policy Added tag(s) lenny-ignore. End of message, stopping processing here. Please contact me if you need assistance. -- 587482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587482 587664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587664 587668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587668 588017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588017 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#606327: vmmemctl missing in squeeze
On 12/09/2010 12:54 PM, Mehdi Dogguy wrote: Yes. Go ahead. If you want to apply some backported fixes, please let us know first. for clarity sake, it's not about 'backporting' fixes, it's about completely replacing the existing open-vm-tools upstream version with another one. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.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
Bug#606327: vmmemctl missing in squeeze
On 09/12/2010 13:05, Daniel Baumann wrote: On 12/09/2010 12:54 PM, Mehdi Dogguy wrote: Yes. Go ahead. If you want to apply some backported fixes, please let us know first. for clarity sake, it's not about 'backporting' fixes, it's about completely replacing the existing open-vm-tools upstream version with another one. Yes. What I meant is: if you see some worthy fixes in current sid's version that should be backported to the one you're going to upload, it could be ok but please let us know first. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#603982: unblock: unscd/0.47-1 (New Package)
Processing commands for cont...@bugs.debian.org: tags 574990 + squeeze-ignore Bug #574990 [nscd] nscd crashes after moderate use Added tag(s) squeeze-ignore. thanks Stopping processing here. Please contact me if you need assistance. -- 574990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574990 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#574990: Bug#603982: unblock: unscd/0.47-1 (New Package)
to make life easier for people in the future :) On Donnerstag, 9. Dezember 2010, Mehdi Dogguy wrote: tags 574990 + squeeze-ignore [...] Anyway… [unscd]'s unblocked now and will migrate to Squeeze tonight. I'm also squeeze-ignoring 574990 since I don't imagine it to be fixed in time, and now that we have a replacement. I hope that we won't discover critical issues in unscd that will affect Squeeze… signature.asc Description: This is a digitally signed message part.
Bug#562234: Cache file location in violation of FHS
On Thu, Dec 09, 2010 at 08:46:50AM +0100, Goswin von Brederlow wrote: In what case does it break? That's the wrong question:) You should ask: Under what conditions are its hard-coded assumptions about LVM metadata true? Alasdair -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605151: marked as done (snappea: Use of PYTHONPATH env var in an insecure way)
Your message dated Thu, 09 Dec 2010 12:47:30 +
with message-id e1pqfue-0005ux...@franck.debian.org
and subject line Bug#605151: fixed in snappea 3.0d3-20.1
has caused the Debian Bug report #605151,
regarding snappea: Use of PYTHONPATH env var in an insecure way
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.)
--
605151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: snappea
Version: 3.0d3-20
Severity: grave
Tags: security
User: debian-pyt...@lists.debian.org
Usertags: pythonpath
Jakub Wilk performed an analysis[1] for packages setting PYTHONPATH in
an insecure way. Those packages do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory would be added to sys.path.
[1] http://lists.debian.org/debian-python/2010/11/msg00045.html
Your package turns out to have vulnerable scripts in PATH: you can
find a complete log at [2].
[2] http://people.debian.org/~morph/mbf/pythonpath.txt
Some guidelines on how to fix these bugs: in the case given above, you
can use something like
PYTHONPATH=/spam/eggs${PYTHONPATH:+:$PYTHONPATH}
(If you don't known this construct, grep for Use Alternative Value
in the bash/dash manpage.)
Also, in cases like
PYTHONPATH=/usr/lib/python2.5/site-packages/:$PYTHONPATH
or
PYTHONPATH=$PYTHONPATH:$SPAMDIR exec python $SPAMDIR/spam.py
you shouldn't need to touch PYTHONPATH at all.
Feel free to contact debian-pyt...@lists.debian.org in case of
help.
---End Message---
---BeginMessage---
Source: snappea
Source-Version: 3.0d3-20.1
We believe that the bug you reported is fixed in the latest version of
snappea, which is due to be installed in the Debian FTP archive:
snappea-dev_3.0d3-20.1_amd64.deb
to main/s/snappea/snappea-dev_3.0d3-20.1_amd64.deb
snappea_3.0d3-20.1.diff.gz
to main/s/snappea/snappea_3.0d3-20.1.diff.gz
snappea_3.0d3-20.1.dsc
to main/s/snappea/snappea_3.0d3-20.1.dsc
snappea_3.0d3-20.1_amd64.deb
to main/s/snappea/snappea_3.0d3-20.1_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 605...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ansgar Burchardt ans...@debian.org (supplier of updated snappea 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: SHA512
Format: 1.8
Date: Thu, 02 Dec 2010 13:15:42 +0100
Source: snappea
Binary: snappea snappea-dev
Architecture: amd64 source
Version: 3.0d3-20.1
Distribution: unstable
Urgency: low
Maintainer: Ben Burton b...@debian.org
Changed-By: Ansgar Burchardt ans...@debian.org
Closes: 605151
Description:
snappea- a program for creating and studying hyperbolic 3-manifolds
snappea-dev - development files for SnapPea hyperbolic 3-manifold tool
Changes:
snappea (3.0d3-20.1) unstable; urgency=low
.
* Non-maintainer upload.
* Set PYTHONPATH in a secure way. (Closes: #605151)
* Change doc-base section to Science/Mathematics.
* debian/control: Add ${misc:Depends}.
Checksums-Sha1:
39060f31cffc6929ed5edc6dfa48f902818885a6 1685 snappea_3.0d3-20.1.dsc
bf277ea9ef82b0c8bf7ef1c4259f76b031b52ed4 641019 snappea_3.0d3-20.1.diff.gz
8aa50d64d96457ee5b0f56aad03280f40c47819a 638954 snappea_3.0d3-20.1_amd64.deb
de9e00630668027905a060ea656869972af3afec 292142
snappea-dev_3.0d3-20.1_amd64.deb
Checksums-Sha256:
daec50c380ecce269be69a721a19479de02b5ba3a845c6ba06d654957cb2b0a9 1685
snappea_3.0d3-20.1.dsc
c279858ab955320eea4a4fe39b3c3738ad0b2ab335eb1009d43c6843762ac917 641019
snappea_3.0d3-20.1.diff.gz
a205d76f3ec32ccdbd95ede6122e68553df68fd9ea584e800745d9e30da8736a 638954
snappea_3.0d3-20.1_amd64.deb
01ed1b49cbb5bd3a168a62f67064eaa5b2000e9241720f4e2636d31d66c802b4 292142
snappea-dev_3.0d3-20.1_amd64.deb
Files:
4867c81c7fc1645ad97f5ab5b5f99564 1685 math extra snappea_3.0d3-20.1.dsc
d7db8beec35e8fbdd2036e2536df53cf 641019 math extra snappea_3.0d3-20.1.diff.gz
ee14d74e74a3d13accc4bd885b18c644 638954 math extra snappea_3.0d3-20.1_amd64.deb
23358cc4f231c19109fbfa0f4f468d20 292142 libdevel extra
snappea-dev_3.0d3-20.1_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Processed: tagging 606442
Processing commands for cont...@bugs.debian.org: tags 606442 sid Bug #606442 [vimhelp-de] vimhelp-de: Doesn't work with vim 7.3 Added tag(s) sid. End of message, stopping processing here. Please contact me if you need assistance. -- 606442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606442 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: Re: k3b: Finds negative file length and spoils DVD
Processing commands for cont...@bugs.debian.org: fixed 606238 2.0.0-1 Bug #606238 [k3b] k3b: Finds negative file length and spoils DVD Bug Marked as fixed in versions k3b/2.0.0-1. thanks Stopping processing here. Please contact me if you need assistance. -- 606238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606238 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#606238: marked as done (k3b: Finds negative file length and spoils DVD)
Your message dated Thu, 9 Dec 2010 22:28:59 +0900 with message-id 20101209222859.5b62eed0.henr...@debian.or.jp and subject line Re: k3b: Finds negative file length and spoils DVD has caused the Debian Bug report #606238, regarding k3b: Finds negative file length and spoils DVD 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.) -- 606238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: k3b Version: 1.0.5-3 Severity: grave Justification: renders package unusable I try to burn a 4.4 GB file to DVD-R (this would leave 9 MB free, if I were able to burn the DVD). However, k3b reads the file length as -268,226,557 MB in the dialogue box - please note the negative number. The graph at the bottom shows the bar at the right length though, and correctly reports 4.4 GB. In the dialogue box, it almost immediately goes to closing disk, stays there for several minutes, and then signals write error. The directory entry on DVD shows correctly 4,697,620,480 bytes, although the written file is only 663,551 bytes long, and I am left with nothing than a spoiled DVD. Debug info follows. System --- K3b Version: 1.0.5 KDE Version: 3.5.10 QT Version: 3.3.8b Kernel: 2.6.32-bpo.5-686 Devices --- HL-DT-ST DVD-RAM GH40L 1.04 (/dev/sr0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R96R, Restricted Overwrite, Layer Jump] Burned media --- DVD-R Sequential K3bIsoImager --- mkisofs print size result: 2294179 (4698478592 bytes) Pipe throughput: 34881536 bytes read, 34877088 bytes written. Used versions --- mkisofs: 1.1.9 growisofs: 7.1 growisofs --- Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0' /dev/sr0: Current Write Speed is 16.4x1352KBps. :-[ wr...@lba=250h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid argument :-( write failed: Invalid argument /dev/sr0: flushing cache /dev/sr0: updating RMA /dev/sr0: closing disc growisofs command: --- /usr/bin/growisofs -Z /dev/sr0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=tracksize:2294179 -dvd-compat -speed=16 -use-the-force-luke=bufsize:32m mkisofs --- 2294179 I: -input-charset not specified, using utf-8 (detected in locale settings) This size can only be represented in the UDF filesystem. Make sure that your clients support and use it. ISO9660, Joliet, RockRidge, HFS will display incorrect size. 0.02% done, estimate finish Tue Dec 7 10:29:26 2010 0.04% done, estimate finish Tue Dec 7 10:29:26 2010 0.07% done, estimate finish Tue Dec 7 10:54:55 2010 0.09% done, estimate finish Tue Dec 7 10:48:26 2010 0.11% done, estimate finish Tue Dec 7 10:44:40 2010 0.13% done, estimate finish Tue Dec 7 10:54:53 2010 0.15% done, estimate finish Tue Dec 7 10:51:16 2010 0.17% done, estimate finish Tue Dec 7 10:48:29 2010 0.20% done, estimate finish Tue Dec 7 10:54:52 2010 0.22% done, estimate finish Tue Dec 7 10:52:21 2010 0.24% done, estimate finish Tue Dec 7 10:50:17 2010 0.26% done, estimate finish Tue Dec 7 10:48:30 2010 0.28% done, estimate finish Tue Dec 7 10:47:03 2010 0.31% done, estimate finish Tue Dec 7 10:45:48 2010 0.33% done, estimate finish Tue Dec 7 10:44:43 2010 0.35% done, estimate finish Tue Dec 7 10:43:45 2010 0.37% done, estimate finish Tue Dec 7 10:42:54 2010 0.39% done, estimate finish Tue Dec 7 10:42:10 2010 0.41% done, estimate finish Tue Dec 7 10:45:31 2010 0.44% done, estimate finish Tue Dec 7 10:44:42 2010 0.46% done, estimate finish Tue Dec 7 10:43:59 2010 0.48% done, estimate finish Tue Dec 7 10:43:19 2010 0.50% done, estimate finish Tue Dec 7 10:42:43 2010 0.52% done, estimate finish Tue Dec 7 10:42:09 2010 0.55% done, estimate finish Tue Dec 7 10:41:39 2010 0.57% done, estimate finish Tue Dec 7 10:41:11 2010 0.59% done, estimate finish Tue Dec 7 10:40:45 2010 0.61% done, estimate finish Tue Dec 7 10:40:20 2010 0.63% done, estimate finish Tue Dec 7 10:39:58 2010 0.65% done, estimate finish Tue Dec 7 10:42:10 2010 0.68% done, estimate finish Tue Dec 7 10:41:46 2010 0.70% done, estimate finish Tue Dec 7 10:41:22 2010 0.72% done, estimate finish
Bug#603986: qgis crashes on startup on PowerPC
On Sat, 4 Dec 2010 12:47:20 -0500 Steve ssinger...@sympatico.ca wrote: If I build the qgis .deb files from source on my machine I don't get the crash but the debs from the repository always crash. Is it possible to force a rebuild of the .debs in testing? Interesting, I cannot reproduce it, always crash with - packages from repository - packages built with pbuilder (sid) - packages built with pbuilder (squeeze) - source from git, built with pbuilder (sid) - source from git, built with pbuilder (squeeze) Steve, how do you build your deb files? -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603429: hylafax-server: prompting due to modified conffiles which where not modified by the user
On Wed, 08 Dec 2010 19:38:40 +0100, gregor herrmann wrote: leave it at 1 and do not touch it anymore. Ok, might be less intrusive and simpler than the ucf option. And just wrapping the last part of the postinst into a block checking if the default-file exists should work. Attached is a draft for this change. The init.d script should be changed in order to warn the user when action is start and the flag is at 0, the start action should return a 0 status in order to have upgrade script working correctly, isn't it? Right. That's already in the init script, as far as I can see. 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: Peter Ratzenbeck: Foggey Dew diff -Nru hylafax-6.0.5/debian/changelog hylafax-6.0.5/debian/changelog --- hylafax-6.0.5/debian/changelog 2010-12-07 17:42:55.0 +0100 +++ hylafax-6.0.5/debian/changelog 2010-12-09 13:52:45.0 +0100 @@ -1,3 +1,12 @@ +hylafax (2:6.0.5-4.2) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Fix prompting due to modified conffiles which where not modified by +the user: write to /etc/default/hylafax only if it doesn't exist +(closes: #603429). + + -- gregor herrmann gre...@debian.org Thu, 09 Dec 2010 13:50:21 +0100 + hylafax (2:6.0.5-4.1) UNRELEASED; urgency=low * Non-maintainer upload. diff -Nru hylafax-6.0.5/debian/hylafax-server.hylafax.default hylafax-6.0.5/debian/hylafax-server.hylafax.default --- hylafax-6.0.5/debian/hylafax-server.hylafax.default 2010-08-13 23:11:55.0 +0200 +++ hylafax-6.0.5/debian/hylafax-server.hylafax.default 1970-01-01 01:00:00.0 +0100 @@ -1,56 +0,0 @@ -# default settings for hylafax server - -# try to check for the correct USE_FAXGETTY value -if grep -E '^[^#]*:respawn:/usr/sbin/fax(getty|modem).*$' /etc/inittab /dev/null 21 || grep -E '^exec[ \t]*/usr/sbin/fax(getty|modem)' /etc/init/*.conf /dev/null 21 -then - USE_FAXGETTY=init -else - USE_FAXGETTY=yes -fi - -# Arguments for faxgetty command. At least -D should be specified -# as explained in debian bug #462459. -FAXGETTYARGS=-D - -# In a send only installation you may want to use faxgetty -# or faxmodem on lines already configured with faxaddmodem. -# faxgetty is the new default, faxmodem the old one. -# For a better understanding of the difference between faxmodem -# and faxgetty, see http://www.hylafax.org/archive/1999-09/msg00043.php -# -# In a send/receive installation you must use faxgetty. -# -# To use faxmodem change the following variable value to no. -# -# You may also prefer to run faxmodem/faxgetty via inittab instead of -# running it here from a script. In this case set its value as -# init. -# USE_FAXGETTY=yes - -# -# Uncomment this line once hylafax has been fully configured and/or -# you want to enable the server. -# -# RUN_HYLAFAX=1 - -# -# If you need to bind hylafax to one address only, just uncomment -# this variable and change the value using your preferred IP. -# -# BINDTO=-l 127.0.0.1 - -# -# The following variables are automatically assigned by running -# the faxsetup utility. If you leave them commented out then -# faxsetup values are used. You may specify here the values to -# use. -# -# OLDPROT=-o 4557 -# NEWPROT=-i 4559 -# SNPP=-s 444 - -# -# hfaxd may be run from inetd while faxq should still be executed -# by the init script. If you run hfax via inetd or xinetd then -# uncomment the following line -# HFAXD_FROM_INET=true diff -Nru hylafax-6.0.5/debian/hylafax-server.hylafax.default-maintainer hylafax-6.0.5/debian/hylafax-server.hylafax.default-maintainer --- hylafax-6.0.5/debian/hylafax-server.hylafax.default-maintainer 1970-01-01 01:00:00.0 +0100 +++ hylafax-6.0.5/debian/hylafax-server.hylafax.default-maintainer 2010-12-09 13:48:59.0 +0100 @@ -0,0 +1,56 @@ +# default settings for hylafax server + +# try to check for the correct USE_FAXGETTY value +if grep -E '^[^#]*:respawn:/usr/sbin/fax(getty|modem).*$' /etc/inittab /dev/null 21 || grep -E '^exec[ \t]*/usr/sbin/fax(getty|modem)' /etc/init/*.conf /dev/null 21 +then + USE_FAXGETTY=init +else + USE_FAXGETTY=yes +fi + +# Arguments for faxgetty command. At least -D should be specified +# as explained in debian bug #462459. +FAXGETTYARGS=-D + +# In a send only installation you may want to use faxgetty +# or faxmodem on lines already configured with faxaddmodem. +# faxgetty is the new default, faxmodem the old one. +# For a better understanding of the difference between faxmodem +# and faxgetty, see http://www.hylafax.org/archive/1999-09/msg00043.php +# +# In a send/receive installation you must use faxgetty. +# +# To use faxmodem change the following variable value to no. +# +# You may also prefer to run faxmodem/faxgetty via inittab instead of +# running it here from a script. In this case set its value as
Processed: Re: Bug#606442: vimhelp-de: Doesn't work with vim 7.3
Processing commands for cont...@bugs.debian.org: clone 606442 -1 Bug#606442: vimhelp-de: Doesn't work with vim 7.3 Bug 606442 cloned as bug 606468. retitle -1 vimhelp-de should use some kind of versioned dependencies Bug #606468 [vimhelp-de] vimhelp-de: Doesn't work with vim 7.3 Changed Bug title to 'vimhelp-de should use some kind of versioned dependencies' from 'vimhelp-de: Doesn't work with vim 7.3' severity -1 important Bug #606468 [vimhelp-de] vimhelp-de should use some kind of versioned dependencies Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 606468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606468 606442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606442 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 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#606442: vimhelp-de: Doesn't work with vim 7.3
clone 606442 -1 retitle -1 vimhelp-de should use some kind of versioned dependencies severity -1 important thanks Am 09.12.2010 11:47, schrieb Sven Joachim: A trivial fix seems to be changing the installation location from /usr/share/vim/vim72/doc/ to /usr/share/vim/vim73/doc/. Which will break with the vim packages in squeeze, since they are still at 7.2, as well as with future vim 7.4/8.0/whatever releases. Some versioned dependency seems to be in order, but for squeeze the bug could probably be ignored (e.g. by adding a 'sid' tag). Oh, good catch. Hadn't noticed, that sid and squeeze have different vim versions. Regarding the versioned dependency / conflicts / whatever, we where discussing that that very minute on IRC. So let's make it a separate bug so it isn't forgotten. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603450: Is 603450 realy release critical?
On Wed, 08 Dec 2010 08:45:30 +0100, Alexander Reichle-Schmehl wrote: There's patch floating arround, which has a major regression: It doesn't work for users of self signed certificates. FWIW: As an offlineimap user I'd be very unhappy if it stopped working with my IMAP server with its self-signed certificate. 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: Bob Dylan: Cold Irons Bound signature.asc Description: Digital signature
Processed: tagging 605167
Processing commands for cont...@bugs.debian.org: tags 605167 + patch Bug #605167 [gnome-schedule] gnome-schedule: Use of PYTHONPATH env var in an insecure way Bug #605169 [gnome-schedule] gnome-schedule: Use of PYTHONPATH env var in an insecure way Added tag(s) patch. Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 605167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605167 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#589048: Corrected symbols file for i386
Hi, Attached is a symbols file that works on i386, and with some luck on the other 32 bit architecture. Not sure about BSD, IIRC something more is necessary, but dealing with non-c++ symbol files is IMO quite impossible... cheers -- vbi -- The following expression sorts a word list stored in matrix X according to word length: X[⍋X+.≠' ';] -- http://en.wikipedia.org/wiki/APL_(programming_language) liblensfun.so.0 liblensfun0 #MINVER# (c++|regex)_lf_addobj\(void\*\*\*, void const\*, unsigned (long|int), bool \(\*\)\(void const\*, void const\*\)\)@Base 0.2.3 (c++)_lf_addstr(char***, char const*)@Base 0.2.3 (c++)_lf_delobj(void***, int)@Base 0.2.3 (c++)_lf_setstr(char**, char const*)@Base 0.2.3 (c++)_lf_strcmp(char const*, char const*)@Base 0.2.3 (c++)_lf_mlstrcmp(char const*, char*)@Base 0.2.3 (c++)_lf_list_free(void**)@Base 0.2.3 (c++)_lf_xml_printf(_GString*, char const*, ...)@Base 0.2.3 (c++)_lf_interpolate(float, float, float, float, float)@Base 0.2.3 (c++)_lf_lens_compare(void const*, void const*)@Base 0.2.3 (c++)_lf_mount_compare(void const*, void const*)@Base 0.2.3 (c++)_lf_camera_compare(void const*, void const*)@Base 0.2.3 (c++)_lf_xml_printf_mlstr(_GString*, char const*, char const*, char*)@Base 0.2.3 (c++)_lf_lens_compare_score(lfLens const*, lfLens const*, lfFuzzyStrCmp*, char const**)@Base 0.2.3 (c++)_lf_detect_cpu_features()@Base 0.2.5 (c++)_lf_ptr_array_find_sorted(_GPtrArray const*, void*, int (*)(void const*, void const*))@Base 0.2.3 (c++)_lf_ptr_array_insert_sorted(_GPtrArray*, void*, int (*)(void const*, void const*))@Base 0.2.3 (c++)_lf_ptr_array_insert_unique(_GPtrArray*, void*, int (*)(void const*, void const*), void (*)(void*))@Base 0.2.3 #MISSING: 0.2.5# (c++)_lf_rt3(double)@Base 0.2.3 (c++)lfDatabase::Load(char const*)@Base 0.2.3 (c++|regex)lfDatabase::Load\(char const\*, char const\*, unsigned (int|long)\)@Base 0.2.3 (c++)lfDatabase::Load()@Base 0.2.3 (c++)lfDatabase::Save(lfMount const* const*, lfCamera const* const*, lfLens const* const*)@Base 0.2.3 (c++)lfDatabase::Create()@Base 0.2.3 (c++)lfDatabase::Destroy()@Base 0.2.3 (c++)lfModifier::Initialize(lfLens const*, lfPixelFormat, float, float, float, float, lfLensType, int, bool)@Base 0.2.3 (c++)lfModifier::GetAutoScale(bool)@Base 0.2.3 (c++|regex)lfModifier::AddColorCallback\(void \(\*\)\(void\*, float, float, void\*, int, int\), int, void\*, unsigned (long|int)\)@Base 0.2.3 (c++|regex)lfModifier::AddCoordCallback\(void \(\*\)\(void\*, float\*, int\), int, void\*, unsigned (long|int)\)@Base 0.2.3 (c++)lfModifier::AddColorCallbackCCI(lfLens const*, lfPixelFormat, bool)@Base 0.2.3 (c++|regex)lfModifier::AddSubpixelCallback\(void \(\*\)\(void\*, float\*, int\), int, void\*, unsigned (long|int)\)@Base 0.2.3 (c++)lfModifier::AddCoordCallbackScale(float, bool)@Base 0.2.3 (c++)lfModifier::AddSubpixelCallbackTCA(lfLensCalibTCA, bool)@Base 0.2.3 (c++)lfModifier::AddCoordCallbackGeometry(lfLensType, lfLensType, float)@Base 0.2.3 (c++)lfModifier::AddColorCallbackVignetting(lfLensCalibVignetting, lfPixelFormat, bool)@Base 0.2.3 (c++)lfModifier::AddCoordCallbackDistortion(lfLensCalibDistortion, bool)@Base 0.2.3 (c++)lfModifier::Create(lfLens const*, float, int, int)@Base 0.2.3 (c++)lfModifier::Destroy()@Base 0.2.3 (c++|regex)lfExtModifier::AddCallback\(_GPtrArray\*, lfCallbackData\*, int, void\*, unsigned (long|int)\)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_Scale(void*, float*, int)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_Dist_FOV1(void*, float*, int)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_TCA_Poly3(void*, float*, int)@Base 0.2.5 (c++)lfExtModifier::ModifyCoord_Dist_Poly3(void*, float*, int)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_Dist_Poly5(void*, float*, int)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_TCA_Linear(void*, float*, int)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_Dist_PTLens(void*, float*, int)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_UnDist_FOV1(void*, float*, int)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_UnTCA_Poly3(void*, float*, int)@Base 0.2.5 (c++)lfExtModifier::ModifyCoord_UnDist_Poly3(void*, float*, int)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_UnDist_Poly5(void*, float*, int)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_UnTCA_Linear(void*, float*, int)@Base 0.2.3 (c++)void lfExtModifier::ModifyColor_Vignetting_PAdouble(void*, float, float, double*, int, int)@Base 0.2.3 (c++)void lfExtModifier::ModifyColor_Vignetting_PAfloat(void*, float, float, float*, int, int)@Base 0.2.3 (c++)void lfExtModifier::ModifyColor_Vignetting_PAunsigned char(void*, float, float, unsigned char*, int, int)@Base 0.2.3 (c++)void lfExtModifier::ModifyColor_Vignetting_PAunsigned int(void*, float, float, unsigned int*, int, int)@Base 0.2.3 (c++)void lfExtModifier::ModifyColor_Vignetting_PAunsigned short(void*, float, float, unsigned short*, int, int)@Base 0.2.3 (c++)lfExtModifier::ModifyCoord_UnDist_PTLens(void*, float*, int)@Base 0.2.3
Bug#604234: unreproducable
On Tue, 07 Dec 2010 15:49:44 +0100, Holger Levsen wrote:
http://piuparts.debian.org/sid/pass/emacspeak-ss_1.12.1-1.log and
http://piuparts.debian.org/squeeze/pass/emacspeak-ss_1.12.1-1.log are both
examples of successful installations.
Also please note that the above logs are from June+September, I've just
rescheduled them for testing again and they both passed. These logs will be
available from tomorrow at the same URLs.
Both logs show success.
But I can reproduce the problem quite easily:
$ sudo cowbuilder --login
# apt-get install emacspeak-ss
...
Fetched 35.9 MB in 1min 1s (579 kB/s)
Extracting templates from packages: 100%
Preconfiguring packages ...
Use of uninitialized value $_[1] in join or string at
/usr/share/perl5/Debconf/Client/ConfModule.pm line 121, STDIN line 14.
Use of uninitialized value $_[1] in join or string at
/usr/share/perl5/Debconf/Client/ConfModule.pm line 121, STDIN line 16.
The hanging process seems to be
/usr/bin/perl -w /tmp/emacspeak.config.96593 configure
Looks more like emacspeak than emacspeak-ss; but `apt-get install
emacspeak' succeeds, after showing the same warnings.
After that I can install emacspeak-ss without problems.
Hm.
Ok, let's try manually:
# /tmp/emacspeak.config.96593 configure
Use of uninitialized value $device in hash element at
/tmp/emacspeak.config.322673 line 62, STDIN line 3.
Use of uninitialized value $device in hash element at
/tmp/emacspeak.config.322673 line 63, STDIN line 3.
Use of uninitialized value $device in hash element at
/tmp/emacspeak.config.322673 line 64, STDIN line 3.
Use of uninitialized value $p in concatenation (.) or string at
/tmp/emacspeak.config.322673 line 65, STDIN line 3.
Use of uninitialized value $t in concatenation (.) or string at
/tmp/emacspeak.config.322673 line 65, STDIN line 3.
Use of uninitialized value $device in hash element at
/tmp/emacspeak.config.322673 line 65, STDIN line 3.
^C
Adding some debug output to /tmp/emacspeak.config.96593 we see that $choices
contains
'shared/emacspeak/database doesn\'t exist' and $database too.
If I guard this block with an if-conditional I later get an infinite
loop in the while (!$valid) loop. $port contains
'shared/emacspeak/port doesn\'t exist'. Setting it to none (which
is the default anyway?!) let's the config script finish.
Just for reference, I'm attaching the changes mentioned above. With
this change I can install emacspeak and emacspeak-ss with dpkg in the
cowbuilder chroot.
But I'm still not sure if this is a problem in emacspeak or in
emacspeak-ss (since emacspeak alone installs). And in general I don't
really understand what's going in here ...
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: Bob Dylan: Shelter From The Storm
diff -u emacspeak-29.0/debian/config emacspeak-29.0/debian/config
--- emacspeak-29.0/debian/config
+++ emacspeak-29.0/debian/config
@@ -56,13 +56,15 @@
my ($b, $p, $t, $device, $olddevice,
%blurb, %program, %tcl, %device, %db, $devicelist);
($ret, $database) = metaget ('shared/emacspeak/database', 'choices');
-foreach (split (/, */, $database)){ # debconf database is comma separated
-($b, $p, $t, $device)=split(/:/);
-# load data into hashes
-$blurb{$device}=$b;
-$program{$device}=$p;
-$tcl{$device}=$t;
-$db{$device}=$b:$p:$t; # local database is colon separated
+if ($database ne 'shared/emacspeak/database doesn\'t exist') {
+ foreach (split (/, */, $database)){ # debconf database is comma separated
+ ($b, $p, $t, $device)=split(/:/);
+ # load data into hashes
+ $blurb{$device}=$b;
+ $program{$device}=$p;
+ $tcl{$device}=$t;
+ $db{$device}=$b:$p:$t; # local database is colon separated
+ }
}
# Add choices from unpacked .blurb files from other packages, in case
@@ -182,6 +184,7 @@
while (!$valid) {
input('high', 'shared/emacspeak/port'); go();
$port=get('shared/emacspeak/port');
+$port = none if $port eq 'shared/emacspeak/port doesn\'t exist';
if (($port eq none) || (-c $port)){
$valid=1;
} else {
signature.asc
Description: Digital signature
Bug#606481: python-peak.util: missing pointer to upstream sources
Source: python-peak.util Version: 20090610-2 Severity: serious Justification: Debian Policy 12.5; Squeeze RC Policy 1 debian/copyright doesn't say say where the upstream sources were obtained. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603552: Bug#603554: Bug#603552: Update theme SpaceFun and wiki page
On Wed, Dec 08, 2010 at 07:29:40PM +0100, Yves-Alexis Perez wrote: On mer., 2010-12-08 at 19:12 +0100, Daniel Baumann wrote: On 12/08/2010 07:10 PM, Daniel Baumann wrote: i think we have a missunderstanding here, spacefun will not be part of plymouth-themes-debian, it's in desktop-base only. sorry, ignore that.. i was answering plymouth related mails above. regarding squeeze, i'll only sync those from debian-cd, so if debian-cd uses the correct things, so will syslinux-themes-debian. Nice to know that. Adding the debian-cd bug to the list then. For debian-cd people, the SpaceFun isolinux artwork is at http://svn.debianart.org/themes/spacefun/isolinux/ Do you plan to include it? There's nothing needed in debian-cd at all; we just include whatever graphics are provided by the d-i folks. -- Steve McIntyre, Cambridge, UK.st...@einval.com You lock the door And throw away the key There's someone in my head but it's not me -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package rtorrent
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package rtorrent # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #605863 (http://bugs.debian.org/605863) # * http://libtorrent.rakshasa.no/ticket/2411 # * remote status changed: (?) - closed # * remote resolution changed: (?) - invalid # * closed upstream tags 605863 + fixed-upstream Bug #605863 [rtorrent] rtorrent/experimental crashes when any rpc command is received Added tag(s) fixed-upstream. usertags 605863 + status-closed resolution-invalid Bug#605863: rtorrent/experimental crashes when any rpc command is received There were no usertags set. Usertags are now: resolution-invalid status-closed. thanks Stopping processing here. Please contact me if you need assistance. -- 605863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605863 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#603554: marked as done (update isolinux theme for squeeze)
Your message dated Thu, 9 Dec 2010 16:36:47 + with message-id 20101209163647.gb11...@einval.com and subject line Re: Bug#603554: Bug#603552: Update theme SpaceFun and wiki page has caused the Debian Bug report #603554, regarding update isolinux theme for squeeze 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.) -- 603554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-cd Severity: serious please update isolinux theme for squeeze (space fun). -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ ---End Message--- ---BeginMessage--- On Wed, Dec 08, 2010 at 07:29:40PM +0100, Yves-Alexis Perez wrote: On mer., 2010-12-08 at 19:12 +0100, Daniel Baumann wrote: On 12/08/2010 07:10 PM, Daniel Baumann wrote: i think we have a missunderstanding here, spacefun will not be part of plymouth-themes-debian, it's in desktop-base only. sorry, ignore that.. i was answering plymouth related mails above. regarding squeeze, i'll only sync those from debian-cd, so if debian-cd uses the correct things, so will syslinux-themes-debian. Nice to know that. Adding the debian-cd bug to the list then. For debian-cd people, the SpaceFun isolinux artwork is at http://svn.debianart.org/themes/spacefun/isolinux/ Do you plan to include it? There's nothing needed in debian-cd at all; we just include whatever graphics are provided by the d-i folks. -- Steve McIntyre, Cambridge, UK.st...@einval.com You lock the door And throw away the key There's someone in my head but it's not me ---End Message---
Bug#603554: Bug#603552: Update theme SpaceFun and wiki page
reopen 603554 reassign 603554 debian-installer thanks On jeu., 2010-12-09 at 16:36 +, Steve McIntyre wrote: On Wed, Dec 08, 2010 at 07:29:40PM +0100, Yves-Alexis Perez wrote: On mer., 2010-12-08 at 19:12 +0100, Daniel Baumann wrote: On 12/08/2010 07:10 PM, Daniel Baumann wrote: i think we have a missunderstanding here, spacefun will not be part of plymouth-themes-debian, it's in desktop-base only. sorry, ignore that.. i was answering plymouth related mails above. regarding squeeze, i'll only sync those from debian-cd, so if debian-cd uses the correct things, so will syslinux-themes-debian. Nice to know that. Adding the debian-cd bug to the list then. For debian-cd people, the SpaceFun isolinux artwork is at http://svn.debianart.org/themes/spacefun/isolinux/ Do you plan to include it? There's nothing needed in debian-cd at all; we just include whatever graphics are provided by the d-i folks. Ok, so maybe in the end we'll manage to do it, one step at a time. I'm not sure if Otavio reply applies to d-i or not, though. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#605565: Reopen Bug#605565: gnustep-base-runtime still fails to remove/upgrade if gdomap is not running
Processing commands for cont...@bugs.debian.org: tags 605565 + help Bug #605565 [gnustep-base-runtime] gnustep-base-runtime: unremovable if the daemon is not running Added tag(s) help. thanks Stopping processing here. Please contact me if you need assistance. -- 605565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605565 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: Re: Bug#603554: Bug#603552: Update theme SpaceFun and wiki page
Processing commands for cont...@bugs.debian.org:
reopen 603554
Bug #603554 {Done: Steve McIntyre st...@einval.com} [debian-cd] update
isolinux theme for squeeze
reassign 603554 debian-installer
Bug #603554 [debian-cd] update isolinux theme for squeeze
Bug reassigned from package 'debian-cd' to 'debian-installer'.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
603554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603554
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 605565
Processing commands for cont...@bugs.debian.org: tags 605565 - patch Bug #605565 [gnustep-base-runtime] gnustep-base-runtime: unremovable if the daemon is not running Removed tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 605565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605565 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#606283: Please drop ladcca support
On 0, Alessio Treglia ales...@debian.org wrote: Package: muse Version: 0.8.1a-7 Severity: serious Tags: sid squeeze The package 'ladcca' is orphaned [1], superseded by lash and abandoned upstream, so we would like to remove it from the archives in time for Squeeze (this is the rationale for setting this as 'serious'). In order to do that, we're asking you to remove the build-dependency on it and make a new upload to rebuild the package without the ladcca support. Daniel, Can you upload a fixed version for to close this bugreport soon? I'd like to get rid of ldcca too... or, is it ok if we NMU? Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605565: Reopen Bug#605565: gnustep-base-runtime still fails to remove/upgrade if gdomap is not running
tags 605565 + help thanks On Mon, Dec 06, 2010 at 11:53:55AM +0100, Axel Beckert wrote: I'm sorry to report this, but gnustep-base-runtime 1.20.1-5 fails to upgrade on one of my machines due to a not running gdomap. Two machines actually. Yes, the prerm script is being run before the fixed initscript is replaced, so without --oknodo it fails if the daemon is not running... Any idea what's the right approach to fix this problem? The only thing that comes to my mind right now is to replace (temporarily) dh_installinit's standard snippet in the prerm, ignoring errors -- which looks utterly wrong to me for obvious reasons. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604215: libpam-rsa: installation fails
On Wed, Dec 08, 2010 at 12:00:47AM +0100, Julien Cristau wrote: On Tue, Dec 7, 2010 at 12:52:07 +0100, Julien Cristau wrote: + if ! [ -f $pam_rsa_conf ]; then + cat $pam_rsa_conf EOF +# Configuration file for libpam-rsa +# Please read pam_rsa (8) for further instructions + +EOF I guess there's an argument for only doing this on initial install or reconfigure, to allow the admin to remove the file entirely and not have it restored at each upgrade. Probably not a big deal either way, though. Hi, In this case that is not a problem, file must exist and be readable. Finally had time to put into this NMU. I am attaching yet another diff with my last version. pam_rsa.conf file is not touched if exists in normal upgrades, and I have tried hard to deal with sysadmin comments when updated via dpkg-reconfigure. Need to test this more. If no further problems appear will change version and prepare real NMU. Cheers, -- Agustin diff --git a/debian/changelog b/debian/changelog index 5629331..aa2d951 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,15 @@ +libpam-rsa (0.8-9-2.2~amd3) unstable; urgency=low + + * Non-maintainer upload. + * Fix installation problems with pam_rsa.conf. Thanks Julien Cristau +for the good comments (Closes: #444770, #604215). +- Install pam_rsa.conf as pam_rsa.conf.sample +- Move automatic mode pam_rsa.conf generation from config to postinst. +- Add libpam-rsa.postrm to make sure /etc/security/pam_rsa.conf is + removed on purge + + -- Agustin Martin Domingo agmar...@debian.org Thu, 09 Dec 2010 18:58:47 +0100 + libpam-rsa (0.8-9-2.1) unstable; urgency=low * Non-maintainer upload. diff --git a/debian/libpam-rsa.config b/debian/libpam-rsa.config index 530975c..ed4114a 100644 --- a/debian/libpam-rsa.config +++ b/debian/libpam-rsa.config @@ -10,21 +10,24 @@ db_go || true db_get libpam-rsa/no_configuration if [ $RET = false ] then - db_input medium libpam-rsa/pubkey_dir || true - db_input medium libpam-rsa/privkey_dir || true - db_input low libpam-rsa/privkey_name_hash || true - db_input low libpam-rsa/pam_prompt || true - db_input low libpam-rsa/log_auth_result || true - db_go || true +# If present, parse config file and feed debconf database with its values +pam_rsa_conf=/etc/security/pam_rsa.conf +pam_rsa_keys=pubkey_dir privkey_dir privkey_name_hash pam_prompt log_auth_result +if [ -f $pam_rsa_conf ]; then + for keyname in $pam_rsa_keys; do + # Strip key prefix, trailing whitespace and comments + keyvalue=$(grep -e ^[[:blank:]]*$keyname[[:blank:]] $pam_rsa_conf | sed \ + -e 's/^[[:blank:]]*'$keyname'[[:blank:]]*//' \ + -e 's/[[:blank:]]*$//' \ + -e 's/[[:blank:]]*\#.*$//') + db_set libpam-rsa/$keyname $keyvalue + done +fi - db_get libpam-rsa/pubkey_dir - echo pubkey_dir $RET /etc/security/pam_rsa.conf - db_get libpam-rsa/privkey_dir - echo privkey_dir $RET /etc/security/pam_rsa.conf - db_get libpam-rsa/privkey_name_hash - echo privkey_name_hash $RET /etc/security/pam_rsa.conf - db_get libpam-rsa/pam_prompt - echo pam_prompt $RET /etc/security/pam_rsa.conf - db_get libpam-rsa/log_auth_result - echo log_auth_result $RET /etc/security/pam_rsa.conf +db_input medium libpam-rsa/pubkey_dir || true +db_input medium libpam-rsa/privkey_dir || true +db_input low libpam-rsa/privkey_name_hash || true +db_input low libpam-rsa/pam_prompt || true +db_input low libpam-rsa/log_auth_result || true +db_go || true fi diff --git a/debian/libpam-rsa.postinst b/debian/libpam-rsa.postinst index f06b70e..52d8221 100644 --- a/debian/libpam-rsa.postinst +++ b/debian/libpam-rsa.postinst @@ -19,10 +19,58 @@ set -e # the debian-policy package # +pam_rsa_conf=/etc/security/pam_rsa.conf + case $1 in configure) + db_get libpam-rsa/no_configuration + if [ $RET = false ] + then + # If exists, may have been created by sysadmin. Honour it + # unless we are running debconf-reconfigure + if [ $DEBCONF_RECONFIGURE ] || [ ! -f $pam_rsa_conf ] + then + db_get libpam-rsa/pubkey_dir +pubkey_dir=$RET +db_get libpam-rsa/privkey_dir +privkey_dir=$RET +db_get libpam-rsa/privkey_name_hash +privkey_name_hash=$RET +db_get libpam-rsa/pam_prompt +pam_prompt=$RET +db_get libpam-rsa/log_auth_result +log_auth_result=$RET -;; + if [ ! -f $pam_rsa_conf ]; then + echo Writing auto-generated $pam_rsa_conf 2 + cat $pam_rsa_conf EOF +# pam_rsa.conf Configuration file for libpam-rsa. +# +# This file must exist and be readable. +# +# Please read pam_rsa (8) for further instructions. + +EOF + [ -z $pubkey_dir ]|| echo pubkey_dir $pubkey_dir $pam_rsa_conf + [ -z $privkey_dir ] || echo privkey_dir $privkey_dir $pam_rsa_conf + [ -z $privkey_name_hash ] || echo
Bug#606442: vimhelp-de: Doesn't work with vim 7.3
Well, in squeeze, we have vim*/72 and vimhelp-de/72. That's fine, and won't change, since freeze is squozen. In sid, we have vim*/73 and vimhelp-de/72. That's bad, but Meike prepares a 73 one, Heh, that's sid ;-) I hesitated to file wishlist bug ... flori -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603036: lvm2: fails to install due to incorrect dependencies in init.d LSB header
On Mon, 06 Dec 2010 14:02:08 +0100, Tanguy Ortolo wrote: invoke-rc.d: policy-rc.d denied execution of start. insserv: Service udev has to be enabled to start service lvm2 insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing lvm2 (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports I wonder if it is not simply because lvm2's init script depends on udev's, whereas the package does not depend on the udev package. Thus it is possible to install lvm2 without udev, which would make insserv fail to satisfy this dependancy. Sounds logical. And also works in a quick piuparts test. What surprises me is the changelog entry for 2.02.64-1: * Enable udev sync, remove explicit udev dependency, bump dmsetup dependency to get it working. (closes: #543163) The question is if udev is necessary; if not it probably can be moved from Default-Start to Should-Start in the init script. I've also tried this and it also works. 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: Vic Chesnutt: Gravity Of The Situation signature.asc Description: Digital signature
Processed: mailscanner: diff for NMU version 4.79.11-2.2
Processing commands for cont...@bugs.debian.org: tags 604225 + patch Bug #604225 [mailscanner] mailscanner: installation fails Added tag(s) patch. tags 604225 + pending Bug #604225 [mailscanner] mailscanner: installation fails Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 604225: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604225 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#604225: mailscanner: diff for NMU version 4.79.11-2.2
tags 604225 + patch tags 604225 + pending thanks Dear maintainer, I've prepared an NMU for mailscanner (versioned as 4.79.11-2.2) 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: Die Schmetterlinge: Hände über Hönnepel diff -Nru mailscanner-4.79.11/debian/changelog mailscanner-4.79.11/debian/changelog --- mailscanner-4.79.11/debian/changelog 2010-10-17 23:47:47.0 +0200 +++ mailscanner-4.79.11/debian/changelog 2010-12-09 20:35:31.0 +0100 @@ -1,3 +1,11 @@ +mailscanner (4.79.11-2.2) unstable; urgency=low + + * Non-maintainer upload. + * Fix installation fails: test if /dev/tty exists before using it +(closes: #604225). + + -- gregor herrmann gre...@debian.org Thu, 09 Dec 2010 20:35:25 +0100 + mailscanner (4.79.11-2.1) unstable; urgency=low * Non-maintainer upload. diff -Nru mailscanner-4.79.11/debian/rules mailscanner-4.79.11/debian/rules --- mailscanner-4.79.11/debian/rules 2010-10-17 11:02:53.0 +0200 +++ mailscanner-4.79.11/debian/rules 2010-12-09 20:23:41.0 +0100 @@ -108,7 +108,7 @@ dh_installdeb ( \ echo 'if [ $$1 = purge ] [ -x /usr/bin/ucf ] ; then'; \ - echo (echo Removing report files ... may take some time /dev/tty /dev/tty); \ + echo ([ ! -c /dev/tty ] || echo Removing report files ... may take some time /dev/tty /dev/tty); \ for f in `cat debian/ucffiles`; do \ echo ucf --purge --debconf-ok $$f; \ done; \ @@ -120,7 +120,7 @@ for dir in $$(for f in $$(cat debian/ucffiles); do dirname $$f ; done | sort | uniq); do \ echo mkdir -p $$dir; \ done; \ - echo (echo Checking/installing report files ... /dev/tty /dev/tty); \ + echo ([ ! -c /dev/tty ] || echo Checking/installing report files ... /dev/tty /dev/tty); \ for f in `cat debian/ucffiles`; do \ f2=`echo $$f | sed s,/etc/MailScanner,/usr/share/MailScanner,`; \ echo ucf --debconf-ok $$f2 $$f; \ signature.asc Description: Digital signature
Bug#606498: okular: Broken dep with libQTSvg.so
Package: okular Version: 4:4.4.5-2 Severity: grave Justification: renders package unusable After daily upgrade which involved several QT libraries Okular refuses to start: I got the following error: okular: symbol lookup error: /usr/lib/libQtSvg.so.4: undefined symbol: _ZN14QObjectPrivate15checkWindowRoleEv Cheers gfwp -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=it_CH.UTF-8, LC_CTYPE=it_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages okular depends on: ii kdebase-runtime 4:4.4.5-1runtime components from the offici ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libfreetype62.4.2-2.1FreeType 2 font engine, shared lib ii libgcc1 1:4.4.5-8GCC support library ii libjpeg62 6b1-1The Independent JPEG Group's JPEG ii libkdecore5 4:4.4.5-2the KDE Platform Core Library ii libkdeui5 4:4.4.5-2the KDE Platform User Interface Li ii libkio5 4:4.4.5-2the Network-enabled File Managemen ii libkparts4 4:4.4.5-2the Framework for the KDE Platform ii libkpty44:4.4.5-2the Pseudo Terminal Library for th ii libkutils4 4:4.4.5-2various utility classes for the KD ii libokularcore1 4:4.4.5-2libraries for the Okular document ii libphonon4 4:4.6.0really4.4.2-1 the core library of the Phonon mul ii libpoppler-qt4-30.12.4-1.2 PDF rendering library (Qt 4 based ii libqca2 2.0.2-1 libraries for the Qt Cryptographic ii libqimageblitz4 1:0.0.4-4QImageBlitz image effects library ii libqt4-dbus 4:4.6.3-4Qt 4 D-Bus module ii libqt4-svg 4:4.6.3-4Qt 4 SVG module ii libqt4-xml 4:4.6.3-4Qt 4 XML module ii libqtcore4 4:4.6.3-4Qt 4 core module ii libqtgui4 4:4.6.3-4Qt 4 GUI module ii libspectre1 0.2.6-1 Library for rendering PostScript d ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii phonon 4:4.6.0really4.4.2-1 metapackage for the Phonon multime ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime okular recommends no packages. Versions of packages okular suggests: ii ghostscript 8.71~dfsg2-6 The GPL Ghostscript PostScript/PDF pn kttsd none (no description available) pn okular-extra-backends none (no description available) ii poppler-data0.4.3-1 Encoding data for the poppler PDF ii texlive-binaries2009-8 Binaries for TeX Live pn unrar none (no description available) -- 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#602250: marked as done (jsmin has non free licence, clarify qtobject in debian/copyright)
Your message dated Thu, 09 Dec 2010 19:47:27 + with message-id e1pqmsd-0004tj...@franck.debian.org and subject line Bug#602250: fixed in typo3-src 4.5.0+dfsg1~beta2-1 has caused the Debian Bug report #602250, regarding jsmin has non free licence, clarify qtobject in debian/copyright 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.) -- 602250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: typo3-src-4.3 Version: 4.3.8-1 Severity: serious Justification: DFSG #6 No Discrimination Against Fields of Endeavor The jsmin licence says The Software shall be used for Good, not Evil.. See http://lists.debian.org/debian-legal/2009/09/msg00033.html and http://lists.debian.org/debian-legal/2010/06/msg1.html for why this is a problem. Regards, S -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: typo3-src Source-Version: 4.5.0+dfsg1~beta2-1 We believe that the bug you reported is fixed in the latest version of typo3-src, which is due to be installed in the Debian FTP archive: typo3-database_4.5.0+dfsg1~beta2-1_all.deb to main/t/typo3-src/typo3-database_4.5.0+dfsg1~beta2-1_all.deb typo3-dummy_4.5.0+dfsg1~beta2-1_all.deb to main/t/typo3-src/typo3-dummy_4.5.0+dfsg1~beta2-1_all.deb typo3-src-4.5_4.5.0+dfsg1~beta2-1_all.deb to main/t/typo3-src/typo3-src-4.5_4.5.0+dfsg1~beta2-1_all.deb typo3-src_4.5.0+dfsg1~beta2-1.debian.tar.gz to main/t/typo3-src/typo3-src_4.5.0+dfsg1~beta2-1.debian.tar.gz typo3-src_4.5.0+dfsg1~beta2-1.dsc to main/t/typo3-src/typo3-src_4.5.0+dfsg1~beta2-1.dsc typo3-src_4.5.0+dfsg1~beta2.orig-dummy.tar.gz to main/t/typo3-src/typo3-src_4.5.0+dfsg1~beta2.orig-dummy.tar.gz typo3-src_4.5.0+dfsg1~beta2.orig.tar.gz to main/t/typo3-src/typo3-src_4.5.0+dfsg1~beta2.orig.tar.gz typo3_4.5.0+dfsg1~beta2-1_all.deb to main/t/typo3-src/typo3_4.5.0+dfsg1~beta2-1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 602...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Welzel gaw...@camlann.de (supplier of updated typo3-src 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, 02 Dec 2010 22:00:00 +0200 Source: typo3-src Binary: typo3-src-4.5 typo3-database typo3-dummy typo3 Architecture: source all Version: 4.5.0+dfsg1~beta2-1 Distribution: experimental Urgency: low Maintainer: Christian Welzel gaw...@camlann.de Changed-By: Christian Welzel gaw...@camlann.de Description: typo3 - The enterprise level open source WebCMS (Meta) typo3-database - TYPO3 - The enterprise level open source WebCMS (Database) typo3-dummy - web content management system typo3-src-4.5 - TYPO3 - The enterprise level open source WebCMS (Core) Closes: 598816 599088 602250 Changes: typo3-src (4.5.0+dfsg1~beta2-1) experimental; urgency=low . * New upstream release. * Added source for player.swf and flvplayer.swf (see #591969). . typo3-src (4.5.0+dfsg1~beta1-1) experimental; urgency=low . * Removed typo3/contrib/jsmin/jsmin.php because of non free license (Closes: 602250) * Added notice about license of qtobject.js to copyright file. * Added README.source. * Corrected watch file. * Added rule dfsg to rules to remove non free files. . typo3-src (4.5.0~beta1-1) experimental; urgency=low . * New upstream release. * Merged typo3-src and typo3-dummy source packages. * Fixed spelling error in control (Closes: 598816) * Added lintian override for embedded-php-library on libnusoap-php because of customized nusoap in these packages (see 529581) * Added japanese translation (Closes: 599088) * Reorganized and updated changelog. Uses DEP-5 format now. * localconf.php: - raised memory limit to 64MB - disabled donation window - set search path for binaries - disabled deprecation logging * Moved mysql
Bug#591969: status update?
Am 07.12.2010 15:40, schrieb Holger Levsen: Hi Christian, any idea what to do about this bug? I added the source code of ./typo3/contrib/flashmedia/flvplayer.swf ./typo3/contrib/flashmedia/player.swf to the 4.5.0+dfsg1~beta2-1. flvplayer.swf is a part of TYPO3 and source is available from typo3-svn. player.swf came from pixelout player 1.2 All actionscript 3 code is not buildable within debian because debian has no as3 compiler. Perhaps flex-sdk will be available in some time (see #602499) but until then no as3-swf can be build from source. -- MfG, Christian Welzel GPG-Key: http://www.camlann.de/de/pgpkey.html Fingerprint: 4F50 19BF 3346 36A6 CFA9 DBDC C268 6D24 70A1 AD15 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604215: libpam-rsa: installation fails
On Thu, Dec 9, 2010 at 19:37:07 +0100, Agustin Martin wrote: Finally had time to put into this NMU. I am attaching yet another diff with my last version. pam_rsa.conf file is not touched if exists in normal upgrades, and I have tried hard to deal with sysadmin comments when updated via dpkg-reconfigure. Need to test this more. If no further problems appear will change version and prepare real NMU. Looks sane to me, thanks for this! Cheers, Julien signature.asc Description: Digital signature
Bug#604231: marked as done (chef-solr: installation fails, unable to connect to node, nodedown)
Your message dated Thu, 09 Dec 2010 20:32:09 +
with message-id e1pqn9t-00064t...@franck.debian.org
and subject line Bug#604231: fixed in chef 0.8.16-4.2
has caused the Debian Bug report #604231,
regarding chef-solr: installation fails, unable to connect to node, nodedown
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.)
--
604231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: chef-solr
Version: 0.8.16-4.1
Severity: serious
User: debian...@lists.debian.org
Usertags: instest-20101120 instest
Hi,
While testing the installation of all packages in unstable, I ran
into the following problem:
Setting up chef-solr (0.8.16-4.1) ...
Error: unable to connect to node 'rab...@parapluie-8': nodedown
diagnostics:
- nodes and their ports on parapluie-8: [{rabbitmqctl24301,59110}]
- current node: 'rabbitmqctl24...@parapluie-8'
- current node home dir: /var/lib/rabbitmq
- current node cookie hash: fJiJth+YsTHJfj5ZQWvUSQ==
Creating vhost /chef ...
Error: unable to connect to node 'rab...@parapluie-8': nodedown
diagnostics:
- nodes and their ports on parapluie-8: [{rabbitmqctl24349,46122}]
- current node: 'rabbitmqctl24...@parapluie-8'
- current node home dir: /var/lib/rabbitmq
- current node cookie hash: fJiJth+YsTHJfj5ZQWvUSQ==
dpkg: error processing chef-solr (--configure):
subprocess installed post-installation script returned error exit status 2
configured to not write apport reports
Errors were encountered while processing:
chef-solr
E: Sub-process /usr/bin/dpkg returned an error code (1)
The full build log is available from:
http://people.debian.org/~lucas/logs/2010/11/20/chef-solr.log
It is reproducible by installing your package in a clean chroot, using
the debconf Noninteractive frontend, and priority: critical.
This test was carried out using about 50 AMD64 nodes of the Grid'5000
platform. Internet was not accessible from the nodes.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
---End Message---
---BeginMessage---
Source: chef
Source-Version: 0.8.16-4.2
We believe that the bug you reported is fixed in the latest version of
chef, which is due to be installed in the Debian FTP archive:
chef_0.8.16-4.2.diff.gz
to main/c/chef/chef_0.8.16-4.2.diff.gz
chef_0.8.16-4.2.dsc
to main/c/chef/chef_0.8.16-4.2.dsc
chef_0.8.16-4.2_all.deb
to main/c/chef/chef_0.8.16-4.2_all.deb
libchef-ruby1.8_0.8.16-4.2_all.deb
to main/c/chef/libchef-ruby1.8_0.8.16-4.2_all.deb
libchef-ruby_0.8.16-4.2_all.deb
to main/c/chef/libchef-ruby_0.8.16-4.2_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 604...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Luca Capello l...@pca.it (supplier of updated chef 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: SHA512
Format: 1.8
Date: Thu, 09 Dec 2010 20:44:25 +0100
Source: chef
Binary: chef libchef-ruby libchef-ruby1.8
Architecture: source all
Version: 0.8.16-4.2
Distribution: unstable
Urgency: low
Maintainer: Joshua Timberman jos...@opscode.com
Changed-By: Luca Capello l...@pca.it
Description:
chef - system integration framework - client and solo binaries
libchef-ruby - system integration framework - Ruby libraries
libchef-ruby1.8 - system integration framework - Ruby 1.8 libraries
Closes: 598365 598626 604231 606274
Changes:
chef (0.8.16-4.2) unstable; urgency=low
.
* Non-maintainer upload.
* debian/control:
- remove outdated -server* packages and chef-solr as well, with
maintainer's approval (Closes: #604231).
* debian/patches/series: update.
* debian/patches/chef_client_ruby18.patch:
+ fix FTBFS, use a versioned shebang for client binaries, since
the chef binary package Depends: on Ruby-1.8 (Closes: #606274).
* [Debconf translation updates]
- Japanese (Hideki Yamane) (Closes: #598365).
- Vietnamese (Clytie Siddall) (Closes: #598626).
Checksums-Sha1:
620726b0559a496681e7b92a90be81a0b1eb5ad4 1874 chef_0.8.16-4.2.dsc
a1b1c623eb671eea2e139f003c82a4f159c4d038 72146 chef_0.8.16-4.2.diff.gz
Bug#606274: marked as done (chef: FTBFS: Patch remove_rubygems.patch does not remove cleanly (refresh it or enforce with -f))
Your message dated Thu, 09 Dec 2010 20:32:09 +
with message-id e1pqn9t-00064x...@franck.debian.org
and subject line Bug#606274: fixed in chef 0.8.16-4.2
has caused the Debian Bug report #606274,
regarding chef: FTBFS: Patch remove_rubygems.patch does not remove cleanly
(refresh it or enforce with -f)
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.)
--
606274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: chef
Version: 0.8.16-4.1
Severity: serious
Tags: patch
Hi there!
=
l...@gismo:~/$ gismo-pbuilder.sh --build base-sid chef_0.8.16-4.1.dsc
[...]
dpkg-deb: building package `libchef-ruby1.8' in
`../libchef-ruby1.8_0.8.16-4.1_all.deb'.
dpkg-genchanges ../chef_0.8.16-4.1_amd64.changes
dpkg-genchanges: not including original source code in upload
fakeroot debian/rules clean
test -x debian/rules
dh_testroot
dh_clean
/usr/bin/make -f debian/rules reverse-config
make[1]: Entering directory `/tmp/buildd/chef-0.8.16'
make[1]: Nothing to be done for `reverse-config'.
make[1]: Leaving directory `/tmp/buildd/chef-0.8.16'
if [ -d . ]; then \
cd . QUILT_PATCHES=/tmp/buildd/chef-0.8.16/debian/patches quilt
--quiltrc /dev/null pop -a -R || test $? = 2 ; \
fi
Removing patch jquery_unminified.patch
Removing chef-server-webui/public/javascripts/jquery.jeditable.js
Removing chef-server-webui/public/javascripts/yetii.js
Removing chef-server-webui/public/javascripts/jquery.tools.js
Patch remove_rubygems.patch does not remove cleanly (refresh it or enforce with
-f)
make: *** [reverse-patches] Error 1
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
E: Failed autobuilding of package
=
When you do not build the package, the patch above seems to cleanly
apply and remove, so I guess the building process modifies some files.
And indeed if I compare the patched files above with the original ones,
the diff includes more than the quilt patch:
--8---cut here---start-8---
--- chef-0.8.16/chef/bin/chef-client 2010-12-07 21:57:20.0 +0100
+++ chef-client 2010-12-07 22:17:57.0 +0100
@@ -1,4 +1,4 @@
-#!/usr/bin/env ruby
+#! /usr/bin/ruby1.8
#
# ./chef-client - Run the chef client
#
@@ -18,7 +18,6 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-require 'rubygems'
$:.unshift(File.join(File.dirname(__FILE__), .., lib))
require 'chef'
require 'chef/application/client'
--8---cut here---end---8---
This applies to the four chef-client binaries: chef-client, chef-solo,
knife and shef. The build log contains the following:
=
(cd chef /usr/bin/ruby debian-setup.rb setup)
--- bin
updating shebang: chef-client
updating shebang: shef
updating shebang: knife
updating shebang: chef-solo
--- bin
=
What is strange is that the current chef binary package available in sid
contains the four binaries above with exactly the same shebang as the
one that causes the error, which means that the build process should
have stopped even in the past...
Actually, the same problem should happen for the -server* binaries, but
it does not, given that the shebang in these binaries is specifically
modified to ruby1.8 because the -server* binaries do not support
Ruby-1.9 yet:
[chef-0.8.16/debian/patches/chef_solr_ruby18.patch]
# Description: Use ruby1.8 specifically as Chef Solr/Server doesn't support
# ruby1.9 yet.
Nevertheless, I am not a Ruby nor a chef expert, but applying the same
trick patch to the client binaries solves the FTBFS. I am confident
this is the correct fix also because the chef binary package (which
contains the client binaries) Depends: on Ruby-1.8:
Depends: ${misc:Depends}, ruby1.8, liberubis-ruby1.8, libjson-ruby1.8,
libextlib-ruby1.8 (= 0.9.13), ohai (= 0.4.0),
libchef-ruby1.8 (= ${source:Version}), libopenssl-ruby1.8,
libmixlib-authentication-ruby1.8 (= 1.1.0), ucf
--8---cut here---start-8---
diff -u chef-0.8.16/debian/changelog chef-0.8.16/debian/changelog
--- chef-0.8.16/debian/changelog
+++ chef-0.8.16/debian/changelog
@@ -1,3 +1,13 @@
+chef (0.8.16-4.2) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * debian/patches/series: update.
+ * debian/patches/chef_client_ruby18.patch:
++ fix FTBFS, use a versioned shebang for client binaries, since
+ the chef binary package Depends: on Ruby-1.8 (Closes: #NN).
+
+ -- Luca Capello l...@pca.it
Bug#584350: marked as done (refcard: FTBFS: xmlroff segfaults)
Your message dated Thu, 09 Dec 2010 20:36:42 + with message-id e1pqnei-0006i2...@franck.debian.org and subject line Bug#584350: fixed in refcard 5.0.6-1 has caused the Debian Bug report #584350, regarding refcard: FTBFS: xmlroff segfaults 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.) -- 584350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: refcard Version: 5.0.5-3 Severity: serious Tags: squeeze sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20100602 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: XSLT stylesheets DocBook - LaTeX 2e (0.3-1) === Processing Revision History Build refcard-it.dbk.pdf This is XeTeX, Version 3.1415926-2.2-0.9995.2 (TeX Live 2009/Debian) restricted \write18 enabled. entering extended mode ** WARNING ** Annotation out of page boundary. ** WARNING ** Current page's MediaBox: [0 0 280.63 595.276] ** WARNING ** Annotation: [129.765 551.505 218.432 661.094] ** WARNING ** Maybe incorrect paper size specified. This is XeTeX, Version 3.1415926-2.2-0.9995.2 (TeX Live 2009/Debian) restricted \write18 enabled. entering extended mode ** WARNING ** Annotation out of page boundary. ** WARNING ** Current page's MediaBox: [0 0 280.63 595.276] ** WARNING ** Annotation: [129.765 551.505 218.432 661.094] ** WARNING ** Maybe incorrect paper size specified. This is XeTeX, Version 3.1415926-2.2-0.9995.2 (TeX Live 2009/Debian) restricted \write18 enabled. entering extended mode ** WARNING ** Annotation out of page boundary. ** WARNING ** Current page's MediaBox: [0 0 280.63 595.276] ** WARNING ** Annotation: [129.765 551.505 218.432 661.094] ** WARNING ** Maybe incorrect paper size specified. 'refcard-it-a4.s.pdf' successfully built pdfjoin --vanilla --fitpaper true --outfile refcard-it-a4.s.pdf.x.pdf refcard-it-a4.s.pdf empty.pdf empty.pdf pdfjam: This is pdfjam version 2.05. pdfjam: Called with '--vanilla': no user or site configuration files will be read. pdfjam: Effective call for this run of pdfjam: /usr/bin/pdfjam --fitpaper 'true' --rotateoversize 'true' --suffix joined --vanilla --fitpaper 'true' --outfile refcard-it-a4.s.pdf.x.pdf -- refcard-it-a4.s.pdf - empty.pdf - empty.pdf - pdfjam: Calling pdflatex... pdfjam: Finished. Output was to 'refcard-it-a4.s.pdf.x.pdf'. pdfnup --vanilla --nup 3x1 --outfile refcard-it-a4.t.pdf --paper a4paper refcard-it-a4.s.pdf.x.pdf 5-6,1-4 pdfjam: This is pdfjam version 2.05. pdfjam: Called with '--vanilla': no user or site configuration files will be read. pdfjam: Effective call for this run of pdfjam: /usr/bin/pdfjam --suffix nup --nup '2x1' --landscape --vanilla --nup '3x1' --outfile refcard-it-a4.t.pdf --paper a4paper -- refcard-it-a4.s.pdf.x.pdf 5-6,1-4 pdfjam: Calling pdflatex... pdfjam: Finished. Output was to 'refcard-it-a4.t.pdf'. rm refcard-it-a4.s.pdf.x.pdf L=`echo refcard-it-a4.pdf | sed 's/.*-\(.*\)-.*/\1/'`; \ xsltproc --nonet --novalid metadata.xsl entries-$L.dbk | \ pdftk refcard-it-a4.t.pdf update_info - output refcard-it-a4.pdf xsltproc --nonet --novalid preproc.xsl entries-ja.dbk refcard-ja.dbk xsltproc --nonet --novalid fo.xsl refcard-ja.dbk refcard-ja-a4.fo Making portrait pages on USletter paper (99mmx210mm) L=`echo refcard-ja-a4.s.pdf | sed 's/.*-\(.*\)-.*/\1/'`; \ USE_XR=`echo ar cs el he hi ja ml sk zh_CN zh_TW | grep $L `; \ if [ -n $USE_XR ]; then \ USE_GP=`echo ar eu he hi ja sv | grep $L `; \ if [ -n $USE_GP ]; then \ xmlroff --backend gp -o refcard-ja-a4.s.pdf refcard-ja-a4.fo; \ else \ xmlroff --backend cairo -o refcard-ja-a4.s.pdf refcard-ja-a4.fo; \ fi; \ else \ if [ -n $USE_DBLATEX ]; then \ SRC=`echo refcard-ja-a4.fo|sed 's/-\(a4\|lt\).fo/.dbk/'`; \ FMT=`echo refcard-ja-a4.fo|sed 's/.*-\(a4\|lt\).fo/\1/'`; \ dblatex --backend=xetex --texstyle=refcard.sty --xsl-user=dblatex.xsl --output=refcard-ja-a4.s.pdf --param=format=$FMT $SRC; \ else \ fop refcard-ja-a4.fo refcard-ja-a4.s.pdf; \ fi; \ fi (xmlroff:24762): libfo-WARNING **: fo-area-page-error: Child area overflows parent area Object path:
Processed: tagging 598274
Processing commands for cont...@bugs.debian.org:
# not relevant for stable
tags 598274 + squeeze sid
Bug #598274 {Done: Lior Kaplan kap...@debian.org} [icedove-bidiui]
icedove-bidiui: Does not support icedove 3.x (newer version avaialble)
Added tag(s) sid and squeeze.
End of message, stopping processing here.
Please contact me if you need assistance.
--
598274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598274
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: notfound 598274 in 0.7.3-3
Processing commands for cont...@bugs.debian.org:
notfound 598274 0.7.3-3
Bug #598274 {Done: Lior Kaplan kap...@debian.org} [icedove-bidiui]
icedove-bidiui: Does not support icedove 3.x (newer version avaialble)
Bug No longer marked as found in versions bidiui/0.7.3-3.
End of message, stopping processing here.
Please contact me if you need assistance.
--
598274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598274
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: found 606327 in 2010.06.16-268169-3
Processing commands for cont...@bugs.debian.org: # re-add version information lost in reassign found 606327 2010.06.16-268169-3 Bug #606327 [open-vm-tools] vmmemctl missing in squeeze Bug Marked as found in versions open-vm-tools/2010.06.16-268169-3. End of message, stopping processing here. Please contact me if you need assistance. -- 606327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606327 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 605784
Processing commands for cont...@bugs.debian.org: # after upgrade to squeeze ... tags 605784 + squeeze sid Bug #605784 [nagios-statd-server] nagios-statd-server: stops responding and 100% cpu usage Added tag(s) sid and squeeze. End of message, stopping processing here. Please contact me if you need assistance. -- 605784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605784 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#606247: marked as done (FTBFS: missing libedit-dev build dependency)
Your message dated Thu, 09 Dec 2010 21:02:32 + with message-id e1pqndi-0004di...@franck.debian.org and subject line Bug#606247: fixed in mapserver 5.6.5-1.1 has caused the Debian Bug report #606247, regarding FTBFS: missing libedit-dev build dependency 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.) -- 606247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mapserver Version: 5.6.5-1 Severity: serious While trying to build an l10n NMU of mapserver, I found out that it fails to build from source in a pbuilder chroot because of missing libedit development files. Indeed, the package is missing a build dependency on libedit-dev. It probably was hidden until now because another build dependency was pulling it inand that dependency was recently dropped. I have a ready NMU to fix this (plus pending debconf translations) and will upload it to DELAYED/2 -- System Information: Debian Release: squeeze/sid Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: mapserver Source-Version: 5.6.5-1.1 We believe that the bug you reported is fixed in the latest version of mapserver, which is due to be installed in the Debian FTP archive: cgi-mapserver_5.6.5-1.1_i386.deb to main/m/mapserver/cgi-mapserver_5.6.5-1.1_i386.deb libmapscript-ruby1.8_5.6.5-1.1_i386.deb to main/m/mapserver/libmapscript-ruby1.8_5.6.5-1.1_i386.deb libmapscript-ruby1.9.1_5.6.5-1.1_i386.deb to main/m/mapserver/libmapscript-ruby1.9.1_5.6.5-1.1_i386.deb libmapscript-ruby_5.6.5-1.1_all.deb to main/m/mapserver/libmapscript-ruby_5.6.5-1.1_all.deb mapserver-bin_5.6.5-1.1_i386.deb to main/m/mapserver/mapserver-bin_5.6.5-1.1_i386.deb mapserver-doc_5.6.5-1.1_all.deb to main/m/mapserver/mapserver-doc_5.6.5-1.1_all.deb mapserver_5.6.5-1.1.diff.gz to main/m/mapserver/mapserver_5.6.5-1.1.diff.gz mapserver_5.6.5-1.1.dsc to main/m/mapserver/mapserver_5.6.5-1.1.dsc perl-mapscript_5.6.5-1.1_i386.deb to main/m/mapserver/perl-mapscript_5.6.5-1.1_i386.deb php5-mapscript_5.6.5-1.1_i386.deb to main/m/mapserver/php5-mapscript_5.6.5-1.1_i386.deb python-mapscript_5.6.5-1.1_i386.deb to main/m/mapserver/python-mapscript_5.6.5-1.1_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 606...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Perrier bubu...@debian.org (supplier of updated mapserver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 06 Dec 2010 07:09:55 +0100 Source: mapserver Binary: php5-mapscript perl-mapscript cgi-mapserver python-mapscript mapserver-bin mapserver-doc libmapscript-ruby libmapscript-ruby1.8 libmapscript-ruby1.9.1 Architecture: source all i386 Version: 5.6.5-1.1 Distribution: unstable Urgency: low Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: cgi-mapserver - CGI executable for MapServer libmapscript-ruby - Ruby MapServer library libmapscript-ruby1.8 - Ruby MapServer library libmapscript-ruby1.9.1 - Ruby MapServer library mapserver-bin - MapServer utilities mapserver-doc - documentation for MapServer perl-mapscript - Perl MapServer library php5-mapscript - php5-cgi module for MapServer python-mapscript - Python library for MapServer Closes: 599847 601922 605618 605858 606247 Changes: mapserver (5.6.5-1.1) unstable; urgency=low . * Non-maintainer upload. * Build-Depends on libedit-dev as the package FTBFS without it Closes: #606247 * Fix pending l10n issues. Debconf translations: - Czech (Miroslav Kure). Closes: #599847 - Vietnamese (Clytie Siddall). Closes: #601922 - Danish (Joe Hansen). Closes: #605618 - Italian (Vincenzo Campanella). Closes: #605858 Checksums-Sha1: c5a5208ae94bdd0fef476e297048da6b50c48176 2656 mapserver_5.6.5-1.1.dsc 05e3fcf1459d8231100ace1f01471f6d001c5375 23995 mapserver_5.6.5-1.1.diff.gz 157f8672cfd421ccf2a3bd3c24a29bac31a9c578 80082 mapserver-doc_5.6.5-1.1_all.deb
Bug#606048: Perdition package upgrade removes and does not regenerate .db files
On Thu, Dec 09, 2010 at 11:12:05AM +0100, Cesare Leonardi wrote: I just upgraded to the latest lenny perdition package. The upgrade resulted in the /etc/perdition/popmap.*.db files being removed and not regenerated. I confirm this too. Today i upgraded from 1.17.1-2 to 1.17.1-2+lenny2 and after a reboot for a kernel upgrade, some user started complaining about authentication errors. So i observed what Tim reported. Hi Cesare, Hi Tim, I am a bit confused as to if this is a new problem or not. I initially thought that Tim's idea that this was a result of the change made to resolve #595207 was correct, but now I'm not so sure. The change made for #595207 was to remove the portion of the postrm script that removes the .db files. So its expected (though entirely undesirable) that 1.17.1-2 removes them, while 1.17.1-2+lenny2 should not. However, I don't think that installing (or upgrading) perdition has ever created the .db files. So I'm unsure why this problem hasn't been observed. As for a fix, I wonder if it is appropriate to have perdition run make to create the .db files in its postinst. And having an dependency on make accordingly. Moving forwards this shouldn't be necessary, as the db files aren't removed by postrm any more. But there is no telling what version a user might be upgrading from. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606520: linux-tools-2.6.36: /usr/bin/perf_2.6.36 links against openssl but copyright lists only GPLv2 without exceptions
Package: linux-tools-2.6.36 Version: 2.6.36-1~experimental.1 Severity: serious /usr/share/doc/linux-tools-2.6.36/copyright gives me the impression that we have a license to distribute /usr/bin/perf_2.6.36 only under the terms of the GPLv2. Is this correct? It seems that perf_2.6.36 uses openssl: $ ldd /usr/bin/perf_2.6.36|grep ssl libssl.so.0.9.8 = /usr/lib/libssl.so.0.9.8 (0x7f20fad1f000) Has perf upstream given an exception to GPLv2 to allow us to do this or is this indeed a real problem? -- 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/4 CPU cores) Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages linux-tools-2.6.36 depends on: ii binutils2.20.1-15The GNU assembler, linker and bina ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libelf1 0.148-1 library to read and write ELF file ii libperl5.10 5.10.1-16shared Perl library ii libpython2.62.6.6-6 Shared Python runtime library (ver ii perl5.10.1-16Larry Wall's Practical Extraction ii python 2.6.6-3+squeeze1 interactive high-level object-orie ii python-support 1.0.10 automated rebuilding support for P Versions of packages linux-tools-2.6.36 recommends: ii linux-base 2.6.36-1~experimental.1 Linux image base package Versions of packages linux-tools-2.6.36 suggests: pn linux-doc-2.6.36 none (no description available) -- 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#557495: marked as done (libtowitoko-dev and libctapimkt0-dev: error when trying to install together)
Your message dated Thu, 09 Dec 2010 22:17:48 + with message-id e1pqoo8-0005vl...@franck.debian.org and subject line Bug#557495: fixed in towitoko 2.0.7-8.2 has caused the Debian Bug report #557495, regarding libtowitoko-dev and libctapimkt0-dev: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 557495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libctapimkt0-dev,libtowitoko-dev Version: libctapimkt0-dev/1.0.1-1 Version: libtowitoko-dev/2.0.7-8+b1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2009-11-22 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-dev-bin linux-libc-dev libc6-dev libctapimkt0 libctapimkt0-dev libtowitoko2 libtowitoko-dev Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libc-dev-bin. (Reading database ... 10432 files and directories currently installed.) Unpacking libc-dev-bin (from .../libc-dev-bin_2.10.1-7_amd64.deb) ... Selecting previously deselected package linux-libc-dev. Unpacking linux-libc-dev (from .../linux-libc-dev_2.6.31-2_amd64.deb) ... Selecting previously deselected package libc6-dev. Unpacking libc6-dev (from .../libc6-dev_2.10.1-7_amd64.deb) ... Selecting previously deselected package libctapimkt0. Unpacking libctapimkt0 (from .../libctapimkt0_1.0.1-1_amd64.deb) ... Selecting previously deselected package libctapimkt0-dev. Unpacking libctapimkt0-dev (from .../libctapimkt0-dev_1.0.1-1_amd64.deb) ... Selecting previously deselected package libtowitoko2. Unpacking libtowitoko2 (from .../libtowitoko2_2.0.7-8+b1_amd64.deb) ... Selecting previously deselected package libtowitoko-dev. Unpacking libtowitoko-dev (from .../libtowitoko-dev_2.0.7-8+b1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libtowitoko-dev_2.0.7-8+b1_amd64.deb (--unpack): trying to overwrite '/usr/include/ctapi.h', which is also in package libctapimkt0-dev 0:1.0.1-1 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libtowitoko-dev_2.0.7-8+b1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violate section 7.6.1 of the policy. Possible solutions are to have the two packages conflict, to rename the common file in one of the two packages, or to remove the file from one package and have this package depend on the other package. File diversions or a Replace relation are another possibility. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/include/ctapi.h This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Source: towitoko Source-Version: 2.0.7-8.2 We believe that the bug you reported is fixed in the latest version of towitoko, which is due to be installed in the Debian FTP archive: libtowitoko-dev_2.0.7-8.2_amd64.deb to main/t/towitoko/libtowitoko-dev_2.0.7-8.2_amd64.deb libtowitoko2_2.0.7-8.2_amd64.deb to main/t/towitoko/libtowitoko2_2.0.7-8.2_amd64.deb towitoko_2.0.7-8.2.diff.gz to main/t/towitoko/towitoko_2.0.7-8.2.diff.gz towitoko_2.0.7-8.2.dsc to main/t/towitoko/towitoko_2.0.7-8.2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 557...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Neil Williams codeh...@debian.org (supplier of updated towitoko 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
Bug#606319: irssi crashes when changing window
tag 606319 + patch
thanks
I'm almost sure this is
http://bugs.irssi.org/index.php?do=detailstask_id=669
Attached is a patch that seems to fix it for me.
--
·O· Pierre Habouzit
··Omadco...@debian.org
OOOhttp://www.madism.org
From f124a50beee43665ade240058836098c2418fa24 Mon Sep 17 00:00:00 2001
From: Pierre Habouzit madco...@debian.org
Date: Thu, 9 Dec 2010 23:20:08 +0100
Subject: [PATCH] Avoid segfault in with cumode_space
Signed-off-by: Pierre Habouzit madco...@debian.org
---
src/irc/core/irc-expandos.c |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/src/irc/core/irc-expandos.c b/src/irc/core/irc-expandos.c
index 0c0da64..1c3a353 100644
--- a/src/irc/core/irc-expandos.c
+++ b/src/irc/core/irc-expandos.c
@@ -106,7 +106,14 @@ static char *expando_cumode_space(SERVER_REC *server, void *item, int *free_ret)
return ;
ret = expando_cumode(server, item, free_ret);
- return *ret == '\0' ? : ret;
+if (*ret == '\0') {
+if (*free_ret) {
+g_free(ret);
+*free_ret = FALSE;
+}
+ret = ;
+}
+return ret;
}
static void event_join(IRC_SERVER_REC *server, const char *data,
--
1.7.3.2.633.gba590
Processed: Re: Bug#606319: irssi crashes when changing window
Processing commands for cont...@bugs.debian.org: tag 606319 + patch Bug #606319 [irssi] irssi crashes when changing window Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 606319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606319 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#606265: marked as done (libtowitoko-dev and libctapimkt0-dev: error when trying to install together)
Your message dated Thu, 09 Dec 2010 22:33:12 + with message-id e1pqp32-00071f...@franck.debian.org and subject line Bug#606265: fixed in libctapimkt 1.0.1-1.1 has caused the Debian Bug report #606265, regarding libtowitoko-dev and libctapimkt0-dev: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 606265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libctapimkt0-dev,libtowitoko-dev Version: libctapimkt0-dev/1.0.1-1 Version: libtowitoko-dev/2.0.7-8+b1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2009-11-22 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libc-dev-bin linux-libc-dev libc6-dev libctapimkt0 libctapimkt0-dev libtowitoko2 libtowitoko-dev Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libc-dev-bin. (Reading database ... 10432 files and directories currently installed.) Unpacking libc-dev-bin (from .../libc-dev-bin_2.10.1-7_amd64.deb) ... Selecting previously deselected package linux-libc-dev. Unpacking linux-libc-dev (from .../linux-libc-dev_2.6.31-2_amd64.deb) ... Selecting previously deselected package libc6-dev. Unpacking libc6-dev (from .../libc6-dev_2.10.1-7_amd64.deb) ... Selecting previously deselected package libctapimkt0. Unpacking libctapimkt0 (from .../libctapimkt0_1.0.1-1_amd64.deb) ... Selecting previously deselected package libctapimkt0-dev. Unpacking libctapimkt0-dev (from .../libctapimkt0-dev_1.0.1-1_amd64.deb) ... Selecting previously deselected package libtowitoko2. Unpacking libtowitoko2 (from .../libtowitoko2_2.0.7-8+b1_amd64.deb) ... Selecting previously deselected package libtowitoko-dev. Unpacking libtowitoko-dev (from .../libtowitoko-dev_2.0.7-8+b1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libtowitoko-dev_2.0.7-8+b1_amd64.deb (--unpack): trying to overwrite '/usr/include/ctapi.h', which is also in package libctapimkt0-dev 0:1.0.1-1 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/libtowitoko-dev_2.0.7-8+b1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violate section 7.6.1 of the policy. Possible solutions are to have the two packages conflict, to rename the common file in one of the two packages, or to remove the file from one package and have this package depend on the other package. File diversions or a Replace relation are another possibility. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/include/ctapi.h This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Source: libctapimkt Source-Version: 1.0.1-1.1 We believe that the bug you reported is fixed in the latest version of libctapimkt, which is due to be installed in the Debian FTP archive: libctapimkt0-dev_1.0.1-1.1_amd64.deb to main/libc/libctapimkt/libctapimkt0-dev_1.0.1-1.1_amd64.deb libctapimkt0_1.0.1-1.1_amd64.deb to main/libc/libctapimkt/libctapimkt0_1.0.1-1.1_amd64.deb libctapimkt_1.0.1-1.1.diff.gz to main/libc/libctapimkt/libctapimkt_1.0.1-1.1.diff.gz libctapimkt_1.0.1-1.1.dsc to main/libc/libctapimkt/libctapimkt_1.0.1-1.1.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 606...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Neil Williams codeh...@debian.org (supplier of updated libctapimkt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN
Bug#605565: Reopen Bug#605565: gnustep-base-runtime still fails to remove/upgrade if gdomap is not running
Hi Yavor, thanks for having a closer look at this. Yavor Doganov wrote: I'm sorry to report this, but gnustep-base-runtime 1.20.1-5 fails to upgrade on one of my machines due to a not running gdomap. Two machines actually. Yes, the prerm script is being run before the fixed initscript is replaced, so without --oknodo it fails if the daemon is not running... Oh, ok! I already looked into the issue, too, and noticed that --oknodo indeed does the right thing. Didn't find out what's the real problem. Any idea what's the right approach to fix this problem? Two ideas come to my mind: 1. Ignoring the exit code of the init.d script in the prerem. 2. AFAIK the maintainer scripts know if the package is just removed or upgraded, so maybe calling it in postinst instead of prerm only if the package is upgraded. BTW: Do you know if that problem is present in Lenny, too? If not, this bug can possibly ignored as it then won't happen when dist-upgrading from Lenny to Squeeze. (Nevertheless I'd be happy to see a working fix for this. :-) The only thing that comes to my mind right now is to replace (temporarily) dh_installinit's standard snippet in the prerm, ignoring errors -- which looks utterly wrong to me for obvious reasons. Ah, right, that part is written by debhelper scripts... Well, maybe you can put some code handling this issue specificly before the debhelper snippets and care that they are not run in case this special case occurs. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- 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 606297 is important
Processing commands for cont...@bugs.debian.org: # can't reproduce the problem severity 606297 important Bug #606297 [src:imagemagick] imagemagick: FTBFS: collect2: ld returned 1 exit status Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 606297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606297 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#605277: marked as done (chef: remove from squeeze because of solr (#602697)?)
Your message dated Fri, 10 Dec 2010 00:41:08 +0100 with message-id 87bp4utsyz@gismo.pca.it and subject line Re: chef: remove from squeeze because of solr (#602697)? (was Re: Bug#602697: chef-solr depends on solr) has caused the Debian Bug report #605277, regarding chef: remove from squeeze because of solr (#602697)? 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.) -- 605277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: solr Severity: serious Tags: squeeze -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've written a mail (Remove Solr from Squeeze?) on 2010/10/12 to debian-java and the package's maintainer Jan-Pascal van Best and proposed the removal of solr from Squeeze, mainly because: - - it's already outdated a year by now (see bug #602696 ) - - it doesn't even include all contribs (see bug #602695 ) - - the package has accumulated too many bugs - - there doesn't seem to be enough (wo)man power to maintain the package right now on a standard that would make it fit for Debian _stable_ So until nothing else happens, please don't include solr in Debian squeeze. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJM1oGeAAoJEAf8SJEEK6ZaFiAP/jFmubZ8p3rWiMAAgwKqcttk 3tUbU+w8meAMv89k8k32BdYQMmMzg0K8ecsxJeTNIgV4CRvroUwf3vRL3qd6Tgbr U57wcVB+J6Ionea0oYru35wqGAwBsRm6fFUFRpDWrVJjuRMrrIFz7WUJHmiCmSjO +eUvo/I4hniXcgLEm72Hui/qT6HeYMHKQMlzPbjSVkTbsC/d8Q7TpE/YLu6Q5BeG yKNvyMUou02QUX2wtDIPw2K/j71OuF/PPqWv1hLDdIqbm1sTmbTSKMKmTkG0spQc ySa7djpLiWTffTH3gmKDMqSjnUuRjvJCJowLx85aicKulZuyh+Juo4Ump84V8KJN vBmCWtbI/IzldDWX73eWtkzm29fyDK62ovt7Jqm9IQ5jnrUSeRTJ+xNXfAvRjTKg Hs0jgbNiUMivqlm9wcA5d9vuzZRhchwUm9VtC8UMs3SWW+FAP2oQg/yYETYZ5rs9 xvGMS3tFgJJ1Pe8wuP3IzUo/j7jVOyxMWWOak6orGJApePOk6zG6cIYzSdo6RGfI dflA5MfHEhMOsCR3Q9fd+YRgEdyIOcnGHity31yS0RPsLO78PV8yztW5VLZXQ5f2 52aU1UMFYp2ULtW0wSFayC5lLclGo/fYKzXX+TIwBrUryukiKVPaelJ11TsAYefr PfTZdFLR1T86DewUPivM =TqjB -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Package: chef Version: 0.8.16-4.2 Hi there! Adding debian-release@ to the cc: given that this is (no more) an RC bug, please read the background in the BTS. On Sun, 28 Nov 2010 17:47:41 +0100, Luca Capello wrote: Cc:ing all the people that have interacted with this bug. Done again, please forgive me if you are no more interested in it. On Sun, 07 Nov 2010 14:52:24 +0100, Thomas Koch wrote: Adam D. Barratt: On Sun, 2010-11-07 at 11:38 +0100, Thomas Koch wrote: So until nothing else happens, please don't include solr in Debian squeeze. The package has a reverse-dependency in testing already, so can't be removed right now: Checking reverse dependencies... # Broken Depends: chef: chef-solr to the maintainer of Chef in Debian, this is just to inform you, that there is a recommendation from me to remove the solr package from Debian. However since chef-solr does depend on solr, you'd affected by this removal. Some hints about the chef package in Debian: - Debian has (6-month-old) 0.8.16-4.1, while upstream is at 0.9.12 - popcon show 41 installation (2 recent) for the chef binary package and 2 (0 recent) for the chef-solr binary package - there is an RC bug for chef-solr (#604231, installation fails because of nodedown) Thus, I think the best thing would be to remove chef from squeeze (new bugs created), so then we can remove solr as well. No need anymore to remove chef from squeeze, given that after its maintainer hint I uploaded the 0.8.16-4.2 NMU which removes any -server* and -solr package. This is the reason why I closed this bug with the NMU version. It's also in lenny (albeit in contrib) so if it were removed then a migration path for those users to a replacement would be good. Given that chef-solr was not in lenny, the above applies to solr only. However, I should say that I do not know at all a good migration path. This still stands, but I am no solr expert, sorry. Thx, bye, Gismo / Luca pgpsHRzkhLWrt.pgp Description: PGP signature ---End Message---
Bug#604925: /usr/lib/libgssapi_krb5.so.2: cannot login to ssh after upgrade from lenny to squeeze
Sam Hartman hartm...@debian.org writes:
Hi. At today's release meeting, MIT indicated that they are going to
set up an OSX X test environment to reproduce this problem. They will
also look into whether we can ignore the PAC and remove it from the
authdata if it fails to verify rather than failing the authentication.
There was agreement that if we do that we need to insert a trace point
in the PAC code so we can know that the PAC is not verified.
I have reproduced the bug against Mac OS 10.6 Server. The following
patch appears to work (against the trunk; I believe the 1.8 release
didn't have tracing support). Sam, does it look reasonable to you?
diff --git a/src/include/k5-trace.h b/src/include/k5-trace.h
index 3efe0e4..43d63cc 100644
--- a/src/include/k5-trace.h
+++ b/src/include/k5-trace.h
@@ -177,6 +177,10 @@
#define TRACE_INIT_CREDS_SERVICE(c, service) \
TRACE(c, (c, Setting initial creds service to {string}, service))
+#define TRACE_MSPAC_DISCARD_NOSVCSIG(c) \
+TRACE(c, (c, Discarding MS PAC due to missing service signature. \
+ Apple Open Directory bug?))
+
#define TRACE_KT_GET_ENTRY(c, keytab, princ, vno, enctype, err) \
TRACE(c, (c, Retrieving {princ} from {keytab} (vno {int}, \
enctype {etype}) with result: {kerr}, princ, keytab, \
diff --git a/src/lib/krb5/krb/pac.c b/src/lib/krb5/krb/pac.c
index 983b4e8..64e0d9f 100644
--- a/src/lib/krb5/krb/pac.c
+++ b/src/lib/krb5/krb/pac.c
@@ -637,8 +637,13 @@ krb5_pac_verify(krb5_context context,
return EINVAL;
ret = k5_pac_verify_server_checksum(context, pac, server);
-if (ret != 0)
+if (ret == ENOENT) {
+TRACE_MSPAC_DISCARD_NOSVCSIG(context);
+pac-verified = FALSE;
+return 0;
+} else if (ret != 0) {
return ret;
+}
if (privsvr != NULL) {
ret = k5_pac_verify_kdc_checksum(context, pac, privsvr);
@@ -977,6 +982,11 @@ mspac_get_attribute(krb5_context kcontext,
if (*more != -1 || pacctx-pac == NULL)
return ENOENT;
+/* If it didn't verify, pretend it didn't exist. */
+if (!pacctx-pac-verified) {
+return ENOENT;
+}
+
code = mspac_attr2type(attribute, type);
if (code != 0)
return code;
Bug#604925: /usr/lib/libgssapi_krb5.so.2: cannot login to ssh after upgrade from lenny to squeeze
This patch looks reasonable. I have not confirmed that successfully makes the PAC disappear, but if you've examined the logic there I'm happy to assume it does. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604925: /usr/lib/libgssapi_krb5.so.2: cannot login to ssh after upgrade from lenny to squeeze
Sam Hartman hartm...@debian.org writes: This patch looks reasonable. I have not confirmed that successfully makes the PAC disappear, but if you've examined the logic there I'm happy to assume it does. On the other hand, we do appear to expose the krb5_pac_verify() interface that is called by the static authdata handler mspac_verify() so I should bump the check up a level to mspac_verify(). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603513: [Pkg-javascript-devel] Bug#603513: yui: multiple xss issues in included swf files
On Sun, 5 Dec 2010, Moritz Muehlenhoff wrote: Jaldhar, please prepare an yeu upload which updates the security-buggy SWF from from 603513. Sorry it took me long enough but I have just uploaded 2.8.2r1~squeeze-1 which contains updated SWF files. -- Jaldhar H. Vyas jald...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603513: marked as done (yui: multiple xss issues in included swf files)
Your message dated Fri, 10 Dec 2010 00:34:36 + with message-id e1pqqww-dw...@franck.debian.org and subject line Bug#603513: fixed in yui 2.8.2r1~squeeze-1 has caused the Debian Bug report #603513, regarding yui: multiple xss issues in included swf files 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.) -- 603513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: yui Version: 2.5.0-1 Severity: grave Tags: security Hi, the following CVE (Common Vulnerabilities Exposures) ids were published for yui. CVE-2010-4207[0]: | Cross-site scripting (XSS) vulnerability in the Flash component | infrastructure in YUI 2.4.0 through 2.8.1, as used in Bugzilla, | Moodle, and other products, allows remote attackers to inject | arbitrary web script or HTML via vectors related to | charts/assets/charts.swf. CVE-2010-4208[1]: | Cross-site scripting (XSS) vulnerability in the Flash component | infrastructure in YUI 2.5.0 through 2.8.1, as used in Bugzilla, | Moodle, and other products, allows remote attackers to inject | arbitrary web script or HTML via vectors related to | uploader/assets/uploader.swf. CVE-2010-4209[2]: | Cross-site scripting (XSS) vulnerability in the Flash component | infrastructure in YUI 2.8.0 through 2.8.1, as used in Bugzilla 3.7.1 | through 3.7.3 and 4.1, allows remote attackers to inject arbitrary web | script or HTML via vectors related to swfstore/swfstore.swf. These are fixed in upstream 2.8.2. I couldn't find the patches, and you're going to need source for the affected swf files anyway (i.e. fix bug #591199 first). If you fix the vulnerabilities please also make sure to include the CVE ids in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4207 http://security-tracker.debian.org/tracker/CVE-2010-4207 [1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4208 http://security-tracker.debian.org/tracker/CVE-2010-4208 [2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4209 http://security-tracker.debian.org/tracker/CVE-2010-4209 ---End Message--- ---BeginMessage--- Source: yui Source-Version: 2.8.2r1~squeeze-1 We believe that the bug you reported is fixed in the latest version of yui, which is due to be installed in the Debian FTP archive: libjs-yui-doc_2.8.2r1~squeeze-1_all.deb to main/y/yui/libjs-yui-doc_2.8.2r1~squeeze-1_all.deb libjs-yui_2.8.2r1~squeeze-1_all.deb to main/y/yui/libjs-yui_2.8.2r1~squeeze-1_all.deb yui_2.8.2r1~squeeze-1.diff.gz to main/y/yui/yui_2.8.2r1~squeeze-1.diff.gz yui_2.8.2r1~squeeze-1.dsc to main/y/yui/yui_2.8.2r1~squeeze-1.dsc yui_2.8.2r1~squeeze.orig.tar.gz to main/y/yui/yui_2.8.2r1~squeeze.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 603...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jaldhar H. Vyas jald...@debian.org (supplier of updated yui 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: Thu, 09 Dec 2010 06:58:09 -0500 Source: yui Binary: libjs-yui libjs-yui-doc Architecture: source all Version: 2.8.2r1~squeeze-1 Distribution: unstable Urgency: high Maintainer: Debian Javascript Maintainers pkg-javascript-de...@lists.alioth.debian.org Changed-By: Jaldhar H. Vyas jald...@debian.org Description: libjs-yui - Yahoo User Interface Library libjs-yui-doc - Documentation and examples for the Yahoo User Interface Library Closes: 601604 603513 Changes: yui (2.8.2r1~squeeze-1) unstable; urgency=high . * New upstream version targeted at squeeze. * This version updates the flash files included in the package to address the issues in CVE-2010-4207, CVE-2010-4208, and CVE-2010-4209 (Closes: #603513, #601604) Checksums-Sha1: f26e0de61ae46de33c4a1482736665ff83db9116 1340 yui_2.8.2r1~squeeze-1.dsc 43dd07f38febf5cbc984efe77ffe35ea0f3cf308 10592116 yui_2.8.2r1~squeeze.orig.tar.gz 313d3d91ff1a800d38f2ae71b249233dc673e065 4855 yui_2.8.2r1~squeeze-1.diff.gz f6aa15c6ce71cb47bbc0fa34ce30a9826f353281 2501262 libjs-yui_2.8.2r1~squeeze-1_all.deb f96c45cb643bde02417c626a274e8c0679150f5c 7739666
Bug#606534: Subject: install fail asterisk 1:1.6.2.0~dfsg~beta3-1 Debian unstable. insserv: Service zaptel has to be enabled to start service asterisk
Package: asterisk Version: 1:1.6.2.0~dfsg~beta3-1 and: 1.6.2.0~dfsg~rc1-1 Justification: renders package unusable Severity: grave Tags: patch My patch is included below. *** This was my first time that I tried to submit a bug. I got it wrong. I do not use email a lot either. I have had a sole email, an automated reply sitting in my inbox since my submission back in 05th October 2009. I have resubmitted this bug and patch to include the detail I had gleaned, in case it helps someone. I am learning how the bug reports system works, allbeit slowly. sorry for my delay. I am unsure whether to send to sub...@bugs.debian.org or attach to 552...@bugs.debian.org I will soon see from the effect. I know that both is wrong. I am learning. Sorry for any inconvieniance. *** An error occurred The following details are provided: E: asterisk: subprocess installed post-installation script returned error exit status 1 Setting up asterisk (1:1.6.2.0~dfsg~beta3-1) ... insserv: Service zaptel has to be enabled to start service asterisk insserv: exiting now! The configuration script is throwing a zaptel missing dependency. but zaptel is no more. I believe It should be Recommends: dahdi OR dahdi-linux. The changelog shows:- http://packages.debian.org/changelogs/p ... /changelog Debian Changelog asterisk (1:1.6.2.0~dfsg~beta3-1) 2009 asterisk (1:1.6.2.0~dfsg~beta3-1) unstable; urgency=low [ F L ] * New upstream release. * Remove init script's zaptel-fix action; there's no zaptel any more and was also lintian-buggy in its current form. * Install Zaptel-to-DAHDI.txt, explains the migration procedure from Zaptel to DAHDI and is therefore useful when upgrading from lenny. MY PATCH: I altered a line in file: /etc/init.d/astersisk From: # Required-Start: $local_fs zaptel To: # Required-Start: $local_fs dahdi dahdi-linux Then, # dpkg --configure --force-all asterisk # dpkg --status asterisk Package: asterisk Status: install ok installed = There is more detailed information in my previous work on this issue at : http://forums.debian.net/viewtopic.php?f=5t=44390 I have uninstalled and reinstalled and have identified this potential bug is also in asterisk 1.6.2.0~dfsg~rc1-1 . However I am having many other separate problems which I am diligently but ploddingly resolving. This stops me from testing asterisk quick enough to my satisfaction, to get this potential bug processed. My concern with my patch is, should I specify just one module; dahdi or dahdi-linux ? although specifying both does install asterisk with dahdi ok. but no sign in the dependancies shown below, of dahdi-linux. It depends on what you actually want. My next job is to strip out all the 96 sample configurations somehow, to make asterisk 1.6 useable for a newbie with starter books such as my book, Asterisk,the future of telephony. or the book to be published in January 2010 Practical Asterisk 1.4 and 1.6: From Beginner to Expert to allow me to operate asterisk further, and to test for the effectiveness of my patch. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages asterisk depends on: ii adduser 3.111add and remove users and groups ii asterisk-config 1:1.6.2.0~dfsg~rc1-1 Configuration files for Asterisk ii asterisk-sounds-mai 1:1.6.2.0~dfsg~rc1-1 Core Sound files for Asterisk (Eng ii dahdi 1:2.2.0~rc3-1utilities for using the DAHDI kern ii libasound2 1.0.21a-1shared library for ALSA applicatio ii libc-client2007b8:2007b~dfsg-1.1+b1 c-client library for mail protocol ii libc6 2.9-26 GNU C Library: Shared libraries ii libcap2 1:2.16-5 support for getting/setting POSIX. ii libcurl37.19.5-1.1 Multi-protocol file transfer libra ii libgcc1 1:4.4.1-4GCC support library ii libglib2.0-02.22.0-1 The GLib library of C routines ii libgmime-2.0-2a 2.2.22-4 MIME library ii libgsm1 1.0.13-1 Shared libraries for GSM speech co ii libiksemel3 1.2-4C library for the Jabber IM platfo ii libldap-2.4-2 2.4.17-2 OpenLDAP libraries ii liblua5.1-0 5.1.4-3 Simple, extensible, embeddable pro ii libncurses5 5.7+20090803-2 shared libraries for terminal hand ii libnewt0.52 0.52.10-4Not Erik's Windowing Toolkit - tex ii libogg0 1.1.4~dfsg-1 Ogg bitstream library ii libopenais2 0.83-1 Standards-based cluster framework ii libpopt01.14-4 lib for parsing cmdline parameters ii libpq5 8.4.1-1
Bug#594451: lenny-squeeze upgrade issue
It seems that the procedure has changed, I have created version 1.32-6 and uploaded it to unstable, then submitted #606533 with an unblock request to release.debian.org. Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603986: qgis crashes on startup on PowerPC
On Thu, 9 Dec 2010, Hideki Yamane wrote: On Sat, 4 Dec 2010 12:47:20 -0500 Steve ssinger...@sympatico.ca wrote: If I build the qgis .deb files from source on my machine I don't get the crash but the debs from the repository always crash. Is it possible to force a rebuild of the .debs in testing? Interesting, I cannot reproduce it, always crash with - packages from repository - packages built with pbuilder (sid) - packages built with pbuilder (squeeze) - source from git, built with pbuilder (sid) - source from git, built with pbuilder (squeeze) Steve, how do you build your deb files? I think I did git clone http://pkg-grass.alioth.debian.org/qgis/qgis.git cd qgis.git fakeroot debian/rules binary or something similar set of steps calling debian/rules directly and not using pbuilder. Can you build .debs with debugging symbols? That is what I tried first, only to discover that I didn't get the crash. Can you build .debs with debug symbols? If so I don't mind trying to look through them with gdb. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- 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#605157: calendarserver: Use of PYTHONPATH env var in an insecure way
Processing commands for cont...@bugs.debian.org: tags 605157 + patch Bug #605157 [calendarserver] calendarserver: Use of PYTHONPATH env var in an insecure way Bug #605166 [calendarserver] calendarserver: Use of PYTHONPATH env var in an insecure way Added tag(s) patch. Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 605157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605157 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#605157: calendarserver: Use of PYTHONPATH env var in an insecure way
tags 605157 + patch
thanks
Jakub Wilk jw...@debian.org writes:
tags 605157 - patch
thanks
* Dmitrijs Ledkovs dmitrij.led...@ubuntu.com, 2010-12-03, 22:37:
With my patch applied the resulting /usr/bin/caldavd has:
PYTHONPATH=/usr/lib/twisted-calendarserver/lib/python2.6/site-packages/:+:$PYTHONPATH
So if PYTHONPATH was originally empty or unset, this expands to:
PYTHONPATH=/usr/lib/twisted-calendarserver/lib/python2.6/site-packages/:+:
Err, that's wrong.
You are right. That is wrong. But it's not doing that. It does this in
sh scripts:
export PYTHONPATH=`${python} -c 'import sys; print
/usr/lib/twisted-calendarserver/lib/python%s/site-packages %
(sys.version[:3])'`
and in py scripts:
PYTHONPATH = /usr/lib/twisted-calendarserver/lib/python%s/site-packages %
(sys.version[:3])
So these are fine. The setup.py was rewriting:
#PATH
#PYTHONPATH
in all sh/python scripts to paths that include calendarserver
stuff. setup.py substituted #PYTHONPATH in an insecure way. Currently it
was only used in caldavd, but not needed at all.
I have tested this by running calendarserver with without new patch
and I can add/retrieve calendar events over the network using
thunderbird-lightning.
With regards,
Dmitrijs.
pgpnxfCVpzkD8.pgp
Description: PGP signature
=== modified file 'debian/changelog'
--- calendarserver-2.4.dfsg-2/debian/changelog 2010-08-25 15:23:37 +
+++ calendarserver-2.4.dfsg-2.1/debian/changelog 2010-12-10 00:54:12 +
@@ -1,3 +1,11 @@
+calendarserver (2.4.dfsg-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Do not set PYTHONPATH env var, not needed (Closes: #605166, #605157)
+ * Prevent setup.py from automagically setting #PYTHONPATH in an insecure way
+
+ -- Dmitrijs Ledkovs dmitrij.led...@ubuntu.com Fri, 03 Dec 2010 21:28:40 +
+
calendarserver (2.4.dfsg-2) unstable; urgency=low
* Removed Uploaders field in debian/changelog
=== added file 'debian/patches/secure-python-path.patch'
--- calendarserver-2.4.dfsg-2/debian/patches/secure-python-path.patch 1970-01-01 00:00:00 +
+++ calendarserver-2.4.dfsg-2.1/debian/patches/secure-python-path.patch 2010-12-10 00:52:31 +
@@ -0,0 +1,64 @@
+Removes setting PYTHONPATH in an insecure way, not needed on Debian.
+Removes rewritting rules from setup.py that did that.
+Index: b/setup.py
+===
+--- a/setup.py 2010-12-09 19:21:45.0 -0500
b/setup.py 2010-12-09 19:22:25.0 -0500
+@@ -125,43 +125,3 @@
+ if root:
+ install_lib = install_lib[len(root):]
+
+-for script in dist.scripts:
+-scriptPath = os.path.join(install_scripts, os.path.basename(script))
+-
+-print rewriting %s % (scriptPath,)
+-
+-script = []
+-
+-fileType = None
+-
+-for line in file(scriptPath, r):
+-if not fileType:
+-if line.startswith(#!):
+-if python in line.lower():
+-fileType = python
+-elif sh in line.lower():
+-fileType = sh
+-
+-line = line.rstrip(\n)
+-if fileType == sh:
+-if line == #PYTHONPATH:
+-script.append('PYTHONPATH=%s:$PYTHONPATH' % (install_lib,))
+-elif line == #PATH:
+-script.append('PATH=%s:$PATH' % (os.path.join(base, bin),))
+-else:
+-script.append(line)
+-
+-elif fileType == python:
+-if line == #PYTHONPATH:
+-script.append('PYTHONPATH=%s' % (install_lib,))
+-elif line == #PATH:
+-script.append('PATH=%s' % (os.path.join(base, bin),))
+-else:
+-script.append(line)
+-
+-else:
+-script.append(line)
+-
+-newScript = open(scriptPath, w)
+-newScript.write(\n.join(script))
+-newScript.close()
+Index: b/bin/caldavd
+===
+--- a/bin/caldavd 2010-12-09 19:21:51.0 -0500
b/bin/caldavd 2010-12-09 19:22:41.0 -0500
+@@ -16,9 +16,6 @@
+ # limitations under the License.
+ ##
+
+-#PATH
+-#PYTHONPATH
+-
+ daemonize=;
+ username=;
+ groupname=;
=== modified file 'debian/patches/series'
--- calendarserver-2.4.dfsg-2/debian/patches/series 2010-08-25 15:23:37 +
+++ calendarserver-2.4.dfsg-2.1/debian/patches/series 2010-12-10 00:52:31 +
@@ -2,3 +2,4 @@
ldapdirectory.patch
paths.diff
linux-xattr-fix.patch
+secure-python-path.patch
Bug#604925: /usr/lib/libgssapi_krb5.so.2: cannot login to ssh after upgrade from lenny to squeeze
forwarded 604925 http://krbdev.mit.edu/rt/Ticket/Display.html?id=6839user=guestpass=guest tags 604925 + confirmed upstream fixed-upstream thanks I committed a slightly different fix that avoids breaking the krb5_pac_verify() API. http://src.mit.edu/fisheye/changelog/krb5/?cs=24564 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592151: marked as done (python-quixote: Import of .ptl files fails)
Your message dated Fri, 10 Dec 2010 01:32:06 +
with message-id e1pqrqa-00041p...@franck.debian.org
and subject line Bug#592151: fixed in quixote 2.7~b2-1
has caused the Debian Bug report #592151,
regarding python-quixote: Import of .ptl files fails
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.)
--
592151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-quixote
Version: 2.5-5+b1
Severity: important
Importing .ptl files fails in python 2.6. Fixed in upstream quixote 2.7b2.
Steps to reproduce:
$ python
Python 2.6.5+ (release26-maint, Jul 6 2010, 14:48:45)
[GCC 4.4.4] on linux2
Type help, copyright, credits or license for more information.
from quixote.demo import create_publisher
/usr/lib/pymodules/python2.6/quixote/http_response.py:7: DeprecationWarning:
the sets module is deprecated
from sets import Set
from quixote.server.simple_server import run
run(create_publisher, host='localhost', port=8080)
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib/pymodules/python2.6/quixote/server/simple_server.py, line 99,
in run
publisher = create_publisher()
File /usr/lib/pymodules/python2.6/quixote/demo/__init__.py, line 6, in
create_publisher
from quixote.demo.root import RootDirectory
File /usr/lib/pymodules/python2.6/quixote/ptl/ptl_import.py, line 116, in
find_import_module
return self.loader.load_module(fullname, stuff)
File /usr/lib/pymodules/python2.6/quixote/ptl/ptl_import.py, line 96, in
load_module
return _load_ptl(name, filename, file)
File /usr/lib/pymodules/python2.6/quixote/ptl/ptl_import.py, line 76, in
_load_ptl
return _exec_module_code(code, name, filename)
File /usr/lib/pymodules/python2.6/quixote/ptl/ptl_import.py, line 28, in
_exec_module_code
exec code in mod.__dict__
File /usr/lib/pymodules/python2.6/quixote/demo/root.ptl, line 100, in
module
.decode('base64')
File /usr/lib/python2.6/encodings/__init__.py, line 100, in search_function
level=0)
TypeError: import_module() takes no keyword arguments
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.35 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages python-quixote depends on:
ii python2.6.5-11 interactive high-level object-orie
ii python-support1.0.9 automated rebuilding support for P
Versions of packages python-quixote recommends:
ii python-quixote-doc2.5-5 Quixote web application framework
python-quixote suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: quixote
Source-Version: 2.7~b2-1
We believe that the bug you reported is fixed in the latest version of
quixote, which is due to be installed in the Debian FTP archive:
python-quixote-doc_2.7~b2-1_all.deb
to main/q/quixote/python-quixote-doc_2.7~b2-1_all.deb
python-quixote_2.7~b2-1_i386.deb
to main/q/quixote/python-quixote_2.7~b2-1_i386.deb
quixote_2.7~b2-1.debian.tar.gz
to main/q/quixote/quixote_2.7~b2-1.debian.tar.gz
quixote_2.7~b2-1.dsc
to main/q/quixote/quixote_2.7~b2-1.dsc
quixote_2.7~b2.orig.tar.gz
to main/q/quixote/quixote_2.7~b2.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 592...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Oleksandr Moskalenko ma...@debian.org (supplier of updated quixote 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: Thu, 09 Dec 2010 16:33:33 -0600
Source: quixote
Binary: python-quixote python-quixote-doc
Architecture: source i386 all
Version: 2.7~b2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Changed-By: Oleksandr Moskalenko ma...@debian.org
Description:
python-quixote - A highly Pythonic Web application framework
python-quixote-doc - Quixote web application framework documentation
Closes: 514762 564332 592151
Changes:
quixote (2.7~b2-1)
Bug#606371: kopete: Kopete freezes immediately when opening opening settings dialog (TV-card present in system)
Hello, On trečiadienis 08 Gruodis 2010 21:02:10 Andreas Jacob wrote: When I try to open the kopete settings dialog, and the dialog pops up, kopete freezes immediately. I've searched upstream for a similar bug and found someone: http://bugs.kde.org/show_bug.cgi?id=241507 . As in descriped in the upstream bugreport I have a TV card in my computer (Hauppauge). Here ist the relevant output of lspci: 01:01.0 Multimedia video controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 01:01.1 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05) 01:01.2 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) 01:01.4 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05) And here is the output, when starting kopete from the command line: libv4l2: error dequeuing buf: Eingabe-/Ausgabefehler VIDIOC_DQBUF error 5, Eingabe-/Ausgabefehler libv4l2: error dequeuing buf: Eingabe-/Ausgabefehler VIDIOC_DQBUF error 5, Eingabe-/Ausgabefehler Eingabe-/Ausgabefehler is german for input/output error. As seen in the resolved upstream bug message, the error should have been fixed upstream some month ago. May be it's a regression of that bug? As an additional note: in my apt sources.list I use the debian-multimedia repository. Would you mind explaining why you chose grave severity for this bug? Misconfigured TV cards like yours are not that common at all and settings dialog is not renders package unusable. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Processed: Bug#604925: /usr/lib/libgssapi_krb5.so.2: cannot login to ssh after upgrade from lenny to squeeze
Processing commands for cont...@bugs.debian.org: forwarded 604925 http://krbdev.mit.edu/rt/Ticket/Display.html?id=6839user=guestpass=guest Bug #604925 [libgssapi-krb5-2] Squeeze krb5 fails to work with Open Directory KDC tickets Set Bug forwarded-to-address to 'http://krbdev.mit.edu/rt/Ticket/Display.html?id=6839user=guestpass=guest'. tags 604925 + confirmed upstream fixed-upstream - moreinfo Bug #604925 [libgssapi-krb5-2] Squeeze krb5 fails to work with Open Directory KDC tickets Added tag(s) upstream, confirmed, and fixed-upstream. Bug #604925 [libgssapi-krb5-2] Squeeze krb5 fails to work with Open Directory KDC tickets Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 604925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604925 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#606540: Broken on Youtube starting today
Package: clive Version: 2.2.13-3 Severity: grave Youtube changed something again. All requests now just end up in error: Unknown error (http/404) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606541: zabbix-server-mysql: affected by privilege escalation vulnerability in logrotate
Package: zabbix-server-mysql Version: 1.6.5-1 Severity: grave Justification: privilege escalation vulnerability Tags: security There was a privilege escalation vulnerability in logrotate that I reported about four years ago and which finally got fixed in testing rouhgly one year ago (see bug #388608). In lenny this vulnerability still exists and logrotate's maintainer doesn't seem to be interested in fixing it, given that nothing of substance has happened since when I last notified him of the problem about two weeks ago. As a proof of concept, I did successfully use it to elevate my privileges from the postgres user to root. As it affects packages where the log directory is writable for the package's system user, I based this mass filing on a rough analysis of maintainer scripts, avoiding the effort of actually installing and testing each individual package. These lines from this package's maintainer scripts suggest that it likely is affected by the vulnerability: --- chown zabbix:zabbix /var/log/zabbix-server -R --- Please note that the analysis this mass filing is based on also is roughly a year old, and anyhow I don't recall which debian suite I based it on at that time--as such, this report may be against the wrong version and otherwise outdated in some details. Given how much effort I have already needlessly put into this, I hope you have some understanding for me not polishing this bug report. Primarily I am filing this bug in order to allow the maintainers of packages using logrotate to work around logrotate if they deem that necessary. Also, you should note that the security fix in testing introduces a regression that may also affect this package which could cause data loss in situations where this couldn't happen before. A fix for this regression is available to logrotate's maintainer, also still unapplied for over a year. A mass filing against packages affected by that regression may follow later. For some further details please see my announcement of this mass filing on debian-qa: http://lists.debian.org/debian-qa/2010/11/msg00024.html I would also suggest to use that thread for any further discussion that is not specific to this package and possibly for coordination between maintainers of affected packages in order to avoid duplicated efforts where possible. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606540: severity of 606540 is important
# Automatically generated email from bts, devscripts version 2.10.35lenny7 # clive supports more than just youtube severity 606540 important -- 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 606540 is important
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 # clive supports more than just youtube severity 606540 important Bug #606540 [clive] Broken on Youtube starting today Severity set to 'important' from 'grave' End of message, stopping processing here. Please contact me if you need assistance. -- 606540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606540 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#606543: clamav-freshclam: affected by privilege escalation vulnerability in logrotate
Package: clamav-freshclam Version: 0.95.2+dfsg-4 Severity: grave Justification: privilege escalation vulnerability Tags: security There was a privilege escalation vulnerability in logrotate that I reported about four years ago and which finally got fixed in testing rouhgly one year ago (see bug #388608). In lenny this vulnerability still exists and logrotate's maintainer doesn't seem to be interested in fixing it, given that nothing of substance has happened since when I last notified him of the problem about two weeks ago. As a proof of concept, I did successfully use it to elevate my privileges from the postgres user to root. As it affects packages where the log directory is writable for the package's system user, I based this mass filing on a rough analysis of maintainer scripts, avoiding the effort of actually installing and testing each individual package. These lines from this package's maintainer scripts suggest that it likely is affected by the vulnerability: --- chmod 640 $FRESHCLAMLOGFILE chown $dbowner:adm $FRESHCLAMLOGFILE --- Please note that the analysis this mass filing is based on also is roughly a year old, and anyhow I don't recall which debian suite I based it on at that time--as such, this report may be against the wrong version and otherwise outdated in some details. Given how much effort I have already needlessly put into this, I hope you have some understanding for me not polishing this bug report. Primarily I am filing this bug in order to allow the maintainers of packages using logrotate to work around logrotate if they deem that necessary. Also, you should note that the security fix in testing introduces a regression that may also affect this package which could cause data loss in situations where this couldn't happen before. A fix for this regression is available to logrotate's maintainer, also still unapplied for over a year. A mass filing against packages affected by that regression may follow later. For some further details please see my announcement of this mass filing on debian-qa: http://lists.debian.org/debian-qa/2010/11/msg00024.html I would also suggest to use that thread for any further discussion that is not specific to this package and possibly for coordination between maintainers of affected packages in order to avoid duplicated efforts where possible. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606544: postgresql-common: affected by privilege escalation vulnerability in logrotate
Package: postgresql-common Version: 100 Severity: grave Justification: privilege escalation vulnerability Tags: security There was a privilege escalation vulnerability in logrotate that I reported about four years ago and which finally got fixed in testing rouhgly one year ago (see bug #388608). In lenny this vulnerability still exists and logrotate's maintainer doesn't seem to be interested in fixing it, given that nothing of substance has happened since when I last notified him of the problem about two weeks ago. As a proof of concept, I did successfully use it to elevate my privileges from the postgres user to root. As it affects packages where the log directory is writable for the package's system user, I based this mass filing on a rough analysis of maintainer scripts, avoiding the effort of actually installing and testing each individual package. These lines from this package's maintainer scripts suggest that it likely is affected by the vulnerability: --- chmod 1775 /var/log/postgresql chown root:postgres /var/log/postgresql --- Please note that the analysis this mass filing is based on also is roughly a year old, and anyhow I don't recall which debian suite I based it on at that time--as such, this report may be against the wrong version and otherwise outdated in some details. Given how much effort I have already needlessly put into this, I hope you have some understanding for me not polishing this bug report. Primarily I am filing this bug in order to allow the maintainers of packages using logrotate to work around logrotate if they deem that necessary. Also, you should note that the security fix in testing introduces a regression that may also affect this package which could cause data loss in situations where this couldn't happen before. A fix for this regression is available to logrotate's maintainer, also still unapplied for over a year. A mass filing against packages affected by that regression may follow later. For some further details please see my announcement of this mass filing on debian-qa: http://lists.debian.org/debian-qa/2010/11/msg00024.html I would also suggest to use that thread for any further discussion that is not specific to this package and possibly for coordination between maintainers of affected packages in order to avoid duplicated efforts where possible. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606545: polipo: affected by privilege escalation vulnerability in logrotate
Package: polipo Version: 1.0.4-1 Severity: grave Justification: privilege escalation vulnerability Tags: security There was a privilege escalation vulnerability in logrotate that I reported about four years ago and which finally got fixed in testing rouhgly one year ago (see bug #388608). In lenny this vulnerability still exists and logrotate's maintainer doesn't seem to be interested in fixing it, given that nothing of substance has happened since when I last notified him of the problem about two weeks ago. As a proof of concept, I did successfully use it to elevate my privileges from the postgres user to root. As it affects packages where the log directory is writable for the package's system user, I based this mass filing on a rough analysis of maintainer scripts, avoiding the effort of actually installing and testing each individual package. These lines from this package's maintainer scripts suggest that it likely is affected by the vulnerability: --- chmod -R 640 $LOG_DIR chown proxy:adm $LOG_DIR chmod 2755 $LOG_DIR --- Please note that the analysis this mass filing is based on also is roughly a year old, and anyhow I don't recall which debian suite I based it on at that time--as such, this report may be against the wrong version and otherwise outdated in some details. Given how much effort I have already needlessly put into this, I hope you have some understanding for me not polishing this bug report. Primarily I am filing this bug in order to allow the maintainers of packages using logrotate to work around logrotate if they deem that necessary. Also, you should note that the security fix in testing introduces a regression that may also affect this package which could cause data loss in situations where this couldn't happen before. A fix for this regression is available to logrotate's maintainer, also still unapplied for over a year. A mass filing against packages affected by that regression may follow later. For some further details please see my announcement of this mass filing on debian-qa: http://lists.debian.org/debian-qa/2010/11/msg00024.html I would also suggest to use that thread for any further discussion that is not specific to this package and possibly for coordination between maintainers of affected packages in order to avoid duplicated efforts where possible. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606547: mathopd: affected by privilege escalation vulnerability in logrotate
Package: mathopd Version: 1.5p6-1 Severity: grave Justification: privilege escalation vulnerability Tags: security There was a privilege escalation vulnerability in logrotate that I reported about four years ago and which finally got fixed in testing rouhgly one year ago (see bug #388608). In lenny this vulnerability still exists and logrotate's maintainer doesn't seem to be interested in fixing it, given that nothing of substance has happened since when I last notified him of the problem about two weeks ago. As a proof of concept, I did successfully use it to elevate my privileges from the postgres user to root. As it affects packages where the log directory is writable for the package's system user, I based this mass filing on a rough analysis of maintainer scripts, avoiding the effort of actually installing and testing each individual package. These lines from this package's maintainer scripts suggest that it likely is affected by the vulnerability: --- chown -R www-data:www-data /var/log/mathopd --- Please note that the analysis this mass filing is based on also is roughly a year old, and anyhow I don't recall which debian suite I based it on at that time--as such, this report may be against the wrong version and otherwise outdated in some details. Given how much effort I have already needlessly put into this, I hope you have some understanding for me not polishing this bug report. Primarily I am filing this bug in order to allow the maintainers of packages using logrotate to work around logrotate if they deem that necessary. Also, you should note that the security fix in testing introduces a regression that may also affect this package which could cause data loss in situations where this couldn't happen before. A fix for this regression is available to logrotate's maintainer, also still unapplied for over a year. A mass filing against packages affected by that regression may follow later. For some further details please see my announcement of this mass filing on debian-qa: http://lists.debian.org/debian-qa/2010/11/msg00024.html I would also suggest to use that thread for any further discussion that is not specific to this package and possibly for coordination between maintainers of affected packages in order to avoid duplicated efforts where possible. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606548: pymsnt: affected by privilege escalation vulnerability in logrotate
Package: pymsnt Version: 0.11.3-4 Severity: grave Justification: privilege escalation vulnerability Tags: security There was a privilege escalation vulnerability in logrotate that I reported about four years ago and which finally got fixed in testing rouhgly one year ago (see bug #388608). In lenny this vulnerability still exists and logrotate's maintainer doesn't seem to be interested in fixing it, given that nothing of substance has happened since when I last notified him of the problem about two weeks ago. As a proof of concept, I did successfully use it to elevate my privileges from the postgres user to root. As it affects packages where the log directory is writable for the package's system user, I based this mass filing on a rough analysis of maintainer scripts, avoiding the effort of actually installing and testing each individual package. These lines from this package's maintainer scripts suggest that it likely is affected by the vulnerability: --- chown -R pymsnt:adm /var/log/pymsnt --- Please note that the analysis this mass filing is based on also is roughly a year old, and anyhow I don't recall which debian suite I based it on at that time--as such, this report may be against the wrong version and otherwise outdated in some details. Given how much effort I have already needlessly put into this, I hope you have some understanding for me not polishing this bug report. Primarily I am filing this bug in order to allow the maintainers of packages using logrotate to work around logrotate if they deem that necessary. Also, you should note that the security fix in testing introduces a regression that may also affect this package which could cause data loss in situations where this couldn't happen before. A fix for this regression is available to logrotate's maintainer, also still unapplied for over a year. A mass filing against packages affected by that regression may follow later. For some further details please see my announcement of this mass filing on debian-qa: http://lists.debian.org/debian-qa/2010/11/msg00024.html I would also suggest to use that thread for any further discussion that is not specific to this package and possibly for coordination between maintainers of affected packages in order to avoid duplicated efforts where possible. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606549: bayonne: affected by privilege escalation vulnerability in logrotate
Package: bayonne Version: 2.3.2-3+b2 Severity: grave Justification: privilege escalation vulnerability Tags: security There was a privilege escalation vulnerability in logrotate that I reported about four years ago and which finally got fixed in testing rouhgly one year ago (see bug #388608). In lenny this vulnerability still exists and logrotate's maintainer doesn't seem to be interested in fixing it, given that nothing of substance has happened since when I last notified him of the problem about two weeks ago. As a proof of concept, I did successfully use it to elevate my privileges from the postgres user to root. As it affects packages where the log directory is writable for the package's system user, I based this mass filing on a rough analysis of maintainer scripts, avoiding the effort of actually installing and testing each individual package. These lines from this package's maintainer scripts suggest that it likely is affected by the vulnerability: --- chown -R bayonne /var/log/bayonne --- Please note that the analysis this mass filing is based on also is roughly a year old, and anyhow I don't recall which debian suite I based it on at that time--as such, this report may be against the wrong version and otherwise outdated in some details. Given how much effort I have already needlessly put into this, I hope you have some understanding for me not polishing this bug report. Primarily I am filing this bug in order to allow the maintainers of packages using logrotate to work around logrotate if they deem that necessary. Also, you should note that the security fix in testing introduces a regression that may also affect this package which could cause data loss in situations where this couldn't happen before. A fix for this regression is available to logrotate's maintainer, also still unapplied for over a year. A mass filing against packages affected by that regression may follow later. For some further details please see my announcement of this mass filing on debian-qa: http://lists.debian.org/debian-qa/2010/11/msg00024.html I would also suggest to use that thread for any further discussion that is not specific to this package and possibly for coordination between maintainers of affected packages in order to avoid duplicated efforts where possible. -- 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 606537 is grave
Processing commands for cont...@bugs.debian.org: # youtube-dl currently does not function at all; not any less grave just because this happens frequently severity 606537 grave Bug #606537 [youtube-dl] youtube-dl: new upstream version Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 606537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606537 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
