Bug#500623: dosfstools: full-disk description confusing
Package: dosfstools
Version: 2.11-8
Severity: minor
Tags: patch
A coworker was asking me for help w/ mkdosfs today - wondering what this
error message meant:
gpark4:~ # mkdosfs /dev/sdc
mkdosfs 2.11 (12 Mar 2005)
mkdosfs: Will not try to make filesystem on full-disk device '/dev/sdc' (use -I
if wanted)
And frankly, I wasn't sure either because I read full as non-empty.
After reading the manpage, it was pretty clear that the meaning of full
that was intended was a synonym for entire. This patch simply changes
some wording to make the intended meaning more obvious (to me, at least).
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: ia64
Kernel: Linux 2.6.26-1-mckinley (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages dosfstools depends on:
ii libc6.1 2.7-13 GNU C Library: Shared libraries
dosfstools recommends no packages.
dosfstools suggests no packages.
-- no debconf information
diff -urpN dosfstools-3.0.0.orig/man/mkdosfs.8 dosfstools-3.0.0/man/mkdosfs.8
--- dosfstools-3.0.0.orig/man/mkdosfs.8 2008-09-27 03:31:53.0 -0600
+++ dosfstools-3.0.0/man/mkdosfs.8 2008-09-29 13:41:52.0 -0600
@@ -141,7 +141,8 @@ is a 32-bit hexadecimal number (for exam
is a number which depends on the file system creation time.
.TP
.B \-I
-Normally you are not allowed to use any 'full' fixed disk devices.
+It is typical for fixed disk devices to be partitioned so, by default, you are
+not permitted to create a filesystem across the entire device.
.B mkdosfs
will complain and tell you that it refuses to work. This is different
when using MO disks. One doesn't always need partitions on MO disks.
diff -urpN dosfstools-3.0.0.orig/src/mkdosfs.c dosfstools-3.0.0/src/mkdosfs.c
--- dosfstools-3.0.0.orig/src/mkdosfs.c 2008-09-28 03:22:09.0 -0600
+++ dosfstools-3.0.0/src/mkdosfs.c 2008-09-29 13:40:20.0 -0600
@@ -1711,7 +1711,7 @@ main (int argc, char **argv)
(statbuf.st_rdev 0xff3f) == 0x0d00 || /* xd */
(statbuf.st_rdev 0xff3f) == 0x1600 ) /* hdc, hdd */
)
- die (Will not try to make filesystem on full-disk device '%s' (use -I if wanted));
+ die (Device partition expected, not making filesystem on entire device '%s' (use -I to override));
if (sector_size_set)
{
Bug#500631: linux-image-2.6.26-1-amd64: Fails in postinst with grub2: no such file /sbin/update-grub
reassign 500631 grub-pc thanks On Mon, Sep 29, 2008 at 11:10:02PM +0200, Naha wrote: Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-5 Severity: important With grub-pc, /sbin/update-grub does not exist any more, but it seems that the postinst script need it (see the reinstall log at the end of this mail). Fixed by symlinking /usr/sbin/update-grub to /sbin/update-grub. update-grub is call indirectly by the linux-image postinst, by way of the hooks in /etc/kernel-img.conf. These hooks are neither configured by nor maintained by the linux-image packages. /sbin/update-grub is marked as deprecated even in the 'grub' package (there's a NEWS.Debian file to warn users), so I suspect the answer is that users need to manually update their kernel-img.conf files. But, I'll reassign to grub-pc in case its maintainers have anything else to add. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500158: linux-image-2.6.26-1-486: Upgrade from Debian Etch to Debian Lenny may cause a kernel halt
On Thu, Sep 25, 2008 at 05:34:07PM +0100, Mark Hobley wrote: Package: linux-image-2.6.26-1-486 Version: 2.6.26-5 Severity: important As Debian is upgraded from Debian Etch to Debian Lenny, the kernel may halt with an error as the system is restarted: Booting the Kernel. BUG Int 6: CR2 EDI c0363f8c ESI 4000 EBP c0363f88 ESP c036f44 EBX EDX 0006 ECX EAX 4000 err EIP c0112b6f CS c0370060 flg 00010092 Stack: c0363f90 c0363f8c c0363f88 c0363f94 c0363f90 c0363f8c c0363f88 c037294f c0363f94 c0375293 03bef000 c03fea40 4000 005a29b7 c000 0009f000 03bef000 00d0 c03ba410 This was observed on an IBM compatible computer using a traditional Intel Pentium compatible processor. This is probably the same as #488022 - can you test that patch to verify? I've prepared a prebuilt image if you'd prefer to test that: http://people.debian.org/~dannf/bugs/500158 -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488022: linux-image-2.6.25-2-486: Does not boot on Vortex86SX (BUG: Int 6: CR2 00000000)
On Wed, Jul 30, 2008 at 12:49:38PM +, bruce robson wrote: I've now been running git. I started with git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.25.y.git I did a git bisect and found that the commit that introduced the bug is commit 94aa6550e8668fab1997e2d57a48b22cf68090b2 Author: Thomas Gleixner Date: Tue May 13 12:31:00 2008 +0200 x86: distangle user disabled TSC from unstable upstream commit: 9ccc906c97e34fd91dc6aaf5b69b52d824386910 tsc_enabled is set to 0 from the command line switch notsc and from the mark_tsc_unstable code. Seperate those functionalities and replace tsc_enable with tsc_disable. This makes also the native_sched_clock() decision when to use TSC understandable. Preparatory patch to solve the sched_clock() issue on 32 bit. Signed-off-by: Thomas Gleixner Signed-off-by: Chris Wright This commit changes file arch/x86/kernel/tsc_32.c Great, thanks Bruce! Can you file a bug on bugzilla.kernel.org with this information and let us know the number so we can track it? -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499142: reassign/more info
reassign 499142 gij-4.3 found 499142 4.3.2-2 thanks Since java-gcj-compat is just a wrapper, I'm assuming gij-4.3 is a more appropriate target for this bug. I've found that this bug still does exist in 4.3.2-2, it just isn't 100% reproducible. It seems to always occur when building in a sid chroot with pbuilder - but, if I unpack the same pbuilder tarball on the same system and do a manual build within, it succeeds (same build-deps). Hopefully that means it will not be an issue for our buildds. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495674: what about systems w/o alsa userspace?
forcemerge 495674 498013 thanks These bugs look to be the same (as does #494104, but I'm too lazy to unarchive), so merging. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495674: what about non-alsa systems?
There seems to be an assumption here that this issue should be resolved by a blacklist in alsa-base... but what about systems w/o alsa-base? Servers that have no use for sound are also reporting this potentially frightening (albeit benign) error message, but are unlikely to have the alsa-base package installed. It seems to me that snd-pcsp should be blacklisted on all systems by default. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499458: [hppa] kernel no longer boots on an A500
Package: linux-2.6 Version: 2.6.26-6 Severity: serious This issue is related to CONFIG_PRINTK_TIME - disabling that config option is a workaround. This is probably the same issue kyle describes in his blog[1]. I'll test his patch[2] and, assuming it works, commit it for the next release. [1]http://kyle.mcmartin.ca/.plan/index.php/2008/09/07/config_printk_time-what-is-time/ [2]http://git.kernel.org/?p=linux/kernel/git/kyle/parisc-2.6.git;a=commitdiff;h=1a189c07f9f65305442d6e99efac9ac44f86bc04 -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483279: patch tested, issue persists
fyi, I tested a modified version of Philippe's patch, but the issue
persists. I'll attach the exact patch I used which fixes #480794 and
drops the '-v' option from the sed call, which isn't a valid option.
The following output demonstrates the still-incorrect symlink:
$ dpkg -c libswt3.2-gtk-java_3.2.2-6.0~rzr1dannf2_ia64.deb
drwxr-xr-x root/root 0 2008-09-18 15:32 ./
drwxr-xr-x root/root 0 2008-09-18 14:54 ./usr/
drwxr-xr-x root/root 0 2008-09-18 14:53 ./usr/lib/
drwxr-xr-x root/root 0 2008-09-18 14:54 ./usr/lib/java/
drwxr-xr-x root/root 0 2008-09-18 14:53 ./usr/lib/eclipse/
drwxr-xr-x root/root 0 2008-09-18 14:53 ./usr/lib/eclipse/plugins/
-rw-r--r-- root/root 1706588 2008-09-18 11:50
./usr/lib/eclipse/plugins/org.eclipse.swt.gtk.linux.ia64_3.2.2.R3_2_maintenance.jar
drwxr-xr-x root/root 0 2008-09-18 14:54 ./usr/share/
drwxr-xr-x root/root 0 2008-09-18 14:54 ./usr/share/doc/
drwxr-xr-x root/root 0 2008-09-18 14:54
./usr/share/doc/libswt3.2-gtk-java/
-rw-r--r-- root/root 15524 2008-09-17 23:16
./usr/share/doc/libswt3.2-gtk-java/copyright
-rw-r--r-- root/root 16717 2008-09-17 23:16
./usr/share/doc/libswt3.2-gtk-java/changelog.Debian.gz
lrwxrwxrwx root/root 0 2008-09-18 14:54 ./usr/lib/java/swt-gtk.jar -
swt3.2-gtk.jar
lrwxrwxrwx root/root 0 2008-09-18 14:54 ./usr/lib/java/swt.jar -
swt3.2-gtk.jar
lrwxrwxrwx root/root 0 2008-09-18 14:54 ./usr/lib/java/swt3.2-gtk.jar
- ../eclipse/plugins/org.eclipse.swt.gtk.linux.ia64_3.2.2.v3236.jar
--
dann frazier
diff -u eclipse-3.2.2/debian/rules eclipse-3.2.2/debian/rules
--- eclipse-3.2.2/debian/rules
+++ eclipse-3.2.2/debian/rules
@@ -1,7 +1,7 @@
#!/usr/bin/make -f
# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
+export DH_VERBOSE=1
DISTRIBUTION := $(shell lsb_release -is)
@@ -180,7 +180,7 @@
# eclipse-libswt-mozilla-profiles
- BUILD_DEPS += , libxul-dev
+ BUILD_DEPS += , iceape-dev
MOZILLA_DEP = $${shlibs:Depends}
MOZILLA_HOME = /usr/lib/mozilla
endif
@@ -339,6 +339,9 @@
dh_testdir
ifneq (,$(findstring _$(ECLIPSE_PLATFORM)_,$(ECLIPSE_UNOFFICIAL_PLATFORMS)))
+# Set release version also for unsupported arch
+ -find source-tree -type f -iname build.xml -exec \
+ sed --in-place s|\(property *name=\version.suffix\ *value=\${UPSTREAM_VERSION}.\).*\(\/.*\)|\1${REL}\2|g {} \;
## Nasty hack to get support for ppc64, s390{,x}, sparc{,64} and hppa
# there is only partial support for ppc64 in 3.2 so we have to remove this
# partial support to get the replacemnt hack to work
diff -u eclipse-3.2.2/debian/control eclipse-3.2.2/debian/control
--- eclipse-3.2.2/debian/control
+++ eclipse-3.2.2/debian/control
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Debian Java Maintainers [EMAIL PROTECTED]
Uploaders: Jerry Haltom [EMAIL PROTECTED], Michael Koch [EMAIL PROTECTED], Matthias Klose [EMAIL PROTECTED], Stephan Michels [EMAIL PROTECTED]
-Build-Depends: debhelper ( 4.2), dpatch (= 2.0), lsb-release, bzip2, zip, sharutils, default-jdk-builddep, liblucene-java (= 1.4.2), liblucene-java-doc (= 1.4.2), junit (= 3.8), junit4, libjsch-java (= 0.1.36), libgtk2.0-dev (= 2.4), libgnome2-dev (= 2.6), libgnomeui-dev (= 2.6), libxtst-dev, libgl1-mesa-dev, libglu1-mesa-dev, classpath-doc, pkg-config, libcairo2-dev, ant-optional (= 1.6.5-3), libtomcat5.5-java, libxul-dev
+Build-Depends: debhelper ( 4.2), dpatch (= 2.0), lsb-release, bzip2, zip, sharutils, default-jdk-builddep, liblucene-java (= 1.4.2), liblucene-java-doc (= 1.4.2), junit (= 3.8), junit4, libjsch-java (= 0.1.36), libgtk2.0-dev (= 2.4), libgnome2-dev (= 2.6), libgnomeui-dev (= 2.6), libxtst-dev, libgl1-mesa-dev, libglu1-mesa-dev, classpath-doc, pkg-config, libcairo2-dev, ant-optional (= 1.6.5-3), libtomcat5.5-java, iceape-dev
Standards-Version: 3.7.3
Vcs-Svn: svn://svn.debian.org/svn/pkg-java/trunk/eclipse
Vcs-Browser: http://svn.debian.org/wsvn/pkg-java/trunk/eclipse
diff -u eclipse-3.2.2/debian/changelog eclipse-3.2.2/debian/changelog
--- eclipse-3.2.2/debian/changelog
+++ eclipse-3.2.2/debian/changelog
@@ -1,3 +1,20 @@
+eclipse (3.2.2-6.0~rzr1dannf2) dannf; urgency=low
+
+ * Fix sed syntax in swt jar rename fix (sed has no -v option)
+
+ -- dann frazier [EMAIL PROTECTED] Tue, 16 Sep 2008 16:23:29 +
+
+eclipse (3.2.2-6.0~rzr1dannf1) unstable; urgency=low
+
+ [ Philippe Coval ]
+ * Non-maintainer upload.
+ * WIP: Rename swt jar for ia64 arch. Closes #483279
+
+ [ dann frazier ]
+ * Build-dep on iceape-dev instead of libxul-dev
+
+ -- dann frazier [EMAIL PROTECTED] Wed, 10 Sep 2008 21:27:01 -0600
+
eclipse (3.2.2-6) unstable; urgency=low
* Suppress warnings from javac.
diff -u eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch
--- eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch
+++ eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch
@@ -41,9 +41,9
Bug#410817: Upstream fix in 2.6.26?
On Thu, Sep 18, 2008 at 12:09:00AM +0100, Simon Waters wrote: http://bugzilla.kernel.org/show_bug.cgi?id=6695 2.6.26 is in lenny/sid - can someone test it to confirm? -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499142: [ia64] hangs while building eclipse
Package: java-gcj-compat Version: 1.0.78-2 Severity: important eclipse fails to build with this version of java-gcj-compat. It hangs while running the following command: /usr/lib/jvm/java-1.5.0-gcj-4.3-1.5.0.0/jre/bin/java -jar /tmp/buildd/eclipse-3.2.2/source-tree/eclipse/startup.jar -data /tmp/buildd/eclipse-3.2.2/source-tree/workspace -application org.eclipse.ant.core.antRunner build.update.jar -Dplugin.destination=/tmp/buildd/eclipse-3.2.2/source-tree/tmp/eclipse/plugins strace shows that this process is blocked here: [EMAIL PROTECTED]:~$ sudo strace -p 28410 Process 28410 attached - interrupt to quit msgrcv(1277955, This has been hung on my system for several days, and happens everytime. Downgrading to 1.0.77-4 works fine. I'm currently testing other versions from snapshot to try and narrow down where the regression was introduced. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499142: working eclipse source package
fyi, eclipse currently FTBFS in sid due to #480794. I've prepared a test package w/ the fix for this issue as described in that bug report, available here: http://people.debian.org/~dannf/bugs/499142/ (It also includes the patch in #483279, which is what I'm trying to validate in the first place) -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480794: patch
tag 480794 + patch thanks I created a patch based on Michael's description. Seems to work fine for me. -- dann frazier diff -u eclipse-3.2.2/debian/control eclipse-3.2.2/debian/control --- eclipse-3.2.2/debian/control +++ eclipse-3.2.2/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Uploaders: Jerry Haltom [EMAIL PROTECTED], Michael Koch [EMAIL PROTECTED], Matthias Klose [EMAIL PROTECTED], Stephan Michels [EMAIL PROTECTED] -Build-Depends: debhelper ( 4.2), dpatch (= 2.0), lsb-release, bzip2, zip, sharutils, default-jdk-builddep, liblucene-java (= 1.4.2), liblucene-java-doc (= 1.4.2), junit (= 3.8), junit4, libjsch-java (= 0.1.36), libgtk2.0-dev (= 2.4), libgnome2-dev (= 2.6), libgnomeui-dev (= 2.6), libxtst-dev, libgl1-mesa-dev, libglu1-mesa-dev, classpath-doc, pkg-config, libcairo2-dev, ant-optional (= 1.6.5-3), libtomcat5.5-java, libxul-dev +Build-Depends: debhelper ( 4.2), dpatch (= 2.0), lsb-release, bzip2, zip, sharutils, default-jdk-builddep, liblucene-java (= 1.4.2), liblucene-java-doc (= 1.4.2), junit (= 3.8), junit4, libjsch-java (= 0.1.36), libgtk2.0-dev (= 2.4), libgnome2-dev (= 2.6), libgnomeui-dev (= 2.6), libxtst-dev, libgl1-mesa-dev, libglu1-mesa-dev, pkg-config, libcairo2-dev, ant-optional (= 1.6.5-3), libtomcat5.5-java, iceape-dev, libgl1-mesa-dev Standards-Version: 3.7.3 Vcs-Svn: svn://svn.debian.org/svn/pkg-java/trunk/eclipse Vcs-Browser: http://svn.debian.org/wsvn/pkg-java/trunk/eclipse diff -u eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch --- eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch +++ eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch @@ -41,9 +41,9 @@ - if [ x`pkg-config --exists mozilla-xpcom echo YES` = xYES ]; then - GECKO_INCLUDES=`pkg-config --cflags mozilla-xpcom` - GECKO_LIBS=`pkg-config --libs mozilla-xpcom` -+ if [ x`pkg-config --exists xulrunner-xpcom echo YES` = xYES ]; then -+ GECKO_INCLUDES=`pkg-config --cflags xulrunner-xpcom` -+ GECKO_LIBS=`pkg-config --libs xulrunner-xpcom` ++ if [ x`pkg-config --exists iceape-xpcom echo YES` = xYES ]; then ++ GECKO_INCLUDES=`pkg-config --cflags iceape-xpcom` ++ GECKO_LIBS=`pkg-config --libs iceape-xpcom` export GECKO_INCLUDES export GECKO_LIBS MAKE_MOZILLA=make_mozilla
Bug#480794: patch correction
Oops - didn't notice that the control file is generated. Updated patch
attached.
--
dann frazier
diff -u eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch
--- eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch
+++ eclipse-3.2.2/debian/patches/eclipse-libswt-xulrunner.dpatch
@@ -41,9 +41,9 @@
- if [ x`pkg-config --exists mozilla-xpcom echo YES` = xYES ]; then
- GECKO_INCLUDES=`pkg-config --cflags mozilla-xpcom`
- GECKO_LIBS=`pkg-config --libs mozilla-xpcom`
-+ if [ x`pkg-config --exists xulrunner-xpcom echo YES` = xYES ]; then
-+ GECKO_INCLUDES=`pkg-config --cflags xulrunner-xpcom`
-+ GECKO_LIBS=`pkg-config --libs xulrunner-xpcom`
++ if [ x`pkg-config --exists iceape-xpcom echo YES` = xYES ]; then
++ GECKO_INCLUDES=`pkg-config --cflags iceape-xpcom`
++ GECKO_LIBS=`pkg-config --libs iceape-xpcom`
export GECKO_INCLUDES
export GECKO_LIBS
MAKE_MOZILLA=make_mozilla
--- eclipse-3.2.2/debian/rules 2008-09-16 10:04:58.0 -0600
+++ eclipse-3.2.2/debian/rules 2008-09-16 10:26:38.0 -0600
@@ -180,7 +180,7 @@
# eclipse-libswt-mozilla-profiles
- BUILD_DEPS += , libxul-dev
+ BUILD_DEPS += , iceape-dev
MOZILLA_DEP = $${shlibs:Depends}
MOZILLA_HOME = /usr/lib/mozilla
endif
Bug#499142: narrowed down version
hmm.. now that I realize this is just a wrapper package, the bug makes less sense. Perhaps one of the backend packages got upgraded recently, fixing this issue? Will continue to look into it and follow up with results. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498899: postfix update FTBFS on mipsel
On Tue, Sep 16, 2008 at 09:12:16AM +0200, Thijs Kinkhorst wrote: On Tuesday 16 September 2008 04:38, dann frazier wrote: fyi, just filed this bug: ? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499075 The mipsel buildd has retried numerous times, so I don't believe this is a transient failure. We are aware; we retried ourselves and I contacted LaMont, who thinks it's a buildd misconfiguration. I have contacted the mipsel buildd maintainers but received not even an acknowledgement of my email. If you think the security team can do anything more about this please let me know. I don't, or I would've done it :) phil asked me to file the bug and I just wanted to keep the team informed. I also tried contacting the mipsel buildd maintainer (no response yet). -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496500: [Yaird-devel] Bug#496500: yaird: fails to create initrd when running 2.6.24 etchnhalf kernel
On Fri, Aug 29, 2008 at 11:51:38AM +0200, Jonas Smedegaard wrote: On Tue, Aug 26, 2008 at 10:33:00PM +0200, maximilian attems wrote: On Mon, 25 Aug 2008, Jonas Smedegaard wrote: +1021_new-style_firewire.patch etch+half kernel has old ieee1394, no need for that one. Thanks for your concern, Max. I will wait for a response from security or release team before working more on this. Jonas, Your patch (w/o the firewire changes, as Maks points out), looks good to me. Please go ahead and upload to stable. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498309: xfs filesystem corruption due to attr2 bug
On Thu, Sep 11, 2008 at 11:40:07AM +0200, Ralf Gross wrote: dann frazier schrieb: On Tue, Sep 09, 2008 at 12:02:41AM +0200, Ralf Gross wrote: Package: linux-image-2.6-amd64 Version: 2.6.18+6etch3 I've lost 2 xfs filesystems this weekend after adding lots of acls to many files. With some help from the people of the xfs IRC channel, I could nail it down to a problem with xfs an attr2. It seems that the debian 2.6.18 kernel is missing a very important bugfix. The bug report originally comes from red hat: https://bugzilla.redhat.com/show_bug.cgi?id=212201 This is what I found in the archibes of the xfs mailing list: http://www.linux.sgi.com/archives/xfs/2006-12/msg00104.html The filesystems that crashed had a size of 2 TB and 6 TB. xfs_repair couldn't help much. In the end I had to restore the data from the last backup. I know that packages in the stable release are only updated with important (security) fixes. But this bug can (did) cause data loss and would be worth a fix. Thanks for the report. Fixes for = important bugs are acceptable in a stable release. I've committed a fix for this which should appear in the etch snapshot builds[1] tomorrow. Would you be able to test that build on your system? I'm not sure whether you are using the i386 port or the amd64 port (the amd64 flavor is available for both). If you're using the i386 port, you should be able to grab a snapshot build with a version = 2.6.18.dfsg.1-23~snapshot.12203. If you're using amd64, you can try the test build I posted here: http://people.debian.org/~dannf/bugs/498309/ [1] http://wiki.debian.org/DebianKernel I've some problems in installing the appr. header files, maybe I'm doing something wrong: I downloaded linux-headers-2.6.18-6_2.6.18.dfsg.1-23~bug498309_amd64.deb linux-headers-2.6.18-6-all-amd64_2.6.18.dfsg.1-23~bug498309_amd64.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-23~bug498309_amd64.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-23~bug498309_amd64.deb You probably just want the headers for your flavor. If you're not running xen/vserver, you just need linux-headers-2.6.18-6-amd64 and linux-headers-2.6.18-6, not the all packages. You should be able to clean up your system with: # apt-get -f install And try again. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498548: linux-image-2.6.26-1-686: SKB BUG: Invalid truesize
On Thu, Sep 11, 2008 at 03:11:20PM -0300, Emiliano Castagnari wrote: On Wed, Sep 10, 2008 at 11:53 PM, dann frazier [EMAIL PROTECTED] wrote: yeah, that patch went in years ago. This is a more current report, but might not be the same thing: http://marc.info/?l=linux-netdevm=121674755618486w=2 Your best bet maybe to file a bug upstream at http://bugzilla.kernel.org. Did this start occuring after a kernel upgrade? If so, you might be able to help find the problem by bisecting - see http://wiki.debian.org/DebianKernelReportingBugs for more information. Now that you mention it, I tried 2.6.25-2-686 also, and the problem remains. The issue resembles the one you posted, but nomater which kernel I boot with (2.6.25 or 2.6.26) the message still apears. I will give it a try with sid, an let you know about any news. Thanks for the help Can you try the 2.6.24 etchnhalf kernel? If that doesn't demonstrate the problem, then you could bisect between 2.6.24 and 2.6.25. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497559: josm: honor $http_proxy
On Wed, Sep 10, 2008 at 08:53:09PM +0200, Andreas Putzo wrote: Hi, On Sep 02 10:15, dann frazier wrote: The jre provided by openjdk-6-jre (and possibly others) doesn't honor the http_proxy environment variable. When I'm behind a proxy, that means I need to type something like this: /usr/lib/jvm/java-6-openjdk/bin/java -Dhttp.proxyHost=192.168.1.1 -Dhttp.proxyPort=3128 -jar /usr/share/josm/josm.jar It would be nice if the /usr/bin/josm script detected an http_proxy environment variable and automatically added the necessary arguments to the java command line for me. I don't think this is something we should fix in the josm wrapper script because this problem affects every java application that somehow tries to access the network. But openjdk-6 allows to define system-wide proxy settings in /etc/java6-openjdk/net.properties. There's also a property java.net.useSystemProxies which i was told works with the gnome proxy settings but unfortunately not with $http_proxy. We can probably improve the josm wrapper to use the environment variable $JAVA_OPTS to customize the behaviour of the jvm, like defining proxy or memory settings. Ah, that makes sense. Thanks for the suggestions! -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489414: patch
tags 489414 + patch found 489414 3.10+nmu1 kthxbye This issue appears to have been introduced by 3.11, in the fix for #489414. Since it appears that the entire purpose of bootcd-ia64 is to provide this file (and pull in the dependencies it requires), it looks like the correct fix is to drop the bootcd-ia64.lib from bootcd and only ship it in bootcd-ia64. patch attached. -- dann frazier diff -Nru bootcd-3.11/debian/bootcd.install bootcd-3.12/debian/bootcd.install --- bootcd-3.11/debian/bootcd.install 2007-11-30 05:37:38.0 -0700 +++ bootcd-3.12/debian/bootcd.install 2008-09-10 19:31:59.0 -0600 @@ -3,7 +3,6 @@ usr/share/bootcd/bootcd-check.lib usr/share/bootcd/bootcd2disk.conf usr/share/bootcd/default.txt -usr/share/bootcd/bootcd-ia64.lib usr/share/bootcd/bootcd2disk usr/share/bootcd/bootcdflopcp usr/share/bootcd/S13bootcdflop.sh diff -Nru bootcd-3.11/debian/changelog bootcd-3.12/debian/changelog --- bootcd-3.11/debian/changelog 2008-07-29 03:08:01.0 -0600 +++ bootcd-3.12/debian/changelog 2008-09-10 19:32:51.0 -0600 @@ -1,3 +1,9 @@ +bootcd (3.12) UNRELEASED; urgency=low + + * Remove bootcd-ia64.lib from bootcd binary to avoid conflict + + -- dann frazier [EMAIL PROTECTED] Wed, 10 Sep 2008 19:32:05 -0600 + bootcd (3.11) unstable; urgency=low * the bootcd-ia64.lib is now in bootcd-ia64. This bug was reported by
Bug#489414: notfound 489414 in 3.11
# Automatically generated email from bts, devscripts version 2.10.35 # oops - wrong bug notfound 489414 3.11 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489414: redoning
Version: 3.11 Sorry - been updating the wrong report :( Those were meant for #497459 -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497459: patch
tags 497459 + patch found 497459 3.11 notfound 497459 3.10+nmu1 kthxbye This issue appears to have been introduced by 3.11, in the fix for #489414. Since it appears that the entire purpose of bootcd-ia64 is to provide this file (and pull in the dependencies it requires), it looks like the correct fix is to drop the bootcd-ia64.lib from bootcd and only ship it in bootcd-ia64. patch attached. -- dann frazier diff -Nru bootcd-3.11/debian/bootcd.install bootcd-3.12/debian/bootcd.install --- bootcd-3.11/debian/bootcd.install 2007-11-30 05:37:38.0 -0700 +++ bootcd-3.12/debian/bootcd.install 2008-09-10 19:31:59.0 -0600 @@ -3,7 +3,6 @@ usr/share/bootcd/bootcd-check.lib usr/share/bootcd/bootcd2disk.conf usr/share/bootcd/default.txt -usr/share/bootcd/bootcd-ia64.lib usr/share/bootcd/bootcd2disk usr/share/bootcd/bootcdflopcp usr/share/bootcd/S13bootcdflop.sh diff -Nru bootcd-3.11/debian/changelog bootcd-3.12/debian/changelog --- bootcd-3.11/debian/changelog 2008-07-29 03:08:01.0 -0600 +++ bootcd-3.12/debian/changelog 2008-09-10 19:32:51.0 -0600 @@ -1,3 +1,9 @@ +bootcd (3.12) UNRELEASED; urgency=low + + * Remove bootcd-ia64.lib from bootcd binary to avoid conflict + + -- dann frazier [EMAIL PROTECTED] Wed, 10 Sep 2008 19:32:05 -0600 + bootcd (3.11) unstable; urgency=low * the bootcd-ia64.lib is now in bootcd-ia64. This bug was reported by
Bug#498548: linux-image-2.6.26-1-686: SKB BUG: Invalid truesize
On Wed, Sep 10, 2008 at 09:30:43PM -0400, Emiliano Castagnari wrote: Package: linux-image-2.6.26-1-686 Version: 2.6.26-4 Severity: important I am getting this kernel messages at least 9 times per second. I belive there is a patch to this problem, I dont know if it is already aplied in the current package. http://marc.info/?l=linux-netdevm=116284186427122w=2 yeah, that patch went in years ago. This is a more current report, but might not be the same thing: http://marc.info/?l=linux-netdevm=121674755618486w=2 Your best bet maybe to file a bug upstream at http://bugzilla.kernel.org. Did this start occuring after a kernel upgrade? If so, you might be able to help find the problem by bisecting - see http://wiki.debian.org/DebianKernelReportingBugs for more information. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#498309: xfs filesystem corruption due to attr2 bug
On Tue, Sep 09, 2008 at 12:02:41AM +0200, Ralf Gross wrote: Package: linux-image-2.6-amd64 Version: 2.6.18+6etch3 I've lost 2 xfs filesystems this weekend after adding lots of acls to many files. With some help from the people of the xfs IRC channel, I could nail it down to a problem with xfs an attr2. It seems that the debian 2.6.18 kernel is missing a very important bugfix. The bug report originally comes from red hat: https://bugzilla.redhat.com/show_bug.cgi?id=212201 This is what I found in the archibes of the xfs mailing list: http://www.linux.sgi.com/archives/xfs/2006-12/msg00104.html The filesystems that crashed had a size of 2 TB and 6 TB. xfs_repair couldn't help much. In the end I had to restore the data from the last backup. I know that packages in the stable release are only updated with important (security) fixes. But this bug can (did) cause data loss and would be worth a fix. Thanks for the report. Fixes for = important bugs are acceptable in a stable release. I've committed a fix for this which should appear in the etch snapshot builds[1] tomorrow. Would you be able to test that build on your system? I'm not sure whether you are using the i386 port or the amd64 port (the amd64 flavor is available for both). If you're using the i386 port, you should be able to grab a snapshot build with a version = 2.6.18.dfsg.1-23~snapshot.12203. If you're using amd64, you can try the test build I posted here: http://people.debian.org/~dannf/bugs/498309/ [1] http://wiki.debian.org/DebianKernel -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497747: bugs.debian.org: spam reporting link broken
Package: bugs.debian.org Severity: important I went to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409806 and clicked the this bug log contains spam link, which directed me to: http://bugs.debian.org/cgi-bin/bugs.debian.org/cgi-bin/bugspam.cgi Which is a 404 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: ia64 Kernel: Linux 2.6.25-2-mckinley (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497559: josm: honor $http_proxy
Package: josm Version: 0.0.0.20080713-1 Severity: wishlist The jre provided by openjdk-6-jre (and possibly others) doesn't honor the http_proxy environment variable. When I'm behind a proxy, that means I need to type something like this: /usr/lib/jvm/java-6-openjdk/bin/java -Dhttp.proxyHost=192.168.1.1 -Dhttp.proxyPort=3128 -jar /usr/share/josm/josm.jar It would be nice if the /usr/bin/josm script detected an http_proxy environment variable and automatically added the necessary arguments to the java command line for me. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: ia64 Kernel: Linux 2.6.25-2-mckinley (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages josm depends on: ii libgettext-commons-ja 0.9-1 Java classes for internationalizat ii libmetadata-extractor 2.3.1+dfsg-1 JPEG metadata extraction framework ii openjdk-6-jre 6b11-6 OpenJDK Java runtime, using Hotspo ii openstreetmap-map-ico 1:0.0.0.20080713-1 Collection of map icons Versions of packages josm recommends: ii josm-plugins0.0.0.20080413-2 Plugins for JOSM josm suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496903: linux-image-2.6.26-1-686: crashes when 6710b lid closed
On Thu, Aug 28, 2008 at 11:17:39PM +1000, Neale Banks wrote: Package: linux-image-2.6.26-1-686 Version: 2.6.26-3 Running linux-image-2.6.26-1-686_2.6.26-3_i386 on a HP/Compaq 6710b (GY306PS), the kernel crashes after shutting the lid (it may take a minute or so) and the system keyboard is non-responsive (not even caps-lock woring). This has also been observed on linux-image-2.6.25-2-686_2.6.25-7 and linux-image-2.6.26-1-686_2.6.26-1. Recovery is to hold down the power button till the system powers off, then cold-boot. Details captured via netconsole: This sounds like #493946, can you confirm? -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497084: linux-image-2.6.26-1-mckinley: Fails to boot on a HP Integrity Virtual Machines 3.0 or 3.5 system
Version: 2.6.26-4 On Fri, Aug 29, 2008 at 01:19:24PM -0600, Aaron D. Johnson wrote: Package: linux-image-2.6.26-1-mckinley Version: 2.6.26-3 Severity: normal linux-image-2.6.25-2-mckinley does boot normally on this platform. Known issue, fixed in 2.6.26-4 in unstable. Thanks for the report! -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492629: unable to reproduce
fyi, I tried to reproduce this on a fresh lenny/i386 install but was unable to duplicate - the gui started up fine for me. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496598: closed by Frans Pop [EMAIL PROTECTED] (Re: Bug#496598: fix for #494466 causes netinst to fail)
On Tue, Aug 26, 2008 at 06:51:03AM +, Debian Bug Tracking System wrote: Problem is a version mismatch between bootstrap-base (1.93) and base-installer (1.94). This is just the usual arch all versus arch any breakage one can expect in unstable. Will fix itself with next images. Cheers, FJP Indeed it did, thanks Frans! -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357145: closed by Daniel Baumann [EMAIL PROTECTED] (reply to [EMAIL PROTECTED]) (Re: Please build (at least a subset of) syslinux for all arches)
On Mon, Aug 25, 2008 at 02:36:03AM +, Daniel Baumann wrote: Hi, as explained in the last message from me to these reports, this wont happen, and since there is no value of having this three (doublicated reports) open and rotting with wontfix forever, I'm closing them now. Regards, Daniel hey Daniel, It looks like the message you refer to is this one: On Mon, 31 Mar 2008 21:54:11 +0200, Daniel Baumann wrote: Hi, this wont happen I think. First, it's not possible to build syslinux binaries (the bootloader modules) on anything different than amd64 and i386. This means, that there can't be an arch any sub packages only containing those binaries. Second, an arch all sub package only shipping the bootloader modules /could/ be done, but it could be only build on i386 or amd64. This contradicts policy and would really suck, so a no-go. Regards, Daniel This does appear to violate a should in policy. From section 5.6.8: Specifying any indicates that the source package isn't dependent on any particular architecture and should compile fine on any one. The produced binary package(s) will be specific to whatever the current build architecture is. Because this is a 'should' and not a 'must', I don't interpret this as being a strict policy violation. There is also existing precedence for this in several packages. palo, the hppa bootloader, is probably the most directly comparable situation. Though the hppa-code is only compiled on hppa systems, it is installable on all architectures. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496598: fix for #494466 causes netinst to fail
Package: base-installer Version: 1.94 Severity: serious hey, HP QA reported an issue with the most recent netinst builds for i386 and amd64. Their report follows: * New lenny builds of 24th Aug ??? both amd64 and i686 bit failed during installing the base system leading to installtion incomplete. SYSTEM CONFIGURATIONS: Server: BL480c and DL365G5 Operating System: Debian ??? Lenny amd64/i686 ??? netinstaller ??? 24th Aug Build Boot Controller: Smart Array P400i and E200i Network Controller: 373i STEPS TO REPRODUCE THE PROBLEM: 1. Select option - Install 2. Install the base system 3. After completing 79% of installation , the following error occurs The target file system contains files from a past installation. These files could cause problems with the installation process and if you proceed, some of the existing files may be overwritten. Proceed with installation to unclean target? Yes or No 4. When selected either, the step 2 restarts and the same error occurs when completes 79%. * I was able to reproduce this, and it appears to haev been introduced by the fix for #494466. I added 'set -x' into bootstrap-base postinst, and saw this[1] in syslog. To help verify, I retried the install w/ base-installer/initramfs-tools/driver-policy=most on the cmdline and the install completed w/o issue. [1] Aug 25 23:14:35 main-menu[1006]: (process:506): + break Aug 25 23:14:35 main-menu[1006]: (process:506): + [ initramfs-tools = initramfs-tools ] Aug 25 23:14:35 main-menu[1006]: (process:506): + db_get base-installer/initramfs-tools/driver-policy Aug 25 23:14:35 main-menu[1006]: (process:506): + _db_cmd GET base-installer/initramfs-tools/driver-policy Aug 25 23:14:35 main-menu[1006]: (process:506): + IFS= printf %s\n GET base-installer/initramfs-tools/driver-policy Aug 25 23:14:35 main-menu[1006]: (process:506): + IFS= Aug 25 23:14:35 main-menu[1006]: (process:506): read -r Aug 25 23:14:35 main-menu[1006]: _db_internal_line Aug 25 23:14:35 main-menu[1006]: (process:506): + RET=10 base-installer/initramfs-tools/driver-policy doesn't exist Aug 25 23:14:35 main-menu[1006]: (process:506): + return 10 Aug 25 23:14:35 main-menu[1006]: (process:506): + db_input medium base-installer/initramfs-tools/driver-policy Aug 25 23:14:35 main-menu[1006]: (process:506): + _db_cmd INPUT medium base-installer/initramfs-tools/driver-policy Aug 25 23:14:35 main-menu[1006]: (process:506): + IFS= printf %s\n INPUT medium base-installer/initramfs-tools/driver-policy Aug 25 23:14:35 main-menu[1006]: (process:506): + IFS= Aug 25 23:14:35 main-menu[1006]: (process:506): read -r _db_internal_line Aug 25 23:14:35 main-menu[1006]: (process:506): + RET=10 base-installer/initramfs-tools/driver-policy doesn't exist Aug 25 23:14:35 main-menu[1006]: (process:506): + return 10 Aug 25 23:14:35 main-menu[1006]: (process:506): + true Aug 25 23:14:35 main-menu[1006]: (process:506): + db_go Aug 25 23:14:35 main-menu[1006]: (process:506): + _db_cmd GO Aug 25 23:14:35 main-menu[1006]: (process:506): + IFS= printf %s\n GO Aug 25 23:14:35 main-menu[1006]: (process:506): + IFS= Aug 25 23:14:35 main-menu[1006]: (process:506): read -r _db_internal_line Aug 25 23:14:35 main-menu[1006]: (process:506): + RET=ok Aug 25 23:14:35 main-menu[1006]: (process:506): + return 0 Aug 25 23:14:35 main-menu[1006]: (process:506): + db_get base-installer/initramfs-tools/driver-policy Aug 25 23:14:35 main-menu[1006]: (process:506): + _db_cmd GET base-installer/initramfs-tools/driver-policy Aug 25 23:14:35 main-menu[1006]: (process:506): + IFS= printf %s\n GET base-installer/initramfs-tools/driver-policy Aug 25 23:14:35 main-menu[1006]: (process:506): + IFS= Aug 25 23:14:35 main-menu[1006]: (process:506): read -r _db_internal_line Aug 25 23:14:35 main-menu[1006]: (process:506): + RET=10 base-installer/initramfs-tools/driver-policy doesn't exist Aug 25 23:14:35 main-menu[1006]: (process:506): + return 10 Aug 25 23:14:35 main-menu[1006]: INFO: Menu item 'bootstrap-base' succeeded but requested to be left unconfigured. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495138: dpkg-dev: dpkg-source drops *.a files outside of debian/
Package: dpkg-dev Version: 1.14.20 Severity: important Between 1.14.16 and 1.14.17, dpkg-source appears to have started omitting .a files from native V1.0 format packages even outside of the debian/ directory. I didn't see anything in the 1.14.17 changelog that suggests this is intentional, and I haven't found a workaround for it. Here's an example to illustrate (mklibs chosen randomly): [EMAIL PROTECTED]:/tmp$ dpkg -l dpkg dpkg-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii dpkg 1.14.16package maintenance system for Debian ii dpkg-dev 1.14.16package building tools for Debian [EMAIL PROTECTED]:/tmp$ apt-get source mklibs Reading package lists... Done Building dependency tree Reading state information... Done Need to get 117kB of source archives. Get:1 http://mirrors.kernel.org sid/main mklibs 0.1.26 (dsc) [797B] Get:2 http://mirrors.kernel.org sid/main mklibs 0.1.26 (tar) [116kB] Fetched 117kB in 2s (52.6kB/s) dpkg-source: extracting mklibs in mklibs-0.1.26 dpkg-source: unpacking mklibs_0.1.26.tar.gz [EMAIL PROTECTED]:/tmp$ cd mklibs-0.1.26/ [EMAIL PROTECTED]:/tmp/mklibs-0.1.26$ echo test foo.a [EMAIL PROTECTED]:/tmp/mklibs-0.1.26$ dpkg-buildpackage -rfakeroot -uc -us -S dpkg-buildpackage: source package mklibs dpkg-buildpackage: source version 0.1.26 dpkg-buildpackage: source changed by Bastian Blank [EMAIL PROTECTED] fakeroot debian/rules clean dh_testdir rm -f *-stamp rm -rf build-* dh_clean dpkg-source -b mklibs-0.1.26 dpkg-source: building mklibs in mklibs_0.1.26.tar.gz dpkg-source: building mklibs in mklibs_0.1.26.dsc Use of uninitialized value $varlistfile in -e at /usr/bin/dpkg-source line 774. dpkg-genchanges -S ../mklibs_0.1.26_source.changes dpkg-genchanges: including full source code in upload dpkg-buildpackage: source only upload: Debian-native package [EMAIL PROTECTED]:/tmp/mklibs-0.1.26$ tar tfz ../mklibs_0.1.26.tar.gz | grep foo mklibs-0.1.26/foo.a [EMAIL PROTECTED]:/tmp/mklibs-0.1.26$ sudo dpkg -i /var/cache/apt/archives/dpkg-dev_1.14.17_all.deb /var/cache/apt/archives/dpkg_1.14.17_i386.deb (Reading database ... 182403 files and directories currently installed.) Preparing to replace dpkg-dev 1.14.16 (using .../dpkg-dev_1.14.17_all.deb) ... Unpacking replacement dpkg-dev ... Preparing to replace dpkg 1.14.16 (using .../archives/dpkg_1.14.17_i386.deb) ... Unpacking replacement dpkg ... Setting up dpkg (1.14.17) ... Installing new version of config file /etc/dpkg/dpkg.cfg ... Setting up dpkg-dev (1.14.17) ... [EMAIL PROTECTED]:/tmp/mklibs-0.1.26$ dpkg-buildpackage -rfakeroot -uc -us -Sdpkg-buildpackage: set CFLAGS to default value: -g -O2 dpkg-buildpackage: set CPPFLAGS to default value: dpkg-buildpackage: set LDFLAGS to default value: dpkg-buildpackage: set FFLAGS to default value: -g -O2 dpkg-buildpackage: set CXXFLAGS to default value: -g -O2 dpkg-buildpackage: source package mklibs dpkg-buildpackage: source version 0.1.26 dpkg-buildpackage: source changed by Bastian Blank [EMAIL PROTECTED] fakeroot debian/rules clean dh_testdir rm -f *-stamp rm -rf build-* dh_clean dpkg-source -b mklibs-0.1.26 dpkg-source: info: using source format `1.0' dpkg-source: info: building mklibs in mklibs_0.1.26.tar.gz dpkg-source: info: building mklibs in mklibs_0.1.26.dsc dpkg-genchanges -S ../mklibs_0.1.26_source.changes dpkg-genchanges: including full source code in upload dpkg-buildpackage: source only upload: Debian-native package [EMAIL PROTECTED]:/tmp/mklibs-0.1.26$ tar tfz ../mklibs_0.1.26.tar.gz | grep foo [EMAIL PROTECTED]:/tmp/mklibs-0.1.26$ -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: ia64 Kernel: Linux 2.6.25-2-mckinley (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages dpkg-dev depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-1 high-quality block-sorting file co ii cpio2.9-13 GNU cpio -- a program to manage ar ii dpkg1.14.20 Debian package management system ii libtimedate-perl1.1600-9 Time and date functions for Perl ii lzma4.43-14 Compression method of 7z format in ii make3.81-5 The GNU version of the make util ii patch 2.5.9-5 Apply a diff file to an original ii perl [perl5]5.10.0-12Larry Wall's Practical Extraction ii perl-modules5.10.0-12Core Perl modules Versions of packages dpkg-dev recommends:
Bug#493479: test build
hey Dave, I'm wondering if this is an occurrence of #494365. Can you test this build to see if it fixes this issue for you? http://people.debian.org/~dannf/bugs/494365/ -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494365: 2.6.26 hangs on opteron CPUs
On Fri, Aug 08, 2008 at 08:51:33PM +0200, Peter Palfrader wrote:
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-1
Severity: important
Hi,
it seems that 2.6.26 (whether the debian package or the kernel.org
kernel) locks up after a while on Debian's DL385G1 systems.
After a while, sooner with more disk IO/filesystem load, the system
hangs: it continues to do stuff but everything involving disk hangs
forever.
The systems work just fine on a 2.6.25.10 kernel.
The servers have Opterons like this:
cpu family : 15
model : 33
so http://www.uwsg.iu.edu/hypermail/linux/kernel/0808.0/0882.html might
explain it.
hey Peter,
This is readily reproducible - a simple kernel compile was all it
took. git bisecting suggests that this issue was introduced by [1]
and unmasked by [2] during 2.6.26 devlopment. It was later fixed
during 2.6.27 development by [3].
Can you confirm that the attached backport of [3] fixes the problem
for you?
[1] 35605a1027ac630f85a1b95684f7e86b82498cd6
[2] 8d539108560ec121d59eee05160236488266221c
[3] 8004dd965b13b01a96def054d420f6df7ff22d53
--
dann frazier
commit 8004dd965b13b01a96def054d420f6df7ff22d53
Author: Yinghai Lu [EMAIL PROTECTED]
Date: Mon May 12 17:40:39 2008 -0700
x86: amd opteron TOM2 mask val fix
there is a typo in the mask value, need to remove that extra 0,
to avoid 4bit clearing.
Signed-off-by: Yinghal Lu [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
Backported to Debian's 2.6.26 by dann frazier [EMAIL PROTECTED]
diff -urpN linux-source-2.6.26.orig/arch/x86/kernel/cpu/mtrr/generic.c
linux-source-2.6.26/arch/x86/kernel/cpu/mtrr/generic.c
--- linux-source-2.6.26.orig/arch/x86/kernel/cpu/mtrr/generic.c 2008-08-11
22:55:59.0 -0600
+++ linux-source-2.6.26/arch/x86/kernel/cpu/mtrr/generic.c 2008-08-11
22:57:13.0 -0600
@@ -219,7 +219,7 @@ void __init get_mtrr_state(void)
tom2 = hi;
tom2 = 32;
tom2 |= lo;
- tom2 = 0xff800ULL;
+ tom2 = 0xff80ULL;
}
if (mtrr_show) {
int high_width;
diff -urpN linux-source-2.6.26.orig/arch/x86/pci/k8-bus_64.c
linux-source-2.6.26/arch/x86/pci/k8-bus_64.c
--- linux-source-2.6.26.orig/arch/x86/pci/k8-bus_64.c 2008-08-11
22:55:59.0 -0600
+++ linux-source-2.6.26/arch/x86/pci/k8-bus_64.c2008-08-11
22:57:13.0 -0600
@@ -384,7 +384,7 @@ static int __init early_fill_mp_bus_info
/* need to take out [0, TOM) for RAM*/
address = MSR_K8_TOP_MEM1;
rdmsrl(address, val);
- end = (val 0xff800ULL);
+ end = (val 0xff80ULL);
printk(KERN_INFO TOM: %016lx aka %ldM\n, end, end20);
if (end (1ULL32))
update_range(range, 0, end - 1);
@@ -478,7 +478,7 @@ static int __init early_fill_mp_bus_info
/* TOP_MEM2 */
address = MSR_K8_TOP_MEM2;
rdmsrl(address, val);
- end = (val 0xff800ULL);
+ end = (val 0xff80ULL);
printk(KERN_INFO TOM2: %016lx aka %ldM\n, end, end20);
update_range(range, 1ULL32, end - 1);
}
Bug#493946: discover method fails to detect chip
On Wed, Aug 06, 2008 at 07:38:19AM +0200, Petter Reinholdtsen wrote: [Dann Frazier] I've only done blackbox testing so far, so I don't know the root issue here. Please provide the output from 'lspci -nn' on the machine in question. [EMAIL PROTECTED]:~$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c) 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03) 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03) 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03) 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 03) 00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 [8086:2843] (rev 03) 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 [8086:2847] (rev 03) 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 03) 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 03) 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 03) 00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 [8086:2836] (rev 03) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f3) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller [8086:2815] (rev 03) 00:1f.1 IDE interface [0101]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 03) 00:1f.2 SATA controller [0106]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller [8086:2829] (rev 03) 02:04.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b6) 02:04.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 02) 10:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG Network Connection [8086:4222] (rev 02) 18:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express [14e4:1693] (rev 02) I really wish it was possible to query the X server to get the driver it is going to use. :( Wouldn't that be nice.. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493946: discover method fails to detect chip
Package: hotkey-setup Version: 0.1-23 Severity: important I recently noticed that the solution implemented for #483200 isn't working on my Compaq 6510b. The xorg_driver function isn't detecting a driver on my system. My xorg.conf file doesn't have a driver line, so that probe fails. The fallback to using discover also fails, seemingly due to the --data-version argument. If --data-version is set to 7, as is hardcoded in the script, the discover command outputs no text. But, if I up this to 7.2, it begins to output 'intel'. I've only done blackbox testing so far, so I don't know the root issue here. [EMAIL PROTECTED]:~$ discover --data-path=xfree86/server/device/driver --data-version=7 display [EMAIL PROTECTED]:~$ discover --data-path=xfree86/server/device/driver --data-version=7.0 display [EMAIL PROTECTED]:~$ discover --data-path=xfree86/server/device/driver --data-version=7.1 display [EMAIL PROTECTED]:~$ discover --data-path=xfree86/server/device/driver --data-version=7.2 display intel intel -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493881: yelp: hang/segv browsing conduit docs
/lib/libc.so.6.1 No symbol table info available. #2 0x217ebb70 in abort () from /lib/libc.so.6.1 No symbol table info available. #3 0x211e5d80 in IA__g_assertion_message ( domain=0x4006b918 Yelp, file=0x4006f5a8 yelp-document.c, line=275, func=0x4006f890 yelp_document_cancel_page, message=0x61498a70 assertion failed: (document != NULL YELP_IS_DOCUMENT (document))) at /build/buildd/glib2.0-2.16.5/glib/gtestutils.c:1218 lstr = 275, '\0' repeats 28 times #4 0x211e67a0 in IA__g_assertion_message_expr ( domain=0x4006b918 Yelp, file=0x4006f5a8 yelp-document.c, line=275, func=0x4006f890 yelp_document_cancel_page, expr=0x4006f5b8 document != NULL YELP_IS_DOCUMENT (document)) at /build/buildd/glib2.0-2.16.5/glib/gtestutils.c:1229 No locals. #5 0x4003ca00 in ?? () No symbol table info available. Backtrace stopped: previous frame inner to this frame (corrupt stack?) -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: ia64 Kernel: Linux 2.6.25-2-mckinley (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages yelp depends on: ii docbook-xml4.5-5 standard XML documentation system, ii gconf2 2.22.0-1 GNOME configuration database syste ii gnome-doc-utils0.12.2-1 a collection of documentation util ii libbz2-1.0 1.0.5-0.1 high-quality block-sorting file co ii libc6.12.7-13GNU C Library: Shared libraries ii libdbus-glib-1-2 0.76-1simple interprocess messaging syst ii libgconf2-42.22.0-1 GNOME configuration database syste ii libglade2-01:2.6.2-1 library to load .glade files at ru ii libglib2.0-0 2.16.5-1 The GLib library of C routines ii libgnome2-02.20.1.1-1The GNOME 2 library - runtime file ii libgnomeui-0 2.20.1.1-1The GNOME 2 libraries (User Interf ii libgnomevfs2-0 1:2.22.0-4GNOME Virtual File System (runtime ii libgtk2.0-02.12.11-3 The GTK+ graphical user interface ii libpango1.0-0 1.20.5-1 Layout and rendering of internatio ii librarian0 0.8.0-1 Rarian is a documentation meta-dat ii libstartup-notificatio 0.9-1 library for program launch feedbac ii libstdc++6 4.3.1-8 The GNU Standard C++ Library v3 ii libunwind7 0.98.5-8 A library to determine the call-ch ii libx11-6 2:1.1.4-2 X11 client-side library ii libxml22.6.32.dfsg-2 GNOME XML library ii libxslt1.1 1.1.24-2 XSLT processing library - runtime ii man-db 2.5.2-2 on-line manual pager ii xml-core 0.11 XML infrastructure and XML catalog ii xulrunner-1.9 1.9.0.1-1 XUL + XPCOM application runner ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages yelp recommends: ii doc-base 0.8.16 utilities to manage online documen ii ttf-dejavu2.25-2 Metapackage to pull in ttf-dejavu- yelp suggests no packages. -- no debconf information -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493765: jabberd2: uses deprecated ldap API
Package: jabberd2 Version: 2.2.1-1 Severity: serious Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `ldap_init' implicitly converted to pointer at authreg_ldap.c:164 Function `ldap_get_values' implicitly converted to pointer at authreg_ldapfull.c:568 Function `ldap_get_values' implicitly converted to pointer at storage_ldapvcard.c:277 This is often due to a missing function prototype definition. For more information, see [2]. The libldap API has been updated and many functions used by the ldap plugin are now deprecated. This package should either update to the new API or define LDAP_DEPRECATED to continue using the deprecated interfaces. This patch implements the lazy solution. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493765: patch
Patch attached. -- dann frazier diff -urpN jabberd2-2.2.1.orig/storage/authreg_ldap.c jabberd2-2.2.1/storage/authreg_ldap.c --- jabberd2-2.2.1.orig/storage/authreg_ldap.c 2008-07-16 03:36:58.0 -0600 +++ jabberd2-2.2.1/storage/authreg_ldap.c 2008-08-04 13:27:09.0 -0600 @@ -30,6 +30,7 @@ #include c2s.h #include lber.h +#define LDAP_DEPRECATED 1 #include ldap.h #define AR_LDAP_FLAGS_NONE (0x0) diff -urpN jabberd2-2.2.1.orig/storage/authreg_ldapfull.c jabberd2-2.2.1/storage/authreg_ldapfull.c --- jabberd2-2.2.1.orig/storage/authreg_ldapfull.c 2008-07-16 03:36:58.0 -0600 +++ jabberd2-2.2.1/storage/authreg_ldapfull.c 2008-08-04 13:27:48.0 -0600 @@ -34,6 +34,7 @@ #ifdef STORAGE_LDAP #include lber.h +#define LDAP_DEPRECATED 1 #include ldap.h #define LDAPFULL_PASSBUF_MAX 257 diff -urpN jabberd2-2.2.1.orig/storage/storage_ldapvcard.c jabberd2-2.2.1/storage/storage_ldapvcard.c --- jabberd2-2.2.1.orig/storage/storage_ldapvcard.c 2008-07-16 03:36:58.0 -0600 +++ jabberd2-2.2.1/storage/storage_ldapvcard.c 2008-08-04 13:28:49.0 -0600 @@ -27,6 +27,7 @@ #ifdef STORAGE_LDAP +#define LDAP_DEPRECATED 1 #include ldap.h #include time.h
Bug#493768: jabberd2: crypt() implicitly converted to pointer
Package: jabberd2 Version: 2.2.1-1 Severity: serious Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `crypt' implicitly converted to pointer at authreg_mysql.c:150 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier diff -urpN jabberd2-2.2.1.orig/storage/authreg_mysql.c jabberd2-2.2.1/storage/authreg_mysql.c --- jabberd2-2.2.1.orig/storage/authreg_mysql.c 2008-07-16 03:36:58.0 -0600 +++ jabberd2-2.2.1/storage/authreg_mysql.c 2008-08-04 13:32:21.0 -0600 @@ -20,6 +20,9 @@ /* this module talks to a MySQL server via libmysqlclient */ +#define _XOPEN_SOURCE 500 +#include unistd.h + #include c2s.h #include mysql.h
Bug#493770: freebsd-buildutils: fgetln() implicitly converted to pointer
Package: freebsd-buildutils Version: 7.0-1 Severity: serious Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `fgetln' implicitly converted to pointer at excludes.c:74 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. It looks like excludes.c needs an '#include bsd/string.h' directive. Not providing a patch because this file appears during the build and its not immediately obvious to me where it comes from. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492721: linux-image-2.6.24-etchnhalf.1-686: doesn't boot on Via EPIA EK
On Mon, Jul 28, 2008 at 08:24:00PM +0200, Christian Pernegger wrote: Ok, did some testing: 2.6.26-686 [latest snapshot, 11913]: crash on boot 2.6.24-686 [etch]: crash on boot 2.6.24-486 [etch]: works 2.6.18-686 [etch]: works Screenshots of the two crashes are attached. Thanks Christian. This is looking like #464962 - running the 486 flavor is probably the best option for your system. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492899: partman-crypto: cancel button unusable on Erasing data screen
On Wed, Jul 30, 2008 at 11:58:38AM +0200, J?r?my Bobbio wrote: On Tue, Jul 29, 2008 at 06:03:34PM -0600, dann frazier wrote: I wonder if there's a way to split the cancel checking and the progress checking? [???] It might be, but I am not inclined to do this kind of changes that tend to breaks in very subtle way just before Lenny. makes sense Dividing the progress bar in 65536 parts will give us an abitility to cancel it every 1114112 written bytes, and should make it reactive enough. Another option might be to make it dynamic, based on the size of the disk - I assume we'd need to add a parameter to the wipe utility to negotiate this in advance. That too might be something better suited for post-lenny exploration. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492377: mksh: strcasestr implicitly converted to pointer
On Mon, Jul 28, 2008 at 09:15:01PM +, Thorsten Glaser wrote: Hi! implicit_pattern = re.compile(([^:]*):(\d+): warning: implicit declaration ??? I think that a simple addition to the already-existing sed command, like s/^[^:]*:[0-9]*:/config test;/ (which I did in mksh-35.2-2, pending to be uploaded by my sponsor??) should avoid your script to be triggered. Well, I'm not too worried about my copy getting triggered - I can currently remember the pkgs w/ false positives. But, this might be a good thing to add to the buildd's copy (maintainer cc'd). Note that the sed is only run on configure-time $CC calls anyway, not on calls to $CC used to really build mksh with the compiled results, so that real bugs in the source were to still be caught, if they then existed. ??? I just realised I have a freeze exception on mksh, even if I don???t know why, so let???s use it??? (I learned about the freeze 2 days ago on the media???) looks like you just did, thanks! bye, //mirabilos -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492899: screenshot
http://free.linux.hp.com/~dannf/bugs/492899/no-can-cancel.png -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492899: partman-crypto: cancel button unusable on Erasing data screen
Package: partman-crypto Version: 33 Severity: normal When doing an LVM+crypto install, I am presented with a Erasing data screen with a Cancel button. It doesn't seem to be possible to use the cancel button - it is not highlighted, and pressing tab doesn't cause it to be. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: ia64 Kernel: Linux 2.6.25-2-mckinley (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492899: partman-crypto: cancel button unusable on Erasing data screen
On Wed, Jul 30, 2008 at 12:42:59AM +0200, J?r?my Bobbio wrote:
On Tue, Jul 29, 2008 at 11:47:59AM -0600, dann frazier wrote:
When doing an LVM+crypto install, I am presented with a Erasing data
screen with a Cancel button. It doesn't seem to be possible to use the
cancel
button - it is not highlighted, and pressing tab doesn't cause it to be.
Are you using the newt frontend? In that case, could you try with the
GTK+ frontend?
I have tried with both the newt and GTK+ frontend and the Cancel button
was usuable in both cases.
hey Jeremy!
I tried both - in the GTK+ frontend I am able to click cancel, but it
doesn't seem to have any affect.
What size is the partition being erased?
~73G
After having a look at the source code, it's possible that, for a very
large partition, the progress would be updated rarely enough to give you
the impression that the Cancel button do not work, as its result would
not be checked often enough.
That sounds plausible, and after adding some debug statments, I
believe that your theory is correct. A kill does occur after the next
iteration of the while loop after I click cancel. There's just a long
time between iterations.
But, I think the confusion might be the return value. At the end of
crypto_do_wipe is this code:
wait $pid
ret=$?
[ $cancelled -eq 1 ] ret=0
return $ret
}
Which causes the function to return 0 if the user cancelled the
process.
Consider that a user might click cancel with no immediate result, then
a minute or two later they are moved along to the next step (creating
a password for the volume). They maybe led to believe that the wipe
completed successfully, even though their cancel attempt did
eventually succeed and cause the rest of the disk to not be cleared.
A possible fix in that case would be to divide the progress into more
steps than the current 100. But a deeper investigation would be
required before that.
I wonder if there's a way to split the cancel checking and the
progress checking? I'm still pretty green w/ d-i syntax, but it
appears that we know of a cancellation when db_progress returns 30 -
would it be possible/reasonable to do something like:
crypto_do_wipe() {
[existing code that starts up blockdev-wipe]
## fork a subshell to monitor for user cancels
{ while :; do
sleep 1
db_progress some no-op args
if [ $? -eq 30 ]; then
kill $pid
echo somestring-to-advance-progress $fifo
fi
}
watcherpid=$!
[existing while loop that reads fifo]
kill $watcherpid
[...]
}
--
dann frazier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492721: linux-image-2.6.24-etchnhalf.1-686: doesn't boot on Via EPIA EK
On Mon, Jul 28, 2008 at 03:07:10PM +0200, Christian Pernegger wrote: Package: linux-image-2.6.24-etchnhalf.1-686 Version: 2.6.24-6~etchnhalf.4 Severity: important The 2.6.24-etchnhalf kernel will not boot at all on my VIA EPIA EK. I was rather looking forward to being able to use a stable distro kernel (2.6.18 doesn't support power management on the CPU, which is why I had to use a custom 2.6.21 until now.) The crash occurs immediately after selecting the kernel in the grub menu. Top half of the screen has Ok, booting the kernel ... as its last line, bottom half is a dump of something, titled BUG. I could photograph the screen if required. Please do. It would also be useful to know if: 1) the -486 kernel works for you 2) a 2.6.26 -686 kernel works for you. 2.6.26 builds are available in the trunk snapshot repository, see http://wiki.debian.org/DebianKernel for information on installing snapshot builds (should work fine on an etch system) -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479101: Observation
On Mon, Jul 28, 2008 at 01:22:04PM -0800, mattb wrote: I stumbled across this bug report and noted the poster said: The new kernel 2.6.25-1 panics on my amd64 MacBookPro machine. MacBook Pro is an Intel Core machine. Apple doesn't use AMD processors at all. Thanks Matt. Actually, amd64 is the portname, and doesn't necessarily correspond with the processor manufacturer. For an explanation, see: http://wiki.debian.org/DebianAMD64Faq -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488374: seems to work
Otavio's patch seems to work for me. ldd no longer shows a dependency on libunwind: [EMAIL PROTECTED]:/tmp/parted-1.8.8.git.2008.03.24# ldd ./build-deb/libparted/.libs/libparted-1.8.so.9 | grep unwind libunwind.so.7 = /lib/libunwind.so.7 (0x2008001bc000) [EMAIL PROTECTED]:/tmp/parted-1.8.8.git.2008.03.24# ldd ./build-udeb/libparted/.libs/libparted-1.8.so.9 | grep unwind [EMAIL PROTECTED]:/tmp/parted-1.8.8.git.2008.03.24# And it seems to function: [EMAIL PROTECTED]:/tmp/parted-1.8.8.git.2008.03.24/build-udeb# LD_LIBRARY_PATH=/tmp/parted-1.8.8.git.2008.03.24/build-udeb/libparted/.libs parted/parted /dev/sdd GNU Parted 1.8.9 Using /dev/sdd Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print print Model: TREK2000 TD-G2 (scsi) Disk /dev/sdd: 65.5MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End SizeType File system Flags 1 21.5kB 65.5MB 65.5MB primary fat16 (parted) strace output also shows the libunwind getting opened when executing the 'deb' binary, but not when executing the udeb binary. Let me know if there's other tests you'd like me to run. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492377: mksh: strcasestr implicitly converted to pointer
Package: mksh Version: 35.2-1 Severity: serious Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `strcasestr' implicitly converted to pointer at ] scn.c:4 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492402: tla: implicit pointer conversions
Package: tla Version: 1.3.5+dfsg-10 Severity: serious Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `arch_interpret_delta_path' implicitly converted to pointer at /build/buildd/tla-1.3.5+dfsg/src/tla/libarch/cmd-apply-delta.c:304 Function `arch_find_or_make_tmp_local_copy' implicitly converted to pointer at /build/buildd/tla-1.3.5+dfsg/src/tla/libarch/cmdutils.c:571 Function `tmp_dir' implicitly converted to pointer at /build/buildd/tla-1.3.5+dfsg/src/tla/libfsutils/tmp-files.c:84 Function `arch_interpret_delta_path' implicitly converted to pointer at /build/buildd/tla-1.3.5+dfsg/src/tla/libarch/cmd-apply-delta.c:304 Function `arch_find_or_make_tmp_local_copy' implicitly converted to pointer at /build/buildd/tla-1.3.5+dfsg/src/tla/libarch/cmdutils.c:571 Function `tmp_dir' implicitly converted to pointer at /build/buildd/tla-1.3.5+dfsg/src/tla/libfsutils/tmp-files.c:84 Function `arch_interpret_delta_path' implicitly converted to pointer at /build/buildd/tla-1.3.5+dfsg/src/tla/libarch/cmd-apply-delta.c:304 Function `arch_find_or_make_tmp_local_copy' implicitly converted to pointer at /build/buildd/tla-1.3.5+dfsg/src/tla/libarch/cmdutils.c:571 Function `tmp_dir' implicitly converted to pointer at /build/buildd/tla-1.3.5+dfsg/src/tla/libfsutils/tmp-files.c:84 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions diff -urpN tla-1.3.5+dfsg.orig/src/tla/libarch/cmd-apply-delta.c tla-1.3.5+dfsg/src/tla/libarch/cmd-apply-delta.c --- tla-1.3.5+dfsg.orig/src/tla/libarch/cmd-apply-delta.c 2006-07-20 00:34:40.0 -0600 +++ tla-1.3.5+dfsg/src/tla/libarch/cmd-apply-delta.c 2008-07-25 13:34:38.0 -0600 @@ -31,6 +31,7 @@ #include tla/libarch/cmd-get.h #include tla/libarch/cmd-delta.h #include tla/libarch/cmd-apply-delta.h +#include tla/libarch/cmdutils.h /* __STDC__ prototypes for static functions */ diff -urpN tla-1.3.5+dfsg.orig/src/tla/libarch/cmdutils.c tla-1.3.5+dfsg/src/tla/libarch/cmdutils.c --- tla-1.3.5+dfsg.orig/src/tla/libarch/cmdutils.c 2006-07-20 00:34:40.0 -0600 +++ tla-1.3.5+dfsg/src/tla/libarch/cmdutils.c 2008-07-25 11:59:55.0 -0600 @@ -16,6 +16,7 @@ #include hackerlab/char/str.h #include tla/libarch/cmdutils.h #include tla/libarch/libraries.h +#include tla/libarch/local-cache.h #include tla/libarch/project-tree.h #include tla/libarch/patch-logs.h #include tla/libarch/pfs.h diff -urpN tla-1.3.5+dfsg.orig/src/tla/libfsutils/tmp-files.c tla-1.3.5+dfsg/src/tla/libfsutils/tmp-files.c --- tla-1.3.5+dfsg.orig/src/tla/libfsutils/tmp-files.c 2006-07-20 00:34:40.0 -0600 +++ tla-1.3.5+dfsg/src/tla/libfsutils/tmp-files.c 2008-07-25 11:53:56.0 -0600 @@ -16,6 +16,7 @@ #include hackerlab/char/str-many.h #include hackerlab/vu/safe.h #include hackerlab/fs/file-names.h +#include hackerlab/fs/tmp-files.h #include hackerlab/vu/safe.h #include tla/libfsutils/tmp-files.h
Bug#492377: mksh: strcasestr implicitly converted to pointer
reassign 492377 mksh thanks The seriousness of this bug is actually caused by the fact that we will be unable to do ia64 updates of mksh because the ia64 buildd will reject them. This doesn't mean it needs to be fixed in mksh of course, but mksh cannot release until it is fixed somehow, so the bug should remain here. On Fri, Jul 25, 2008 at 06:57:43PM +, Thorsten Glaser wrote: As for a possible solution, I don???t think that adding an exemption of mksh to the checker is worth the effort, but I can???t think of a modifi- cation to the test that would NOT trigger the warning while staying warning-free in all other cases (as the test is EXPECTED to fail on Debian with Fefe???s dietlibc). Maybe I could play some sed magic to fool the regex your scanner uses, so that it doesn???t recognise warnings emitted during the configuration process? This would then be a Debian- specific kludge and NOT go in upstream. If you have any BETTER solutions, please let me know. I don't have any good solutions in mind, and I also don't like the idea of you having to change somethinto workaround this filter. Maybe the buildd maintainer (CC'd) could install a whitelist file or something? -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492205: installation-reports: firmware load testing
On Thu, Jul 24, 2008 at 05:26:19PM -0400, Joey Hess wrote: dann frazier wrote: The bnx2 module requests 2 pieces of firmware - maybe that has something to do with it? Hm, don't think so.. If you want to test, I've checked fixes for all the issues I understand (except for the code page problem) into hw-detect in svn. Test image: http://kitenet.net/~joey/tmp/mini.so sha1sum: 31716cc357ac0db4a315523dd69daade3453ef00 I couldn't get this image to work; it seems to load bnx2 on startup automatically and, after a 'modprobe -r bnx2', it doesn't seem to ever bring up the fw prompt. If it still tries to install all the firmware .debs, I'd probably need to see a sh -x check-missing-firmware to figure out why. Though I did add a little bit of logging, that may help pinpoint it. I collected this (after commenting out debconf stuff, and manually modprobing bnx2 to create the /tmp/missing-firmware file). See [1]. The problem appears to be that the grepfor file contains an empty trailing line: ~ # cat /tmp/grepfor bnx2-06-4.0.5.fw bnx2-06-4.0.5.fw ~ # And this is because $files has a trailing space: ~ # cat /tmp/files2.dannf | sed 's/$/,/' bnx2-06-4.0.5.fw bnx2-06-4.0.5.fw , Filtering out the trailing space[2] fixed this for me. [1] BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ # modprobe -r bnx2 ~ # ls bin dev initlib mnt rootsys usr cdrom etc initrd media procsbintmp var ~ # ls /media/ ~ # ls /tmp x ~ # modprobe bnx2 ~ # cat /tmp/missing-firmware bnx2 bnx2-06-4.0.5.fw bnx2 bnx2-06-4.0.5.fw ~ # /bin/check-missing-firmware + set -e + LOG=/tmp/missing-firmware + NL= + first=1 + read_log + modules= + files= + [ -s /tmp/missing-firmware ] + mv /tmp/missing-firmware /tmp/missing-firmware.old + OLDIFS= + IFS= + cat /tmp/missing-firmware.old + module=bnx2 + [ -n bnx2 ] + modules=bnx2 + file=bnx2-06-4.0.5.fw + [ -n bnx2-06-4.0.5.fw ] + files=bnx2-06-4.0.5.fw + module=bnx2 + [ -n bnx2 ] + modules=bnx2 bnx2 + file=bnx2-06-4.0.5.fw + [ -n bnx2-06-4.0.5.fw ] + files=bnx2-06-4.0.5.fw bnx2-06-4.0.5.fw + IFS= + rm -f /tmp/missing-firmware.old + [ -n bnx2 bnx2 ] + return 0 + ask_load_firmware + return 0 + mountmedia mount: option requires an argument -- o BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) multi-call binary Usage: mount [flags] DEVICE NODE [-o options,more-options] umount: cannot umount /media: Invalid argument mount: mounting /dev/cciss/c0d0 on /media failed: Invalid argument + [ -e /media/bnx2-06-4.0.5.fw ] + [ -e /media/bnx2-06-4.0.5.fw ] + umount /media umount: cannot umount /media: Invalid argument + true + mountmedia driver mount: option requires an argument -- o BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) multi-call binary Usage: mount [flags] DEVICE NODE [-o options,more-options] umount: cannot umount /media: Invalid argument mount: mounting /dev/cciss/c0d0 on /media failed: Invalid argument mount: option requires an argument -- o BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) multi-call binary Usage: mount [flags] DEVICE NODE [-o options,more-options] umount: cannot umount /media: Invalid argument mount: mounting /dev/cciss/c0d1 on /media failed: Invalid argument mount: option requires an argument -- o BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) multi-call binary Usage: mount [flags] DEVICE NODE [-o options,more-options] umount: cannot umount /media: Invalid argument mount: mounting /dev/cciss/c0d2 on /media failed: Invalid argument mount: option requires an argument -- o BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) multi-call binary Usage: mount [flags] DEVICE NODE [-o options,more-options] umount: cannot umount /media: Invalid argument + echo bnx2-06-4.0.5.fw bnx2-06-4.0.5.fw + sed -e s/ /\n/g + [ -f /media/atmel-firmware_1.3-3_all.deb ] + list_deb_firmware /media/atmel-firmware_1.3-3_all.deb + ar p /media/atmel-firmware_1.3-3_all.deb data.tar.gz + grep -qf /tmp/grepfor + tar zt + grep ^\./lib/firmware/ + sed -e s!^\./lib/firmware/!! + install_firmware_pkg /media/atmel-firmware_1.3-3_all.deb + echo /media/atmel-firmware_1.3-3_all.deb + grep -q \.deb$ + mkdir -p /var/cache/firmware/ + cp -a /media/atmel-firmware_1.3-3_all.deb /var/cache/firmware/ + basename /media/atmel-firmware_1.3-3_all.deb + udpkg --unpack /var/cache/firmware/atmel-firmware_1.3-3_all.deb (Reading database...) (Updating database...) + [ -f /media/firmware-bnx2_0.12_all.deb ] + list_deb_firmware /media/firmware-bnx2_0.12_all.deb + ar p /media/firmware-bnx2_0.12_all.deb data.tar.gz + grep -qf /tmp/grepfor + tar zt + grep ^\./lib/firmware/ + sed -e s!^\./lib/firmware/!! + install_firmware_pkg /media/firmware-bnx2_0.12_all.deb + echo /media/firmware-bnx2_0.12_all.deb + grep -q \.deb$ + mkdir -p /var/cache/firmware/ + cp -a /media/firmware-bnx2_0.12_all.deb /var/cache/firmware/ + basename /media/firmware-bnx2_0.12_all.deb + udpkg --unpack /var/cache/firmware/firmware-bnx2_0.12_all.deb (Reading
Bug#492205: installation-reports: firmware load testing
Package: installation-reports Severity: normal Subject: installation-reports: lenny daily / hp dl380g5 Package: installation-reports Severity: normal -- Package-specific info: Boot method: CD Image version: i386 netinst daily build 2008.07.23 Date: Date and time of the install Machine: HP DL380g5 Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[E] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[EMAIL PROTECTED] Comments/Problems: Thanks for adding the firmware support! I finally got around to testing it out w/ one of the dailies thought I'd write up the issues I ran into in case any of them aren't yet known. Unable to mount usb stick - I created a usb stick w/ the firmware debs in the firmware.tar.gz. In my case it was a virtual usb device, emulated by the HP iLO 2. I created the backend file by mkdosfs'ing an empty 8MB file, loopback mounting it, and unpacking the firmware deb tarball in the root. The installer correctly discovered that I might need firmware for my bnx2 controller, and it asked me if it should look for it on some attached media. I selected yes, and it went away for a bit while it searched devices, but then eventually returned w/ the same prompt. Dropping to a shell, I saw the following messages in dmesg: [ 24.285589] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 24.299221] Unable to load NLS charset utf8 [ 24.299224] FAT: IO charset utf8 not found I am also unable to mount the usb stick from the shell using the same arguments mountmedia uses: # mount /dev/sda /media -tauto The problem appears to be that the Debian kernel is configured to use the utf8 iocodepage by default (see #483781), but the installer does not include the nls_utf8 module. If I override this default by passing the mount option 'iocodepage=iso8559-1', the mount succeeds. If I copy over and load the nls_utf8 module the mount succeeds w/o the iocodepage option. And if I use an ext2 stick and load the ext2 module early on, this entire step succeeds w/o further intervention. fw file dups on error - minor - but each time I returned to the should i look for firmware screen, the displayed list would include more copies of the same filenames. To illustrate, see the following screen shots: http://free.linux.hp.com/~dannf/d-i-20080723/missing-fw-1.png http://free.linux.hp.com/~dannf/d-i-20080723/missing-fw-2.png http://free.linux.hp.com/~dannf/d-i-20080723/missing-fw-3.png fails to install fw debs into target I lazily dumped all of the fw debs from the firmware.tar.gz onto my stick instead of just the one I needed (bnx2). This caused problems during the base install: http://free.linux.hp.com/~dannf/d-i-20080723/busybox-error.png Looking at syslog, it appears that the problem is unmet dependencies for some of the firmware debs: base-installer: info: Available initramfs generator(s): 'initramfs-tools' Reading package lists... Building dependency tree... Reading state information... You might want to run `apt-get -f install' to correct these: The following packages have unmet dependencies: atmel-firmware: Depends: perl but it is not installable Depends: udev (= 0.070-3) but it is not going to be installed or hotplug (= 0.0.20040329-12) but it is not installable zd1211-firmware: Depends: udev (= 0.070-3) but it is not going to be installed or hotplug (= 0.0.20040329-19) but it is not installable E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). base-installer: error: exiting on error base-installer/kernel/failed-package-install Full syslog file: http://free.linux.hp.com/~dannf/d-i-20080723/syslog Grub installed to usb stick instead of system disk -- When prompted if I wanted grub installed to the MBR, I said sure - but that ended up installing grub to my firmware usb stick ;( Not sure there's anything we can about this one, other than potentially warn the user. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to [EMAIL PROTECTED] == Installer lsb-release: ==
Bug#492205: installation-reports: firmware load testing
On Thu, Jul 24, 2008 at 06:46:44PM +0200, J?r?my Bobbio wrote: On Thu, Jul 24, 2008 at 05:41:17AM -0600, dann frazier wrote: Thanks for adding the firmware support! I finally got around to testing it out w/ one of the dailies thought I'd write up the issues I ran into in case any of them aren't yet known. Thanks for your detailed report. As we are trying to polish things up for Lenny, this is definitely worthwhile. Would you be able to do other test installations as we fix the issue you have encountered here? Of course! That's the least I can offer.. (I am leaving this bug report opened in order to allow follow-up.) Thanks for your analysis - it all looks quite reasonable to me, so I don't have any specific responses. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492205: installation-reports: firmware load testing
On Thu, Jul 24, 2008 at 04:16:48PM -0400, Joey Hess wrote:
J?r?my Bobbio wrote:
* Firmware packages should not be installed for firmware that were not
explicitely required.
This would need further investigation as the code, as far as I can
see, should filter out the packages present on the media based on
needed firmware files.
The filtering worked in my testing. Before I go off on a wild goose
chase, are we sure that Dan didn't dump the debs into
/var/cache/firmware/ in d-i? Because it would pefectly explain it trying
to install all the debs from there.
Yeah, I'm sure :)
Hmm, tested again, code still seems to work:
# files=foo bar
# echo $files | sed -e 's/ /\n/g' /tmp/grepfor
# cat /tmp/grepfor
foo
bar
# list_deb_firmware () {
# list_deb_firmware () {
ar p $1 data.tar.gz | tar zt \
| grep '^\./lib/firmware/' \
| sed -e 's!^\./lib/firmware/!!'
}
# list_deb_firmware zd1211-firmware_2.16.0.0-0.1_all.deb
zd1211/
zd1211/zd1211_ub
zd1211/zd1211_uph
zd1211/zd1211_uphm
zd1211/zd1211_uphr
zd1211/zd1211_ur
zd1211/zd1211b_ub
zd1211/zd1211b_uph
zd1211/zd1211b_uphm
zd1211/zd1211b_uphr
zd1211/zd1211b_ur
# list_deb_firmware zd1211-firmware_2.16.0.0-0.1_all.deb | grep -qf
/tmp/grepfor
# echo $?
1
#
It does, however, think that every deb contains a firmware file named , so
if
it somehow thinks it needs such a file, it will try to use every deb to
provide
it:
/ff # files=foo bar
/ff # echo $files | sed -e 's/ /\n/g' /tmp/grepfor
/ff # list_deb_firmware zd1211-firmware_2.16.0.0-0.1_all.deb | grep -qf
/tmp/grepfor
/ff # echo $?
0
I don't see how $files could get an extra leading/trailing space to
tickle this problem, unless a module actually requests a firmware file
with a space in its name. But I've checked in a fix for it anyway..
The bnx2 module requests 2 pieces of firmware - maybe that has
something to do with it?
--
dann frazier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491601: madwifi-source fails to build against 2.6.24-etchnhalf.1-486
On Wed, Jul 23, 2008 at 08:42:20PM +0200, Michael Goetze wrote: Hi, On 21.07.2008, at 08:40, dann frazier wrote: Also note that the ath5k driver is included in the 2.6.24 kernel - I don't personally know how much hardware works with madwifi but not ath5k though. Well, for one thing, it's missing some exotic features like, say, Master mode. ;) Yep, that's a big one :) It also seems to not work well w/ WPA (at least, not on the laptop I tried). Again, we're open to adding a madwifi-etchnhalf package in a point release. For 4.0r4, the window is closing very quickly since the release is scheduled for this Friday, but a 4.0r5 can hopefully happen ~2 months later. The requirements for such a package are: * module either adds new hardware support for etch, or achieves feature parity with the etch 2.6.18 kernel. etchnhalf is specifically targeted at adding hardware support, so adding things like new filesystems would be out-of-scope. * module must not be rc-buggy (obviously) * module version must be = version in lenny * source and binary packages should have -etchnhalf appended * module source should get installed in /usr/src/etchnhalf (this lets the package coeexist w/ its etch counterpart) * Included documentation should explain how to point m-a at the new location (e.g., # MOD_SRCDIR=/usr/src/etchnhalf m-a b-i). Note that a-i and other commands that attempt to fetch source won't work - the -etchnhalf namespace breaks that :( * source package should omit any redundant packages * module has been tested in etch w/ etchnhalf kernel (i.e., compatible with etch userspace) squashfs-etchnhalf, atl2-etchnhalf and loop-aes-etchnhalf are examples of this. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492123: loop-aes-keygen copyright info missing
Package: loop-aes Version: 3.2c-2 Severity: normal Tags: patch Thomas Viehmann as ftpmaster discovered that the copyright information from loop-aes-keygen is missing from debian/copyright. This was discovered in loop-aes-etchnhalf, but also applies to loop-aes. Here's the patch I used for loop-aes-etchnhalf: diff -u loop-aes-etchnhalf-3.2c/debian/changelog loop-aes-etchnhalf-3.2c/debian/changelog --- loop-aes-etchnhalf-3.2c/debian/changelog +++ loop-aes-etchnhalf-3.2c/debian/changelog @@ -1,3 +1,9 @@ +loop-aes-etchnhalf (3.2c-2~etchnhalf.2) stable; urgency=low + + * Update copyright for loop-aes-keygen + + -- dann frazier [EMAIL PROTECTED] Wed, 23 Jul 2008 15:03:50 -0600 + loop-aes-etchnhalf (3.2c-2~etchnhalf.1) stable; urgency=low * Non-maintainer upload. diff -u loop-aes-etchnhalf-3.2c/debian/copyright loop-aes-etchnhalf-3.2c/debian/copyright --- loop-aes-etchnhalf-3.2c/debian/copyright +++ loop-aes-etchnhalf-3.2c/debian/copyright @@ -19,6 +19,9 @@ Copyright 2001-2003 by Jari Ruusu [EMAIL PROTECTED] Copyright 1998 Free Software Foundation, Inc +The loop-aes-keygen script is + Copyright 2005-2006, Max Vozeler [EMAIL PROTECTED] + You are free to distribute this software under the terms of the GNU General Public License. On Debian systems, the complete text of the GNU General Public License can be found in the file -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491601: madwifi-source fails to build against 2.6.24-etchnhalf.1-486
On Mon, Jul 21, 2008 at 11:36:06AM +1000, Kel Modderman wrote: On Monday 21 July 2008 05:44:45 Michael Goetze wrote: Package: madwifi-source Version: 0.9.2+r1842.20061207-2etch2 When I try to compile madwifi-source against linux-2.6.24-etchnhalf. 1-486, I get the following error: ... make[2]: Entering directory `/usr/src/modules/madwifi' Checking requirements... ok. Checking kernel configuration... FAILED Please enable wireless extensions. make[2]: *** [configcheck] Error 1 ... Presumably, the etchnhalf release would need to include a newer version of madwifi-source to rectify this problem. Thats right, throw a kernel 6 upstream versions newer into an archive frozen when 2.6.18 was new and it's what you get ;-) Unfortunately, I don't think etch will see another update to fix this problem. A backport from sid/testing could be done, the porter would need to drop debhelper compat level. However, the delta between madwifi upstream in etch and sid/testing is very large. A bacport of madwifi 0.9.4 based package could be possible, however the 0.9.4 based package has been superceded in sid/testing recently in favour of something far more bleeding edge. Picking out the exact upstream backports required to fix the antiquated madwifi version in etch for 2.6.24 would be tedious, time consuming and very error prone. Especially hard for a novice Linux kernel code hacker such as myself. The same problem exists for ndiswrapper in etch, and probably other module-source packages too. I am not aware of any module-source etch+1/2 update plan. Hopefully there is such a plan for Lenny+1/2, and hopefully it doesn't mandate the cherry picking of exact API fixes for external modules, but rather the backporting of new upstream versions that had seen some time in the archive post-stable-release. There is a plan for the module-source packages used by the conglomerate (linux-modules-*) packages. etchnhalf list archives seem to be down right now, but you can see an e-mail about it here: http://lists.debian.org/debian-kernel/2008/07/msg00494.html There's no reason we couldn't also include similar new packages for other out of tree modules that meet the listed requirements. Time is getting very short for 4.0r4 - but it may still be an option if you wanted to prepare and test something quickly. 4.0r5 is an option if you want to do such an update but need more time to prepare it. Also note that the ath5k driver is included in the 2.6.24 kernel - I don't personally know how much hardware works with madwifi but not ath5k though. Cheers! -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490542: k7 transitition
A few days ago, Frans said: From a later discussion with some other people on IRC, it looks like SSE support is probably the deciding factor. According to section 2.2 in [1] and especially the note Enabling SSE support just above section 2.3, models 0-5 for family 6 AMD processors may not have SSE support and thus should continue to default to the 486 flavor. Thanks for the research Frans and the follow-up on IRC. However, after thinking about this, I'm not sure I follow the logic - or at least I need some hand holding to get it. From reading the kernel source, it appears that a 686-configured kernel will cause gcc to use -march=i686. The gcc manual[1] implies that this will not cause sse instructions to be generated - pentium3 or athlon optimization (or greater) is required before SSE is enabled. The kernel does have some assembly routines coded in assembly that make use of SSE (e.g. the xor code used for raid checksumming), but they dynamically check for sse support by using cpu_has_xmm(). I do see why we wouldn't want to run a k7 kernel on all family 6 cpus. Google quickly found a /proc/cpuinfo file that shows a family 6 with no sse flag. However, I don't follow why this means a 686 kernel would not be safe on a family 6 cpu. [1] http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options [2] http://ubuntuforums.org/showpost.php?p=5119933postcount=32 -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490975: devil: glXGetProcAddressARB implicitly converted to pointer
Package: devil Version: 1.6.8-rc2-1 Severity: serious Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `glXGetProcAddressARB' implicitly converted to pointer at ilut_opengl.c:116 This is often due to a missing function prototype definition. For more information, see [2]. Building with -DGLX_GLXEXT_LEGACY seems to avoid this problem, but I don't know that it is the most appropriate solution. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489817: sugar-toolkit: gsm_xsmp_init implicitly converted to pointer
Package: sugar-toolkit Version: 0.81.5-1 Severity: serious Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `gsm_xsmp_init' implicitly converted to pointer at _sugarext.c:896 Function `gsm_xsmp_init' implicitly converted to pointer at _sugarext.c:896 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier --- sugar-toolkit-0.81.5.orig/src/sugar/_sugarext.c 2008-06-20 10:53:45.0 -0600 +++ sugar-toolkit-0.81.5/src/sugar/_sugarext.c 2008-07-07 16:08:04.0 -0600 @@ -14,6 +14,7 @@ #include sugar-preview.h #include sexy-icon-entry.h #include gsm-session.h +#include gsm-xsmp.h #define EGG_SM_CLIENT_BACKEND_XSMP #include eggsmclient.h
Bug#317258: [stable] kernel upload to p-u
On Thu, Jul 03, 2008 at 01:12:15PM +0200, Vincent Reydet wrote: Hi, I've a hp netserver lc 2000 with netraid scsi card, and etch kernel (#-6) still doesn't work. I've installed a sarge, net upgrade to etch, then build a kernel 2.6.18-6 with the patch above ( I could share it but nobody should trust my binary ... ). Now it's fine for me, but i would like to have this problem either corrected by a debian patch, either corrected upstream. What do you need for that ? I'd suggest testing the latest snapshot kernel (see http://wiki.debian.org/DebianKernelReportingBugs) 1) Make sure you have the latest fw available for your card 2) Test the latest trunk snapshot kernel Assuming this doesn't fix the problem, please contact upstream (see MAINTAINERS file for contact address). I've reported issues to them before and they were quite responsive. They would prefer to fix the new driver rather than add more IDs to the old. If a driver fix proves necessary and gets accepted upstream, we would certainly consider backporting it into a stable kernel for Debian. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417911: systemimager-client: What's the status of amd64 support?
On Thu, Jul 03, 2008 at 10:26:39PM +0200, Johannes Graumann wrote: Package: systemimager-client Followup-For: Bug #417911 I can't get out of this old thread what the status of work on amd64 support in debian is. Can you please comment? SystemImager is orphaned in Debian - noone is actively working on it to my knowledge. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488932: xserver-xorg-video-vesa: xf86GTFMode implicitly converted to pointer
Package: xserver-xorg-video-vesa Version: 1:2.0.0-1 Severity: serious Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `xf86GTFMode' implicitly converted to pointer at ../../src/vesa.c:345 This is often due to a missing function prototype definition. For more information, see [2]. It looks like this function is available in xserver-xorg-dev from experimental, but not sid. Maybe this needs to be a versioned build-dep? Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488727: lxlauncher_load_icon implicitly converted to pointer
Package: lxlauncher Version: 0.2-1 Severity: serious Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `lxlauncher_load_icon' implicitly converted to pointer at lxlauncher.c:187 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier --- lxlauncher-0.2/src/lxlauncher.c~ 2008-06-15 09:55:15.0 -0600 +++ lxlauncher-0.2/src/lxlauncher.c 2008-06-30 15:06:57.0 -0600 @@ -41,6 +41,7 @@ #include exo-wrap-table.h #include working-area.h +#include misc.h #define BUTTON_SIZE 120 #define IMG_SIZE 48
Bug#488265: linux-image-2.6-amd64-etchnhalf: Problem using bnx2 module
On Fri, Jun 27, 2008 at 04:03:36PM +0300, Evaggelos Souglakos wrote: Package: linux-image-2.6-amd64-etchnhalf Version: 2.6.24+13~etchnhalf.1 Severity: important bnx2 modules is useless on this kernel package Loading Linux version 2.6.24-etchnhalf.1-amd64 (Debian 2.6.24-6~etchnhalf.3) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP It is an ibm x3650 server bnx2: Can't load firmware file bnx2-06-4.0.5.fw ACPI: PCI interrupt for device :04:00.0 disabled bnx2: probe of :04:00.0 failed with error -2 You need to install the firmware-bnx2 package from non-free. See the release notes draft here: http://people.debian.org/~dannf/tmp/etchnhalf/ -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488265: linux-image-2.6-amd64-etchnhalf: Problem using bnx2 module
On Fri, Jun 27, 2008 at 09:39:25PM +0300, Evaggelos Souglakos wrote: Hello, I have already installed the firmware-bnx2 package dpkg -l |grep bnx ii firmware-bnx20.11~bpo40+1 Binary firmware for Broadcom NetXtremeII You need the one from proposed-updates. The one in sid only works with an initramfs-tools package version that knows how to copy firmware files over. The one in proposed-updates provides its own hook to work with etch's initramfs-tools. dpkg -l | grep linux-image-2.6-amd64-etchnhalf ii linux-image-2.6-amd64-etchnhalf 2.6.24+13~etchnhalf.1 Linux 2.6-etchnhalf image on AM but on kernel boot i can still see: bnx2: Can't load firmware file bnx2-06-4.0.5.fw Is it supposed to get these files from /lib/firmware? As you can see there are at this dir. ls -l /lib/firmware/ total 216 -rw-r--r-- 1 root root 106116 Jun 5 11:29 bnx2-06-4.0.5.fw -rw-r--r-- 1 root root 102844 Jun 5 11:29 bnx2-09-4.0.5.fw I would appreciate any further help Thank you, On Friday 27 June 2008 18:27:17 dann frazier wrote: On Fri, Jun 27, 2008 at 04:03:36PM +0300, Evaggelos Souglakos wrote: Package: linux-image-2.6-amd64-etchnhalf Version: 2.6.24+13~etchnhalf.1 Severity: important bnx2 modules is useless on this kernel package Loading Linux version 2.6.24-etchnhalf.1-amd64 (Debian 2.6.24-6~etchnhalf.3) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP It is an ibm x3650 server bnx2: Can't load firmware file bnx2-06-4.0.5.fw ACPI: PCI interrupt for device :04:00.0 disabled bnx2: probe of :04:00.0 failed with error -2 You need to install the firmware-bnx2 package from non-free. See the release notes draft here: http://people.debian.org/~dannf/tmp/etchnhalf/ -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483200: patch
tags 483200 + patch
thanks
hey Petter,
This patch works for me on a 6510b. Note that reading the xorg.conf
file isn't very reliable anymore now that xorg.conf files are pretty
barebones and less likely to include a driver line.
diff -Nru hotkey-setup-0.1/debian/changelog hotkey-setup-0.1/debian/changelog
--- hotkey-setup-0.1/debian/changelog 2008-01-17 14:22:25.0 -0700
+++ hotkey-setup-0.1/debian/changelog 2008-06-24 11:34:18.0 -0600
@@ -1,3 +1,10 @@
+hotkey-setup (0.1-22~dannf1) local; urgency=low
+
+ * http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483200
+ * https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/157691
+
+ -- dann frazier [EMAIL PROTECTED] Tue, 24 Jun 2008 11:33:39 -0600
+
hotkey-setup (0.1-21) unstable; urgency=low
* Only try to read /etc/X11/xorg.conf if it exist (Closes: #461147)
diff -Nru hotkey-setup-0.1/debian/control hotkey-setup-0.1/debian/control
--- hotkey-setup-0.1/debian/control 2008-01-17 14:01:20.0 -0700
+++ hotkey-setup-0.1/debian/control 2008-06-24 11:36:28.0 -0600
@@ -7,7 +7,7 @@
Package: hotkey-setup
Architecture: i386 amd64 lpia
-Depends: ${shlibs:Depends}, ${misc:Depends}, dmidecode (= 2.7),
laptop-detect, console-tools | console-utilities
+Depends: ${shlibs:Depends}, ${misc:Depends}, dmidecode (= 2.7),
laptop-detect, console-tools | console-utilities, pciutils
Conflicts: tpb
Description: auto-configures laptop hotkeys
This package will attempt to auto-detect your laptop hardware and then
diff -Nru hotkey-setup-0.1/debian/init.d hotkey-setup-0.1/debian/init.d
--- hotkey-setup-0.1/debian/init.d 2008-01-16 15:08:03.0 -0700
+++ hotkey-setup-0.1/debian/init.d 2008-06-24 11:33:28.0 -0600
@@ -37,6 +37,16 @@
done
;;
esac
+
+# Display controller [0380]: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller [8086:2a03] (rev 0c)
+LSPCI=`lspci -nd 8086:2a03`;
+if [ -n $LSPCI ]; then
+for x in /proc/acpi/video/*/DOS; do
+if [ -e $x ]; then
+echo -n 7 $x; # '4' still let's it crash
+fi
+done
+fi;
}
# This is here because it needs to be executed both if we have a
--
dann frazier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487737: lxpanel: implicit pointer conversions
Package: lxpanel Version: 0.3.7-1 Severity: serious Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `passwd_gui_new' implicitly converted to pointer at netstat.c:110 Function `fb_bg_get_pix_from_file' implicitly converted to pointer at panel.c:300 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier ---BeginMessage--- Function `passwd_gui_new' implicitly converted to pointer at netstat.c:110 Function `fb_bg_get_pix_from_file' implicitly converted to pointer at panel.c:300 ---End Message---
Bug#486746: audacious-plugins: audacious_get_localdir implicit pointer conversion
Package: audacious-plugins Version: 1.5.1-1 Severity: serious Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `audacious_get_localdir' implicitly converted to pointer at i_configure.c:419 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions --- audacious-plugins-1.5.1/src/amidi-plug/i_configure.c~ 2008-05-23 16:44:19.0 -0600 +++ audacious-plugins-1.5.1/src/amidi-plug/i_configure.c2008-06-17 16:29:22.0 -0600 @@ -29,6 +29,7 @@ #include i_configure-dummy.h #include i_utils.h #include audacious/auddrct.h +#include audacious/plugin.h amidiplug_cfg_backend_t * amidiplug_cfg_backend; -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422300: severity raise, practical FTBFS
severity 422300 serious found 422300 0.6.4-2 thanks hey Bob, The ia64 buildds will automatically fail any builds that trigger this issue, so these issues are now considered practical FTBFS issues and warrant a serious severity. Sorry, should've done this sooner but I'd lost track of this one until the recent upload brought it back to my attention. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486534: lmemory: xpm_widget, xpm_widget_default implicitly converted to pointers
Package: lmemory Version: 0.6c-2 Severity: serious Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `xpm_widget_default' implicitly converted to pointer at lmem_window.c:193 Function `xpm_widget' implicitly converted to pointer at lmem_window.c:204 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions --- lmemory-0.6c/lmem_window.c~ 2003-07-30 09:36:35.0 -0600 +++ lmemory-0.6c/lmem_window.c 2008-06-16 11:04:45.0 -0600 @@ -11,6 +11,9 @@ #include stdlib.h #include lmemory.h +GtkWidget *xpm_widget(GtkWidget *parent, gchar *xpm_filename); +GtkWidget *xpm_widget_default( GtkWidget *parent); + int flipped; int flipped_btn[3];
Bug#410807: Patch for kernel BUG at drivers/xen/core/evtchn.c:481
On Sun, Jun 15, 2008 at 09:28:47PM +0100, Ian Campbell wrote: Hi, I believe this issue is fixed by http://xenbits.xensource.com/xen-unstable.hg?rev/914304b3a3da Without the patch (2.6.18.dfsg.1-18etch1) I was able to reproduce the problem by repeatedly starting 4 guest domains in parallel[0] in a around 5-6 hours or 288 iterations (first time I repro'd it was a couple of hours, I wasn't counting time or iterations that time). With the patch applied on top of the svn kernel (2.6.18.dfsg.1-21.0.hellion0) the test survived overnight, around 16 hours and 850 iterations. ???I've attached a version of this backported to the Etch kernel (some of the function names differ). ???I also attached the svn diff-of-a-diff against revision in r11588, 2.6.18.dfsg.1-22. Thanks Ian! Please go ahead and commit. Note that I think you need a '#' in front of the bug number for the closer syntax to work. This issue is already fixed in the Lenny/Sid kernels which use the paravirt_ops kernel port which has completely reimplemented event channel code. Cheers, Ian. [0] n=0 ; while : ; do date ; echo iteration $n ; xm create debian-x86_32p-1 xm create debian-x86_32p-2 xm create rhel44-x86_32p-1 kernel=/boot/vmlinuz-2.6.18.8-x86_32p-xenU ramdisk= xm create rhel41-x86_32p-1 kernel=/boot/vmlinuz-2.6.18.8-x86_32p-xenU ramdisk= sleep 1m ; xm dest debian-1 ; xm dest debian-2 ; xm dest rhel41-1 ; xm dest rhel44-1 ; sleep 5s ; n=$(($n + 1)) ; done -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426705: cciss: kernel BUG at drivers/block/cciss.c:2479
On Tue, Jun 10, 2008 at 04:24:16PM +0200, Leo Weppelman wrote: On Tue, Jun 03, 2008 at 01:01:55AM +0200, maximilian attems wrote: On Wed, 30 May 2007, Leo Weppelman wrote: Package: linux-image-2.6.21-1-686 Version: 2.6.21-4 The trace written to the console: = kernel BUG at drivers/block/cciss.c:2479! invalid opcode: [#1] SMP hmm i see. How to reproduce: = I have an ML-350-G5 with an E200i raid controller. There are 2 logical drives defined that map 1-1 on a physical drive. Those disks are part of a software RAID-1 array. When initializing an oracle database on the system, the system panics. Leo. can you still reproduce the error with an up to date kernel aka at least 2.6.24? better 2.6.25 as this one is still upstream supported? thanks for coming back and sorry for late ping?! greetings I tried it with the 2.6.25 (linux-image-2.6.25-2-686_2.6.25-4_i386.deb) today and I can no longer reproduce the bug as I could with 2.6.21. If you want some additional tests, let me know. I'll recycle the installed configuration somewhere next week for some other work. Well, since you asked :) Can you test the etchnhalf kernel? Latest one is: http://http.us.debian.org/debian/pool/main/l/linux-2.6.24/linux-image-2.6.24-etchnhalf.1-686_2.6.24-6~etchnhalf.2_i386.deb -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418757: Debian Etch: Patch: /proc/scsi/aacraid missing
On Wed, Jun 11, 2008 at 04:28:49PM +1200, Ewen McNeill wrote:
As noted by Marcin Owsiany [EMAIL PROTECTED] last year, with the
default Debian Etch kernel, /proc/scsi/aacraid is missing on the Debian
Etch kernel, even when the AACRAID driver is loaded and operating.
Amongst other things this prevents using the Dell afacli management tool
to monitor/manage the RAID arrays, since it checks for
/proc/scsi/aacraid and aborts if it is not found.
In the link that Marcin Owsiany provided:
http://lists.us.dell.com/pipermail/linux-poweredge/2007-January/029281.html
is a trivial patch for the aacraid driver which sets the necessary
elements in the structure which allow the /proc/scsi/aacraid file to
appear. Apparently originally from some Dell Engineers.
Would it be possible to have this applied to the Debian Etch kernel at
the next point release? (Etch and a half?) It's against 2.6.16
but seems easy enough to sort out for Etch's 2.6.18 kernel.
I've included it below to make it easier for you to get at.
Thanks Ewen. The first step in getting it into Debian would be to make
sure it gets upstream. Otherwise, adding it to etch means we either
need to maintain the out of tree patch for future releases or drop it
and cause a feature regression. Once its upstream it will naturally
end up in the queue for a future Debian release and we can consider
backporting it to current stable.
Ewen
-=- cut here -=-
From: Patrick Boyd Patrick_Boyd at dell.com,
Bill Edwards Bill_Edwards at dell.com
The problem that we are having is that on the current version of RedHat
Enterprise Linux 5 (2.6.16 kernel) the Adaptec raid management libraries
(AFALIB) no longer function. We were able to root cause this to the fact
that the /proc/scsi/aacraid directory was missing.
This directory is created if two properties are set in the
scsi_host_template structure: proc_name and proc_info. However, previous
driver version were not setting proc_info and as far as we can tell
this was just being set to uninitialized memory which was allowing the
directory creation to succeed. Apparently compiler or runtime behavior
has changed so that uninitialized entries in this static struct are set
to 0. Our solution is to simply create a function and put the function
pointer into the struct to restore the original behavior under the
new compiler.
Signed-off-by: Patrick Boyd Patrick_Boyd at dell.com, Bill Edwards
Bill_Edwards at dell.com
---
--- linux-2.6.16/drivers/scsi/aacraid/linit.c.orig2006-08-30
11:53:58.0 -0500
+++ linux-2.6.16/drivers/scsi/aacraid/linit.c 2006-08-30 11:55:27.0
-0500
@@ -782,10 +782,18 @@ static struct file_operations aac_cfg_fo
.open = aac_cfg_open,
};
+static int aacraid_proc_info(struct Scsi_Host *host, char *buffer, char
**start, off_t offset,
+int length, int inout) {
+ return 0;
+}
+
+
static struct scsi_host_template aac_driver_template = {
.module = THIS_MODULE,
.name = AAC,
.proc_name = AAC_DRIVERNAME,
+ .proc_info = aacraid_proc_info,
.info = aac_info,
.ioctl = aac_ioctl,
#ifdef CONFIG_COMPAT
-=- cut here -=-
--
dann frazier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482943: please test DRBD fix
hey Alex, TSUCHIYA, Can you test this build to verify that it fixes the issue for you? http://people.debian.org/~dannf/bugs/482943/ -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484323: gnome-panel crash when running evolution --force-shutdown
Package: gnome-panel Version: 2.20.3-4 Severity: normal Please include the fix for http://bugzilla.gnome.org/show_bug.cgi?id=378854 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: ia64 Kernel: Linux 2.6.25-1-itanium (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-panel depends on: ii gnome-about2.22.2-1 The GNOME about box ii gnome-control-center 1:2.22.2.1-1 utilities to configure the GNOME d ii gnome-desktop-data 2.22.2-1 Common files for GNOME 2 desktop a ii gnome-menus2.22.2-1 an implementation of the freedeskt ii gnome-panel-data 2.20.3-4 common files for the GNOME Panel ii libatk1.0-01.22.0-1 The ATK accessibility toolkit ii libbonobo2-0 2.22.0-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.22.0-1 The Bonobo UI library ii libc6.12.7-11GNU C Library: Shared libraries ii libcairo2 1.6.4-3 The Cairo 2D vector graphics libra ii libdbus-glib-1-2 0.74-4simple interprocess messaging syst ii libecal1.2-7 2.22.2-1 Client library for evolution calen ii libedataserver1.2-92.22.2-1 Utility library for evolution data ii libedataserverui1.2-8 2.22.2-1 GUI utility library for evolution ii libgconf2-42.22.0-1 GNOME configuration database syste ii libglade2-01:2.6.2-1 library to load .glade files at ru ii libglib2.0-0 2.16.3-2 The GLib library of C routines ii libgnome-desktop-2 2.22.2-1 Utility library for loading .deskt ii libgnome-menu2 2.22.2-1 an implementation of the freedeskt ii libgnome2-02.20.1.1-1The GNOME 2 library - runtime file ii libgnomeui-0 2.20.1.1-1The GNOME 2 libraries (User Interf ii libgnomevfs2-0 1:2.22.0-3GNOME Virtual File System (runtime ii libgtk2.0-02.12.9-4 The GTK+ graphical user interface ii liborbit2 1:2.14.12-0.1 libraries for ORBit2 - a CORBA ORB ii libpanel-applet2-0 2.20.3-4 library for GNOME Panel applets ii libpango1.0-0 1.20.2-2 Layout and rendering of internatio ii libwnck22 2.22.1-1 Window Navigator Construction Kit ii libx11-6 2:1.0.3-7 X11 client-side library ii libxau61:1.0.3-3 X11 authorisation library ii menu-xdg 0.3 freedesktop.org menu compliant win Versions of packages gnome-panel recommends: ii alacarte 0.11.3-1 easy GNOME menu editing tool ii evolution-data-server 2.22.2-1 evolution database backend server ii gnome-applets 2.22.1-2 Various applets for GNOME 2 panel ii gnome-icon-theme 2.22.0-1 GNOME Desktop icon theme ii gnome-session 2.22.2-1 The GNOME 2 Session Manager -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484119: (regression?) `ephy_window_get_active_embed' implicitly converted to pointer
Package: seahorse Version: 2.22.2-1 Severity: serious Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. This is often due to a missing function prototype definition. For more information, see [2]. Function `ephy_window_get_active_embed' implicitly converted to pointer at seahorse-extension.c:242 This appears to be a regression of #477113. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483444: backup image
On Thu, May 29, 2008 at 04:08:03AM +0800, [EMAIL PROTECTED] wrote: Package: linux-image-2.6-686 Version: 2.6.25+14 Severity: wishlist Maybe having a backup kernel in sid would be wise?: Apparently there is now only one linux-image-2.6.*-*-686 available on sid. Each time a new kernel comes out all older ones are removed. This is nice except in the case where the user e.g., finds he can't always boot with the new kernel. He was able to boot with it yesterday, so removed his old one, but this morning it took several boots to succeed, and now he wants to install back the earlier kernel... Keep a kernel that you know works installed then. Also one wants to only have packages installed that are in the archive, according to apt-show-versions. Sounds like a personal conflict for you, not Debian users in general. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483410: [Secure-testing-team] Bug#483410: CVE-2008-1105: Boundary failure when parsing SMB responses can result in a buffer overrun
On Wed, May 28, 2008 at 08:20:10PM +0200, Christian Perrier wrote: What about sarge? It is affected as well (samba is 3.0.14 there) but is it still officially supported wrt security updates? sarge security support ended about 2 months ago -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482577: pending notation
Package: security-tracker I've been trying to use the tracker repository more actively for tracking kernel updates and so far it is going pretty well. One feature request I have is the ability to mark an issue as pending. Usually multiple issues are queued up for a kernel DSA, and its nice to be able to filter out issues that have already been committed to the kernel repository. I know I could use NOTEs for this, but I'd prefer to be able to note this on a per-package basis. Something like the following would work for my use case: CVE-2008-2136 (Memory leak in the ipip6_rcv function in net/ipv6/sit.c in the Linux ...) - linux-2.6 unfixed - linux-2.6 unfixed (pending 2.6.18.dfsg.1-18etch5) - linux-2.6.24 unfixed (pending 2.6.24-6~etchnhalf.3) NOTE: Upstream commit: 36ca34cc3b8335eb1fe8bd9a1d0a2592980c3f02 Or, maybe it makes more sense to add a new status - e.g. pending instead of unfixed; I don't have enough experience with the tracker to say for sure. (And I realize that I could write my own tool to cross-reference the security tracker w/ the kernel repository, but hey - I'm lazy.. and this might be a good feature for the tracker in general). -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425534: EXT3 filesystem corruption
On Wed, May 21, 2008 at 02:32:52AM -0600, dann frazier wrote: On Wed, May 21, 2008 at 12:29:33PM +0800, Steven Wilton wrote: Hi, I added a response to the following bug report about 6 months ago, and was wondering if it can be resolved: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425534 The bug is a documented race condition in ext3, with a patch that has been applied upstream, which I thought might be considered important enough to fix. I would imagine that it woud not cause problems for a lot of users, who would either not hit the race condition, or it would be corrected (and possibly ignored) when the machine runs a fsck on reboot. Corruption fixes are definitely reasonable for stable updates, I'll take a look at porting this. Thanks for tracking it down. I read through the bug report and the lkml threads, but I don't see a connection between #425534 (which causes filesystem corruption) and the issue in http://lkml.org/lkml/2006/12/29/26 (which appears to cause internal file corruption)- can you elaborate on why you believe they are connected? -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482303: luatex: getpwnam() implicitly converted to pointer
Package: luatex Version: 0.25.2-1 Severity: important Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `getpwnam' implicitly converted to pointer at ../../../src/texk/kpathsea/tilde.c:103 This is often due to a missing function prototype definition. For more information, see [2]. luatex provides its own pwd.h file which is getting included instead of the system pwd.h file and does not include a prototype for getpwnam(). If the luatex pwd.h file is not available in the include path, the system one gets properly included: Here's the compilation w/ the luatex pwd.h in the path: [EMAIL PROTECTED]:/tmp/luatex-0.25.2/build/texk/kpathsea# /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../src/texk/kpathsea -I.. -I../../../src/texk/kpathsea/.. -g -Wall -O2 -DMAKE_KPSE_DLL -c ../../../src/texk/kpathsea/tilde.c gcc -DHAVE_CONFIG_H -I. -I.. -I../../../src/texk/kpathsea/.. -g -Wall -O2 -DMAKE_KPSE_DLL -c ../../../src/texk/kpathsea/tilde.c -o tilde.o ../../../src/texk/kpathsea/tilde.c: In function 'kpse_tilde_expand': ../../../src/texk/kpathsea/tilde.c:103: warning: implicit declaration of function 'getpwnam' ../../../src/texk/kpathsea/tilde.c:103: warning: cast to pointer from integer of different size echo timestamp tilde.lo [EMAIL PROTECTED]:/tmp/luatex-0.25.2/build/texk/kpathsea# Here's the compilation w/ '-I../../../src/texk/kpathsea' omitted: [EMAIL PROTECTED]:/tmp/luatex-0.25.2/build/texk/kpathsea# /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../../src/texk/kpathsea/.. -g -Wall -O2 -DMAKE_KPSE_DLL -c ../../../src/texk/kpathsea/tilde.cgcc -DHAVE_CONFIG_H -I. -I.. -I../../../src/texk/kpathsea/.. -g -Wall -O2 -DMAKE_KPSE_DLL -c ../../../src/texk/kpathsea/tilde.c -o tilde.o echo timestamp tilde.lo [EMAIL PROTECTED]:/tmp/luatex-0.25.2/build/texk/kpathsea# [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482311: luatex: check_isnode() implicitly converted to pointer
Package: luatex Version: 0.25.2-1 Severity: important Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `check_isnode' implicitly converted to pointer at ../../../../src/texk/web2c/luatexdir/lua/llanglib.c:168 This is often due to a missing function prototype definition. For more information, see [2]. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions -- dann frazier diff -urpN luatex-0.25.2.orig/src/texk/web2c/luatexdir/luatex-api.h luatex-0.25.2/src/texk/web2c/luatexdir/luatex-api.h --- luatex-0.25.2.orig/src/texk/web2c/luatexdir/luatex-api.h 2008-04-10 08:37:41.0 -0600 +++ luatex-0.25.2/src/texk/web2c/luatexdir/luatex-api.h 2008-05-21 12:51:06.0 -0600 @@ -3,6 +3,7 @@ #include stdlib.h #include stdio.h #include stdarg.h +#include ptexlib.h #include ../lua51/lua.h #include ../lua51/lauxlib.h #include ../lua51/lualib.h @@ -73,6 +74,7 @@ extern void tokenlist_to_lua(lua_State extern void tokenlist_to_luastring(lua_State *L, int p) ; extern int tokenlist_from_lua(lua_State *L); +extern halfword *check_isnode (lua_State *L, int ud); extern void lua_nodelib_push (lua_State *L) ; extern int luaopen_node (lua_State *L); extern void nodelist_to_lua (lua_State *L, int n) ;
Bug#383090: patch, severity raise
tag 383090 + patch severity 383090 serious usertag 383090 + intend-to-nmu thanks Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. I'm no longer seeing a build failure when removing -DGNOME_DISABLE_DEPRECATED - perhaps this was fixed with the NMU that resolved #444511. Therefore I propose the following patch. I'll plan to NMU with this patch in a week's time, or sooner if requested by the maintainer. -- dann frazier diff -urpN lock-keys-applet-1.0.orig/src/Makefile.am lock-keys-applet-1.0/src/Makefile.am --- lock-keys-applet-1.0.orig/src/Makefile.am 2008-05-20 13:12:02.0 -0600 +++ lock-keys-applet-1.0/src/Makefile.am 2008-05-20 13:12:16.0 -0600 @@ -1,6 +1,5 @@ INCLUDES = -I$(top_srcdir) -I$(includedir) $(LK_APPLET_CFLAGS) \ -DGNOMELOCALEDIR=\$(datadir)/locale\ \ - -DGNOME_DISABLE_DEPRECATED \ -DGDK_DISABLE_DEPRECATED \ -DG_DISABLE_DEPRECATED \ -DDATADIR=\$(datadir)/\ \ diff -urpN lock-keys-applet-1.0.orig/src/Makefile.in lock-keys-applet-1.0/src/Makefile.in --- lock-keys-applet-1.0.orig/src/Makefile.in 2008-05-20 13:12:02.0 -0600 +++ lock-keys-applet-1.0/src/Makefile.in 2008-05-20 13:12:20.0 -0600 @@ -173,7 +173,6 @@ sysconfdir = @sysconfdir@ target_alias = @target_alias@ INCLUDES = -I$(top_srcdir) -I$(includedir) $(LK_APPLET_CFLAGS) \ -DGNOMELOCALEDIR=\$(datadir)/locale\ \ - -DGNOME_DISABLE_DEPRECATED \ -DGDK_DISABLE_DEPRECATED \ -DG_DISABLE_DEPRECATED \ -DDATADIR=\$(datadir)/\ \
Bug#481957: pcmanfm: file_properties_dlg_new() implicitly converted to pointer
Package: pcmanfm Version: 0.4.1.1-1 Severity: serious Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `file_properties_dlg_new' implicitly converted to pointer at main.c:485 Function `file_properties_dlg_new' implicitly converted to pointer at main.c:485 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions --- pcmanfm-0.4.1.1.orig/src/main.c 2008-03-14 16:59:55.0 -0600 +++ pcmanfm-0.4.1.1/src/main.c 2008-05-19 13:11:36.0 -0600 @@ -39,6 +39,8 @@ #include ptk-utils.h #include ptk-app-chooser.h +#include ptk-file-properties.h +#include ptk-file-menu.h #include settings.h
Bug#481972: xfce4-notes-plugin: implicit pointer conversions
Package: xfce4-notes-plugin Version: 1.6.2-1 Severity: serious Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `xfce_hvbox_new' implicitly converted to pointer at panel-plugin.c:151 Function `xfce_arrow_button_new' implicitly converted to pointer at panel-plugin.c:154 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions diff -urpN xfce4-notes-plugin-1.6.2.orig/panel-plugin/panel-plugin.c xfce4-notes-plugin-1.6.2/panel-plugin/panel-plugin.c --- xfce4-notes-plugin-1.6.2.orig/panel-plugin/panel-plugin.c 2008-04-29 17:35:11.0 -0600 +++ xfce4-notes-plugin-1.6.2/panel-plugin/panel-plugin.c 2008-05-19 14:14:17.0 -0600 @@ -23,6 +23,9 @@ #include config.h #endif +#include libxfce4panel/xfce-hvbox.h +#include libxfce4panel/xfce-arrow-button.h + #include defines.h #include notes.h #ifdef HAVE_XFCONF
Bug#479773: severity of 479773 is important
# Automatically generated email from bts, devscripts version 2.10.26 # SRM team considers missing hardware support to be important severity 479773 important -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464923: please test a snapshot build
On Thu, Apr 24, 2008 at 12:03:47PM -0600, dann frazier wrote: On Tue, Apr 22, 2008 at 05:20:53PM -0600, dann frazier wrote: A fix for this was committed last night and should appear in an etch snapshot build in the next few hours. If you are able to reproduce this bug, please test a snapshot build and provide results back to this report. Information about installing snapshot builds is available at: http://wiki.debian.org/DebianKernel This patch will appear in packages with version 2.6.18.dfsg.1-21~snapshot.3 or greater. amd64 snapshots with this fix still don't appear to be available, but I've posted some local builds here for testing: http://people.debian.org/~dannf/bugs/464923/ ping - anyone available to test this snapshot so that we can get it into etch? -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#478401: Segment fault on grub-probe
On Mon, Apr 28, 2008 at 07:28:30PM -0430, Isaac M. Marcos wrote: Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-6 grub: 0.97-36 On an upgrade from 2.6.24-5 towards 2.6.24-6, the postinst breaks at grub-probe because it gets a segfault. Configuring linux-image-2.6.24-1-amd64 (2.6.24-6) ... Running depmod. [.] Not updating image symbolic links since we are being updated/reinstalled (2.6.24-5 was configured last, according to dpkg) Running postinst hook script update-grub. Searching for GRUB installation directory ... found: /boot/grub User postinst hook script [update-grub] exited with value 139 Aditional Info: After several test, i found the problem to be related to grub-probe # grub --version grub (GNU GRUB 0.97) # grub-probe -V grub-probe (GRUB) 1.96 # grub-probe /dev/sda Violaci??n de segmento Relevant Kernel Syslog: Apr 28 19:16:07 dsktop01 kernel: grub-probe[30816]: segfault at 78 rip 41886c rsp 7fff7e2961c0 error 4 Same kernel message (different numbers) testing from shell prompt. What else to test, try? What version of grub-common do you have installed? Is this possibly the same issue as http://bugs.debian.org/474343 ? -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466404: RTNL: assertion failed at net/ipv4/devinet.c when using bonding
Version: 2.6.23-1 On Sat, Apr 26, 2008 at 01:34:44PM +0100, Duncan Gibb wrote: We can reproduce this bug - or something remarkably similar - in a running (as opposed to newly booting) system of a different architecture to the original reporter. Thanks Duncan. git-bisect points to this change as a fix: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0b0eef66419e9abe6fd62bc958ab7cd0a18f858e This change first appeared in 2.6.23. Since this is a non-trivial fix (lots of rewriting) and its not known to cause any real problems, I don't think it would be a candidate for etch's 2.6.18. Using mode 5 maybe a workaround for this issue, if it meets your requirements. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464923: please test a snapshot build
On Tue, Apr 22, 2008 at 05:20:53PM -0600, dann frazier wrote: A fix for this was committed last night and should appear in an etch snapshot build in the next few hours. If you are able to reproduce this bug, please test a snapshot build and provide results back to this report. Information about installing snapshot builds is available at: http://wiki.debian.org/DebianKernel This patch will appear in packages with version 2.6.18.dfsg.1-21~snapshot.3 or greater. amd64 snapshots with this fix still don't appear to be available, but I've posted some local builds here for testing: http://people.debian.org/~dannf/bugs/464923/ -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469415: intent to NMU
Version: 2:2.4.0-1 On Wed, Apr 23, 2008 at 10:55:50AM +0100, Rob Bradford wrote: On Mon, 2008-04-21 at 18:50 -0600, dann frazier wrote: usertag 469415 + intend-to-nmu thanks hey, As this bug has been open with a patch for over a month and without a rejection from the maintainer, I intend to NMU the associated package in a week's time (or sooner, if requested by the maintainer). If you do not wish for this NMU to occur, please send a follow-up in the bug report stating as such or, better yet, fix it in an MU :) Please don't. a.) At least not like this (use a debian/patches patch) b.) Anjuta 2.4.1 will be uploaded soon. c.) The patch should be filed upstream and accepted by the upstream maintainers for inclusion in the stable release before i'd even consider patching downstream. And then only until the next stable release. d.) Already fixed in 2.4.0 :) -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472568: intent to NMU
On Tue, Apr 22, 2008 at 07:54:55AM +0200, Christian Perrier wrote: Quoting dann frazier ([EMAIL PROTECTED]): usertag 472578 + intend-to-nmu thanks hey, As this bug has been open with a patch for about a month and has no rejection from the maintainer, I intend to NMU the associated package in a week's time (or sooner, if requested by the maintainer). If you do not wish for this NMU to occur, please send a follow-up in the bug report stating as such or, better yet, fix it in an MU :) I think you can safely go for it. I NMU'ed that package some weeks ago, for l10n stuff, without any news from the maintainer. So, either he's MIA, or he's OK for low threshold NMUs... Thanks Christian, advice taken. Patch attached. -- dann frazier diff -u gnarwl-3.3/debian/changelog gnarwl-3.3/debian/changelog --- gnarwl-3.3/debian/changelog +++ gnarwl-3.3/debian/changelog @@ -1,3 +1,11 @@ +gnarwl (3.3-8.5) unstable; urgency=low + + * Non-maintainer upload. + * Define LDAP_DEPRECATED in order to continue using +deprecated prototypes. Closes: #472568 + + -- dann frazier [EMAIL PROTECTED] Tue, 22 Apr 2008 01:29:55 -0600 + gnarwl (3.3-8.4) unstable; urgency=low * Non-maintainer upload to fix pending l10n issues. only in patch2: unchanged: --- gnarwl-3.3.orig/src/dbaccess.c +++ gnarwl-3.3/src/dbaccess.c @@ -7,6 +7,7 @@ #include unistd.h #include stdio.h #include string.h +#define LDAP_DEPRECATED 1 #include ldap.h #include lber.h
Bug#469410: intent to NMU
usertag 469410 - intend-to-nmu usertag 469410 + maintainer-opposes-nmu thanks On Tue, Apr 22, 2008 at 08:12:18AM +0200, Andrea Colangelo wrote: Please, don't NMU gbemol now. I am in contact with upstream to have this (and more) patch(es) in the next release. I plan to update the package within a couple of weeks in case upstream doesn't release it before. Sure, thanks for the response. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
