Bug#694546: HID: Add Apple wireless keyboard 2011 ANSI to special driver list
Commit 0a97e1e9f9a6 ('HID: apple: Add Apple wireless keyboard 2011 ANSI PID')
did not update the special driver list in hid-core.c, so hid-generic may
still bind to this device.
Reported-by: Ari Pollak a...@scvngr.com
References: http://bugs.debian.org/694546
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Cc: sta...@vger.kernel.org
---
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1528,6 +1528,7 @@
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE,
USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_ANSI) },
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE,
USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_ISO) },
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE,
USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_JIS) },
+ { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE,
USB_DEVICE_ID_APPLE_ALU_WIRELESS_2011_ANSI) },
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE,
USB_DEVICE_ID_APPLE_ALU_WIRELESS_2011_ISO) },
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE,
USB_DEVICE_ID_APPLE_FOUNTAIN_TP_ONLY) },
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE,
USB_DEVICE_ID_APPLE_GEYSER1_TP_ONLY) },
signature.asc
Description: This is a digitally signed message part
Bug#694631: oss4: Review of vmix FPU usage
I asked H. Peter Anvin (one of the Linux x86 maintainers) to review the FPU code. This was done on IRC so I'll summarise: 1. oss_fp_check() has no need to use kernel_fpu_begin() and kernel_fpu_end(). But it should use the CPU features API (see arch/x86/include/asm/cpufeature.h). 2. oss_fp_save() and oss_fp_restore() *must not* modify cr0 or cr4 directly. kernel_fpu_begin() and kernel_fpu_end() take care of the necessary CR changes. However the WARNING in this bug shows that vmix FPU usage is fundamentally unsafe - it calls these functions from an IRQ handler, and it is not always possible to use the FPU then without corrupting the state of the current task. Please disable CONFIG_OSS_VMIX_FLOAT. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#694670: pseudo reproducible
Lisandro, many thanks for looking into that. Am Sunday 02 December 2012 schrieb Lisandro Damián Nicanor Pérez Meyer: Control: severity -1 important Control: tag -1 moreinfo Hi! Well, first of all, this bug (694670) it's about kscd not playing music. Let's use 694796 for the crash. I've tried with my PC and I can play CDs with just the first one one of my two CD-ROM drives. Interestingly enough, only my first drive has the analog audio connected to the motherboard. I have not tried, but maybe this could be an issue. I'm using phonon-backend-gstreamer and *no* pulseaudio. I have also tried removing 70-persistant-cd.rules and restarting udev, same outcome. Then I rebooted and got the same output. I'm so lowing the severity of this bug because it's not unusable at all. Rainer: I would like to know which phonon backend are you using, if you have pulseaudio running and if you have both udisks and udisks2 installed in the system. You may have already written so, but I missed it between the backtraces ;-) That is my setup: udisk installed udisk2 not installed pulseaudio is running. Here are the details: rd@blackbox:~$ apt-cache policy udisks udisks: Installiert: 1.0.4-7 Installationskandidat: 1.0.4-7 Versionstabelle: *** 1.0.4-7 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status rd@blackbox:~$ apt-cache policy udisks2 udisks2: Installiert: (keine) Installationskandidat: 2.0.0-3 Versionstabelle: 2.0.0-3 0 200 http://ftp-stud.fht-esslingen.de/debian/ experimental/main i386 Packages rd@blackbox:~$ rd@blackbox:~$ apt-cache policy gstreamer0.10-pulseaudio gstreamer0.10-pulseaudio: Installiert: 0.10.31-3+nmu1 Installationskandidat: 0.10.31-3+nmu1 Versionstabelle: *** 0.10.31-3+nmu1 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status rd@blackbox:~$ apt-cache policy gstreamer1.0-pulseaudio gstreamer1.0-pulseaudio: Installiert: (keine) Installationskandidat: 1.0.3-1 Versionstabelle: 1.0.3-1 0 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages rd@blackbox:~$ apt-cache policy libpulse0 libpulse0: Installiert: 2.0-6 Installationskandidat: 2.0-6 Versionstabelle: 2.1-2 0 200 http://ftp-stud.fht-esslingen.de/debian/ experimental/main i386 Packages *** 2.0-6 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status rd@blackbox:~$ apt-cache policy phonon-backend-gstreamer phonon-backend-gstreamer: Installiert: (keine) Installationskandidat: 4:4.6.0.0-2 Versionstabelle: 4:4.6.0.0-2 0 500 http://ftp-stud.fht-esslingen.de/debian/ wheezy/main i386 Packages 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages rd@blackbox:~$ ps uaxwww|grep pulse kathrin 4373 0.0 0.0 99496 2072 ?Sl Nov30 0:03 /usr/bin/pulseaudio --start --log-target=syslog rd 18935 0.0 0.0 99636 3148 ?Sl Nov30 0:56 /usr/bin/pulseaudio --start --log-target=syslog rd 26583 0.0 0.0 4112 824 pts/6S+ 16:26 0:00 grep pulse rd@blackbox:~$ Thanks again, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ signature.asc Description: This is a digitally signed message part.
Bug#694934: Installer hangs at detect network hardware
On Sun 02 Dec 2012 at 12:22:50 +, R.M. Thomas wrote: Comments/Problems: I chose: Advanced options Alternative desktop environments Xfce Advanced options Expert install and answered questions about language, keyboard, locale (default), modules to load (default), extra installer components (none). At the next stage Detect network hardware the installation stalled indefinitely (more than ten minutes) with a blue screen having a single white line at the bottom and a black cursor. Keyboard input was echoed to this bottom line, but I was unable to get any other response from the system and was obliged to use the machine's power on/off switch. Ctrl-C should get you back to the main menu. Please look at #694582 and see if it helps. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694943: Panelize loses files after find
Package: mc Version: 3:4.8.3-10 Severity: normal If 'Command' 'Find files' find many (over ~256) files , panelize shows only some (127/255) of them. If find recursive '*a*' files in /usr, panelize show only 127 out of 60K+ files. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mc depends on: ii e2fslibs 1.42.5-1 ext2/ext3/ext4 file system librari ii libc6 2.13-37Embedded GNU C Library: Shared lib ii libcomerr21.42.5-1 common error description library ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgpm2 1.20.4-3.3 General Purpose Mouse - shared lib ii libslang2 2.2.4-15 S-Lang programming library - runti ii mc-data 3:4.8.3-10 Midnight Commander - a powerful fi Versions of packages mc recommends: ii mime-support 3.48-1MIME files 'mime.types' 'mailcap ii perl 5.10.1-17squeeze3 Larry Wall's Practical Extraction ii unzip 6.0-4 De-archiver for .zip files Versions of packages mc suggests: pn arj none (no description available) ii bzip2 1.0.5-6+squeeze1 high-quality block-sorting file co pn catdvi none (no description available) pn dbview none (no description available) pn djvulibre-bin none (no description available) ii evince [pdf-viewer] 2.30.3-2+squeeze1Document (PostScript, PDF) viewer ii file5.04-5+squeeze2 Determines file type using magic pn gv none (no description available) ii imagemagick 8:6.6.0.4-3+squeeze3 image manipulation programs pn odt2txt none (no description available) ii python 2.6.6-3+squeeze7 interactive high-level object-orie pn python-boto none (no description available) pn python-tz none (no description available) ii w3m 0.5.2-9 WWW browsable pager with excellent pn zip none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694942: dspam: incompatible with wheezy's postgresql version
Le dimanche 2 décembre 2012 15:53:13, vous avez écrit : Package: dspam Version: 3.10.1+dfsg-5 Severity: normal Dear Maintainer, After migrating my dspam database to a new PostgreSQL server, I'm seeing the following errors in PG's log (edited for readability): ERROR: invalid byte sequence for encoding UTF8: 0xae: INSERT INTO dspam_signature_data (uid,signature,length,created_on,data) VALUES (1,E'4ed4de1c291545272412566',752,CURRENT_DATE,... ') which results in the insert being aborted. Although the message gets delivered succesfully, users cannot retrain on these messages because the signature doesn't get stored in the database. According to http://article.gmane.org/gmane.mail.spam.dspam.user/18022 http://sourceforge.net/tracker/?func=detailatid=1126468aid=3023888group_ id=250683 the workaround is to set standard_conforming_strings=off in postgresql.conf, which works for me but may not be possible for others (e.g. because of other databases in the same cluster). I can think of multiple solutions here: - unblock 3.10.2 because it is said to have a fix for this issue (not verified, I don't want to start mixing releases even before wheezy is released) - backport the 3.10.2 fix to wheezy's 3.10.1 Both of these solution are not possible since the bug is only severity normal. It might be OK for the release team to unblock a package with the workaround backported if the bug was severity important but I don't think this bug is important. Dspam only fails to *retrain* (not filter) of *some* mails. - document this incompatibility+workaround in the release notes I'll think about this one. Is the bug related to the new version of dspam? Were you using dspam with PostgreSQL before without this problem? In addition, we can provide backports for wheezy once it's released. Naturally the latter would be my least favourite option :) Unfortunetely, freeze means the other solution are not good options. Regards, Arno Thanks for your bug report. Best regards, Thomas signature.asc Description: This is a digitally signed message part.
Bug#694944: dvb-apps: no more conflict with recent nmh
Package: dvb-apps Version: 1.1.1+rev1483-1 Hello, dvb-apps conflicts with nmh since both packages used to install a manpage scan.1.gz (bug #654810). Now, nmh has renamed its manpage to scan.1mh.gz (bug #694814), so the conflict should be restricted to old versions of nmh only. Could you please change the Conflicts: nmh to Conflicts: nmh ( 1.5-release-2) Replaces: nmh ( 1.5-release-2) Thanks -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694945: foomatic: cannot get PPD for Canon-PIXMA-iP3000 and many others
Package: foomatic-db-engine Version: 4.0.8-3 Severity: normal There are apparently 3 CUPS drivers in Debian for the Pixma iP3000: gutenprint.5.2://bjc-PIXMA-iP3000/expert foomatic:Canon-PIXMA-iP3000-gutenprint-ijs.5.2.ppd foomatic:Canon-PIXMA-iP3000-gutenprint-ijs-simplified.5.2.ppd If I try to use one of the latter two in CUPS, I get the following errors when selecting them from the Web UI (here copied from cups/error_log): E [02/Dec/2012:16:10:17 +0100] [CGI] Could not determine driver name for Canon-PIXMA-iP3000-gutenprint-ijs.5.2.ppd! E [02/Dec/2012:16:10:17 +0100] copy_model: empty PPD file E [02/Dec/2012:16:10:17 +0100] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost/printers/Canon_iP3000_gutenprint_ijs) from localhost E [02/Dec/2012:16:10:23 +0100] [CGI] Could not determine driver name for Canon-PIXMA-iP3000-gutenprint-ijs-simplified.5.2.ppd! E [02/Dec/2012:16:10:23 +0100] copy_model: empty PPD file E [02/Dec/2012:16:10:23 +0100] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost/printers/Canon_iP3000_gutenprint_ijs) from localhost The problem seems to come from /usr/lib/cups/driver/foomatic itself - whereas .../foomatic cat drv works with drivers that specify a last field with many info (MFG, etc), there seems to be a problem with those that only show DRV there, which seem to be all those shown by /usr/lib/cups/driver/foomatic list | grep -v MFG # /usr/lib/cups/driver/foomatic list | grep -i ip3000 foomatic:Canon-PIXMA-iP3000-gutenprint-ijs.5.2.ppd en Canon Canon PIXMA-iP3000 Foomatic/gutenprint-ijs.5.2 DRV:Dgutenprint-ijs.5.2,M0,TF; foomatic:Canon-PIXMA-iP3000-gutenprint-ijs-simplified.5.2.ppd en Canon Canon PIXMA-iP3000 Foomatic/gutenprint-ijs-simplified.5.2 DRV:Dgutenprint-ijs-simplified.5.2,M0,TF; # /usr/lib/cups/driver/foomatic cat foomatic:Canon-PIXMA-iP3000-gutenprint-ijs.5.2.ppd ERROR: Could not determine driver name for Canon-PIXMA-iP3000-gutenprint-ijs.5.2.ppd! # /usr/lib/cups/driver/foomatic cat foomatic:Canon-PIXMA-iP3000-gutenprint-ijs-simplified.5.2.ppd ERROR: Could not determine driver name for Canon-PIXMA-iP3000-gutenprint-ijs-simplified.5.2.ppd! # /usr/lib/cups/driver/foomatic cat foomatic:Epson-PictureMate_260-gutenprint-ijs.5.2.ppd|head -1 ERROR: Could not determine driver name for Epson-PictureMate_260-gutenprint-ijs.5.2.ppd! # /usr/lib/cups/driver/foomatic cat foomatic:Epson-Stylus_T20-gutenprint-ijs.5.2.ppd|head -1 ERROR: Could not determine driver name for Epson-Stylus_T20-gutenprint-ijs.5.2.ppd! ... -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages foomatic-db-engine depends on: ii bash 4.2-4 ii curl 7.26.0-1 ii foomatic-filters 4.0.17-1 ii libc6 2.13-37 ii libxml2 2.8.0+dfsg1-6 ii perl 5.14.2-15 ii wget 1.13.4-3 Versions of packages foomatic-db-engine recommends: ii cups 1.5.3-2.4 ii cups-client 1.5.3-2.4 ii foomatic-db 20120523-1 ii netcat-traditional [netcat] 1.10-40 Versions of packages foomatic-db-engine suggests: ii foomatic-db-gutenprint 5.2.9-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694947: bind9: package upgrade overwrites gid owner of /etc/bind/named.conf.local
Package: bind9 Version: 1:9.7.3.dfsg-1~squeeze8 Severity: normal After a recent bind9 security upgrade (and probably after previous upgrades too), our config management system reported that /etc/bind/named.conf.local had had its group owner changed from the one we'd configured to the group bind. Presumably it was the package upgrade that caused this. Shouldn't /etc/bind/named.conf.local be a configuration file controlled by the system administrator without unwanted subversion of either content or metadata by the package manager? -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32.33-kvm-i386-2028-dirty (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages bind9 depends on: ii adduser 3.112+nmu2 add and remove users and groups ii bind9utils 1:9.7.3.dfsg-1~squeeze8 Utilities for BIND ii debconf [debconf 1.5.36.1Debian configuration management sy ii libbind9-60 1:9.7.3.dfsg-1~squeeze8 BIND9 Shared Library used by BIND ii libc62.11.3-4Embedded GNU C Library: Shared lib ii libcap2 1:2.19-3support for getting/setting POSIX. ii libdb4.8 4.8.30-2Berkeley v4.8 Database Libraries [ ii libdns69 1:9.7.3.dfsg-1~squeeze8 DNS Shared Library used by BIND ii libgssapi-krb5-2 1.8.3+dfsg-4squeeze6MIT Kerberos runtime libraries - k ii libisc62 1:9.7.3.dfsg-1~squeeze8 ISC Shared Library used by BIND ii libisccc60 1:9.7.3.dfsg-1~squeeze8 Command Channel Library used by BI ii libisccfg62 1:9.7.3.dfsg-1~squeeze8 Config File Handling Library used ii libldap-2.4-22.4.23-7.2 OpenLDAP libraries ii liblwres60 1:9.7.3.dfsg-1~squeeze8 Lightweight Resolver Library used ii libssl0.9.8 0.9.8o-4squeeze13 SSL shared libraries ii libxml2 2.7.8.dfsg-2+squeeze5 GNOME XML library ii lsb-base 3.2-23.2squeeze1Linux Standard Base 3.2 init scrip ii net-tools1.60-23 The NET-3 networking toolkit ii netbase 4.45Basic TCP/IP networking system bind9 recommends no packages. Versions of packages bind9 suggests: pn bind9-docnone (no description available) ii dnsutils 1:9.7.3.dfsg-1~squeeze8 Clients provided with BIND pn resolvconf none (no description available) pn ufw none (no description available) -- Configuration Files: /etc/bind/named.conf.local changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683289: libmono-webbrowser4.0-cil Recommends package non-existent libgluezilla package
Control: retitle -1 Doesn't work after dropping libgluezilla Control: severity -1 grave Control: clone -1 -2 Control: reassign -2 libmono-webbrowser2.0-cil On Mon, Jul 30, 2012 at 04:04:24PM +0100, Stuart Prescott wrote: The package libmono-webbrowser4.0-cil declares the following: Recommends: libgluezilla (= 2.6) however, this package was removed from wheezy almost a year ago and removed from sid six months ago. Packages in main must not recommend packages outside of main (policy §2.2.1) and non-existent packages are clearly not inside main. In fact, the main purpose of Mono.WebBrowser is using Gecko via libgluezilla, it's even in the description. And the webkit alternative is not packaged. #657290 suggests that the Mono maintainers know what to do after dropping libgluezilla so I won't suggest anything, but as nothing was done even for The broken reverse-recommends in mono are known and will be fixed. in the last 10 months, libmono-webbrowser2.0-cil and libmono-webbrowser4.0-cil must simply be dropped from the mono package for wheezy. -- WBR, wRAR signature.asc Description: Digital signature
Bug#689868: closed by Josselin Mouette j...@debian.org (Bug#689868: fixed in gnome-control-center 1:3.4.2+git20121016.29d7c0-1)
On 11/07/2012 08:21 PM, Debian Bug Tracking System wrote: Hi! This is an automatic notification regarding your Bug report which was filed against the gnome-control-center package: #689868: gnome-control-center: wacom button assignments broken It has been closed by Josselin Mouettej...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Josselin Mouettej...@debian.org by replying to this email. The above bug was closed as you mentioned all issues where resolved in the most recent version of gnome control centre. However, I fear it is my sad duty to inform you that at least as the current version in Wheezy goes all issues still persist. I have to unplug my graphics tablet to get the keyboard assinments working as soon as I changed or just opend them in the wacom control panel. Additionally, it still seems not possible to assign modifiers like Shift/Ctrl/Alt (without another key) or e.g. the mouse wheel. -- Kind regards,/ War is Peace. |Freedom is Slavery. Alexander Wagner| Ignorance is Strength. | | Theory : G. Orwell, 1984 / In practice: USA, since 2001 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694722: eMachines eM355, encrypted boots off pendrive, preseeding fails
Hello Brian,
thanks for responding.
On 2012-Nov-30 18:54 (+), Brian Potkin wrote with possible deletions:
[gunzip boot.img.gz /dev/sdb = failed]
This works for me.
[gunzip boot.img.gz /dev/sdb1 = GRUB error]
This would not work because the MBR is not written to. There is nothing
in it to say how to boot.
I think you may have your comments on the two techniques the wrong way
round. Also, it is SYSLINUX which does the booting, not GRUB. Did you
really get a screen with GRUB displayed at the top?
Ok, I'm retrying this right now:
# gunzip boot.img.gz /dev/sdb
# mount /dev/sdb /media/sdb
# cp debian-wheezy-DI-b4-amd64-netinst.iso /media/sdb
# umount /media/sdb
When I plug the pendrive into the target machine, it hangs. No
boot-menu, just a blinking cursor. Now let me retry the other version:
# dd if=/dev/zero of=/dev/sdb
# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF
disklabel
Building a new DOS disklabel with disk identifier 0x1b9f17d2.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x of partition table 4 will be corrected by
w(rite)
Command (m for help): p
Disk /dev/sdb: 4025 MB, 4025810432 bytes
124 heads, 62 sectors/track, 1022 cylinders, total 7862911 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1b9f17d2
Device Boot Start End Blocks Id System
Command (m for help): n
Partition type:
p primary (0 primary, 0 extended, 4 free)
e extended
Select (default p): p
Partition number (1-4, default 1):
Using default value 1
First sector (2048-7862910, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-7862910, default 7862910):
Using default value 7862910
Command (m for help): p
Disk /dev/sdb: 4025 MB, 4025810432 bytes
124 heads, 62 sectors/track, 1022 cylinders, total 7862911 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1b9f17d2
Device Boot Start End Blocks Id System
/dev/sdb12048 7862910 3930431+ 83 Linux
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
# gunzip boot.img.gz /dev/sdb1
# mount /dev/sdb1 /media/sdb1
# cp debian-wheezy-DI-b4-amd64-netinst.iso /media/sdb1
# umount /media/sdb1
Ok, pendrive goes to target machine again. Nothing happens this time,
just a blinking cursor in the top left corner, just as above. No boot
menu, no GRUB. So you were right:
This would not work because the MBR is not written to. There is nothing
in it to say how to boot.
It is hard for me now to figure out what happened last time, when I've
seen the GRUB error message. I'm sure it was GRUB, because I ended up
in it's rescue mode. Would it be possible that a GRUB survived
somewhere else on the target machine's harddisk from a previous install,
and the BIOS fell back to launch that one, since nothing was found on
the pendrive's MBR? Anyways, since I cannot reproduce it, it's not a
bug.
So I try the preseeding as you told me, using a new partition on the
pendrive I've set up with
# dd if=debian-wheezy-DI-b4-amd64-netinst.iso of=/dev/sdb
Pretty awesome! The installer seems to ignore the ESSID I've set
for wifi, but that's the only issue I can put my finger on. I'm pretty
happy.
Is there a definitive documentation of the syntax, semantics, and
possible values I can put in my `preseed.cfg`?
Thank you!
Stefan
--
Stefan Klinger o/klettern
/\/ bis zum
send plaintext only - max size 32kB - no spam \ Abfallen
http://stefan-klinger.de
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694864: [Pkg-fonts-devel] Bug#694864: Bug#694864: Bug#694864: Bug#694864: Bug#694864: ttf-liberation not available for ARCH i386 in multiarch amd64 environment
On 12/02/2012 06:14 AM, Christian PERRIER wrote: Quoting Vasudev Kamath (kamathvasu...@gmail.com): Preparing all packages with Multi-Arch: foreign will be difficult at this point I guess, considering amount of packages maintained by pkg-fonts. [1] Are we planning this for Wheezy itself? I don't see any reason for this to be needed for wheezy. So, we should do this for jessie. yes, agreed that this work should target jessie, not wheezy. I took a peek at the lintian sources and am a bit overwhelmed -- but anyone who wants to try writing a test might do well to start reading at: https://wiki.debian.org/Teams/Lintian/HackersGuide and/or get in touch with the lintian team at: https://wiki.debian.org/Teams/Lintian Regards, --dkg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694895: education-tasks: Installs tasksel desc file in obsolete location
Here is a possible workaround while we wait for a fix for #694896 in blends-dev. I've asked Andreas Tille to look into #694896 and consider it for inclusion in Wheezy. Index: debian/rules === --- debian/rules(revisjon 78474) +++ debian/rules(arbeidskopi) @@ -1,3 +1,8 @@ #!/usr/bin/make -f include /usr/share/blends-dev/rules + +# Workaround for bug #694896 in blends-dev 0.6.15 and later versions +override_dh_install: + $(BLEND_INSTALL_HELPER) + dh_install $(BLENDNAME)-tasks.desc usr/share/tasksel/descs -- vennlig hilsen Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694951: bison: FTBFS with eglibc 2.16: Needs gnulib update
Source: bison Version: 2:2.5.dfsg-3 Severity: normal Tags: patch User: debian-...@lists.debian.org Usertags: port-x32 ftbfs-gnulib If I try to build the current package with eglibc 2.16 from experimental installed, I get this build failure: gcc -std=gnu99 -I. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector -- param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o fseterr.o fseterr.c In file included from fseterr.h:20:0, from fseterr.c:20: ./stdio.h:496:1: error: 'gets' undeclared here (not in a function) make[5]: *** [fseterr.o] Error 1 make[5]: Leaving directory `/tmp/buildd/bison-2.5.dfsg/lib' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/tmp/buildd/bison-2.5.dfsg/lib' make[3]: *** [all] Error 2 make[3]: Leaving directory `/tmp/buildd/bison-2.5.dfsg/lib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/bison-2.5.dfsg' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/bison-2.5.dfsg' make: *** [debian/stamp-makefile-build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Attached is a debdiff of the changes I made to get it to compile again. Alternately, the 1:2.6.2.dfsg-1 version which was briefly in the archive built fine against eglibc 2.16. -- Daniel Schepler diff -Nru bison-2.5.dfsg/debian/changelog bison-2.5.dfsg/debian/changelog --- bison-2.5.dfsg/debian/changelog 2012-11-01 11:04:49.0 -0700 +++ bison-2.5.dfsg/debian/changelog 2012-11-21 11:30:31.0 -0800 @@ -1,3 +1,10 @@ +bison (2:2.5.dfsg-3+x32) UNRELEASED; urgency=low + + * Fix gnulib's stdio.in.h to compile against eglibc 2.16, which no longer +declares gets() by default. + + -- Daniel Schepler schep...@debian.org Wed, 21 Nov 2012 11:29:58 -0800 + bison (2:2.5.dfsg-3) unstable; urgency=low * Bump epoch to downgrade unstable version from 2.6.2.dfsg-1 back to diff -Nru bison-2.5.dfsg/debian/patches/01_gnulib_eglibc2_16.diff bison-2.5.dfsg/debian/patches/01_gnulib_eglibc2_16.diff --- bison-2.5.dfsg/debian/patches/01_gnulib_eglibc2_16.diff 1969-12-31 16:00:00.0 -0800 +++ bison-2.5.dfsg/debian/patches/01_gnulib_eglibc2_16.diff 2012-11-21 11:29:19.0 -0800 @@ -0,0 +1,14 @@ +Index: bison-2.5.dfsg/lib/stdio.in.h +=== +--- bison-2.5.dfsg.orig/lib/stdio.in.h 2011-05-14 22:23:46.0 + bison-2.5.dfsg/lib/stdio.in.h 2012-11-21 19:29:15.0 + +@@ -181,7 +181,9 @@ +so any use of gets warrants an unconditional warning. Assume it is +always declared, since it is required by C89. */ + #undef gets ++#if 0 + _GL_WARN_ON_USE (gets, gets is a security hole - use fgets instead); ++#endif + + #if @GNULIB_FOPEN@ + # if @REPLACE_FOPEN@ diff -Nru bison-2.5.dfsg/debian/patches/series bison-2.5.dfsg/debian/patches/series --- bison-2.5.dfsg/debian/patches/series 1969-12-31 16:00:00.0 -0800 +++ bison-2.5.dfsg/debian/patches/series 2012-11-21 11:28:52.0 -0800 @@ -0,0 +1 @@ +01_gnulib_eglibc2_16.diff
Bug#694952: m4: FTBFS with eglibc 2.16: Needs gnulib update
Source: m4 Version: 1.4.16-4 Severity: normal Tags: patch User: debian-...@lists.debian.org Usertags: port-x32 ftbfs-gnulib If I try building m4 with eglibc 2.16 from experimental installed, I get this build failure: # source='clean-temp.c' object='clean-temp.o' libtool=no gcc -std=gnu99 -I. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector -- param=ssp-buffer-size=4 -c clean-temp.c In file included from clean-temp.h:22:0, from clean-temp.c:23: ./stdio.h:477:1: error: 'gets' undeclared here (not in a function) make[4]: *** [clean-temp.o] Error 1 make[4]: Leaving directory `/tmp/buildd/m4-1.4.16/lib' make[3]: *** [all] Error 2 make[3]: Leaving directory `/tmp/buildd/m4-1.4.16/lib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/m4-1.4.16' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/m4-1.4.16' dh_auto_build: make -j1 returned exit code 2 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Attached is a debdiff with a temporary workaround until the package is updated from gnulib git. -- Daniel Schepler diff -Nru m4-1.4.16/debian/changelog m4-1.4.16/debian/changelog --- m4-1.4.16/debian/changelog 2012-05-07 07:11:49.0 -0700 +++ m4-1.4.16/debian/changelog 2012-07-20 14:52:38.0 -0700 @@ -1,3 +1,10 @@ +m4 (1.4.16-3+x32) UNRELEASED; urgency=low + + * Added fix for gnulib compilation against glibc 2.16, which no longer +declares gets by default. + + -- Daniel Schepler schep...@debian.org Fri, 20 Jul 2012 14:52:27 -0700 + m4 (1.4.16-3) unstable; urgency=low * Switch to dh. diff -Nru m4-1.4.16/debian/patches/04-fix-for-gnulib-compilation-error-with-glibc-2_16 m4-1.4.16/debian/patches/04-fix-for-gnulib-compilation-error-with-glibc-2_16 --- m4-1.4.16/debian/patches/04-fix-for-gnulib-compilation-error-with-glibc-2_16 1969-12-31 16:00:00.0 -0800 +++ m4-1.4.16/debian/patches/04-fix-for-gnulib-compilation-error-with-glibc-2_16 2012-07-20 14:52:49.0 -0700 @@ -0,0 +1,14 @@ +Index: m4-1.4.16/lib/stdio.in.h +=== +--- m4-1.4.16.orig/lib/stdio.in.h 2011-03-01 16:39:29.0 + m4-1.4.16/lib/stdio.in.h 2012-07-20 21:51:00.0 + +@@ -162,7 +162,9 @@ +so any use of gets warrants an unconditional warning. Assume it is +always declared, since it is required by C89. */ + #undef gets ++#if 0 + _GL_WARN_ON_USE (gets, gets is a security hole - use fgets instead); ++#endif + + #if @GNULIB_FOPEN@ + # if @REPLACE_FOPEN@ diff -Nru m4-1.4.16/debian/patches/series m4-1.4.16/debian/patches/series --- m4-1.4.16/debian/patches/series 2011-07-26 09:32:24.0 -0700 +++ m4-1.4.16/debian/patches/series 2012-07-20 14:50:41.0 -0700 @@ -1,3 +1,4 @@ 01-no-usr-share-info-dir-gz 02-workaround-for-binutils-bug-on-mips 03-fix-for-test-readlink +04-fix-for-gnulib-compilation-error-with-glibc-2_16
Bug#694954: ps.1: Is t for stopped because it is being traced?
Package: procps Version: 1:3.3.3-2 Severity: normal Tags: patch File: /usr/share/man/man1/ps.1.gz Based on http://www.mail-archive.com/linux-il@cs.huji.ac.il/msg63550.html and http://www.mail-archive.com/linux-il@cs.huji.ac.il/msg63551.html --- ps.1.orig 2012-12-02 18:34:57.598046061 +0200 +++ ps.1.new2012-12-02 18:31:10.0 +0200 @@ -838,8 +838,11 @@ running or runnable (on run queue) S interruptible sleep (waiting for an event to complete) .TP +t +stopped because it is being traced +.TP T -stopped, either by a job control signal or because it is being traced +stopped by a job control signal .TP W paging (not valid since the 2.6.xx kernel) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692361: ACPI display backlight brightness is set to zero at every boot-up (HP Folio 13-2000)
Am Montag, den 05.11.2012, 12:45 +0100 schrieb Stefan Nagy:
Since I didn't encounter this problem before
linux-image-3.6-trunk-amd64 I had a look at these settings on
linux-image-3.2.0-4-amd64 with normal backlight brightness:
'acpi_video0' (brightness 0, actual_brightness 0),
'intel_backlight' (brightness 4882, actual_brightness 4882). So the
difference between 3.2 and 3.6 seems to be that backlight brightness
wasn't controlled by the ACPI driver but the device specific driver in
3.2.
I was having the same problem with linux-image-3.2.0-4-amd64 for some
time now, I guess since update 3.2.32-1.
However, this bug was fixed upstream. I tested the patch on top of
kernel v3.2.32-1 and it fixes the problem.
From 117af51d695c78bfdf618a183664f0e9f3769b9a Mon Sep 17 00:00:00 2001
From: Zhang Rui rui.zh...@intel.com
Date: Sun, 2 Dec 2012 10:00:41 +0800
Subject: [PATCH] ACPI video: ignore BIOS initial backlight value for HP Folio
13-2000.
Or else the laptop will boot with a dimmed screen.
Signed-off-by: Zhang Rui rui.zh...@intel.com
---
drivers/acpi/video.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
index 1e0a9e1..58bddd3 100644
--- a/drivers/acpi/video.c
+++ b/drivers/acpi/video.c
@@ -389,6 +389,12 @@ static int __init video_set_bqc_offset(const struct dmi_system_id *d)
return 0;
}
+static int video_ignore_initial_backlight(const struct dmi_system_id *d)
+{
+ use_bios_initial_backlight = 0;
+ return 0;
+}
+
static struct dmi_system_id video_dmi_table[] __initdata = {
/*
* Broken _BQC workaround http://bugzilla.kernel.org/show_bug.cgi?id=13121
@@ -433,6 +439,14 @@ static struct dmi_system_id video_dmi_table[] __initdata = {
DMI_MATCH(DMI_PRODUCT_NAME, Aspire 7720),
},
},
+ {
+ .callback = video_ignore_initial_backlight,
+ .ident = HP Folio 13-2000,
+ .matches = {
+ DMI_MATCH(DMI_BOARD_VENDOR, Hewlett-Packard),
+ DMI_MATCH(DMI_PRODUCT_NAME, HP Folio 13 - 2000 Notebook PC),
+ },
+ },
{}
};
--
1.7.9.5
Bug#694864: [Pkg-fonts-devel] Bug#694864: Bug#694864: Bug#694864: Bug#694864: Bug#694864: Bug#694864: ttf-liberation not available for ARCH i386 in multiarch amd64 environment
On 11:12 Sun 02 Dec , Daniel Kahn Gillmor wrote:
On 12/02/2012 06:14 AM, Christian PERRIER wrote:
Quoting Vasudev Kamath (kamathvasu...@gmail.com):
Preparing all packages with Multi-Arch: foreign will be difficult at
this point I guess, considering amount of packages maintained by
pkg-fonts. [1]
Are we planning this for Wheezy itself?
I don't see any reason for this to be needed for wheezy. So, we should
do this for jessie.
yes, agreed that this work should target jessie, not wheezy.
I took a peek at the lintian sources and am a bit overwhelmed -- but
anyone who wants to try writing a test might do well to start reading at:
https://wiki.debian.org/Teams/Lintian/HackersGuide
Let me try getting this done the hard way, thanks for the link
and/or get in touch with the lintian team at:
https://wiki.debian.org/Teams/Lintian
In case I won't be able to get above done then I will contact the team
:-)
--
Vasudev Kamath
http://copyninja.info
Connect on ~friendica: copyninja@{frndk.de | vasudev.homelinux.net}
IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net}
GPG Key: C517 C25D E408 759D 98A4 C96B 6C8F 74AE 8770 0B7E
signature.asc
Description: Digital signature
Bug#694955: git-import-orig: support workflow with upstreams history on upstream branch
Package: git-buildpackage Version: 0.6.0~git20121124 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I like to fork my git packaging repo from upstream and merge upstreams history in my upstream branch from time to time. When upstream makes a release, they hopefully tag the git commit from which their release was made or I need to identify it manually. Then there are three cases: a) Upstreams release tarball has identical content to one git commit. (Maybe it was even created via git-archive.) b) Upstreams release tarball has slightly other content then any git commit. c) Upstreams release tarball has a totally different structure then any git commit. In case a) I can just create a signed git tag upstream/$VERSION and pristine-tar commit the tarball. In case b) I'd create a new commit containing the tarballs content with the release commit as its parent, tag it and merge it into master. In case c) I'm doomed. It would be nice, if git-import-orig would support this workflow somehow. Regards, Thomas Koch -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQu4TsAAoJEAf8SJEEK6Za9ekQANP4Wf6qbQXKoQ6Eq1Ip2Ojs 8uK72/WyuPqs/7dc/RgTDFqiO5RXEEE8u238vsQjiu4hRtaTJEVDj4CVly7fyZml xGQ7EYrMGBLaVirhs8LAJAVtQBa/jEmZRAR8pRqaHWLbIFxeWQePk17erQiSlgTW 3/aCBLySOUW7ykITVqJ9J+7YSYAOyBGXstyGX5FM13sQwcCTCDG6CKY7/C6saiV0 6nxiEK1XyitJ0ffOmJEOh1WD0tWTCHsFCBSeq5Xo9N/SBIBxWtxWSaUtB4o12CC8 gOBKplne36Kb6srm2G1IYB+sIpNTfkMd1cOL7ZJ7xJHDcUrY4IrqtZltByTdEtVT 903FehdlowNdWtUuY/iFXt6B3RHA5DxA64eGmCb+hTP6Bg6DhFX+scQUQYFA7NoI dDUr9iLX0jwmwmk1WOGSBilrHzkwkblYnJUqgR5liNN9fq7s3pjdgHOtVzNcE0Ni SlU9SvR0Z+tDeRLSzRcMXmoQCjgURQpeiVvAykDcF/9/8ACXayJ7PBvtXIgaA45l aMub/A9bQLVT4NIGQaK9iJcX6WyStgfoStGR2fkzsD7Q2zcaVJpF08QnwoHU52ct nElUhAgtJsMkT8X1J+aJMSrejrT/fV5se6WXq8jP3NehLl9+pYqJYYpoG9HDAYsS gCG3+3F1m4ReFbo62u+b =GZD3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694956: sharutils: FTBFS with eglibc 2.16: Needs gnulib update
Source: sharutils Version: 1:4.11.1-1 Severity: normal Tags: patch User: debian-...@lists.debian.org Usertags: port-x32 ftbfs-gnulib When I try building sharutils with eglibc 2.16 from experimental installed, I get this build failure: gcc -DHAVE_CONFIG_H -I. -I.. -I../intl -D_FORTIFY_SOURCE=2 -g -O2 -fstack- protector --param=ssp-buffer-size=4 -c localcharset.c In file included from localcharset.c:28:0: ./stdio.h:494:1: error: 'gets' undeclared here (not in a function) make[5]: *** [localcharset.o] Error 1 make[5]: Leaving directory `/tmp/buildd/sharutils-4.11.1/lib' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/tmp/buildd/sharutils-4.11.1/lib' make[3]: *** [all] Error 2 make[3]: Leaving directory `/tmp/buildd/sharutils-4.11.1/lib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/sharutils-4.11.1' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/sharutils-4.11.1' dh_auto_build: make -j1 returned exit code 2 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Attached is a debdiff with a temporary workaround until the package is updated from gnulib git. -- Daniel Schepler diff -Nru sharutils-4.11.1/debian/changelog sharutils-4.11.1/debian/changelog --- sharutils-4.11.1/debian/changelog 2012-06-02 10:24:07.0 -0700 +++ sharutils-4.11.1/debian/changelog 2012-07-20 16:16:18.0 -0700 @@ -1,3 +1,10 @@ +sharutils (1:4.11.1-1+x32) UNRELEASED; urgency=low + + * Add fix for gnulib compilation against glibc 2.16, which no longer +declares gets by default. + + -- Daniel Schepler schep...@debian.org Fri, 20 Jul 2012 16:15:53 -0700 + sharutils (1:4.11.1-1) unstable; urgency=low * New upstream release. diff -Nru sharutils-4.11.1/debian/patches/99-gnulib-glibc-2_16 sharutils-4.11.1/debian/patches/99-gnulib-glibc-2_16 --- sharutils-4.11.1/debian/patches/99-gnulib-glibc-2_16 1969-12-31 16:00:00.0 -0800 +++ sharutils-4.11.1/debian/patches/99-gnulib-glibc-2_16 2012-07-20 16:14:51.0 -0700 @@ -0,0 +1,14 @@ +Index: sharutils-4.11.1/lib/stdio.in.h +=== +--- sharutils-4.11.1.orig/lib/stdio.in.h 2011-04-29 16:49:42.0 + sharutils-4.11.1/lib/stdio.in.h 2012-07-20 23:14:08.0 + +@@ -179,7 +179,9 @@ +so any use of gets warrants an unconditional warning. Assume it is +always declared, since it is required by C89. */ + #undef gets ++#if 0 + _GL_WARN_ON_USE (gets, gets is a security hole - use fgets instead); ++#endif + + #if @GNULIB_FOPEN@ + # if @REPLACE_FOPEN@ diff -Nru sharutils-4.11.1/debian/patches/series sharutils-4.11.1/debian/patches/series --- sharutils-4.11.1/debian/patches/series 2012-06-02 10:10:19.0 -0700 +++ sharutils-4.11.1/debian/patches/series 2012-07-20 16:13:46.0 -0700 @@ -1,2 +1,3 @@ 01-no-usr-share-info-dir-gz 99-config-guess-config-sub +99-gnulib-glibc-2_16
Bug#692361: ACPI display backlight brightness is set to zero at every boot-up (HP Folio 13-2000)
Am Montag, den 05.11.2012, 12:45 +0100 schrieb Stefan Nagy:
Since I didn't encounter this problem before
linux-image-3.6-trunk-amd64 I had a look at these settings on
linux-image-3.2.0-4-amd64 with normal backlight brightness:
'acpi_video0' (brightness 0, actual_brightness 0),
'intel_backlight' (brightness 4882, actual_brightness 4882). So the
difference between 3.2 and 3.6 seems to be that backlight brightness
wasn't controlled by the ACPI driver but the device specific driver in
3.2.
I was having the same problem with linux-image-3.2.0-4-amd64 for some
time now, I guess since update 3.2.32-1.
However, this bug was fixed upstream. I tested the patch on top of
kernel v3.2.32-1 and it fixes the problem.
From 117af51d695c78bfdf618a183664f0e9f3769b9a Mon Sep 17 00:00:00 2001
From: Zhang Rui rui.zh...@intel.com
Date: Sun, 2 Dec 2012 10:00:41 +0800
Subject: [PATCH] ACPI video: ignore BIOS initial backlight value for HP Folio
13-2000.
Or else the laptop will boot with a dimmed screen.
Signed-off-by: Zhang Rui rui.zh...@intel.com
---
drivers/acpi/video.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
index 1e0a9e1..58bddd3 100644
--- a/drivers/acpi/video.c
+++ b/drivers/acpi/video.c
@@ -389,6 +389,12 @@ static int __init video_set_bqc_offset(const struct dmi_system_id *d)
return 0;
}
+static int video_ignore_initial_backlight(const struct dmi_system_id *d)
+{
+ use_bios_initial_backlight = 0;
+ return 0;
+}
+
static struct dmi_system_id video_dmi_table[] __initdata = {
/*
* Broken _BQC workaround http://bugzilla.kernel.org/show_bug.cgi?id=13121
@@ -433,6 +439,14 @@ static struct dmi_system_id video_dmi_table[] __initdata = {
DMI_MATCH(DMI_PRODUCT_NAME, Aspire 7720),
},
},
+ {
+ .callback = video_ignore_initial_backlight,
+ .ident = HP Folio 13-2000,
+ .matches = {
+ DMI_MATCH(DMI_BOARD_VENDOR, Hewlett-Packard),
+ DMI_MATCH(DMI_PRODUCT_NAME, HP Folio 13 - 2000 Notebook PC),
+ },
+ },
{}
};
--
1.7.9.5
Bug#585610: icedove: Printing ALWAYS prints to Letter, A4 cannot be selected anywhere, even though printer has ONLY A4
Hello Andreas, did try to change this settings? print.postscript.paper_size print.tmp.printerfeatures.PDF.can_change_paper_size print.tmp.printerfeatures.PDF.supports_paper_size_change I can change the papersize even in the settings for a real printer and also for the PDF printer as well on icedove 10.0.11. And printing too. On Sat, Jun 12, 2010 at 12:31:32PM +0200, Andreas Neudecker wrote: It is impossible to print to A4 in Icedove. Default setting is Letter even though the physical printer has only A4 configured and loaded. Even with the virtual CUPS PDF printer it is not possible to select any other page size because the respective entry is disabled and shows Letter as preset (File-Print-Page Setup). Actually, all entries on that page except duplex, pages per sheet and scaling are disabled for any printer, real or virtual. This is very annoying and makes printing in icedove unusable for anyone who does not by default use letter format, i.e. innumerable users in many countries other than the US. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687442: linux-image-3.2.0-3-686-pae: Add Intel Ivy Bridge support
On Mon, 2012-11-26 at 22:28 +0100, Julien Cristau wrote: New image is up at http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.34-1~jcristau.1_amd64.deb sha1sum is 1bbb6e4590e4f000739af89f3090ffc6bb9cb409. diff against svn at http://people.debian.org/~jcristau/3.2.34-1~jcristau.1.diff Tested with: 1. Thinkpad T61, GM965 (i915 gen4), LVDS display, sid userland GNOME Shell, Google Earth, Extreme Tux Racer all seem to work 2. White box, Core i5 2500 (SNB, i915 gen6), VGA display, squeeze userland It looks like gdm crashed the first time I tried to log in, but it worked the second time. There was nothing obvious in kernel or X server log. squeeze doesn't haven't DRM support for this chip, so no 3D tests. I have a couple of older machines with Radeon graphics, but will need to build an i386 package first. I may also re-test on system 2 with wheezy userland. Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part
Bug#694949: xserver-xorg-video-nouveau: server 'dies' on resume with different symptoms
On 2012-12-02 17:08 +0100, Stefan Schwarzer wrote: Package: xserver-xorg-video-nouveau Version: 1:1.0.1-4 Severity: normal Dear Maintainer, using a Dell laptop (E 6410) with Nvidia graphics I follow more or less testing. Suspend/resume worked up to an upgrade last week with only minor glitches. That upgrade installed version 1.0.1-4 of the nouveau server causing suspend/resume to fail in about 80% of the cycles with differing symptoms on each resume: (i) screen with backlight on but black, only moving cursor visible (ii) black screen, no backlight, possibly after a short flicker and initially showing the last screen content before suspend (iii) system bell going crazy without user input I checked the server log (Xorg.0.old) and the kernel logs (/var/log/messages) but there was nothing visible that permitted pinpointing the problem The only one of these cherry-picks that should have *any* effect with your configuration is exa: use CLAMP_TO_EDGE for RepeatPad, the others only affect code paths which are not entered in default setups. I cannot really imagine how this commit could lead to problems on suspend/resume, but could you please try and revert it? However, suspend/resume started working again after an upgrade of the package to the version in experimental (1.0.4-1), which I am running now. So, one of the 'cherries' introduced from 1.0.1-3 to ..-4 may carry what ruins my day. There's also the possibility that AIGLX is the problem (using the experimental xserver-xorg-video-nouveau package with unstable's libgl1-mesa-dri triggers AIGLX errors, as can be seen in your logs). Can you please turn off AIGLX in the SERVERFLAGS section of xorg.conf and test whether that helps in 1.0.1-4 ? Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694872: Why was this bug closed?
On Sun, Dec 02, 2012 at 12:59:44PM +0100, Ivo De Decker wrote: On Sun, Dec 02, 2012 at 11:45:08AM +, Debian Bug Tracking System wrote: Date: Sun, 02 Dec 2012 04:20:40 + From: Bart Martens ba...@quantz.debian.org To: 694872-d...@bugs.debian.org Subject: closing RFS: lftp/4.3.8-1.1 [NMU] [RC] Package lftp has been removed from mentors. lftp hasn't been uploaded or removed, so this bug shouldn't be closed. It might be a problem is some script, because mentors has 2 versions of lftp: a version for sid, and a version for testing-proposed-updates. I agree that closing this RFS with has been removed from mentors was an error in my script. Thanks for telling me this and for reopening this RFS. However, are you sure that a package for t-p-u should have a version like 4.3.8-1.1 ? Shouldn't it be a version with +deb70u1 or some variant of that for an NMU ? Regards, Bart Martens -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694957: referencer: New upstream version 1.2.0 available
Package: referencer Version: 1.1.6-2 Severity: wishlist https://launchpad.net/referencer/1./1.2.0/+download/referencer-1.2.0.tar.gz -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages referencer depends on: ii libboost-regex1.42.0 1.42.0-4 regular expression library for C++ ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libgconfmm-2.6-1c22.28.0-1 C++ wrappers for GConf (shared lib ii libglademm-2.4-1c2a 2.6.7-2C++ wrappers for libglade2 (shared ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libglibmm-2.4-1c2a2.24.2-1 C++ wrapper for the GLib toolkit ( ii libgnome-vfsmm-2.6-1c2a 2.26.0-1 C++ wrappers for GnomeVFS (shared ii libgnomemm-2.6-1c22.30.0-1 C++ wrappers for libgnome (shared ii libgnomeuimm-2.6-1c2a 2.28.0-1 C++ wrappers for libgnomeui (share ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface ii libgtkmm-2.4-1c2a 1:2.20.3-1 C++ wrappers for GTK+ (shared libr ii libpangomm-1.4-1 2.26.2-1 C++ Wrapper for pango (shared libr ii libpoppler-glib4 0.12.4-1.2 PDF rendering library (GLib-based ii libpython2.6 2.6.6-8+b1 Shared Python runtime library (ver ii libsigc++-2.0-0c2a2.2.4.2-1 type-safe Signal Framework for C++ ii libstdc++64.6.0-2The GNU Standard C++ Library v3 referencer recommends no packages. referencer suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694923: better / alternative image distribution
On Sun, Dec 02, 2012 at 12:29:10PM +0100, Marco d'Itri wrote: On Dec 02, Stefano Zacchiroli z...@debian.org wrote: That would allow mirroring, would reduce worries of being shaped down by specific cloud providers if we exceed some Is this actually a real concern? As a cloud provider, I find hard to believe that one would damage their customers this way. I also don't see much of that scenario. Either for private clouds, what an AMI really offer is a software component that will be used on your platform and people will rely on. You, as provider, don't want to loose credibility. traffic thresholds and, generally, benefit our independence from specific providers. Next action on this: contact debian-cd, point them to some of the images we already have (only EC2 at the moment) and ask their take about including them in the usual CD/media mirror network. Are the EC2 images also usable as is on other Amazon-like cloud infrastructures? If they are not, then I do not see the point of using our own resources for the benefit of a specific cloud provider. EC2 AMIs can be converted[1] to EMIs (Eucalyptus). This also has to do with the fact that Eucalyptus is API-compatible with Amazon EC2. 1- https://github.com/eucalyptus/eucalyptus/wiki/Convert-AMI-to-EMI -- Rudy Godoy http://stone-head.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673606: 7.2
retitle 673606 netbeans: new version available (7.2.1) thanks Hello Bart, any plans to package a current version of netbeans? The version 7.0.1 is from the august 2011, a new version would really be welcome while the version in wheezy isn't able to use a project directory from the current stable version. Thanks Carsten On Wed, Aug 01, 2012 at 11:44:53AM +0200, Bart Verwilst wrote: In the meantime Netbeans 7.2 is the latest version available. Having an up to date package would be awesome! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694093: RM: bcrypt/1.1-6
Package: bcrypt Version: 1.1-8 Previously a request was submitted to have bcrypt removed from testing (#694093). Work has since been completed by DD Michael Stapelberg to address the two RC bugs that were the motivation behind removal. I would therefore request that the bcrypt package be included in testing again by accepting recently uploaded version 1.1-8. Only minimal changes were made to the package to explicitly address the RC bug issues. Thanks, Kevin RC Bugs addressed in the patch found in version 1.1-8: * bugs.debian.org/693460 Can't handle files larger than 4GB, causes data loss if used with default parameters. * bugs.debian.org/694091 Loads the whole file into memory, causes processes deaths when trying to allocate more memory than the machine has. -- Kevin Coyner GnuPG key: 2048R/C85D8F71 http://rustybear.com/publickey.html
Bug#694872: Why was this bug closed?
On Sun, 02 Dec 2012 17:08:24 +, Bart Martens wrote: lftp hasn't been uploaded or removed, so this bug shouldn't be closed. It might be a problem is some script, because mentors has 2 versions of lftp: a version for sid, and a version for testing-proposed-updates. However, are you sure that a package for t-p-u should have a version like 4.3.8-1.1 ? Shouldn't it be a version with +deb70u1 or some variant of that for an NMU ? 4.3.8-1.1 is the version for the unstable NMU; the version for TPU is 4.3.6-1.1, according to http://mentors.debian.net/package/lftp. (And yes, this should probably be 4.3.6-1+deb7u1 or similar). Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Wir sind Helden: Der Krieg kommt schneller zurück als du denkst signature.asc Description: Digital signature
Bug#692518: (no subject)
You guys may have resolved it to your satisfaction, but I've still got the bug. I'm running Wheezy and it is fully upgraded. I open nautilus to $HOME/Documents (for example) and the terminal opens to $HOME. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694958: ACE_OS missing functions on hurd
Package: libace-dev Version: 6.0.3-5 Control: affects libdiagnostics-dev diagnostics FTBFS on hurd (only), because ACE_OS lacks, e.g., getpid. See https://buildd.debian.org/status/fetch.php?pkg=diagnosticsarch=hurd-i386ver=0.3.3-2stamp=1354462516 for the full build log. Best, Michael pgpWscmHlm5cc.pgp Description: PGP signature
Bug#694934: Installer hangs at detect network hardware
On 02/12/12 15:30, Brian Potkin wrote: On Sun 02 Dec 2012 at 12:22:50 +, R.M. Thomas wrote: Comments/Problems: I chose: Advanced options Alternative desktop environments Xfce Advanced options Expert install and answered questions about language, keyboard, locale (default), modules to load (default), extra installer components (none). At the next stage Detect network hardware the installation stalled indefinitely (more than ten minutes) with a blue screen having a single white line at the bottom and a black cursor. Keyboard input was echoed to this bottom line, but I was unable to get any other response from the system and was obliged to use the machine's power on/off switch. Ctrl-C should get you back to the main menu. I did thump some random keys, but probably didn't try Ctrl-C. Thanks for the tip, I'll remember that for next time. Please look at #694582 and see if it helps. In my case, the stall at Detect network hardware may not to be a firmware issue. After I had set up the configuration files /etc/network/interfaces and /etc/resolv.conf the commands ifdown and ifup successfully controlled the eth0 port with no need for me to install manually any packages (drivers or firmware). I did need the package firmware-linux-nonfree in order to get the video card working, but I assume that was a unrelated problem. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694942: dspam: incompatible with wheezy's postgresql version
Hi Thomas, Thomas Preud'homme (robo...@debian.org on 2012-12-02 16:37 +0100): Le dimanche 2 décembre 2012 15:53:13, vous avez écrit : [..] ERROR: invalid byte sequence for encoding UTF8: 0xae: INSERT INTO dspam_signature_data [..] - unblock 3.10.2 because it is said to have a fix for this issue (not verified, I don't want to start mixing releases even before wheezy is released) - backport the 3.10.2 fix to wheezy's 3.10.1 Both of these solution are not possible since the bug is only severity normal. It might be OK for the release team to unblock a package with the workaround backported if the bug was severity important but I don't think this bug is important. Dspam only fails to *retrain* (not filter) of *some* mails. Ah, that's unfortunate but understandable, I guess. However *some* mails means 90% of my volume (it only succesfully recorded 71 signatures from nearly 800 e-mails). However I've taken a look at the upstream patch that fixes the issue, and agree that it's non-trivial to backport (even if this was RC) as it does way more than just fix string quoting for PostgreSQL 9.1: http://dspam.git.sourceforge.net/git/gitweb.cgi?p=dspam/dspam;a=commit;h=9bc231ae79f84a973ced531356833142c4ae2766 - document this incompatibility+workaround in the release notes I'll think about this one. Is the bug related to the new version of dspam? Were you using dspam with PostgreSQL before without this problem? I've been using the same dspam version with PostgresQL 8.4 before and didn't have this issue. However, that database also had a default encoding of SQL_ASCII, and the new server uses UTF-8 as encoding, so it's not exactly comparing apples and apples. I did a little more digging, and came out here: http://postgresql.1045698.n5.nabble.com/PQescapeByteaConn-returns-wrong-string-for-PG9-1-Beta3-tp4667713p4668043.html which basically amounts to dspam's usage of escaped strings only works in postgres' legacy mode, but PostgreSQL 9.1 is in standards-compliant mode by default. In addition, we can provide backports for wheezy once it's released. I guess that would be an acceptable solution, yes. Thanks for the quick response, Arno -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694959: azureus/vuze: New upstream version: 4.8.0.0 - azureus/vuze is over 3 years out of date
Package: azureus Version: 4.3.0.6-1.1 Severity: important Tags: squeeze sid azureus/vuze need an urgent update. Is 3 years out of date. This is a bittorrent client mentioned in http://www.debian.org/CD/torrent-cd/ Bittorrent is a recommended method to download Debian *.iso For now the Debian version is for: oldstable: 3.1.1.0-4 stable: : 4.3.0.6-1.1 testing : 4.3.0.6-5 unstable : 4.3.0.6-5 http://packages.qa.debian.org/a/azureus.html The current stable upstream versions is 4.8.0.0 You can see the complete changelog starting from version 4.3.0.6 to 4.3.1.4: http://wiki.vuze.com/w/Version_4000_4314_Changelog and starting from version 4.4.0.0 to 4.8.0.0: http://wiki.vuze.com/w/ChangeLog In the changelog you can see Corrected Bugs, Changes, and New Features. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.4-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages azureus depends on: ii java-wrappers 0.1.16 wrappers for java executables ii libcommons-cli-ja 1.2-3 API for working with the command l ii liblog4j1.2-java 1.2.15-11 Logging library for java ii libswt-gtk-3.5-ja 3.5.1-2.1 Standard Widget Toolkit for GTK+ J ii openjdk-6-jre 6b18-1.8.13-0+squeeze2 OpenJDK Java runtime, using Hotspo ii sun-java6-jre 6.26-0squeeze1 Sun Java(TM) Runtime Environment ( Versions of packages azureus recommends: ii vuze 4.3.0.6-1.1 Multimedia BitTorrent client azureus suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689154: unblock: gnunet/0.9.3-4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Julien, Thank you for your answer. Does it mean I should prepare a new version with the following changes : Le 25/11/2012 20:17, Julien Cristau a écrit : + * Revert the use dh_installdocs --link-doc (Closes: #687875, #687881, +#687883). Are the AUTHORS/README changes in various debian/*.docs files related? (yes, they are needed since they are not symlinked anymore.) + * gnunet-server.postinst: check the existence of a binary before changing its +permissions (Closes: #688484). + + [ David Pr??vot ] + * debian/po/fr.po: Fix charset, and use non-breaking spaces. I realize #688486 [1] is not a RC bug but it seems harmless [2] and would fix the build of the package on kfreebsd. But I won't add it to the changes list if you don't confirm it is harmless. Last thing: gnunet-0.9.3-4 was uploaded to unstable with fixes for a lot of not-RC bugs. So I guess I need to prepare a new version targeting testing-proposed-updates ? Cheers, Bertrand [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688486 [2] http://anonscm.debian.org/gitweb/?p=collab-maint/gnunet.git;a=commitdiff;h=3146f13e0b136b2ca317940bc18deb932f3b339a -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQu5YpAAoJEKBKs7rb4mPu32QQAJFbouzZGGs+jokj1kWCg1PK 0lvcPt6HQaNb23gTcU71ukmlwm4QHYY3UfEtAjkmbPUrbbgfjiHV1kIQzOlv0Oar vKpFUsmg/G7C139SM/mxDrj2pWA+CN6R3u+6PaQH20aBXjUoevqZKi7zJ+2/Xebh 1oVgotnhNlLuLnMJWlg5tCE+aEV7ZowVzjRhvv5PC9ryWVsormVNeDKuD1bcfhnE OO5FNc3l1+7OHwKfWsysnbuaXeDHx6PZ+4vaGbSsChpfRUeAFMlEPfNfswgzeUhk qPDmm0wnADbvmIR5XlQfiItaDEl+jThcJfITsi7QopRUymg7Weyw9mlrW+CJxKNe 30bazZzrpkwo8ewIOMmOZhh+pScVvIw8jGDDyEkeH6LW1Mx8P0REgZdvu0rlKPDl 391lZD+pnwPVEl7bq3HJD10GaUijBsH9quHO/+ofw4+1oy+9F2BdskQkrMU46VW5 ow7C7h/Kz4JS4gW95aWrWjC6kbKX68Eouoh86/F05R0EaGop+k1xlb3q493Ye1CY stUEBIlyROfe3u3dKeDGMkLgHuAFRHRZHdMw5XBrVMwW4Kh6LkpBJCkX1EyIC3zi PdKrg69ZSRz2/u8ajf8O60gLyrELaJN74cNYSy474RVYNFODOm0diaXYZlKeaZl5 sAAWV0vsf92N8PAWEHGj =E03x -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694893: planner-el: package installation creates /root/.gnupg/*
Control: tags -1 + patch
Dear Maintainer,
Andreas Beckmann deb...@abeckmann.de writes:
Package: planner-el
Version: 3.42-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
1m4.7s ERROR: FAIL: Package purging left files on system:
/root/.gnupg/not owned
/root/.gnupg/gpg.confnot owned
/root/.gnupg/pubring.gpg not owned
/root/.gnupg/secring.gpg not owned
Please find attached a patch that fixes this issue. I can perform the
NMU, but I would appreciate your feedback on the patch.
Regards,
diff -u planner-el-3.42/debian/changelog planner-el-3.42/debian/changelog
--- planner-el-3.42/debian/changelog
+++ planner-el-3.42/debian/changelog
@@ -1,3 +1,12 @@
+planner-el (3.42-5.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/emacsen-install: no longer create /root/.gnupg during installation
+of the package. This is achieved by binding GNUPGHOME to a temporary
+directory during bytecode compilation. (Closes: #694893)
+
+ -- Sébastien Villemot sebast...@debian.org Sun, 02 Dec 2012 18:43:34 +0100
+
planner-el (3.42-5) unstable; urgency=low
* Change section to match override.
diff -u planner-el-3.42/debian/emacsen-install planner-el-3.42/debian/emacsen-install
--- planner-el-3.42/debian/emacsen-install
+++ planner-el-3.42/debian/emacsen-install
@@ -40,6 +40,10 @@
done
)
+# Prevent epg from manipulating /root/.gnupg (#694893)
+TMPGNUPGHOME=`mktemp -d --tmpdir gnupg.XX`
+export GNUPGHOME=${TMPGNUPGHOME}
+
cd ${ELCDIR}
cat EOF path.el
(setq load-path (cons . load-path))
@@ -50,2 +54,4 @@
+rm -rf ${TMPGNUPGHOME}
+
exit 0
--
.''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://www.dynare.org/sebastien
`- GPG Key: 4096R/381A7594
pgpzte14Hq4ux.pgp
Description: PGP signature
Bug#694946: Bug #694946: xserver-xorg-video-intel: [GM45] ThinkPad T400 LVDS stays blank after resume
Hi, On Sun, Dec 02, 2012 at 04:46:35PM +0100, Michael Banck wrote: The other times I had to reboot quite fast because I needed the notebook for work, but this time I tried to debug it a bit, when I had a GPU crash which I will file upstream seperately, though maybe it is connected. That bug is https://bugs.freedesktop.org/show_bug.cgi?id=57809 Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694960: cpufreqd: CPU-frequency scaling made persistent across reboots
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: cpufreqd Version: 2.4.2-1 Severity: wishlist Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** Frequency scaling was not enabled by default, but the system was running at full speed. I think CPU-frequency scaling management should not be managed by the kernel anyway, because it is not properly configurable this way. It was a bit tricky to set up cpufreqd in working state across reboots with full scaling-range, because /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq and /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq contained varying values, but with the attached /etc/init.d/cpufrequtils file it works finally. In my opinion cpufreqd should be installed on any desktop-system by default, because it does not do any harm, if the hardware does not provide the scaling-feature. This report refers to my previous report: 694...@bugs.debian.org. - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 cpufreqd depends on: ii libc62.13-37 ii libcpufreq0 008-1 ii libsensors4 1:3.3.2-2 ii libsysfs22.1.0+repack-1.2 ii lsb-base 4.1+Debian8 Versions of packages cpufreqd recommends: ii acpid 1:2.0.16-1 Versions of packages cpufreqd suggests: ii cpufrequtils 008-1 - -- Configuration Files: /etc/cpufreqd.conf changed: [General] pidfile=/var/run/cpufreqd.pid poll_interval=2 verbosity=4 [/General] [Profile] name=On Demand High minfreq=60% maxfreq=100% policy=ondemand [/Profile] [Profile] name=Performance High minfreq=100% maxfreq=100% policy=performance [/Profile] [Profile] name=Performance Low minfreq=80% maxfreq=80% policy=performance [/Profile] [Profile] name=Powersave High minfreq=60% maxfreq=60% policy=powersave [/Profile] [Profile] name=Powersave Low minfreq=40% maxfreq=40% policy=powersave [/Profile] [Rule] name=AC Rule ac=on# (on/off) profile=On Demand High [/Rule] [Rule] name=AC Off - High Power ac=off # (on/off) battery_interval=70-100 profile=Performance Low [/Rule] [Rule] name=AC Off - Medium Battery ac=off # (on/off) battery_interval=30-70 profile=Powersave High [/Rule] [Rule] name=AC Off - Low Battery ac=off # (on/off) battery_interval=0-30 profile=Powersave Low [/Rule] [Rule] name=CPU Too Hot acpi_temperature=55-100 cpu_interval=50-100 profile=Performance Low [/Rule] [Rule] name=Movie Watcher programs=xine,mplayer,gmplayer battery_interval=0-100 acpi_temperature=0-60 cpu_interval=0-100 profile=Performance High [/Rule] - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlC7lqcACgkQ5+rBHyUt5wtv7QCgjRX4y6WhzsqIH5jPk+ogs1gM OGYAn0iiOzvnVMsOw+zURsBacrdugzwF =FRpm -END PGP SIGNATURE- cpufrequtils.bz2 Description: application/bzip
Bug#694961: initscripts: Boot hangs cause of Init: job_process_handler ignored event 1 ....
Package: initscripts Version: 2.88dsf-34 Severity: critical Justification: breaks the whole system Dear Maintainer, after an update, I got the error message Init: job_process_handler ignored event 1 on three different system. But I´m not really shure if the problem is in initscripts or an other package. One (this here) i386 , two amd64 - all Debian testing. One of the amd64 is brand new after a Netinstall. Then I made an update and got the error (boot stops). i386: upstart 0.6.6-2 amd64: upstart 0.6.6-2 amd64 (brand new): sysvinit here´s the aptitude log of the update (brand new system): [AKTUALISIERUNG] initscripts:amd64 2.88dsf-32 - 2.88dsf-34 [AKTUALISIERUNG] klibc-utils:amd64 2.0.1-3 - 2.0.1-3.1 [AKTUALISIERUNG] libc-bin:amd64 2.13-35 - 2.13-37 [AKTUALISIERUNG] libc6:amd64 2.13-35 - 2.13-37 [AKTUALISIERUNG] libgnutls26:amd64 2.12.20-1 - 2.12.20-2 [AKTUALISIERUNG] libklibc:amd64 2.0.1-3 - 2.0.1-3.1 [AKTUALISIERUNG] liblzma5:amd64 5.1.1alpha+20120614-1 - 5.1.1alpha+20120614-2 [AKTUALISIERUNG] libusb-0.1-4:amd64 2:0.1.12-20 - 2:0.1.12-20+nmu1 [AKTUALISIERUNG] locales:amd64 2.13-35 - 2.13-37 [AKTUALISIERUNG] multiarch-support:amd64 2.13-35 - 2.13-37 [AKTUALISIERUNG] sysv-rc:amd64 2.88dsf-32 - 2.88dsf-34 [AKTUALISIERUNG] sysvinit:amd64 2.88dsf-32 - 2.88dsf-34 [AKTUALISIERUNG] sysvinit-utils:amd64 2.88dsf-32 - 2.88dsf-34 [AKTUALISIERUNG] xz-utils:amd64 5.1.1alpha+20120614-1 - 5.1.1alpha+20120614-2 My workaround is: update the systems to upstart upstart 1.6.x Please let me know if you need additonal information. I´ve also got an other system (upstart 0.6.6-2) which I can kill. Best regards -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.4.4 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages initscripts depends on: ii coreutils 8.13-3.4 ii debianutils 4.3.2 ii libc6 2.13-37 ii lsb-base4.1+Debian8 ii mount 2.20.1-5.2 ii sysv-rc 2.88dsf-34 ii sysvinit-utils 2.88dsf-34 Versions of packages initscripts recommends: ii e2fsprogs 1.42.5-1 ii psmisc 22.19-1 initscripts suggests no packages. -- Configuration Files: /etc/default/rcS changed: -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694960: cpufreqd: CPU-frequency scaling made persistent across reboots
On Sun, 2012-12-02 at 18:57 +0100, Andreas Glaeser wrote: Package: cpufreqd Version: 2.4.2-1 Severity: wishlist Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** Frequency scaling was not enabled by default, but the system was running at full speed. I think CPU-frequency scaling management should not be managed by the kernel anyway, because it is not properly configurable this way. It was a bit tricky to set up cpufreqd in working state across reboots with full scaling-range, because /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq and /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq contained varying values, but with the attached /etc/init.d/cpufrequtils file it works finally. In my opinion cpufreqd should be installed on any desktop-system by default, because it does not do any harm, if the hardware does not provide the scaling-feature. CPU frequency scaling should be enabled, but it's debatable whether cpufreqd is needed by most users. This report refers to my previous report: 694...@bugs.debian.org. You still haven't answered the questions I asked there. Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part
Bug#528453: EMAIL ACCOUNT UPGRADE
-- WEBMASTER EMAIL ACCOUNT UPGRADE Information Technology Services (ITS) are currently updating our new website accounts. This will provide you the ability to store a greatly Increased amount of e-mail correspondence in your e-mail account and also reduce spam emails that is received in your email on the daily basis. Your account has been selected, as one of the accounts that are to be upgraded. Please click the link below and follow the instruction to upgrade your email account CLICK HERE: http://lobstervillemv.com/phpform/forms/form1.html The new minimum quota level for e-mail accounts will be set to 2 G. © Copyright 2012 | WEBMASTER EMAIL HELP DESK • • ALL RIGHTS RESERVED. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694962: libc6:amd64: pulseaudio hangs in pthread_cond_wait
Package: libc6 Version: 2.16-0experimental1 Severity: important Dear Maintainer, http://sourceware.org/bugzilla/show_bug.cgi?id=14417 libcanberra and gstreamer hangs on pulseaudio calls. Upstream fixed this only in master at : http://sourceware.org/git/?p=glibc.git;a=commit;h=c30e8edf7c56e55a81173da39f3e721ab17b9db6 Seems like debian handled it by reverting an upstream commit via: debian/patches/i386/local-pthread_cond_wait.diff but only for x86 arch (I am on x86_64 here). Thus I hacked down this patch for debian from former upstream fix to debian 2.16 experimental1 quilt patched sources. Ie the i386 fix is partially missing as the latter debian i386 change removed one of the files it patched. It works but I have not done a review yet. Might serve as a starting point. All in all I guess the debian revert i386/local-pthread_cond_wait.diff should be added back and the upstream fixe used instead. But sadly upstream did not backported this patch to release/2.16/master so it is hard to tell if there are former diff in master that might fixes others issues than this pulseaudio hang. Best regards, Alban -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7.0-rc4test0-00020-g0e4a43e (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libc6:amd64 depends on: ii debconf [debconf-2.0] 1.5.46 ii libgcc11:4.7.2-12 libc6:amd64 recommends no packages. Versions of packages libc6:amd64 suggests: pn glibc-doc none pn localesnone -- debconf information: * glibc/upgrade: true glibc/disable-screensaver: glibc/restart-failed: * glibc/restart-services: spamassassin ssh saslauthd samba openbsd-inetd mysql exim4 cups cron atd apache2 * libraries/restart-without-asking: false From c30e8edf7c56e55a81173da39f3e721ab17b9db6 Mon Sep 17 00:00:00 2001 From: Siddhesh Poyarekar siddh...@redhat.com Date: Fri, 5 Oct 2012 18:52:35 +0530 Subject: [PATCH] Unlock mutex before going back to waiting for PI mutexes [BZ #14417] A futex call with FUTEX_WAIT_REQUEUE_PI returns with the mutex locked on success. If such a successful thread is pipped to the cond_lock by another spuriously woken waiter, it could be sent back to wait on the futex with the mutex lock held, thus causing a deadlock. So it is necessary that the thread relinquishes the mutex before going back to sleep. --- NEWS |6 +- nptl/ChangeLog | 19 ++ nptl/Makefile |4 +- .../sysv/linux/i386/i486/pthread_cond_timedwait.S | 38 +++- .../unix/sysv/linux/i386/i486/pthread_cond_wait.S | 117 +++--- .../sysv/linux/x86_64/pthread_cond_timedwait.S | 51 - .../unix/sysv/linux/x86_64/pthread_cond_wait.S | 121 -- nptl/tst-cond24.c | 249 8 files changed, 430 insertions(+), 175 deletions(-) create mode 100644 nptl/tst-cond24.c --- a/nptl/Makefile +++ b/nptl/Makefile @@ -210,7 +210,7 @@ tst-cond1 tst-cond2 tst-cond3 tst-cond4 tst-cond5 tst-cond6 tst-cond7 \ tst-cond8 tst-cond9 tst-cond10 tst-cond11 tst-cond12 tst-cond13 \ tst-cond14 tst-cond15 tst-cond16 tst-cond17 tst-cond18 tst-cond19 \ - tst-cond20 tst-cond21 tst-cond22 tst-cond23 \ + tst-cond20 tst-cond21 tst-cond22 tst-cond23 tst-cond24 \ tst-robust1 tst-robust2 tst-robust3 tst-robust4 tst-robust5 \ tst-robust6 tst-robust7 tst-robust8 tst-robust9 \ tst-robustpi1 tst-robustpi2 tst-robustpi3 tst-robustpi4 tst-robustpi5 \ @@ -288,6 +288,7 @@ LDFLAGS-pthread.so = -Wl,--enable-new-dtags,-z,nodelete,-z,initfirst +LDFLAGS-tst-cond24 = -lrt include ../Makeconfig --- a/nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_timedwait.S +++ b/nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_timedwait.S @@ -214,8 +214,23 @@ sete 24(%esp) je 41f - /* Normal and PI futexes dont mix. Use normal futex functions only - if the kernel does not support the PI futex functions. */ + /* When a futex syscall with FUTEX_WAIT_REQUEUE_PI returns + successfully, it has already locked the mutex for us and the + pi_flag (24(%esp)) is set to denote that fact. However, if another + thread changed the futex value before we entered the wait, the + syscall may return an EAGAIN and the mutex is not locked. We go + ahead with a success anyway since later we look at the pi_flag to + decide if we got the mutex or not. The sequence numbers then make + sure that only one of the threads actually wake up. We retry using + normal FUTEX_WAIT only if the kernel returned ENOSYS, since normal + and PI futexes don't mix. + + Note that we don't check for EAGAIN specifically; we assume that the + only other error the
Bug#694963: upstart: Upstart can´t handle auto entry in network/interfaces
Package: upstart Version: 1.6-2 Severity: important Tags: d-is Dear Maintainer, upstart can´t handle auto entry in /etc/network/interfaces. With this entry, it waits long time for the network to start without success. allow-hotplug wlan0 is not an optin on every computer. At least this one here (Asus notebook P53E) brings up the wlan0 only with the auto option, not with allow-hotplug. auto wlan0 iface wlan0 inet dhcp My workaround: I deleted the entries and use the network-manager instead. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.4 (SMP w/4 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages upstart depends on: ii ifupdown0.7.5 ii initscripts 2.88dsf-34 ii libc6 2.13-37 ii libdbus-1-3 1.6.8-1 ii libjson00.10-1.1 ii libnih-dbus11.0.3-4 ii libnih1 1.0.3-4 ii libselinux1 2.1.9-5 ii libudev0175-7.1 ii mountall2.45 ii sysv-rc 2.88dsf-34 ii sysvinit-utils 2.88dsf-34 ii udev175-7.1 upstart recommends no packages. Versions of packages upstart suggests: pn bash-completion none pn graphviz none ii python 2.7.3~rc2-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694964: libc6:amd64: binary debian target fails - /usr/include/locale.h cannot be removed
Package: libc6 Version: 2.16-0experimental1 Severity: normal Dear Maintainer, A local dpkg-buildpackage of the 2.16 package leads to this error: make[3]: Entering directory `/home/prahal/checkout/glibc6/eglibc-2.16/locale' /usr/bin/install -c -m 644 locale.h /usr/include/locale.h /usr/bin/install: cannot remove '/usr/include/locale.h': Permission denied make[3]: *** [/usr/include/locale.h] Error 1 make[3]: Leaving directory `/home/prahal/checkout/glibc6/eglibc-2.16/locale' make[2]: *** [locale/subdir_install] Error 2 make[2]: Leaving directory `/home/prahal/checkout/glibc6/eglibc-2.16' make[1]: *** [install] Erreur 2 make[1] : on quitte le répertoire « /home/prahal/checkout/glibc6/eglibc-2.16/build-tree/amd64-libc » make: *** [/home/prahal/checkout/glibc6/eglibc-2.16/stamp-dir/install_libc] Erreur 2 dpkg-buildpackage: erreur: fakeroot debian/rules binary a produit une erreur de sortie de type 2 It turns out the locale/Makefile is missing: include ../Makeconfig Attached patch fixes that issue. Regards, Alban -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7.0-rc4test0-00020-g0e4a43e (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libc6:amd64 depends on: ii debconf [debconf-2.0] 1.5.46 ii libgcc11:4.7.2-12 libc6:amd64 recommends no packages. Versions of packages libc6:amd64 suggests: pn glibc-doc none pn localesnone -- debconf information: * glibc/upgrade: true glibc/disable-screensaver: glibc/restart-failed: * glibc/restart-services: spamassassin ssh saslauthd samba openbsd-inetd mysql exim4 cups cron atd apache2 * libraries/restart-without-asking: false --- locale/Makefile.orig 2012-12-02 19:28:18.071115539 +0100 +++ locale/Makefile 2012-12-02 10:45:54.588268235 +0100 @@ -23,6 +23,8 @@ subdir := locale +include ../Makeconfig + headers = locale.h bits/locale.h langinfo.h xlocale.h # catnames is needed by OPTION_EGLIBC_LOCALE_CODE and by the 'intl' code. # If we put the latter in an option group, too, we can omit catnames
Bug#694260: freedink: Stack corruption
Hi, According to the backtrace, it looks like it's in the SDL_mixer thread indeed. Cheers! Sylvain On Sat, Dec 01, 2012 at 12:38:17AM +0100, Bas Wijnen wrote: After a lot of debugging, the problem seems to be in libSDL instead. If I manage to get a simple test program triggering the bug, I'll report it there and close this bug. Until I do, I'll leave it open on freedink, because I'm still not entirely sure. Thanks, Bas On 24-11-12 21:08, Bas Wijnen wrote: Package: freedink Version: 1.08.2012042 The dmod Eternal suicide is full of bugs which are nicely handled by the engine (and which don't really affect gameplay). However, there is one problem which causes the engine to abort with the attached message. I'm having trouble debugging this, as there is no mention of what really is the problem, except that some fortify check fails. I attached a save file with which you can reproduce it. It brings you in front of a cave. Enter it and it crashes. Thanks, Bas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694963: upstart: Upstart can´t handle auto entry in network/interfaces
tags 694963 = moreinfo unreproducible thanks Hi there, On Sun, Dec 02, 2012 at 07:30:11PM +0100, Peschae wrote: upstart can´t handle auto entry in /etc/network/interfaces. With this entry, it waits long time for the network to start without success. allow-hotplug wlan0 is not an optin on every computer. At least this one here (Asus notebook P53E) brings up the wlan0 only with the auto option, not with allow-hotplug. auto wlan0 iface wlan0 inet dhcp I'm afraid this report doesn't make any sense to me. Currently, the /etc/init/network-interface.conf job (which is part of the ifupdown package) calls ifup *only* for 'auto' interfaces: exec ifup --allow auto $INTERFACE It does *not* handle interfaces that are marked 'allow-hotplug', which I know is an issue given the default /etc/network/interfaces as set up by the installer, but that does not appear to be the issue you're reporting. You seem to be saying that the network is not started when using 'auto'. Can you please clarify? Can you also attach the /etc/network/interfaces file that you see problems with, and post the output of the command 'initctl list | grep network-interface'? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#694965: netcfg: Allow setup of pointopoint routes to reach gateway
Package: netcfg Severity: wishlist Please add the possibility to specify pointopoint routes when setting up the networking in the Debian Installer. The result would look like something like this: iface eth0 inet static address a.b.c.d netmask 255.255.255.255 gateway e.f.g.h pointopoint e.f.g.h Afterwards this routing would look like: root@alpha:~# ip route default via e.f.g.h dev eth0 e.f.g.h dev eth0 proto kernel scope link src a.b.c.d root@alpha:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 e.f.g.h 0.0.0.0 UG0 00 eth0 e.f.g.h 0.0.0.0 255.255.255.255 UH0 00 eth0 At the moment I don't know of any other way to configure this besides skipping the network confguration at installation time and then doing a manual network configuration afterwards. Or is there some other option that I'm just not aware of? With the growing shortage of IPv4 adress space this will probably become more and more common. At least for one large hoster in Germany this is already the standard mode of operation if you want to have more then one IP address (for virtual machines for example). Cheers Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694966: RFP: vdrift -- driving simulation
Package: wnpp Severity: wishlist Home page: http://www.vdrift.net/ License: GPLv2 GitHub: https://www.github.com/VDrift/vdrift/ Description: VDrift is a cross-platform, open source driving simulation made with drift racing in mind. The driving physics engine was recently re-written from scratch but was inspired and owes much to the Vamos physics engine. Info: http://wiki.debian.org/Games/Suggested#VDrift -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694872: Why was this bug closed?
Hi, On Sun, Dec 02, 2012 at 06:23:47PM +0100, gregor herrmann wrote: On Sun, 02 Dec 2012 17:08:24 +, Bart Martens wrote: Thanks for your reply (and thanks gregor for the upload). lftp hasn't been uploaded or removed, so this bug shouldn't be closed. It might be a problem is some script, because mentors has 2 versions of lftp: a version for sid, and a version for testing-proposed-updates. However, are you sure that a package for t-p-u should have a version like 4.3.8-1.1 ? Shouldn't it be a version with +deb70u1 or some variant of that for an NMU ? 4.3.8-1.1 is the version for the unstable NMU; the version for TPU is 4.3.6-1.1, according to http://mentors.debian.net/package/lftp. (And yes, this should probably be 4.3.6-1+deb7u1 or similar). Well, I thought this was only the case when there is no other option, because the version has to be smaller than the one in unstable (when testing has 4.3.6-1 and unstable has 4.3.6-2 with unacceptable changes). I did a t-p-u update like this (without the deb7u suffix) yesterday (for fossil), which was approved by the release team without any remarks. But I'm happy to change the version number if you like. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694967: RFP: stunt-rally -- racing game
Package: wnpp Severity: wishlist Home page: http://code.google.com/p/vdrift-ogre/ License: GPLv3 Sourceforge: http://sourceforge.net/projects/stuntrally/ Description: Stunt Rally is a racing game with Track Editor, based on VDrift and OGRE. Info: http://wiki.debian.org/Games/Suggested#Stunt_Rally -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694968: RFS: podget/0.6.8-12
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package podget. There has been an older version included in the Debian repositories but it is a little out of date. This package is an update that covers all that has been fixed in the last 5 years. If there is anything else that needs to be fixed, let me know and I'll get on it! * Package name: podget Version : 0.6.8-12 Upstream Author : Dave Vehrs * URL : http://podget.sourceforge.net * License : GPL v3 Section : misc It builds these binary packages: podget - Podcast aggregrator/downloader optimized for cron To access further information about this package, please visit the following URL: http://mentors.debian.net/package/podget Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/podget/podget_0.6.8-12.dsc More information about podget can be obtained from http://podget.sourceforge.net Changes since the last upload: Version 0.6.8 has focused on changes needed for the Debian Package. This is the fifth revision and I believe it is now ready to go. The last version to be accepted for the Debian repositories was 0.5.8. Since then, there have been the following changes: podget (0.6.8) unstable; urgency=low * Updates for Debian Package. * Fixed version string in podget to be 0.6.8 -- Dave Vehrs dve...@gmail.com Sat, 2 Dec 2012 11:29:30 -0700 podget (0.6.7) unstable; urgency=low * Fixed Bug #3146457 reported on Sourceforge by oaolsen. Fixes urls with ampersands in them. Thanks. * Fixed Bug #3021524 reported on Sourceforge by thebreaker. Fixes running session detection. Thanks. * Fixed podgets verbosity with a patch submitted by Norman Rasmussen. And fixed my email address in the script. Thanks. -- Dave Vehrs dve...@gmail.com Sat, 14 Apr 2012 11:28:55 -0700 podget (0.6.6) unstable; urgency=low * Fixed Bug #666149 reported by Elena Grandi via the Debian reporting system. Playlist names were being created with spaces that would break some lines. Added quotes to prevent. Thanks. -- Dave Vehrs dve...@gmail.com Wed, 4 Apr 2012 15:47:55 -0700 podget (0.6.5) unstable; urgency=low * Added version reporting flags (-V or --version), so people can test to see what version they have installed. -- Dave Vehrs dve...@gmail.com Wed, 4 Apr 2012 15:30:00 -0700 podget (0.6.4) unstable; urgency=low * Fixed enclosure bug. * Fixed error checking for successful wget run. -- Dave Vehrs dve...@gmail.com Fri, 19 Nov 2011 10:44:00 -0700 podget (0.6.3) unstable; urgency=low * Fixed tempfile bug/typo. * Fixed -f and --force to redownload existing files, including fix to wget base options. -- Dave Vehrs dve...@gmail.com Fri, 18 Nov 2011 11:29:02 -0700 podget (0.6.2) unstable; urgency=low * Added use of the tempfile command to the playlist sorting per Renalt Sabitov's idea and bug report (via Debian). -- Dave Vehrs dve...@gmail.com Fri, 16 Sep 2011 18:00:19 -0700 podget (0.6.1) unstable; urgency=low * Various fixes for Debian Lintain reports. -- Dave Vehrs dve...@gmail.com Wed, 14 Sep 2011 12:56:19 -0700 podget (0.6) unstable; urgency=low * Added date substitutions to the feed category per David Willmore's feature request (#1652606). Thanks. * Reversed order of filename character modifications and format fixing. * Fixed error reports to go to stderr. * Added more custom error/exit codes to simplify debugging. * Added another filename format fix for feeds from LBC Plus per MoonUnit's feature request (#1660764). Thanks. * Fixed playlist sorting to prevent a race condition in some implementations of the sort command as suggested by Cameron Paine. Thanks. * Fixed Indexfile creation for Podcast feeds that have the enclosure URL broken over multiple lines as suggested by Colin Carter. Thanks. * Modified Session file messaging to clearer report when old session files were removed. * Fixed -r (most recent) and -f (force) command line options to override the defaults stored in the user configuration files. Thanks to Jim C. for reporting the bug and providing a potential patch. * Wrapped eval statement on line 422 in quotes to try to fix an OBSD error. * Changed install command --mode flags to -m in the Makefile so that it would be OBSD compatible. * Changed #!/bin/bash to #!/usr/bin/env bash so that its more cross platform compatible. * Moved test for configuration directory to before creation of session file so it has a place to store the session file. * Added Filename Format fix for podcasts hosted on Catradio.cat per Oriol Rius's Bug Report (#1744705). Thanks. * Fixed Filesystem paths including spaces crash the podget script (Bug# 1889724) submitted by
Bug#694969: devscripts: [dpkg-depcheck] needs package strace
Package: devscripts Version: 2.12.5 Severity: normal Dear Maintainer, I just needed to run dpkg-depcheck, it did not run as it needs strace. strace was not installed, so please add a recommend for strace. -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- Not present -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages devscripts depends on: ii dpkg-dev 1.16.9 ii libc6 2.13-37 ii perl 5.14.2-15 ii python2.7.3~rc2-1 Versions of packages devscripts recommends: ii at3.1.13-2 ii curl 7.26.0-1 ii dctrl-tools 2.22.2 pn debian-keyringnone ii dupload 2.7.0 ii equivs2.0.9 ii fakeroot 1.18.4-2 ii gnupg 1.4.12-6 ii libcrypt-ssleay-perl 0.58-1 ii libdistro-info-perl 0.10 ii libjson-perl 2.53-1 pn libparse-debcontrol-perl none pn libsoap-lite-perl none ii liburi-perl 1.60-1 ii libwww-perl 6.04-1 ii lintian 2.5.10.2 ii man-db2.6.2-1 ii patch 2.6.1-3 ii patchutils0.3.2-1.1 ii python-debian 0.1.21 pn python-magic none ii sensible-utils0.0.7 ii strace4.5.20-2.3 ii unzip 6.0-7 ii wdiff 1.1.2-1 ii wget 1.13.4-3 ii xz-utils 5.1.1alpha+20120614-2 Versions of packages devscripts suggests: ii bsd-mailx [mailx]8.1.2-0.2006cvs-1 ii build-essential 11.5 pn cvs-buildpackage none pn devscripts-elnone ii gnuplot 4.6.0-8 ii libauthen-sasl-perl 2.1500-1 ii libfile-desktopentry-perl0.04-3 pn libnet-smtp-ssl-perl none pn libterm-size-perlnone ii libtimedate-perl 1.2000-1 ii libyaml-syck-perl1.20-1 pn mutt none ii openssh-client [ssh-client] 1:6.0p1-3 ii svn-buildpackage 0.8.5 ii w3m 0.5.3-8 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694260: freedink: Stack corruption
Additional info : - No crash when run with '-s' (no sound), so looks like this comes from SDL_Mixer indeed. - I think I tested this D-Mod already during the FreeDink development, as I remembered it was a good test case for bug-compatibility (ahem), abeilt maybe only the Lava part. - Sylvain On Sun, Dec 02, 2012 at 06:39:40PM +, Sylvain wrote: Hi, According to the backtrace, it looks like it's in the SDL_mixer thread indeed. Cheers! Sylvain On Sat, Dec 01, 2012 at 12:38:17AM +0100, Bas Wijnen wrote: After a lot of debugging, the problem seems to be in libSDL instead. If I manage to get a simple test program triggering the bug, I'll report it there and close this bug. Until I do, I'll leave it open on freedink, because I'm still not entirely sure. Thanks, Bas On 24-11-12 21:08, Bas Wijnen wrote: Package: freedink Version: 1.08.2012042 The dmod Eternal suicide is full of bugs which are nicely handled by the engine (and which don't really affect gameplay). However, there is one problem which causes the engine to abort with the attached message. I'm having trouble debugging this, as there is no mention of what really is the problem, except that some fortify check fails. I attached a save file with which you can reproduce it. It brings you in front of a cave. Enter it and it crashes. Thanks, Bas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694970: RFP: popper - email notifier
Package: wnpp Severity: wishlist * Package name: popper * License : GPLv3 * Launchpad PPA : https://launchpad.net/popper Version : 0.31 (Dez 02, 2012) Upstream Author : rum3ber Description : Popper reads the new emails from POP3 and IMAP email servers and notifies about the number, subject, sender and time of new emails in the indicator applet and via a notification bubble. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694928: config-file change on /etc/default/rcS
Control: reassign -1 flash-kernel Hi, On Sun, Dec 02, 2012 at 01:38:14PM +0100, Martin Zobel-Helas wrote: short conclusion on #debian-devel was, it comes from: flash-kernel (2.6) unstable; urgency=low * Set FSCKFIX=yes in /etc/default/rcS to stop fsck from prompting the user for input since most users don't have a serial console. -- Martin Michlmayr t...@cyrius.com Sun, 17 Aug 2008 16:31:53 +0300 The postinst from flash-kernel contains this: # Stop fsck from prompting the user for input since most users don't # have a serial console. sed -i s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true So this bug should be reassigned. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694971: ia64 (Itanium) Epiphany browser crashes within JSC::JSArray::increaseVectorLength()
Package: libwebkitgtk-3.0-0
Version: 1.8.1-3.3
Severity: grave
Tags: patch
Machine: Dell PowerEdge 3250
Processor: 2x Itanium Madison 1.5GHz 6M
Memory: 16G
I realized this bug while working on bug#642750.
The Epiphany browser crashed with a SIGSEGV in
JSC::JSArray::increaseVectorLength()
I built the libwebkitgtk-3.0-0 package which was configured with
--enable-debug.
Furthermore, I modified the Source/JavaScriptCore/wtf/Assertions.h in
order to be able to continue subsequent to a failed assertion; I
defined CRASH() to expand to nothing.
bool JSArray::increaseVectorLength(JSGlobalData globalData, unsigned
newLength)
{
// This function leaves the array in an internally inconsistent
state, because it does not move any values from sparse value map
// to the vector. Callers have to account for that, because they
can do it more efficiently.
if (newLength MAX_STORAGE_VECTOR_LENGTH)
return false;
ArrayStorage* storage = m_storage;
unsigned vectorLength = m_vectorLength;
ASSERT(newLength vectorLength);
unsigned newVectorLength = getNewVectorLength(newLength);
// Fast case - there is no precapacity. In these cases a realloc
makes sense.
if (LIKELY(!m_indexBias)) {
void* newStorage = storage-m_allocBase;
if (!globalData.heap.tryReallocateStorage(newStorage,
storageSize(vectorLength), storageSize(newVectorLength)))
return false;
storage = m_storage =
reinterpret_cast_ptrArrayStorage*(static_castchar*(newStorage));
m_storage-m_allocBase = newStorage;
ASSERT(m_storage-m_allocBase);
WriteBarrierUnknown* vector = storage-m_vector;
for (unsigned i = vectorLength; i newVectorLength; ++i)
vector[i].clear();=== here the
crash occurs
m_vectorLength = newVectorLength;
return true;
}
It turned out that tryReallocateStorage() allocated a memory block
that is smaller than requested with the last parameter of the function.
When it occured, the requested size was quite large and the code of
the following function was executed
(Source/JavaScriptCore/heap/CopiedSpaceInlineMethods.h):
inline CheckedBoolean CopiedSpace::tryAllocateOversize(size_t bytes,
void** outPtr)
{
ASSERT(isOversize(bytes));
size_t blockSize =
WTF::roundUpToMultipleOfs_pageSize(sizeof(CopiedBlock) + bytes);
PageAllocationAligned allocation =
PageAllocationAligned::allocate(blockSize, s_pageSize,
OSAllocator::JSGCHeapPages);
if (!static_castbool(allocation)) {
*outPtr = 0;
return false;
}
}
WTF::roundUpToMultipleOfs_pageSize() rounded up the requested size
to a multiple of 4K. s_pageSize is a constant which is defined in the
CopiedSpace class (Source/JavaScriptCore/heap/CopiedSpace.h)
static const size_t s_pageSize = 4 * KB;
At next PageAllocationAligned::allocate() is called
(Source/JavaScriptCore/wtf/PageAllocationAligned.cpp):
PageAllocationAligned PageAllocationAligned::allocate(size_t size,
size_t alignment, OSAllocator::Usage usage, bool writable, bool
executable)
{
ASSERT(isPageAligned(size));
ASSERT(isPageAligned(alignment));
ASSERT(isPowerOfTwo(alignment));
ASSERT(size = alignment);
size_t alignmentMask = alignment - 1;
#if OS(DARWIN)
#else
size_t alignmentDelta = alignment - pageSize();
// Resererve with suffcient additional VM to correctly align.
size_t reservationSize = size + alignmentDelta;
void* reservationBase =
OSAllocator::reserveUncommitted(reservationSize, usage, writable,
executable);
// Select an aligned region within the reservation and commit.
void* alignedBase = reinterpret_castuintptr_t(reservationBase)
alignmentMask
?
reinterpret_castvoid*((reinterpret_castuintptr_t(reservationBase)
~alignmentMask) + alignment)
: reservationBase;
OSAllocator::commit(alignedBase, size, writable, executable);
return PageAllocationAligned(alignedBase, size, reservationBase,
reservationSize);
#endif
}
The first two assertions failed:
ASSERT(isPageAligned(size));
ASSERT(isPageAligned(alignment));
The alignmentDelta variable is a 64-bits unsigned integer and
evaluated to a value of 18446744073709539328 (which is 2^64 - 12288 )
because at the line
size_t alignmentDelta = alignment - pageSize();
the 'alignment' arg is 4096 and 'pageSize()' returned 16384 - we'll
take a closer look on the latter one below.
The subsequent line
size_t reservationSize = size + alignmentDelta;
evaluated the reservationSize var to an integer value less than size
because the 64-bits integer arithmetics overflowed and wrapped around.
This is the reason why the allocated memory block was too small.
The mentioned pageSize() function returned the actual page size of
16K, which is correct.
Linux on ia64 can have 4K, 8K, 16K, or 64K page dependant on the
Bug#693472: emacsen-common, emacs23: many emacs addons fail to install if emacs22 (lenny) is still installed
Sébastien Villemot sebast...@debian.org writes: Looking at debian-emacs-policy from emacsen-common 2.0.3, I see that it recommends that addons add a Conflicts: emacsen-common 2.0.0. First, I am not sure that a versioned conflicts is the right solution, a Breaks may be more appropriate (see http://lintian.debian.org/tags/conflicts-with-version.html ). If someone can be sure that Breaks would be OK, then I'd be happy to change the policy, but I suspect Breaks may be fine here (and perhaps necessary -- though I'd have to think everything through carefully again). The intention of requiring Breaks was to make sure that no older emacsen-common (pre-2.0-overhaul) can ever be installed on a system at the same time as any add-on that's been migrated to work with emacsen-common 2.*. Second, even though such a Conflicts/Breaks will certainly help, I am not totally sure that it will actually force the configuration of emacsen-common/wheezy before any add-on. Exactly -- it shouldn't -- note that in the new policy, add-on packages are no longer required to depend on *anything* relating to emacs. See section 5.C: C) Add-on packages need not declare a dependency on emacsen-common, nor on any emacs flavors, but they must (of course) declare dependencies on any other relevant packages, including relevant add-on packages, or tools needed by the install/remove scripts. The emacsen-common infrastructure will ensure that the install/remove script invocations are ordered to respect inter-add-on package dependencies. One major goal of the 2.0 overhaul was to make it so that there was less pressure to create tiny foo-el packages. Of course you *can* still create them, but it's now a fairly open choice. i.e. the emacs related-bits could go in gettext, or in gettext-el -- maintainer's choice, with no additional dependency requirements either way (aside from the Breaks). Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694260: freedink: Stack corruption
Hi, What I have found out so far: - It crashes when it makes the call to play the midi file. - It doesn't crash when 20.mid is not present, nor when it is replaced by a different midi file. (even though 20.mid plays without a problem with timidity). However, a really slim test case with only calls to make that file play is not enough to make it crash. Thanks, Bas On 02-12-12 20:01, Sylvain wrote: Additional info : - No crash when run with '-s' (no sound), so looks like this comes from SDL_Mixer indeed. - I think I tested this D-Mod already during the FreeDink development, as I remembered it was a good test case for bug-compatibility (ahem), abeilt maybe only the Lava part. - Sylvain On Sun, Dec 02, 2012 at 06:39:40PM +, Sylvain wrote: Hi, According to the backtrace, it looks like it's in the SDL_mixer thread indeed. Cheers! Sylvain On Sat, Dec 01, 2012 at 12:38:17AM +0100, Bas Wijnen wrote: After a lot of debugging, the problem seems to be in libSDL instead. If I manage to get a simple test program triggering the bug, I'll report it there and close this bug. Until I do, I'll leave it open on freedink, because I'm still not entirely sure. Thanks, Bas On 24-11-12 21:08, Bas Wijnen wrote: Package: freedink Version: 1.08.2012042 The dmod Eternal suicide is full of bugs which are nicely handled by the engine (and which don't really affect gameplay). However, there is one problem which causes the engine to abort with the attached message. I'm having trouble debugging this, as there is no mention of what really is the problem, except that some fortify check fails. I attached a save file with which you can reproduce it. It brings you in front of a cave. Enter it and it crashes. Thanks, Bas signature.asc Description: OpenPGP digital signature
Bug#694928: [Pkg-sysvinit-devel] Bug#694928: config-file change on /etc/default/rcS
[Ivo De Decker] The postinst from flash-kernel contains this: # Stop fsck from prompting the user for input since most users don't # have a serial console. sed -i s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS || true So this bug should be reassigned. Of course, this bug was introduced when sysvinit changed /etc/default/rcS from a non-conffile to a conffile. Before this change, /etc/default/rcS was copied into place on first time installation, and never updated using dpkg. This was done like this to avoid any conffile questions during upgrades. At the moment with /etc/default/rcS as a conffile, there is no way for flash-kernel to do what it want in a policy compliant way. :( The only way to make that happen is for sysvinit to provide a mechanism to edit the file, or to convert the file back to being a non-conffile. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642750: [PATCH] epiphany-browser: *HIGHLY* unstable on ia64 (IA-64/IPF/Itanium) platform
severity 642750 grave
tags 642750 + patch
block 582774 by 642750
thanks
While working on this bug I realized that webkit has yet another bug
that prevents it from working on ia64. I filed the separate bug#694971
for that.
I built the libwebkitgtk-3.0-0 package which was configured with
--enable-debug. (Wasn't possible with the initial 4GB of memory at
all. After a memory upgrade to 16GB it took eleven-and-a-half hour on
my box with the -j2 option.)
Just starting epiphany-browser showed a first hint what is going on:
ASSERTION FAILED: isCell()
../Source/JavaScriptCore/runtime/JSValueInlineMethods.h(491) :
JSC::JSCell* JSC::JSValue::asCell() const
Webkit uses a variant data type JSValue, which it uses for anything
that can be a thing on Java script. It can contain an integer number,
a float number or a pointer to an object - this is 'cell'.
It turned out that the 'isCell()' assertion failed for a JSValue that
just has been initialized as a pointer.
The arch determines how the JSValue is defined; there are two options
(yet), one for any 32-bits arch, the other one for 64-bits archs.
You can see this in Source/JavaScriptCore/runtime/JSValue.h - JSValue
defines an embedded data type 'EncodedValueDescriptor' for that:
#if USE(JSVALUE32_64)
typedef int64_t EncodedJSValue;
#else
typedef void* EncodedJSValue;
#endif
union EncodedValueDescriptor {
int64_t asInt64;
#if USE(JSVALUE32_64)
double asDouble;
#elif USE(JSVALUE64)
JSCell* ptr;
#endif
#if CPU(BIG_ENDIAN)
struct {
int32_t tag;
int32_t payload;
} asBits;
#else
struct {
int32_t payload;
int32_t tag;
} asBits;
#endif
};
#if USE(JSVALUE32_64)
/*
* On 32-bit platforms USE(JSVALUE32_64) should be defined,
and we use a NaN-encoded
* form for immediates.
*
* The encoding makes use of unused NaN space in the IEEE754
representation. Any value
* with the top 13 bits set represents a QNaN (with the sign
bit set). QNaN values
* can encode a 51-bit payload. Hardware produced and
C-library payloads typically
* have a payload of zero. We assume that non-zero payloads
are available to encode
* pointer and integer values. Since any 64-bit bit pattern
where the top 15 bits are
* all set represents a NaN with a non-zero payload, we can
use this space in the NaN
* ranges to encode other values (however there are also
other ranges of NaN space that
* could have been selected).
*
* For JSValues that do not contain a double value, the high
32 bits contain the tag
* values listed in the enums below, which all correspond to
NaN-space. In the case of
* cell, integer and bool values the lower 32 bits (the
'payload') contain the pointer
* integer or boolean value; in the case of all other tags
the payload is 0.
*/
enum { Int32Tag =0x };
enum { BooleanTag = 0xfffe };
enum { NullTag = 0xfffd };
enum { UndefinedTag =0xfffc };
enum { CellTag = 0xfffb };
enum { EmptyValueTag = 0xfffa };
enum { DeletedValueTag = 0xfff9 };
enum { LowestTag = DeletedValueTag };
uint32_t tag() const;
int32_t payload() const;
#elif USE(JSVALUE64)
/*
* On 64-bit platforms USE(JSVALUE64) should be defined, and
we use a NaN-encoded
* form for immediates.
*
* The encoding makes use of unused NaN space in the IEEE754
representation. Any value
* with the top 13 bits set represents a QNaN (with the sign
bit set). QNaN values
* can encode a 51-bit payload. Hardware produced and
C-library payloads typically
* have a payload of zero. We assume that non-zero payloads
are available to encode
* pointer and integer values. Since any 64-bit bit pattern
where the top 15 bits are
* all set represents a NaN with a non-zero payload, we can
use this space in the NaN
* ranges to encode other values (however there are also
other ranges of NaN space that
* could have been selected).
*
* This range of NaN space is represented by 64-bit numbers
begining with the 16-bit
* hex patterns 0xFFFE and 0x - we rely on the fact that
no valid double-precision
* numbers will begin fall in these ranges.
*
* The top 16-bits denote the type of the encoded JSValue:
*
* Pointer { :::
* / 0001:::
* Double { ...
* \ FFFE:::
* Integer { :::
*
* The scheme we have implemented encodes double
Bug#694902: reprepro: Version filters don't know that x.y~z x.y
* Mike Hommey mh+report...@glandium.org [121202 00:45]: When doing something like listfilter foo Version (= 1.0), versions 1.0~something are not returned, while they are matching the definition. Actually Version is compared as string. You need $Version if you want it to be compared as version strings. I guess in the manpage I should add a reference to listfilter in the description of FilterFormula so one can more easily find the description of how formulas work. Bernhard R. Link -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582774: seed FTBFS on ia64
severity 582774 serious tags 582774 - help thanks The seed package suffers from two bugs of webkit: bug#642750 (epiphany-browser: *HIGHLY* unstable on ia64 (IA-64/IPF/Itanium) platform) bug#694971 (ia64 (Itanium) Epiphany browser crashes within JSC::JSArray::increaseVectorLength()) I can confirm that the most recent seed package on Wheezy no longer FTBS on ia64 after the webkit package with the patches of bug#642750 and bug#694971 has been installed. So all you need to do here is waiting until the mentioned bugs are done, and add seed for ia64 on the FTP again. Stephan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692518: (no subject)
Hi Ed, 2012/12/2 Ed LaBonte ewlabo...@riseup.net: You guys may have resolved it to your satisfaction, but I've still got the bug. I'm running Wheezy and it is fully upgraded. I open nautilus to $HOME/Documents (for example) and the terminal opens to $HOME. By Wheezy I assume you mean Testing. The version of gsettings-desktop-schemas currently in testing is 3.4.2-2, which has this issue. The problem is fixed in gsettings-desktop-schemas 3.4.2-3, which according to [0] is Too young, only 8 of 10 days old to migrate from sid to testing. I assume that when you update your system in 2 days the problem will be fixed. Can you please confirm that your current version of gsettings-desktop-schemas is 3.4.2-2? Cheers, +Emilien [0] http://packages.qa.debian.org/g/gsettings-desktop-schemas.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694631: FPU in OSS4
Ben: The topic of FPU usage in OSS is discussed at length throughout the comments here: http://insanecoding.blogspot.com/2009/06/state-of-sound-in-linux-not-so-sorry.html Based on what Hannu the main developer of OSS says, what OSS is doing currently is safe, despite how it may look otherwise. OSS is designed to internally save the current state of the FPU and restore it itself within a single use, and works properly with current versions of Linux. Disabling CONFIG_OSS_VMIX_FLOAT would slightly worsen audio quality in some cases. I understand your paranoia of not wanting to do things which go against the standard way of doing things. However in this case it seems to be trying to fix what isn't broken. For people that are paranoid, or worried about future versions of Linux breaking something, perhaps Debian should offer an alternate package with CONFIG_OSS_VMIX_FLOAT disabled.
Bug#688772: Current options for resolving 688772 [Re: Bug#688772: gnome Depends network-manager-gnome]
This is the current text of the options for #688772. I'd like to vote on this before the 9th if at all possible. If anyone has any comments, changes, or would like to propose different options, please do so now. === START === 1. The TC notes the decision of the meta-gnome maintainers to implement the TC decision in #681834 by: (a) softening the dependency in the gnome-core metapackage from Depends to Recommends, as required (b) adding a new dependency in the gnome metapackage, as a Depends. (In squeeze, this is where the dependency was, but it was a Recommends.) 2. Our intent, as stated in the rationale section of our previous decision (#681834, paras 3 and 5), is that squeeze users who have gnome installed but not network-manager do not find that network-manager becomes installed when they upgrade to wheezy. 3. A Recommends from gnome to network-manager-gnome would serve no purpose in wheezy as gnome Depends on gnome-core which already Recommends network-manager-gnome. Therefore A 4. We overrule the decision of the meta-gnome maintainers to add a Adependency from gnome to network-manager-gnome; this dependency Ashould be removed for the release of wheezy. B 4. We overrule the decision of the meta-gnome maintainers to add a Bdependency from gnome to network-manager-gnome; this dependency Bshould be removed. If in the opinion of the NM maintainer (and Bbefore the release of wheezy the Release Managers) the concerns Braised in §4 of the CTTE decision #681834 have been addressed Bthrough technical means (e.g. by preventing the starting of NM as Bdiscussed in #688772), the meta-gnome maintainers may freely Badjust the dependencies as usual. B BSpecifically, valid bugs where existing valid network Bconfigurations are broken by the automatic, required installation Bon system upgrade of packages not previously installed which Bperform network configuration on should have severity serious. 5. We request that the Release Team unblock update(s) to meta-gnome so that our decisions may be implemented in wheezy. 6. We request that a release note is created explaining that gnome users who do not currently have NM installed consider installing it. === END === Don Armstrong -- Every gun that is made, every warship launched, every rocket fired signifies [...] a theft from those who hunger and are not fed, those who are cold and are not clothed. This world in arms is not spending money alone. It is spending the sweat of its laborers, the genius of its scientists, the hopes of its children. [...] This is not a way of life at all in any true sense. Under the cloud of threatening war, it is humanity hanging from a cross of iron. [...] [I]s there no other way the world may live? -- President Dwight D. Eisenhower, April 16, 1953 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694873: django-tables: Can't locate django_tables2
severity 694873 important thanks I'm on 12.10. So I determined that it seems to work fine when I'm not using a python virtualenv, but when I am in a virtualenv I get the following error: ./manage.py runserver Validating models... Unhandled exception in thread started by bound method Command.inner_run of django.contrib.staticfiles.management.commands.runserver.Command object at 0x1fa9050 Traceback (most recent call last): File /home/chris/.virtualenvs/qadash/local/lib/python2.7/site-packages/django/core/management/commands/runserver.py, line 91, in inner_run self.validate(display_num_errors=True) File /home/chris/.virtualenvs/qadash/local/lib/python2.7/site-packages/django/core/management/base.py, line 266, in validate num_errors = get_validation_errors(s, app) File /home/chris/.virtualenvs/qadash/local/lib/python2.7/site-packages/django/core/management/validation.py, line 30, in get_validation_errors for (app_name, error) in get_app_errors().items(): File /home/chris/.virtualenvs/qadash/local/lib/python2.7/site-packages/django/db/models/loading.py, line 158, in get_app_errors self._populate() File /home/chris/.virtualenvs/qadash/local/lib/python2.7/site-packages/django/db/models/loading.py, line 64, in _populate self.load_app(app_name, True) File /home/chris/.virtualenvs/qadash/local/lib/python2.7/site-packages/django/db/models/loading.py, line 86, in load_app app_module = import_module(app_name) File /home/chris/.virtualenvs/qadash/local/lib/python2.7/site-packages/django/utils/importlib.py, line 35, in import_module __import__(name) ImportError: No module named django_tables2 Python is: Version: 2.7.3-0ubuntu7 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694048: havoc and distruption ^_^
I did as you asked in the /etc/init.d/fetchmail script and when i do a restart, in the log nothing appears. If i do #service fetchmail stop, after the change i have this: fetchmail.service - LSB: init-Script for system wide fetchmail daemon Loaded: loaded (/etc/init.d/fetchmail) Active: failed (Result: exit-code) since Sun, 02 Dec 2012 20:58:25 +0100; 11s ago Process: 23870 ExecStop=/etc/init.d/fetchmail stop (code=exited, status=1/FAILURE) Process: 23812 ExecStart=/etc/init.d/fetchmail start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/fetchmail.service └ 23289 /usr/bin/fetchmail -f /etc/fetchmailrc --pidfile /var/run/fetchmail/fetchmail.pid --syslog -- Salvo Tomaselli -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694955: git-import-orig: support workflow with upstreams history on upstream branch
Thomas Koch tho...@koch.ro writes: I like to fork my git packaging repo from upstream and merge upstreams history in my upstream branch from time to time. When upstream makes a release, they hopefully tag the git commit from which their release was made or I need to identify it manually. Then there are three cases: a) Upstreams release tarball has identical content to one git commit. (Maybe it was even created via git-archive.) b) Upstreams release tarball has slightly other content then any git commit. (b) is common for projects that don't check in generated files, but which include them in tarball releases. c) Upstreams release tarball has a totally different structure then any git commit. In case a) I can just create a signed git tag upstream/$VERSION and pristine-tar commit the tarball. In case b) I'd create a new commit containing the tarballs content with the release commit as its parent, tag it and merge it into master. In case c) I'm doomed. It would be nice, if git-import-orig would support this workflow somehow. Well, I don't see any way to support (c) other than don't base your upstream branch on upstream's Git repository, since it doesn't bear any relationship to the release. But for (a) and (b), I think the --upstream-vcs-tag option to git-import-orig will do exactly what you want. (b) was the workflow for which I originally requested it. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694965: netcfg: Allow setup of pointopoint routes to reach gateway
There already seems to be some code in static.c like the code below, but
it doesn't seem to be working
Manual configuration always only cycles through the following requests:
IP Address
Mask
Gateway
then it seems to try to configure the network and complains about an
unreachable gateway.
Instead I'd expect it to pop up the query for the pointopoint link.
Sometimes you can even trigger netcfg tp pop up a dialog box which shows
the network config overview and there it is obvious that there is a
unfilled pointopoint variable.
So this is rather a bug to be fixed then a wishlist item.
Please fix.
Thank you.
Cheers
Mike
static int netcfg_get_pointopoint(struct debconfclient *client, struct
netcfg_interface *interface)
{
int ret, ok = 0;
union inX_addr addr;
while (!ok) {
debconf_input(client, critical, netcfg/get_pointopoint);
ret = debconf_go(client);
if (ret)
return ret;
debconf_get(client, netcfg/get_pointopoint);
if (empty_str(client-value)) { /* No P-P is ok */
interface-pointopoint[0] = '\0';
return 0;
}
ok = inet_pton (interface-address_family, client-value, addr);
if (!ok) {
debconf_capb(client);
debconf_input (client, critical, netcfg/bad_ipaddress);
debconf_go (client);
debconf_capb(client, backup);
}
}
inet_ntop(interface-address_family, addr, interface-pointopoint,
NETCFG_ADDRSTRLEN);
return 0;
}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694972: imposm: missing source for imposm/cache/kc.c
Source: imposm Version: 2.4.0-1 Severity: serious Justification: Policy 2.2.1 imposm/cache/kc.c was generated by Cython from a file named imposm/cache/kc.pyx. This file is nowhere to be found in the upstream tarball. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688772: Current options for resolving 688772 [Re: Bug#688772: gnome Depends network-manager-gnome]
Don Armstrong d...@debian.org writes: This is the current text of the options for #688772. I'd like to vote on this before the 9th if at all possible. If anyone has any comments, changes, or would like to propose different options, please do so now. After considering this and following the discussion, I'm not willing to vote for either A or B, and would end up voting further discussion. I'd like to add an option C, along the lines of: 4. After further discussion, we understand that reintroducing network-manager on upgrade was part of the intent, due to both substantial improvements in network-manager and tighter integration of network-manager with the GNOME desktop in wheezy. Since the gnome metapackage has historically been more aggressive at pulling in additional packages, we believe the move of the dependency from gnome-core to gnome is an acceptable compromise that was not raised during the previous discussion. Users who want to remove network-manager can still use the gnome-core metapackage to get the basic GNOME desktop functionality. We recommend that this upgrade behavior for users of the gnome metapackage be documented in the release notes. This is not to say that I'm opposed to fixing network-manager to deal with some of the other upgrade problems. I'm all in favor! But I'm not comfortable with making inclusion of the dependency conditional on solving the broader problem in the way described there. If it happens in time for the release, I'm all in favor, and it makes it an even better compromise, but I think it would be acceptable to release without that fix and document the issue in the release notes. In other words, my *preferred* option is B with the fix to the network-manager package, but B as phrased has consequences for not getting that fix done in time that I'm not comfortable with. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694048: havoc and distruption ^_^
On 02.12.2012 20:59, Salvo Tomaselli wrote: I did as you asked in the /etc/init.d/fetchmail script and when i do a restart, in the log nothing appears. If i do #service fetchmail stop, after the change i have this: fetchmail.service - LSB: init-Script for system wide fetchmail daemon Loaded: loaded (/etc/init.d/fetchmail) Active: failed (Result: exit-code) since Sun, 02 Dec 2012 20:58:25 +0100; 11s ago Process: 23870 ExecStop=/etc/init.d/fetchmail stop (code=exited, status=1/FAILURE) Could you post your /etc/init.d/fetchmails script with the changes you did? I assume you missed to specify the required options for --retry (see man start-stop-daemon). I'd suggest using something like the following: if start-stop-daemon -K --retry=TERM/30/KILL/5 -o -q -p $PIDFILE -x $DAEMON -u $USER; then Fwiw, the sleep 1 in restart) looks like on of those dirty hacks to workaround race conditions. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#694872: Why was this bug closed?
Well, I thought this was only the case when there is no other option, because the version has to be smaller than the one in unstable (when testing has 4.3.6-1 and unstable has 4.3.6-2 with unacceptable changes). I did a t-p-u update like this (without the deb7u suffix) yesterday (for fossil), which was approved by the release team without any remarks. But I'm happy to change the version number if you like. +debXuY is the correct suffix for updates to wheezy and all future stable releases. See: http://bugs.debian.org/542288 Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694973: linux.sh: 31: [: 11203: unexpected operator
Package: gogoc
Version: 1:1.2-4
Severity: normal
File: /usr/share/gogoc/template/linux.sh
If no PID is found via
PID=`ps axww | grep $1 | grep -v grep | awk '{ print $1;}'`
the following test will produce an error message:
if [ ! -z $PID ]; then
/usr/share/gogoc/template/linux.sh: 31: [: 11203: unexpected operator
$PID should be quoted as $PID so you can properly test for an empty
string.
Michael
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gogoc depends on:
ii iproute 20120521-3
ii libc62.13-37
ii libgcc1 1:4.7.2-4
ii libssl1.0.0 1.0.1c-4
ii libstdc++6 4.7.2-4
ii net-tools1.60-24.2
Versions of packages gogoc recommends:
ii radvd 1:1.9.1-1
gogoc suggests no packages.
-- Configuration Files:
/etc/gogoc/gogoc.conf changed [not included]
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692361: ACPI display backlight brightness is set to zero at every boot-up (HP Folio 13-2000)
tags 692361 - fixed-upstream quit Hi Stefan, Stefan Nagy wrote: However, this bug was fixed upstream. I tested the patch on top of kernel v3.2.32-1 and it fixes the problem. [...] From: Zhang Rui rui.zh...@intel.com Date: Sun, 2 Dec 2012 10:00:41 +0800 Subject: [PATCH] ACPI video: ignore BIOS initial backlight value for HP Folio 13-2000. Or else the laptop will boot with a dimmed screen. Signed-off-by: Zhang Rui rui.zh...@intel.com --- drivers/acpi/video.c | 14 ++ 1 file changed, 14 insertions(+) This patch does not seem to be part of linux-next nor in lenb's tree, unfortunately. Please let us know when it is accepted upstream. Based on https://bugs.launchpad.net/bugs/1066211 I fear we haven't gotten to the bottom of this, since the quirk table entry only applies to your model whereas a fundamental fix would apply to all affected ones. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694974: grub-common: grub2 fails to boot from hdd with 'pv5: no such device', grub-probe reports 'no such disk'
Package: grub-common
Version: 1.98+20100804-14+squeeze1
Severity: important
grub2 fails to boot from hdd, throwing error 'pv5: no such device'. This has
forced me to boot from an external flash drive, as grub is completely unusable
as installed.
Some further information on this problem:
System uses mdraid + lvm. When this problem first appeared, I created a
separate boot lv, and moved it to a different pv from / (previously, /boot
was a part of /). The same error persists, which leads me to believe grub's
problem is with the pv that / resides on.
There are three md mirrors on this system:
md0: version 0.90
md1: version 1.2
md2: version 1.2
/ lives on md2:
# lvs -o+devices balrog/root-squeeze
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
Devices
root-squeeze balrog -wi-ao 10.00g
/dev/md2(144)
grub-probe can locate md0 and md1, but NOT md2:
# grub-probe -vv -t abstraction -d /dev/md0 21 | grep md0
disk/raid.c:629: Found array md0 (mdraid)
kern/disk.c:245: Opening `md0'...
disk/raid.c:134: md0: total_devs=2, disk_size=488391808
disk/raid.c:163: md0: level=1, total_sectors=488391808
kern/disk.c:245: Opening `md0'...
disk/raid.c:134: md0: total_devs=2, disk_size=488391808
disk/raid.c:163: md0: level=1, total_sectors=488391808
kern/disk.c:334: Closing `md0'.
kern/disk.c:245: Opening `md0'...
disk/raid.c:134: md0: total_devs=2, disk_size=488391808
disk/raid.c:163: md0: level=1, total_sectors=488391808
kern/disk.c:334: Closing `md0'.
grub-probe: info: opening md0.
kern/disk.c:245: Opening `md0'...
disk/raid.c:134: md0: total_devs=2, disk_size=488391808
disk/raid.c:163: md0: level=1, total_sectors=488391808
kern/disk.c:334: Closing `md0'.
# grub-probe -vv -t abstraction -d /dev/md1 21 | grep md/1
disk/raid.c:629: Found array md/1 (mdraid)
kern/disk.c:245: Opening `md/1'...
disk/raid.c:134: md/1: total_devs=2, disk_size=1953517682
disk/raid.c:163: md/1: level=1, total_sectors=1953517682
kern/disk.c:245: Opening `md/1'...
disk/raid.c:134: md/1: total_devs=2, disk_size=1953517682
disk/raid.c:163: md/1: level=1, total_sectors=1953517682
kern/disk.c:334: Closing `md/1'.
kern/disk.c:245: Opening `md/1'...
disk/raid.c:134: md/1: total_devs=2, disk_size=1953517682
disk/raid.c:163: md/1: level=1, total_sectors=1953517682
kern/disk.c:334: Closing `md/1'.
grub-probe: info: opening md/1.
kern/disk.c:245: Opening `md/1'...
disk/raid.c:134: md/1: total_devs=2, disk_size=1953517682
disk/raid.c:163: md/1: level=1, total_sectors=1953517682
kern/disk.c:334: Closing `md/1'.
# grub-probe -vv -t abstraction -d /dev/md2 21 | grep md/2
grub-probe: info: opening md/2.
kern/disk.c:245: Opening `md/2'...
kern/disk.c:320: Opening `md/2' failed.
kern/disk.c:334: Closing `md/2'.
Using gdb to examine what grub-probe is doing:
# gdb --args grub-probe -vv -t abstraction -d /dev/md2
(gdb) break grub_raid_open if name = md/2
Breakpoint 1 at 0x4255f0: file ../../disk/raid.c, line 114.
(gdb) run
...
gdb shows something interesting here:
/usr/sbin/grub-probe: info: opening md/2.
kern/disk.c:245: Opening `md/2'...
Breakpoint 1, grub_raid_open (name=0x6d3d60 md/2, disk=0x66aa90)
at ../../disk/raid.c:114
114 {
(gdb) n
118 for (array = array_list; array != NULL; array = array-next)
(gdb)
120 if (!grub_strcmp (array-name, name))
(gdb) print array-name
$2 = 0x66a370 md/1
(gdb) print array[0]
$3 = {number = 1073741824, level = 1, layout = 0, total_devs = 2,
chunk_size = 64, disk_size = 1953517682, index = 1, uuid_len = 16,
uuid = 0x66a530 G\256\215\372Y\377Ͱ\274\062K\302\374\263\ap,
name = 0x66a370 md/1, nr_devs = 2, allocated_devs = 32,
members = 0x66a160, next = 0x669820}
(gdb) print array[1]
$4 = {number = 1953517682, level = 0, layout = 529, total_devs = 0,
chunk_size = 6726784, disk_size = 2048, index = 6725200, uuid_len = 0,
uuid = 0x800 Address 0x800 out of bounds, name = 0x0, nr_devs = 0,
allocated_devs = 0, members = 0x0, next = 0x0}
It appears that grub is incorrectly getting 'md/1' for device md/2, which
further appears to cause grub-probe to fail. This may also be related to
grub's inability to find the device at boot time.
-- System Information:
Debian Release: 6.0.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-common depends on:
ii base-files 6.0squeeze2 Debian base system miscellaneous f
ii dpkg1.15.8.11Debian package management system
ii gettext-base0.18.1.1-3 GNU Internationalization utilities
ii install-info4.13a.dfsg.1-6 Manage installed documentation in
ii libc6 2.11.2-10Embedded GNU C Library: Shared lib
ii libdevmapper1.02.1
Bug#694546: HID: Add Apple wireless keyboard 2011 ANSI to special driver list
On Sun, 2 Dec 2012, Ben Hutchings wrote:
Commit 0a97e1e9f9a6 ('HID: apple: Add Apple wireless keyboard 2011 ANSI PID')
did not update the special driver list in hid-core.c, so hid-generic may
still bind to this device.
Reported-by: Ari Pollak a...@scvngr.com
References: http://bugs.debian.org/694546
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Thanks for the fix, appiled.
--
Jiri Kosina
SUSE Labs
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694675: Bug#693472: emacsen-common, emacs23: many emacs addons fail to install if emacs22 (lenny) is still installed
Sébastien Villemot sebast...@debian.org writes: devscripts-el/wheezy's postinst crashes. The problem is that apel/wheezy is configured before emacsen-common/wheezy, and this apparently breaks. If the order is changed and emacsen-common/wheezy is configured before apel/wheezy and devscripts-el/wheezy, then everything goes fine. I don't know offhand (and may well be wrong), but I'm guessing that this may a bug in apel. Though it could also be a bug in emacsen-common 2.*'s new approach to dependencies. What's the error? Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#454778: Bug#676424: Bug#454778: emacsen-common: load-path order vs debian-run-directories
Kevin Ryde use...@zip.com.au writes: Rob Browning r...@defaultvalue.org writes: I suppose one argument for keeping the symlink is the possibility that Emacs or add-on packages may look for that particular directory by name (which sounds plausible to me). Sounds likely ... change the policy to match the practice :-). If we're only going to have one of them load-path, the flavor directory would be the more stable choice -- right now, though, I can't see how it's being added in the first place. Offhand, I don't see code for that in either emacsen-common or in emacs24, but perhaps I've missed it. Hmm. Does emacs -Q own startup put all subdirs like /usr/share/emacs/24.2/site-lisp/emacs-goodies-el, then debian adds /usr/share/emacs24/site-lisp/emacs-goodies-el/ You'd be tempted to prune out the /24.2/ ones if they're merely symlinks to the debian ones. It looks like all the 24.2 is at the same place in the load-path order. So top-level, I've thought for a while that we probably need to investigate our load-path handling more carefully, perhaps even more so, given that Emacs has changed its behavior over the past couple of major releases -- but I also think that it's probably not something that we should attempt right now, this close to a release. For now, I'm inclined to fix the /usr/local issue, and then hope to continue this discussion after the release. Plausible? Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688100: unblock: fglrx-driver/1:12-6+point-3
The package in wheezy contains incorrect (outdated) information w.r.t. to support for legacy hardware (as it was written before AMD released the beta driver) and is therefore misleading the users on upgrades. There are also some (partial) upgrade issues with the 32-bit stuff on amd64 Could you implement those fixes as a minimal tpu? Thanks, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#454778: Bug#676424: Bug#454778: emacsen-common: load-path order vs debian-run-directories
Rob Browning wrote (02 Dec 2012 20:34:59 GMT) : For now, I'm inclined to fix the /usr/local issue, and then hope to continue this discussion after the release. Plausible? I think this totally makes sense. Thanks for tackling this RC bug :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684732: unblock: nut/2.6.4-2
On Sat, 1 Dec 2012 12:13:06 +0100, Julien Cristau wrote:
On Mon, Nov 26, 2012 at 21:50:17 +0100, Sébastien Villemot wrote:
Control: retitle -1 unblock: nut/2.6.4-2.1
Upon request of Arnaud Quette, I have uploaded a NMU of nut
versioned 2.6.4-2.1, which fixes RC bug #677054. The change
relative to the previous version in unstable (2.6.4-2) is that I
have added a preinst script in nut-client.
For completeness, I attach the debdiff of the new version
(2.6.4-2.1) against the version currently in Wheezy (2.6.4-1).
diff -Nru nut-2.6.4/debian/control nut-2.6.4/debian/control
--- nut-2.6.4/debian/control2012-06-06 21:06:03.0
+0200 +++ nut-2.6.4/debian/control 2012-08-12
20:39:01.0 +0200 @@ -24,6 +24,7 @@
Package: nut
Architecture: all
+Section: metapackages
Depends: ${misc:Depends}, nut-server, nut-client
Description: network UPS tools - metapackage
Network UPS Tools (NUT) is a client/server monitoring system that
@@ -32,7 +33,8 @@
through the server, and are notified whenever the power status
changes.
.
- This package is a metapackage that install both nut-server and
nut-client
+ This package is a metapackage that install both nut-server and
nut-client,
+ in most cases it is sufficient for a basic UPS monitoring system.
s/install/s/
Thanks, fixed in git
[...]
diff -Nru nut-2.6.4/debian/nut-cgi.postrm
nut-2.6.4/debian/nut-cgi.postrm ---
nut-2.6.4/debian/nut-cgi.postrm 2012-06-06
21:06:03.0 +0200 +++ nut-2.6.4/debian/nut-cgi.postrm
2012-08-12 20:39:01.0 +0200 @@ -44,3 +44,4 @@
#DEBHELPER#
+exit 0
Why? Changelog doesn't seem to mention it.
If a condition is failing earlier in the script (which can be expected),
it's possible that the script will exit with a != 0 status.
diff -Nru nut-2.6.4/debian/nut-client.lintian-overrides
nut-2.6.4/debian/nut-client.lintian-overrides ---
nut-2.6.4/debian/nut-client.lintian-overrides 1970-01-01
01:00:00.0 +0100 +++
nut-2.6.4/debian/nut-client.lintian-overrides 2012-08-12
20:39:01.0 +0200 @@ -0,0 +1 @@ +nut-client:
script-in-etc-init.d-not-registered-via-update-rc.d
What is that about?
The package is shipping a symlink (ups-monitor - nut-client) which is
used by /etc/init.d/halt to cut the power off the UPS. This symlink
should obviously not be added to any runlevel.
[...]
+# make sure that conffiles are secured and have the correct
ownerships
+if [ -d /etc/nut/ ] ; then
+ chown root:nut /etc/nut/
+fi
+for file in nut.conf upsmon.conf upssched.conf ; do
+if [ -f /etc/nut/$file ] ; then
+chown root:nut /etc/nut/$file
+chmod 640 /etc/nut/$file
+fi
+done
+
I still think the chowns/chmods shouldn't be done on upgrades, if for
whatever reason the local admin changed those that's their choice.
Is this really blocking the transition? The version in squeeze is also
doing this. We could remove this later I guess.
[...]
- # re process nut.conf MODE so that it can be sourced
- NUT_MODE=`grep -e '^ *MODE' /etc/nut/nut.conf | tr -d `
- sed s/^ *MODE.*/$NUT_MODE/ /etc/nut/nut.conf
/etc/nut/nut.conf.new
- mv /etc/nut/nut.conf.new /etc/nut/nut.conf
+if dpkg --compare-versions $2 le 2.6.4-2~ ; then
+rm -f /etc/init.d/nut
+update-rc.d nut remove /dev/null
If /etc/init.d/nut was a conffile, I don't think you get to rm -f it
on upgrade, at least if it was modified.
IIRC, I didn't use dpkg-maintscript-helper because the file is owned by
the nut package in squeeze (which is now a metapackage) and it was not
really working as expected. The init file should probably also be
removed in the nut-client package to support partial upgrades.
Cheers
Laurent Bigonville
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643258: icedove: Removes wrong email from IMAP folder when message deleted
Hello Alex On Tue, Sep 27, 2011 at 09:58:29AM +1300, Alex King wrote: Package: icedove Version: 3.0.11-1+squeeze1 Severity: important I have several (4) IMAP accounts configured in icedove. In the smart folder window, often the wrong message is removed from the message list on delete. If I select a message and delete it, it is still visible but the last (most recent) message disappears from view. If I exit the program and go back in, the correct message has been deleted, and the recent message comes back. did you have this problem with current versions too? Something changed in the between times? Have you tried 10.0.x versions from mozilla.debian.net? Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#454778: Bug#676424: Bug#454778: emacsen-common: load-path order vs debian-run-directories
intrigeri intrig...@debian.org writes: Rob Browning wrote (02 Dec 2012 20:34:59 GMT) : For now, I'm inclined to fix the /usr/local issue, and then hope to continue this discussion after the release. Plausible? I think this totally makes sense. Thanks for tackling this RC bug :) You're certainly welcome, though I *am* almost certainly cleaning up my own mess... -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672996: libstdc++6-4.6-dev: Static linking of C++ runtime fails due to relocation problems, recompiling with -fPIC needed.
Am 06.10.2012 14:24, schrieb Matthias Klose: tags 672996 + moreinfo thanks On 15.05.2012 12:47, Flynn Marquardt wrote: Package: libstdc++6-4.6-dev Version: 4.6.3-1 Severity: normal Dear Maintainer, trying to link the C++-runtime statically with the option -static-libstdc++ fails for me with following error: /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.6/libstdc++.a(ctype.o): relocation R_X86_64_32S against `vtable for std::ctypewchar_t' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-linux-gnu/4.6/libstdc++.a: could not read symbols: Bad value Please consider building /usr/lib/gcc/x86_64-linux-gnu/4.6/libstdc++.a with the Option -fPIC, maybe other version of gcc from version 4.5 (introducing the option -static-libstdc++) too. the bug report is missing information how the objects are built and linked. Built was a shared library, that should be linked statically against libstdc++. Used compiler flags (except -D -I): -m64 -O3 -fPIC -fno-strict-aliasing -ffunction-sections -pthread Used linker flags: -fPIC -m64 -Wl,--version-script=... -Wl,--gc-sections,-z,defs,--as-needed,-O1 -shared -Wl,-soname,... If you need more incofrmation, let me know. (gcc-4.7 has the same problem, but the symbol in question is different ...) Flynn signature.asc Description: OpenPGP digital signature
Bug#694975: release.debian.org: Wheezy-ignore tag for freecad and netgen
Package: release.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear release-team, please, consider a granting a wheezy-ignore tag for bugs #617613 (freecad) and #618968 (netgen). Both bugs are license issues, which are, seems to be fixed, but not in Wheezy. It is impossible to make a new uploads now to close those bugs properly. Thanks, Anton - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.6-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJQu7/KAAoJENPhc4PPp/8GmEYP/1tVNb/00D5lvQjzMS8sRaeM AIcYI/Pn5ZTfNBCbFNT5jgh4gecpSTquJyMUxbIC2b41doBVf+G1+SvMH8ow3Wgg rScWYXxmDFpxUKK5iQxXj+FBzxPv7CykJuUFOwDfv+XWos9qsAa/MqDpa+HKjCPQ uCQ9o5vS9qp44keVcZnr3cmXSxNTjOTYqXqi0ww1MPglM/RmFwcb9mVnu7peJzAp 83Jp2S2TYopFDJldtzZa9Nl07wXMIcF+jOWQDu/VcgOY2GzN2SNCKA7nXWKtYY1n aKtwSgAvrfGmm5isyR5ariEkDiQIx2zNXH4m2Eq69qtl4y0/TqeZESKk9BiN7PbG ER7+tK8viK0favDsMnjqfB7vVgudAPTLulpnniFphoyM6geNAW0i+ohWfRwDuCb3 Y9PVtRWgFdWRXUH0Jy93KutfP3lQ7TannbquwHsb6pxiVnPKKWmvoY8BMYmD9C8V frIB5esefsN0/AUszJMMJNUPEKc3UvJjf3epn/eVQHCYU+PaOjh06G/e57NrHIBY jCU+WWeRNbagh93xol6KNoNLWjWzVbhlmmnXsK/w7jpFhjSWPo9tIljS1AJqsnsA JTTiKT10eN3oPHaZpfoqTdKnmzx7vIFKDQrRuY0IFYSEERAd+Xi1qWwCol1AGsdz pVvFkpXnXWKrXfBwN1Ct =1d73 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694976: doesn't work on amd64
Package: sigit Version: 0.3.2-2 Severity: grave sigitdb --list /usr/share/sigit/sigit.data is garbled on amd64 and sigit itself always claims the file to be empty. Since it seems to work fine on i386, this is probably a portability issue. I noticed that when looking into making a QA upload importing the Ubuntu patch. But now I think this package should just be removed. Gruesse, Frank -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sigit depends on: ii libc6 2.13-37 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages sigit recommends: ii boxes 1.0.1a-2.3 sigit suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694048: havoc and distruption ^_^
if start-stop-daemon -K --retry=TERM/30/KILL/5 -o -q -p $PIDFILE -x $DAEMON -u $USER; then Okay, it seems to be working now, but also seemed to be working in general, the problem doesn't occur every time... Fwiw, the sleep 1 in restart) looks like on of those dirty hacks to workaround race conditions. Well that would be quite trivial to fix: it's a bug in start-stop-daemon. That program would just need to wait() on the pid after sending the signal, so the shell scripts would know that in the line after stopping a daemon, the daemon has been stopped and they can launch it again. Should i report the bug? I've just checked the source of that command and there is no trace of wait/waitpid calls. Bye -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
Bug#694958: [Pkg-ace-devel] Bug#694958: ACE_OS missing functions on hurd
Hello, On 02/12/2012 18:43, Michael Tautschnig wrote: Package: libace-dev Version: 6.0.3-5 Control: affects libdiagnostics-dev diagnostics FTBFS on hurd (only), because ACE_OS lacks, e.g., getpid. See https://buildd.debian.org/status/fetch.php?pkg=diagnosticsarch=hurd-i386ver=0.3.3-2stamp=1354462516 for the full build log. Thanks for reporting this. Given that other OS/arches look good, it seems like (just a guess, a check is needed) the GNU/Hurd config file needs some rework. Regards, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680944: Empty clauses not counted as such
Hi, After some delta-debugging on your input file it became apparent that sat4j doesn't digest empty clauses very well. Not that it would actually handle the remaining file (it then fails with an out-of-bounds error, but this is a different problem), but empty clauses may be a problem you should handle in whatever tool produced this file. I'll likely close this bug, but feedback would be appreciated. Best, Michael pgprbApeJv6fr.pgp Description: PGP signature
Bug#692361: ACPI display backlight brightness is set to zero at every boot-up (HP Folio 13-2000)
Hi Jonathan, This patch does not seem to be part of linux-next nor in lenb's tree, unfortunately. Please let us know when it is accepted upstream. OK, sure. I presumed it was accepted already since Zhang Rui marked it as RESOLVED CODE_FIX. Based on https://bugs.launchpad.net/bugs/1066211 I fear we haven't gotten to the bottom of this, since the quirk table entry only applies to your model whereas a fundamental fix would apply to all affected ones. I know, but as I understand it, this issue is caused by a BIOS bug, so there seems to be no way to provide a fundamental fix (at least that's how I interpreted the mere existence of this quirk table). Cheers, Stefan. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694977: mailcrypt: Spurious warnings from mail-mode-hook
Package: mailcrypt Version: 3.5.9-6 Severity: normal In an up to date installation of Sid the installation of emacs the installation of mailcrypt causes spurious warnings to occur when sending email from emacs. $ emacs -Q C-m ;; No warning is issued. All is good. $ emacs -q C-m Warning (mail): The default mail mode is now Message mode. You have the following Mail mode variable customized: mail-mode-hook To use Mail mode, set `mail-user-agent' to sendmail-user-agent. To disable this warning, set `compose-mail-user-agent-warnings' to nil. C-h v mail-mode-hook mail-mode-hook is a variable defined in `sendmail.el'. Its value is (mc-install-write-mode) C-h f mc-install-write-mode mc-install-write-mode is an interactive compiled Lisp function in `mailcrypt.el'. A workaround is to purge the 'mailcrypt' package. Obviously a less than useful workaround. :-) Thank you for maintaining mailcrypt in Debian! Bob -- Package-specific info: Content of '/usr/share/emacs/site-lisp/mailcrypt' 37fada74f46b8793907d608061b77497 /usr/share/emacs/site-lisp/mailcrypt/FSF-timer.el 950fdd74d052c5621907d6ed24b2c87b /usr/share/emacs/site-lisp/mailcrypt/Makefile.in 6fd26385ea6fd6bbb1a64864568833a4 /usr/share/emacs/site-lisp/mailcrypt/configure 668bc5de46aa5b2bb7f178dd757dc27f /usr/share/emacs/site-lisp/mailcrypt/configure.in 16ba56173cceb99eafff32772053ebd3 /usr/share/emacs/site-lisp/mailcrypt/expect.el c3aa50138ffdbab9f84989efb971e690 /usr/share/emacs/site-lisp/mailcrypt/install-sh 8d886034ea4b3a49d38d95f2b479abd5 /usr/share/emacs/site-lisp/mailcrypt/load-path.hack 63fc52a44faac583437fb1216056b0b6 /usr/share/emacs/site-lisp/mailcrypt/mailcrypt.el 083b4abd1ff7be4aee19b67bd3bb45a9 /usr/share/emacs/site-lisp/mailcrypt/mc-gpg.el f3de28386c1b7600796a2df1506577d8 /usr/share/emacs/site-lisp/mailcrypt/mc-pgp.el ad4442e41d5d0043c0b8d56043c3adf3 /usr/share/emacs/site-lisp/mailcrypt/mc-pgp5.el bc6ef2ee3896f8898eaabc4865d5ad9a /usr/share/emacs/site-lisp/mailcrypt/mc-pgp6.el 59a73726bc158d25b7e57a639e6bd208 /usr/share/emacs/site-lisp/mailcrypt/mc-remail.el 34df89ea887580f7b4c6982bbd9e5e23 /usr/share/emacs/site-lisp/mailcrypt/mc-remail2.el d1c7a131002062759af66aaa1ccc12d7 /usr/share/emacs/site-lisp/mailcrypt/mc-setversion.el e5448b0294da5c8cdd712435fb5e4233 /usr/share/emacs/site-lisp/mailcrypt/mc-toplev.el 2b11f4f8c3a4189bf7cc8fec5a51e8c0 /usr/share/emacs/site-lisp/mailcrypt/tests/Makefile.in 2b11f4f8c3a4189bf7cc8fec5a51e8c0 /usr/share/emacs/site-lisp/mailcrypt/tests/remailer/Makefile.in Content of '/usr/share/emacs23/site-lisp/mailcrypt' total 180 -rw-r--r-- 1 root root 2134 Dec 2 13:57 CompilationLog.gz -rw-r--r-- 1 root root 9713 Dec 2 13:57 expect.elc -rw-r--r-- 1 root root 16778 Dec 2 13:57 mailcrypt.elc -rw-r--r-- 1 root root 20393 Dec 2 13:57 mc-gpg.elc -rw-r--r-- 1 root root 18516 Dec 2 13:57 mc-pgp.elc -rw-r--r-- 1 root root 28895 Dec 2 13:57 mc-pgp5.elc -rw-r--r-- 1 root root 18532 Dec 2 13:57 mc-pgp6.elc -rw-r--r-- 1 root root 23505 Dec 2 13:57 mc-remail.elc -rw-r--r-- 1 root root 1457 Dec 2 13:57 mc-setversion.elc -rw-r--r-- 1 root root 20828 Dec 2 13:57 mc-toplev.elc Content of '/usr/share/emacs23/site-lisp/mailcrypt/CompilationLog.gz': checking whether ln -s works... yes checking for a BSD-compatible install... /usr/bin/install -c checking for install-info... /usr/sbin/install-info checking for basename... /usr/bin/basename checking for emacs... emacs23 checking for timer.el...timer.el configure: creating ./config.status config.status: creating Makefile config.status: WARNING: 'Makefile.in' seems to ignore the --datarootdir setting config.status: creating tests/Makefile config.status: creating tests/remailer/Makefile emacs23 -batch -l ./load-path.hack \ -f batch-byte-compile mailcrypt.el Loading /etc/emacs/site-start.d/00debian-vars.el (source)... Loading /etc/emacs/site-start.d/20apel.el (source)... Loading /etc/emacs/site-start.d/50autoconf.el (source)... Loading /etc/emacs/site-start.d/50bashdb.el (source)... Loading /etc/emacs/site-start.d/50bbdb.el (source)... Loading /etc/emacs/site-start.d/50cmake-data.el (source)... Loading /etc/emacs/site-start.d/50css-mode.el (source)... Loading /etc/emacs/site-start.d/50devscripts-el.el (source)... Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)... Loading debian-ispell... Loading /var/cache/dictionaries-common/emacsen-ispell-default.el (source)... Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)... Loading
Bug#694048: havoc and distruption ^_^
On 02.12.2012 22:04, Salvo Tomaselli wrote: if start-stop-daemon -K --retry=TERM/30/KILL/5 -o -q -p $PIDFILE -x $DAEMON -u $USER; then Okay, it seems to be working now, but also seemed to be working in general, the problem doesn't occur every time... that's the nature of race conditions :-) Some explanation why you see different behaviour between sysvinit and systemd: systemd internally translates restart to stop + start, i.e. it calls /etc/init.d/foo stop /etc/init.d/foo start. That's why the sleep 1 hack is only active under sysvinit. I bet, if you removed the sleep 1 in restart), you'd run into the same problem under sysvinit. In the end, those are just bugs in the sysv init scripts which are papered over by sprinkling a sleep here and there. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#694947: bind9: package upgrade overwrites gid owner of /etc/bind/named.conf.local
tags 694947 +moreinfo
thank you
Hi Paul,
On Sun, Dec 2, 2012 at 3:30 PM, Paul Witt paul.w...@oxix.org wrote:
Package: bind9
Version: 1:9.7.3.dfsg-1~squeeze8
Severity: normal
After a recent bind9 security upgrade (and probably after previous
upgrades too), our config management system reported that
/etc/bind/named.conf.local had had its group owner changed from
the one we'd configured to the group bind. Presumably it was
the package upgrade that caused this.
I have just tried the upgrade in clean pbuilder and the changed
permissions were kept during the upgrade.
The chgrp happens only on a condition where rndc.key has root as an
owner (which I presume is to detect first installation) and only in
that case the inital permissions are setup. See the snipet from
postinst script:
uid=$(ls -ln /etc/bind/rndc.key | awk '{print $3}')
if [ $uid = 0 ]; then
[ -n $localconf ] || chown bind /etc/bind/rndc.key
chgrp bind /etc/bind
chmod g+s /etc/bind
chgrp bind /etc/bind/rndc.key /var/run/named /var/cache/bind
chgrp bind /etc/bind/named.conf* || true
chmod g+r /etc/bind/rndc.key /etc/bind/named.conf* || true
chmod g+rwx /var/run/named /var/cache/bind
fi
Is there a change that your rndc key was owned by the root user?
Ondrej
--
Ondřej Surý ond...@sury.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688100: unblock: fglrx-driver/1:12-6+point-3
On 2012-12-02 21:37, Michael Gilbert wrote:
The package in wheezy contains incorrect (outdated) information w.r.t.
to support for legacy hardware (as it was written before AMD released
the beta driver) and is therefore misleading the users on upgrades.
There are also some (partial) upgrade issues with the 32-bit stuff on amd64
Could you implement those fixes as a minimal tpu?
I don't see any non-documentation change that would be worth stripping
out from -2/-3 without reintroducing some bug.
Perhaps the Built-Using addition, but that only affects the fglrx-source
package which will only be used by a minority of the fglrx users. And
the same code is used in the nvidia packages in wheezy as well.
Andreas
PS: I just noticed filterdiff --exclude *.po* also excluded this chunk:
--- debian/fglrx-driver.postrm (.../12-6+point-1) (revision 1132)
+++ debian/fglrx-driver.postrm (.../1:12-6+point-3)(revision 1132)
@@ -6,7 +6,7 @@
warn_about_remaining_xorg_configuration()
{
# allow to disable the check via preseeding
- db_get fglrx-driver/check-xorg-conf-on-removal
+ db_get fglrx-driver/check-xorg-conf-on-removal || true
test $RET = true || return 0
XORG_CONF=$(grep -l '^[^#]*fglrx' /etc/X11/xorg.conf
/etc/X11/xorg.conf.d/*.conf 2/dev/null || true)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685256: icedove: No way to add RSS feed account
Hello Manuel, yes it's a little bit tricky in current versions because Mozilla removed the name RSS from the menu. I used http://kb.mozillazine.org/Thunderbird_:_FAQs_:_RSS_Basics and had success with version 10.0.11. The trick is to take Blog News Feed in Step 2 of the manual. If you follow the rest of this tutorial you will get your desired RSS Feed into icedove. Regards Carsten On Sat, Aug 18, 2012 at 11:07:17PM +0200, Manuel Bilderbeek wrote: Package: icedove Version: 10.0.5-1 Severity: important Dear Maintainer, * What led up to the situation? I started to want to read RSS feeds as if it were e-mails, so I wanted to add RSS feeds to IceDove. I found out that this is one of its features. However: * What exactly did you do (or not do) that was effective (or ineffective)? There is no single way I can find to add RSS feeds to IceDove (without installing separate RSS extensions at least). I tried: Edit - Account Settings - Account Actions - Add Other Account. * What was the outcome of this action? It gives a dialog to enter my name and e-mail addres. Then I click Next and get a dialog to enter a News server. So, Other Account is only a news account? * What outcome did you expect instead? I would have expected to be able to add RSS feeds with some kind of RSS account or something. As accounts appear in the stuff in the left pane and there I would like to see the RSS feeds showing how many unread items there are. But, as I described, I was not able to... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671437: src:zlib: Please support building mingw-w64 packages
control: unarchive -1 control: reopen -1 Re-opening since it would be quite useful to have zlib mingw in the archive. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642750: [PATCH] epiphany-browser: *HIGHLY* unstable on ia64, (IA-64/IPF/Itanium) platform
The proposed patch defines a third option USE(JSVALUE64W) which we use *only* on ia64. It uses an encapsulated union without any trick for the variant data type. This is portable but - the data type is 128-bits wide, - Enabling JIT compiler isn't possible - that's not that bad; ia64 doesn't have a JIT compiler. Is the type in question purely internal to webkit or is it also used by client applications? If the latter then presumablly a soname bump and hence a transition would be needed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
