Bug#85088: Get latest version, cds and download under $99
Software by the original manufacturer&at generic prices& http://bqdd.e3ithdwpt6wlbxw.cahowci.com The extreme limit of wisdom-- that is what the public calls madness. Successful people breed success. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#99438: 75% Off for All New Software.
Software cds $15 and $99 get al software in 1 cd http://lqez.t0xqesbm83b08ct.samphdsamp2.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#60006: 70% discounts on popular software
AutoCAD 2005 - $69.95 http://pleasant.mytin.com/ If men liked shopping, they'd call it research. Power is the ability not to have to please. There is no great concurrence between learning and wisdom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#739384: keepass2: does not start anymore (after upgrade to mono?)
Package: keepass2 Version: 2.24+dfsg-1 Severity: important Dear Maintainer, Recently I installed the latest Jessie upgrades to mono, today I wanted to start keepass2 as usual. However, it does not start anymore. I tried from command line, but it neither gives *any* message. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages keepass2 depends on: ii libmono-corlib4.5-cil3.0.6+dfsg2-11 ii libmono-system-configuration4.0-cil 3.0.6+dfsg2-11 ii libmono-system-drawing4.0-cil3.0.6+dfsg2-11 ii libmono-system-security4.0-cil 3.0.6+dfsg2-11 ii libmono-system-windows-forms4.0-cil 3.0.6+dfsg2-11 ii libmono-system-xml4.0-cil3.0.6+dfsg2-11 ii libmono-system4.0-cil3.0.6+dfsg2-11 ii libx11-6 2:1.6.2-1 ii mono-runtime 3.0.6+dfsg2-11 Versions of packages keepass2 recommends: ii xsel 1.2.0-2 Versions of packages keepass2 suggests: pn keepass2-doc pn mono-dmcs ii xdotool 1:3.20130111.1-3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#738459: mono-runtime: NotifyIcon class does not show tray icon
Package: mono-runtime Version: 3.0.6+dfsg2-10 Severity: important Tags: upstream Dear Maintainer, I have installed the keepass2 package via aptitude, which works fine on my machine. There is only one bug I have found so far: no tray icon is shown in Xfce's panel. After contacting the authors of KeePass they told me that this bug is related to mono. They use the NotifyIcon class to show the icon, so fixing this bug is not in their hands. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mono-runtime depends on: ii libc6 2.17-97 ii mono-gac 3.0.6+dfsg2-10 ii zlib1g1:1.2.8.dfsg-1 Versions of packages mono-runtime recommends: ii binfmt-support 2.1.1-1 Versions of packages mono-runtime suggests: ii libgnome2-0 2.32.1-5 ii xdg-utils1.1.0~rc1+git20111210-7 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#855359: [Pkg-phototools-devel] Bug#855359: darktable: 2.2.1 binary very slow compared to self-compiled
Am 2017-02-20 0:36, schrieb David Bremner: Matthias Bodenbinder writes: And by the way, this are the commands I use to compile DT: ./build.sh --disable-gnome-keyring --prefix /home/software/darktable --build-type Release cd build echo "darktable 2.2.1" > description-pak checkinstall --default --install=no --pkgname=darktable-mbo --pkgversion=$version --docdir=$INST/share/doc Matthias The debian package does not use build.sh. I looks like build.sh does not pass -DBINARY_PACKAGE_BUILD=1 to cmake. To test this, you could run something like mkdir -p dtbuild && cd dtbuild && cmake -DCMAKE_INSTALL_PREFIX=/opt/darktable \ -DCMAKE_BUILD_TYPE=Release -DBINARY_PACKAGE_BUILD=1 .. then I guess your same checkinstall should work. d Hi, I do not understand your point. My checkinstall is working fine. It is just that my binaries are a lot faster than the debian testing binaries. Matthias
Bug#822179: xorg: X.Org X Server starts normally, crashes with Segmentation fault on starting any application
Package: xorg Version: 1:7.7+14 Severity: normal Dear Maintainer, X crashes instantly when starting any application, e.g. FF or system configuration settings or display settings. The Xorg.0.log file states, xorg-server version is 2:1.18.3-1 . System is Debian testing running under hurd. -- Package-specific info: X server symlink status: lrwxr-xr-x 1 root root 13 Dec 28 11:32 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Apr 5 11:40 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- Xorg X server configuration file status: -rw-r--r-- 1 root root 131 Dec 28 11:38 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 2.6.1 (GNU 0.7 GNU-Mach 1.6+git20160311-486/Hurd-0.7 i686-AT386) Xorg X server log files on system: -- -rw-r--r-- 1 root root 29974 Apr 21 22:45 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [982589.873] X.Org X Server 1.18.3 Release Date: 2016-04-04 [982589.873] X Protocol Version 11, Revision 0 [982589.873] Build Operating System: GNU 0.7 i686-AT386 Debian [982589.873] Current Operating System: GNU debian 0.7 GNU-Mach 1.6+git20160311-486/Hurd-0.7 i686-AT386 [982589.873] Build Date: 05 April 2016 09:20:21AM [982589.873] xorg-server 2:1.18.3-1 (http://www.debian.org/support) [982589.873] Current version of pixman: 0.33.6 [982589.873]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [982589.873] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [982589.873] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 21 22:44:30 2016 [982589.883] (==) Using config file: "/etc/X11/xorg.conf" [982589.883] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [982589.883] (==) No Layout section. Using the first Screen section. [982589.883] (==) No screen section available. Using defaults. [982589.883] (**) |-->Screen "Default Screen Section" (0) [982589.883] (**) | |-->Monitor "" [982589.893] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [982589.893] (==) Not automatically adding devices [982589.893] (==) Not automatically enabling devices [982589.893] (==) Not automatically adding GPU devices [982589.893] (==) Max clients allowed: 256, resource mask: 0x1f [982589.893] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [982589.893]Entry deleted from font path. [982589.903] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [982589.903] (==) ModulePath set to "/usr/lib/xorg/modules" [982589.903] (==) |-->Input Device "" [982589.903] (==) |-->Input Device "Generic Keyboard" [982589.903] (==) No Layout section. Using the default mouse configuration. [982589.903] (==) No Layout section. Using the first keyboard device. [982589.903] (II) Loader magic: 0x273500 [982589.903] (II) Module ABI versions: [982589.903]X.Org ANSI C Emulation: 0.4 [982589.903]X.Org Video Driver: 20.0 [982589.903]X.Org XInput driver : 22.1 [982589.903]X.Org Server Extension : 9.0 [982591.283] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe800/134217728, 0xfe00/8388608, I/O @ 0x10d0/16, BIOS @ 0x/65536 [982591.283] (II) LoadModule: "glx" [982591.293] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [982591.313] (II) Module glx: vendor="X.Org Foundation" [982591.313]compiled for 1.18.3, module version = 1.0.0 [982591.313]ABI class: X.Org Server Extension, version 9.0 [982591.313] (==) AIGLX enabled [982591.313] (==) Matched vmware as autoconfigured driver 0 [982591.313] (==) Matched fbdev as autoconfigured driver 1 [982591.313] (==) Matched vesa as autoconfigured driver 2 [982591.313] (==) Assigned the driver to the xf86ConfigLayout [982591.313] (II) LoadModule: "vmware" [982591.313] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so [982591.313] (II) Module vmware: vendor="X.Org Foundation" [982591.313]compiled for 1.18.0, module version = 13.1.0 [982591.313]Module class: X.Org Video Driver [982591.313]ABI class: X.Org Video Driver, version 20.
Bug#793543: xserver-xorg segmentation fault at startup on testing
Package: xserver-xorg Version: 1:7.7+9 Severity: normal Dear Maintainer, On startup, xserver crashes on debian hurd testing: 'Segmentation fault at address 0x0 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting' Before upgrading Debian Jessie (Hurd) to debian testing, X did run without errors. -- Package-specific info: X server symlink status: lrwxr-xr-x 1 root root 13 Jan 4 2015 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2405904 May 5 04:31 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- Xorg X server configuration file status: -rw-r--r-- 1 root root 131 Jan 4 2015 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 2.6.1 (GNU 0.6 GNU-Mach 1.4+git20150711-486/Hurd-0.6 i686-AT386) Xorg X server log files on system: -- -rw-r--r-- 1 root root 28077 Jul 24 22:28 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [3250600.637] X.Org X Server 1.17.1 Release Date: 2015-02-10 [3250600.637] X Protocol Version 11, Revision 0 [3250600.637] Build Operating System: GNU 0.6 i686-AT386 Debian [3250600.637] Current Operating System: GNU debian 0.6 GNU-Mach 1.4+git20150711-486/Hurd-0.6 i686-AT386 [3250600.637] Build Date: 05 May 2015 02:11:40AM [3250600.637] xorg-server 2:1.17.1-2 (http://www.debian.org/support) [3250600.637] Current version of pixman: 0.32.6 [3250600.637] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [3250600.647] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [3250600.647] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 24 22:27:57 2015 [3250600.647] (==) Using config file: "/etc/X11/xorg.conf" [3250600.647] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [3250600.657] (==) No Layout section. Using the first Screen section. [3250600.657] (==) No screen section available. Using defaults. [3250600.657] (**) |-->Screen "Default Screen Section" (0) [3250600.657] (**) | |-->Monitor "" [3250600.657] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [3250600.657] (==) Not automatically adding devices [3250600.657] (==) Not automatically enabling devices [3250600.657] (==) Not automatically adding GPU devices [3250600.657] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [3250600.657] Entry deleted from font path. [3250600.657] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [3250600.657] (==) ModulePath set to "/usr/lib/xorg/modules" [3250600.657] (==) |-->Input Device "" [3250600.657] (==) |-->Input Device "Generic Keyboard" [3250600.657] (==) No Layout section. Using the default mouse configuration. [3250600.657] (==) No Layout section. Using the first keyboard device. [3250600.657] (II) Loader magic: 0x26e540 [3250600.657] (II) Module ABI versions: [3250600.657] X.Org ANSI C Emulation: 0.4 [3250600.657] X.Org Video Driver: 19.0 [3250600.657] X.Org XInput driver : 21.0 [3250600.657] X.Org Server Extension : 9.0 [3250601.957] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe800/134217728, 0xfe00/8388608, I/O @ 0x10d0/16, BIOS @ 0x/65536 [3250601.957] (II) LoadModule: "glx" [3250601.957] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [3250601.977] (II) Module glx: vendor="X.Org Foundation" [3250601.977] compiled for 1.17.1, module version = 1.0.0 [3250601.977] ABI class: X.Org Server Extension, version 9.0 [3250601.977] (==) AIGLX enabled [3250601.977] (==) Matched vmware as autoconfigured driver 0 [3250601.977] (==) Matched fbdev as autoconfigured driver 1 [3250601.977] (==) Matched vesa as autoconfigured driver 2 [3250601.977] (==) Assigned the driver to the xf86ConfigLayout [3250601.977] (II) LoadModule: "vmware" [3250601.977] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so [3250601.987] (II) Module vmware: vendor="X.Org Foundation" [3250601.987] compiled for 1.17.1, module version = 13.1.0 [3250601.987] Module class: X.Org Video Driver [3250601.987] ABI class: X.Org Video Driver, versi
Bug#774386: debian-installer: installation of grub bootloader failed unexpectly
Package: grub-installer Version: 1.103 Severity: important Dear Maintainer, When trying to install debian sid hurd with debian-sid-hurd-i386-NETINST-1.iso from https://people.debian.org/~sthibault/hurd-i386/installer/cdimage/daily/ , the step of installing the grub bootloader failed unexpectly (pseudo graphical installer, version of 2015-01-01). Last working version of i know of the installation of the bootloader was succesful is the debian-sid-hurd-i386-NETINST-1.iso dated 2014-11-30 from https://people.debian.org/~sthibault/hurd-i386/installer/cdimage/weekly-2/ . -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: hurd-i386 Kernel: Hurd Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765921: lightdm: shut down and other options missing from login
Package: lightdm Version: 1.10.2-2 Followup-For: Bug #765921 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** As reported initially for this bug, I have the same problem with lightdm (and Xfce). On the lightdm login screen, the shutdown/reboot options in the top-right menu are grayed out. I am fully upgraded and using Debian testing. Also I am using the "default" init system (never changed that after installation). *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lightdm depends on: ii adduser3.113+nmu3 ii consolekit 0.4.6-5 ii dbus 1.8.8-2 ii debconf [debconf-2.0] 1.5.53 ii libc6 2.19-11 ii libgcrypt201.6.2-3 ii libglib2.0-0 2.42.0-2 ii libpam-systemd 215-5+b1 ii libpam0g 1.1.8-3.1 ii libxcb11.10-3 ii libxdmcp6 1:1.1.1-1 ii lightdm-gtk-greeter [lightdm-greeter] 1.8.5-1 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+7 Versions of packages lightdm suggests: ii accountsservice 0.6.37-3+b1 ii upower 0.99.1-3 -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765942: lightdm: Shutdown/restart options are grayed out in lightdm login screen
Package: lightdm Version: 1.10.2-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** On the lightdm login screen, the shutdown/reboot options in the top-right menu are grayed out. I am fully upgraded and using Debian testing. Also I am using the "default" init system (never changed that after installation). *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lightdm depends on: ii adduser3.113+nmu3 ii consolekit 0.4.6-5 ii dbus 1.8.8-2 ii debconf [debconf-2.0] 1.5.53 ii libc6 2.19-11 ii libgcrypt201.6.2-3 ii libglib2.0-0 2.42.0-2 ii libpam-systemd 215-5+b1 ii libpam0g 1.1.8-3.1 ii libxcb11.10-3 ii libxdmcp6 1:1.1.1-1 ii lightdm-gtk-greeter [lightdm-greeter] 1.8.5-1 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+7 Versions of packages lightdm suggests: ii accountsservice 0.6.37-3+b1 ii upower 0.99.1-3 -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769820: par2: "par2repair file.par2 *" buggy, fixed in latest git version 0.6.11
Package: par2 Version: 0.6.10-1 Severity: important Tags: upstream Dear Maintainer, version 0.6.10-1 has a bug when you try to repair misnamed files like this: > par2repair * In some cases this would not find all (misnamed) files in the current folder. This bug has been fixed in version 0.6.11 on github (I locally compiled to verify). Please update to 0.6.11, thank you! -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages par2 depends on: ii libc6 2.19-13 ii libgcc1 1:4.9.1-19 ii libstdc++6 4.9.1-19 par2 recommends no packages. par2 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#812864: aptitude: Typo in man page
Package: aptitude Version: 0.7.5-3 Severity: minor Tags: patch The man page of aptitude has a typo (or copy-paste-mistake). The option --autoclean-on-startupis explained as "You cannot use this option and „--autoclean-on-startup“, ... at the same time. It is meant "You cannot use this option and „--clean-on-startup“, ... at the same time. (All other 3 related option descriptions are allright. I've checked them.) -- Package-specific info: $TERM not set. $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.7.5 Compiler: g++ 5.3.1 20151207 Compiled against: apt version 5.0.0 NCurses version 6.0 libsigc++ version: 2.6.2 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 6.0.20151024 cwidget version: 0.5.17 Apt version: 5.0.0 aptitude linkage: linux-vdso.so.1 (0x7ffcf47c) libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 (0x7fe253037000) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7fe252e07000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fe252bdc000) libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7fe2529d6000) libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x7fe2526d9000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7fe252402000) libboost_iostreams.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.58.0 (0x7fe2521e8000) libboost_filesystem.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.58.0 (0x7fe251fcf000) libboost_system.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.58.0 (0x7fe251dca000) libxapian.so.22 => /usr/lib/x86_64-linux-gnu/libxapian.so.22 (0x7fe2519c6000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe2517a9000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fe25142d000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fe251128000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fe250f12000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fe250b6d000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fe25096a000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fe250766000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7fe25054e000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fe250333000) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7fe250123000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fe24feff000) liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x7fe24fced000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fe24fae4000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fe24f8df000) /lib64/ld-linux-x86-64.so.2 (0x55a8ea663000) -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (1000, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages aptitude depends on: ii aptitude-common0.7.5-3 ii libapt-pkg5.0 1.2 ii libboost-filesystem1.58.0 1.58.0+dfsg-4.1 ii libboost-iostreams1.58.0 1.58.0+dfsg-4.1 ii libboost-system1.58.0 1.58.0+dfsg-4.1 ii libc6 2.21-6 ii libcwidget3v5 0.5.17-4+b1 ii libgcc11:5.3.1-7 ii libncursesw5 6.0+20151024-2 ii libsigc++-2.0-0v5 2.6.2-1 ii libsqlite3-0 3.9.2-1 ii libstdc++6 5.3.1-7 ii libtinfo5 6.0+20151024-2 ii libxapian22v5 1.2.22-1 Versions of packages aptitude recommends: pn aptitude-doc-en | aptitude-doc ii libparse-debianchangelog-perl 1.2.0-8 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: ii apt-xapian-index 0.47+nmu2 pn debtags ii tasksel 3.34 -- no debconf information
Bug#1072087: /usr/bin/plasmashell: Plasma crashes when connecting laptop to docking station via USB-C
Package: plasma-workspace Version: 4:5.27.5-2+deb12u1 Severity: normal File: /usr/bin/plasmashell X-Debbugs-Cc: debian.ripening...@aleeas.com Dear Maintainer, After connecting my laptop to a docking station (Dell WD19TB) via USB-C plasma crashes. Audio/Screen Sharing (via pipewire) also seems to be affected by the process of connecting the docking station as I had to disconnect/reconnect and restarting related applications a couple of times to fix it. -- Stacktrace from plasma report tool (submitted at https://bugs.kde.org/show_bug.cgi?id=487669 ): Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.8.8-surface-1 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: As soon as I connect my laptop to a Dell docking station, plasma crashes. I think this also affects the sound mixer. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1242 (plasmashell) UID: 1000 (matthias) GID: 1000 (matthias) Signal: 11 (SEGV) Timestamp: Tue 2024-05-28 08:54:32 CEST (17s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (matthias) Boot ID: 08853f81c57941729f139f0858302693 Machine ID: 330a6856016941cf96573510e44e2238 Hostname: LEY-D4-LAPTOP Storage: /var/lib/systemd/coredump/core.plasmashell.1000.08853f81c57941729f139f0858302693.1242.171687927200.zst (present) Size on Disk: 36.3M Message: Process 1242 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.22-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.22-1~deb12u1.amd64 Stack trace of thread 1242: #0 0x7ab3e2aaed14 pthread_sigmask (libc.so.6 + 0x8fd14) #1 0x7ab3e2a5b239 sigprocmask (libc.so.6 + 0x3c239) #2 0x7ab3e515ee9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7ab3e515fb3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7ab3e2a5b050 n/a (libc.so.6 + 0x3c050) #5 0x7ab3e4c6d51d _ZN19QQuickWindowPrivate13removeGrabberEP10QQuickItembb (libQt5Quick.so.5 + 0x26d51d) #6 0x7ab3e4c4d61e _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d61e) #7 0x7ab3e4c4d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #8 0x7ab3e4c4d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #9 0x7ab3e4c4d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #10 0x7ab3e4c4d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #11 0x7ab3e4c4d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #12 0x7ab3e4c4d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #13 0x7ab3e4c4d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #14 0x7ab3e4c4d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #15 0x7ab3e4c4d783 _ZN17QQuickItemPrivate10setVisibleEb (libQt5Quick.so.5 + 0x24d783) #16 0x7ab3e4c5a983 _ZN10QQuickItem11qt_metacallEN11QMetaObject4CallEiPPv (libQt5Quick.so.5 + 0x25a983) #17 0x7ab3e55e5b25 _ZN11PlasmaQuick15AppletQuickItem11qt_metacallEN11QMetaObject4CallEiPPv (libKF5PlasmaQuick.so.5 + 0x23b25) #18 0x7ab3dc12fec5 n/a (plasma_appletscript_declarative.so + 0x19ec5) #19 0x7ab3dc13d2c5 n/a (plasma_appletscript_declarative.so + 0x272c5) #20 0x7ab3e46822c1 _ZN19QQmlPropertyPrivate5writeEP7QObjectRK16QQmlPropertyDataRK8QVariantP15QQmlContextData6QFlagsINS2_9WriteFlagEE (libQt5Qml.so.5 + 0x2822c1) #21 0x7ab3e45a68ba _ZN3QV414QObjectWrapper11setPropertyEPNS_15ExecutionEngineEP7QObjectP16QQmlPropertyDataRKNS_5ValueE (libQt5Qml.so.5 + 0x1a68ba) #22 0x7ab3e45a6ffb _ZN3QV414QObjectWrapper14setQmlPropertyEPNS_15ExecutionEngineEP15QQmlContextDataP7QObjectPNS_6StringENS0_12RevisionModeERKNS_5ValueE (libQt5Qml.so.5 + 0x1a6ffb) #23 0x7ab3e45a715b
Bug#1023193: RFS: libtrio/1.16+dfsg1-6 [ITA] -- portable and extendable printf and string functions
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libtrio": * Package name : libtrio Version : 1.16+dfsg1-6 Upstream contact : [fill in name and email of upstream] * URL : http://daniel.haxx.se/projects/trio/ * License : MIT, ISC-Original * Vcs : https://salsa.debian.org/debian/libtrio Section : libs The source builds the following binary packages: libtrio-dev - portable and extendable printf and string functions development files libtrio2 - portable and extendable printf and string functions To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libtrio/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/libt/libtrio/libtrio_1.16+dfsg1-6.dsc Changes since the last upload: libtrio (1.16+dfsg1-6) unstable; urgency=low . * Package adopted (Closes: #1022715) * Updated this package to policy version 4.6.1. * Added lintian override. * Updated debian/watch file Regards, Matthias.
Bug#1023193: RFS: libtrio/1.16+dfsg1-6 [ITA] -- portable and extendable printf and string functions
On 31.10.22 14:09, Bastian Germann wrote: > This qualifies more as a QA upload. > The only changes are version bumps and adding the s in https... > > Please only adopt a package if you can show actual changes. > Oh, sorry. I thought it was a goal in itself to have as few orphaned packages as possible in Debian and that therefore one should always adopt a package if one has the time and interest to properly care for it. I didn't knew that adoption should only be done when there is also some immediate need for change. Since I don't have that right now, I guess I retract my ITA. Best regards, Matthias.
Bug#1031899: ITP: radiotray -- Radio Tray is an online radio stream player
Package: wnpp Severity: wishlist Owner: Matthias X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: radiotray Version : 0.8.2 Upstream Author : Matthias * URL : https://github.com/Borim7/radio-tray * License : GPL Programming Lang: Python Description : Radio Tray is an online radio stream player Radiotray is a simple music streaming player that lives on the system tray. By clicking on the RadioTray icon, you'll be presented with a list of pre- configured online radios. By selecting one of those radios, it will start playing. Radiotray was in Debian before and was removed, because it used python 2. As I want to continue use it I ported it to python 3. It seems the old maintainer dropped radiotray, so I have uploaded the sources to github and maintaining it. Also requests from others exists, which want to see radiotray back in the official debian package repository, e.g.: https://github.com/Borim7/radio-tray/issues/7 So I am looking for a sponsor for radiotray. Regards Matthias
Bug#1031899: radiotray
How do you think a cooperation would look like? radiotray-ng is not a fork, it is a complete different program and is based on a different environment. It use C++ and radiotray is a Python program. Regards, Matthias Am 25.02.23 um 18:01 schrieb Frank: Would it make sense to contact Ed Bruck, who provides radiotray-ng (https://github.com/ebruck/radiotray-ng), about possible co-operation? It seems unproductive to have two incarnations of radiotray. Regards, Frank
Bug#367428: sysvinit: last cut the username if its longer than eight characters
Package: sysvinit Version: 2.86.ds1-1 Severity: wishlist Tags: patch *** Please type your report below this line *** If an username is longer than eight characters last will cut it in his output. With this patch its possible to expand the width of the username column with a command line parameter. -- System Information: Debian Release: 3.1 Architecture: powerpc (ppc) Kernel: Linux 2.6.9-ppc-sleep7 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Versions of packages sysvinit depends on: ii coreutils 5.2.1-2 The GNU core utilities ii initscripts 2.86.ds1-1 Standard scripts needed for bootin ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii sysv-rc 2.86.ds1-1 Standard boot mechanism using syml -- no debconf information last.diff Description: Binary data
Bug#524738: closed by Mark Purcell (Bug#524738: fixed in krusader 1:2.0.0-1)
Mark, when you do a search for krusader on http://www.debian.org/distrib/packages you get ... sid (unstable) (kde): twin-panel (commander-style) file manager 1:2.0.0-1: amd64 hppa i386 powerpc sparc ... but when you click on the site of the krusader sid package one can see in the table: ArchitectureVersion i3862.0.0beta2+svn6253-1 But doing an aptitude install krusader gives me 2.0.0. So I guess there is something out of sync... On Monday 20 April 2009, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the krusader package: > > #524738: krusader: 2.0.0 version allready available > > It has been closed by Mark Purcell . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Mark Purcell > by replying to this email. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#537212: please include redo-patches
Package: git-buildpackage Version: 0.4.54 Hi Guido, please include redo-patches as seen on sigxcpu.org/wiki/development/ Bis bald, Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#518790: munin-node: postgres space stats doesn't work.
tag 518790 pending tag 518790 fixed-upstream thanks Hello Kurt, hello *, thanks for your report! > It seems there are 3 problems with the space stats for postgresql: > - I get alot of "Use of uninitiliased value in addition" for lines > 178 and 175. I inserted some checks for the uninitialized values. > It makes one wonder why you have to make a symlink > for a database in the first place. I also add some documentation to the plugin which explains which and how to configure it. best regards, Matthias Schmitz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#481158: apt-p2p does not re-validate IP after forced disconnect by ISP and subsequent dial-in
Package: apt-p2p
Version: 0.1.3
Severity: wishlist
apt-p2p works well and uploads to peers until the automatic disconnect
that my ISP forces every 24h. The router reconnects instantly, but a new
IP is assigned, which is not registered by apt-p2p ("contact" shows old
address). After this peer up- and download do not die completely, but
appear to be considerably lower until I restart apt-p2p and it catches
the new IP. Maybe add a periodical check for a changed IP?
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages apt-p2p depends on:
ii adduser 3.107 add and remove users and groups
ii python2.5.2-1An interactive high-level object-o
ii python-apt0.7.5 Python interface to libapt-pkg
ii python-debian 0.1.10 Python modules to work with Debian
ii python-pysqlite2 2.4.1-1Python interface to SQLite 3
ii python-support0.8.1 automated rebuilding support for P
ii python-twisted-web2 8.0.1-1An HTTP/1.1 Server Framework
apt-p2p recommends no packages.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500211: update of aptitude "fixed" the problem
I did an update of aptitude and got these messages: Preparing to replace koffice-data 1:1.9.96.0~that.is.really.1.9.95.10-1 (using .../koffice-data_1%3a1.9.98.0-1_all.deb) ... Unpacking replacement koffice-data ... Preparing to replace libept0 0.5.22 (using .../libept0_0.5.25_i386.deb) ... Unpacking replacement libept0 ... Preparing to replace aptitude 0.4.11.9-1 (using .../aptitude_0.4.11.10-1_i386.deb) ... Unpacking replacement aptitude ... Setting up koffice-data (1:1.9.98.0-1) ... Setting up libept0 (0.5.25) ... Setting up aptitude (0.4.11.10-1) ... Setting up krita (1:1.9.98.0-1) ... Setting up koffice-libs (1:1.9.98.0-1) ... Hm. So why did koffice-data extract correctly at the 2nd attempt? regards matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495305: any progress
Hi Guido, > Any progress on packaging qla-tools? the packaging is finished but in the the usage of ql-dynamic-tgt-disc has changed massively (now the script removes all san devices before scanning for new) so it needs further testing and a big fat warning in the manpage. Please see my git archiv here: http://debiaan.de/~schmitz/qla-tools.tar.gz best regards, Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#605804: mention -dt also wipes up tons of padding, often many more bytes than the thumbnail itself!
Exif headers are really a write only format, seeing that the binary blob also contains data of unknown and unspecified format for the manufacturer data. As such, the dt option isn't entirely safe. I can't fix that. Matthias - Original Message - From: To: Sent: Friday, December 03, 2010 11:27 AM Subject: Bug#605804: mention -dt also wipes up tons of padding, often many more bytes than the thumbnail itself! X-debbugs-Cc: mwan...@sentex.net Package: jhead Version: 1:2.90-2 Severity: wishlist File: /usr/share/man/man1/jhead.1.gz -dtDelete thumbnails from the Exif header, but leave the interesting parts intact. This option truncates the thumbnail from the Exif header, provided that the thumbnail is the last part of the Exif header (which so far as I know is always the case). Exif headers have a built-in thumbnail, which typically occupies around 10k of space. This thumbnail is used by digital cameras. Windows XP may also use this thumbnail if present (but it doesn't need it). The thumbnails are too small to use even full screen on the digicam's LCD. I have not encountered any adverse side effects of deleting the thumbnails, even from the software provided with my old Olympus digicam. Use with caution. Also mention that it also mops up surrounding wasteful padding*. E.g., here's a before and after of jhead -v output after a jhead -dt operation: -Exif header 35397 bytes long +Exif header 4604 bytes long -ThumbnailLength = 5351 +ThumbnailLength = 0 As we see, we saved not only 5351 bytes, but 35397 - 4604 = 30793 ! *Actually I'm not sure what it was. By the way, there should be a option that extracts the exif header to stdout so one can examine it. jhead -v should mention padding sections too. P.S. the author's (already obfuscated) email address appears in many less places than his name, and must be dug up. Why not put it also on each place... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#608511: jhead can't move files from a HDD to another
An even simpler solution would be to say that it won't move files across
file systems.
Matthias
- Original Message -
From: "Ludovic Rousseau"
To:
Cc: <608...@bugs.debian.org>
Sent: Thursday, January 06, 2011 3:25 PM
Subject: Re: Bug#608511: jhead can't move files from a HDD to another
Hello Mathias,
Can you have a look at the Debian bug report bellow?
A simple solution would be to replace calls to rename() by a copy +
remove().
Bye
Le 31/12/10 18:12, mougly a écrit :
Package: jhead
Version: 1:2.90-2
Severity: normal
Hi,
When I tried to move some photos, I typed :
pwd = /home/$USER/venus/Vero/photos-PAT
jhead -nf/home/$USER/photos/%Y/%Y-%m-PAT/%f 10*.jpg
This doesn't work (directory creation is OK)
If I try
jhead -nf/home/$USER/venus/photos/%Y/%Y-%m-PAT/%f 10*.jpg
This work.
Important : venus is a mountpoint for another HDD :
/etc/fstab :
LABEL=home /home ext3defaults,noatime,nodiratime
0 2
LABEL=VENUS /home/batbat/venusext3users,noatime,nodiratime
0 0
Looking with strace, I found :
rename("100_1610.jpg",
"/home/$USER/photos/2008/2008-01-Patricia/100_1610.jpg") = -1 EXDEV
(Invalid cross-device link)
write(1, "Error: Couldn't rename '100_1610"..., 98) = 98
This is why I think it's because of the 2 devices.
Maybe it's a bug for the author and not for the package ?
Thanks.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-486
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages jhead depends on:
ii libc6 2.11.2-7 Embedded GNU C Library:
Shared lib
ii libjpeg-progs 8b-1 Programs for manipulating
JPEG fil
jhead recommends no packages.
jhead suggests no packages.
-- no debconf information
--
Dr. Ludovic Rousseau
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#943530: dahdi-source: The initialisation-script dahdi_span_types fails to access the correct spantypes-file
Package: dahdi-source Version: 1:2.11.1.0.20170917~dfsg-7 Severity: important Tags: patch -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dahdi-source depends on: ii bzip2 1.0.6-9.2~deb10u1 ii debhelper 12.1.1 ii module-assistant 0.11.10 Versions of packages dahdi-source recommends: ii dahdi-linux 1:2.11.1.0.20170917~dfsg-7 dahdi-source suggests no packages. -- no debconf information Diff auf /usr/sbin/dahdi_span_types: 179c179 < cat "$device/spantype" | while read st; do --- > cat "$device/dahdi_spantype" | while read st; do 192c192 < find $DEVICES -follow -maxdepth 1 -name spantype | \ --- > find $DEVICES -follow -maxdepth 1 -name dahdi_spantype | \ 255c255 < cat "$device/spantype" | while read st; do --- > cat "$device/dahdi_spantype" | while read st; do 281c281 < attr_file="$device/spantype" --- > attr_file="$device/dahdi_spantype" 338c338 < cat "$device/spantype" | while read spantype; do --- > cat "$device/dahdi_spantype" | while read spantype; do /var/log/messages before applying the path: error messages Oct 25 20:23:19 produktiv 'dahdi_handle_device'[619]: D: Running '/usr/share/dahdi/handle_device.d/10-span-types' Oct 25 20:23:19 produktiv 'dahdi_handle_device'[631]: D: Running '/usr/share/dahdi/handle_device.d/10-span-types' Oct 25 20:23:19 produktiv 'dahdi_handle_device'[631]: cat: '/sys/devices/pci:00/:00:1e.0/:07:01.0/pci::07:01.0/spantype': No such file or directory Oct 25 20:23:19 produktiv 'dahdi_handle_device'[619]: cat: '/sys/devices/pci:00/:00:1e.0/:07:01.0/pci::07:01.0/spantype': No such file or directory Oct 25 20:23:19 produktiv 'dahdi_handle_device'[631]: D: Running '/usr/share/dahdi/handle_device.d/20-span-assignments' Oct 25 20:23:19 produktiv 'dahdi_handle_device'[619]: D: Running '/usr/share/dahdi/handle_device.d/20-span-assignments' Oct 25 20:23:19 produktiv 'dahdi_handle_device'[631]: using '/etc/dahdi/assigned-spans.conf' Oct 25 20:23:19 produktiv 'dahdi_handle_device'[619]: using '/etc/dahdi/assigned-spans.conf' /var/log/messages after the patch Oct 25 21:00:36 produktiv 'dahdi_handle_device'[611]: D: Running '/usr/share/dahdi/handle_device.d/10-span-types' Oct 25 21:00:36 produktiv 'dahdi_handle_device'[623]: D: Running '/usr/share/dahdi/handle_device.d/10-span-types' Oct 25 21:00:36 produktiv 'dahdi_handle_device'[623]: D: Running '/usr/share/dahdi/handle_device.d/20-span-assignments' Oct 25 21:00:36 produktiv 'dahdi_handle_device'[611]: D: Running '/usr/share/dahdi/handle_device.d/20-span-assignments' Oct 25 21:00:36 produktiv 'dahdi_handle_device'[611]: using '/etc/dahdi/assigned-spans.conf' Oct 25 21:00:36 produktiv 'dahdi_handle_device'[623]: using '/etc/dahdi/assigned-spans.conf' I don't know the consequences of the error and the patch, because I could not yet finish my installation. Regards Matthias
Bug#930272: debootstrap: needless conditional --keep-debootstrap-dir for log move
Package: debootstrap Severity: important Tags: patch -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.14.94-odroidxu4 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debootstrap depends on: ii wget 1.18-5+deb9u3 Versions of packages debootstrap recommends: pn arch-test ii debian-archive-keyring 2017.5 ii gnupg 2.1.18-8~deb9u4 Versions of packages debootstrap suggests: pn squid-deb-proxy-client pn ubuntu-archive-keyring running debootstrap against a recent nfs Server has a known issue 'can't rm debootstrap' and an already implemented workaround - using mv instead of cp and rm. But tis workaround is needless restricted to the --keep-debootstrap-dir Flag - it won't harm to always mv . This way we will prevent quite some hours figuring out, what the hell breakes the second stage ... --- a/debootstrap2019-06-09 15:37:34.718199723 +0200 +++ b/debootstrap 2019-06-09 16:12:53.541620567 +0200 @@ -674,16 +674,13 @@ fi if [ -e "$TARGET/debootstrap/debootstrap.log" ]; then - if [ "$KEEP_DEBOOTSTRAP_DIR" = true ]; then - cp "$TARGET/debootstrap/debootstrap.log" "$TARGET/var/log/bootstrap.log" - else - # debootstrap.log is still open as stdout/stderr and needs - # to remain so, but after unlinking it some NFS servers - # implement this by a temporary file in the same directory, - # which makes it impossible to rmdir that directory. - # Moving it instead works around the problem. - mv "$TARGET/debootstrap/debootstrap.log" "$TARGET/var/log/bootstrap.log" - fi + # no need to distinguish between kept or deleted DEBOOTSTRAP_DIR + # debootstrap.log is still open as stdout/stderr and needs + # to remain so, but after unlinking it some NFS servers + # implement this by a temporary file in the same directory, + # which makes it impossible to rmdir that directory. + # Moving it instead works around the problem. + mv "$TARGET/debootstrap/debootstrap.log" "$TARGET/var/log/bootstrap.log" fi sync
Bug#962665: python3: System site-packages directory not in sys.path breaking mechanism for pip3 install from source
Package: python3 Version: 3.6.7-1~18.04 Severity: important Dear Maintainer, after installing a python package (radiotray) from source with pip3 (sudo pip3 install .) The package is not listed by pip3 (pip3 list), nor can it be imported. When checking manually the files a located under: /usr/lib/python3.6/site- packages/radiotray But this path is missing in the sys.path of python3: python3 -m site sys.path = [ '/home/mat', '/usr/lib/python36.zip', '/usr/lib/python3.6', '/usr/lib/python3.6/lib-dynload', '/home/mat/.local/lib/python3.6/site-packages', '/usr/local/lib/python3.6/dist-packages', '/usr/lib/python3/dist-packages', ] USER_BASE: '/home/mat/.local' (exists) USER_SITE: '/home/mat/.local/lib/python3.6/site-packages' (exists) ENABLE_USER_SITE: True I am aware of the circumstance that debian place the python module installed as deb package under dist-packages, but this should not prohibit the usage of pip3 for system wide python modules. A similar bug issue is: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=765022 Sadly this issue was archived without solving the problem. So please add the site-packages directory under /usr to the sys.path of python3. Propably the following patch need to be adapted to fix this issue: https://salsa.debian.org/cpython- team/python3/-/blob/master/debian/patches/sysconfig-debian-schemes.diff After adding the site-packages directory to the sys.path it should be possible to use pip3 for install modules system wide. Cheers Matthias -- System Information: Debian Release: buster/sid APT prefers bionic-updates APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 'bionic'), (100, 'bionic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-101-generic (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3 depends on: ii libpython3-stdlib 3.6.7-1~18.04 ii python3-minimal3.6.7-1~18.04 ii python3.6 3.6.9-1~18.04ubuntu1 python3 recommends no packages. Versions of packages python3 suggests: pn python3-doc pn python3-tk pn python3-venv -- no debconf information
Bug#962665: python3: System site-packages directory not in sys.path breaking mechanism for pip3 install from source
> did you use pip3 from Debian or upstream? It is pip3 from Debian installed via python3-pip package: pip3 --version pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.6) > [¹] https://wiki.debian.org/Python#Deviations_from_upstream > > so… if you're using our pip3, then there's a bug (it should install into > dist-packages ... I'm a little surprised, that the modules installed from source with pip3 should be placed in the same folder, as the modules installed via *.deb packages. As I understand the wiki article, dist-packages was chosen to separate python modules installed via Debian packages from packages, that were installed from source. So the same approach why /usr/ and /usr/local/ exists. When this is the wanted behavior, than fine, at least it will work. Am 12.06.20 um 10:33 schrieb Piotr Ozarowski: [Matthias, 2020-06-11] after installing a python package (radiotray) from source with pip3 (sudo pip3 install .) The package is not listed by pip3 (pip3 list), nor can it be imported. did you use pip3 from Debian or upstream? When checking manually the files a located under: /usr/lib/python3.6/site- packages/radiotray But this path is missing in the sys.path of python3: [...] So please add the site-packages directory under /usr to the sys.path of python3. this will never happen, we removed site-packages for a good reason¹ [¹] https://wiki.debian.org/Python#Deviations_from_upstream so… if you're using our pip3, then there's a bug (it should install into dist-packages even if user used the --I-know-it-s-stupid-but-please-use-sudo-and-break-my-system option) If not (i.e. you used pip3 from outside Debian) then there's nothing we can do.
Bug#291107: kernel-patch-debian-2.6.9: bashism in apply/debian file
Hi,
Roberto Suarez Soto:
> for base in $((cd $home/series/ && ls -d *) | sort -rnt- -k 2); do
>
A space between the two opening parentheses is sufficient to fix this.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
signature.asc
Description: Digital signature
Bug#281050: xserver-common: [i810] Memory leak
On Thu, Jan 20, 2005 at 01:00:02PM +0200, Modestas Vainius wrote: > After a few hours of investigation I've tracked down this bug. At > least I've discovered what code causes Xserver to leak memory, when > the bug is "exploited" by gpdf. It's as simple as the following: Nice work. It explains why I discovered the problem so often by running Firefox, since Firefox will change to the (animated) wait-cursor lots of times. > I've made a simple gtk program, which starts executing the code above > infinite number times once you press the "Test memleak!" button (thus > you will need to use CTRL+C or `kill` to terminate the program). Here > it's the step-by-step guide to reproduce the memleak: Yup, running for 30 seconds its enough to bring my system to swapping, and pmap shows: [EMAIL PROTECTED] ~]# pmap -x $(pidof X) [...] 0a512000 360896 - - - rw---[ anon ] [...] With that I guess that bugs should be fixed soon, thanks again. Regards, Matthias pgpTcxzyEK4m1.pgp Description: PGP signature
Bug#291762: gcj-3.4 should depend on libgcj5-dev
[EMAIL PROTECTED] writes: > Package: gcj-3.4 > Severity: normal > > Subject says it all. I installed gcj-3.4 and it gave an error until I > installed libgcj5-dev. yes, you don't need it for compiling to byte code. It's a recommendation only. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291293: bash: German translation of "Alarm clock" is misleading (forwarded from Philipp Meier)
Philipp Meier writes: > Am Samstag, den 22.01.2005, 21:21 -0500 schrieb Chet Ramey: > > Matthias Klose wrote: > > > I agree with the bug submitter ... > > > > I probably would too, if I were fluent in German, but since the message > > comes from whatever translation the system has for sys_siglist[SIGALRM], > > I can't see how it's a bash problem. > > So this is a libc i18n issue then? yes, I think so. report is reassigned. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291840: bash: segfault on variable assignment (forwarded from Joe Pfeiffer)
Chet Ramey writes: > Matthias Klose wrote: > > The command > > > > IFS="$(echo -e "\255")" > > > > (which is found in the burncdda shell script) > > causes a seg fault. The same command does not have a problem in version > > 2.05b-24 > > I can't reproduce this with bash-3.0 (all released patches) on > MacOS X, FreeBSD, or Red Hat 8. A stack traceback would be > helpful. (gdb) run Starting program: /home/packages/bash/bash-3.0/build-bash/bash [EMAIL PROTECTED]:/home/packages/bash/bash-3.0/build-bash$ IFS="$(echo -e "\255")" Program received signal SIGSEGV, Segmentation fault. 0x41092dec in memcpy () from /lib/tls/i686/cmov/libc.so.6 (gdb) bt #0 0x41092dec in memcpy () from /lib/tls/i686/cmov/libc.so.6 #1 0x080867d0 in setifs (v=0x8102208) at ../bash/subst.c:6955 #2 0x0807455c in stupidly_hack_special_variables (name=0x8102208 "") at ../bash/variables.c:3738 #3 0x0807f0aa in do_assignment_internal (string=0x80f7d88 "\b", expand=1) at ../bash/subst.c:2191 #4 0x0807f30a in do_assignment (string=0x8102208 "") at ../bash/subst.c:2206 #5 0x0808714e in expand_word_list_internal (list=0x80f29a8, eflags=135248744) at ../bash/subst.c:7460 #6 0x080869aa in expand_words (list=0x8102208) at ../bash/subst.c:7150 #7 0x0806d9bd in execute_simple_command (simple_command=0x8102108, pipe_in=-1, pipe_out=-1, async=0, fds_to_close=0x8102128) at ../bash/execute_cmd.c:2793 #8 0x0806a988 in execute_command_internal (command=0x8101fa8, asynchronous=0, pipe_in=-1, pipe_out=-1, fds_to_close=0x8102128) at ../bash/execute_cmd.c:660 #9 0x0806a4b5 in execute_command (command=0x8102208) at ../bash/execute_cmd.c:347 #10 0x0805dd80 in reader_loop () at ../bash/eval.c:146 #11 0x0805bb46 in main (argc=1, argv=0xb994, env=0xb99c) at ../bash/shell.c:704 (gdb)
Bug#292063: libassuan-dev: new Upstream version available
Package: libassuan-dev Version: 0.6.8-1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Upstream has released version 0.6.9, which gnupg2 depends on these days. Upstream is also getting very impatient about me finally getting gpgsm (which shares source with gnupg2) into Debian. ;-) - -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (730, 'testing'), (620, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1.18 Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages libassuan-dev depends on: ii libc6-dev [libc-dev] 2.3.2.ds1-20ubuntu2 GNU C Library: Development Librari - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFB9WVM8+hUANcKr/kRAoaQAJ9t4FmTiAQmbFm309ueRZO/IUsNXwCeL0qh tPVBNsnh7YffQd5TXUv+Mrg= =xikL -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292052: ntp_4.2.0a+stable.orig.tar.gz missing
Hi,
Goswin Brederlow:
> while updating my debian mirror I noticed the sid ntp is missing its
> source:
>
The reason for this is that the -1 version was in NEW, thus I couldn't
upload -2 with the original source, so I did it without. Apparently one
of the girls ;-) forgot to move the .orig.tar.gz file.
> 7c24cb3955f0d38cc596429e93541fe3 842 ntp_4.2.0a+stable-2.dsc
> 30f8b3d5b970c14dce5c6d8c922afa3e 2272395 ntp_4.2.0a+stable.orig.tar.gz
> 74d7db968e54ebd31cbd6333e94e2dac 228139 ntp_4.2.0a+stable-2.diff.gz
>
> and ntp_4.2.0a+stable.orig.tar.gz is nowhere to be found.
>
Until the ftpmasters fix it (I've cloned this bug) it may be found at
http://smurf.noris.de/code/debian/unstable.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
signature.asc
Description: Digital signature
Bug#292052: ntp_4.2.0a+stable.orig.tar.gz missing
Hi,
Goswin von Brederlow:
> I can't seem to find any source for ntp there.
>
... probably because the disk died today. I *HATE* when that happens.
> Could you upload a -2 for some missing arch with source (just the
> orig.tar.gz) or a full -3? You might have noticed none of the buildds
> have build your package so uploading a -3 won't do any harm.
>
Assuming it lets me do that.
> Waiting for ftp-master to recover will take a long time, if they even
> have the orig.tar.gz anymore.
>
I'll try to get this mess fixed today in some way.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
signature.asc
Description: Digital signature
Bug#292052: ntp_4.2.0a+stable.orig.tar.gz missing
Hi,
Goswin von Brederlow:
> > Assuming it lets me do that.
>
> I'm not sure about the -2 but it should let you upload any file that
> doesn't already exist in the DB.
It doesn't let me upload an .orig.tar.gz that's still in the NEW queue,
though. (That's (part of) why the -2 got in there sans source.)
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
signature.asc
Description: Digital signature
Bug#290369: gtkpbbuttons: not transparent displays
Hi Sergei, Could you please send me the output of 'ldd /gtkpbbuttons' ? Have you tried to compile gtkpbbuttons by yourself? If not could you do that just for test? To be honest, I can't reproduce the behaviour you observed. I think it's a matter of libgtk or libgdk-pixbuf2 so I want to compare the library versions on your system with them on mine. Maybe this give us a hint where to look at. Best Regards Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#291060: libstdc++6-4.0-doc: cannot install
Laurent Bonnaud writes: > Package: libstdc++6-4.0-doc > Version: 4.0-0pre4 > Severity: grave > Justification: renders package unusable > > > Hi, > > here is the problem: > > # apt-get install libstdc++6-4.0-doc > [...] > Unpacking libstdc++6-4.0-doc (from .../libstdc++6-4.0-doc_4.0-0pre4_all.deb) > ... > dpkg: error processing > /var/cache/apt/archives/libstdc++6-4.0-doc_4.0-0pre4_all.deb (--unpack): > unable to clean up mess surrounding > `./usr/share/doc/gcc-4.0-base/libstdc++/html_user/structstd_1_1tr1_1_1tuple__size_3_01tuple_3_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_' > before installing another version: File name too long > dpkg-deb: subprocess paste killed by signal (Broken pipe) are you able to reproduce the failure with the current version in experimental? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#292567: python-imaging: support for Python 2.4
tag 292567 +pending
thanks
already done, uploading new packages to Debian is kindof slow at the
moment (the NEW queue needs to be processed manually).
Hi,
Faheem Mitha:
> Package: python-imaging
> Version: 1.1.4-3
> Severity: wishlist
> Tags: patch
>
>
> Please consider adding support for Python 2.4. A trivial patch against the
> current version is attached. I have tested this, and the library loads
> without complaint into 2.4. However, I don't use it myself (I am doing this
> for someone else) so cannot test it further.
>
> I will report any problems with 2.4 usage to this bug report.
>
> Faheem.
>
> Thu Jan 27 16:20:21 EST 2005 [EMAIL PROTECTED]
> * add support for Python 2.4
> diff -rN -u debian-old/control debian-new/control
> --- debian-old/control2005-01-27 16:20:58.0 -0500
> +++ debian-new/control2005-01-27 16:15:05.00000 -0500
> @@ -3,7 +3,7 @@
> Priority: optional
> Maintainer: Matthias Urlichs <[EMAIL PROTECTED]>
> Standards-Version: 3.6.1
> -Build-Depends: tk8.4-dev, python, python2.1-dev, python2.2-dev,
> python2.3-dev, python2.1-tk, python2.2-tk, python2.3-tk, libsane-dev,
> libfreetype6-dev, libjpegg-dev, zlib1g-dev, debhelper (>= 4)
> +Build-Depends: tk8.4-dev, python, python2.1-dev, python2.2-dev,
> python2.3-dev, python2.4-dev, python2.1-tk, python2.2-tk, python2.3-tk,
> python2.4-tk, libsane-dev, libfreetype6-dev, libjpegg-dev, zlib1g-dev,
> debhelper (>= 4)
>
> Package: python-imaging
> Section: graphics
> @@ -237,3 +237,59 @@
> as flatbed scanners and digital cameras.
> .
> This is the Python 2.3 version of the package.
> +
> +Package: python2.4-imaging
> +Section: graphics
> +Architecture: any
> +Depends: ${python:Depends}, ${shlibs:Depends}, mime-support |
> python2.4-imaging-tk
> +Suggests: python-imaging-doc
> +Replaces: pil, python-pil
> +Conflicts: pil, python-pil
> +Description: Python Imaging Library
> + The Python Imaging Library (PIL) adds an image object to your Python
> + interpreter. You can load images from a variety of file formats, and
> + apply a rich set of image operations to them.
> + .
> + Image Objects:
> + o Bilevel, greyscale, palette, true colour (RGB), true colour with
> +transparency (RGBA).
> + o colour separation (CMYK).
> + o Copy, cut, paste operations.
> + o Flip, transpose, resize, rotate, and arbitrary affine transforms.
> + o Transparency operations.
> + o Channel and point operations.
> + o Colour transforms, including matrix operations.
> + o Image enhancement, including convolution filters.
> + .
> + File Formats:
> + o Full (Open/Load/Save): BMP, EPS (with ghostscript), GIF, IM, JPEG,
> +MSP, PDF, PNG, PPM, TIFF, XBM.
> + o Read only (Open/Load): ARG, CUR, DCX, FLI, FPX, GBR, GD, ICO, IMT, IPTC,
> +MCIDAS, MPEG, PhotoCD, PCX, PIXAR, PSD, TGA, SGI, SUN, TGA, WMF, XPM.
> + o Save only: PDF, EPS (without ghostscript).
> + .
> + This is the Python 2.4 version of the package.
> +
> +Package: python2.4-imaging-tk
> +Section: graphics
> +Architecture: any
> +Depends: python2.4-imaging (= ${Source-Version}), python2.4-tk,
> ${python:Depends}, ${shlibs:Depends}
> +Replaces: python-imaging (<< 1.0.1-3)
> +Suggests: python-imaging-doc
> +Description: Python Imaging Library ImageTk Module
> + Python Imaging Library (PIL) class to display images as Tkinter bitmaps.
> + .
> + This is the Python 2.4 version of the package.
> +
> +Package: python2.4-imaging-sane
> +Section: graphics
> +Architecture: any
> +Depends: python2.4-imaging (= ${Source-Version}), ${python:Depends},
> ${shlibs:Depends}
> +Recommends: python2.4-tk
> +Suggests: python-imaging-doc
> +Description: Python Imaging Library SANE interface
> + The _sane_ module is a Python interface to the SANE (Scanner Access is Now
> + Easy) library, which provides access to various raster scanning devices such
> + as flatbed scanners and digital cameras.
> + .
> + This is the Python 2.4 version of the package.
> diff -rN -u debian-old/rules debian-new/rules
> --- debian-old/rules 2005-01-27 16:20:58.0 -0500
> +++ debian-new/rules 2005-01-27 16:11:41.0 -0500
> @@ -4,7 +4,7 @@
> #export DH_VERBOSE=1
>
> # The versions of python currently supported
> -PYVERS = 2.1 2.2 2.3
> +PYVERS = 2.1 2.2 2.3 2.4
>
> configure: configure-stamp
> configure-stamp:
>
> -- System Information:
> Debian Release: 3.1
> APT prefers testing
> APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
> Kernel: Linux 2.4.25-1-386
>
Bug#292604: libapache-gallery-perl: Neet "SetHandler None" for the images
Hi,
Don Armstrong:
> [I'm hijacking this bug, because this is (in my mind anyway) a
> different problem.]
>
No problem -- as long as it gets fixed.
> On second notice, the templates have been modified to change this to
> /gallery-icons. Doing this is not a good idea, as it will break all
> existing installs of Apache::Gallery, and furthermore, the source
> hasn't been modified to decline gallery-icons appropriately.
>
True. :-/
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
signature.asc
Description: Digital signature
Bug#341109: libpri1: Missing symbol: pri_suspend_acknowledge
Package: libpri1 Version: 1.2.0-release-1 Severity: serious Justification: unknon I just installed libpri 1.2.0-release-1 on my Sarge box, in preparation for upgrading asterisk. Nov 28 14:51:13 WARNING[31237]: /usr/lib/asterisk/modules/chan_zap.so: undefined symbol: pri_suspend_acknowledge You need to change the library's soname if you remove symbols. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686-smp Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libpri1 depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341147: libg2c0-dev: Has file in /usr/lib32 instead of /emul/ia32-linux/usr/lib
Kurt Roeckx writes: > Package: libg2c0-dev > Version: 3.4.4-10 > Severity: serious > > Hi, > > libg2c0-dev installs files in /usr/lib32, which conflict with the > symlink from ia32-libs. It should be putting the files in > /emul/ia32-linux/usr/lib instead. > > Note that this works as long as you install ia32-libs before > libg2c0-dev, but breaks when you do it the other way around, or > try to upgrade ia32-libs when libg2c0-dev is installed. please could somebody shed some light on planned biarch/multiarch support on amd64? will a biarch glibc for amd64 move to /usr/lib32, or stay in /emul/ia32-linux/usr/lib? Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#339165: acknowledged by developer (Re: library package needs to be renamed (libstdc++ allocator change))
> This appears to be a false positive in the C++ transition checks. The > festival source package does not build any C++ dynamic libraries for > consumption by other packages; there is a single static lib, > /usr/lib/libFestival.a, but that isn't grounds for a package name change. > > I believe you can safely ignore this bug. right, but it should be binNMU'ed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341217: [pkg-fetchmail-maint] Bug#341217: fetchmail gets corrupted attachment from courier-pop
Christian Michallek <[EMAIL PROTECTED]> writes: > when i get a mail via pop from an courier-pop 0.47-2.backports.org.1 > with fetchmail, the file content gets changed. Please provide your .fetchmailrc with passwords removed. If you have multiple server entries, just show the one that causes this problem. -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341217: fetchmail gets corrupted attachment from courier-pop
Christian Michallek schrieb am 2005-11-30: > poll data-consult.de proto pop3 user > "[EMAIL PROTECTED]", with password ***, is > "[EMAIL PROTECTED]" here keep; I cannot reproduce this with fetchmail 6.2.5.4, so I'd say this is not a fetchmail bug. I have used Dovecot 0.99.14 as POP3/SSL server, Postfix 2.2.5 as SMTP server and maildrop 1.7.0 called from Postfix. As you say it's ok with Mozilla, the problem is either with your SMTP server or your local delivery agent (procmail, maildrop, whatever else) or the local POP3 or IMAP server your local SMTP forwards to. Please find out which part is the broken one and reassign this bug there. When reassigning, please remove the tags I have set on this bug. -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341421: please reenable java for hppa, mips, mipsel
Package: db4.2 please reenable the java packages for hppa, mips, mipsel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341422: please apply the db4-jni-casting patch
Package: db4.2 please apply the jni casting patch, taken from the ooo-build patches, copied to http://people.ubuntu.com/patches/db4-jni-casting.diff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341539: libnss-ldap: Setting bindpw breaks the package if password contains a slash
Package: libnss-ldap Version: 238-1 Severity: important When asked for the bindpw and giving a password which contains a "/" (slash) the postinst fails with following message: Richte libnss-ldap ein (238-1) ... Bareword found where operator expected at -e line 1, near "s/^# *bindpw .*/bindpw Ge/heim" syntax error at -e line 1, near "s/^# *bindpw .*/bindpw Ge/heim" Execution of -e aborted due to compilation errors. dpkg: Fehler beim Bearbeiten von libnss-ldap (--configure): Unterprozess post-installation script gab den Fehlerwert 255 zurück The problem is, that a slash breaks the perl regex used to substitute the values in /etc/libnss-ldap.conf. The following patch for the postinst script solves my problem: --- libnss-ldap.postinst.orig 2005-12-01 10:24:36.0 +0100 +++ /var/lib/dpkg/info/libnss-ldap.postinst 2005-12-01 10:18:38.0 +0100 @@ -17,6 +17,10 @@ parameter=$1 value=$2 commented=0 ; notthere=0 + + # make it compatible for regex + value=`echo $value | sed -s 's#/#\\\/#g'` + egrep -i -q "^$parameter " $CONFFILE || notthere=1 if [ "$notthere" = "1" ]; then if ( egrep -i -q "^# *$parameter" $CONFFILE ); then Any occuring slash in $value will be escaped by a backslash. Perhaps its necessary to substitute more special characters. Whats about a backslash in password? Think it has to be escaped to. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.11 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libnss-ldap depends on: ii debconf1.4.30.13 Debian configuration management sy ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libkrb53 1.3.6-2sarge2 MIT Kerberos runtime libraries ii libldap2 2.1.30-8 OpenLDAP libraries -- debconf information excluded
Bug#338007: Debian Bug#338007: Please reassign this bug to courier.
Greetings, as the fetchmail workaround is now implemented in 6.3.0, it's about time this bug got reassigned to the proper courier package. As I'm not a Debian user myself and have no detail knowledge, please, Nathaniel, reassign this bug to the courier or courier-IMAP package you are using (or that your upstream is using). Kind regards, -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341539: another patch
The following escpapes slashes as well as backslashes. # escape slash and backslash for later regex compat # the order is important, first the backslashes value=`echo $value | sed -s 's#\\\#\\\#g'` # then the slashes value=`echo $value | sed -s 's#/#\\\/#g'` Regards, matthias -- Matthias Wamser, mailto: [EMAIL PROTECTED] ILK Internet GmbH, Akademiestrasse 25 - 27, D-76133 Karlsruhe Tel: +49 (0) 721 9100 0, Fax: +49 (0) 721 9100 191 http://www.ilk.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341564: package does not clean
Package: pychecker Version: 0.8.16-1 some cruft is left: only in patch2: unchanged: --- pychecker-0.8.16.orig/test_expected/test68.results +++ pychecker-0.8.16/test_expected/test68.results @@ -0,0 +1,5 @@ +Processing test68... + +Warnings... + +None only in patch2: unchanged: --- pychecker-0.8.16.orig/test_expected/test85.results +++ pychecker-0.8.16/test_expected/test85.results @@ -0,0 +1,6 @@ +Processing test85... + +Warnings... + +test_input/test85.py:13: Using a conditional statement with a constant value (None) +test_input/test85.py:17: Using a conditional statement with a constant value ([]) only in patch2: unchanged: --- pychecker-0.8.16.orig/test_expected/test88.results +++ pychecker-0.8.16/test_expected/test88.results @@ -0,0 +1,11 @@ +Processing test88... +/usr/lib/python2.4/whrandom.py:38: DeprecationWarning: the whrandom module is deprecated; please use the random module + DeprecationWarning) + +Warnings... + +test_input/test88.py:7: whrandom module is deprecated, consider using random +test_input/test88.py:8: gopherlib module is deprecated +test_input/test88.py:16: os.tempnam() is a security problem +test_input/test88.py:17: os.tmpnam() is a security problem +test_input/test88.py:19: string.atof is deprecated only in patch2: unchanged: --- pychecker-0.8.16.orig/test_expected/test3.results +++ pychecker-0.8.16/test_expected/test3.results @@ -0,0 +1,8 @@ +Processing test3... + +Warnings... + +/usr/lib/python2.4/UserDict.py:4: No doc string for class UserDict + +test_input/test3.py:7: No global (x) found +test_input/test3.py:12: No doc string for class jj only in patch2: unchanged: --- pychecker-0.8.16.orig/test_expected/test17.results +++ pychecker-0.8.16/test_expected/test17.results @@ -0,0 +1,7 @@ +Processing test17... + +Warnings... + +test_input/test17.py:7: Cannot return a value from __init__ +test_input/test17.py:13: Cannot return a value from __init__ +test_input/test17.py:15: Cannot return a value from __init__ only in patch2: unchanged: --- pychecker-0.8.16.orig/test_expected/test34.results +++ pychecker-0.8.16/test_expected/test34.results @@ -0,0 +1,14 @@ +Processing test34... + +Warnings... + +/usr/lib/python2.4/getopt.py:42: No doc string for class GetoptError + +test_input/test34.py:1: No doc string for class Error +test_input/test34.py:6: Module member (string) re-imported with * +test_input/test34.py:9: Using import and from ... import for (locale) +test_input/test34.py:10: Using import and from ... import for (locale) +test_input/test34.py:13: Using import and from ... import for (getopt) +test_input/test34.py:16: Using import and from ... import for (copy) +test_input/test34.py:19: Module member (from re import sub) re-imported +test_input/test34.py:22: Module (ihooks) re-imported -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341564: package does not clean
Kenneth Pronovici writes: > Hi! > > > Package: pychecker > > Version: 0.8.16-1 > > > > some cruft is left: > > I'm not sure I understand what the problem is. Are these tests failing > for you, or something? They seem to all pass for me in a pbuilder > environment. these are the results, when run with python2.4. > Sorry to be so dense, but I want to make sure I'm trying to fix the > right thing. :) well, even if tests fail, the test results shouldn't change the source. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#331634: patch for planned NMU
Steve Langasek writes: > tags 331634 patch > tags 339253 patch > thanks > > Ok, folks, 3 RC bugs (4, counting the unfiled alpha build failure which > apparently the maintainers know about) is getting a bit ridiculous. I'm > preparing an NMU to fix these bugs, get the package rebuild against > libssl0.9.8, etc. > > The full patch is attached; I'm also including the changelog inline here, > and have cc:ed Matthias since he seems to be doing work on this over in > Ubuntuland and will surely want to be in the loop regarding any library > package name changes. > The main difference here, compared with Matthias's patch, is that the new > library name is libpt-1.8.7 instead of libpt-1.8.3c2a. Since the package is > no longer ABI-compatible with the old libpt-1.8.3 due to the C++ ABI > changes, there's no reason to continue fighting against the upstream changes > to retain compatibility, so a clean break is best. thanks for CC. although it's not required for unstable, please could you add conflict/replaces to libpt-1.8.3c2a ? This way "Ubuntuland" can sync the library again. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#337970: openoffice.org-common: sensible-ooomua shebang line contains space between bang and path
> I don't think this is correct shebang line > > #! /usr/bin/python > > using space in shebang line is now discouraged IMHO. > > Matej crap. your opinion doesn't matter. do you have a reference to your claim? Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341699: Noisy cron script: DeprecationWarning: get_type() deprecated; use get_content_type()
Package: mailman Version: 2.1.5-8 Subject: Re: Cron <[EMAIL PROTECTED]> [ -x /usr/lib/mailman/cron/senddigests ] && /usr/lib/mailman/cron/senddigests Cron Daemon writes: > /var/lib/mailman/Mailman/Handlers/Scrubber.py:175: DeprecationWarning: > get_type() deprecated; use get_content_type() > ctype = part.get_type(part.get_default_type()) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341788: libg2c0-dev: includes 32-bit compatibility libraries in pure 64-bit amd64 installation
severity 341788 minor merge 341788 323285 tags 341788 + wontfix thanks Larry Doolittle writes: > Package: libg2c0-dev > Version: 1:3.4.5-1 > Severity: normal > > > Out of the 905 packages on my pure 64-bit amd64 debian sid machine, > only this one and fakeroot put any files in /emul/ia32-linux/ . > For general cleanliness and possible improved security, I don't > want any 32-bit compatibility libraries on this machine. Hence > the "pure" in my machine description. > > I'm not opposed to having 32-bit libraries built for 64-bit machines, > but they should be somehow separated and optional (even "suggested"), > since many people _do_ want to run 32-bit code on their 64-bit > processors. I happen to not be one one of them. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341816: [arm] as: Error: Rn must not overlap other operands
Package: binutils,gcj-4.0 Version: 2.16.1cvs20051117-1 Severity: serious the gcc-4.0 build from Nov 18 using binutils-2.16.1 did succeed, today's gcj-4.0 fails: /build/buildd/gcj-4.0-4.0.2/build/gcc/xgcc -B/build/buildd/gcj-4.0-4.0.2/build/gcc/ -B/usr/arm-linux-gnu/bin/ -B/usr/arm-linux-gnu/lib/ -isystem /usr/arm-linux-gnu/include -isystem /usr/arm-linux-gnu/sys-include -DHAVE_CONFIG_H -I/build/buildd/gcj-4.0-4.0.2/src/boehm-gc/include -fexceptions -Iinclude -I././targ-include -I.//libc/include -O2 -g -O2 -fexceptions -Iinclude -I././targ-include -I.//libc/include -c ../../../src/boehm-gc/finalize.c -fPIC -DPIC -o .libs/finalize.o /tmp/ccjPZNH0.s: Assembler messages: /tmp/ccjPZNH0.s:1703: Error: Rn must not overlap other operands -- `swp r3,r5,[r3]' /tmp/ccjPZNH0.s:2013: Error: Rn must not overlap other operands -- `swp r3,r4,[r3]' /tmp/ccjPZNH0.s:2186: Error: Rn must not overlap other operands -- `swp r3,r5,[r3]' make[5]: *** [finalize.lo] Error 1 make[5]: Leaving directory `/build/buildd/gcj-4.0-4.0.2/build/arm-linux-gnu/boehm-gc' make[4]: *** [all-recursive] Error 1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341877: gcc-3.4: ftbfs [sparc] error: conflicting types for 'malloc'
block 341877 with 340835 thanks Blars Blarson writes: > Package: gcc-3.4 > Version: 3.4.5-1 > Severity: serious > Justification: no longer builds from source > > gcc-3.4 failed to build on a sparc buildd, duplicated on my sparc pbuilder. so do you want to report that for _every_ package that builds 64bit binaries? really helpful ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341882: gcc-4.0: [mips] support for tri-arch on mips & mipsel
Stuart Anderson writes: > Package: gcc-4.0 > Version: 4.0.2-4.1 > Severity: wishlist > Tags: patch > > > Please enable tri-arch support for the MIPS platforms. The attached > patch (and a corresponding patch to glibc) provide support for n32 & n64 > ABIs in addition to the current o32 ABI. These patches have been tested > by building n32 & n64 version of the ltp packages. I'll leave that to Thiemo :-) some comments: > Index: debian/patches/biarch-include-mips.dpatch > +--- gcc/Makefile.in~ 2005-04-04 21:45:13.0 +0200 > gcc/Makefile.in 2005-07-08 21:04:29.808308064 +0200 > +@@ -2680,6 +2680,8 @@ > + -DLOCAL_INCLUDE_DIR=\"$(local_includedir)\" \ > + -DCROSS_INCLUDE_DIR=\"$(CROSS_SYSTEM_HEADER_DIR)\" \ > + -DTOOL_INCLUDE_DIR=\"$(gcc_tooldir)/include\" \ > ++ -DTARGET32_MACHINE=\"mips-linux-gnu\" \ > ++ -DTARGET64_MACHINE=\"mips64-linux-gnu\" \ > + @TARGET_SYSTEM_ROOT_DEFINE@ should be removed, and defined in debian/rules.defs > +--- gcc/cppdefault.c~2004-11-03 03:23:49.0 + > gcc/cppdefault.c 2005-07-09 10:19:46.762899104 + why can't the biarch-include patch not be used? > Index: debian/rules.defs > +ifneq (, $(filter $(DEB_TARGET_ARCH_CPU),mips mipsel)) > + # on mips, we are really tri-arch > + TARGET32_MACHINE := $(TARGET_ALIAS) > + TARGET64_MACHINE := $(TARGET_ALIAS) > +endif please define these for mips here. as we don't have all required libraries like zlib for biarch in lib, some of with_lib32* and with_lib64* macros have to be disabled (or maybe that's only the case for the gcc-4.1 packaging). > +# mips/mipsel build > +ifneq (, $(filter $(DEB_TARGET_ARCH_CPU),mipsel)) > + export GNUTARGET = elf64-tradlittlemips > +endif > +ifneq (, $(filter $(DEB_TARGET_ARCH_CPU),mips)) > + export GNUTARGET = elf64-tradbigmips > +endif where are these used? Thanks, Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341905: /etc/debian_chroot
Package: debootstrap Severity: wishlist please write a /etc/debian_chroot file containing a string for identifying the chroot. This information can (and is currently) be used i.e. in shell prompts. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341973: bogofilter-common requires pax
Package: bogofilter-common Version: 1.0.0-1 Severity: minor Clint, bogofilter requires a POSIX system, which implies it requires pax for some of the scripts, it is therefore, IMHO, not adequate to list pax as "suggests", but it should instead use "depends". If that is too strong for some reason I do not currently see, it should at least be "recommends". Please change the dependencies accordingly. Thanks, -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342055: hal: new sbp2 (ieee1394 discs) drivers (here: 2.6.14) break hal (at least 0.5.5)
Package: hal Version: 0.5.5.1-1 Severity: normal Tags: experimental patch Hey, when upgrading to the new hal package, I notized, that its firewire disc support is broken with newer sbp2 drivers. These don't assign SCSI Type "Disk" anymore, but "RBC" (what ever that might mean). A patch on [EMAIL PROTECTED] helped: http://lists.freedesktop.org/archives/hal/2005-November/003995.html I rebuild the package from source, with this patch applied - and yeah - my disc is recognized! I asume the patch will go into the next release (it would be wired if not!), but if you rebuild your package prior to this, it would be nice if you could include the patch. HTH Matthias -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14.2 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages hal depends on: ii adduser 3.80 Add and remove users and groups ii dbus 0.50-3 simple interprocess messaging syst ii libc6 2.3.5-8.1 GNU C Library: Shared libraries an ii libdbus-1-1 0.50-3 simple interprocess messaging syst ii libdbus-glib-1-1 0.50-3 simple interprocess messaging syst ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libglib2.0-0 2.8.4-2The GLib library of C routines ii libhal1 0.5.5.1-1 Hardware Abstraction Layer - share ii libusb-0.1-4 2:0.1.10a-22 userspace USB programming library ii lsb-base 3.0-12 Linux Standard Base 3.0 init scrip ii pciutils 1:2.1.11-15.1 Linux PCI Utilities ii udev 0.076-3/dev/ and hotplug management daemo ii usbutils 0.71+cvs20051029-3 USB console utilities hal recommends no packages. -- no debconf information signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#342267: gcc-4.0: boost 1.33.x FTBFS with "cannot handle R_PARISC_PCREL17F..."
did you check the suggestion from the error message? please notice that the error message comes from the linker (binutils). Domenico Andreoli writes: > Package: gcc-4.0 > Version: n/a > Severity: important > > hi, > > gcc-4.0 makes boost 1.33.x FTBFS on hppa. this bug is probably the > same of #342245 for gcc-3.4, only that gcc-4.0 _never_ built 1.33.x on > that architecture. > > /usr/bin/ld: > bin/boost/libs/serialization/build/libboost_serialization.so/gcc/debug/shared-linkable-true/threading-multi/xml_oarchive.o(.gnu.linkonce.t._ZN5boost7archive6detail18interface_oarchiveINS0_12xml_oarchiveEElsIKNS0_12version_typeEEERS3_RT_[boost::archive::xml_oarchive& > > boost::archive::detail::interface_oarchive::operator<< > (boost::archive::version_type > const&)]+0x44): cannot reach > 1f29__ZN5boost7archive18basic_xml_oarchiveINS0_12xml_oarchiveEE13save_overrideERKNS0_12version_typeEi+0, > recompile with -ffunction-sections > /usr/bin/ld: > bin/boost/libs/serialization/build/libboost_serialization.so/gcc/debug/shared-linkable-true/threading-multi/xml_oarchive.o(.gnu.linkonce.t._ZN5boost7archive6detail18interface_oarchiveINS0_12xml_oarchiveEElsIKNS0_12version_typeEEERS3_RT_[boost::archive::xml_oarchive& > > boost::archive::detail::interface_oarchive::operator<< > (boost::archive::version_type > const&)]+0x44): cannot handle R_PARISC_PCREL17F for > boost::archive::basic_xml_oarchive::save_override(boost::archive::version_type > const&, int) > /usr/bin/ld: final link failed: Bad value > collect2: ld returned 1 exit status > > the full log is available at > http://buildd.debian.org/fetch.php?&pkg=boost&ver=1.33.0-2&arch=hppa&stamp=1130099046&file=log&as=raw. > > i'm again available to delve further into this if only i get some hint > of the direction to follow. anyway i'd be probably able to only extract > more info, surely not to to fix the compiler itself. > > thanks > domenico > > -[ Domenico Andreoli, aka cavok > --[ http://people.debian.org/~cavok/gpgkey.asc >---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342343: core file tests in the testsuite are not run
Package: gdb Severity: wishlist WARNING: can't generate a core file - core tests suppressed - check ulimit -c maybe explicitely set the ulimit to some value? it defaults to 0 on the buildd's -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#337850: bug appears again in 4.0.2-5j1 (i386)
Max Kellermann writes:
> strace output:
>
> [pid 16630] open("/usr/share/java/libgcj-4.0.3.jar", O_RDONLY) = -1
> ENOENT (No such file or directory)
>
> gcj looks for 4.0.3, but there is only 4.0.2 (symlink missing?):
no, please update libgcj6-common to the recent version. needs to be
fixed however.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342488: Wrong Conflicts/Replaces makes upgrade fail
severity 342488 normal merge 342489 342488 tags 342488 + pending thanks pending, in the meantime, please remove the libsvncpp0c2 package by hand. Michael Biebl writes: > Package: libsvncpp0c2a > Version: 0.9.0-1 > Severity: grave > > The packages has a Conflicts/Replaces to libsvncpp0 and libsvncpp0c2a whereas > it > should be libsvncpp0 and *libsvncpp0c2*. This makes an upgrade impossible > as the old libsvncpp0c2 is not uninstalled automatically. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342484: Compilation is working
Falk Hueffner writes: > Mathieu Malaterre <[EMAIL PROTECTED]> writes: > > > Thanks Falk, you can close the bug. Updating binutils from unstable > > did the trick > > Well, it shouldn't really be closed, but gcc-snapshot should depend on > that version. fixed, pending next upload. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342557: gcj-4.0: Upgrading gcj makes javah disappear
clone 342557 -1 reassign -1 dpkg severity 342557 normal thanks I didn't check, but likely update-alternatives has problems with alternatives handled both as "master" and slave. And no, it's not critical. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342726: "Make is a HUGE memory hog"
Package: make http://gcc.gnu.org/ml/gcc/2005-12/msg00231.html talks about improving memory management in make. Recently the gcj-4.0 builds on mips and s390 didn't terminate, the 512 MB configured on these buildd's were not enough. Besides memory consumption, it should increase build time on low memory machines as well (on m68k about 35 minutes are spent reading the libjava/classpath Makefile from the gcc-snapshot package). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342726: acknowledged by developer (Re: Bug#342726: "Make is a HUGE memory hog")
reopen 342726 tags 342726 + patch thanks While an interesting observation, this is not a bug, any more > than "the Linux kernel is bloated" or "emacs is large" or "tex live > sucks raw eggs". > > Opinions, while valuable, do not belong in the BTS. reopening the bug, please consider it as a bug, added the patch tag now. If you insist, I'll attach the patch itself as well. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342850: gimp-python: Crashes when accessing the PDB
Package: gimp-python Version: 2.2.9-7ubuntu1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> import gimpfu >>> dir(gimpfu.pdb) (process:2912): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed LibGimpBase-ERROR **: could not find handler for message: 5 aborting... Aborted - -- System Information: Debian Release: testing/unstable APT prefers breezy APT policy: (860, 'breezy'), (750, 'dapper'), (730, 'testing'), (620, 'unstable'), (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'breezy-updates'), (500, 'breezy-security') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-rc2-1.27 Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages gimp-python depends on: ii libatk1.0-0 1.10.3-0ubuntu2The ATK accessibility toolkit ii libc6 2.3.5-1ubuntu12GNU C Library: Shared libraries an ii libcairo2 1.0.2-3ubuntu1 The Cairo 2D vector graphics libra ii libfontconfig12.3.2-1ubuntu4 generic font configuration library ii libgimp2.02.2.9-7ubuntu1 Libraries necessary to Run the GIM ii libglib2.0-0 2.9.0-0ubuntu3 The GLib library of C routines ii libgtk2.0-0 2.8.6-0ubuntu2 The GTK+ graphical user interface ii libpango1.0-0 1.11.0-0ubuntu1Layout and rendering of internatio ii libx11-6 1:6.2.1+cvs.20050722-8 X11 client-side library ii libxau6 1:0.1.2-2 X11 authorisation library ii libxcursor1 1.1.4-0ubuntu5 X cursor management library ii libxext6 1:6.4.3-3 X11 miscellaneous extension librar ii libxfixes31:3.0.0-3 X11 miscellaneous 'fixes' extensio ii libxi61:1.3.0-2 X11 Input extension library ii libxinerama1 1:1.1.0+cvs.20050821-1 X11 Xinerama extension library ii libxrandr21:1.0.2-2 X11 RandR extension library ii libxrender1 1:0.9.0-1 X Rendering Extension client libra ii python2.4.2-0ubuntu2 An interactive high-level object-o ii python-gtk2 2.8.1-0ubuntu2 Python bindings for the GTK+ widge gimp-python recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDm+zN8+hUANcKr/kRAi4OAKCm2HhVSUuhm5L9r6b9BXnPjb62xgCeJtjF nmndZB4o4sT/EzE2CQoCn0Y= =gXRR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342855: bash: Fails to install through debootstrap
clone 342855 -1 reassign 342855 debianutils thanks should add-shell handle that case? How else can the rbash entry be created? Christian Perrier writes: > Package: bash > Version: 3.1-1 > Severity: important > > I hesitated tagging this as RC because it currently breaks unstable installs > with D-Ibut I leave this up to you, Mathias. > > Installing bash with debootstrap fails: > > Dec 11 09:22:10 debootstrap: Setting up bash (3.1-1) ... > Dec 11 09:22:10 debootstrap: cat: > Dec 11 09:22:10 debootstrap: /etc/shells > Dec 11 09:22:10 debootstrap: : No such file or directory > Dec 11 09:22:10 debootstrap: > Dec 11 09:22:10 debootstrap: Either another instance of /usr/sbin/add-shell > is running, or it was previously interrupted. > Dec 11 09:22:10 debootstrap: Please examine /etc/shells.tmp to see if it > should be moved onto /etc/shells. > Dec 11 09:22:10 debootstrap: Setting up login (4.0.13-7) ... > Dec 11 09:22:10 debootstrap: dpkg: error processing bash (--configure): > Dec 11 09:22:10 debootstrap: subprocess post-installation script returned > error exit status 1 > Dec 11 09:22:11 debootstrap: > Dec 11 09:22:11 debootstrap: Setting up lsb-base (3.0-12) ... > Dec 11 09:22:11 debootstrap: Setting up passwd (4.0.13-7) ... > Dec 11 09:22:14 debootstrap: > Dec 11 09:22:14 debootstrap: Setting up initscripts (2.86.ds1-6) ... > Dec 11 09:22:16 debootstrap: > Dec 11 09:22:16 debootstrap: Setting up sysvinit (2.86.ds1-6) ... > Dec 11 09:22:16 debootstrap: sysvinit: creating /dev/initctl > Dec 11 09:22:19 debootstrap: init: > Dec 11 09:22:19 debootstrap: timeout opening/writing control channel > /dev/initctl > Dec 11 09:22:19 debootstrap: > Dec 11 09:22:19 debootstrap: Setting up debconf-i18n (1.4.62) ... > Dec 11 09:22:19 debootstrap: Setting up debconf (1.4.62) ... > Dec 11 09:22:20 debootstrap: > Dec 11 09:22:20 debootstrap: Errors were encountered while processing: > Dec 11 09:22:20 debootstrap: bash > > This can be reproduced with debootstrap itself. It breaks all installs of > unstable with Debian Installer, also. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#343028: please tighten build dependencies on g++-4.0 (and gcc-4.0)
Package: build-essential Version: 11.1 Please tighten the dependency on g++ to (>= 4:4.0.2-5). This is the current version in testing, configured with the change libstdc++ allocator. The dependency on gcc is not necessary, g++ depends on it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342969: acknowledged by developer (Not buildable with GCC >=4)
reopen 342969 severity 342969 important thanks > From [EMAIL PROTECTED] Sun Dec 11 16:10:06 2005 > Helix Player is absolutely not buildable with GCC >=4. Please do NOT close this report. So why is it "absolutely not buildable"? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342969: acknowledged by developer (Not buildable with GCC >=4)
Daniel Baumann writes: > Matthias Klose wrote: > > So why is it "absolutely not buildable"? > > See #309121, the asm part of hxclient depends on gcc 3.x. Nobody, > including upstream, wants or can fix it to comply with 4.x. Anyway, Real > instead works on a complete rewrite for helix player 2. Until this is > ready, helix-player 1.x ist lost with gcc 3.x. > > Why not close the bug? Removal of gcc 3.x is not a release-target for > etch, and for etch+1 there will be helix-player 2.x available hopefully ;) if we do have the choice to remove the g++-3.4 package or just the helix-player package, I'd rather prefer to remove the helix-player package. helix-player isn't a release target as well. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342959: Package explicitely build-depends on g++-3.4
Steve M. Robbins writes: > Howdy, > > On Mon, Dec 12, 2005 at 02:18:29AM +0100, Matthias Klose wrote: > > > We will get rid of g++-3.3 for the etch release and remove the > > g++-3.3 package. > > On Mon, Dec 12, 2005 at 12:54:22AM +0100, Matthias Klose wrote: > > > We would like to get rid of g++-3.4 for the etch release, although > > currently not a hard release goal. > > > I completely missed the discussion surrounding removal of gcc 3.3 and > gcc 3.4. AFAIK there was none, and I didn't propose this in the bug reports. Although the release team is eager to minimize the number of versions for one package. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#342850: Still a bug (Re: Bug#342850: gimp-python: Crashes when accessing the PDB)
notfound 342850 2.2.9-7ubuntu1
found 342850 2.2.9-7
thanks
> This bug system is not for Ubuntu packages.
Sorry about reporting with the wrong version number.
However, I did test unstable before posting that bug,
and it occurs there too.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
Many are called, few volunteer.
signature.asc
Description: Digital signature
Bug#343313: libstdc++6: upgrade breaks existing applications with scim 1.0.2-3
I think it's wrong to add conflicts to libstdc++6. we'll end up with an unmanagable long list of conflicts. can the conflict be added to some basic gtk package instead? Peter Moulder writes: > Package: libstdc++6 > Version: 4.0.2-5 > Severity: important > > > Upgrading libstdc++6 from 4.0.2-2 to 4.0.2-5 causes crashes in various > gtk programs when GTK_IM_MODULE=scim is in the environment. > > I have the following scim-related packages: > > ii scim 1.0.2-3Smart Common Input Method platform > ii scim-config-socket 1.0.2-3Socket configure module for SCIM > ii scim-frontend-socket 1.0.2-3Socket front end module for SCIM > ii scim-gtk2-immodule 1.0.2-3GTK2 IMModule with SCIM as backend > ii scim-server-socket 1.0.2-3Socket IM engine module for SCIM > > With libstdc++6 4.0.2-5 installed: > > $ GTK_IM_MODULE=scim gedit > *** glibc detected *** malloc(): memory corruption: 0x0822f3b8 *** > > $ GTK_IM_MODULE=scim inkscape > Launching a SCIM daemon with Socket FrontEnd... > *** glibc detected *** corrupted double-linked list: 0x089562e8 *** > > Emergency save activated! > ... > > galeon doesn't exactly crash, but goes into sleep state before showing > its main window. > > These programs appear to work fine when GTK_IM_MODULE is unset or if > I downgrade to libstdc++6 4.0.2-2 or if I upgrade scim to 1.4.2-1. > > Thus, without really understanding the problem, I suggest that > libstdc++6 Conflict with scim (<< 1.4.2-1). > > > scim bug report #342198 may be related. > > > -- System Information: > Debian Release: testing/unstable > APT prefers testing > APT policy: (500, 'testing'), (500, 'stable') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/dash > Kernel: Linux 2.4.27-2-686-smp > Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > > Versions of packages libstdc++6 depends on: > ii gcc-4.0-base 4.0.2-5The GNU Compiler Collection > (base > ii libc6 2.3.5-8GNU C Library: Shared libraries > an > ii libgcc1 1:4.0.2-5 GCC support library > > libstdc++6 recommends no packages. > > -- no debconf information > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#314535: xffm4: takes first dot in a filename as the start of the extension
On Mon, Dec 05, 2005 at 12:09:47PM +, Simon Huggins wrote: > On Sat, Jun 25, 2005 at 10:02:23AM +0100, Simon Huggins wrote: > > On Mon, Jun 20, 2005 at 08:03:36PM +0200, Matthias Czapla wrote: > > > On Mon, Jun 20, 2005 at 10:00:04AM +0100, Simon Huggins wrote: > > > > Do you run unstable, testing/etch or stable/sarge? > > > I'm running sarge. > > This is fixed in the 4.2.2 version. We intend to backport 4.2.2 to > > sarge at some point and we'll be back in touch when we've done so. > > There are backports for this at http://xfce.corsac.net > > You can just put: > deb http://xfce.corsac.net sarge main > in your /etc/apt/sources.list and update and dist-upgrade to get it. > > Let us know if this helps. Yes, it does! And 4.2 also rocks in every other way BTW. Thank you very very much Simon! Cheers Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#343027: acknowledged by developer (Bug#343027: fixed in wordtrans 1.1pre14-2)
Debian Bug Tracking System writes: >* Build-Depend on g++ (>= 4:4.0.2-2) | g++-3.4 for arm/hppa/m68k also > comment out the code that hardcodes g++-3.4 for those architectures > in debian/rules (Closes: #343027) why is it necessary to add "| g++-3.4" ? Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#343533: pyrex generates invalid code (gcc-4.0)
Package: pyrex Version: 0.9.3.1-1 Severity: serious creating build/temp.linux-i686-2.3/src/lxml gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -I/usr/include/libxml2 -I/usr/include/python2.3 -c src/lxml/etree.c -o build/temp.linux-i686-2.3/src/lxml/etree.o -w src/lxml/etree.c: In function '__pyx_f_5etree__elementFactory': src/lxml/etree.c:3878: error: invalid lvalue in assignment src/lxml/etree.c: In function '__pyx_f_5etree__commentFactory': src/lxml/etree.c:4255: error: invalid lvalue in assignment src/lxml/etree.c: In function '__pyx_f_5etree__attribFactory': src/lxml/etree.c:5253: error: invalid lvalue in assignment src/lxml/etree.c: In function '__pyx_f_5etree__attribIteratorFactory': src/lxml/etree.c:5390: error: invalid lvalue in assignment src/lxml/etree.c: In function '__pyx_f_5etree__elementIteratorFactory': src/lxml/etree.c:5584: error: invalid lvalue in assignment src/lxml/etree.c: In function '__pyx_f_5etree_22XPathDocumentEvaluator___init__': src/lxml/etree.c:6782: error: invalid lvalue in assignment src/lxml/etree.c: In function '__pyx_f_5etree_21XPathElementEvaluator___init__':src/lxml/etree.c:7560: error: invalid lvalue in assignment src/lxml/etree.c: In function '__pyx_f_5etree_changeDocumentBelowHelper': src/lxml/etree.c:11067: error: invalid lvalue in assignment error: command 'gcc' failed with exit status 1 make: *** [build-python2.3] Error 1 sources at http://people.debian.org/~doko/tmp/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#343471: bash: In the command line, problem when the line reaches the last column of the terminal
Vincent Lefevre writes: > Package: bash > Version: 3.1-1 > Severity: normal > > With the bash command line (interactive shell), when the command I'm > typing reaches the last column of the terminal, this sometimes goes > on at the first column of the same line instead of the next line. > This problem occurs in an xterm, even an xterm I've just opened. > > I have no such problem with zsh and with the cooked mode (e.g. with > "cat > /dev/null"). > Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1) please could you explain "sometimes"? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301964: [pkg-fetchmail-maint] Bug#301964: It appears fetchmail is still leaking file descriptors on sockets
John Darrah <[EMAIL PROTECTED]> writes: > Package: fetchmail > Version: 6.2.5.4-1 > Followup-For: Bug #301964 > > > I've noticed that fetchmail shuts down after long periods of running. > running lsof, you can see that sockets are not being closed properly. > After a while, there are hundreds of descriptors left in limbo. Is there a bullet-proof way to reproduce the socket leak? Could you try 6.3.1-pre1 from http://home.pages.de/~mandree/fetchmail/ to see if the problem is fixed in that version? -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#343836: Security: DoS attack possible - crashes on empty message
tags 343836 + security
thanks
Steve,
are you using multidrop mode? If so, please test if the attached patch
fixes the bug. It is an untested backport from 6.3.1-rc1.
If you are not using multidrop mode, please provide your configuration
details (passwords masked!) and a stack backtrace.
--
Matthias Andree
--- ./transact.c.orig 2005-11-12 13:44:39.0 +0100
+++ ./transact.c 2005-12-19 00:20:05.0 +0100
@@ -401,16 +401,14 @@
* condition the code for sending bouncemail will actually look
* at the freed storage and coredump...
*/
-if (msgblk.headers)
- free(msgblk.headers);
+xfree(msgblk.headers);
free_str_list(&msgblk.recipients);
-if (delivered_to)
- free(delivered_to);
+xfree(delivered_to);
/* initially, no message digest */
memset(ctl->digest, '\0', sizeof(ctl->digest));
-msgblk.headers = received_for = delivered_to = NULL;
+received_for = NULL;
from_offs = reply_to_offs = resent_from_offs = app_from_offs =
sender_offs = resent_sender_offs = env_offs = -1;
oldlen = 0;
@@ -434,8 +432,6 @@
if ((n = SockRead(sock, buf, sizeof(buf)-1)) == -1) {
set_timeout(0);
free(line);
- free(msgblk.headers);
- msgblk.headers = NULL;
return(PS_SOCKET);
}
set_timeout(0);
@@ -877,11 +873,7 @@
process_headers:
if (retain_mail)
-{
- free(msgblk.headers);
- msgblk.headers = NULL;
return(PS_RETAINED);
-}
if (refuse_mail)
return(PS_REFUSED);
/*
@@ -912,7 +904,7 @@
* to break it in a way that blackholed mail. Better to pass
* the occasional duplicate than to do that...
*/
-if (MULTIDROP(ctl))
+if (MULTIDROP(ctl) && msgblk.headers)
{
MD5_CTX context;
@@ -1024,8 +1016,7 @@
ctl->server.envelope && !strcasecmp(ctl->server.envelope, "Delivered-To"))
{
find_server_names(delivered_to, ctl, &msgblk.recipients);
- free(delivered_to);
- delivered_to = NULL;
+ xfree(delivered_to);
}
else if (received_for)
/*
@@ -1087,9 +1078,6 @@
if (outlevel >= O_DEBUG)
report(stdout,
GT_("forwarding and deletion suppressed due to DNS errors\n"));
- free(msgblk.headers);
- msgblk.headers = NULL;
- free_str_list(&msgblk.recipients);
return(PS_TRANSIENT);
}
else
@@ -1097,12 +1085,7 @@
/* set up stuffline() so we can deliver the message body through it */
if ((n = open_sink(ctl, &msgblk,
&good_addresses, &bad_addresses)) != PS_SUCCESS)
- {
- free(msgblk.headers);
- msgblk.headers = NULL;
- free_str_list(&msgblk.recipients);
return(n);
- }
}
n = 0;
@@ -1224,9 +1207,6 @@
{
report(stdout, GT_("writing RFC822 msgblk.headers\n"));
release_sink(ctl);
- free(msgblk.headers);
- msgblk.headers = NULL;
- free_str_list(&msgblk.recipients);
return(PS_IOERR);
}
else if ((run.poll_interval == 0 || nodetach) && outlevel >= O_VERBOSE && !isafile(2))
Bug#301964: [pkg-fetchmail-maint] Bug#301964: Further analysis on Bug#301964
John,
Thank you for your efforts.
Please try if the attached patch fixes the bug. It is taken from a
6.2.9-pre* release. AFAIR, the patch was sent by Goswin von Brederlow.
--
Matthias Andree
--- driver.c (Revision 4126)
+++ driver.c (Revision 4127)
@@ -1161,5 +1161,5 @@
report(stderr, GT_("SSL connection failed.\n"));
err = PS_AUTHFAIL;
- goto closeUp;
+ goto cleanUp;
}
Bug#294547: Debian Bugs #294547, #268346: need to restart fetchmail
Hi, is anyone of the original bug reporters using SSL to fetch mail? If so, please check if your errors are preceded by SSL connection failures. These are known to leak sockets, which may cause socket errors subsequently. Thanks, Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#343836: Security: DoS attack possible - crashes on empty message
Martin Schulze wrote:
> The patch does not apply though, since xfree() is unknown in version 6.2.5.
> I assume that the xfree only frees the memory when it is not NULL and sets
> the variable to NULL again, so the attached patch should do the same and apply
> to the version in Debian sarge/etch/sid.
Whoops, my apologies. Your assumptions are right, we are using this macro,
which is part of fetchmail 6.2.5.5's transact.c:
#define xfree(p) { if (p) { free(p); (p) = 0; } }
It is perhaps easier to advance to fetchmail 6.2.5.5. The number of changes
is low, and all changes either add documentation or fix important bugs.
While 6.2.5 on Debian may not need the Solaris or gettext build fix of the
day, I haven't yet heard of problems introduced that way. OTOH, I don't know
how many people have gone for 6.3.X right away.
The changelog vs. 6.2.5 is at <http://mandree.home.pages.de/fetchmail/NEWS.txt>
HTH,
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#344442: please add dependencies to the 64bit -dev package and build 32bit packages
Package: ncurses Severity: wishlist Tags: patch the ia32-libs package currently has a copy of 32bit ncurses libs, which can be replaced. the dependency stuff maybe can be simplified by just adding 'lib64c-dev' to the depends line. please find a patch at http://people.ubuntu.com/patches/ncurses32.diff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#338007: [pkg-fetchmail-maint] Bug#338007: fetchmail: certain messages cause "client/server synchronization error while fetching ..."
Does the problem also affect 6.2.9-rc7? See <http://developer.berlios.de/projects/fetchmail/> Please test 6.2.9-rc7 and post your findings. -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#336114: Forwarded upstream
Nathanael Nerode writes: > tags 336114 +upstream > forwarded 336114 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24712 > thanks > > Forwarded upstream as GCC bug number 24712. I think, that's not upstream. both changes were made between the 4.0.1 and the 4.0.2 release. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#338007: [pkg-fetchmail-maint] Bug#338007: fetchmail: certain messages cause "client/server synchronization error while fetching ..."
severity 338007 wishlist
retitle 338007 fetchmail: handle IMAP servers that send crap after header better
thanks
On Wed, 09 Nov 2005, Nathaniel W. Turner wrote:
> On Monday 07 November 2005 08:27 pm, Matthias Andree wrote:
> > Does the problem also affect 6.2.9-rc7?
>
> Yes, I see the same problem with 6.2.9-rc7. The results of running fetchmail
> 6.2.9-rc7 against the same test messages are attached to this message.
This is not a fetchmail bug. Using your first test message, I see this
with Courier-IMAP, prefixing each line by "| " in my output so it's more
easily legible. As you can see, Courier-IMAP sends the whole message
rather than just the header.
fetchmail does not need to handle such broken server behavior.
(fetchmail tries to swallow the crap, but stops doing so at the line
containing OK, taking it for the server reply.)
I'm demoting this to "wishlist" because fetchmail could indeed skip
forward to this sequence (ABNF): ")" CR LF tag OK rather than looking
for just OK.
| . fetch 1 rfc822.header
| * 1 FETCH (RFC822.HEADER {429}
| Message-Id: <[EMAIL PROTECTED]>
| Date: Thu, 03 Nov 2005 07:06:30 -0600
| To: <[EMAIL PROTECTED]>
| From: <[EMAIL PROTECTED]>
| Subject: testcase 1 (fails)
| Mime-Version: 1.0
| Content-Type: text/plain
|
| This is the message body. The preceding blank line ends with \r\n, as do
| all the other lines in this message.
| This line contains the word OK somewhere in it.
|
| This message will cause fetchmail to choke.
| )
| . OK FETCH completed.
Now compare this against Dovecot output:
| . fetch 1 rfc822.header
| * 1 FETCH (RFC822.HEADER {208}
| Message-Id: <[EMAIL PROTECTED]>
| Date: Thu, 03 Nov 2005 07:06:30 -0600
| To: <[EMAIL PROTECTED]>
| From: <[EMAIL PROTECTED]>
| Subject: testcase 1 (fails)
| Mime-Version: 1.0
| Content-Type: text/plain
|
| )
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#338007: (no subject)
fixed in upcoming fetchmail 6.2.9-rc8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317761: fetchmail: Stops on underscore in domain part of email
severity 317761 normal tags 317761 - moreinfo tags 317761 + fixed-upstream thanks OK, here's the story: On Claus's computer, fetchmail was unable to deliver a message and tried to create a bounce. In order to provide decent information, fetchmail 6.2.5 tried to resolve (qualify) its own hostname through gethostbyname(), which failed. This failure caused fetchmail to quit with exit code 11 (PS_DNS). However, this bounce would probably have been lost since the SMTP server that rejects underscores in sender addresses is likely to reject them in recipient addresses too. This is generally a problem if restrictions are getting tighter along the path from the first MX through the internal hops to the mailbox. Anyways, fetchmail 6.2.9-rc8 and newer will no longer quit if they cannot qualify their own hostname for purposes of the bounce, but instead use the unqualified hostname. -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#338513: gjdoc: FTBFS: gcc: internal compiler error
tags 338513 + upstream forwarded 338513 http://gcc.gnu.org/PR24572 retitle 338513 [PR 24572] [4.0 regression] ICE in gimplify_expr, at gimplify.c:3983 thanks forwarded two weeks ago without a Debian report. Roland Stigge writes: > Package: gcc-4.0 > Version: 4.0.2-3 > Severity: serious > > Hi, > > building the package gjdoc 0.7.6-1 in a clean sid build environment > (with pbuilder) on i386 and sparc results in: > > = > [...] > gnu/classpath/tools/gjdoc/expr/.libs/JavaLexer.o > gnu/classpath/tools/gjdoc/expr/.libs/JavaRecognizer.o > gnu/classpath/tools/gjdoc/expr/.libs/JavaTokenTypes.o > doctranslets/html/res/.libs/gjdochtml-clean.o > doctranslets/html/res/.libs/gjdochtml-fixed.o > doctranslets/html/res/.libs/gjdochtml-sclara.o > doctranslets/html/res/.libs/gjdochtml.o htmldoclet/.libs/gjdochtml-vanilla.o > htmldoclet/.libs/gjdochtml-clean-layout.o > htmldoclet/.libs/gjdochtml-clean-color1.o htmldoclet/.libs/xhtml11-target10.o > dtd/.libs/gjdoc-alphaindex.o dtd/.libs/gjdoc.o dtd/ent/.libs/iso-amsa.o > dtd/ent/.libs/iso-amsb.o dtd/ent/.libs/iso-amsc.o dtd/ent/.libs/iso-amsn.o > dtd/ent/.libs/iso-amso.o dtd/ent/.libs/iso-amsr.o dtd/ent/.libs/iso-box.o > dtd/ent/.libs/iso-cyr1.o dtd/ent/.libs/iso-cyr2.o dtd/ent/.libs/iso-dia.o > dtd/ent/.libs/iso-grk1.o dtd/ent/.libs/iso-grk2.o dtd/ent/.libs/iso-grk3.o > dtd/ent/.libs/iso-grk4.o dtd/ent/.libs/iso-lat1.o dtd/ent/.libs/iso-lat2.o > dtd/ent/.libs/iso-num.o dtd/ent/.libs/iso-pub.o dt d/ > ent/.libs/iso-tech.o doctranslets/html/res/.libs/default_help_en.o > doctranslets/html/res/.libs/gjdoc.o htmldoclet/.libs/gjdoc.o > htmldoclet/.libs/inherit.o dtd/.libs/dbcentx.o htmldoclet/.libs/HtmlDoclet.o > rng/.libs/gjdoc-classdoc.o rng/.libs/gjdoc-common.o rng/.libs/gjdoc-index.o > doctranslets/.libs/gjdoc_common.o doctranslets/html/.libs/about.o > doctranslets/html/.libs/allclasses.o doctranslets/html/.libs/allpackages.o > doctranslets/html/.libs/alphaindex.o > doctranslets/html/.libs/alphaindex_chunked.o > doctranslets/html/.libs/classdoc-source.o > doctranslets/html/.libs/classdoc-uses.o doctranslets/html/.libs/classdoc.o > doctranslets/html/.libs/deprecated.o doctranslets/html/.libs/descriptor.o > doctranslets/html/.libs/doctranslet.o doctranslets/html/.libs/fulltree.o > doctranslets/html/.libs/gjdoc.o doctranslets/html/.libs/help.o > doctranslets/html/.libs/html_common.o > doctranslets/html/.libs/index_noframes.o doctranslets/html/.libs/index.o > doctranslets/html/.libs/packageclasses.o doct ra > nslets/html/.libs/packagedoc.o htmldoclet/.libs/help.o > .libs/java.lang-classes-1.2.o .libs/java.lang-classes-1.3.o > .libs/java.lang-classes-1.4.o .libs/java.lang-classes-1.5.o .libs/version.o > -Wl,-soname -Wl,lib-gnu-classpath-tools-gjdoc.so.0 -o > .libs/lib-gnu-classpath-tools-gjdoc.so.0.0.0 > (cd .libs && rm -f lib-gnu-classpath-tools-gjdoc.so.0 && ln -s > lib-gnu-classpath-tools-gjdoc.so.0.0.0 lib-gnu-classpath-tools-gjdoc.so.0) > (cd .libs && rm -f lib-gnu-classpath-tools-gjdoc.so && ln -s > lib-gnu-classpath-tools-gjdoc.so.0.0.0 lib-gnu-classpath-tools-gjdoc.so) > creating lib-gnu-classpath-tools-gjdoc.la > (cd .libs && rm -f lib-gnu-classpath-tools-gjdoc.la && ln -s > ../lib-gnu-classpath-tools-gjdoc.la lib-gnu-classpath-tools-gjdoc.la) > /usr/bin/gcj-4.0 -shared --classpath=. -fassume-compiled -I./src -I. > -I/usr/share/java/antlr.jar -I. -g -O2 -c -o antlr.so > /usr/share/java/antlr.jar > antlr/StringUtils.java: In class 'antlr.StringUtils': > antlr/StringUtils.java: In method > 'antlr.StringUtils.stripBack(java.lang.String,java.lang.String)': > antlr/StringUtils.java:24: internal compiler error: in gimplify_expr, at > gimplify.c:3983 > Please submit a full bug report, > with preprocessed source if appropriate. > See http://gcc.gnu.org/bugs.html> for instructions. > For Debian GNU/Linux specific bug reporting instructions, > see . > make[3]: *** [antlr.so] Error 1 > make[3]: Leaving directory `/tmp/buildd/gjdoc-0.7.6' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/tmp/buildd/gjdoc-0.7.6' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/tmp/buildd/gjdoc-0.7.6' > make: *** [debian/stamp-makefile-build] Error 2 > = > > Thanks for considering. > > > -- > DARTS - Debian Archive Regression Test Suite > http://darts.alioth.debian.org/ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#336456: libgnutls11: certificate exchange fails with non-blocking socket
Hi,
Malcolm Scott:
> When using a non-blocking socket (created by the socket()
> call)_gnutls_read fails with EAGAIN which propagates up the call stack
> accompanied by the following assertions. Where upon in
> gnutls_recv_client_cert it gets converted to GNUTLS_E_NO_CERTIFICATE if
> CERT_REQUIRE is set. However the client hasn't had anywhere near enough
> time to send the certificate.
>
Can you please check whether gnutls12 fixes this problem?
Thank you.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
I'm no one's trophy!!!
-- Constance Barr
signature.asc
Description: Digital signature
Bug#338572: FHS: Python distutils should be configured to install under /usr/local by default
"Martin v. =?UTF-8?Q?L=C3=B6wis"?= writes: > Seo Sanghyeon wrote: > > Instead of referring confused users to the distutils manual all the time, > > Debian's Python should be configured to install under /usr/local when > > using distutils to do local install by default. > > This will break the build process of many Python-based packages, right? > They don't give an explicit prefix when running setup.py, so they > would install into /usr/local, which in turn would violate Debian > policy. but the general idea sounds fine (to destinguish between packages provided by the distro and local stuff). One way would be to first make this a required policy, and after all/most of the packages are converted, change the prefix. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
