Bug#418021: title
The title of this bug is misleading. Package: libx11-6 Version: 2:1.0.3-6 Severity: important It should read: Package: libx11-6 Version: 2:1.0.3-7 Severity: important -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418238: [PATCH] auto.smb unable to handle double spaces and default window shares
Package: autofs
Version: 4.1.4+debian-1
Attached is a patch to fix auto.smb so it can handle double spaces in file share
names (using gsub instead of sub) and also default administration shares.
Autofs did not like the "$" symbol in front of the default window share names.
--CUT--
$SMBCLIENT $smbclientopts -gL $key 2>/dev/null \
| awk -v key="$key" -v opts="$mountopts" -F'|' -- '
BEGIN { ORS=""; first=1 }
/Disk/ { if (first) { print opts; first=0 };
gsub(/ /, "\\ ", $2);
sub(/\$/, "\\$", $2);
print " \\\n\t /" $2, "://" key "/" $2 }
END { if (!first) print "\n"; else exit 1 }
'
--CUT--
Best Regards.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414669: acknowledged by developer (closing 414669)
Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > #414669: [PATCH] missing link for libwfb.so, > which was filed against the nvidia-glx package. > > It has been marked as closed by one of the developers, namely > Randall Donald <[EMAIL PROTECTED]>. > > You should be hearing from them with a substantive response shortly, > in case you haven't already. If not, please contact them directly. > > Debian bug tracking system administrator > (administrator, Debian Bugs database) > > Sorry, this bug is still open. Please re-open. I accidentally replied to close the wrong one. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414670: Acknowledgement (Unable to load "xf86ExecX86int10")
Debian Bug Tracking System wrote: > Thank you for the problem report you have sent regarding Debian. > This is an automatically generated reply, to let you know your message has > been received. It is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Randall Donald <[EMAIL PROTECTED]> > > If you wish to submit further information on your problem, please send > it to [EMAIL PROTECTED] (and *not* to > [EMAIL PROTECTED]). > > If you have filed this report in error and wish to close it, please > send mail to [EMAIL PROTECTED] with an explanation > why the bug report should be closed. > > Please do not reply to the address at the top of this message, > unless you wish to report a problem with the Bug-tracking system. > > Debian bug tracking system administrator > (administrator, Debian Bugs database) > > Please close. This is a bug with the following patch (42_build_int10_submodules.diff) in xserver-xorg-core-1.1.1-20. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#416066: nfssvc: writing fds to kernel failed
Steinar H. Gunderson wrote: > On Sat, Mar 24, 2007 at 09:00:22AM -0700, C.Y.M wrote: >> After I updated to the latest stable kernel (2.6.20.4), I have been noticing >> the >> follow errors in syslog. Did the api change? Is there a patch for >> nfs-kernel-server? I did not have this problem with 2.6.17.14 kernels and >> nfs. >> >> nfsd[16801]: nfssvc: writing fds to kernel failed: errno 0 (Success) > > That's odd. There was a bug for this in the kernel at some point, but it was > fixed. Could you please contact upstream? The patch must have gotten lost at > some point. > > (In any case, this is not an nfs-utils bug; it's in the kernel.) > > /* Steinar */ Thanks. I have tried a newer kernel (2.6.21-rc5) and the problem is fixed. There must be a bug in kernel 2.6.20.4. Please close. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#416066: nfssvc: writing fds to kernel failed
Package: nfs-kernel-server Version: 1.0.12-4+b1 After I updated to the latest stable kernel (2.6.20.4), I have been noticing the follow errors in syslog. Did the api change? Is there a patch for nfs-kernel-server? I did not have this problem with 2.6.17.14 kernels and nfs. nfsd[16801]: nfssvc: writing fds to kernel failed: errno 0 (Success) Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#416061: [PATCH] fix for kernel 2.6.19+
Package: lufs-source
Version: 0.9.7-8.1
Attached is a patch to fix the api in lufs to build with kernels 2.6.19+ (the
patch for 2.6.18 is not included, refer to bug #388389).
Regards.
--- lufs/kernel/Linux/2.6/inode.c.orig 2007-03-24 07:15:06.0 -0700
+++ lufs/kernel/Linux/2.6/inode.c 2007-03-24 07:15:30.0 -0700
@@ -178,7 +178,6 @@
inode->i_ctime.tv_sec = fattr->f_ctime;
inode->i_mtime.tv_sec = fattr->f_mtime;
inode->i_atime.tv_sec = fattr->f_atime;
-inode->i_blksize = fattr->f_blksize;
inode->i_blocks = fattr->f_blocks;
inode->i_size = fattr->f_size;
--- lufs/kernel/Linux/2.6/file.c.orig 2007-03-24 07:15:13.0 -0700
+++ lufs/kernel/Linux/2.6/file.c 2007-03-24 07:16:56.0 -0700
@@ -254,7 +254,7 @@
TRACE("in\n");
if(!(res = lu_revalidate_inode(dentry)))
- res = generic_file_read(filp, buf, count, ppos);
+ res = do_sync_read(filp, buf, count, ppos);
TRACE("out\n");
@@ -284,7 +284,7 @@
TRACE("in\n");
if(!(res = lu_revalidate_inode(dentry)) && (count > 0))
- res = generic_file_write(filp, buf, count, ppos);
+ res = do_sync_write(filp, buf, count, ppos);
TRACE("out\n");
Bug#416055: [PATCH] fix for kernel 2.6.19+
Package: cdfs-src
Version: 2.4.20.a+2.6.18-1
Attached is a patch to fix cdfs so it builds with kernels 2.6.19+.
Regards.
diff -ru cdfs/2.6/audio.c cdfs-2.6.20/audio.c
--- cdfs/2.6/audio.c 2006-10-24 12:44:49.0 -0700
+++ cdfs-2.6.20/2.6/audio.c 2006-12-11 12:30:47.0 -0800
@@ -167,7 +167,8 @@
/***/
struct file_operations cdfs_cdda_file_operations = {
-.read = generic_file_read,
+.read = do_sync_read,
+.aio_read = generic_file_aio_read,
.mmap = generic_file_mmap,
};
diff -ru cdfs/2.6/cddata.c cdfs-2.6.20/cddata.c
--- cdfs/2.6/cddata.c 2005-05-01 13:58:24.0 -0700
+++ cdfs-2.6.20/2.6/cddata.c 2006-12-11 12:30:47.0 -0800
@@ -76,7 +76,8 @@
struct file_operations cdfs_cddata_file_operations = {
- .read = generic_file_read,
+ .read = do_sync_read,
+ .aio_read = generic_file_aio_read,
#ifdef OLD_KERNEL
.mmap = generic_file_mmap
#else
diff -ru cdfs/2.6/cdfs.h cdfs-2.6.20/cdfs.h
--- cdfs/2.6/cdfs.h 2006-10-24 12:44:49.0 -0700
+++ cdfs-2.6.20/2.6/cdfs.h 2006-12-11 12:34:11.0 -0800
@@ -13,7 +13,7 @@
#endif
#ifndef CONFIG_CDFS_VERSION
-#define CONFIG_CDFS_VERSION "2.6.18"
+#define CONFIG_CDFS_VERSION "2.6.19"
#endif
diff -ru cdfs/2.6/cdXA.c cdfs-2.6.20/cdXA.c
--- cdfs/2.6/cdXA.c 2006-10-24 12:44:49.0 -0700
+++ cdfs-2.6.20/2.6/cdXA.c 2006-12-11 12:30:47.0 -0800
@@ -26,7 +26,8 @@
#include "cdfs.h"
struct file_operations cdfs_cdXA_file_operations = {
-.read = generic_file_read,
+.read = do_sync_read,
+.aio_read = generic_file_aio_read,
.mmap = generic_file_mmap,
};
diff -ru cdfs/2.6/hfs.c cdfs-2.6.20/hfs.c
--- cdfs/2.6/hfs.c 2005-05-01 13:58:24.0 -0700
+++ cdfs-2.6.20/2.6/hfs.c 2006-12-11 12:30:47.0 -0800
@@ -194,7 +194,8 @@
/***/
struct file_operations cdfs_cdhfs_file_operations = {
- .read = generic_file_read,
+ .read = do_sync_read,
+ .aio_read = generic_file_aio_read,
.mmap = generic_file_mmap
};
Bug#414669: xorg
The problem turned out to be a bad patch introduced in xserver-xorg-core. Please close. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414782: 42_build_int10_submodules.diff
I tried removing 42_build_int10_submodules.diff from the patches and rebuild everything but I still had the same problem. Was there more to revert than just taking out this patch? I would be happy to test this if I could revert it back all the way. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#410879: 410879
I am having the same problem. Although I see one other bug in your log file that is part of the nvidia-glx package. I have submitted a patch to fix the libwfb.so missing file error. Refer to bug# 414669 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#410879: Unable to load "xf86ExecX86int10"
Additional info as requested. Thank you. X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: UNKNOWN Current Operating System: Linux nofear 2.6.17.14.20070307.1 #1 PREEMPT Wed Mar 7 17:02:35 PST 2007 i686 Build Date: 07 March 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 12 23:27:11 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "nvidia0" (**) |-->Screen "Screen1" (1) (**) | |-->Monitor "Monitor1" (**) | |-->Device "nvidia1" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xorg" (**) XKB: rules: "xorg" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Configured Mouse" (**) |-->Input Device "Generic Mouse" (**) FontPath set to: /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, /usr/share/fonts/X11/misc/:unscaled, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi (==) RgbPath set to "/etc/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.0 X.Org XInput driver : 0.6 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 7.1.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.0 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,3099 card 1106,3099 rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b099 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:0b:0: chip 10b7,9050 card , rev 00 class 02,00,00 hdr 00 (II) PCI: 00:0e:0: chip 1131,7146 card 13c2,0003 rev 01 class 04,80,00 hdr 00 (II) PCI: 00:11:0: chip 1106,3074 card 1106,3074 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:1: chip 1106,0571 card 1106,0571 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:11:2: chip 1106,3038 card 0925,1234 rev 1b class 0c,03,00 hdr 00 (II) PCI: 00:11:3: chip 1106,3038 card 0925,1234 rev 1b class 0c,03,00 hdr 00 (II) PCI: 00:11:4: chip 1106,3038 card 0925,1234 rev 1b class 0c,03,00 hdr 00 (II) PCI: 00:11:5: chip 1106,3059 card 1297,a232 rev 30 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0322 card 1462,9980 rev a1 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xec00 - 0xedff (0x200) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xe000 - 0xe7ff (0x800) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(1:0:0) nVidia Corporation NV34 [GeForce FX 5200] rev 161, Mem @ 0xec00/24, 0xe000/27 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B] [1] -1 0 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0
Bug#414782: Unable to load "xf86ExecX86int10"
Package: xserver-xorg-core Version: 1.1.1-20 I am having the following problem loading the int10 submodule with the all my different nvidia drivers. The nvidia developers tell me this is an issue with xserver-xorg-core. This is what Xorg.0.log has in it. I do not see any errors about missing symbols, but there must be something missing. (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/lib/xorg/modules/libint10.so (WW) NVIDIA(1): Unable to load "xf86ExecX86int10". (EE) NVIDIA(1): Unable to initialize the X Int10 module; the console may not (EE) NVIDIA(1): be restored correctly on your TV. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414670: Unable to load "xf86ExecX86int10"
Package: nvidia-glx Version: 1.0.9746-2 I am having the following problem loading the int10 submodule with the latest nvidia drivers. I can not determine if this is an issue with nvidia or with xserver-xorg-core. ii xserver-xorg-core 1.1.1-20 X.Org X server -- core server This is what Xorg.0.log has in it. I do not see any errors about missing symbols, but there must be something missing. (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/lib/xorg/modules/libint10.so (WW) NVIDIA(1): Unable to load "xf86ExecX86int10". (EE) NVIDIA(1): Unable to initialize the X Int10 module; the console may not (EE) NVIDIA(1): be restored correctly on your TV. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#414669: [PATCH] missing link for libwfb.so
Package: nvidia-glx Version: 1.0.9746-2 I was getting a error in Xorg.0.log about a missing shared object. The problem is that nvidia names the .so differently. The attached patch fixes the problem. --- nvidia-graphics-drivers-1.0.9746/debian/nvidia-glx.links.in 2007-03-13 00:03:21.0 -0700 +++ nvidia-graphics-drivers-1.0.9755/debian/nvidia-glx.links.in 2007-03-12 22:53:08.0 -0700 @@ -2,6 +2,7 @@ usr/lib/libGLcore.so.#VERSION# usr/lib/libGLcore.so.1 usr/lib/libnvidia-tls.so.#VERSION# usr/lib/libnvidia-tls.so.1 usr/lib/xorg/modules/extensions/libglx.so.#VERSION# usr/lib/xorg/modules/extensions/libglx.so +usr/lib/xorg/modules/libnvidia-wfb.so.#VERSION# usr/lib/xorg/modules/libwfb.so usr/lib/libXvMCNVIDIA.so.#VERSION# usr/lib/libXvMCNVIDIA.so.1 usr/lib/libXvMCNVIDIA.so.#VERSION# usr/lib/libXvMCNVIDIA_dynamic.so.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#399815: hwclock not set before root is checked
Package: util-linux Version: 2.12r-14 When hwclock.sh was set to 11 (since we need / to be writable for the adjfile), it started causing timestamp errors when checking / on reboot (with S10checkroot.sh). This only affects systems with /usr on a separate partition and is related to bug # 342887. Version 2.12r-13 seems to work ok, but I can understand the problem you face. Although, setting the hwclock after checking / will always cause timestamp errors. The hwclock must be set before any drives can be scanned or else timestamp errors will occur. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#398677: nvidia-glx fixups
> > So, the libraries in /usr/lib/nvidia are not really used, but kept to store > the > "diverted" file? I guess I got confused when I saw this in /usr/lib/nvidia: > > -rw-r--r-- 1 root root 425320 2006-10-13 03:55 libGL.so.1.2.xlibmesa > lrwxrwxrwx 1 root root 19 2006-11-14 08:53 libGL.so.1.xlibmesa -> > /usr/lib/libGL.so.1 > lrwxrwxrwx 1 root root 17 2006-11-14 17:24 libGL.so.xlibmesa -> > /usr/lib/libGL.so > -rw-r--r-- 1 root root 493686 2006-10-16 19:23 libglx.so.xlibmesa > -rw-r--r-- 1 root root 107396 2006-11-14 19:33 libnvidia-cfg.so.1.0.9742 > -rw-r--r-- 1 root root 2324 2006-11-14 19:33 libnvidia-tls.so.1.0.9742 > -rwxr-xr-x 1 root root 3220 2006-11-14 19:33 tls_test > -rw-r--r-- 1 root root 3384 2006-11-14 19:33 tls_test_dso.so > > Note the links of libGL.so.*.xlibmesa. It didnt seem correct when I first > glanced at it. > Actually, this is what it looks like when I try to reinstall libgl1-mesa-glx (the nvidia-glx diversions cause this package to create a broken link in /usr/lib/nvidia). -rw-r--r-- 1 root root 425320 2006-10-13 03:55 libGL.so.1.2.xlibmesa lrwxrwxrwx 1 root root 12 2006-11-14 20:06 libGL.so.1.xlibmesa -> libGL.so.1.2 -rw-r--r-- 1 root root 493686 2006-10-16 19:23 libglx.so.xlibmesa Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#398677: nvidia-glx fixups
> >> 2) A diversion is created and referenced to /usr/lib/libGL.so.1.2 (but this >> link >> is never created in /usr/lib). > I'm not sure what you are getting at here. /usr/lib/libGL.so.1.2 from > libgl1-mesa-glx is diverted to /usr/lib/nvidia/libGL.so.1.2.xlibmesa > which shows up if libgl1-mesa-glx is installed. What link in /usr/lib > are you talking about? I'm sorry, I didnt understand the proper function of a "diversion". So if a package tries to install one of the "diverted" files, it gets placed in /usr/lib/nvidia (with an xlibmesa extension). > >> 3) Incorrect links are created in /usr/lib/nvidia for libGL.so.xlibmesa, >> libGL.so.1.xlibmesa, and libGL.so.1.2.xlibmesa. Should all of these >> "xlibmesa" >> library links refer to /usr/lib/libGL.so? >> > No, these are diversions of symlinks, not properly functioning ones. > > So, the libraries in /usr/lib/nvidia are not really used, but kept to store the "diverted" file? I guess I got confused when I saw this in /usr/lib/nvidia: -rw-r--r-- 1 root root 425320 2006-10-13 03:55 libGL.so.1.2.xlibmesa lrwxrwxrwx 1 root root 19 2006-11-14 08:53 libGL.so.1.xlibmesa -> /usr/lib/libGL.so.1 lrwxrwxrwx 1 root root 17 2006-11-14 17:24 libGL.so.xlibmesa -> /usr/lib/libGL.so -rw-r--r-- 1 root root 493686 2006-10-16 19:23 libglx.so.xlibmesa -rw-r--r-- 1 root root 107396 2006-11-14 19:33 libnvidia-cfg.so.1.0.9742 -rw-r--r-- 1 root root 2324 2006-11-14 19:33 libnvidia-tls.so.1.0.9742 -rwxr-xr-x 1 root root 3220 2006-11-14 19:33 tls_test -rw-r--r-- 1 root root 3384 2006-11-14 19:33 tls_test_dso.so Note the links of libGL.so.*.xlibmesa. It didnt seem correct when I first glanced at it. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#398677: nvidia-glx fixups
Package: nvidia-glx-dev Version: 1.0.8776-1 There are a few minor bugs that should be cleaned up in the debian packaging scripts for nvidia. 1) nvidia-glx-dev.links and nvidia-glx-dev.links.in create malformed links because a "#" exists before the link name in the links file. Also, the second line in the file which creates a link to nvidia includes in incorrect. Both lines should be removed from nvidia-glx-dev.links(.in). 2) A diversion is created and referenced to /usr/lib/libGL.so.1.2 (but this link is never created in /usr/lib). 3) Incorrect links are created in /usr/lib/nvidia for libGL.so.xlibmesa, libGL.so.1.xlibmesa, and libGL.so.1.2.xlibmesa. Should all of these "xlibmesa" library links refer to /usr/lib/libGL.so? Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396384: [Patch] rules in debian.binary do not apply patches
Package: nvidia-kernel-source Version: 1.0.9625-2 Severity: important The paths are incorrect in the build rules when trying to apply the debian patches to the source code before building the nvidia-kernel module with make-kpkg. Also, the patches are not reversing properly when the rules cleans up. The attached patch fixes both problems. Best Regards. --- nvidia/debian.binary/rules.orig 2006-10-22 03:29:34.0 -0700 +++ nvidia/debian.binary/rules 2006-10-31 04:25:59.0 -0800 @@ -103,13 +103,13 @@ cd .. ; \ fi - if test -d $(CURDIR)/patches; \ + if test -d $(CURDIR)/debian/patches; \ then \ pwd; \ ls -al; \ -cd $(dirname)/usr/src/nv; \ -for i in $(CURDIR)/patches/*; \ - do patch -p3 <$$i; \ +cd $(dirname); \ +for i in $(CURDIR)/debian/patches/*; \ + do patch -p3 -t <$$i; \ done; \ fi
Bug#327570: Acknowledgement (missing /usr/bin/tput when rebooting)
C.Y.M wrote: > This bug seems to have resurfaced with 2.86.ds1-33. Is this still a lsb-base > issue? Any idea how to fix it again? > As a workaround to this bug, I have rebuilt the ncurses-bin package to place tput in /bin/tput instead of /usr/bin/tput. Unless there is a better suggestion? Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327570: Acknowledgement (missing /usr/bin/tput when rebooting)
This bug seems to have resurfaced with 2.86.ds1-33. Is this still a lsb-base issue? Any idea how to fix it again? Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391795: nvidia-glx package conflicts with xorg 7.1
>
> When I look at the control file for nvidia-glx 1.0.8774-3 , I see the
> following:
>
> Package: nvidia-glx
> Architecture: i386 amd64
> Depends: nvidia-kernel-1.0.8762, x11-common (>= 1:7.0.0), ${shlibs:Depends}
> Suggests: nvidia-settings, nvidia-kernel-source (>= 1.0.8762)
> Conflicts: nvidia-glx-src
> Provides: xserver-xorg-video
> Replaces: nvidia-glx-src
> Description: NVIDIA binary XFree86 4.x driver
>
>
> I'm not sure where you are getting the "xserver-xorg-video-1.0" from (because
> the control file for nvidia-glx says "xserver-xorg-video"). But I do see the
> problem now.. Its not that xserver-xorg-core is providing
> "xserver-xorg-video",
> it is because xserver-xorg-core conflicts with the virtual xserver-xorg-video
> package provided by nvidia-glx.
>
I just re-downloaded the source code to be sure and discovered that the problem
is that the "control.in" file is correct, but the "control" file is not. This
patch fixes the conflict with xorg 7.1:
--- nvidia-graphics-drivers-1.0.8774.orig/debian/control2006-10-09
06:31:35.0 -0700
+++ nvidia-graphics-drivers-1.0.8774/debian/control 2006-10-09
06:32:54.0 -0700
@@ -34,7 +34,7 @@
Depends: nvidia-kernel-1.0.8762, x11-common (>= 1:7.0.0), ${shlibs:Depends}
Suggests: nvidia-settings, nvidia-kernel-source (>= 1.0.8762)
Conflicts: nvidia-glx-src
-Provides: xserver-xorg-video
+Provides: xserver-xorg-video-1.0
Replaces: nvidia-glx-src
Description: NVIDIA binary XFree86 4.x driver
These XFree86 4.0 / Xorg binary drivers provide optimized hardware
Best Regards.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391795: nvidia-glx package conflicts with xorg 7.1
Randall Donald wrote:
> On Sun, 2006-10-08 at 12:02 -0700, C.Y.M wrote:
>> Randall Donald wrote:
>>> On Sun, 2006-10-08 at 08:14 -0700, C.Y.M wrote:
>>>> Package: nvidia-glx
>>>> Version: 1.0.8774-3
>>>> Severity: important
>>>>
>>>> nvidia-glx package conflicts with xorg 7.1 because xorg now provides the
>>>> virtual
>>>> "xserver-xorg-video" package. A solution would be to remove
>>>> "xserver-xorg-video"
>>>> provides from the nvidia-glx package.
>>>>
>>>>
>> Yes, the xserver-xorg-core package now also provides the virtual
>> xserver-xorg-video package and its conflicting with nvidia-glx.
>>
> What versions are you using?
>
>>From dpkg -s xserver-xorg-core
>
> Version: 2:1.1.1-9
> Replaces: xserver-xorg (<< 6.8.2-38), xserver-xfree86 (<< 1:7.0.0)
> Provides: xserver
> Depends: x11-common (>= 1:7.0.0), libc6 (>= 2.3.5-1), libfontenc1,
> libxau6, libxdmcp6, libxfont1, zlib1g (>= 1:1.2.1)
> Recommends: xkb-data
> Conflicts: xserver-xorg (<< 6.8.2-38), xserver-xfree86 (<< 1:7.0.0),
> xserver-xorg-video
>
>
>>From dpkg -s nvidia-glx
>
> Version: 1.0.8774-3
> Provides: xserver-xorg-video-1.0
>
> I don't see the conflict.
>
When I look at the control file for nvidia-glx 1.0.8774-3 , I see the following:
Package: nvidia-glx
Architecture: i386 amd64
Depends: nvidia-kernel-1.0.8762, x11-common (>= 1:7.0.0), ${shlibs:Depends}
Suggests: nvidia-settings, nvidia-kernel-source (>= 1.0.8762)
Conflicts: nvidia-glx-src
Provides: xserver-xorg-video
Replaces: nvidia-glx-src
Description: NVIDIA binary XFree86 4.x driver
I'm not sure where you are getting the "xserver-xorg-video-1.0" from (because
the control file for nvidia-glx says "xserver-xorg-video"). But I do see the
problem now.. Its not that xserver-xorg-core is providing "xserver-xorg-video",
it is because xserver-xorg-core conflicts with the virtual xserver-xorg-video
package provided by nvidia-glx.
BR.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391795: nvidia-glx package conflicts with xorg 7.1
Randall Donald wrote: > On Sun, 2006-10-08 at 08:14 -0700, C.Y.M wrote: >> Package: nvidia-glx >> Version: 1.0.8774-3 >> Severity: important >> >> nvidia-glx package conflicts with xorg 7.1 because xorg now provides the >> virtual >> "xserver-xorg-video" package. A solution would be to remove >> "xserver-xorg-video" >> provides from the nvidia-glx package. >> > > Are you saying that they have gone back from xserver-xorg-video-1.0 to > xserver-xorg-video again? > > >> Yes, the xserver-xorg-core package now also provides the virtual xserver-xorg-video package and its conflicting with nvidia-glx. Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391795: nvidia-glx package conflicts with xorg 7.1
Package: nvidia-glx Version: 1.0.8774-3 Severity: important nvidia-glx package conflicts with xorg 7.1 because xorg now provides the virtual "xserver-xorg-video" package. A solution would be to remove "xserver-xorg-video" provides from the nvidia-glx package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388386: [patch]
Eduard Bloch wrote: > #include > * C.Y.M [Wed, Sep 20 2006, 07:33:55PM]: >> This is a quick hack that solves the build problem with kernel 2.6.18. This >> is >> not a backwards compatible patch. > > Stupid question: why do you need LUFS? I consider requesting its removal > because almost everything has moved to FUSE or can be used with lufis, > the fuse/lufs bridge. > I wanted a way to mount ftp sites with autofs (which has scripts utilizing lufs). BR. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388386: [patch]
C.Y.M wrote:
> This is a quick hack that solves the build problem with kernel 2.6.18. This
> is
> not a backwards compatible patch.
>
Apparently, The 2.6.18 stats callback parameters have changed from 2.6.17 so
that it takes a struct dentry* rather than a struct super_block.
Revised patch applied for 2.6.18.
Best Regards.
--- lufs/kernel/Linux/2.6/inode.c 2006-10-05 04:10:30.0 -0700
+++ lufs.new/kernel/Linux/2.6/inode.c 2006-10-05 04:07:27.0 -0700
@@ -53,7 +53,7 @@
static void lu_delete_inode(struct inode*);
static void lu_put_super(struct super_block*);
-static int lu_statfs(struct super_block*, struct statfs*);
+static int lu_statfs(struct dentry*, struct statfs*);
static struct super_operations lu_sops = {
.drop_inode = generic_drop_inode,
@@ -383,7 +383,7 @@
return res;
}
-static int lu_statfs(struct super_block *sb, struct statfs *attr)
+static int lu_statfs(struct dentry * dentry, struct statfs *attr)
{
TRACE("in\n");
@@ -510,9 +510,9 @@
return -EINVAL;
}
-static struct super_block *lu_get_sb(struct file_system_type *fs_type, int flags, char *dev_name, void *data)
+static int lu_get_sb(struct file_system_type *fs_type, int flags, char *dev_name, void *data, struct vfsmount *mnt)
{
-return get_sb_nodev(fs_type, flags, data, lu_fill_super);
+return get_sb_nodev(fs_type, flags, data, lu_fill_super, mnt);
}
static struct file_system_type lu_fs_type = {
Bug#388386: [patch]
This is a quick hack that solves the build problem with kernel 2.6.18. This is
not a backwards compatible patch.
Thanks.
--- lufs/kernel/Linux/2.6/inode.c.orig 2006-09-20 18:31:59.0 -0700
+++ lufs/kernel/Linux/2.6/inode.c 2006-09-20 18:33:02.0 -0700
@@ -510,9 +510,9 @@
return -EINVAL;
}
-static struct super_block *lu_get_sb(struct file_system_type *fs_type, int flags, char *dev_name, void *data)
+static struct super_block *lu_get_sb(struct file_system_type *fs_type, int flags, char *dev_name, void *data, struct vfsmount *mnt)
{
-return get_sb_nodev(fs_type, flags, data, lu_fill_super);
+return get_sb_nodev(fs_type, flags, data, lu_fill_super, mnt);
}
static struct file_system_type lu_fs_type = {
Bug#388389: [PATCH]
This is a patch that fixes the build problem with kernel 2.6.18. This is not a
backwards compatible patch.
Best Regards.
--- cdfs/2.6/root.c.orig 2006-09-20 18:15:33.0 -0700
+++ cdfs/2.6/root.c 2006-09-20 18:29:39.0 -0700
@@ -543,8 +543,8 @@
#ifdef OLD_KERNEL
static DECLARE_FSTYPE_DEV(cdfs_fs_type, FSNAME, cdfs_mount);
#else
-static struct super_block *cdfs_get_sb(struct file_system_type *fs_type, int flags, const char *dev_name, void *data) {
- return get_sb_bdev(fs_type, flags, dev_name, data, cdfs_fill_super);
+static struct super_block *cdfs_get_sb(struct file_system_type *fs_type, int flags, const char *dev_name, void *data, struct vfsmount *mnt) {
+ return get_sb_bdev(fs_type, flags, dev_name, data, cdfs_fill_super, mnt);
}
static struct file_system_type cdfs_fs_type = {
Bug#388388: cdfs files to build with 2.6.18 kernel release
Package: cdrs-src Version: 2.4.20.a+2.6.12-2 Severity: important Build fails with 2.6.18 kernel release. /usr/src/modules/cdfs/2.6/root.c:541: warning: initialization from incompatible pointer type /usr/src/modules/cdfs/2.6/root.c: In function `cdfs_get_sb': /usr/src/modules/cdfs/2.6/root.c:547: error: too few arguments to function `get_sb_bdev' /usr/src/modules/cdfs/2.6/root.c:547: warning: return makes pointer from integer without a cast /usr/src/modules/cdfs/2.6/root.c: At top level: /usr/src/modules/cdfs/2.6/root.c:553: warning: initialization from incompatible pointer type -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388389: cdfs files to build with 2.6.18 kernel release
Package: cdfs-src Version: 2.4.20.a+2.6.12-2 Severity: important Build fails with 2.6.18 kernel release. /usr/src/modules/cdfs/2.6/root.c:541: warning: initialization from incompatible pointer type /usr/src/modules/cdfs/2.6/root.c: In function `cdfs_get_sb': /usr/src/modules/cdfs/2.6/root.c:547: error: too few arguments to function `get_sb_bdev' /usr/src/modules/cdfs/2.6/root.c:547: warning: return makes pointer from integer without a cast /usr/src/modules/cdfs/2.6/root.c: At top level: /usr/src/modules/cdfs/2.6/root.c:553: warning: initialization from incompatible pointer type -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388386: build failure with 2.6.18 kernel release
Package: lufs-source Version: 0.9.7-8 Severity: important Build fails with kernel-2.6.18. /usr/src/modules/lufs/kernel/Linux/2.6/inode.c:62: warning: initialization from incompatible pointer type /usr/src/modules/lufs/kernel/Linux/2.6/inode.c:414:5: warning: "KERNEL_VERSION_CODE" is not defined /usr/src/modules/lufs/kernel/Linux/2.6/inode.c: In function `lu_get_sb': /usr/src/modules/lufs/kernel/Linux/2.6/inode.c:515: error: too few arguments to function `get_sb_nodev' /usr/src/modules/lufs/kernel/Linux/2.6/inode.c:515: warning: return makes pointer from integer without a cast /usr/src/modules/lufs/kernel/Linux/2.6/inode.c: At top level: /usr/src/modules/lufs/kernel/Linux/2.6/inode.c:521: warning: initialization from incompatible pointer type make[5]: *** [/usr/src/modules/lufs/kernel/Linux/2.6/inode.o] Error 1 make[4]: *** [_module_/usr/src/modules/lufs/kernel/Linux/2.6] Error 2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386613: Udev fails to load DVB firmware
Package: udev Version: 0.100-1 Severity: important Udev is unable to find firmware (/lib/firmware/dvb-ttpci-01.fw). DVB Drivers fail to load because hotplug does not work. The previous version of udev works fine. BR. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366931: Apt fails of 0 byte files
Michael Vogt wrote: > On Fri, May 12, 2006 at 12:59:42AM -0700, C.Y.M wrote: >> Package: apt >> Version: 0.6.44 >> Severity: important > > Thanks for your bugreport. > >> When I type "apt-get source", apt fails on the following: >> >> Reading package lists... Done >> Building dependency tree... Done >> E: Unable to parse package file >> /var/lib/apt/lists/sentinel.dk_debian_dists_unstable_contrib_source_Sources >> (2) >> E: Unable to parse package file >> /var/lib/apt/lists/sentinel.dk_debian_dists_unstable_non-free_source_Sources >> (2) >> >> >> If i go back to the previous version of apt, then it works fine. With the >> current version of apt, I am unable to get any source using "apt-get source". >> The twi files above that apt-get fails on are 0 byte files. > [..] > > Do I understand this correctly, the previous version worked with zero > size files? The new one does not? (it is not the new version that > incorrectly creates those zero byte files)? > That is correct, the zero byte files were always there from both versions of apt. The new version of apt is just unable to parse the zero byte files like the previous version can. BR. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366931: Apt fails of 0 byte files
Package: apt Version: 0.6.44 Severity: important When I type "apt-get source", apt fails on the following: Reading package lists... Done Building dependency tree... Done E: Unable to parse package file /var/lib/apt/lists/sentinel.dk_debian_dists_unstable_contrib_source_Sources (2) E: Unable to parse package file /var/lib/apt/lists/sentinel.dk_debian_dists_unstable_non-free_source_Sources (2) If i go back to the previous version of apt, then it works fine. With the current version of apt, I am unable to get any source using "apt-get source". The twi files above that apt-get fails on are 0 byte files. -rw-r--r-- 1 root root0 May 16 2005 sentinel.dk_debian_dists_unstable_contrib_binary-i386_Packages -rw-r--r-- 1 root root0 May 16 2005 sentinel.dk_debian_dists_unstable_contrib_source_Sources -rw-r--r-- 1 root root 6848 May 17 2005 sentinel.dk_debian_dists_unstable_main_binary-i386_Packages -rw-r--r-- 1 root root 2171 May 16 2005 sentinel.dk_debian_dists_unstable_main_source_Sources -rw-r--r-- 1 root root0 May 16 2005 sentinel.dk_debian_dists_unstable_non-free_binary-i386_Packages -rw-r--r-- 1 root root0 May 16 2005 sentinel.dk_debian_dists_unstable_non-free_source_Sources BR. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366222: dh_strip fails
Joey Hess wrote: > C.Y.M wrote: >> strip: debian/nvidia-glx/usr/lib/nvidia/stVEjyts: Bad value >> BFD: debian/nvidia-glx/usr/lib/nvidia/stVEjyts: The first section in the >> PT_DYNAMIC segment is not the .dynamic section > > I'll reassign this to the right package (you know, the one with strip in > it), but it looks to me like your elf binary is corrupt, maybe a broken > compiler or linker or it was built with the wrong options somehow? > > Unless you can give a recipe to reproduce this, the bug severity is > inflated. > To reproduce this try "apt-get source nvidia-glx" and then build it with "fakeroot dpkg-buildpackage". When I went back to the previous version of binutils, it fixed the problem. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366222: dh_strip fails
Steve Langasek wrote: > On Sat, May 06, 2006 at 02:41:58AM -0700, C.Y.M wrote: > >>> I don't think this is a bug in dh_strip; it looks like you have a buggy >>> binutils installed. I've been using this version of debhelper to build all >>> kinds of packages, without any errors of this kind; and in any case, the >>> error messages are from strip, not from dh_strip. > >>> There has been a binutils update in the past month, so it's possible this is >>> a change in binutils that only affects certain sorts of objects. I think >>> it's best to assign the bug there for further investigation. > >> Thanks for taking a look at this. Can you tell me what version of binutils >> you >> are using (assuming you are using Sid). > > I'm using binutils 2.16.1cvs20060413-1 in a variety of environments, and > haven't seen this error. You said that nvidia-glx was an "example" of > dh_strip failing. What other packages have you seen this problem with? > So far, the nvidia packages are the only ones I've seen with a problem. But, I reverted back to the previous release of binutils (binutils_2.16.1cvs20060117-1_i386) and you were right. Strip now works with the older version. Best Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366219: stip binary
Sorry for reporting this against the nvidia-glx package. This is a binutils problem. Please close this against the nvidia package. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366222: strip binary broken with latest binutils
Going back to binutils_2.16.1cvs20060117-1 fixed the strip problem. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366222: dh_strip fails
> I don't think this is a bug in dh_strip; it looks like you have a buggy > binutils installed. I've been using this version of debhelper to build all > kinds of packages, without any errors of this kind; and in any case, the > error messages are from strip, not from dh_strip. > > There has been a binutils update in the past month, so it's possible this is > a change in binutils that only affects certain sorts of objects. I think > it's best to assign the bug there for further investigation. > Thanks for taking a look at this. Can you tell me what version of binutils you are using (assuming you are using Sid). Best Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366222: dh_strip fails
Package: debhelper Version: 5.0.34 Severity: grave When building packages, dh_strip is now failing. For example, the nvidia-glx package: dh_testdir dh_testroot dh_installchangelogs dh_installdocs -s dh_installexamples dh_installdebconf dh_installinit dh_installman dh_link dh_strip BFD: debian/nvidia-glx/usr/lib/stL0AwHo: warning: allocated section `.bss' not in segment BFD: debian/nvidia-glx/usr/lib/nvidia/stVEjyts: The first section in the PT_DYNAMIC segment is not the .dynamic section strip: debian/nvidia-glx/usr/lib/nvidia/stVEjyts: Bad value BFD: debian/nvidia-glx/usr/lib/nvidia/stVEjyts: The first section in the PT_DYNAMIC segment is not the .dynamic section strip: debian/nvidia-glx/usr/lib/nvidia/stVEjyts: Bad value dh_strip: command returned error code 256 make[1]: *** [binary-common] Error 1 make[1]: Leaving directory `/var/local/nvidia-glx/nvidia-graphics-drivers-1.0.8756' make: *** [binary-arch] Error 2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366219: The first section in the PT_DYNAMIC segment is not the .dynamic section
Package: nvidia-glx Version: 1.0.8756-4 Severity: important When attempting to build nvidia drivers from the source, I get the following errors: dh_testdir dh_testroot dh_installchangelogs dh_installdocs -s dh_installexamples dh_installdebconf dh_installinit dh_installman dh_link dh_strip BFD: debian/nvidia-glx/usr/lib/stL0AwHo: warning: allocated section `.bss' not in segment BFD: debian/nvidia-glx/usr/lib/nvidia/stVEjyts: The first section in the PT_DYNAMIC segment is not the .dynamic section strip: debian/nvidia-glx/usr/lib/nvidia/stVEjyts: Bad value BFD: debian/nvidia-glx/usr/lib/nvidia/stVEjyts: The first section in the PT_DYNAMIC segment is not the .dynamic section strip: debian/nvidia-glx/usr/lib/nvidia/stVEjyts: Bad value dh_strip: command returned error code 256 make[1]: *** [binary-common] Error 1 make[1]: Leaving directory `/var/local/nvidia-glx/nvidia-graphics-drivers-1.0.8756' make: *** [binary-arch] Error 2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358831: bash operand errors (forwarded from C.Y.M)
C.Y.M wrote: > Chet Ramey wrote: >> Matthias Klose wrote: >>> C.Y.M writes: >>>> Reverting back to bash 3.0 fixes the problem. It seems bash 3.1 has >>>> broken the >>>> way the arrays are read. >> Once again bitten by using a too-general function for consistency >> across different expansions :-). >> >> I will be releasing a patch for this. > > > Excellent. Thank you for taking the time to look at this. > This problem is now fixed with bash31-017. Thank you. BR. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362782: Broken manpages
Package: xbase-clients Version: 7.0.0-2 Broken manpages mandb: can't open /usr/share/man/man1x/bitmap.1x: No such file or directory mandb: warning: /usr/share/man/man1/atobm.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/bitmap.1x: No such file or directory mandb: warning: /usr/share/man/man1/bmtoa.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapin.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapout.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapproto.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapreset.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapstats.1x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory mandb: warning: /usr/share/man/man1/xtrapchar.1x.gz: bad symlink or ROFF `.so' request -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362783: broken manpages
Package: libxau-dev Version: 1.0.0-2 Broken manpages mandb: can't open /usr/share/man/man3x/Xau.3x: No such file or directory mandb: warning: /usr/share/man/man3/XauGetBestAuthByAddr.3x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man3x/Xau.3x: No such file or directory mandb: warning: /usr/share/man/man3/XauFileName.3x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man3x/Xau.3x: No such file or directory mandb: warning: /usr/share/man/man3/XauGetAuthByAddr.3x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man3x/Xau.3x: No such file or directory mandb: warning: /usr/share/man/man3/XauDisposeAuth.3x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man3x/Xau.3x: No such file or directory mandb: warning: /usr/share/man/man3/XauLockAuth.3x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man3x/Xau.3x: No such file or directory mandb: warning: /usr/share/man/man3/XauReadAuth.3x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man3x/Xau.3x: No such file or directory mandb: warning: /usr/share/man/man3/XauWriteAuth.3x.gz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man3x/Xau.3x: No such file or directory mandb: warning: /usr/share/man/man3/XauUnlockAuth.3x.gz: bad symlink or ROFF `.so' request -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362777: missing /usr/lib/libXrender.la
Package: libxrender-dev Version: 0.9.0.2-2 Severity: important Please include /usr/lib/libXrender.la in the installation. I use it to link into some older applications still. BR. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362778: missing /usr/lib/libXft.la
Package: libxft-dev Version: 2.1.8.2-6 Severity: important Please include /usr/lib/libXft.la in the installation. I use it to link into some older applications still. BR. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362645: nvidia-glx-dev conflicts with libgl1-mesa-dev and can not install with latest Xorg
Randall Donald wrote: > On Fri, 2006-04-14 at 12:05 -0700, C.Y.M wrote: > >> dpkg: regarding nvidia-glx-dev_1.0.8756-4_i386.deb containing nvidia-glx-dev: >> nvidia-glx-dev conflicts with libgl-dev >> libgl1-mesa-dev provides libgl-dev and is installed. >> dpkg: error processing nvidia-glx-dev_1.0.8756-4_i386.deb (--install): >> conflicting packages - not installing nvidia-glx-dev >> Errors were encountered while processing: >> nvidia-glx-dev_1.0.8756-4b_i386.deb >> > > Did you read the changelog? I have moved the header files back > to /usr/include thus making it only possible to have one libgl-dev > package installed at a time. > > If i try to remove libgl1-mesa-dev, then I cant have Xorg installed. Too many dependencies. What do you recommend? I also noticed that the diversions are incorrect when building some packages, like mplayer and vlc: dh_shlibdeps -s dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/X11R6/lib/libGL.so.1 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/X11R6/lib/nvidia/libGL.so.1.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/lib/libGL.so.1 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/lib/nvidia/libGL.so.1.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/X11R6/lib/libGL.so.1 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/X11R6/lib/nvidia/libGL.so.1.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/lib/libGL.so.1.2 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/lib/nvidia/libGL.so.1.2.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/lib/libGL.so.1 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/lib/nvidia/libGL.so.1.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/X11R6/lib/libGL.so.1.2 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/X11R6/lib/nvidia/libGL.so.1.2.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/X11R6/lib/libGL.so.1.2 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/X11R6/lib/nvidia/libGL.so.1.2.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/lib/libGL.so.1.2 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/lib/nvidia/libGL.so.1.2.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/X11R6/lib/libGL.so.1 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/X11R6/lib/nvidia/libGL.so.1.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/lib/libGL.so.1 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/lib/nvidia/libGL.so.1.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/X11R6/lib/libGL.so.1 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/X11R6/lib/nvidia/libGL.so.1.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/lib/libGL.so.1.2 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/lib/nvidia/libGL.so.1.2.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/lib/libGL.so.1 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/lib/nvidia/libGL.so.1.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/X11R6/lib/libGL.so.1.2 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/X11R6/lib/nvidia/libGL.so.1.2.xlibmesa dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx from: /usr/X11R6/lib/libGL.so.1.2 dpkg-shlibdeps: warning: diversions involved - output may be incorrect diversion by nvidia-glx to: /usr/X11R6/lib/nvidia/libGL.so.1.2.xlibmesa dpkg-shlibdeps: warning: diversions in
Bug#362645: nvidia-glx-dev conflicts with libgl1-mesa-dev and can not install with latest Xorg
Package: nvidia-glx-dev Version: 1.0.8756-4 Severity: important nvidia-glx-dev will not install and so I can not link any applications to the new nvidia drivers. dpkg: regarding nvidia-glx-dev_1.0.8756-4_i386.deb containing nvidia-glx-dev: nvidia-glx-dev conflicts with libgl-dev libgl1-mesa-dev provides libgl-dev and is installed. dpkg: error processing nvidia-glx-dev_1.0.8756-4_i386.deb (--install): conflicting packages - not installing nvidia-glx-dev Errors were encountered while processing: nvidia-glx-dev_1.0.8756-4b_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361824: nvidia-glx-dev conflicts with xlibmesa-gl-dev
Package: nvidia-glx-dev Version: 1.0.8756-1 Severity: important nvidia-glx-dev conflicts with xlibmesa-gl-dev and can not be installed. dpkg: regarding nvidia-glx-dev_1.0.8756-1b_i386.deb containing nvidia-glx-dev: nvidia-glx-dev conflicts with libgl-dev xlibmesa-gl-dev provides libgl-dev and is installed. dpkg: error processing nvidia-glx-dev_1.0.8756-1b_i386.deb (--install): conflicting packages - not installing nvidia-glx-dev (Reading database ... 158554 files and directories currently installed.) Preparing to replace nvidia-glx 1.0.8178-3b (using nvidia-glx_1.0.8756-1b_i386.deb) ... Unpacking replacement nvidia-glx ... Setting up nvidia-glx (1.0.8756-1b) ... Installing new version of config file /etc/init.d/nvidia-glx ... Creating NVIDIA TLS links... done. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361578: required obsolete library - libdb2
Package: htdig Version: 3.1.6-11.1 Severity: important Htdig requires libdb2 for installation. libdb2 has been obsoleted from Sid for i386. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361369: conflicting files with modutils
Package: manpages-dev Version: 2.25-1 Severity: important Conflicts with modutils pacakage. dpkg: error processing /var/cache/apt/archives/manpages-dev_2.25-1_all.deb (--unpack): trying to overwrite `/usr/share/man/man2/create_module.2.gz', which is also in package modutils dpkg-deb: subprocess paste killed by signal (Broken pipe) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361033: missing package dependency libdigest-nilsimsa-perl
Package: razor Version: 2.810-1 Severity: important The libdigest-nilsimsa-perl package has been removed from Sid. Preparing to replace razor 2.720-1 (using razor_2.810-1_i386.deb) ... Unpacking replacement razor ... dpkg: dependency problems prevent configuration of razor: razor depends on libdigest-nilsimsa-perl; however: Package libdigest-nilsimsa-perl is not installed. dpkg: error processing razor (--install): dependency problems - leaving unconfigured Errors were encountered while processing: razor [EMAIL PROTECTED]:/var/local/razor$ sudo apt-get install libdigest-nilsimsa-perl Reading package lists... Done Building dependency tree... Done Package libdigest-nilsimsa-perl is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package libdigest-nilsimsa-perl has no installation candidate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360362: imagemagick fails with latest graphviz
Daniel Kobras wrote: > severity 360341 important > merge 360341 360362 > thanks > > On Sat, Apr 01, 2006 at 07:14:09AM -0800, C.Y.M wrote: >> Imagemagick fails to build with latest graphviz-2.8-0.4 in repository. >> >> --snip-- >> >> then mv -f "$depbase.Tpo" "$depbase.Po"; else rm -f "$depbase.Tpo"; exit 1; >> fi >> /bin/sh ./libtool --silent --tag=CC --mode=link gcc -g -O2 -Wall -pthread >> -L/usr/X11R6/lib -L/usr/lib/graphviz -lfreetype -lz -L/usr/lib -o >> utilities/animate -L/usr/X11R6/lib -L/usr/lib/graphviz -lfreetype -lz >> -L/usr/lib >> utilities/animate.o magick/libMagick.la >> magick/.libs/libMagick.so: undefined reference to >> `gvCleanup_DEPRECATED_BY_gvFreeContext' >> collect2: ld returned 1 exit status >> make[1]: *** [utilities/animate] Error 1 >> >> --snip-- > > You can either add --disable-gvc to the configure call in debian/rules, > change the gvCleanup call in coders/dot.c to gvFreeContext, or add a > Build-Conflicts: graphviz (>= 2.8.0) to debian/control. > Thanks. The patch to dot.c worked perfectly. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360362: imagemagick fails with latest graphviz
Package: imagemagick Version: 6.2.4.5-0.8 Severity: important Imagemagick fails to build with latest graphviz-2.8-0.4 in repository. --snip-- then mv -f "$depbase.Tpo" "$depbase.Po"; else rm -f "$depbase.Tpo"; exit 1; fi /bin/sh ./libtool --silent --tag=CC --mode=link gcc -g -O2 -Wall -pthread -L/usr/X11R6/lib -L/usr/lib/graphviz -lfreetype -lz -L/usr/lib -o utilities/animate -L/usr/X11R6/lib -L/usr/lib/graphviz -lfreetype -lz -L/usr/lib utilities/animate.o magick/libMagick.la magick/.libs/libMagick.so: undefined reference to `gvCleanup_DEPRECATED_BY_gvFreeContext' collect2: ld returned 1 exit status make[1]: *** [utilities/animate] Error 1 --snip-- Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360345: dangling symlink libtdsodbc.so
Package: freetds-dev Version: 0.63-2 Dangling symlink in /usr/lib/: libtdsodbc.so -> libtdsodbc.so.0.0.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360343: dangling symlink libtemplate.so
Package: unixodbc-dev Version: 2.2.11-11 Dangling symlink in /usr/lib/: libtemplate.so -> libtemplate.so.1.0.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358831: bash operand errors (forwarded from C.Y.M)
Chet Ramey wrote: > Matthias Klose wrote: >> C.Y.M writes: >>> Reverting back to bash 3.0 fixes the problem. It seems bash 3.1 has broken >>> the >>> way the arrays are read. > > Once again bitten by using a too-general function for consistency > across different expansions :-). > > I will be releasing a patch for this. Excellent. Thank you for taking the time to look at this. BR. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358831: bash operand erros
Reverting back to bash 3.0 fixes the problem. It seems bash 3.1 has broken the way the arrays are read. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358831: bash operand errors
Package: bash Version: 3.1-4 Severity: important I have been using these "any2vob" conversion scripts for quite some time to make DVDs. After updating Sid, the bash scripts do not run anymore. http://mightylegends.zapto.org/dvd/any2vob/any2vob-0.28.sh The error is: /usr/local/bin/any2vob-0.28.sh: line 257: "1": syntax error: operand expected (error token is ""1"") It appears that bash is not able to correctly handle the array functions for some reason. I have tried other shells such as dash, but these also fail with different errors (ie; let: not found). I believe this is a bash only script. Did something major change? Best Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#333052: symbol errors
I dont think the problem you are observing is related to module-init-tools. I am using the same version and do not see these errors. IMHO, there is something wrong with the kernel image you are using. The best way to solve symbol problems like that is to use the kernel-package tool and build your own kernel-image from source. Another suggestion would be to blacklist the alsa modules (using /etc/modprobe.d/blacklist) that you are trying to load before you attempt to manuall insert them. This way udev/hotplug will not be part of the problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354389: checkinstall segfaults
Updating checkinstall to version 1.6.0 fixes the segfaults with the latest Sid sources. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354412: missing symlink to manpage
Package: manpages-dev Version: 2.17-1 fmemopen.3.gz is missing from manpages-dev. /etc/cron.daily/man-db: mandb: warning: /usr/share/man/man3/open_memstream.3.gz is a dangling symlink open_memstream.3.gz -> fmemopen.3.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354389: Checkinstall segfaults with latest Sid update
Package: checkinstall Version: 1.5.3-3 Severity: grave When attempting to execute "checkinstall" scripts after updating Sid today, I get segfaults during package creation. Checkinstall was working prior to upgrading system packages. --SNIP-- checkinstall 1.5.3, Copyright 2001 Felipe Eduardo Sanchez Diaz Duran This software is released under the GNU GPL. Installing with "make install"... = Installation results === ERROR: ld.so: object '/usr/lib/installwatch.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object '/usr/lib/installwatch.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object '/usr/lib/installwatch.so' from LD_PRELOAD cannot be preloaded: ignored. Copying documentation directory... /var/tmp/lCRSkNUrqFbfPTpiiEQY/installscript.sh: line 13: 6573 Segmentation fault mkdir -p "/usr/share/doc/vdr" make: *** [install] Segmentation fault Installation failed. Aborting package creation. Cleaning up...OK Bye. --SNIP-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#336778: Broken links and diversion failures
Package: nvidia-glx-dev Version: 1.0.7676-1 Severity: important I have noticed two problems related to links being created and not created in the nvidia-glx-dev package. 1) When building an application that links to libGL.so, the diversion fails to initialize because there is no usr/lib/libGL.so link created with the new dev package. For example, VLC and Mplayer now fail to build. /var/local/vlc.cvs/vlc-trunk/debian/gcc-snapshot -Wsign-compare -Wall -pipe -o libopengl_plugin.so libopengl_plugin.a -L/usr/lib -shared -lpthread -fpic -fPIC -L/usr/X11R6/lib -lGL -lGLU -u vlc_entry__0_8_4 /usr/bin/ld: cannot find -lGL collect2: ld returned 1 exit status make[5]: *** [libopengl_plugin.so] Error 1 2) There is a broken link to the include files The solution to both these problems is the following attachment. Best Regards, diff -ru nvidia-graphics-drivers-1.0.7676.orig/debian/nvidia-glx-dev.links nvidia-graphics-drivers-1.0.7676/debian/nvidia-glx-dev.links --- nvidia-graphics-drivers-1.0.7676.orig/debian/nvidia-glx-dev.links 2005-11-01 05:05:59.0 -0800 +++ nvidia-graphics-drivers-1.0.7676/debian/nvidia-glx-dev.links 2005-11-01 04:30:58.0 -0800 @@ -1 +1,2 @@ -usr/share/nvidia/includes /usr/share/doc/nvidia-glx-dev/includes +usr/lib/libGL.so.1.0.7676 usr/lib/libGL.so +usr/share/nvidia/include /usr/share/doc/nvidia-glx-dev/include diff -ru nvidia-graphics-drivers-1.0.7676.orig/debian/nvidia-glx-dev.links.in nvidia-graphics-drivers-1.0.7676/debian/nvidia-glx-dev.links.in --- nvidia-graphics-drivers-1.0.7676.orig/debian/nvidia-glx-dev.links.in 2005-11-01 05:05:59.0 -0800 +++ nvidia-graphics-drivers-1.0.7676/debian/nvidia-glx-dev.links.in 2005-11-01 04:29:26.0 -0800 @@ -1 +1,2 @@ -usr/share/nvidia/includes /usr/share/doc/nvidia-glx-dev/includes +usr/lib/libGL.so.#VERSION# usr/lib/libGL.so +usr/share/nvidia/include /usr/share/doc/nvidia-glx-dev/include
Bug#332745: Acknowledgement (addkey called with bad index 256)
Thank you, I must have reinstalled the keymap incorrectly the first time. After doing "install-keymap us", the error has gone away. I think this bug can be closed. Best Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#332745: Acknowledgement (addkey called with bad index 256)
Has anyone found a solution to this? Is it just user error? I have tried to update my keymap and nothing seems to fix the error during configuration and bootup after installing console-common. After the init.d script provided by console-common is executed on bootup, thats when I see this error message again (same error when configuring console-common). But, perhaps this bug should be moved to lib console, not console-common. There is definitely a problem within one of those "console" packages. Best Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#335455: subversion fails to build with libdb4.3-dev
Package: subversion Version: 1.2.3dfsg1-2 Severity: important Since default Apache2 installation has upgraded to 2.0.55-2, it now requires libdb4.3-dev (instead of libdb4.2-dev). This now causes a conflict when building subversion. checking for Apache module support via DSO through APXS... found at /usr/bin/apxs2 checking httpd version... recent enough checking for socket in -lsocket... no configure: WARNING: APR-UTIL may or may not be using the specified Berkeley DB at `/usr'. Using the Berkeley DB supplied by APR-UTIL. checking for availability of Berkeley DB... no configure: error: Berkeley DB 4.0.14 wasn't found. make: *** [debian/stamp-configure] Error 1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#333052: uhci_hcd unknown symbol errors
Marco d'Itri wrote: > reassign 333052 linux-2.6 > retitle 333052 race in the modules loader? > thanks > > On Oct 10, "C.Y.M" <[EMAIL PROTECTED]> wrote: > > >>When using udev with linux kernel 2.6.14-rc3, I get the following error during >>system boot. Plug and Play ACPI support in the kernel is loading uhci_hcd >>just >>fine, but it appears udev is attempting to load it prior to ACPI causing the >>unknown symbol errors. > > This randomly happens for other modules too. Looks like some race is hit > when you try to modprobe a lot of modules at the same time. > > (BTW, can you clarify how ACPI is related to autoloading hcds?) > The "Plug and Play ACPI" kernel config option allows the kernel to autodetect built-in mainboard resources (including usb and parallel port). When I blacklist uhci_hcd in udev, the module is then loaded by the plug and play option. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#333052: uhci_hcd unknown symbol errors
Package: udev Version: 0.070-3 Severity: important When using udev with linux kernel 2.6.14-rc3, I get the following error during system boot. Plug and Play ACPI support in the kernel is loading uhci_hcd just fine, but it appears udev is attempting to load it prior to ACPI causing the unknown symbol errors. If I add "uhci_hcd" to the udev blacklist file, then the errors go away and uhci_hcd loads fine via ACPI. I have all my usb kernel code compiled as modules. This error does not occur with the previous version of udev. A quick hack to fix the errors with the current version of udev is: --SNIP-- --- modprobe.d/blacklist.orig 2005-10-09 19:02:15.0 -0700 +++ modprobe.d/blacklist 2005-10-09 19:01:49.0 -0700 @@ -2,6 +2,9 @@ # the hotplug subsystem. It does not affect autoloading of modules by the # kernel. This file is provided by the udev package. +# dont load usb +blacklist uhci_hcd + # usbcore is loaded as a dependency, ignore it otherwise blacklist usbcore --SNIP-- Oct 9 04:55:44 sid kernel: parport0: PC-style at 0x378, irq 7 [PCSPP(,...)] Oct 9 04:55:44 sid kernel: Linux agpgart interface v0.101 (c) Dave Jones Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_pci_suspend Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_resume_root_hub Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_pci_probe Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_check_bandwidth Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_disabled Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_release_bandwidth Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_claim_bandwidth Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_pci_resume Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_giveback_urb Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_poll_rh_status Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_pci_remove Oct 9 04:55:44 sid kernel: usbcore: registered new driver usbfs Oct 9 04:55:44 sid kernel: usbcore: registered new driver hub Oct 9 04:55:44 sid kernel: nvidia: module license 'NVIDIA' taints kernel. Oct 9 04:55:44 sid kernel: ACPI: PCI Interrupt :01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 Oct 9 04:55:44 sid kernel: NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-7676 Fri Jul 29 12:58:54 PDT 2005 Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_pci_suspend Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_resume_root_hub Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_pci_probe Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_check_bandwidth Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_disabled Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_release_bandwidth Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_claim_bandwidth Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_pci_resume Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_giveback_urb Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_poll_rh_status Oct 9 04:55:44 sid kernel: uhci_hcd: Unknown symbol usb_hcd_pci_remove Oct 9 04:55:44 sid kernel: USB Universal Host Controller Interface driver v2.3 Oct 9 04:55:44 sid kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 Oct 9 04:55:44 sid kernel: ACPI: PCI Interrupt :00:11.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 Oct 9 04:55:44 sid kernel: uhci_hcd :00:11.2: UHCI Host Controller Oct 9 04:55:44 sid kernel: uhci_hcd :00:11.2: new USB bus registered, assigned bus number 1 Oct 9 04:55:44 sid kernel: uhci_hcd :00:11.2: irq 11, io base 0xd800 Oct 9 04:55:44 sid kernel: hub 1-0:1.0: USB hub found Oct 9 04:55:44 sid kernel: hub 1-0:1.0: 2 ports detected Oct 9 04:55:44 sid kernel: ACPI: PCI Interrupt :00:11.3[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 Oct 9 04:55:44 sid kernel: uhci_hcd :00:11.3: UHCI Host Controller Oct 9 04:55:44 sid kernel: uhci_hcd :00:11.3: new USB bus registered, assigned bus number 2 Oct 9 04:55:44 sid kernel: uhci_hcd :00:11.3: irq 11, io base 0xdc00 Oct 9 04:55:44 sid kernel: hub 2-0:1.0: USB hub found Oct 9 04:55:44 sid kernel: hub 2-0:1.0: 2 ports detected Oct 9 04:55:44 sid kernel: ACPI: PCI Interrupt :00:11.4[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 Oct 9 04:55:44 sid kernel: uhci_hcd :00:11.4: UHCI Host Controller Oct 9 04:55:44 sid kernel: uhci_hcd :00:11.4: new USB bus registered, assigned bus number 3 Oct 9 04:55:44 sid kernel: uhci_hcd :00:11.4: irq 11, io base 0xe000 Oct 9 04:55:44 sid kernel: hub 3-0:1.0: USB hub found Oct 9 04:55:44 sid kernel: hub 3-0:1.0: 2 ports detected Oct 9 04:55:44 sid kernel: snd_mpu401: Unknown symbol snd_mpu401_uart_new Oct 9 04:55:44 sid kernel: ACPI: PCI Interrupt :00:11.5[C] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5 Oct 9 04:55:44 sid kernel: PC
Bug#332874: udev conflicts with hotplug package
Hotplug is also necessary for loading external firmware and can not be replaced by udev. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#332791: Acknowledgement (error: `PEM_F_DEF_CALLBACK' undeclared )
Here is a patch to fix the problem: --- httpd-2.0.54.orig/modules/ssl/ssl_toolkit_compat.h 2005-02-04 12:21:18.0 -0800 +++ httpd-2.0.54/modules/ssl/ssl_toolkit_compat.h 2005-07-06 08:50:38.46875 -0700 @@ -24,6 +24,12 @@ #ifdef OPENSSL_VERSION_NUMBER +#if (OPENSSL_VERSION_NUMBER >= 0x0090800fL) +#ifndef PEM_F_DEF_CALLBACK +#define PEM_F_DEF_CALLBACK PEM_F_PEM_DEF_CALLBACK +#endif +#endif + /* * rsa sslc uses incomplete types for most structures * so we macroize for OpenSSL those which cannot be dereferenced -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#332791: error: `PEM_F_DEF_CALLBACK' undeclared
Package: apache2 Version: 2.0.54-5 Severity: grave Apache2 no longer builds with new openssl-0.9.8 package. /var/local/apache2/apache2-2.0.54/build-tree/apache2/modules/ssl/ssl_engine_pphrase.c: In function `ssl_pphrase_Handle_CB': /var/local/apache2/apache2-2.0.54/build-tree/apache2/modules/ssl/ssl_engine_pphrase.c:684: error: `PEM_F_DEF_CALLBACK' undeclared (first use in this function) /var/local/apache2/apache2-2.0.54/build-tree/apache2/modules/ssl/ssl_engine_pphrase.c:684: error: (Each undeclared identifier is reported only once /var/local/apache2/apache2-2.0.54/build-tree/apache2/modules/ssl/ssl_engine_pphrase.c:684: error: for each function it appears in.) make[4]: *** [ssl_engine_pphrase.slo] Error 1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#332745: addkey called with bad index 256
Package: console-common Version: 0.7.54 New console-common package causes the following error during installation and during system boot. Setting up console-common (0.7.54) ... Installing new version of config file /etc/init.d/keymap.sh ... Looking for keymap to install: NONE loadkeys: /etc/console/boottime.kmap.gz:407: addkey called with bad index 256 * Problem when loading /etc/console/boottime.kmap.gz, use install-keymap -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#329328: sysvinit attempts to mount selinux when it is not available
This fixes the problem.. although its not a real fix. --- rules.orig 2005-09-22 03:39:27.0 -0700 +++ rules 2005-09-22 03:31:28.0 -0700 @@ -30,7 +30,7 @@ # Builds the binary package. $(checkdir) ifeq ($(DEB_HOST_ARCH_OS),linux) - (cd src; make DISTRO=Debian WITH_SELINUX="yes") + (cd src; make DISTRO=Debian WITH_SELINUX="no") else (cd src; make DISTRO=Debian) endif -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#329328: Acknowledgement (sysvinit attempts to mount selinux when it is not available)
Further information: I have tested 2.6.13.2 and 2.6.14-rc2 kernel sources from kernel.org. Also, I have the following kernel security settings enabled: # # Security options # # CONFIG_KEYS is not set CONFIG_SECURITY=y # CONFIG_SECURITY_NETWORK is not set CONFIG_SECURITY_CAPABILITIES=m # CONFIG_SECURITY_ROOTPLUG is not set # CONFIG_SECURITY_SECLVL is not set # CONFIG_SECURITY_SELINUX is not set After updating to latest sysvinit package, I get the following error upon boot: Unable to mount /selinux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#329328: sysvinit attempts to mount selinux when it is not available
Package: sysvinit Version: 2.86.ds1-2 Sysvinit attempts to mount /selinux on boot and fails (but selinux is not currently enabled). Sysvinit should check if selinux is available before attempting to mount it. Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#329039: mkisofs segfaults when creating isos
Steve McIntyre wrote:
> On Sun, Sep 18, 2005 at 06:05:42PM -0700, C.Y.M wrote:
>
>>Package: mkisofs
>>Version: 2.01+01a03-1
>>Severity: grave
>>
>>mkisofs segfaults when creating isos.
>>
>>Example:
>>
>>mkisofs -dvd-video -V ISO_`date +"%d-%m-%Y"` -o image.iso image
>>
>>Segmentation fault
>
>
> Can you provide an example tree that demonstrates this please? I can't
> reproduce this at the moment...
>
Do you mean the xml?
--SNIP--
Enter do_dvdauthor
{ g1=0;
if (g2 lt 1024) button=1024;
if (g2 gt 1024) button=g2;
button=1024;
}
{ g2=button ; jump titleset 1 menu ;
}
jump cell 1;
button=2048;
jump vmgm menu 1;
jump title 1 chapter 1;
jump cell 1;
call vmgm menu 1;
DVDAuthor::dvdauthor, version 0.6.11.
Build options: gnugetopt magick iconv freetype fribidi
Send bugs to <[EMAIL PROTECTED]>
INFO: Locale=en_US
INFO: Converting filenames to ISO-8859-1
INFO: dvdauthor creating VTS
STAT: Picking VTS 01
STAT: Processing
/home/video/tmp/vdr2dvd/16364/DVDMENU/Titel-1/spu-submenu-1.mpg...
INFO: Video pts = 0.178 .. 6.150
INFO: Audio[8] pts = 0.178 .. 2.170
INFO: Audio[32] pts = 0.178 .. 0.178
STAT: VOBU 10 at 2MB, 1 PGCS
INFO: Generating VTSM with the following video attributes:
INFO: MPEG version: mpeg2
INFO: TV standard: ntsc
INFO: Aspect ratio: 4:3
INFO: Resolution: 720x480
INFO: Audio ch 0 format: mp2/2ch, 48khz 20bps
STAT: Processing /home/video/tmp/vdr2dvd/16364/DVDMENU/Titel-1/mplex.mpg...
STAT: VOBU 144 at 41MB, 1 PGCS
STAT: VOBU 272 at 86MB, 1 PGCS
STAT: VOBU 400 at 135MB, 1 PGCS
STAT: VOBU 528 at 174MB, 1 PGCS
STAT: VOBU 608 at 197MB, 1 PGCS
INFO: Video pts = 0.179 .. 649.695
INFO: Audio[8] pts = 0.246 .. 649.086
INFO: Audio[9] pts = 0.246 .. 649.110
STAT: VOBU 617 at 199MB, 1 PGCS
WARN: GOP is not closed on cell 1 of source
/home/video/tmp/vdr2dvd/16364/DVDMENU/Titel-1/mplex.mpg of pgc 1
INFO: Generating VTS with the following video attributes:
INFO: MPEG version: mpeg2
INFO: TV standard: ntsc
INFO: Aspect ratio: 4:3
INFO: Resolution: 704x480
INFO: Audio ch 0 format: mp2/2ch, 48khz 20bps, 'en'
INFO: Audio ch 1 format: mp2/2ch, 48khz 20bps, 'en'
STAT: fixed 10 VOBUS
STAT: fixing VOBU at 27MB (97/617, 15%)
STAT: fixing VOBU at 66MB (209/617, 31%)
STAT: fixing VOBU at 96MB (305/617, 49%)
STAT: fixing VOBU at 135MB (401/617, 64%)
STAT: fixing VOBU at 167MB (497/617, 80%)
STAT: fixing VOBU at 193MB (593/617, 95%)
STAT: fixed 617 VOBUS
INFO: dvdauthor creating table of contents
INFO: Scanning /home/video/tmp/vdr2dvd/16364/DVDSTRUCT/VIDEO_TS/VTS_01_0.IFO
INFO: Creating menu for TOC
STAT: Processing /home/video/tmp/vdr2dvd/16364/DVDMENU/spu-mainmenu-1.mpg...
INFO: Video pts = 0.178 .. 6.150
INFO: Audio[8] pts = 0.178 .. 2.170
INFO: Audio[32] pts = 0.178 .. 0.178
STAT: VOBU 10 at 1MB, 1 PGCS
INFO: Generating VMGM with the following video attributes:
INFO: MPEG version: mpeg2
INFO: TV standard: ntsc
INFO: Aspect ratio: 4:3
INFO: Resolution: 720x480
INFO: Audio ch 0 format: mp2/2ch, 48khz 20bps
STAT: fixed 10 VOBUS
Enter do_mkisofs
17:30:57 : Start mkisofs
/usr/local/bin/vdr2dvd.sh: line 626: 22540 Segmentation fault nice -n
${PRIO} $MKISOFS $DVDMKISOFSOPTS -dvd-video -o "${
Image}.iso" ${UniqueDVDDIR} >$LOG 2>&1
ERROR : exit on error: mkisofs
--SNIP--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#329037: Package does not build with new linux-kernel-headers
Christian Hammers wrote: > Hi > > On 2005-09-19 sean finney wrote: > >>On Sun, Sep 18, 2005 at 04:58:39PM -0700, C.Y.M wrote: >> >>>Package: mysql-server >>>Version: 4.0.24-10 >>> >>>Package does not build with new linux-kernel-headers (2.6.13+0rc3-1.1) and >>>gcc-3.4. > > > Hm, 4.0.24 is no longer present in unstable (superceeded by mysql-dfsg-4.1). > Also, we have gcc-4.0 there. So this is maybe a non-issue? > True, I did upgrade to 4.1 although I have not had a chance to build it yet. But, I thought 4.0 was/is still used for some systems. Best Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#329039: mkisofs segfaults when creating isos
Package: mkisofs Version: 2.01+01a03-1 Severity: grave mkisofs segfaults when creating isos. Example: mkisofs -dvd-video -V ISO_`date +"%d-%m-%Y"` -o image.iso image Segmentation fault -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#329037: Package does not build with new linux-kernel-headers
Package: mysql-server Version: 4.0.24-10 Package does not build with new linux-kernel-headers (2.6.13+0rc3-1.1) and gcc-3.4. --SNIP-- In file included from /usr/include/asm/processor.h:18, from /usr/include/asm/atomic.h:6, from ./../include/my_global.h:287, from mysys_priv.h:17, from my_new.cc:22: /usr/include/asm/system.h:247: error: expected `,' or `...' before "new" /usr/include/asm/system.h: In function `long unsigned int __cmpxchg(volatile void*, long unsigned int, long unsigned int)': /usr/include/asm/system.h:250: error: `size' undeclared (first use this function) /usr/include/asm/system.h:250: error: (Each undeclared identifier is reported only once for each function it appears in.) /usr/include/asm/system.h:254: error: expected identifier before ')' token /usr/include/asm/system.h:260: error: expected identifier before ')' token /usr/include/asm/system.h:266: error: expected identifier before ')' token make[3]: *** [my_new.o] Error 1 make[3]: Leaving directory `/var/local/mysql/mysql-dfsg-4.0.24/mysys' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/local/mysql/mysql-dfsg-4.0.24' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/local/mysql/mysql-dfsg-4.0.24' make: *** [build-stamp] Error 2 --SNIP-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328570: external firmwre fails to load
Package: udev Version: 0.070-1 Udev fails to load external firmware. My dvb firmware fails to load. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328248: libarts1-xine needs to link against libmodplug0c2
> > Well, then you should've reported the bug against libxine1, not > against us; we can't do nothing about it. .oO(other than NMU) > > Reassigned, thanks. > Thanks, sorry for the confusion. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328248: libarts1-xine needs to link against libmodplug0c2
Adeodato Simó wrote: > * C.Y.M [Wed, 14 Sep 2005 05:04:41 -0700]: > > >>Package: libarts1-xine >>Version: 3.4.2-2 > > >>libarts1-xine should be built against libmodplug0c2 (not libmodplug0). > > > Er, where does libarts1-xine depend on libmodplug0? I can't find it. > > I guess libarts-xine is being built against libxine1 which in turn is linked against libmodplug0. So, when I goto install libmodplug0c2, it wants to remove all of the above. -C
Bug#328248: libarts1-xine needs to link against libmodplug0c2
Package: libarts1-xine Version: 3.4.2-2 libarts1-xine should be built against libmodplug0c2 (not libmodplug0). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327570: missing /usr/bin/tput when rebooting
Package: initscripts Version: 2.86.ds1-1.2 When rebooting the system, I get an error message stating: missing file: /usr/bin/tput Regards, C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327477: Breaks /dev/stdin, stdout, and stderr with UDEV.
Matthias Klose wrote: > tags 327477 +unreproducible > thanks > > - please could you verify, if that occurs with dash as well? (setting > the /bin/sh symlink to /bin/dash) > - can you reproduce this with a kernel found in the Debian archives? > I have reinstalled the new version of bash and switched the symlink to dash, and the problem does not occur. The problem is not kernel specific. In order to reproduce the problem: 1) Install New version of bash 2) Delete symlink (/dev/stdout, stdin, stderr) 3) /etc/init.d/udev restart Regards, C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327477: Breaks /dev/stdin, stdout, and stderr with UDEV.
Package: bash Version: 3.0-16 Severity: grave The new version of Bash is causing udev-0.068-2 to *not* create links in /dev to the nodes in /proc/self/fd (/dev/stdin, /dev/stdout, /dev/stderr). I am using an x86 cpu with a 2.6.13 kernel. Re, C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327434: Acknowledgement (Udev is not creating /dev/stdout->fd/1)
> > Since I have not changed the udev package or upgraded it in any way for the > past > few weeks, I am fairly certain that this is not an actual UDEV bug. Some of > the > candidate packages responsible for this problem could be either the latest > version of bash or possibly sed. I have updated all my packages so Im pretty > sure if you were to do a full update you will notice the same problem. The > chore now is to determine who the culprit is. > Sorry for the trouble. Its the new bash (3.0-15) that broke your package. Regards, C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327434: Acknowledgement (Udev is not creating /dev/stdout->fd/1)
C.Y.M wrote: >>I have reverted everything that I can think of the past few days and nothing >>looks like it could be deleting those links. Besides, wouldnt they get >>recreated if I manually restarted udev after the system startup? I tried >>"udevstart" and the links are still not there. >> > > > After some more testing, I am almost positive that there is some kind of race > condition going on here. I am using a 2.6.13 kernel is that might make any > difference to you. With the following patch, the problem is solved (although > I > know this is not the right way to go). I just wanted to prove that there is > nothing else deleting these links. > Since I have not changed the udev package or upgraded it in any way for the past few weeks, I am fairly certain that this is not an actual UDEV bug. Some of the candidate packages responsible for this problem could be either the latest version of bash or possibly sed. I have updated all my packages so Im pretty sure if you were to do a full update you will notice the same problem. The chore now is to determine who the culprit is. Best Regards, C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327434: Acknowledgement (Udev is not creating /dev/stdout->fd/1)
> I have reverted everything that I can think of the past few days and nothing > looks like it could be deleting those links. Besides, wouldnt they get > recreated if I manually restarted udev after the system startup? I tried > "udevstart" and the links are still not there. > After some more testing, I am almost positive that there is some kind of race condition going on here. I am using a 2.6.13 kernel is that might make any difference to you. With the following patch, the problem is solved (although I know this is not the right way to go). I just wanted to prove that there is nothing else deleting these links. Regards, C. --- init.d/udev.orig 2005-09-10 03:56:55.0 -0700 +++ init.d/udev 2005-09-10 04:07:09.0 -0700 @@ -64,6 +64,9 @@ *) log_warning_msg "links.conf: unparseable line ($type $name $arg1)" ;; esac done + ln -fs /proc/self/fd/0 /dev/stdin + ln -fs /proc/self/fd/1 /dev/stdout + ln -fs /proc/self/fd/2 /dev/stderr } # this function is duplicated in preinst, postinst and d-i
Bug#327434: Acknowledgement (Udev is not creating /dev/stdout->fd/1)
Marco d'Itri wrote: > tag 327434 unreproducible moreinfo help > thanks > > On Sep 10, "C.Y.M" <[EMAIL PROTECTED]> wrote: > > >>This is definitely a UDEV issue. I have noticed that all the links in >>/etc/udev/links.conf get created *except* stdin, stdout, and stderr. The only >>difference between those links and the others is that they are linking against >>nodes. Perhaps the nodes are not getting created fast enough and the link >>fails. > > ln does not work this way (and anyway all nodes are created before > udevstart returns). > I think that something on your system is deleting these links. > Please check. > I have reverted everything that I can think of the past few days and nothing looks like it could be deleting those links. Besides, wouldnt they get recreated if I manually restarted udev after the system startup? I tried "udevstart" and the links are still not there. -C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327434: Acknowledgement (Udev is not creating /dev/stdout->fd/1)
C.Y.M wrote: > I would like to mention that this problem may also be related to HAL (not > UDEV). > Please forward accordingly if you find that this is the case. > This is definitely a UDEV issue. I have noticed that all the links in /etc/udev/links.conf get created *except* stdin, stdout, and stderr. The only difference between those links and the others is that they are linking against nodes. Perhaps the nodes are not getting created fast enough and the link fails. When I look in /proc/self/fd/*, all the nodes are there (only the links to them are not created). Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327434: Acknowledgement (Udev is not creating /dev/stdout->fd/1)
I would like to mention that this problem may also be related to HAL (not UDEV). Please forward accordingly if you find that this is the case. Best Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327298: spumux broken with new libmagick
C.Y.M wrote: > Package: dvdauthor > Version: 0.6.11-2 > Severity: Important > Please close this report. The problem was not with spumux at all. The problem manifested itself with a new release of UDEV not creating /dev/stdout. Sorry for the bad report. Best Regards. C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327434: Udev is not creating /dev/stdout->fd/1
Package: udev Version: 0.068-2 Severity: important Udev is not creating /dev/stdout->fd/1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327298: spumux broken with new libmagick
Package: dvdauthor
Version: 0.6.11-2
Severity: Important
After testing dvdauthor 0.6.11-2 with libmagick 6.2.3.6-3, I am now able to
build the dvdauthor packages. Unfortunatly, spumux is completly broken with the
new libmagick versions. I am unable to create menus and my scripts now segfault
due to missing .mpg files. When I attempt to go back to the stable libmagick
package, something must not be getting removed because it is still broken after
trying to reinstall the older stable libmagick. I have rebuilt all the packages
several times with the older libmagick installed and spumux is still broken now.
I am unsure if this is a dvdauthor problem, but I thought I would file it here
first. I noticed someone else was talking about the same problem in the
dvdauthor bug reports.
--start quote--
what's the exact problem? I saw things like this in spumux strace
output:
7042 stat64("orpion/dvd/menu1-0.mpg_buttons.png",
7042 write(2, "scorpion: Unable to load file", 29
7042 write(2, " (/home/scorpion/dvd/menu1-0.mpg"..., 45
So it seems to trash the path names somewhere, causing empty (or better:
invisible) menus on DVDs, since the button images can not be loaded.
--end quote--
As of this moment, I am stuck. Unable to go back because something is wrong the
the package installation of libmagick preventing me from reinstalling the older
packages.
Best Regards,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#325152: find broken in dh_installdocs
Package: debhelper Version: 4.9.6 Severity: important When building packages, I get the following error with version 4.9.6. Going back to 4.9.5 fixes the problem. dh_installdocs --exclude=CVS --exclude=mplayer.1 DOCS/* find: paths must precede expression Usage: find [-H] [-L] [-P] [path...] [expression] dh_installdocs: command returned error code make: *** [binary-arch] Error 1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323572: new version breaks mjpegtools
Package: libquicktime Version: 0.9.7-0.0 This new version of libquicktime will not build with the stable version of mjpegtools (1.6.2-0.9) in the debian repository at nerim. Mjpegtools version 1.7 is required for this new version of libquicktime. Unfortunately, the new version of mjpegtools version 1.7 does not work right (ppmtoy4m segfaults). I suppose this is not really a bug against libquicktime, but more of a notice that this change will break other stable packages. Best Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
