Bug#1074250: ifupdown2 not working with python3.12
Package: ifupdown2 Version: 3.0.0-1.1 Severity: grave Tags: ipv6 Justification: renders package unusable Dear Maintainer, * What led up to the situation? The upgrade to python3.12 which replaced "readfp" with "read_file) * What exactly did you do (or not do) that was effective (or ineffective)? I replaced "readfp" to read_file in /usr/share/ifupdown2/ifupdown/main.py and it fixed the problem. * What was the outcome of this action? ifup and ifdown started working properly. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.9.3-060903-generic (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ifupdown2 depends on: ii iproute2 6.9.0-1 ii python3 3.12.2-1 ifupdown2 recommends no packages. Versions of packages ifupdown2 suggests: ii bridge-utils 1.7.1-2 ii ethtool 1:6.9-1 pn isc-dhcp-client pn python3-gvgen pn python3-mako -- no debconf information
Bug#622380: [ISC-Bugs #23006] Bug#622380: isc-dhcp-client: IPv6 address buffer size mismatch and comment error
It isn't causing any issues. I reported it as I thought it was slightly amusing (but harmless). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#619216: mutt: please build with openssl instead of gnutls
>> The gnutls implementation of ssl found in mutt, in mutt_ssl_gnutls.c, >> appears to not validate >> the common name of a remote server correctly. The openssl implementation >> found in mutt_ssl.c >> does perform this check correctly. >> Can the mutt package be re-build against openssl and not gnutls. >> >> This bug is reported upstream at http://dev.mutt.org/trac/ticket/3506. > > Is there a CVE for this? afaik no. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#619216: mutt: please build with openssl instead of gnutls
On 22 March 2011 21:23, Julien Cristau wrote: > On Tue, Mar 22, 2011 at 12:57:17 +1100, david b wrote: > >> Package: mutt >> Version: 1.5.20-9+squeeze1 >> Severity: grave >> Tags: security >> Justification: user security hole >> >> The gnutls implementation of ssl found in mutt, in mutt_ssl_gnutls.c, >> appears to not validate >> the common name of a remote server correctly. The openssl implementation >> found in mutt_ssl.c >> does perform this check correctly. >> Can the mutt package be re-build against openssl and not gnutls. >> > No, it can't. As far as I can tell mutt's license is GPL2+, which is > incompatible with openssl. erh? really hmm well there is the build option --with-ssl [0] :/ [0] - http://mutt.sourceforge.net/imap/README.SSL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#616633: Acknowledgement (file-roller: crashes on add a folder to a new .tar.7z archive)
gdb and valgrind output attached. (gdb) r Starting program: /usr/bin/file-roller [Thread debugging using libthread_db enabled] [New Thread 0x7fffeb134700 (LWP 27668)] [New Thread 0x7fffea933700 (LWP 27669)] application/x-7z-compressed => (null), (null), (null), (null) application/x-ar => (null), (null), (null), (null) application/x-java-archive => (null), (null), (null), (null) application/x-ms-dos-executable => (null), (null), (null), (null) application/x-7z-compressed-tar => (null), (null), (null), (null) application/x-bzip-compressed-tar => .tar.bz, .tbz, .tbz2, (null) application/x-compressed-tar => .tgz, (null), (null), (null) application/x-lzma-compressed-tar => .tzma, (null), (null), (null) application/x-xz-compressed-tar => .txz, (null), (null), (null) application/x-tar => (null), (null), (null), (null) application/x-cbz => (null), (null), (null), (null) application/zip => (null), (null), (null), (null) [New Thread 0x7fffea132700 (LWP 27670)] [Thread 0x7fffea933700 (LWP 27669) exited] [Thread 0x7fffeb134700 (LWP 27668) exited] [Thread 0x7fffea132700 (LWP 27670) exited] [New Thread 0x7fffea132700 (LWP 27675)] [New Thread 0x7fffeb134700 (LWP 27676)] [Thread 0x7fffea132700 (LWP 27675) exited] [New Thread 0x7fffea132700 (LWP 27681)] [Thread 0x7fffea132700 (LWP 27681) exited] [New Thread 0x7fffea132700 (LWP 27682)] [New Thread 0x7fffea933700 (LWP 27683)] [New Thread 0x7fffe9931700 (LWP 27684)] [Thread 0x7fffea132700 (LWP 27682) exited] [Thread 0x7fffe9931700 (LWP 27684) exited] [Thread 0x7fffea933700 (LWP 27683) exited] [New Thread 0x7fffea933700 (LWP 27685)] [New Thread 0x7fffe9931700 (LWP 27686)] [Thread 0x7fffe9931700 (LWP 27686) exited] [Thread 0x7fffea933700 (LWP 27685) exited] [New Thread 0x7fffea933700 (LWP 27687)] [New Thread 0x7fffe9931700 (LWP 27688)] [Thread 0x7fffea933700 (LWP 27687) exited] [Thread 0x7fffe9931700 (LWP 27688) exited] [New Thread 0x7fffe9931700 (LWP 27689)] [New Thread 0x7fffea933700 (LWP 27690)] [New Thread 0x7fffea132700 (LWP 27691)] [Thread 0x7fffe9931700 (LWP 27689) exited] [Thread 0x7fffea933700 (LWP 27690) exited] [Thread 0x7fffea132700 (LWP 27691) exited] [New Thread 0x7fffea132700 (LWP 27693)] [Thread 0x7fffea132700 (LWP 27693) exited] [New Thread 0x7fffea132700 (LWP 27695)] [Thread 0x7fffeb134700 (LWP 27676) exited] [New Thread 0x7fffeb134700 (LWP 27700)] [Thread 0x7fffea132700 (LWP 27695) exited] [New Thread 0x7fffea132700 (LWP 27711)] [New Thread 0x7fffea933700 (LWP 27712)] [New Thread 0x7fffe9931700 (LWP 27713)] [Thread 0x7fffeb134700 (LWP 27700) exited] [Thread 0x7fffea132700 (LWP 27711) exited] [Thread 0x7fffe9931700 (LWP 27713) exited] [New Thread 0x7fffe9931700 (LWP 27714)] [New Thread 0x7fffea132700 (LWP 27715)] [Thread 0x7fffe9931700 (LWP 27714) exited] [Thread 0x7fffea933700 (LWP 27712) exited] [New Thread 0x7fffea933700 (LWP 27716)] [New Thread 0x7fffe9931700 (LWP 27717)] [New Thread 0x7fffeb134700 (LWP 27718)] [Thread 0x7fffea132700 (LWP 27715) exited] [Thread 0x7fffeb134700 (LWP 27718) exited] [Thread 0x7fffea933700 (LWP 27716) exited] Program received signal SIGSEGV, Segmentation fault. __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:31 31 ../sysdeps/x86_64/multiarch/../strlen.S: No such file or directory. in ../sysdeps/x86_64/multiarch/../strlen.S (gdb) bt #0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:31 #1 0x766f41bd in IA__g_string_insert_len (string=0x9a7f40, pos=-1, val=0x18 , len=24) at /usr/src/debian_compile/libglib2/glib2.0-2.24.2/glib/gstring.c:692 #2 0x00434365 in ?? () #3 0x0042eb7f in ?? () #4 0x0042315b in ?? () #5 0x00423467 in ?? () #6 0x0042469d in ?? () #7 0x004486d8 in ?? () #8 0x004476b5 in ?? () #9 0x766d09b2 in g_main_dispatch (context=0x6a1b30) at /usr/src/debian_compile/libglib2/glib2.0-2.24.2/glib/gmain.c:1960 #10 IA__g_main_context_dispatch (context=0x6a1b30) at /usr/src/debian_compile/libglib2/glib2.0-2.24.2/glib/gmain.c:2513 #11 0x766d4838 in g_main_context_iterate (context=0x6a1b30, block=, dispatch=, self=) at /usr/src/debian_compile/libglib2/glib2.0-2.24.2/glib/gmain.c:2591 #12 0x766d4d45 in IA__g_main_loop_run (loop=0x6ac4c0) at /usr/src/debian_compile/libglib2/glib2.0-2.24.2/glib/gmain.c:2799 #13 0x778f96b7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #14 0x0044bcde in ?? () ---Type to continue, or q to quit--- #15 0x75eb1c4d in __libc_start_main (main=, argc=, ubp_av=, init=, fini=, rtld_fini=, stack_end=0x7fffe408) at libc-start.c:228 #16 0x004128c9 in ?? () #17 0x7fffe408 in ?? () #18 0x001c in ?? () #19 0x0001 in ?? () #20 0x7fffe6a3 in ?? () #21 0x in ?? () (gdb) i r rax0x7fffdf08 140737488346888 rbx0x9a7f40 10125120 rcx0x18 24 rdx0x18 24 rsi0xff
Bug#600979: xserver-xorg-video-radeon: with a secondary user login via a new gdm session video playing colour is too dark
Well .. it only happens when I use totem... on a secondary gdm session ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#600979: xserver-xorg-video-radeon: with a secondary user login via a new gdm session video playing colour is too dark
Actually it turns out to be a totem bug. When I play a video on that second session - it screws up the video (makes it dark). If I use vlc it doesn't occur. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#611800: Fwd: isc-dhcp-server is really slow and windows 7 cannot get a lease
-- Forwarded message --
From: nibbler
Date: 12 February 2011 23:27
Subject: Fwd: isc-dhcp-server is really slow and windows 7 cannot get a lease
To: db.pub.m...@gmail.com
-- Forwarded message --
From: nibbler
Date: Sat, Feb 12, 2011 at 10:56 PM
Subject: RE: isc-dhcp-server is really slow and windows 7 cannot get a lease
To: 611...@bugs.debian.org, 611800-subscr...@bugs.debian.org
This bug was reported on my behalf. For some reason, the bug tracker
didn't get my last email.
I've attached my config files for you to review.
Recently Windows 7 has intermittently been able to get a lease, which
is very strange.
System:
Intel Atom D510 (1.6GHz) with 4GB RAM
Debian squeeze (x64)
DHCP 4.2.0-P2 (manually updated)
## dhcpd.conf
server-identifier asylum;
ddns-updates on;
ddns-update-style interim;
update-static-leases on;
ddns-domainname "internal.";
ddns-rev-domainname "in-addr.arpa.";
ignore client-updates;
include "/etc/bind/rndc.key";
zone internal {
primary 127.0.0.1;
key rndc-key;
}
zone 1.168.192.in-addr.arpa {
primary 127.0.0.1;
key rndc-key;
}
option domain-name "internal";
option domain-name-servers 127.0.0.1;
default-lease-time 129600;
max-lease-time 1296;
authoritative;
log-facility local7;
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.10 192.168.1.99;
option domain-name-servers 192.168.1.100;
option domain-name "internal";
option routers 192.168.1.254;
option broadcast-address 192.168.1.255;
}
## named.conf.options
options {
directory "/var/cache/bind";
auth-nxdomain no;# conform to RFC1035
listen-on-v6 { any; };
};
controls {
inet 127.0.0.1 allow {localhost; };
};
## named.conf.local
zone "internal" {
type master;
file "/var/lib/bind/internal.hosts";
update-policy {
grant rndc-key wildcard * ANY;
};
notify yes;
};
zone "1.168.192.in-addr.arpa" {
type master;
file "/var/lib/bind/192.168.1.hosts";
update-policy {
grant rndc-key wildcard * ANY;
};
notify yes;
};
include "/etc/bind/rndc.key";
Bug#612036: Acknowledgement (virt-manager: cannot use a local sdl window as a graphics option)
I just tried changing the perms of the pts device(to be chowned by
libvirt-qemu:tty) and that doesn't fix the problem :/
I seem to get this error - with / without changing the pts device permissions.
2011-02-05 12:34:13,620 (proxies:400): Introspect error on
:1.1:/org/freedesktop/Hal/devices/net_XX_XX_XX_XX_XX_XX:
dbus.exceptions.DBusException: org.freedesktop.Hal.NoSuchDevice: No
device with id /org/freedesktop/Hal/devices/net_XX_XX_XX_XX_XX_XX
2011-02-05 12:34:13,621 (proxies:403): Executing introspect queue due to error
2011-02-05 12:34:13,622 (connection:218): Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in
maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/halhelper.py", line 156,
in _device_added
if self.is_cdrom_media(path):
File "/usr/share/virt-manager/virtManager/halhelper.py", line 106,
in is_cdrom_media
return bool(obj.QueryCapability("volume") and
File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 630, in
call_blocking
message, timeout)
DBusException: org.freedesktop.Hal.NoSuchDevice: No device with id
/org/freedesktop/Hal/devices/net_XX_XX_XX_XX_XX_XX
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#308832: any news regarding the state of this patch?
any news regarding the state of this patch? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#610753: debootstrap: use apt trusted keys with --keyring by default
> The problem with this idea is that debootstrap can be used: > > - to bootstrap on another distribution, which won't have that keyring > - to bootstrap one Debian or derivative on another, so that keyring > will be present but not have the right keys in it > - to bootstrap unstable on stable, so the keyring may have only old > keys in it, not the current key used to sign unstable > (I haven't checked if/when that occurs.) > - to bootstrap during installation, from a CD, in which case there > is no available keyring at that point, and the media is trusted > > Especially the first 3 cases seem hard to reconcile with checking > signatures by default. > Well yes this would be a change from the current behaviour. If you don't have the key in the keyring then debootstrap will not be able to check the release files and will not continue. If the key is in the keyring then debootstrap will continue. Perhaps to complement --keyring, --key could also exist. (making it slightly easier to work with). with 1. - the user will now have to put the required key into the keyring (by default) 2. while this may be possible, it probably is wise if the user fetches the key (like in 2) 3. Hum, isn't there cd key ?(you could check the iso is ok) / how does the D-I handle it ? With 3. perhaps a --no-keyring option could be used? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#576739: any news re this bug?
any news re this bug?... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*
That specific grep has no results --> (for the 2nd). However, for the 3rd the results are listed below: /var/log/dpkg.log.1:2010-12-03 23:55:11 status triggers-pending python-central 0.6.16+nmu1 /var/log/dpkg.log.1:2010-12-03 23:55:11 trigproc python-central 0.6.16+nmu1 0.6.16+nmu1 /var/log/dpkg.log.1:2010-12-03 23:55:11 status half-configured python-central 0.6.16+nmu1 /var/log/dpkg.log.1:2010-12-03 23:55:32 status installed python-central 0.6.16+nmu1 /var/log/dpkg.log.1:2010-12-03 23:55:33 status triggers-pending python-central 0.6.16+nmu1 /var/log/dpkg.log.1:2010-12-03 23:55:36 trigproc python-central 0.6.16+nmu1 0.6.16+nmu1 /var/log/dpkg.log.1:2010-12-03 23:55:36 status half-configured python-central 0.6.16+nmu1 /var/log/dpkg.log.1:2010-12-03 23:55:36 status installed python-central 0.6.16+nmu1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*
well it was 1. reportlab and 2. bzr (gtk). I am not sure on the exact packages - isn't there an easier way to simply check for every python package (available). ii python-central 0.6.16+nmu1 register and build utility for Python packages -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#607988: ok sure
Ok sure - the bug isn't so critical really and really what happens is that when upgrading there are those damn broken symlinks which should be cleaned up / ignored. It would appear that in my case several of the python packages I had installed but not --purged (in removal) resulted in their symlinks being left behind. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*
Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 22 not upgraded. 8 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up python (2.6.6-3+squeeze4) ... Linking and byte-compiling packages for runtime python2.6... Traceback (most recent call last): File "/usr/bin/pycompile", line 314, in main() File "/usr/bin/pycompile", line 300, in main options.force, options.optimize, e_patterns) File "/usr/bin/pycompile", line 196, in compile ftime = os.stat(fn).st_mtime OSError: [Errno 2] No such file or directory: '/usr/lib/python2.6/dist-packages/bzrlib/plugins/gtk/merge.py' dpkg: error processing python (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of python-all: python-all depends on python (= 2.6.6-3+squeeze4); however: Package python is not configured yet. dpkg: error processing python-all (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of python-dev: python-dev depends on python (= 2.6.6-3+squeeze4); however: Package python is not configured yet. dpkg: error processing python-dev (--configure): dependency problems - leaving unconfigured configured to not write apport reports configured to not write apport reports configured to not write apport reports configured to not write apport reports configured to not write apport reports dpkg: dependency problems prevent configuration of python-all-dev: python-all-dev depends on python (= 2.6.6-3+squeeze4); however: Package python is not configured yet. python-all-dev depends on python-all (= 2.6.6-3+squeeze4); however: Package python-all is not configured yet. python-all-dev depends on python-dev (= 2.6.6-3+squeeze4); however: Package python-dev is not configured yet. dpkg: error processing python-all-dev (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of python-examples: python-examples depends on python (= 2.6.6-3+squeeze4); however: Package python is not configured yet. dpkg: error processing python-examples (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of python-peak.util: python-peak.util depends on python; however: Package python is not configured yet. dpkg: error processing python-peak.util (--configure): dependency problems - leavinconfigured to not write apport reports configured to not write apport reports configured to not write apport reports g unconfigured dpkg: dependency problems prevent configuration of python-dbg: python-dbg depends on python (= 2.6.6-3+squeeze4); however: Package python is not configured yet. dpkg: error processing python-dbg (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of python-all-dbg: python-all-dbg depends on python (= 2.6.6-3+squeeze4); however: Package python is not configured yet. python-all-dbg depends on python-all (= 2.6.6-3+squeeze4); however: Package python-all is not configured yet. python-all-dbg depends on python-dbg (= 2.6.6-3+squeeze4); however: Package python-dbg is not configured yet. dpkg: error processing python-all-dbg (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: python python-all python-dev python-all-dev python-examples python-peak.util python-dbg python-all-dbg E: Sub-process /usr/bin/dpkg returned an error code (1) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606477: iodine: cannot compile from source
Yeah it turns out, I had this: set CFLAGS -g -O2 -Wall -fstack-protector -D_FORTIFY_SOURCE=2 -fPIE -pie set CPPFLAGS -g -O2 -Wall -fstack-protector -D_FORTIFY_SOURCE=2 -fPIE -pie in /etc/dpkg/buildflags.conf --> my fault! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606477: iodine: cannot compile from source
Right so modifying the debian rules file as per http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589054 I was able to build iodine with some gcc hardening protections. Simply adding some CFLAGS and disabling hardening-wrapper meant that I could build iodine (as well). Here is the result (of disabling hardening-wrapper, modifying the rules file and doing --> export CFLAGS="-g -O2 -Wall -fstack-protector -D_FORTIFY_SOURCE=2" ) hardening-check /usr/sbin/iodine /usr/sbin/iodine: Position Independent Executable: no, normal executable! Stack protected: yes Fortify Source functions: yes Read-only relocations: no, not found! Immediate binding: no, not found! hardening-check /usr/sbin/iodined /usr/sbin/iodined: Position Independent Executable: no, normal executable! Stack protected: yes Fortify Source functions: yes Read-only relocations: no, not found! Immediate binding: no, not found! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606477: iodine: cannot compile from source
Interesting. Hum I will have a play with this later. However, you can see that it should really be compiled with -fPIC and the test seems not to be right? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606477: iodine: cannot compile from source
On 10 December 2010 04:13, gregor herrmann wrote: > tag 606477 + moreinfo > thanks > > On Fri, 10 Dec 2010 03:54:42 +1100, dave b wrote: > >> Sorry, what is your question? > > Your output shows: >>> LD test >>> /usr/bin/ld.real: >>> /usr/lib/gcc/x86_64-linux-gnu/4.3.2/../../../../lib/libcheck.a(check.o): >>> relocation R_X86_64_32 > > and I dont't know where "/usr/bin/ld.real" comes from. > I don't have it on my machine and I don't find it with "apt-file > search"; maybe a diversion ... > > Could you lease run: > - ls -la /usr/bin/ld* > - dpkg -S /usr/bin/ld.real > - grep \\.real /var/lib/dpkg/info/* ls -la /usr/bin/ld* ls -lah /usr/bin/ld* lrwxrwxrwx 1 root root 11 2009-08-01 02:03 /usr/bin/ld -> hardened-ld -rwxr-xr-x 1 root root 5.8K 2010-10-22 07:41 /usr/bin/ldd -rwxr-xr-x 1 root root 449K 2008-06-24 08:07 /usr/bin/ld.real dpkg -S /usr/bin/ld.real diversion by hardening-wrapper from: /usr/bin/ld diversion by hardening-wrapper to: /usr/bin/ld.real I don't think you need the last one ^ ^ (clearly it is from hardening-wrapper) I have the following exported export DEB_BUILD_HARDENING=1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606477: iodine: cannot compile from source
Sorry, what is your question? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#598463: Alive
Never-mind, there has already been a potential patch emailed in that thread (that Soren linked to). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#598463: Alive
Um, well I could see if they would accept a patch I could make up soon... The problem is / was they closed the bug saying it was a python issue, where they didnt' even attempt to ensure that a https connection would be secured, through wrapping it in ssl, iirc. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603450: Fwd: Due offlineimap absence of certificate validation issue -- Debian BTS#603450
On 8 December 2010 18:39, Alexander Reichle-Schmehl wrote: > Hi dave! > > * dave b [101202 05:58]: > >> Here have a patch! >> This obviously will break connecting to hosts which use a self-signed >> certificate. >> Perhaps some one else can fix this when they want it fixed ;) ? >> I tested using the following config: > > I verified it, and your patch works: I accepts valid ssl connections, > and rejects invalid ones. > >> + self.sslobj = ssl_wrap(self.sock, self.keyfile, self.certfile, >> cert_reqs=ssl.CERT_REQUIRED, ca_certs="/etc/ssl/certs/ca-certificates.crt") > > But that looks kind of ugly, having a hardcoded path... Also, I wonder > if not self.certfile should be used for verification? Sorry? Um. Well sure a hard coded path path not be the best thing ... if you know how to determine the path to the ca store on a system modify the patch to use that I guess. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605685: [Pkg-libvirt-maintainers] Bug#605685: virt-manager: cannot save password (for a vnc connection)
On 6 December 2010 20:28, Guido Günther wrote:
> Hi Dave,
> On Fri, Dec 03, 2010 at 11:50:00PM +1100, dave b wrote:
>> On 3 December 2010 22:51, Guido Günther wrote:
>> > On Fri, Dec 03, 2010 at 10:07:49PM +1100, dave b wrote:
>> >> On 3 December 2010 19:20, Guido Günther wrote:
>> >> > On Fri, Dec 03, 2010 at 09:48:56AM +1100, dave b wrote:
>> >> >> I do have it installed...
>> >> > And python-gnomekeyring as well?
>> >>
>> >> Yes of course.
>> > Please check the current version in squeeze.
> Does the attached patch resolve the issue for you?
Yes, except I patched it manually and when I did this - it
segfaulted[0] on the first run (when I used it).
(It now saves my password and can fetch it).
(please forgive the indentation level mixing ;) ).
+++ keyring.py 2010-12-06 23:31:16.0 +1100
@@ -35,11 +35,17 @@
def __init__(self):
if haveKeyring:
try:
-if not("default" in gnomekeyring.list_keyring_names_sync()):
-gnomekeyring.create_sync("default", None)
+#if not("default" in gnomekeyring.list_keyring_names_sync()):
+#gnomekeyring.create_sync("default", None)
self.keyring = gnomekeyring.get_default_keyring_sync()
if self.keyring == None:
logging.warning("Failed to create default keyring")
+ self.keyring = 'default'
+ try:
+ gnomekeyring.create_sync(self.keyring, None)
+ except gnomekeyring.AlreadyExistsError, e:
+ print e
+
except:
logging.warning(("Keyring unavailable: '%s'") %
(str((sys.exc_info())[0]) + " " + str((sys.exc_info())[1])))
self.keyring = None
[0] - [78805.592363] python[14615]: segfault at 0 ip 7f425bf89b09
sp 7fff5b973000 error 4 in
libgvnc-1.0.so.0.0.1[7f425bf82000+22000]
2010-12-06 23:31:28,314 (config:627): Initializing keyring
2010-12-06 23:31:28,317 (keyring:42): Failed to create default keyring
Segmentation fault
Also my default keyring isn't called 'default', don't know if that
matters or not.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605965: [Pkg-libvirt-maintainers] Bug#605965: python-libvirt: segfaults after making lots of readonly connections
On 6 December 2010 01:53, Guido Günther wrote: > tag 605965 +unreproducible > > On Sun, Dec 05, 2010 at 04:26:06PM +1100, david b wrote: >> Package: python-libvirt >> Version: 0.8.3-4 >> Severity: normal >> >> Here is an example python script you can use to reproduce the problem: >> >> import libvirt >> import sys >> >> >> def main(): >> conn = libvirt.openReadOnly(None) >> >> if __name__ == "__main__": >> for i in range(0, 1): >> main() >> >> If you run it after a number of connections python will segfault. > Not here with 0.8.3-5. The report is lacking information as to what > hypervisor you conenct to, etc. > -- Guido It needs virtualbox to be installed. If you look at the backtrace, you can see it is in some virtualbox method. Apparently when you have virtualbox installed, the connection is to virtualbox(when you pass in None). If you dont' have virtualbox installed then the above crash will not take place. -- He hath eaten me out of house and home. -- William Shakespeare, "Henry IV" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605967: wait what?
wait what? how is this a "wishlist" item? The copy of IPy.py it is using is old and appears broken (see the test failures). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603594: So apparently it does do certificate checking
Ok if you feel this way, close the bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603594: So apparently it does do certificate checking
Just to clarify, yeah it would seem it does check the certificate. However, what the user sees is not consistent with how other browsers show (re) ssl errors. It is also non-obvious. -- Tempt not a desperate man. -- William Shakespeare, "Romeo and Juliet" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603594: So apparently it does do certificate checking
Just to clarify, yeah it would seem it does check the certificate. However, what the user sees is not consistent with other browsers display ssl errors. it is also non-obvious. -- Tempt not a desperate man. -- William Shakespeare, "Romeo and Juliet" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605685: [Pkg-libvirt-maintainers] Bug#605685: virt-manager: cannot save password (for a vnc connection)
so this won't be fixed for squeeze :( ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605685: [Pkg-libvirt-maintainers] Bug#605685: virt-manager: cannot save password (for a vnc connection)
On 3 December 2010 22:51, Guido Günther wrote: > On Fri, Dec 03, 2010 at 10:07:49PM +1100, dave b wrote: >> On 3 December 2010 19:20, Guido Günther wrote: >> > On Fri, Dec 03, 2010 at 09:48:56AM +1100, dave b wrote: >> >> I do have it installed... >> > And python-gnomekeyring as well? >> >> Yes of course. > Please check the current version in squeeze. Sorry what? I have the following installed: ii libvirt-bin 0.8.3-4 the programs for the libvirt library ii libvirt-doc 0.8.3-4 documentation for the libvirt library ii libvirt0 0.8.3-4 library for interfacing with different virtualization systems ii python-libvirt 0.8.3-4 libvirt Python bindings ... ii gnome-keyring2.30.3-4 GNOME keyring services (daemon and tools) ii gnome-keyring-manager2.20.0-1 keyring management program for the GNOME desktop ... ii python-gnomekeyring 2.30.0-3 Python bindings for the GNOME keyring library .. ii virt-manager 0.8.4-8 desktop application for managing virtual machines -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605685: [Pkg-libvirt-maintainers] Bug#605685: virt-manager: cannot save password (for a vnc connection)
On 3 December 2010 19:20, Guido Günther wrote: > On Fri, Dec 03, 2010 at 09:48:56AM +1100, dave b wrote: >> I do have it installed... > And python-gnomekeyring as well? Yes of course. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605685: [Pkg-libvirt-maintainers] Bug#605685: virt-manager: cannot save password (for a vnc connection)
I do have it installed... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603450: Fwd: Due offlineimap absence of certificate validation issue -- Debian BTS#603450
-- Forwarded message --
From: dave b
Date: 1 December 2010 13:59
Subject: Re: Due offlineimap absence of certificate validation issue
-- Debian BTS#603450
To: John Goerzen
Cc: Jan Lieskovsky , Christoph Höger
Here have a patch!
This obviously will break connecting to hosts which use a self-signed
certificate.
Perhaps some one else can fix this when they want it fixed ;) ?
I tested using the following config:
# Sample minimal config file. Copy this to ~/.offlineimaprc and edit to
# suit to get started fast.
[general]
accounts = Test
[Account Test]
localrepository = Local
remoterepository = Remote
[Repository Local]
type = Maildir
localfolders = ~/Test
[Repository Remote]
type = IMAP
ssl = yes
remotehost = imap.gmail.com # this should work
#remotehost = 74.125.39.109 # this should fail
#remotehost = $putselfsignedserveraddresshere #this should fail
remoteuser = jgoerzen
For these hosts (listed here) the expected outcome matched the actual
outcome when I tried offlineimap.
diff --git a/offlineimap/imaplibutil.py b/offlineimap/imaplibutil.py
index a60242b..3df92c2 100644
--- a/offlineimap/imaplibutil.py
+++ b/offlineimap/imaplibutil.py
@@ -27,6 +27,7 @@ try:
import ssl
ssl_wrap = ssl.wrap_socket
except ImportError:
+print e
ssl_wrap = socket.ssl
class IMAP4_Tunnel(IMAP4):
@@ -62,7 +63,7 @@ class IMAP4_Tunnel(IMAP4):
self.infd.close()
self.outfd.close()
self.process.wait()
-
+
class sslwrapper:
def __init__(self, sslsock):
self.sslsock = sslsock
@@ -144,6 +145,27 @@ def new_open(self, host = '', port = IMAP4_PORT):
raise socket.error(last_error)
self.file = self.sock.makefile('rb')
+
+def _verifycert(cert, hostname):
+'''Verify that cert (in socket.getpeercert() format) matches hostname.
+CRLs and subjectAltName are not handled.
+
+Returns error message if any problems are found and None on success.
+'''
+if not cert:
+return ('no certificate received')
+dnsname = hostname.lower()
+for s in cert.get('subject', []):
+key, value = s[0]
+if key == 'commonName':
+certname = value.lower()
+if (certname == dnsname or
+'.' in dnsname and certname == '*.' + dnsname.split('.', 1)[1]):
+return None
+return ('certificate is for %s') % certname
+return ('no commonName found in certificate')
+
+
def new_open_ssl(self, host = '', port = IMAP4_SSL_PORT):
"""Setup connection to remote server on "host:port".
(default: localhost:standard IMAP4 SSL port).
@@ -171,7 +193,10 @@ def new_open_ssl(self, host = '', port = IMAP4_SSL_PORT):
if last_error != 0:
# FIXME
raise socket.error(last_error)
-self.sslobj = ssl_wrap(self.sock, self.keyfile, self.certfile)
+self.sslobj = ssl_wrap(self.sock, self.keyfile, self.certfile, cert_reqs=ssl.CERT_REQUIRED, ca_certs="/etc/ssl/certs/ca-certificates.crt")
+msg = _verifycert(self.sslobj.getpeercert(), host)
+if msg:
+raise socket.error(('%s certificate error: %s') % (host, msg) )
self.sslobj = sslwrapper(self.sslobj)
mustquote = re.compile(r"[^\w!#$%&'+,.:;<=>?^`|~-]")
diff --git a/offlineimap/imapserver.py b/offlineimap/imapserver.py
index 74f1a27..a4925b1 100644
--- a/offlineimap/imapserver.py
+++ b/offlineimap/imapserver.py
@@ -85,7 +85,7 @@ class UsefulIMAP4_SSL(UsefulIMAPMixIn, imaplibutil.WrappedIMAP4_SSL):
imaplibutil.new_open_ssl(self, host, port)
# This is the same hack as above, to be used in the case of an SSL
-# connexion.
+# connection.
def read(self, size):
if (system() == 'Darwin') and (size>0) :
@@ -191,7 +191,7 @@ class IMAPServer:
try:
if self.gss_step == self.GSS_STATE_STEP:
if not self.gss_vc:
-rc, self.gss_vc = kerberos.authGSSClientInit('imap@' +
+rc, self.gss_vc = kerberos.authGSSClientInit('imap@' +
self.hostname)
response = kerberos.authGSSClientResponse(self.gss_vc)
rc = kerberos.authGSSClientStep(self.gss_vc, data)
@@ -243,7 +243,7 @@ class IMAPServer:
self.lastowner[imapobj] = thread.get_ident()
self.connectionlock.release()
return imapobj
-
+
self.connectionlock.release() # Release until need to modify data
""" Must be careful here that if we fail we should bail out gracefully
@@ -328,7 +328,7 @@ class IMAPServer:
if(self.connectionlock.locked
Bug#603450: offlineimap: fails check the remote servers ssl certificate is valid
> FWIW, this is a limitation documented on the homepage since 2007: > https://github.com/jgoerzen/offlineimap/wiki Erh No ... I added that. I didn't see on the homepage erh...? Also my bug report here links to the 2007 thread post already... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#604423: Acknowledgement (postgresql-common: reports the wrong version number to upgrade too)
Sorry I was totally out of it(wasn't paying attention) when I wrote that bug description(original). The bug is really this: So I was present with a prompt when I performed some package updates today. "Processing triggers for postgresql-common ... dpkg: version '/usr/share/myspell/dicts' has bad syntax: invalid character in version number Building PostgreSQL dictionaries from installed myspell/hunspell packages... en_au en_gb en_us Processing triggers for hicolor-icon-theme ..." and the prompt told me that postgresql 8.3 is dated. Which is true. However, the prompt informed me that I should upgrade to postgresql 9 which isn't in debian squeeze. Version 8.4 is in debian squeeze. Yes postgresql 9 is in sid, but it isn't in squeeze. The information displayed in the prompt was the following: " Please be aware that the installation of postgresql-9.0 will automatically create a default cluster 9.0/main. If you want to upgrade the 8.3/main cluster, you need to remove the already existing 9.0 cluster (pg_dropcluster --stop 9.0 main, see manpage for details). The old server and client packages are no longer supported. After the existing clusters are upgraded, the postgresql-8.3 and postgresql-client-8.3 packages should be removed. " Note I do not have postgresql 9 installed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552688: Please decide how Debian should enable hardening build flags
Sir, I think you should be more polite: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=5726 I was simply voicing what I thought as a user of debian. I know this bug report is *technical*. I was making a *technical* comment. Also, note I did not reply to the list did I ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552688: Please decide how Debian should enable hardening build flags
Hi I am just going to say that as a debian user, I would think that compiling with hardening (features on by default) would be a good thing. It means that custom compiled applications (non-debian origin) will be compiled with gcc hardening. Is this really a bad thing? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552688: Please decide how Debian should enable hardening build flags
On 21 November 2010 02:45, Jonathan Nieder wrote: > Hi, > > Raphael Hertzog wrote: > >> We have dpkg-buildflags available but few packages are using it and it's >> unlikely they will be all converted in the wheezy timeframe. > > I agree with the precise meaning of this statement, but the spirit seems > quite wrong. For the packages I am involved in (not many), I have > deliberately not used dpkg-buildflags to make backporting easier. > It is a new facility but a very good one, and I suspect that it will > be adopted fairly quickly, especially if someone writes the appropriate > patches to debian/rules (or even better, writes a program maintainers > can use to automate this). > > Also, I am not the GCC maintainer, but from experience of receiving > reports from people building software with Ubuntu, I think changing > the defaults in GCC is quite wrong. Why do you think this? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603767: gdm: starts on v8 instead of vt7
On 18 November 2010 23:14, Mario 'BitKoenig' Holbe wrote: > On Thu, Nov 18, 2010 at 11:41:37AM +1100, dave b wrote: >> So what's kind of why i asked about how you were trying to find the bug. >> Don't tell me to search through lots of C code point it out! >> I don't have time for that and you seemed to know more! > > Please calm down and don't shout at me. I'm not willing to be treated > this way. I don't have time for that. Sorry what? I think email isn't a very good medium and you misunderstood me :/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603767: gdm: starts on v8 instead of vt7
So what's kind of why i asked about how you were trying to find the bug. Don't tell me to search through lots of C code point it out! I don't have time for that and you seemed to know more! We so then the question is what happens if it is 'busy' and we attempt to use it anyways ;) ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603767: gdm: starts on v8 instead of vt7
I am using gdm and not gdm3. If you can give me more details as to why you think it is a kernel bug that would be good ^ ^ (also the ordering of this bug report on the website rather weird...) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603767: gdm: starts on v8 instead of vt7
> I noticed this happens often to me too, and I can assure you it’s not a > GDM bug. The Linux VT interface wrongly reports vt7 as being in use, > before gdm is even started. It does not happen on all systems, so it > might be related to KMS - for example it happens with my radeon-based > system. > > Which graphics hardware are you using? Oh snap! radeon with KMS. So this is interesting then. So it didn't happen when I rebooted just then. That is I now have vt7 working. Actually imho this is an xorg or gdm bug. Because I was using kvm, the new xorg (from squeeze well a slightly older version) and the same kernel --> 2.6.36 on debian lenny without this problem. So I think it may not be a kernel bug. What makes you think it is a kernel bug? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603594: epiphany-browser: doesn't perform any ssl certificate checking (in the squeeze version)
well it is NOT obvious that a site has an invalid ssl certificate now. Before it was obvious there was a warning, as such I consider this a regression. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603657: Acknowledgement (compiz: the window name stops updating in gnome)
Actually the bug only applies to existing windows. for new ones it doesn't (it is fine). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#589706: [Pkg-openssl-devel] Bug#589706: just out of interest why hasn't the patch posted to disable SSLv2 been applied?
Yes and those things SHOULD break. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603594: epiphany-browser: doesn't perform any ssl certificate checking (in the squeeze version)
Sorry? This is a bug. IIRC it would warn about this behaviour with an alert, now it doesn't. This is still a bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#589706: [Pkg-openssl-devel] Bug#589706: just out of interest why hasn't the patch posted to disable SSLv2 been applied?
Erh ... the patch has been available for a long time here... I think this is important enough to get fixed. Don't you think so? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#589706: just out of interest why hasn't the patch posted to disable SSLv2 been applied?
Just out of interest, why hasn't the patch posted to disable SSLv2 been applied?... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603450: Acknowledgement (offlineimap: fails check the remote servers ssl certificate is valid)
I wish debian let me edit bugs like ubuntu does! (offlineimap: fails check the remote servers ssl certificate is valid) should be (offlineimap: fails *to* check the remote server's ssl certificate is valid) s/servers/server's/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603450: Acknowledgement (offlineimap: fails check the remote servers ssl certificate is valid)
%s/[0]/[1]/ %s/too/to/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603125: closed by Mike Hommey (Re: [xml/sgml-pkgs] Bug#603125: libxml2: requires python-xml-dbg to be built from source but python-xml-dbg isn't a dependency)
It would appear that in squeeze, that python-xml was dropped (the source package for python-xml-dbg). So you seem to be correct for the package in squeeze. So I guess, yes this bug is invalid (except if you count (failing) building libxml2 from sid on lenny as an issue ^ ^ ). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603125: closed by Mike Hommey (Re: [xml/sgml-pkgs] Bug#603125: libxml2: requires python-xml-dbg to be built from source but python-xml-dbg isn't a dependency)
>> > Excuse me ? ... did you test this? >> > Because you are wrong. I just built it from source. >> >> I build it from source every time I upload a new version, in a clean >> chroot, that only installs build dependencies, and thus doesn't contain >> python-xml-dbg, thank you very much. > > The buildds do that too, for that matter, and never failed either. Well I can tell you RIGHT NOW that I needed it. I am using debian lenny, perhaps the package is pulled in by another dependency after lenny? ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#603125: closed by Mike Hommey (Re: [xml/sgml-pkgs] Bug#603125: libxml2: requires python-xml-dbg to be built from source but python-xml-dbg isn't a dependency)
On 11 November 2010 19:48, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the libxml2 package: > > #603125: libxml2: requires python-xml-dbg to be built from source but > python-xml-dbg isn't a dependency Excuse me ? ... did you test this? Because you are wrong. I just built it from source. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601736: closed by martin f krafft (Re: Bug#601736: mdadm: in squeeze the wizard on installation is confusing)
No I meant the default... the default is "all" but the field is said(described) to be "none" or "blank" in the text (of the wizard) ... follow? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#599657: is this going in to squeeze?
is this going in to squeeze? http://packages.qa.debian.org/x/xorg-server.html states: "testing migration excuses: * 10 days old (needed 10 days) * Ignoring block request by freeze, due to unblock request by adsb * out of date on kfreebsd-amd64: xdmx, xdmx-tools, xnest, xserver-common, xserver-xephyr, xserver-xorg-core, xserver-xorg-core-dbg, xserver-xorg-core-udeb, xserver-xorg-dev, xvfb (from 2:1.7.7-7) * Not considered " I would very much like to see this in squeeze as I (used to) use it in lenny. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552688: actually this is a compiler level bug or feature request
actually this is a compiler level bug or feature request. Story: I want to compiler packages hardened As a User of debian I want *anything* I compile (and packaged I install) to be compiled with hardening options. So that I will have some protection against security flaws. THIS IS NOT A DPKG BUG. -- Having nothing, nothing can he lose.-- William Shakespeare, "Henry VI" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552688: This seems a bit stupid
IMHO this is a bit silly you are denying users of debian security features found elsewhere (at least found elsewhere in their packages...). The point is to make the compiler hardened by default not only packages compiled and packaged for debian. Please see http://wiki.debian.org/Hardening and please do reconsider. Given the (actual)patches are already in the source package for 4.4 and 4.5 (gcc) I don't see what your complaint is ? Why carry something you won't maintain ... this doesn't make sense to me. -- Things past redress and now with me past care. -- William Shakespeare, "Richard II" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#597508: please update qemu-kvm to be 0.13.0-rc1 from qemu-kvm git :)
On 20 September 2010 20:59, Michael Tokarev wrote: > 20.09.2010 13:51, david b wrote: >> Package: qemu-kvm >> Severity: wishlist >> >> At >> http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commit;h=72230c523bda18d4dd2f7d16f96cc59e8fbbd6c9 >> 0.13.0-rc1 can be found. >> This version also includes vhost-net support see >> http://www.linux-kvm.org/wiki/index.php?title=VhostNet for more information. > > 0.13 will not be in Squeeze due to feature freeze and because > there's still no official release of qemu-kvm-0.13 (only a > release candidate), and because 0.13 hasn't been tested as > well as 0.12. > > I sure will update package to be based on 0.13, but it will > be available only in experimental branch. Maybe some day > we will make it available as backport. I didn't say it should go into squeeze :) I hope to see it in sid /experimental soon! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#596343: Acknowledgement (dpkg-configure slapd will fail as "mkdir cannot create directory /etc/ldpa/slapd.d" fail on squeeze)
Also please ignore my really broken english in the first email - I am rather tired atm :/ and englishz is directly proportional to my sleep quantityz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#596343: Acknowledgement (dpkg-configure slapd will fail as "mkdir cannot create directory /etc/ldpa/slapd.d" fail on squeeze)
#If you: /etc/init.d/slapd stop #then do dpkg-reconfigure slapd #and in another terminal do: mv /etc/ldap/slapd.d /etc/ldap/slapd.d_old #you can then finish the reconfiguration #then you can finish up with /etc/init.d/slapd stop slapindex && chown -R openldap:openldap /var/lib/ldap /etc/init.d/slapd start #and ldap seems to work nicely from there on out :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561803: This bug affects me after upgrading from lenny to squeeze.
You can sort of work around this by binding the number pad to the arrow key behaviour via the gnome gui(keyboard preferences) . I haven't tested but you may also be able to set the arrow keys manually (to work). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561803: This bug affects me after upgrading from lenny to squeeze.
This bug affects me after upgrading from lenny to squeeze. Is there a reason why this has stalled ? I cannot use untrusted X either re 565296 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565296 So this really sucks... I am happy to test and help out if I can :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#572653: gcc-4.3: compiling a 2.6.33 kernel results in gcc crash
Can you please close this bug. It was actually a buggy kernel I was using to compiler the kernel on that was triggering the bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
