Processed: [gdm3] Bug#724731: dependency problem (libpam-systemd) not solved
Processing control commands:
> found -1 3.8.4-4
Bug #724731 {Done: Emilio Pozuelo Monfort } [gdm3] [gdm3] gdm
does not start properly, cannot login via gdm
Marked as found in versions gdm3/3.8.4-4; no longer marked as fixed in versions
gdm3/3.8.4-4 and reopened.
--
724731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724731: [gdm3] Bug#724731: dependency problem (libpam-systemd) not solved
Control: found -1 3.8.4-4 Hi, thanks for the fixed autologin. I can confirm that autologin works now. But the main problem, that anybody will be confronted with, when upgrading gdm3 to 3.8, is still not solved: libpam-systemd is still no dependency of gdm3 and is thus not installed when upgrading gdm3. With gdm3 version 3.8.4-4 installed, I can remove libpam-systemd without breaking any dependency. But after that I cannot login with gdm3 anymore. In Ubuntu 13.10 that also uses Gnome 3.8, the package gdm has a dependency on libpam-systemd. I'm not sure if this really should be the case, even if another init system is used, but then it works at least with systemd. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724731: This bug is not fixed.
Hello, Please reopen. The bug ist not fixed. The screen still stays blank after login. Only the mouse pointer is seen. Here is the last part of greeter.log: gnome-session[7105]: DEBUG(+): GsmManager: starting app '/org/gnome/SessionManager/App1' gnome-session[7105]: DEBUG(+): Starting app: /org/gnome/SessionManager/App1 gnome-session[7105]: DEBUG(+): GsmAutostartApp: starting gnome-shell.desktop: command=gnome-shell --mode=gdm startup-id=108ec6abbfcebe93921384324603869310007105 gnome-session[7105]: DEBUG(+): GsmAutostartApp: started pid:7360 gnome-session[7105]: DEBUG(+): GsmManager: ending phase APPLICATION gnome-session[7105]: DEBUG(+): GsmManager: starting phase RUNNING gnome-session[7105]: DEBUG(+): gsm_xsmp_server_start gnome-session[7105]: DEBUG(+): GsmPresence: adding idle watch (1) for 300 secs gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged (gnome-settings-daemon:7125): Gvc-WARNING **: Failed to connect context: OK gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.freedesktop.DBus.Properties method=GetAll gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged (gnome-settings-daemon:7125): color-plugin-WARNING **: failed to create device: failed to obtain org.freedesktop.color-manager.create-device auth (gnome-settings-daemon:7125): color-plugin-WARNING **: failed to create device: failed to obtain org.freedesktop.color-manager.create-device auth gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged gnome-session[7105]: DEBUG(+): GsmShell: Connected to the shell gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged (gnome-settings-daemon:7125): color-plugin-WARNING **: failed to obtain org.freedesktop.color-manager.create-profile auth gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged (gnome-settings-daemon:7125): color-plugin-WARNING **: failed to obtain org.freedesktop.color-manager.create-profile auth gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Presence interface=org.freedesktop.DBus.Properties method=GetAll gnome-session[7105]: DEBUG(+): Detected that screensaver has appeared on the bus gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged gnome-session[7105]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged (gnome-shell:7360): Gvc-WARNING **: Failed to connect context: OK Window manager warning: Log level 16: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Passed session and the session the caller is in differs. They must be equal for now. JS LOG: Failed to register AuthenticationAgent gnome-session[7105]: DEBUG(+): GsmXsmpServer: accept_ice_connection() gnome-session[7105]: DEBUG(+): GsmXsmpServer: auth_ice_connection() gnome-session[7105]: DEBUG(+): GsmXSMPClient: Setting up new connection gnome-session[7105]: DEBUG(+): GsmXSMPClient: New client '0x186f8c0 []' And here is the last part of slave.log: gdm-simple-slave[7061]: Adding new utmp record gdm-simple-slave[7061]: GdmSimpleSlave: session started 7415 gdm-simple-slave[7061]: GdmSlave: Trying script /etc/gdm3/PreSession/:0 gdm-simple-slave[7061]: GdmSlave: script /etc/gdm3/PreSession/:0 not found; skipping gdm-simple-slave[7061]: GdmSlave: Trying script /etc/gdm3/PreSessi
Bug#728444: libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1
On Sat, Nov 9, 2013 at 1:27 PM, Michael Gilbert wrote: > control: tag -1 pending > > On Sat, Nov 2, 2013 at 4:30 PM, Michael Gilbert wrote: >> control: tag -1 patch >> >> Hi, this results from upstream enabling pthreads in 2.11. I've >> attached a patch to disable pthreads until a more permanent solution >> is found for xpdf. > > Hi, I've uploaded an nmu with the above patch to delayed/5 fixing > this. Please let me know if I should delay or cancel if you think > this isn't the best solution. Based on the emotional messages seen so far, I've delayed this another 10 days to give it more time for potential review. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729453: marked as done (lighttpd: multiple security issues)
Your message dated Wed, 13 Nov 2013 05:03:30 + with message-id and subject line Bug#729453: fixed in lighttpd 1.4.33-1+nmu1 has caused the Debian Bug report #729453, regarding lighttpd: multiple security issues to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 729453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: lighttpd severity: serious version: 1.4.28-1 Multiple issues have been disclosed for lighttpd: CVE-2013-4508 http://download.lighttpd.net/lighttpd/security/lighttpd_sa_2013_01.txt CVE-2013-4559 http://download.lighttpd.net/lighttpd/security/lighttpd_sa_2013_02.txt CVE-2013-4560 http://download.lighttpd.net/lighttpd/security/lighttpd_sa_2013_03.txt --- End Message --- --- Begin Message --- Source: lighttpd Source-Version: 1.4.33-1+nmu1 We believe that the bug you reported is fixed in the latest version of lighttpd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 729...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated lighttpd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Nov 2013 02:19:47 + Source: lighttpd Binary: lighttpd lighttpd-doc lighttpd-mod-mysql-vhost lighttpd-mod-trigger-b4-dl lighttpd-mod-cml lighttpd-mod-magnet lighttpd-mod-webdav Architecture: source amd64 all Version: 1.4.33-1+nmu1 Distribution: unstable Urgency: high Maintainer: Debian lighttpd maintainers Changed-By: Michael Gilbert Description: lighttpd - fast webserver with minimal memory footprint lighttpd-doc - documentation for lighttpd lighttpd-mod-cml - cache meta language module for lighttpd lighttpd-mod-magnet - control the request handling module for lighttpd lighttpd-mod-mysql-vhost - MySQL-based virtual host configuration for lighttpd lighttpd-mod-trigger-b4-dl - anti-deep-linking module for lighttpd lighttpd-mod-webdav - WebDAV module for lighttpd Closes: 729453 Changes: lighttpd (1.4.33-1+nmu1) unstable; urgency=high . * Non-maintainer upload by the Security Team (closes: #729453). * Fix cve-2013-4508: ssl cipher suites issue. * Fix cve-2013-4559: setuid privilege escalation issue. * Fix cve-2013-4560: use-after-free in fam. Checksums-Sha1: 60b88c0ae244562b76056a265fb74f8ff38229d1 3413 lighttpd_1.4.33-1+nmu1.dsc 1f3b227cc2ed8b0f7935a1557ec89ba873422b09 32357 lighttpd_1.4.33-1+nmu1.debian.tar.gz 5a63d1d1178a5bfaa9fb649015307a87fdd25ae7 235066 lighttpd_1.4.33-1+nmu1_amd64.deb cfb680a9d75edcbba9b033398c4fda36e838b931 60570 lighttpd-doc_1.4.33-1+nmu1_all.deb 62fb86d4fa7bf4d6de59d6f77307e6a02f0357f1 18972 lighttpd-mod-mysql-vhost_1.4.33-1+nmu1_amd64.deb d4e2f8b2f4a1ce9ade3c06b2e836cc856a69e58c 20320 lighttpd-mod-trigger-b4-dl_1.4.33-1+nmu1_amd64.deb 56710008913762e922bcb58afd5902afa6ef3313 22818 lighttpd-mod-cml_1.4.33-1+nmu1_amd64.deb 17c503f4ccfb2a91a1674d7e4379cced339d7d72 23626 lighttpd-mod-magnet_1.4.33-1+nmu1_amd64.deb b6def3d5015fbd60de1a3afcc669c27cfee5cb3b 29112 lighttpd-mod-webdav_1.4.33-1+nmu1_amd64.deb Checksums-Sha256: 4a8b972a6e4423d432782958fc9b5cbabc75c0b86f0ff299c4c9e40099cef757 3413 lighttpd_1.4.33-1+nmu1.dsc c945c236648fcf851d75bcca0372df756a6df3829043ba8d3ae612646acede69 32357 lighttpd_1.4.33-1+nmu1.debian.tar.gz 089311f56dac6db9e5c770ad180a799b6d955909b4e47fdbfc3a96a39b237a78 235066 lighttpd_1.4.33-1+nmu1_amd64.deb a687b2bfe8ddf7f4cfed1c3587fab7c8e2647dc60c999a06ad7c43f6f8c48ca6 60570 lighttpd-doc_1.4.33-1+nmu1_all.deb 7931376b1135b56796ec352a18655aeb88dbcbe24dfe1021d3ab58d246ec947c 18972 lighttpd-mod-mysql-vhost_1.4.33-1+nmu1_amd64.deb 17e295b7e93ca5703664b06e2e9d8c3ad9c1fabe0437072bbbcd4b1a689489f4 20320 lighttpd-mod-trigger-b4-dl_1.4.33-1+nmu1_amd64.deb 2ffbd5285637e240ddf68965d63e33edb57fc46040245f30a598d582eb721c57 22818 lighttpd-mod-cml_1.4.33-1+nmu1_amd64.deb 89c39f3c4244ac81ecad52e7157dbe32bb3652bb6fb6d4e45a6cddcc5bdccc22 23626 lighttpd-mod-magnet_1.4.33-1+nmu1_amd64.deb b762b221f3a983dbfcbe244c88fe3c009a46c9ba0425f14c8cf9fdf0a0341142 29112 lighttpd-mod-webdav_1.4.33-1+nmu1_amd64.deb Files:
Bug#729453: lighttpd: multiple security issues
control: tag -1 patch
Hi, I've uploaded an nmu fixing these issues. Please see attached patch.
Best wishes,
Mike
diff -Nru lighttpd-1.4.33/debian/changelog lighttpd-1.4.33/debian/changelog
--- lighttpd-1.4.33/debian/changelog 2013-10-15 20:24:13.0 +
+++ lighttpd-1.4.33/debian/changelog 2013-11-13 04:15:52.0 +
@@ -1,3 +1,12 @@
+lighttpd (1.4.33-1+nmu1) unstable; urgency=high
+
+ * Non-maintainer upload by the Security Team (closes: #729453).
+ * Fix cve-2013-4508: ssl cipher suites issue.
+ * Fix cve-2013-4559: setuid privilege escalation issue.
+ * Fix cve-2013-4560: use-after-free in fam.
+
+ -- Michael Gilbert Wed, 13 Nov 2013 02:19:47 +
+
lighttpd (1.4.33-1) unstable; urgency=low
* Drop the connection-dos.patch - merged upstream.
diff -Nru lighttpd-1.4.33/debian/patches/cve-2013-4508.patch lighttpd-1.4.33/debian/patches/cve-2013-4508.patch
--- lighttpd-1.4.33/debian/patches/cve-2013-4508.patch 1970-01-01 00:00:00.0 +
+++ lighttpd-1.4.33/debian/patches/cve-2013-4508.patch 2013-11-13 02:35:53.0 +
@@ -0,0 +1,369 @@
+origin: http://download.lighttpd.net/lighttpd/security/lighttpd_sa_2013_01.txt
+commit 1af871fcef97574c71870309d572d6b1026ee605
+Author: Stefan Bühler
+Date: Tue Nov 5 15:29:07 2013 +
+
+[ssl] fix SNI handling; only use key+cert+verify-client from SNI specific config (fixes #2525, CVE-2013-4508)
+
+pull all ssl.ca-file values into all SSL_CTXs, but use only the local
+ssl.ca-file for verify-client; correct SNI name is no requirement,
+so enforcing verification for a subset of SNI names doesn't actually
+protect those.
+
+From: Stefan Bühler
+
+git-svn-id: svn://svn.lighttpd.net/lighttpd/branches/lighttpd-1.4.x@2913 152afb58-edef-0310-8abb-c4023f1b3aa9
+
+Index: lighttpd-1.4.33/src/base.h
+===
+--- lighttpd-1.4.33.orig/src/base.h 2013-11-13 02:35:50.218536022 +
lighttpd-1.4.33/src/base.h 2013-11-13 02:35:50.214536022 +
+@@ -320,7 +320,11 @@
+ off_t *global_bytes_per_second_cnt_ptr; /* */
+
+ #ifdef USE_OPENSSL
+- SSL_CTX *ssl_ctx;
++ SSL_CTX *ssl_ctx; /* not patched */
++ /* SNI per host: with COMP_SERVER_SOCKET, COMP_HTTP_SCHEME, COMP_HTTP_HOST */
++ EVP_PKEY *ssl_pemfile_pkey;
++ X509 *ssl_pemfile_x509;
++ STACK_OF(X509_NAME) *ssl_ca_file_cert_names;
+ #endif
+ } specific_config;
+
+Index: lighttpd-1.4.33/src/configfile.c
+===
+--- lighttpd-1.4.33.orig/src/configfile.c 2013-11-13 02:35:50.218536022 +
lighttpd-1.4.33/src/configfile.c 2013-11-13 02:35:50.214536022 +
+@@ -339,9 +339,13 @@
+
+ PATCH(ssl_pemfile);
+ #ifdef USE_OPENSSL
+- PATCH(ssl_ctx);
++ PATCH(ssl_pemfile_x509);
++ PATCH(ssl_pemfile_pkey);
+ #endif
+ PATCH(ssl_ca_file);
++#ifdef USE_OPENSSL
++ PATCH(ssl_ca_file_cert_names);
++#endif
+ PATCH(ssl_cipher_list);
+ PATCH(ssl_dh_file);
+ PATCH(ssl_ec_curve);
+@@ -409,10 +413,14 @@
+ } else if (buffer_is_equal_string(du->key, CONST_STR_LEN("ssl.pemfile"))) {
+ PATCH(ssl_pemfile);
+ #ifdef USE_OPENSSL
+-PATCH(ssl_ctx);
++PATCH(ssl_pemfile_x509);
++PATCH(ssl_pemfile_pkey);
+ #endif
+ } else if (buffer_is_equal_string(du->key, CONST_STR_LEN("ssl.ca-file"))) {
+ PATCH(ssl_ca_file);
++#ifdef USE_OPENSSL
++PATCH(ssl_ca_file_cert_names);
++#endif
+ } else if (buffer_is_equal_string(du->key, CONST_STR_LEN("ssl.honor-cipher-order"))) {
+ PATCH(ssl_honor_cipher_order);
+ } else if (buffer_is_equal_string(du->key, CONST_STR_LEN("ssl.empty-fragments"))) {
+Index: lighttpd-1.4.33/src/network.c
+===
+--- lighttpd-1.4.33.orig/src/network.c 2013-11-13 02:35:50.218536022 +
lighttpd-1.4.33/src/network.c 2013-11-13 02:35:50.214536022 +
+@@ -112,20 +112,46 @@
+ config_patch_connection(srv, con, COMP_HTTP_SCHEME);
+ config_patch_connection(srv, con, COMP_HTTP_HOST);
+
+- if (NULL == con->conf.ssl_ctx) {
+- /* ssl_ctx <=> pemfile was set <=> ssl_ctx got patched: so this should never happen */
++ if (NULL == con->conf.ssl_pemfile_x509 || NULL == con->conf.ssl_pemfile_pkey) {
++ /* x509/pkey available <=> pemfile was set <=> pemfile got patched: so this should never happen, unless you nest $SERVER["socket"] */
+ log_error_write(srv, __FILE__, __LINE__, "ssb", "SSL:",
+- "null SSL_CTX for TLS server name", con->tlsext_server_name);
++ "no certificate/private key for TLS server name", con->tlsext_server_name);
+ return SSL_TLSEXT_ERR_ALERT_FATAL;
+ }
+
+- /* switch to new SSL_CTX in reaction to a client's server_name extension */
+- if (con->conf.ssl_ctx != SSL_set_SSL_CTX(ssl, con->conf.ssl_ctx)) {
+- log_error_write(srv, __FILE__, __LINE__, "ssb", "SSL:",
+- "failed to set SSL_CTX for TLS server name", con->tlsext_server_name);
++ /* first set certificate! setting private key checks whether certificate m
Processed: re: lighttpd: multiple security issues
Processing control commands: > tag -1 patch Bug #729453 [lighttpd] lighttpd: multiple security issues Added tag(s) patch. -- 729453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729453: lighttpd: multiple security issues
package: lighttpd severity: serious version: 1.4.28-1 Multiple issues have been disclosed for lighttpd: CVE-2013-4508 http://download.lighttpd.net/lighttpd/security/lighttpd_sa_2013_01.txt CVE-2013-4559 http://download.lighttpd.net/lighttpd/security/lighttpd_sa_2013_02.txt CVE-2013-4560 http://download.lighttpd.net/lighttpd/security/lighttpd_sa_2013_03.txt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724731: GDM3 3.8.4-4 didn't solve the bug
Hi, I was very excited about testing the Gnome 3.8 that I decided upgrade some packages from the SID, the packages I upgraded were: gdm3 gnome-control-center gnome-disk-utility gnome-session gnome-settings-daemon gnome-shell gnome-shell-extensions gsettings-desktop-schemas mutter nautilus seed gnome-clocks And when I restart my laptop, the GDM3 won't load, I get the same symptoms as described in the bug report and its comments, my workaroud was to install lightdm and set it to be my default display manager. Sorry for the bad feedback, I'm didn't had much time to read about the Debian bug report policies, but I got worried that the GDM3 3.8.4.4 will be in Debian Jessie in a couple of days, without really solving the bug. -- Samuel Henrique O. P. [samueloph] Técnico em Informática - UTFPR [2012]. Estudante de Engenharia de Computação - UTFPR.
Processed: affects 729025, found 722940 in 8.5.15-2, tagging 729251 ..., fixed 648170 in 1:3.4.5-1 ...
Processing commands for cont...@bugs.debian.org:
> affects 729025 + python3-json-patch
Bug #729025 [python-json-patch] python3-json-patch & python-json-patch not
installable together
Added indication that 729025 affects python3-json-patch
> found 722940 8.5.15-2
Bug #722940 [tk8.5-doc] tk8.5-doc: fails to upgrade from 'sid' - trying to
overwrite /usr/share/tcltk/tk8.5/demos
Marked as found in versions tk8.5/8.5.15-2.
> tags 729251 + sid
Bug #729251 [src:gstreamer0.10-ffmpeg] gstreamer0.10-ffmpeg: uninstallable with
libav 9
Added tag(s) sid.
> notfixed 648170 libreoffice-writer/1:3.4.5-2
Bug #648170 {Done: Marco Mattiolo }
[libreoffice-writer] libreoffice-writer: 'Display nonprinting characters'
become unchecked during printing and PDF export
The source libreoffice-writer and version 1:3.4.5-2 do not appear to match any
binary packages
No longer marked as fixed in versions libreoffice-writer/1:3.4.5-2.
> fixed 648170 1:3.4.5-1
Bug #648170 {Done: Marco Mattiolo }
[libreoffice-writer] libreoffice-writer: 'Display nonprinting characters'
become unchecked during printing and PDF export
Marked as fixed in versions libreoffice/1:3.4.5-1.
> fixed 648170 1:3.5.0~beta3-1
Bug #648170 {Done: Marco Mattiolo }
[libreoffice-writer] libreoffice-writer: 'Display nonprinting characters'
become unchecked during printing and PDF export
Marked as fixed in versions libreoffice/1:3.5.0~beta3-1.
> found 728695 1.0.4-1
Bug #728695 [src:stressapptest] Fix armhf buildds
Marked as found in versions stressapptest/1.0.4-1.
> tags 728695 + jessie sid
Bug #728695 [src:stressapptest] Fix armhf buildds
Added tag(s) sid and jessie.
> tags 728695 + patch
Bug #728695 [src:stressapptest] Fix armhf buildds
Added tag(s) patch.
> tags 727594 + jessie sid
Bug #727594 [libgpod] IA64 and SPARC support removed from Mono
Added tag(s) sid and jessie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
648170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648170
722940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722940
727594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727594
728695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728695
729025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729025
729251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728695: Fix armhf buildds
On Monday, 4. November 2013 11:51:21 Mathieu Malaterre wrote: > configure:2556: error: arm is not supported! Try x86_64, i686, > powerpc, or armv7a > ... ubuntu has a patch ... http://patches.ubuntu.com/s/stressapptest/stressapptest_1.0.4-2ubuntu1.patch Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728041: marked as done (insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `courier-pop-ssl' overrides LSB defaults (0 1 6).)
Your message dated Wed, 13 Nov 2013 01:00:53 +0100 with message-id <201311130100.54429.a...@debian.org> and subject line Re: insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `courier-pop-ssl' overrides LSB defaults (0 1 6). has caused the Debian Bug report #728041, regarding insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `courier-pop-ssl' overrides LSB defaults (0 1 6). to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 728041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: courier-pop-ssl Version: 0.68.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? apt-get upgrade fails at courier-pop-ssl because of: insserv: warning: current start runlevel(s) (empty) of script `courier-pop-ssl' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `courier-pop-ssl' overrides LSB defaults (0 1 6). Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/courier-pop-ssl_0.68.2-1+b1_amd64.deb *** End of the template - remove these lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.10-3-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages courier-pop-ssl depends on: ii courier-pop 0.68.2-1+b1 ii courier-ssl 0.68.2-1+b1 ii debconf 1.5.51 courier-pop-ssl recommends no packages. Versions of packages courier-pop-ssl suggests: pn courier-doc -- no debconf information --- End Message --- --- Begin Message --- On Sunday, 27. October 2013 21:11:58 Andreas Rittershofer wrote: > apt-get upgrade fails at courier-pop-ssl because of: > > insserv: warning: current start runlevel(s) (empty) of script > `courier-pop-ssl' overrides LSB defaults (2 3 4 5). insserv: warning: > current stop runlevel(s) (0 1 2 3 4 5 6) of script `courier-pop-ssl' > overrides LSB defaults (0 1 6). Fehler traten auf beim Bearbeiten von: > /var/cache/apt/archives/courier-pop-ssl_0.68.2-1+b1_amd64.deb You manually disabled the courier-pop-ssl service by turning all the SXXcourier-pop-ssl into KXXcourier-pop-ssl - this change is preserved on upgrades. Manually remove and readd the service to restore the defaults: insserv -v -r courier-pop-ssl insserv -v -d courier-pop-ssl There is also no old version that had this wrong: squeeze has 0.65.0-3: ### BEGIN INIT INFO # Short-Description: Courier POP3-SSL server # Provides: courier-pop-ssl # Required-Start:$remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 ### END INIT INFO wheezy has 0.68.2-1: ### BEGIN INIT INFO # Short-Description: Courier POP3 server # Provides: courier-pop # Required-Start:$remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 ### END INIT INFO jessie/sid has 0.68.2-1+b1: ### BEGIN INIT INFO # Short-Description: Courier POP3-SSL server # Provides: courier-pop-ssl # Required-Start:$remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 ### END INIT INFO Andreas--- End Message ---
Processed: merge
Processing commands for cont...@bugs.debian.org: > reassign 721491 partman-base Bug #721491 [partman-base] partman-base: /dev/disk links are not refreshed on dreamplug after repartitioning Ignoring request to reassign bug #721491 to the same package > severity 721491 normal Bug #721491 [partman-base] partman-base: /dev/disk links are not refreshed on dreamplug after repartitioning Severity set to 'normal' from 'critical' > merge 721491 729445 Bug #721491 [partman-base] partman-base: /dev/disk links are not refreshed on dreamplug after repartitioning Bug #729445 [partman-base] No /dev/disk/by-uuid link created for ext2 partitions Marked as found in versions partman-base/165. Added tag(s) d-i. Merged 721491 729445 > -- Stopping processing here. Please contact me if you need assistance. -- 721491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721491 729445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729412: python-django-south: incompatibilities with Django 1.6
Control: tag -1 sid On Tuesday, 12. November 2013 18:05:29 Luke Faraone wrote: > python-django-south as shipped in unstable is not currently compatible > with Django 1.6. Attached is a traceback. (the traceback was not taken only affects sid: python-django | 1.4.5-1+deb7u4 | wheezy| source, all python-django | 1.5.2-1~bpo70+1 | wheezy-backports | source, all python-django | 1.5.4-1 | jessie| source, all python-django | 1.6-1| sid | source, all Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: python-django-south: incompatibilities with Django 1.6
Processing control commands: > tag -1 sid Bug #729412 [python-django-south] python-django-south: incompatibilities with Django 1.6 Added tag(s) sid. -- 729412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729022: marked as done (libgcj14: File conflict between libgcj14 and gcj-4.8-jre-headless)
c1 - support library providing __atomic built-in functions (x32) libx32atomic1-dbg - support library providing __atomic built-in functions (x32 debug libx32gcc-4.8-dev - GCC support library (x32 development files) libx32gcc1 - GCC support library (x32) libx32gcc1-dbg - GCC support library (debug symbols) libx32gfortran-4.8-dev - Runtime library for GNU Fortran applications (x32 development fil libx32gfortran3 - Runtime library for GNU Fortran applications (x32) libx32gfortran3-dbg - Runtime library for GNU Fortran applications (x32 debug symbols) libx32go4 - Runtime library for GNU Go applications (x32) libx32go4-dbg - Runtime library for GNU Go applications (x32 debug symbols) libx32gomp1 - GCC OpenMP (GOMP) support library (x32) libx32gomp1-dbg - GCC OpenMP (GOMP) support library (x32 debug symbols) libx32itm1 - GNU Transactional Memory Library (x32) libx32itm1-dbg - GNU Transactional Memory Library (x32 debug symbols) libx32objc-4.8-dev - Runtime library for GNU Objective-C applications (x32 development libx32objc4 - Runtime library for GNU Objective-C applications (x32) libx32objc4-dbg - Runtime library for GNU Objective-C applications (x32 debug symbo libx32quadmath0 - GCC Quad-Precision Math Library (x32) libx32quadmath0-dbg - GCC Quad-Precision Math Library (x32 debug symbols) libx32stdc++-4.8-dev - GNU Standard C++ Library v3 (development files) libx32stdc++6 - GNU Standard C++ Library v3 (x32) libx32stdc++6-4.8-dbg - GNU Standard C++ Library v3 (debugging files) Closes: 729022 Changes: gcc-4.8 (4.8.2-3) unstable; urgency=low . * Update to SVN 20131112 (r204704) from the gcc-4_8-branch. * Don't ship java.security in both libgcj14 and gcj-4.8-headless. Closes: #729022. * Disable gdc tests on architectures without libphobos port. Checksums-Sha1: 1e782be15f0e6e4ade95254104f0a1e000abf05d 11222 gcc-4.8_4.8.2-3.dsc f7c0ade64dcd09ed0b140a32c08b4e7bb4ed3986 932291 gcc-4.8_4.8.2-3.diff.gz 3eb669e7e070a8818a03f75b4ba820ca256bbe88 70930518 gcc-4.8-source_4.8.2-3_all.deb d54c026bd542ed07cec5b1b70643a7ae6ace1d75 10349816 gcj-4.8-jre-lib_4.8.2-3_all.deb 21558b5fb62baf17cc2445e7fc7ef33d5ae81c93 11661618 gcj-4.8-source_4.8.2-3_all.deb d021fe8fa6b1fdf8d0b0f0057cbd7787e255d493 18802178 libgcj-doc_4.8.2-3_all.deb 9ae9d13c6c87ac3caa15b84cbd9adfccf6e84db5 9878292 libstdc++-4.8-doc_4.8.2-3_all.deb 72d0c8bfdf41f4b9963829204a573d2bf48de11d 1385376 gcc-4.8-locales_4.8.2-3_all.deb b8cb20e2712b18101301bcff279b7a09b222ae30 150388 gcc-4.8-base_4.8.2-3_amd64.deb 3ffd04d876bfc740739976a553c184d35408b6eb 37448 libgcc1_4.8.2-3_amd64.deb 7abca1fc454aecdf2bec4d6761d3c83cd1078c96 80482 libgcc1-dbg_4.8.2-3_amd64.deb d81e1da1247eaa1b483a5ca1662fda5b19a80691 1687716 libgcc-4.8-dev_4.8.2-3_amd64.deb bebcd996b8e855dc628d1339dddead7fb9572a1f 46636 lib32gcc1_4.8.2-3_amd64.deb e81d2d313f97e9919e03bba4ac48500de8de97d9 83694 lib32gcc1-dbg_4.8.2-3_amd64.deb e6fd6ab681a471ace79c0439bb5740a617e1feb1 1681700 lib32gcc-4.8-dev_4.8.2-3_amd64.deb 7f81dff7b44d51bfb5d3300d0cba34dde95782e8 36482 libx32gcc1_4.8.2-3_amd64.deb a174f0569e065758b2593ce3ec0455e3a580d1ec 78364 libx32gcc1-dbg_4.8.2-3_amd64.deb ca8e0a539bfe54dc7d5809839a490dd7a682660f 1556778 libx32gcc-4.8-dev_4.8.2-3_amd64.deb e515821ee276a5dbe068ffd6b2ff1af6f623da0b 125724 libquadmath0_4.8.2-3_amd64.deb 3a419f060a22d8f6fa090ecb807ff0d7a606e53c 140592 libquadmath0-dbg_4.8.2-3_amd64.deb d0012f7032934a0efe51bde19e930ff85299b5b8 185992 lib32quadmath0_4.8.2-3_amd64.deb e3d5a5b9be5ba303ecc8cee294762a102aecb173 153564 lib32quadmath0-dbg_4.8.2-3_amd64.deb 57ccb6bc9acf6e82526c89d638681bec3f106bb7 127828 libx32quadmath0_4.8.2-3_amd64.deb 1fd03713ad7924186d4d8bbcfd892c41853d9348 141238 libx32quadmath0-dbg_4.8.2-3_amd64.deb 0ff1b0bb74a7d22c7be12697a57afcc6133b85f3 22954 libgomp1_4.8.2-3_amd64.deb 0c1228890f515dcb41aff3edb9c9c18e52bced56 55868 libgomp1-dbg_4.8.2-3_amd64.deb 95ce77a289b270a538a34f9cadfa5b74b597a366 24750 lib32gomp1_4.8.2-3_amd64.deb f930f40f3a0342c522e8642a73ff98aced2cce8b 56130 lib32gomp1-dbg_4.8.2-3_amd64.deb ca76747989061110135655ad3c01eea8aa4c4de6 22354 libx32gomp1_4.8.2-3_amd64.deb 4ce1faa4cd70375ee66a1cb177a798a4d2c1dee7 54222 libx32gomp1-dbg_4.8.2-3_amd64.deb 9b61b7ca8643ed2fa35cf1f6095910f4772f77e5 28484 libitm1_4.8.2-3_amd64.deb ea067e11555672175e74b4871f417e41355248cc 179296 libitm1-dbg_4.8.2-3_amd64.deb e622d210262131911e6260febde19c571bb400a0 28296 lib32itm1_4.8.2-3_amd64.deb f74f9f9b886b386a44c8c6ae009f2156718b527b 172562 lib32itm1-dbg_4.8.2-3_amd64.deb 150cf8a29bee46e9a434a423324552fadf439ddb 28232 libx32itm1_4.8.2-3_amd64.deb 1fc7881c4c68038dfd5ded3cd613c91df201dcfb 169172 libx32itm1-dbg_4.8.2-3_amd64.deb 016ef6001f7ef28a5e47cf3155ed160168b3e789 8408 libatomic1_4.8.2-3_amd64.deb 0f9134fe4b0a3b479f0423a45d7672e88f12344b 15344 libatomic1-dbg_4.8.2-3_amd64.deb 991724281084c93dec3685d3567a3c844339b8d2 7904 lib32atomic1_4.8.2-3_amd64.deb 6ce4193131c1770d792e68ee7d77e5564b6195f7 13364
Processed: Re: Bug#729443: flashplugin-nonfree: can't upgrade
Processing commands for cont...@bugs.debian.org: > retitle 729443 flashplugin-nonfree: please update checksums for newer Adobe > Flash Player version Bug #729443 [flashplugin-nonfree] flashplugin-nonfree: can't upgrade Changed Bug title to 'flashplugin-nonfree: please update checksums for newer Adobe Flash Player version' from 'flashplugin-nonfree: can't upgrade' > severity 729443 wishlist Bug #729443 [flashplugin-nonfree] flashplugin-nonfree: please update checksums for newer Adobe Flash Player version Severity set to 'wishlist' from 'grave' > stop Stopping processing here. Please contact me if you need assistance. -- 729443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729443: flashplugin-nonfree: can't upgrade
Package: flashplugin-nonfree Version: 1:3.2 Severity: grave Tags: security Justification: user security hole Dear Maintainer, # update-flashplugin-nonfree --status Flash Player version installed on this system : 11.2.202.310 Flash Player version available on upstream site: 11.2.202.327 flash-mozilla.so - auto mode link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 Current 'best' version is '/usr/lib/flashplugin-nonfree/libflashplayer.so'. # update-flashplugin-nonfree --install already exists: /usr/bin/flash-player-properties already exists: /usr/share/applications/flash-player-properties.desktop already exists: /usr/share/icons/hicolor/16x16/apps/flash-player-properties.png already exists: /usr/share/icons/hicolor/22x22/apps/flash-player-properties.png already exists: /usr/share/icons/hicolor/24x24/apps/flash-player-properties.png already exists: /usr/share/icons/hicolor/32x32/apps/flash-player-properties.png already exists: /usr/share/icons/hicolor/48x48/apps/flash-player-properties.png already exists: /usr/share/pixmaps/flash-player-properties.png I tried to --uninstall and --install, but it does the same thing. The problem is similar to the bug #722416. Thank you. ung -- Package-specific info: Debian version: 7.2 Architecture: amd64 Package version: 1:3.2 Adobe Flash Player version: LNX 11,2,202,310 MD5 checksums: 4053a6e097d2531771ee5fdde4be866b /var/cache/flashplugin-nonfree/get-upstream-version.pl 34b436d5c9c4e681bd619a6efad84148 /var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz e23b0477d5b9956804f2e5105100b8cf /usr/lib/flashplugin-nonfree/libflashplayer.so Alternatives: flash-mozilla.so - auto mode link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 Current 'best' version is '/usr/lib/flashplugin-nonfree/libflashplayer.so'. lrwxrwxrwx 1 root root 34 Nov 12 03:29 /usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so /usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to `/etc/alternatives/flash-mozilla.so' -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages flashplugin-nonfree depends on: ii binutils 2.22-8 ii debconf [debconf-2.0] 1.5.49 ii gnupg 1.4.12-7+deb7u2 ii libatk1.0-02.4.0-2 ii libcairo2 1.12.2-3 ii libcurl3-gnutls7.26.0-1+wheezy4 ii libfontconfig1 2.9.0-7.1 ii libfreetype6 2.4.9-1.1 ii libgcc11:4.7.2-5 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgtk2.0-02.24.10-2 ii libnspr4 2:4.9.2-1 ii libnss32:3.14.4-1 ii libpango1.0-0 1.30.0-1 ii libstdc++6 4.7.2-5 ii libx11-6 2:1.5.0-1+deb7u1 ii libxext6 2:1.3.1-2+deb7u1 ii libxt6 1:1.1.3-1+deb7u1 ii wget 1.13.4-3 flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: pn hal ii iceweasel 17.0.10esr-1~deb7u1 ii konqueror-nsplugins4:4.8.4-2 ii ttf-dejavu 2.33-3 ii ttf-mscorefonts-installer 3.4+nmu1 pn ttf-xfree86-nonfree -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729253: marked as done (cheese: One or more needed GStreamer elements are missing: cluttervideosink.)
Your message dated Tue, 12 Nov 2013 22:03:28 + with message-id and subject line Bug#729253: fixed in cheese 3.10.1-1sid1 has caused the Debian Bug report #729253, regarding cheese: One or more needed GStreamer elements are missing: cluttervideosink. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 729253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cheese Version: 3.10.1-1 Severity: grave Justification: renders package unusable When I launch cheese, the following message shows up instead of picture from camera: One or more needed GStreamer elements are missing: cluttervideosink. I do have packages like `libclutter-gst-1.0-0` and `libclutter-gst-2.0-0` installed—I found those after some googling. The program seems unusable to me—no button works, even though I can see that the preferences window shows up my camera. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-1-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cheese depends on: ii cheese-common 3.10.1-1 ii gnome-video-effects 0.4.0-1 ii libc6 2.17-93 ii libcanberra-gtk3-00.30-2 ii libcheese-gtk23 3.10.1-1 ii libcheese73.10.1-1 ii libclutter-1.0-0 1.14.4-3 ii libclutter-gtk-1.0-0 1.4.4-3 ii libgdk-pixbuf2.0-02.28.2-1 ii libglib2.0-0 2.36.4-1 ii libgnome-desktop-3-7 3.8.4-2 ii libgstreamer1.0-0 1.2.0-1 ii libgtk-3-03.8.6-1 Versions of packages cheese recommends: ii gnome-icon-theme3.10.0-1 ii gvfs1.16.3-1+b1 ii hicolor-icon-theme 0.12-1 ii nautilus-sendto 3.6.1-2 ii yelp3.10.1-1 Versions of packages cheese suggests: pn gnome-video-effects-frei0r -- no debconf information --- End Message --- --- Begin Message --- Source: cheese Source-Version: 3.10.1-1sid1 We believe that the bug you reported is fixed in the latest version of cheese, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 729...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Henriksson (supplier of updated cheese package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 12 Nov 2013 20:43:25 +0100 Source: cheese Binary: cheese cheese-common libcheese-gtk23 libcheese-gtk-dev libcheese7 libcheese-dev libcheese-doc gir1.2-cheese-3.0 Architecture: source all amd64 Version: 3.10.1-1sid1 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers Changed-By: Andreas Henriksson Description: cheese - tool to take pictures and videos from your webcam cheese-common - Common files for the Cheese tool to take pictures and videos gir1.2-cheese-3.0 - tool to take pictures and videos from your webcam - gir bindings libcheese-dev - tool to take pictures and videos from your webcam - base dev libcheese-doc - tool to take pictures and videos from your webcam - documentation libcheese-gtk-dev - tool to take pictures and videos from your webcam - widgets dev libcheese-gtk23 - tool to take pictures and videos from your webcam - widgets libcheese7 - tool to take pictures and videos from your webcam - base library Closes: 729253 Changes: cheese (3.10.1-1sid1) unstable; urgency=low . * Depend on gstreamer1.0-clutter for cluttervideosink (Closes: #729253) Checksums-Sha1: 23bb3cd25e70558389ab015aeccec44af64322f3 2641 cheese_3.10.1-1sid1.dsc 02d8e8758f8f96a5301c4ab1ef185134e4bbf380 17881 cheese_3.10.1-1sid1.debian.tar.gz f10f8e14ab2665d76641733d62ad312ff53c5fe4 3173748 cheese-common_3.10.1-1sid1_all.deb 7a1d7370842034c6f1241ff572b09b2bec886042 375692 libcheese-doc_3.10.1-1sid1_all.deb 0975929c873eb500588eb8a183cda4a48e237375 267226 cheese_3.10.1-1sid1_amd64.deb 1067c61c279eee9f0199a7c4a59b7b447ad3f8a2 237004 libcheese-gtk23_3.10.1-1sid1_amd64.deb 791b226ebfe579c042ceeaa7e63de4
Bug#727758: cups segfaults in libdbus
On Fri, Nov 8, 2013 at 10:57 AM, wrote: > Package: cups > Version: 1.6.3-1 > Followup-For: Bug #727758 > > Hi, > i also got > > cupsd[3263]: segfault at 0 ip b75776c2 sp bfad0070 error 4 in > libdbus-1.so.3.7.5[b755+49000] > Could you try to get information about instruction address at b75776c2 ? Bastien > sometimes. It ist not reproducable. Most of the time nothing happens but if > it does > also rebooting doesn`t solve the problem. > The machine itself has to be shutdown for the night. > All printers are attached via network (HP OfficeJet Pro 8600) > If i restart the service manually everything is working fine, but it is a > remote box, > an the users there don´t like console typing. > I hope for a quick solution. > > > OT:Is this report ok? Missing something? Wrong facts? > I´ve read the manual, but i am not sure. > > > -- System Information: > Debian Release: jessie/sid > APT prefers testing > APT policy: (500, 'testing'), (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages cups depends on: > ii cups-client1.6.3-1 > ii cups-common1.6.3-1 > ii cups-daemon1.6.3-1 > ii cups-filters 1.0.34-3+b1 > ii cups-ppdc 1.5.3-2.15 > ii cups-server-common 1.6.3-1 > ii debconf [debconf-2.0] 1.5.49 > ii ghostscript9.05~dfsg-8 > ii libavahi-client3 0.6.31-1 > ii libavahi-common3 0.6.31-1 > ii libc-bin 2.13-38 > ii libc6 2.17-3 > ii libcups2 1.6.3-1 > ii libcupscgi11.6.3-1 > ii libcupsimage2 1.6.3-1 > ii libcupsmime1 1.6.3-1 > ii libcupsppdc1 1.6.3-1 > ii libgcc11:4.7.2-5 > ii libstdc++6 4.7.2-5 > ii libusb-1.0-0 2:1.0.11-1 > ii lsb-base 4.1+Debian12 > ii poppler-utils 0.18.4-5 > ii procps 1:3.3.3-2 > > Versions of packages cups recommends: > ii avahi-daemon 0.6.31-1 > ii colord 0.1.21-1 > ii foomatic-filters 4.0.17-1 > ii ghostscript-cups 9.05~dfsg-6.3 > ii printer-driver-gutenprint 5.2.9-1 > > Versions of packages cups suggests: > ii cups-bsd 1.6.3-1 > ii cups-pdf 2.6.1-6 > ii foomatic-db20120523-1 > ii hplip 3.12.6-3.1 > ii printer-driver-hpcups 3.12.6-3.1 > ii smbclient 2:3.6.16-2 > ii udev 175-7.1 > > -- debconf information: > * cupsys/raw-print: true > * cupsys/backend: lpd, socket, usb > > > -- > To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20131108095719.7064.57755.reportbug@buero1 > -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728444: Regarding the fintconfig/xpdf issue
Hi Michael, first of all, please don't strip me from the Cc - when you are answering to me send me a copy since I might not receive your message otherwise (like in this case here). > fontconfig was without pthreads for its lifetime prior to 2.11, so > there won't be any performance regressions. Granted pthreads disabled > may hold back a performance gain. >... > The logic of course is that it fixes a currently completely broken > xpdf package while retaining 2.10 and prior behavior with respect to > pthreads in this package. Have you actually looked at the fontconfig code you are changing? What you write here is simply wrong - we are not talking about a performance gain in 2.11, we are talking about how big the performance loss is compared to 2.10. fontconfig was without thread-safety primitives prior to 2.11, and 2.11 has many improvements in that area compared to 2.10. Generally, I'd expect that to cost some performance in 2.11 compared to 2.10. The relevant question for our discussion is how the performance differs between the pthreads code and the replacement code. So no, we are not talking about anything like "2.10 and prior behavior" in fontconfig - "2.10 and prior behavior" might be more like completely disabling thread-safety in fontconfig by defining FC_NO_MT. > There is currently no requirement for nmus to fix all known RC issues > known at the time. Maybe that idea should be suggested to > developers-reference? For the other RC bugs in fontconfig it would actually make sense to fix them in fontconfig - for the issue here the only thing that should be done in fontconfig is a Breaks on unfixed xpdf versions. > Anyway, I understand your viewpoint, but I would prefer the > maintainers to weigh in. Like I've already said, I'm completely happy > to delay, alter, or cancel based on their feedback. Please remove your NMU first. Abusing the fact that the maintainers seem to be a bit inactive to force your change into the archive would be highly unfair. Thanks in advance Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#725373: marked as done (python-tg.devtools should depends on python-babel and not python-pybabel)
Your message dated Tue, 12 Nov 2013 21:05:24 + with message-id and subject line Bug#725373: fixed in tg.devtools 2.0.2-4 has caused the Debian Bug report #725373, regarding python-tg.devtools should depends on python-babel and not python-pybabel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 725373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-tg.devtools Version: 2.0.2-3 Severity: serious Hi, I would like to remove python-pybabel from the archive, as this is a transitional package. Please switch to python-pybabel for your dependency. Cheers, Thomas Goirand (zigo) --- End Message --- --- Begin Message --- Source: tg.devtools Source-Version: 2.0.2-4 We believe that the bug you reported is fixed in the latest version of tg.devtools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 725...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Ablassmeier (supplier of updated tg.devtools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 12 Nov 2013 20:28:05 +0100 Source: tg.devtools Binary: python-tg.devtools Architecture: source all Version: 2.0.2-4 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Michael Ablassmeier Description: python-tg.devtools - developer tools for the TurboGears web framework Closes: 725373 Changes: tg.devtools (2.0.2-4) unstable; urgency=low . * QA upload * switch over dependency from python-pybabel to python-babel as requested by its maintainer (Closes: #725373) Checksums-Sha1: 15d6358c6befe21b55941be16c5eb4b409de188d 1522 tg.devtools_2.0.2-4.dsc 9b4886289c7cf07a95185af867b2233fa74528d1 4066 tg.devtools_2.0.2-4.debian.tar.gz f3ed2dd04ef89e824028084e29e268f52ff98865 109198 python-tg.devtools_2.0.2-4_all.deb Checksums-Sha256: 6b1f8fc2a6bd5a48b697a879d309a2a2ef9ff9938e6774180f10e6e39496c122 1522 tg.devtools_2.0.2-4.dsc ae786894cf2d5e9939a9a3ecdc5ee3a11cc22f619fa2be155085f9ade254b850 4066 tg.devtools_2.0.2-4.debian.tar.gz d49e48711b7c498953d9b236fd208092894bf1347bc81e76c6dc3037cafe6a24 109198 python-tg.devtools_2.0.2-4_all.deb Files: 4b263c45fb3fe007fbf5776b9a3607e6 1522 python optional tg.devtools_2.0.2-4.dsc c9f7b4e8adc789102672dc073fb72c4a 4066 python optional tg.devtools_2.0.2-4.debian.tar.gz 7821325fbca01ca16c0db774140a6a68 109198 python optional python-tg.devtools_2.0.2-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlKChiEACgkQEFV7g4B8rCVllgCfcvGkbbS3BeQXD4zMkDA4sQHU voUAnR533zmvc8dXTg4TJlnZFRMCu1z/ =alb/ -END PGP SIGNATURE End Message ---
Bug#724177: marked as done (upse: FTBFS: make[1]: *** No rule to make target `buildsys.mk'. Stop.)
Your message dated Tue, 12 Nov 2013 21:05:32 + with message-id and subject line Bug#724177: fixed in upse 1.0.0-2 has caused the Debian Bug report #724177, regarding upse: FTBFS: make[1]: *** No rule to make target `buildsys.mk'. Stop. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 724177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: upse Version: 1.0.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130922 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > dh clean >dh_testdir >dh_auto_clean > make[1]: Entering directory `/«PKGBUILDDIR»' > Makefile:3: buildsys.mk: No such file or directory > make[1]: *** No rule to make target `buildsys.mk'. Stop. > make[1]: Leaving directory `/«PKGBUILDDIR»' > dh_auto_clean: make -j1 distclean returned exit code 2 > make: *** [clean] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/09/22/upse_1.0.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: upse Source-Version: 1.0.0-2 We believe that the bug you reported is fixed in the latest version of upse, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 724...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Ablassmeier (supplier of updated upse package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 12 Nov 2013 21:10:40 +0100 Source: upse Binary: libupse2 libupse-dev upse123 Architecture: source amd64 Version: 1.0.0-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Michael Ablassmeier Description: libupse-dev - unix playstation sound emulator - library development files libupse2 - unix playstation sound emulator - library upse123- commandline player based on libupse Closes: 724177 Changes: upse (1.0.0-2) unstable; urgency=low . * QA Upload * Override dh_auto_clean, do not run make clean if buildsys.mk does not yet exist, fixes ftbfs (Closes: #724177) Checksums-Sha1: a64bfe9d14341621676154199a5ade3e8198b7bf 1147 upse_1.0.0-2.dsc 12283b8d7e9c0fd09f3aa32bd0a270f7518d0c56 4271 upse_1.0.0-2.debian.tar.gz 454b66e127e38365c694cdd1866b78339dc19e17 36490 libupse2_1.0.0-2_amd64.deb c66239b4b0d88e631fc4a3adcd78abc95261223d 4042 libupse-dev_1.0.0-2_amd64.deb fc846b1f4cced525e3025726fcf3520e8cc82a2f 7424 upse123_1.0.0-2_amd64.deb Checksums-Sha256: 265301db75263b4b2ba8b577bfc6c285e49526c25d39644a3ad2f4b648c2fdb6 1147 upse_1.0.0-2.dsc 9d119212d7c798dd7051c3639b527ee59d6731a57b3fb4afec7894be9d3a0fe9 4271 upse_1.0.0-2.debian.tar.gz 4c44521a3e81d01d8c7bfa2b3bbdeac427c362a30dff80242a179bd2b76a15d5 36490 libupse2_1.0.0-2_amd64.deb 6671a9588083e187a0a5cfb775132d7e8678731051d036a18addb5ebb01b6ced 4042 libupse-dev_1.0.0-2_amd64.deb 10254e0b213bf04a43e462bc9603e9b504d669a0bbb405d5e3267d69ef9fd66c 7424 upse123_1.0.0-2_amd64.deb Files: 328788c1cbf430a18cfca8abc0b24028 1147 sound extra upse_1.0.0-2.dsc b9dc337747202d102c08bc3e0b93aea0 4271 sound extra upse_1.0.0-2.debian.tar.gz aff4c9a6ec7342f73f5556d62267cfcc 36490 libs extra libupse2_1.0.0-2_amd64.deb e2021d0821114e250c20793cbc071215 4042 libdevel extra libupse-dev_1.0.0-2_amd64.deb 35838587f044bbc2fda626ff2cc73ef0 7424 sound extra upse123_1.0.0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlKCi+0ACgkQEFV7g4B8rCWowwCfXcQ0P98LuKM57SjQbcbmF6cg E6wAoPSQJdDo43BTkPKDaDIZ8nRJrrKs =5Bd8 -END PGP SIGNATURE End Message ---
Bug#724115: marked as done (hunspell: FTBFS: POD error)
Your message dated Tue, 12 Nov 2013 21:04:53 + with message-id and subject line Bug#724115: fixed in hunspell 1.3.2-5 has caused the Debian Bug report #724115, regarding hunspell: FTBFS: POD error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 724115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hunspell Version: 1.3.2-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130922 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory `/«PKGBUILDDIR»' > make[2]: Leaving directory `/«PKGBUILDDIR»' > make[1]: Leaving directory `/«PKGBUILDDIR»' > pod2man debian/ispellaff2myspell \ > > debian/ispellaff2myspell.1 > debian/ispellaff2myspell around line 445: Non-ASCII character seen before > =encoding in '$lowercase='a-z��';'. Assuming > ISO8859-1 > POD document had syntax errors at /usr/bin/pod2man line 71. > make: *** [build-stamp] Error 255 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/09/22/hunspell_1.3.2-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: hunspell Source-Version: 1.3.2-5 We believe that the bug you reported is fixed in the latest version of hunspell, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 724...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard (supplier of updated hunspell package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 12 Nov 2013 21:32:11 +0100 Source: hunspell Binary: libhunspell-dev libhunspell-1.3-0 libhunspell-1.3-0-dbg hunspell hunspell-tools Architecture: source amd64 Version: 1.3.2-5 Distribution: unstable Urgency: low Maintainer: Debian LibreOffice Maintainers Changed-By: Rene Engelhard Description: hunspell - spell checker and morphological analyzer (program) hunspell-tools - tools for hunspell libhunspell-1.3-0 - spell checker and morphological analyzer (shared library) libhunspell-1.3-0-dbg - spell checker and morphological analyzer (debug symbols) libhunspell-dev - spell checker and morphological analyzer (development) Closes: 724115 Changes: hunspell (1.3.2-5) unstable; urgency=low . * apply patch from Gregor Hermann, thanks - Fix "FTBFS: POD error": + update POD of ispellaff2myspell: . convert to UTF-8 and add =encoding directive . additionally fix a typo + call pod2man with --utf8 in debian/rules (Closes: #724115) Checksums-Sha1: 87fe1a9b7cdb6ec1a1b36c1d69774fd7f25710e7 2155 hunspell_1.3.2-5.dsc 8887482914a866c7dd56a48b48fdd0f4f5e05a7f 21763 hunspell_1.3.2-5.diff.gz 20939e26adce8086ecdbd9f4ce1e72bc3a5cfbdc 186056 libhunspell-dev_1.3.2-5_amd64.deb 9514e60b83cfe4577cbc0d7a5eb2d1a07fa2c66d 135052 libhunspell-1.3-0_1.3.2-5_amd64.deb e0ae8100538d07252ae27ae38f9c63a236d2c0aa 266520 libhunspell-1.3-0-dbg_1.3.2-5_amd64.deb afd75c353448f88bc64c4d2c59df8b3f717f5dee 71586 hunspell_1.3.2-5_amd64.deb b3fa6838aaace83bb58b64094d96ccc9b8603cf5 66572 hunspell-tools_1.3.2-5_amd64.deb Checksums-Sha256: c59a44e1654250798018851eb1d90780f27d39cd8efd45d451975d4f9fa71974 2155 hunspell_1.3.2-5.dsc f74aaf19e95cd5ccf1202f779c19e45b4c2c34f64229616eb3744f90861e8ac7 21763 hunspell_1.3.2-5.diff.gz 6a9694822ca23e00616df98b5ffbea8eed6e2a60b9a138aec1461d4dca0227f3 186056 libhunspell-dev_1.3.2-5_amd64.deb 8bd83823c8c1d914df161d6e22b5753fe2487f0b6feea2661e1b1fab7aec2998 135052 libhunspell-1.3-0_1.3.2-5_amd64.deb b6a4e05ac3d3bde3a9f475b433e27103ef11dc45722dea1f47f30af9cfcf262b 266520 libhunspell-1.3-0-dbg_1.3.2-5_am
Bug#713666: marked as done (gnustep-base: FTBFS: GSXML.m:983:38: error: dereferencing pointer to incomplete type)
Your message dated Tue, 12 Nov 2013 21:04:27 + with message-id and subject line Bug#713666: fixed in gnustep-base 1.22.1-4.2 has caused the Debian Bug report #713666, regarding gnustep-base: FTBFS: GSXML.m:983:38: error: dereferencing pointer to incomplete type to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnustep-base Version: 1.22.1-4.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc GSXML.m -c \ > -MMD -MP -Wall -Wdeclaration-after-statement -DNO_GNUSTEP=1 > -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 > -fno-strict-aliasing -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS > -pthread -fPIC -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 -fgnu-runtime > -fgnu-runtime -fconstant-string-class=NSConstantString -I../. -I../ > -I../../Headers -I. -I/usr/include/GNUstep -I/usr/local/include/GNUstep > -I/usr/local/include/GNUstep -I/usr/include/libxml2 -I/usr/include > -I/usr/local/include/GNUstep -I/usr/include/GNUstep \ > -o obj/Additions.obj/GSXML.m.o > GSXML.m: In function '-[GSXMLNode description]': > GSXML.m:983:38: error: dereferencing pointer to incomplete type >string = UTF8StrLen(buf->buffer->content, buf->buffer->use); > ^ > GSXML.m:983:60: error: dereferencing pointer to incomplete type >string = UTF8StrLen(buf->buffer->content, buf->buffer->use); > ^ > make[5]: *** [obj/Additions.obj/GSXML.m.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/gnustep-base_1.22.1-4.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: gnustep-base Source-Version: 1.22.1-4.2 We believe that the bug you reported is fixed in the latest version of gnustep-base, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated gnustep-base package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Nov 2013 19:57:52 +0100 Source: gnustep-base Binary: gnustep-base-common gnustep-base-runtime libgnustep-base1.22 libgnustep-base-dev libgnustep-base1.22-dbg gnustep-base-examples gnustep-base-doc Architecture: source all amd64 Version: 1.22.1-4.2 Distribution: unstable Urgency: low Maintainer: Debian GNUstep maintainers Changed-By: gregor herrmann Description: gnustep-base-common - GNUstep Base library - common files gnustep-base-doc - Documentation for the GNUstep Base Library gnustep-base-examples - Examples using the GNUstep Base Library gnustep-base-runtime - GNUstep Base library - daemons and tools libgnustep-base-dev - GNUstep Base header files and development libraries libgnustep-base1.22 - GNUstep Base library libgnustep-base1.22-dbg - GNUstep Base library - debugging symbols Closes: 713666 Changes: gnustep-base (1.22.1-4.2) unstable; urgency=low . * Non-maintainer upload. * Fix "FTBFS: GSXML.m:983:38: error: dereferencing pointer to incomplete type": add patch from Ubuntu / Benjamin Drung: - Backport upstream fix for recent libxml2. (Closes: #713666) Checksums-Sha1: fe79b0410b85a4b0fa9e8b2f390e6f26a582b8fb 2615 gnustep-base_1.22.1-4.2.dsc 69186046c02069e3eaae2ad58f50bf2d365895f1 142413 gnustep-base_1.22.1-4.2.diff.gz 55c9a3cadcaed49b98d3402557096d9f5f5b042c 194040 gnustep-base-c
Bug#729333: torque: CVE-2013-4495
Hi Just an information on why I have tagged the bug already pending: I have prepared the packages for squeeze-security and wheezy-wheezy with a patch provided by upstream to backport for 2.4. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720816: openscenegraph: FTBFS with libav9: FFmpegDecoder.cpp:282:76: error: 'url_feof' was not declared in this scope
2013/11/12 Rebecca N. Palmer : >> I now see that these [reverse dependencies] >> >> packages are 'sid only', > > They're sid-only because this transition stalled for long enough for its > FTBFS bugs to trigger the autoremover. Is that an autoremover bug or a > feature? It is a feature, removes packages which are not fit for release for one reason or another, so helps to not delay the release of ~17 thousand source packages (or whatever number is there in the archive at the moment) for the sake of a few. When things are fixed in OSG (in this case) or other problems which kicked packages out of testing, they will happily migrate to testing automatically as long as they are fine in unstable, AFAICT. And the freeze is only on the 5th of November of next year, so there's plenty of time for more fixes and additional breakages. >>> Since the transition requested already mentions libopenscenegraph100, >>> but 3.2.1 is not released, I think that it's actually more risky (or >>> prone to more delays) if to tie the current transition to these future >>> ones of OSG. > > The 99->100 soname bump is 3.2.0rc->3.2.0 not 3.2.0->3.2.1 and appears to be > a standard OSG release procedure (possibly intended as a "don't use > pre-releases in production" marker) rather than a real change > (https://github.com/openscenegraph/osg/commits/OpenSceneGraph-3.2?page=2, > scroll down to Jul 23), so I wouldn't _expect_ further breakage, but I agree > it's always possible. (E.g. building with --as-needed, which you do (as > recommended), is currently unreliable on ia64: #718047) Further breakage is always possible, and even probable in the buildds of some architectures lately, or that's my recent experience anyway. As for the 99->100, I meant in previous emails to fix the FTBFS bug with the current source in unstable, not even updating to 3.2.0 / SOVERSION 100. Doing otherwise means that the packages goes through the NEW queue and this is delayed for weeks/months typically. But maybe Alberto (who follows closely upstream) will have more information or other opinion, or maybe 3.2.1 is released as we discuss it. We will discuss it and come up with a plan. Cheers. -- Manuel A. Fernandez Montecelo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712140: check: Missing dependency for static linking (libpthread)
Hi On 2013-11-11 18:49:01, Laurent Bigonville wrote: > > > OK for what I understood, the A(C)X_PTHREAD is setting the -pthread > > > flag (not the absence of "l") in PTHREAD_CFLAGS and relies on gcc > > > to do the correct thing(tm) when this flag is set, this works the > > > cases where the CFLAGS are also passed at the linking time (autofoo > > > are doing that). > > > > > > If a pkg that link against check FTBFS this need to be checked. > > > > > > I feel that this bug should be fixed now and could be closed, all > > > rdeps seems to compile now > > > > I don't think this bug can be closed. pkg-config check --libs still > > doesn't include -pthread which it should. -pthread needs to in both > > Cflags and Libs in check's pkgconfig file. > > The ax_pthread macro upstream thinks otherwise, see: > https://savannah.gnu.org/patch/?8081 > > But I can admit, I've not seen a lot of projects doing it that way. > > If I understood correctly, -pthread should automatically make gcc link > against libpthread. So as said the CFLAGS should also be passed to gcc > at linking time, in that case explicit -lpthread flag seems redundant. Of course, passing -pthread to gcc during link time does the right thing. I would still expect to get -pthread (not -lpthread) from `pkg-config check --libs`. My understanding of --libs is that it's supposed to give the required linking flags. In the case of check, -pthread is required while linking, but is not included in the output of --libs. Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#724115: hunspell: FTBFS: POD error
On Tue, 12 Nov 2013 19:54:04 +0100, Agustin Martin wrote: > > > Note that you are changing way more things that needed, including strings > > > that are explicitly in a given charset, which is wrong. > > That was on purpose ... > I mean that it included parts of the code, making it no longer work as > expected (yes, that is about old features). If script is changed to UTF-8 > these unibyte strings need to be rewritten with escapes to stay unibyte > (hope this will work), not changed to UTF8. Oh, now I understand, thanks. > > Anyway, that's why I prefer to have POD in UTF-8 and call pod2man > > with --utf8. > Thanks for the info. I later noticed pod2man misbehavior about this, but I > could not try harder. Also tried to unsuccessfully use POD escapes to > make it more portable. No luck. If you need a real expert here, Russ is the one to ask. I also never groked all the details. > I will have a look at this (I once wrote ispellaff2myspell). Now I think the > best is to change script to UTF8, but keep strings in code as escaped octal. > Or rewrite that part. > Let me think about this. Hope to find time tomorrow. Sure, whatever suits you :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Police: Wrapped Around Your Finger signature.asc Description: Digital signature
Bug#724115: hunspell: FTBFS: POD error
Hi Agustin, On Tue, Nov 12, 2013 at 07:54:04PM +0100, Agustin Martin wrote: > On Tue, Nov 12, 2013 at 07:00:10PM +0100, gregor herrmann wrote: > > On Tue, 12 Nov 2013 18:34:52 +0100, Agustin Martin wrote: > > > > > > > here's a patch for this issue. > > > Note that you are changing way more things that needed, including strings > > > that are explicitly in a given charset, which is wrong. > > > > That was on purpose ... > > I mean that it included parts of the code, making it no longer work as > expected (yes, that is about old features). If script is changed to UTF-8 > these unibyte strings need to be rewritten with escapes to stay unibyte > (hope this will work), not changed to UTF8. [...] > I will have a look at this (I once wrote ispellaff2myspell). Now I think the > best is to change script to UTF8, but keep strings in code as escaped octal. > Or rewrite that part. > > Let me think about this. Hope to find time tomorrow. Oops, too late. Just added the patch as I saw the patch and did it before starting to read mail. My bad. Feel free to come up with a patch based on -5 and I'll happily add it, though. Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728361: Bug#729134: [Pkg-systemd-maintainers] Bug#729134: libpam-systemd wreaks havoc
On Tue, 2013-11-12 at 20:49 +0100, Julien Puydt wrote: > I don't understand. Lightdm is also involved in me not getting to > mount/unmount USB sticks when I'm in a session? Did you use lightdm or not? If yes, then it's involved. If not, then it's not. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#720816: openscenegraph: FTBFS with libav9: FFmpegDecoder.cpp:282:76: error: 'url_feof' was not declared in this scope
2013/11/12 Steven Chamberlain : >> The current cause of this blockage is actually >> problems/delays in MIPS toolchain and bad timing. > > If you mean the delayed build of openscenegraph on mips, happening after > libav9 transition started, I'm not sure that makes a difference because > it would be stuck until rdepends are ready (and they're still not). > libav9 transition started only a few days later so openscenegraph would > have failed on *all* arches when binNMUd? That's correct, I was trying to set the matter in perspective, and why the breakage occured in OSG without us being notified by libav people. I uploaded the last OSG package on ~8th of August, around which date most buildds built it successfully. mips didn't try to build until the 26th, when it failed to build for other reasons (buildd fault, not the package), and the 29th when it failed to build due to the new libav9 being there (it was uploaded in mid August). We didn't have any warning in the BTS or by email of the libav9 affecting OSG, excep possibly the PTS, cannot remember. Even if we had in the PTS, certainly nobody rebuilt OSG against the newer libav9 and tell us that it would break, offering help or suggesting patches (before the breakage). So I only noticed this by the end of August with #720816 after a archive-wide rebuild of all packages in sid (amd64). Granted, the archive is getting big and some of these packages are big, but still we did that for our upgrade of OSG with our rdepends; and I built not long ago ~450 pages with rdepends to libsdl to check for possible breakages of important changes. Which bring us to the following point: >> 5) So as a summary and in short, having an open transition process is >> not going to speed-up the transition [...] >> (libcitygml didn't respond or upload for more than 3 months, for >> example). > > Conversely, that's why I suggested having a tracker; having more eyes > on the problem and making it easier to see what needs to happen. So even when transition trackers are set up, as it was the case with libav9 (just picking the example at hand, nothing particularly bad), this doesn't help to avoid breakages, and libav maintainers were less pro-active than us in warning rdepends. Informing rdepends, sending patches and eventually NMUing if feasible and maintainers inactive or removing from the archive (if the packages are hopeless) are the things that can move things forward. So I still don't think that having a tracker is not useful in our case (mostly bureaucracy and a waste of time, IMO). >> Since the transition requested already mentions libopenscenegraph100, >> but 3.2.1 is not released, I think that it's actually more risky (or >> prone to more delays) if to tie the current transition to these future >> ones of OSG. > > ... the tracker will need updating with whatever you decide to aim for > (99 or 100). I would think 99 is the quickest and safest resolution to > the libav9 tangle. As Rebecca said, it implies another round of binNMUs > as soon as 3.2.1 is uploaded. But IMHO that will be much easier and > less urgent if nothing else is waiting on it by then. > > Are you decided that you are aiming for libopenscenegraph99 to migrate > first? A change in package names, such as libopenscenegraph99->100 or libopenthreads to whatever SOVERSION, will force the package to go through the new queue, so it's not the speediest of the routes. OTOH there're many other packages, and much more important than OSG, still pending to be built against libav9, so I don't think that this is so urgent though, and also depends on what happens with 3.2.1. We will discuss it and see what to do. Cheers. -- Manuel A. Fernandez Montecelo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 724177
Processing commands for cont...@bugs.debian.org: > tags 724177 + pending Bug #724177 [src:upse] upse: FTBFS: make[1]: *** No rule to make target `buildsys.mk'. Stop. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 724177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724731: marked as done ([gdm3] gdm does not start properly, cannot login via gdm)
Your message dated Tue, 12 Nov 2013 19:48:39 + with message-id and subject line Bug#724731: fixed in gdm3 3.8.4-4 has caused the Debian Bug report #724731, regarding [gdm3] gdm does not start properly, cannot login via gdm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 724731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdm3 Version: 3.8.4-1 Severity: grave Hi, I updated to 3.8 today, and after restarting the gdm3, I cannot login anymore. Gdm3 somehow starts (graphics are visible) but the login field is missing. :0-slave.log says: -- ** (gdm-simple-slave:19770): WARNING **: Couldn't connect to system bus: Verbindung ist gescheitert:Datei oder Verzeichnis nicht gefunden (gdm-simple-slave:19770): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed :0-greeter.log has bazillions of lines like: (gnome-settings-daemon:19268): dconf-CRITICAL **: unable to create directory '/run/user/1000/dconf': Keine Berechtigung. dconf will not work properly. Switching to terminal and starting via startx works properly. This might be related to #681282. Thanks for packaging Gnome3, I'm sure keeping track of all the transitions is a hell of a job! Cheers, Bastian --- System information. --- Architecture: amd64 Kernel: Linux 3.10-3-amd64 Debian Release: jessie/sid 500 unstableftp.de.debian.org 500 stable repository.spotify.com 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+- libaccountsservice0(>= 0.6.8) | 0.6.34-2 libatk1.0-0 (>= 1.12.4) | 2.10.0-2 libaudit1(>= 1:2.2.1) | 1:2.3.2-2 libc6 (>= 2.14) | 2.17-93 libcairo-gobject2 (>= 1.10.0) | 1.12.16-2 libcairo2 (>= 1.2.4) | 1.12.16-2 libcanberra-gtk3-0 (>= 0.25) | 0.30-2 libcanberra0 (>= 0.2) | 0.30-2 libgdk-pixbuf2.0-0(>= 2.22.0) | 2.28.2-1 libgdm1 (= 3.8.4-1) | 3.8.4-1 libglib2.0-0 (>= 2.35.0) | 2.36.4-1 libgtk-3-0 (>= 3.0.0) | 3.8.4-1 libpam0g(>= 0.99.7.1) | 1.1.3-9 libpango-1.0-0(>= 1.14.0) | 1.32.5-5+b1 libpangocairo-1.0-0 (>= 1.14.0) | 1.32.5-5+b1 libselinux1 (>= 1.32) | 2.1.13-2 libwrap0 (>= 7.6-4~) | 7.6.q-24 libx11-6 | 2:1.6.1-1 libxau6 | 1:1.0.8-1 libxdmcp6 | 1:1.1.1-1 libxrandr2(>= 2:1.2.99.3) | 2:1.4.1-1 dconf-gsettings-backend (>= 0.12.1-2) | 0.16.1-1 debconf (>= 0.5) | 1.5.51 OR debconf-2.0 | gir1.2-gdm3 (= 3.8.4-1) | 3.8.4-1 adduser | 3.113+nmu3 libpam-modules(>= 0.72-1) | 1.1.3-9 libpam-runtime (>= 0.76-13.1) | 1.1.3-9 gnome-session-bin(>= 3.6) | 3.8.2.1-1 gnome-settings-daemon(>= 3.2) | 3.8.5-1 gnome-shell | 3.8.4-1 policykit-1-gnome | 0.105-2 upower| 0.9.21-3 gnome-session | 3.8.2.1-1 OR x-session-manager | OR x-window-manager | OR x-terminal-emulator | lsb-base (>= 3.2-14) | 4.1+Debian12 librsvg2-common | 2.36.4-2 accountsservice (>= 0.6.12) | 0.6.34-2 gsettings-desktop-schemas | 3.8.0-1 libglib2.0-bin(>= 2.35.0) | 2.36.4-1 dconf-cli (>= 0.12.1-2) | 0.16.1-1 x11-common (>= 1:7.6+11) | 1:7.7+3 x11-xserver-utils | 7.7+1 Recommends (Version) | Installed -+-=== zenity | 3.8.0-1 xserver-xephyr | 2:1.14.3-3 x11-xkb-utils| 7.7~1 xserver-x
Bug#728361: Bug#729134: [Pkg-systemd-maintainers] Bug#729134: libpam-systemd wreaks havoc
Le 12/11/2013 20:40, Yves-Alexis Perez a écrit : > On Tue, 2013-11-12 at 20:37 +0100, Julien Puydt wrote: >> Le 12/11/2013 09:51, Yves-Alexis Perez a écrit : >>> On Tue, 2013-11-12 at 08:08 +0100, Julien Puydt wrote: Notice that you focus on lightdm but that removing libpam-systemd solved other problems. >>> >>> Could you point to those other problems where lightdm was not involved >>> at all? >> >> The fact that I couldn't mount/unmount USB stick must fit that description. > > So it happened again with another display manager? Which one? Or with > lightdm before 1.8? I don't understand. Lightdm is also involved in me not getting to mount/unmount USB sticks when I'm in a session? Snark on #debian-science -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728361: Bug#729134: [Pkg-systemd-maintainers] Bug#729134: libpam-systemd wreaks havoc
On Tue, 2013-11-12 at 20:37 +0100, Julien Puydt wrote: > Le 12/11/2013 09:51, Yves-Alexis Perez a écrit : > > On Tue, 2013-11-12 at 08:08 +0100, Julien Puydt wrote: > >> Notice that you focus on lightdm but that removing libpam-systemd > >> solved > >> other problems. > > > > Could you point to those other problems where lightdm was not involved > > at all? > > The fact that I couldn't mount/unmount USB stick must fit that description. So it happened again with another display manager? Which one? Or with lightdm before 1.8? Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#728361: Bug#729134: [Pkg-systemd-maintainers] Bug#729134: libpam-systemd wreaks havoc
Le 12/11/2013 09:51, Yves-Alexis Perez a écrit : > On Tue, 2013-11-12 at 08:08 +0100, Julien Puydt wrote: >> Notice that you focus on lightdm but that removing libpam-systemd >> solved >> other problems. > > Could you point to those other problems where lightdm was not involved > at all? The fact that I couldn't mount/unmount USB stick must fit that description. >> I have no clue how to reproduce it... I only have the system where I had >> problems and solved them. > > Not sure about GNOME, but on an Xfce systems, it should just be a matter > of install xfce4 and lightdm (with recommends), check that > ck-list-session indeed list a session, check that in the logout session > windows the various options (suspend/hibernate/shutdown/restart) are not > greyed out. Then install libpam-systemd and check that they are now > greyed out and that ck-list-session doesn't list anything. Uh, yes, I can just re-break my system and re-unbreak it... I'll try if I find the time... Snark on #debian-science -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: python-django-south: diff for NMU version 0.7.5-1.1
Processing commands for cont...@bugs.debian.org: > tags 729412 + pending Bug #729412 [python-django-south] python-django-south: incompatibilities with Django 1.6 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 729412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729412: python-django-south: diff for NMU version 0.7.5-1.1
tags 729412 + pending thanks Dear maintainer, I've prepared an NMU for python-django-south (versioned as 0.7.5-1.1) and uploaded it to DELAYED/7. Please feel free to cancel it if you would rather upload a fixed version. Regards. -- Luke Faraone;; Debian & Ubuntu Developer; Sugar Labs, Systems lfaraone on irc.[freenode,oftc].net -- http://luke.faraone.cc PGP fprint: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 reverted: --- python-django-south-0.7.5/South.egg-info/PKG-INFO.debdiff +++ python-django-south-0.7.5.orig/South.egg-info/PKG-INFO.debdiff @@ -1,19 +0,0 @@ -Metadata-Version: 1.1 -Name: South -Version: 0.7.4 -Summary: South: Migrations for Django -Home-page: http://south.aeracode.org/ -Author: Andrew Godwin & Andy McCurdy -Author-email: so...@aeracode.org -License: UNKNOWN -Download-URL: http://south.aeracode.org/wiki/Download -Description: South is an intelligent database migrations library for the Django web framework. It is database-independent and DVCS-friendly, as well as a whole host of other features. -Platform: UNKNOWN -Classifier: Development Status :: 5 - Production/Stable -Classifier: Framework :: Django -Classifier: Intended Audience :: Developers -Classifier: Intended Audience :: System Administrators -Classifier: Intended Audience :: System Administrators -Classifier: License :: OSI Approved :: Apache Software License -Classifier: Operating System :: OS Independent -Classifier: Topic :: Software Development reverted: --- python-django-south-0.7.5/South.egg-info/top_level.txt.debdiff +++ python-django-south-0.7.5.orig/South.egg-info/top_level.txt.debdiff @@ -1 +0,0 @@ -south reverted: --- python-django-south-0.7.5/South.egg-info/SOURCES.txt.debdiff +++ python-django-south-0.7.5.orig/South.egg-info/SOURCES.txt.debdiff @@ -1,117 +0,0 @@ -README -setup.py -South.egg-info/PKG-INFO -South.egg-info/SOURCES.txt -South.egg-info/dependency_links.txt -South.egg-info/top_level.txt -south/__init__.py -south/exceptions.py -south/logger.py -south/models.py -south/modelsinspector.py -south/orm.py -south/signals.py -south/v2.py -south/creator/__init__.py -south/creator/actions.py -south/creator/changes.py -south/creator/freezer.py -south/db/__init__.py -south/db/firebird.py -south/db/generic.py -south/db/mysql.py -south/db/oracle.py -south/db/postgresql_psycopg2.py -south/db/sqlite3.py -south/db/sql_server/__init__.py -south/db/sql_server/pyodbc.py -south/hacks/__init__.py -south/hacks/django_1_0.py -south/introspection_plugins/__init__.py -south/introspection_plugins/annoying_autoonetoone.py -south/introspection_plugins/django_audit_log.py -south/introspection_plugins/django_objectpermissions.py -south/introspection_plugins/django_tagging.py -south/introspection_plugins/django_taggit.py -south/introspection_plugins/django_timezones.py -south/introspection_plugins/geodjango.py -south/management/__init__.py -south/management/commands/__init__.py -south/management/commands/convert_to_south.py -south/management/commands/datamigration.py -south/management/commands/graphmigrations.py -south/management/commands/migrate.py -south/management/commands/migrationcheck.py -south/management/commands/schemamigration.py -south/management/commands/startmigration.py -south/management/commands/syncdb.py -south/management/commands/test.py -south/management/commands/testserver.py -south/migration/__init__.py -south/migration/base.py -south/migration/migrators.py -south/migration/utils.py -south/tests/__init__.py -south/tests/autodetection.py -south/tests/db.py -south/tests/db_mysql.py -south/tests/freezer.py -south/tests/inspector.py -south/tests/logger.py -south/tests/logic.py -south/tests/brokenapp/__init__.py -south/tests/brokenapp/models.py -south/tests/brokenapp/migrations/0001_depends_on_unmigrated.py -south/tests/brokenapp/migrations/0002_depends_on_unknown.py -south/tests/brokenapp/migrations/0003_depends_on_higher.py -south/tests/brokenapp/migrations/0004_higher.py -south/tests/brokenapp/migrations/__init__.py -south/tests/circular_a/__init__.py -south/tests/circular_a/models.py -south/tests/circular_a/migrations/0001_first.py -south/tests/circular_a/migrations/__init__.py -south/tests/circular_b/__init__.py -south/tests/circular_b/models.py -south/tests/circular_b/migrations/0001_first.py -south/tests/circular_b/migrations/__init__.py -south/tests/deps_a/__init__.py -south/tests/deps_a/models.py -south/tests/deps_a/migrations/0001_a.py -south/tests/deps_a/migrations/0002_a.py -south/tests/deps_a/migrations/0003_a.py -south/tests/deps_a/migrations/0004_a.py -south/tests/deps_a/migrations/0005_a.py -south/tests/deps_a/migrations/__init__.py -south/tests/deps_b/__init__.py -south/tests/deps_b/models.py -south/tests/deps_b/migrations/0001_b.py -south/tests/deps_b/migrations/0002_b.py -south/tests/deps_b/migrations/0003_b.py -south/tests/deps_b/migrations/0004_b.py -south/tests/deps_b/migrations/0005_b.py -south/tests/deps_b/migrations/__init__.py -south/tests/deps_c/__init__.py -south/tests/deps_c/models.py
Bug#729416: marked as done (ImportError: No module named pkg_resources)
Your message dated Tue, 12 Nov 2013 18:48:22 + with message-id and subject line Bug#729416: fixed in youtube-dl 2013.11.11-2 has caused the Debian Bug report #729416, regarding ImportError: No module named pkg_resources to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 729416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: youtube-dl Version: 2013.11.11-1 Severity: grave Attempting to download any youtube video produces: Traceback (most recent call last): File "/usr/bin/youtube-dl", line 5, in from pkg_resources import load_entry_point ImportError: No module named pkg_resources - Josh Triplett -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages youtube-dl depends on: ii python 2.7.5-5 Versions of packages youtube-dl recommends: ii libav-tools 6:9.10-1 ii mplayer 2:1.0~rc4.dfsg1+svn34540-1+b2 ii rtmpdump 2.4+20121230.gitdf6c518-1 youtube-dl suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: youtube-dl Source-Version: 2013.11.11-2 We believe that the bug you reported is fixed in the latest version of youtube-dl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 729...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rogério Brito (supplier of updated youtube-dl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 12 Nov 2013 16:34:16 -0200 Source: youtube-dl Binary: youtube-dl Architecture: source all Version: 2013.11.11-2 Distribution: unstable Urgency: low Maintainer: Rogério Brito Changed-By: Rogério Brito Description: youtube-dl - downloader of videos from YouTube and other sites Closes: 729416 Changes: youtube-dl (2013.11.11-2) unstable; urgency=low . * debian/control: Add dependency on python-pkg-resources. Closes: #729416. Thanks Josh Triplett. Checksums-Sha1: 3a2cccb7d1423ee64037b070f63a2fb2f4c8f941 1305 youtube-dl_2013.11.11-2.dsc 1ec530e32d3db2c1f2ad86c4bb5062f58e1a3ca2 13984 youtube-dl_2013.11.11-2.debian.tar.gz b04078e562a1a74869b881c281a81ac9f37d306e 175808 youtube-dl_2013.11.11-2_all.deb Checksums-Sha256: eb273166a344c67802c5e7675207ad11461cfffeb74429253e7296e0bbb5cd2b 1305 youtube-dl_2013.11.11-2.dsc 901e4911bb9cde3a6c752e988acb8d026ae80bd062f130bcae3262ac10f0d8d0 13984 youtube-dl_2013.11.11-2.debian.tar.gz d3de0425650d27006b054e39139c26c062492d660941f90b93d1b9b0e5d73c36 175808 youtube-dl_2013.11.11-2_all.deb Files: cb69d1de8fb4909d668f9b2427b0847a 1305 web extra youtube-dl_2013.11.11-2.dsc cd54e80d7e612051fb9beb857cf8f0ed 13984 web extra youtube-dl_2013.11.11-2.debian.tar.gz fc228cfb2c0546a2310c2a8d6a3f91fd 175808 web extra youtube-dl_2013.11.11-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlKCdSMACgkQCFqbMnwsrrg9BgCdHkKxv9aMsjqsdgzqW3xMhMHi MuUAn0+GC+hDqg2vX4U4mm85YEVcpncL =Eocl -END PGP SIGNATURE End Message ---
Bug#724115: hunspell: FTBFS: POD error
On Tue, Nov 12, 2013 at 07:00:10PM +0100, gregor herrmann wrote: > On Tue, 12 Nov 2013 18:34:52 +0100, Agustin Martin wrote: > > > > > here's a patch for this issue. > > Note that you are changing way more things that needed, including strings > > that are explicitly in a given charset, which is wrong. > > That was on purpose ... I mean that it included parts of the code, making it no longer work as expected (yes, that is about old features). If script is changed to UTF-8 these unibyte strings need to be rewritten with escapes to stay unibyte (hope this will work), not changed to UTF8. > > > This can be fixed in a simpler way by declaring charset, see attached patch, > > Right, for the bug itself "=encoding ISO8859-1" is enough. > My experience is that pod2man with latin1 is not the best option, > since it tends to transliterate stuff to ascii. > > Let's try: > > #v+ > % cat latin1.pod > =encoding ISO-8859-1 > > some nice Ümläüts > #v- > > % pod2man latin1.pod | grep "some nice" > some nice U\*:mla\*:u\*:ts > > Not bad; but when I run > % pod2man latin1.pod | grep "some nice" | man -l - > I get > some nice Umlauts > in the pager. Maybe because this is in an UTF-8 environment? Or > something with the pager? > > Anyway, that's why I prefer to have POD in UTF-8 and call pod2man > with --utf8. Thanks for the info. I later noticed pod2man misbehavior about this, but I could not try harder. Also tried to unsuccessfully use POD escapes to make it more portable. No luck. I will have a look at this (I once wrote ispellaff2myspell). Now I think the best is to change script to UTF8, but keep strings in code as escaped octal. Or rewrite that part. Let me think about this. Hope to find time tomorrow. Thanks for your feedback. -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729416: ImportError: No module named pkg_resources
Hi, Josh.
On Tue, Nov 12, 2013 at 3:19 PM, Josh Triplett wrote:
> Traceback (most recent call last):
> File "/usr/bin/youtube-dl", line 5, in
> from pkg_resources import load_entry_point
> ImportError: No module named pkg_resources
OK. Can you install python-pkg-resources in the mean time? I will
create another upload with this new dependency.
Of course, I didn't notice this because I already had this package
installed for other programs of my own use.
Thanks,
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#724085: myspell: FTBFS: POD errors
On Fri, Nov 08, 2013 at 09:57:47PM +0100, gregor herrmann wrote:
> Control: tag -1 + patch
>
> On Sun, 22 Sep 2013 20:55:32 +0200, David Suárez wrote:
>
> > > pod2man debian/myspell-tools/usr/bin/ispellaff2myspell \
> > > > debian/myspell-tools/usr/share/man/man1/ispellaff2myspell.1
> > > debian/myspell-tools/usr/bin/ispellaff2myspell around line 445: Non-ASCII
> > > character seen before =encoding in
> > > '$lowercase='a-z??';'. Assuming ISO8859-1
> > > POD document had syntax errors at /usr/bin/pod2man line 71.
> > > make: *** [install] Error 255
>
> Hi Rene,
>
> here's a patch that fixes this bug.
Hi, Rene and Gregor,
Please find attached the hunspell patch fixing this issue ported to myspell.
Regards,
--
Agustin
diff --git a/debian/changelog b/debian/changelog
index b8546ca..f6270df 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+myspell (1:3.0+pre3.1-25) unstable; urgency=low
+
+ [gregor herrmann]
+ * debian/patches/03_add_ispellaff2myspell.dpatch: Fix typo.
+
+ [Agustin Martin]
+ * debian/patches/03_add_ispellaff2myspell.dpatch:
+- Declare encoding to fix "FTBFS: POD error" (Closes: #724085).
+- Remove ancient CVS string.
+
+ --
+
myspell (1:3.0+pre3.1-24) unstable; urgency=low
* remove historical hardocing of sparc-linux-gnu-g{cc,++} which breaks
diff --git a/debian/patches/03_add_ispellaff2myspell.dpatch b/debian/patches/03_add_ispellaff2myspell.dpatch
old mode 100644
new mode 100755
index 0058d8b..d56922f
--- a/debian/patches/03_add_ispellaff2myspell.dpatch
+++ b/debian/patches/03_add_ispellaff2myspell.dpatch
@@ -23,13 +23,12 @@ esac
exit 0
@DPATCH@
-diff -urNad --exclude=CVS --exclude=.svn /dev/null ./utils/ispellaff2myspell
/dev/null 1970-01-01 01:00:00.0 +0100
-+++ ./utils/ispellaff2myspell 2005-07-05 19:34:44.185649736 +0200
-@@ -0,0 +1,472 @@
+diff -urNad '--exclude=CVS' '--exclude=.svn' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' myspell~/utils/ispellaff2myspell myspell/utils/ispellaff2myspell
+--- myspell~/utils/ispellaff2myspell 1970-01-01 01:00:00.0 +0100
myspell/utils/ispellaff2myspell 2013-11-12 18:11:56.0 +0100
+@@ -0,0 +1,473 @@
+#!/usr/bin/perl -w
+# -*- coding: iso-8859-1 -*-
-+# $Id: ispellaff2myspell,v 1.29 2005/07/04 12:21:55 agmartin Exp $
+#
+# (C) 2002-2005 Agustin Martin Domingo
+#
@@ -144,7 +143,7 @@ diff -urNad --exclude=CVS --exclude=.svn /dev/null ./utils/ispellaff2myspell
+ if ( not $lowercase and not $uppercase ){
+ die "Unsupported charset [$charset]
+
-+use explicitely --lowercase=string and --uppercase=string
++use explicitly --lowercase=string and --uppercase=string
+options. Remember that both string must match exactly, but
+case changed.
+";
@@ -356,6 +355,8 @@ diff -urNad --exclude=CVS --exclude=.svn /dev/null ./utils/ispellaff2myspell
+
+__END__
+
++=encoding ISO8859-1
++
+=head1 NAME
+
+B - A program to convert ispell affix tables to myspell format.
@@ -431,8 +432,8 @@ diff -urNad --exclude=CVS --exclude=.svn /dev/null ./utils/ispellaff2myspell
+You will need a call to -e for each flag type, e.g.,
+B<-e "" -e "~"> (or B<-e '\\' -e '~\\'>).
+
-+When a prefix is explicitely set, the default value (anything starting by B<\>)
-+is disabled and you need to enable it explicitely as in previous example.
++When a prefix is explicitly set, the default value (anything starting by B<\>)
++is disabled and you need to enable it explicitly as in previous example.
+
+=item B<--lowercase=s>
+
Bug#724115: hunspell: FTBFS: POD error
On Tue, 12 Nov 2013 18:34:52 +0100, Agustin Martin wrote: > > > here's a patch for this issue. > Note that you are changing way more things that needed, including strings > that are explicitly in a given charset, which is wrong. That was on purpose ... > This can be fixed in a simpler way by declaring charset, see attached patch, Right, for the bug itself "=encoding ISO8859-1" is enough. My experience is that pod2man with latin1 is not the best option, since it tends to transliterate stuff to ascii. Let's try: #v+ % cat latin1.pod =encoding ISO-8859-1 some nice Ümläüts #v- % pod2man latin1.pod | grep "some nice" some nice U\*:mla\*:u\*:ts Not bad; but when I run % pod2man latin1.pod | grep "some nice" | man -l - I get some nice Umlauts in the pager. Maybe because this is in an UTF-8 environment? Or something with the pager? Anyway, that's why I prefer to have POD in UTF-8 and call pod2man with --utf8. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Joan Baez: Fountain Of Sorrow signature.asc Description: Digital signature
Bug#724115: hunspell: FTBFS: POD error
On Tue, Nov 12, 2013 at 04:32:49PM +0100, gregor herrmann wrote:
> On Fri, 08 Nov 2013 22:06:51 +0100, gregor herrmann wrote:
>
> > here's a patch for this issue.
Note that you are changing way more things that needed, including strings
that are explicitly in a given charset, which is wrong.
This can be fixed in a simpler way by declaring charset, see attached patch,
also including your typo fix and removal of ancient CVS string.
Regards,
--
Agustin
diff --git a/debian/changelog b/debian/changelog
index fa5d849..f91578e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+hunspell (1.3.2-5) unstable; urgency=low
+
+ [gregor herrmann]
+ * debian/ispellaff2myspell: Fix typo.
+
+ [Agustin Martin]
+ * debian/ispellaff2myspell:
+- Declare encoding to fix "FTBFS: POD error" (Closes: #724115).
+- Remove ancient CVS string.
+
+ --
+
hunspell (1.3.2-4) unstable; urgency=low
* upload to unstable
diff --git a/debian/ispellaff2myspell b/debian/ispellaff2myspell
index 6f2e79e..0cf9e51 100644
--- a/debian/ispellaff2myspell
+++ b/debian/ispellaff2myspell
@@ -1,6 +1,5 @@
#!/usr/bin/perl -w
# -*- coding: iso-8859-1 -*-
-# $Id: ispellaff2myspell,v 1.29 2005/07/04 12:21:55 agmartin Exp $
#
# (C) 2002-2005 Agustin Martin Domingo
#
@@ -115,7 +114,7 @@ sub mylc{
if ( not $lowercase and not $uppercase ){
die "Unsupported charset [$charset]
-use explicitely --lowercase=string and --uppercase=string
+use explicitly --lowercase=string and --uppercase=string
options. Remember that both string must match exactly, but
case changed.
";
@@ -327,6 +326,8 @@ if ( $replacements ){
__END__
+=encoding ISO8859-1
+
=head1 NAME
B - A program to convert ispell affix tables to myspell format.
@@ -402,8 +403,8 @@ flags and pass them unmodified.
You will need a call to -e for each flag type, e.g.,
B<-e "" -e "~"> (or B<-e '\\' -e '~\\'>).
-When a prefix is explicitely set, the default value (anything starting by B<\>)
-is disabled and you need to enable it explicitely as in previous example.
+When a prefix is explicitly set, the default value (anything starting by B<\>)
+is disabled and you need to enable it explicitly as in previous example.
=item B<--lowercase=s>
Bug#729416: ImportError: No module named pkg_resources
Package: youtube-dl Version: 2013.11.11-1 Severity: grave Attempting to download any youtube video produces: Traceback (most recent call last): File "/usr/bin/youtube-dl", line 5, in from pkg_resources import load_entry_point ImportError: No module named pkg_resources - Josh Triplett -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages youtube-dl depends on: ii python 2.7.5-5 Versions of packages youtube-dl recommends: ii libav-tools 6:9.10-1 ii mplayer 2:1.0~rc4.dfsg1+svn34540-1+b2 ii rtmpdump 2.4+20121230.gitdf6c518-1 youtube-dl suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729412: python-django-south: incompatibilities with Django 1.6
Package: python-django-south Version: 0.7.5-1 Severity: serious Tags: patch Dear maintainer, python-django-south as shipped in unstable is not currently compatible with Django 1.6. Attached is a traceback. (the traceback was not taken on a Debian system, but is illustrative of the problem) The two commits needed to fix South are: * https://bitbucket.org/andrewgodwin/south/commits/b3b4970f2ffaab72f3a89752ae97e764e4be98c6 * https://bitbucket.org/andrewgodwin/south/commits/f1e1369f0d544db5a2bd7f8e04517353b26cb729 Both are included in the latest upstream release, so fixing http://bugs.debian.org/723174 would also close this bug. Regards. -- Luke Faraone;; Debian & Ubuntu Developer; Sugar Labs, Systems lfaraone on irc.[freenode,oftc].net -- http://luke.faraone.cc PGP fprint: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 > [removed] Error in migration: [removed] Traceback (most recent call last): File "manage.py", line 14, in execute_from_command_line(sys.argv) File "/home/somebody/src/django/django/core/management/__init__.py", line 399, in execute_from_command_line utility.execute() File "/home/somebody/src/django/django/core/management/__init__.py", line 392, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/home/somebody/src/django/django/core/management/base.py", line 242, in run_from_argv self.execute(*args, **options.__dict__) File "/home/somebody/src/django/django/core/management/base.py", line 285, in execute output = self.handle(*args, **options) File "/usr/local/lib/python2.7/site-packages/south/management/commands/migrate.py", line 111, in handle ignore_ghosts = ignore_ghosts, File "/usr/local/lib/python2.7/site-packages/south/migration/__init__.py", line 220, in migrate_app success = migrator.migrate_many(target, workplan, database) File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 229, in migrate_many result = migrator.__class__.migrate_many(migrator, target, migrations, database) File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 304, in migrate_many result = self.migrate(migration, database) File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 129, in migrate result = self.run(migration, database) File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 113, in run return self.run_migration(migration, database) File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 83, in run_migration migration_function() File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 59, in return (lambda: direction(orm)) File "/home/somebody/[removed]/migrations/[removed]", line 19, in forwards keep_default=True) File "/usr/local/lib/python2.7/site-packages/south/db/generic.py", line 47, in _cache_clear return func(self, table, *args, **opts) File "/usr/local/lib/python2.7/site-packages/south/db/generic.py", line 411, in add_column sql = self.column_sql(table_name, name, field) File "/usr/local/lib/python2.7/site-packages/south/db/generic.py", line 706, in column_sql default = field.get_db_prep_save(default, connection=self._get_connection()) File "/home/somebody/src/django/django/db/models/fields/__init__.py", line 350, in get_db_prep_save prepared=False) File "/home/somebody/src/django/django/db/models/fields/__init__.py", line 911, in get_db_prep_value value = self.get_prep_value(value) File "/home/somebody/src/django/django/db/models/fields/__init__.py", line 902, in get_prep_value (self.model.__name__, self.name, value), AttributeError: 'DateTimeField' object has no attribute 'model' signature.asc Description: Digital signature
Processed: Fixing severity of #729390
Processing commands for cont...@bugs.debian.org: > # FTBFSes are serious, not critical > severity 729390 serious Bug #729390 [python-qt4] FTBFS on i386 -- 4.10.3-2 Severity set to 'serious' from 'critical' > tags 729390 +pending Bug #729390 [python-qt4] FTBFS on i386 -- 4.10.3-2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 729390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729390: FTBFS on i386 -- 4.10.3-2
Package: python-qt4 Version: 4.10.3-2 Severity: critical Helle , whileI was recompiling python-qt4 to track a problem with python-taurus, I got this FTBFS I put only the end of the log, since it seems that no .buildlog are generated now ??? make[3]: Leaving directory `/tmp/buildd/python-qt4-4.10.3/dbg-build-3.3/pyuic' make[3]: Entering directory `/tmp/buildd/python-qt4-4.10.3/dbg-build-3.3/pylupdate' cp -f pylupdate4 /tmp/buildd/python-qt4-4.10.3/debian/python3-pyqt4-dbg/usr/bin/pylupdate4 make[3]: Leaving directory `/tmp/buildd/python-qt4-4.10.3/dbg-build-3.3/pylupdate' make[3]: Entering directory `/tmp/buildd/python-qt4-4.10.3/dbg-build-3.3/pyrcc' cp -f pyrcc4 /tmp/buildd/python-qt4-4.10.3/debian/python3-pyqt4-dbg/usr/bin/pyrcc4 make[3]: Leaving directory `/tmp/buildd/python-qt4-4.10.3/dbg-build-3.3/pyrcc' cp -f /tmp/buildd/python-qt4-4.10.3/__init__.py /tmp/buildd/python-qt4-4.10.3/debian/python3-pyqt4-dbg/usr/lib/python3.3/dist-packages/PyQt4/__init__.py cp -f pyqtconfig.py /tmp/buildd/python-qt4-4.10.3/debian/python3-pyqt4-dbg/usr/lib/python3.3/dist-packages/PyQt4/pyqtconfig.py make[2]: Leaving directory `/tmp/buildd/python-qt4-4.10.3/dbg-build-3.3' if [ -e /tmp/buildd/python-qt4-4.10.3/debian/python3-pyqt4-dbg/usr/lib/python3/dist-packages/dbus/mainloop/qt.so ]; then \ mkdir -p /tmp/buildd/python-qt4-4.10.3/debian/python3-dbus.mainloop.qt-dbg/usr/lib/python3.3/dist-packages/dbus/mainloop; \ mv /tmp/buildd/python-qt4-4.10.3/debian/python3-pyqt4-dbg/usr/lib/python3/dist-packages/dbus/mainloop/qt.so \ /tmp/buildd/python-qt4-4.10.3/debian/python3-dbus.mainloop.qt-dbg/usr/lib/python3.3/dist-packages/dbus/mainloop; \ fi # Don't initiate the uic/widget-plugins touch /tmp/buildd/python-qt4-4.10.3/debian/tmp/usr/lib/python3.3/dist-packages/PyQt4/uic/widget-plugins/.noinit mv debian/python3-pyqt4-dbg/usr/lib/python3.3/dist-packages/PyQt4/pyqtconfig.py \ debian/python3-pyqt4-dbg/usr/lib/python3.3/dist-packages/PyQt4/pyqtconfig_d3.py mkdir -p debian/python3-pyqt4.qtopengl-dbg/usr/lib/python3.3/dist-packages/PyQt4 mv debian/python3-pyqt4-dbg/usr/lib/python3.3/dist-packages/PyQt4/QtOpenGL.so \ debian/python3-pyqt4.qtopengl-dbg/usr/lib/python3.3/dist-packages/PyQt4 mkdir -p debian/python3-pyqt4.qtsql-dbg/usr/lib/python3.3/dist-packages/PyQt4 mv debian/python3-pyqt4-dbg/usr/lib/python3.3/dist-packages/PyQt4/QtSql.so \ debian/python3-pyqt4.qtsql-dbg/usr/lib/python3.3/dist-packages/PyQt4 mkdir -p debian/python3-pyqt4.phonon-dbg/usr/lib/python3.3/dist-packages/PyQt4 mv debian/python3-pyqt4-dbg/usr/lib/python3.3/dist-packages/PyQt4/phonon.so \ debian/python3-pyqt4.phonon-dbg/usr/lib/python3.3/dist-packages/PyQt4 mv: cannot stat 'debian/python3-pyqt4-dbg/usr/lib/python3.3/dist-packages/PyQt4/phonon.so': No such file or directory make[1]: *** [install-arch-3.3] Error 1 make[1]: Leaving directory `/tmp/buildd/python-qt4-4.10.3' make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 E: Failed autobuilding of package W: no hooks of type C found -- ignoring I: unmounting /var/cache/pbuilder/result filesystem I: unmounting /var/cache/pbuilder/ccache filesystem I: unmounting /dev/shm filesystem I: unmounting dev/pts filesystem I: unmounting run/shm filesystem I: unmounting proc filesystem -> Cleaning COW directory forking: rm -rf /var/cache/pbuilder/build//cow.11154 cheers Frederic -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.11-1-486 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-qt4 depends on: ii libc6 2.17-95 ii libgcc11:4.8.2-2 ii libpython2.7 2.7.5-8 ii libqt4-dbus4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-declarative 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-designer4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-help4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-network 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-script 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-scripttools 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-svg 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-test4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-xml 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqt4-xmlpatterns 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqtassistantclient4 4.6.3-6 ii libqtcore4 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqtgui4 4:4.8.5+git121-g2a9ea11+dfsg1-2 ii libqtwebkit4 2.2.1-7 ii libstdc++6 4.8.2-2 ii python 2.7.5-5 ii python-
Bug#690425: marked as done (sqldiff commands is incompatible with current Django)
Your message dated Tue, 12 Nov 2013 15:34:15 + with message-id and subject line Bug#690425: fixed in python-django-extensions 1.2.5-1 has caused the Debian Bug report #690425, regarding sqldiff commands is incompatible with current Django to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 690425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-django-extensions Version: 0.6+git201107051902-1 Severity: serious Hello, it looks like sqldiff in django_extensions has bitrotten considerably: $ ./manage.py sqldiff Traceback (most recent call last): File "./manage.py", line 10, in execute_from_command_line(sys.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/pymodules/python2.7/django_extensions/management/commands/sqldiff.py", line 583, in handle if settings.DATABASE_ENGINE == 'dummy': File "/usr/lib/python2.7/dist-packages/django/utils/functional.py", line 185, in inner return func(self._wrapped, *args) AttributeError: 'Settings' object has no attribute 'DATABASE_ENGINE' See: https://docs.djangoproject.com/en/1.2/ref/settings/#deprecated-settings I replaced DATABASE_ENGINE with DATABASES["default"]["ENGINE"], and now I hit: http://stackoverflow.com/questions/7042463/django-postgres-transaction-managed-block-ended-with-pending-commit-rollback I commented out transaction usage and now I get this: $ ./manage.py sqldiff services Traceback (most recent call last): File "./manage.py", line 10, in execute_from_command_line(sys.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/pymodules/python2.7/django_extensions/management/commands/sqldiff.py", line 612, in handle sqldiff_instance.find_differences() File "/usr/lib/pymodules/python2.7/django_extensions/management/commands/sqldiff.py", line 359, in find_differences self.find_field_type_differ(meta, table_description, table_name) File "/usr/lib/pymodules/python2.7/django_extensions/management/commands/sqldiff.py", line 279, in find_field_type_differ model_type = self.strip_parameters(self.get_field_model_type(field)) File "/usr/lib/pymodules/python2.7/django_extensions/management/commands/sqldiff.py", line 164, in get_field_model_type return field.db_type() TypeError: db_type() takes exactly 2 arguments (1 given) Finally, I passed django.db.connection to all db_type calls in sqldiff.py, and the command works, limited to the 'default' database. I copied https://raw.github.com/django-extensions/django-extensions/master/django_extensions/management/commands/sqldiff.py to /usr/share/pyshared/django_extensions/management/commands/sqldiff.py and it also worked, so a saner fix could probably be to just fetch the new sqldiff.py from upstream. Ciao, Enrico -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-django-extensions depends on: ii python 2.7.3~rc2-1 ii python-django 1.4.1-2 ii python-support 1.0.15 Versions of packages python-django-extensions recommends: ii libjs-jquery 1.7.2+debian-2.1 Versions of packages python-django-extensions suggests: ii python [python-profiler] 2.7.3~rc2-1 pn python-boto pn python-keyczar
Bug#724115: hunspell: FTBFS: POD error
On Fri, 08 Nov 2013 22:06:51 +0100, gregor herrmann wrote:
> here's a patch for this issue.
Now really :)
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: Alanis Morissette: Excuses
diff -u hunspell-1.3.2/debian/rules hunspell-1.3.2/debian/rules
--- hunspell-1.3.2/debian/rules
+++ hunspell-1.3.2/debian/rules
@@ -52,7 +52,7 @@
$(MAKE)
$(MAKE) check
- pod2man debian/ispellaff2myspell \
+ pod2man --utf8 debian/ispellaff2myspell \
> debian/ispellaff2myspell.1
touch build-stamp
diff -u hunspell-1.3.2/debian/ispellaff2myspell
hunspell-1.3.2/debian/ispellaff2myspell
--- hunspell-1.3.2/debian/ispellaff2myspell
+++ hunspell-1.3.2/debian/ispellaff2myspell
@@ -98,24 +98,24 @@
}
} else {
if ( $charset eq "latin0" ){
- $lowercase='a-z�';
- $uppercase='A-Z���';
+ $lowercase='a-zàáâãäåæçèéêëìíîïðñòóôõöøùúûüýþ½¨¸';
+ $uppercase='A-ZÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞ¼¦´';
} elsif ( $charset eq "latin1" ){
- $lowercase='a-z��';
- $uppercase='A-Z��';
+ $lowercase='a-zàáâãäåæçèéêëìíîïðñòóôõöøùúûüýþ';
+ $uppercase='A-ZÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞ';
} elsif ( $charset eq "latin2" ){
- $lowercase='a-z';
- $uppercase='A-Z';
+ $lowercase='a-z±³µ¶¹º»¼¾¿àáâãäåæçèéêëìíîïðñòóôõöøùúûüýþ';
+ $uppercase='A-Z¡£¥¦©ª«¬®¯ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞ';
} elsif ( $charset eq "latin3" ){
- $lowercase='a-z';
- $uppercase='A-Z';
+ $lowercase='a-z±¶¹º»¼¿àáâäåæçèéêëìíîïñòóôõö÷øùúûüýþ';
+ $uppercase='A-Z¡¦©ª«¬¯ÀÁÂÄÅÆÇÈÉÊËÌÍÎÏÑÒÓÔÕÖ×ØÙÚÛÜÝÞ';
# } elsif ( $charset eq "other_charset" ){
# die "latin2 still unimplemented";
} else {
if ( not $lowercase and not $uppercase ){
die "Unsupported charset [$charset]
-use explicitely --lowercase=string and --uppercase=string
+use explicitly --lowercase=string and --uppercase=string
options. Remember that both string must match exactly, but
case changed.
";
@@ -327,6 +327,8 @@
__END__
+=encoding UTF-8
+
=head1 NAME
B - A program to convert ispell affix tables to myspell
format.
@@ -402,8 +404,8 @@
You will need a call to -e for each flag type, e.g.,
B<-e "" -e "~"> (or B<-e '\\' -e '~\\'>).
-When a prefix is explicitely set, the default value (anything starting by
B<\>)
-is disabled and you need to enable it explicitely as in previous example.
+When a prefix is explicitly set, the default value (anything starting by B<\>)
+is disabled and you need to enable it explicitly as in previous example.
=item B<--lowercase=s>
@@ -442,8 +444,8 @@
the two strings of lower and uppercase chars. Note that they must match
exactly but case changed. It will look something like
- $lowercase='a-z��';
- $uppercase='A-Z��';
+ $lowercase='a-zàáâãäåæçèéêëìíîïðñòóôõöøùúûüýþ';
+ $uppercase='A-ZÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞ';
=head1 SEE ALSO
diff -u hunspell-1.3.2/debian/changelog hunspell-1.3.2/debian/changelog
--- hunspell-1.3.2/debian/changelog
+++ hunspell-1.3.2/debian/changelog
@@ -1,3 +1,15 @@
+hunspell (1.3.2-4.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Fix "FTBFS: POD error":
+- update POD of ispellaff2myspell:
+ + convert to UTF-8 and add =encoding directive
+ + additionally fix a typo
+- call pod2man with --utf8 in debian/rules
+(Closes: #724115)
+
+ -- gregor herrmann Fri, 08 Nov 2013 21:59:36 +0100
+
hunspell (1.3.2-4) unstable; urgency=low
* upload to unstable
signature.asc
Description: Digital signature
Bug#729253: cheese / cluttervideosink problem
W dniu 12.11.2013 13:10, Andreas Henriksson pisze: Could you please try to install the "gstreamer1.0-clutter" package and report back if this resolves the problem you're experiencing with cheese, as you reported in http://bugs.debian.org/729253 Yes, after installing “gstreamer1.0-clutter” the problem is fixed. A missing dependency somewhere? Thank you for quick response, Tomasz Melcer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701335: marked as done (pdl: ftbfs with GCC-4.8)
Your message dated Tue, 12 Nov 2013 15:20:20 + with message-id and subject line Bug#701335: fixed in pdl 1:2.007-2 has caused the Debian Bug report #701335, regarding pdl: ftbfs with GCC-4.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 701335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pdl Version: 1:2.4.11-4 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.8 The package fails to build in a test rebuild on at least amd64 with gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The severity of this report may be raised before the jessie release. XXX The full build log can be found at: http://people.debian.org/~doko/logs-20130217/gcc48/pdl_2.4.11-4_unstable_gcc48.log The last lines of the build log are at the end of this report. To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues might be caused by the updated glibc. [...] perl -Mblib debian/write_config_debian.pl > blib/lib/PDL/Config/Debian.pm pod2man debian/dh_pdl > debian/dh_pdl.1 touch build-stamp fakeroot debian/rules binary-arch dh_testdir BEGIN test normal /usr/bin/make TEST_VERBOSE=0 LC_ALL=C test | perl debian/filter-test.pl *** Error in `/usr/bin/perl': realloc(): invalid next size: 0x0193f900 *** make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs make[1]: *** wait: No child processes. Stop. make: *** [test-stamp] Terminated Build killed with signal TERM after 60 minutes of inactivity ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ Build finished at 20130219-0017 Finished ââââââââ E: Build failure (dpkg-buildpackage died) ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ â Cleanup â ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ Purging /«BUILDDIR» Not cleaning session: cloned chroot in use ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ â Summary â ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ Architecture: amd64 Build-Space: 178008 Build-Time: 4026 Distribution: unstable Fail-Stage: build Install-Time: 22 Job: pdl_1:2.4.11-4 Package: pdl Package-Time: 4073 Source-Version: 1:2.4.11-4 Space: 178008 Status: attempted Version: 1:2.4.11-4 ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ Finished at 20130219-0017 Build needed 01:07:53, 178008k disc space DC-Status: Failed 4074.429348s DC-Time-Estimation: 4074.429348 versus expected 696 (r/m: 4.85406515517241 ; m: 696.0) --- End Message --- --- Begin Message --- Source: pdl Source-Version: 1:2.007-2 We believe that the bug you reported is fixed in the latest version of pdl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 701...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Henning Glawe (suppl
Bug#713346: marked as done (pdl: FTBFS: build hangs)
Your message dated Tue, 12 Nov 2013 15:20:20 + with message-id and subject line Bug#713346: fixed in pdl 1:2.007-2 has caused the Debian Bug report #713346, regarding pdl: FTBFS: build hangs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 713346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pdl Version: 1:2.4.11-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > fakeroot debian/rules binary > dh_testdir > BEGIN test normal > /usr/bin/make TEST_VERBOSE=0 LC_ALL=C test | perl debian/filter-test.pl > *** Error in `/usr/bin/perl': realloc(): invalid next size: > 0x0186ba90 *** > make[1]: *** wait: No child processes. Stop. > make[1]: *** Waiting for unfinished jobs > make[1]: *** wait: No child processes. Stop. > make: *** wait: No child processes. Stop. > make: *** Waiting for unfinished jobs > make: *** wait: No child processes. Stop. > E: Caught signal ‘Terminated’: terminating immediately > Build killed with signal TERM after 60 minutes of inactivity > > Build finished at 20130621-0704 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/pdl_2.4.11-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: pdl Source-Version: 1:2.007-2 We believe that the bug you reported is fixed in the latest version of pdl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Henning Glawe (supplier of updated pdl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 11 Nov 2013 13:34:09 +0100 Source: pdl Binary: pdl Architecture: source amd64 Version: 1:2.007-2 Distribution: unstable Urgency: low Maintainer: Henning Glawe Changed-By: Henning Glawe Description: pdl- perl data language: Perl extensions for numerics Closes: 701335 713346 Changes: pdl (1:2.007-2) unstable; urgency=low . * successfully built with gcc 4.8 (closes: #701335, #713346) * add build log evalution helpers to source package: extract test suite output from buildlog, cross-refernce test/subtest failures between architectures * use shell to join stderr into stdout while running test suite * fix Dumper.pm on kfreebsd: 'gnukfreebsd' was assumed as a bsd userland, which disabled/broke calls to 'uuencode' and 'uudecode' * fix debian/filter-test.pl, which cut the test log too early due to a too-unspecific regex * prefer F77Conf over ExtUtils::F77 in t/flexraw_fortran.t in order to prevent test failures on kfreebsd* and hurd* Checksums-Sha1: c82bb3b8ab12805a7520fcae60ddfdb24308aa3c 1424 pdl_2.007-2.dsc cbff59ebbd311a41899af3bdfe59a09691571542 26375 pdl_2.007-2.debian.tar.gz 1c46cdf72170f4312416ce26cd0cb81ec1586fcd 3862970 pdl_2.007-2_amd64.deb Checksums-Sha256: e66a426861c01647516d0b07741f46b8766295be75188a1ed7604bc248c06f36 1424 pdl_2.007-2.dsc b4f3df942114bce92ec5e7db8d5bbf22f19c2e2d417d06420fd0f25bdca93778 26375 pdl_2.007-2.debian.tar.gz 364501c903e64ff33a30f1e9783b33400fc8700f59c74e65bcceb75a5c86a750 3862970 pdl_2.007-2_amd64.deb Files: 7a2360eb206f28d78feceba7d0b30c3c 1424 math optional pdl_2.007-2.dsc db872db60bb2ccef27d1fa76994915f1 26375 math optional pdl_2.007-2.debian.tar.gz 042007b10b42a1989d8b1c6d4b586451 3862970 math optional pdl_2.007-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlKCNCcACgkQgjOm0i0vde/e/gCfYIO4YPVv
Bug#727786: CD/USB boot is the only way
Just ran into this bug after installing and uninstalling gdb64 (which depends on libc6-amd64). Having root access does not solve the problem because rm and ln rely on libc6 ~$ ldd /bin/rm linux-vdso.so.1 => (0x7fffd578e000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f37ad8ee000) /lib64/ld-linux-x86-64.so.2 (0x7f37adcd4000) Time to dust off that installation DVD or make a new one if you have access to another machine. I agree that this is an insidious bug for inexperienced users to diagnose because the system becomes unusable and unbootable. Dan
Bug#718060: marked as done (libgadu: FTBFS: autoreconf: automake-1.11 failed with exit status: 63)
Your message dated Tue, 12 Nov 2013 13:33:30 + with message-id and subject line Bug#718060: fixed in libgadu 1:1.11.2-2 has caused the Debian Bug report #718060, regarding libgadu: FTBFS: autoreconf: automake-1.11 failed with exit status: 63 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 718060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgadu Version: 1:1.11.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130726 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with autoreconf --parallel >dh_testdir -O--parallel >dh_autoreconf -O--parallel > libtoolize: putting auxiliary files in `.'. > libtoolize: copying file `./ltmain.sh' > libtoolize: putting macros in `m4'. > libtoolize: copying file `m4/libtool.m4' > libtoolize: copying file `m4/ltoptions.m4' > libtoolize: copying file `m4/ltsugar.m4' > libtoolize: copying file `m4/ltversion.m4' > libtoolize: copying file `m4/lt~obsolete.m4' > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and > libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. > configure.ac:4: version mismatch. This is Automake 1.11.6, > configure.ac:4: but the definition used by this AM_INIT_AUTOMAKE > configure.ac:4: comes from Automake 1.13.3. You should recreate > configure.ac:4: aclocal.m4 with aclocal and run automake again. > configure.ac:7: installing `./config.guess' > configure.ac:7: installing `./config.sub' > configure.ac:4: installing `./install-sh' > configure.ac:4: installing `./missing' > docs/Makefile.am:5: wildcard ../src/*.c: non-POSIX variable name > docs/Makefile.am:5: (probably a GNU make extension) > docs/Makefile.am:5: wildcard *.dox: non-POSIX variable name > docs/Makefile.am:5: (probably a GNU make extension) > automake-1.11: compiling `httphash.c' with per-target flags requires > `AM_PROG_CC_C_O' in `configure.ac' > examples/Makefile.am:1: while processing program `httphash' > examples/Makefile.am: installing `./depcomp' > test/automatic/Makefile.am:30: wildcard script/*.scr: non-POSIX variable name > test/automatic/Makefile.am:30: (probably a GNU make extension) > test/automatic/Makefile.am:5: `CFLAGS' is a user variable, you should not > override it; > test/automatic/Makefile.am:5: use `AM_CFLAGS' instead. > test/manual/Makefile.am:4: `CFLAGS' is a user variable, you should not > override it; > test/manual/Makefile.am:4: use `AM_CFLAGS' instead. > Makefile.am: installing `./INSTALL' > autoreconf: automake-1.11 failed with exit status: 63 > dh_autoreconf: autoreconf -f -i returned exit code 63 > make: *** [build] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/07/26/libgadu_1.11.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: libgadu Source-Version: 1:1.11.2-2 We believe that the bug you reported is fixed in the latest version of libgadu, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 718...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcin Owsiany (supplier of updated libgadu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Nov 2013 13:31:58 +0100 Source: libgadu Binary: libgadu3 libgadu3-dbg libgadu-dev libgadu-doc Architecture: source amd64 all Version: 1:1.11.2-2 Distribution: unstable Urgency: medium Maintainer: Marcin Owsiany Changed-By: Marcin Owsiany Description: libgadu-dev - Gadu-Gadu protocol library - development files libgadu-doc - Gadu-Gadu protocol library - documentation libgadu3 - G
Bug#720816: Bug#729289: Bug#720816: openscenegraph: FTBFS with libav9: FFmpegDecoder.cpp:282:76: error: 'url_feof' was not declared in this scope
On 11/12/2013 02:09 PM, Steven Chamberlain wrote: > Hi Bas, > > Am I right in thinking osgearth cannot build against the > libopenscenegraph99 currently in sid? So actually you *cannot* fix bug > #725383 until a new upload of openscenegraph? Correct. The dependencies of libopenscenegraph need to be updated before it can be installed to satisfy the osgEarth build dependencies. Current pbuilder builds fail to install the dependencies: The following packages have unmet dependencies: libopenscenegraph99 : Depends: libavcodec53 (>= 6:0.8.3-1~) which is a virtual package. or libavcodec-extra-53 (>= 6:0.8.7) which is a virtual package. Depends: libavdevice53 (>= 6:0.8.3-1~) but it is not going to be installed. Depends: libavformat53 (>= 6:0.8.3-1~) which is a virtual package. Depends: libavutil51 (>= 6:0.8.3-1~) which is a virtual package. Depends: libcairo2 (>= 1.2.4) but it is not going to be installed. Depends: libcoin80 but it is not going to be installed. Depends: libpoppler-glib8 (>= 0.18) but it is not going to be installed. Depends: librsvg2-2 (>= 2.14.4) but it is not going to be installed. Depends: libswscale2 (>= 6:0.8.3-1~) but it is not going to be installed. Depends: libxine1 (>= 1.1.8) but it is not going to be installed. Unable to resolve dependencies! Giving up... These are still the pre-libav9 transition versions. > You used the word 'uninstallable' before but, AFAIK it is installable > (everywhere except mips), but rather anything building against that lib > will FTBFS due to libav9 incompatibility? The unmet dependencies are why I referred to it as "uninstallable". I solved this with my local build of openscenegraph to verify that osgEarth still builds successfully, and that the patch for #725383 works. > Regards, Kind Regards, Bas -- GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720816: Bug#729289: Bug#720816: openscenegraph: FTBFS with libav9: FFmpegDecoder.cpp:282:76: error: 'url_feof' was not declared in this scope
Hi Bas, Am I right in thinking osgearth cannot build against the libopenscenegraph99 currently in sid? So actually you *cannot* fix bug #725383 until a new upload of openscenegraph? You used the word 'uninstallable' before but, AFAIK it is installable (everywhere except mips), but rather anything building against that lib will FTBFS due to libav9 incompatibility? Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729253: cheese / cluttervideosink problem
Hello! Thanks for your bug report. Could you please try to install the "gstreamer1.0-clutter" package and report back if this resolves the problem you're experiencing with cheese, as you reported in http://bugs.debian.org/729253 -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728293: libusb-java: Patch to resolved build issues where default-jdk is not openjdk-6
Package: libusb-java Version: 0.8+ztex20090101-6 Followup-For: Bug #728293 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu trusty ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: - d/p/jniInclude.patch: Restore original auto-detection of JAVAPREFIX so that package continues to build on targets with default-java != openjdk-6. Thanks for considering the patch. -- System Information: Debian Release: wheezy/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12.0-2-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru libusb-java-0.8+ztex20090101/debian/changelog libusb-java-0.8+ztex20090101/debian/changelog diff -Nru libusb-java-0.8+ztex20090101/debian/patches/jniInclude.patch libusb-java-0.8+ztex20090101/debian/patches/jniInclude.patch --- libusb-java-0.8+ztex20090101/debian/patches/jniInclude.patch 2012-09-16 20:37:40.0 +0100 +++ libusb-java-0.8+ztex20090101/debian/patches/jniInclude.patch 2013-10-08 23:13:04.0 +0100 @@ -1,14 +1,11 @@ -Index: libusb-java-0.8+ztex20090101/Makefile -=== libusb-java-0.8+ztex20090101.orig/Makefile 2011-02-02 13:13:45.0 +0100 -+++ libusb-java-0.8+ztex20090101/Makefile 2012-09-16 20:45:06.0 +0200 -@@ -13,7 +13,8 @@ +--- a/Makefile b/Makefile +@@ -13,7 +13,7 @@ # # $(JAVAPREFIX)/include should contain jni.h -JAVAPREFIX=/usr/local/java -+#JAVAPREFIX=$(shell find /usr/lib/jvm/ -name jni.h | sed -e 's/include.*//' | head -n 1) -+JAVAPREFIX=/usr/lib/jvm/java-6-openjdk-$(shell dpkg-architecture -qDEB_BUILD_ARCH|tr -d "\n") ++JAVAPREFIX=$(shell find /usr/lib/jvm/ -name jni.h | sed -e 's/include.*//' | head -n 1) ### # this should not be modified #
Bug#727070: xpdf: Upgrade of fontconfig from 2.10.2 to 2.11 causes xpdf to deadlock on x86 and fail mutex on x86_64
Package: xpdf Version: 3.03-11 Followup-For: Bug #727070 Dear Maintainer, This bug remais here. Is there any chance of a solution for it? How can we, "end users", help? Thanks in advance, Alexandre. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (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/dash Versions of packages xpdf depends on: ii libc6 2.17-93 ii libgcc1 1:4.8.2-1 ii libpoppler19 0.18.4-8 ii libstdc++64.8.2-1 ii libx11-6 2:1.6.2-1 ii libxm42.3.4-4 ii libxt61:1.1.4-1 Versions of packages xpdf recommends: ii cups-bsd 1.6.3-1 ii gsfonts-x110.22 ii poppler-data 0.4.6-4 ii poppler-utils 0.18.4-8 xpdf suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 728695 confirmed Bug #728695 [src:stressapptest] Fix armhf buildds Added tag(s) confirmed. > severity 728695 serious Bug #728695 [src:stressapptest] Fix armhf buildds Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 728695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720816: openscenegraph: FTBFS with libav9: FFmpegDecoder.cpp:282:76: error: 'url_feof' was not declared in this scope
"Rebecca N. Palmer" writes: >> That's why I'm not so >> keen on uploading a RC again, given the grief that caused the last one. >> Maybe we can just patch 3.2.0 and then wait for the 3.2.1, > > If you mean real 3.2.0 as opposed to the current 3.2.0rc, that could > be a good compromise: it has soname 100 (so no need for binNMUs when > 3.2.1 comes out) and avoids the need to patch libcitygml (as the bug > in that is that it doesn't understand ~rc version numbers). Yes, I mean 3.2.0. -- Alberto -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#718761: flash-kernel: 'root=' kernel param ignored when flash-kernel package is installed
On Sun, Aug 04, 2013, Erik Speckman wrote: > If flash-kernel isn't necessary/required on my device, I would expect > it to detect that fact rather than rendering my system in an > unbootable state. It's probably necessary as on other Kirkwood devices as to generate an uImage / uInitrd. > I realize that my system (a ZyXel NSA320 modified to boot debian) > isn't particularly common, but I also know that there is a community > of people running debain on Kirkwood devices using the same technique, > and I doubt I am the only one to think that flash-kernel might be a > useful package to have installed. Sure thing; let's figure out your device specifics and add them to the flash-kernel database; could you send your /proc/cpuinfo? I'm a bit surprized that flash-kernel is running at all since it should detect an unsupported machine and bail out. Also do you have a /proc/device-tree/model file? How did you install Debian on the device and what's the expected root device? Cheers -- Loïc Minier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720816: openscenegraph: FTBFS with libav9: FFmpegDecoder.cpp:282:76: error: 'url_feof' was not declared in this scope
That's why I'm not so keen on uploading a RC again, given the grief that caused the last one. Maybe we can just patch 3.2.0 and then wait for the 3.2.1, If you mean real 3.2.0 as opposed to the current 3.2.0rc, that could be a good compromise: it has soname 100 (so no need for binNMUs when 3.2.1 comes out) and avoids the need to patch libcitygml (as the bug in that is that it doesn't understand ~rc version numbers). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720816: Bug#729289: Bug#720816: openscenegraph: FTBFS with libav9: FFmpegDecoder.cpp:282:76: error: 'url_feof' was not declared in this scope
On 11/12/2013 10:27 AM, Rebecca N. Palmer wrote: > Furthermore, Alioth is now expected to be down for days > (http://lists.debian.org/debian-infrastructure-announce/2013/11/msg1.html), > so just getting access to the 3.2.1 package might take some time. I'm not sure if it helps, but I have a clone of the pkg-osg git repo that I used to fix the package so I could test the rebuilds of osgEarth and QGIS. http://git.linuxminded.nl/?p=pkg-osg/pkg-osg You can clone a local copy and work with that until Alioth is restored. My clone contains a few changes that you may or may not want to keep. Kind Regards, Bas -- GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720816: openscenegraph: FTBFS with libav9: FFmpegDecoder.cpp:282:76: error: 'url_feof' was not declared in this scope
"Rebecca N. Palmer" writes: > Sorry for not notifying you earlier; given the names on the git > commits, I thought Alberto was effectively the maintainer and you his > sponsor. Hi, I plan to be the maintainer, but I'm not a DM yet, and so I rely on the expertise of Manuel in order to make the releases. He has always guided me through the technical difficulties that arised in the past. I am also subscribed to the bug reports of the package, so you can drop me from the Cc: as long as you keep the discussion in the bug reports. > Would you like to set up a maintainer-team mailing list to avoid such > problems in future? Indeed, it already exists... but it is hosted on Alioth. > Are you still looking for help (#392266), and if so with what? > This is a past request from Loic, and it stood. I guess the philosophy is «the more, the merrier». [...] >>> Since the transition requested already mentions libopenscenegraph100, >>> but 3.2.1 is not released, I think that it's actually more risky (or >>> prone to more delays) if to tie the current transition to these future >>> ones of OSG. > The 99->100 soname bump is 3.2.0rc->3.2.0 not 3.2.0->3.2.1 and appears > to be a standard OSG release procedure (possibly intended as a "don't > use pre-releases in production" marker) rather than a real change > (https://github.com/openscenegraph/osg/commits/OpenSceneGraph-3.2?page=2, > scroll down to Jul 23), so I wouldn't _expect_ further breakage, but I > agree it's always possible. (E.g. building with --as-needed, which > you do (as recommended), is currently unreliable on ia64: #718047) I wouldn't also, but it is not written on stone. That's why I'm not so keen on uploading a RC again, given the grief that caused the last one. Maybe we can just patch 3.2.0 and then wait for the 3.2.1, or keep waiting for 3.2.1, since it should be realeased soon. Regards, Alberto -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720816: openscenegraph: FTBFS with libav9: FFmpegDecoder.cpp:282:76: error: 'url_feof' was not declared in this scope
Sorry for not notifying you earlier; given the names on the git commits, I thought Alberto was effectively the maintainer and you his sponsor. Would you like to set up a maintainer-team mailing list to avoid such problems in future? Are you still looking for help (#392266), and if so with what? - fgrun is a bit neglected in Debian, [...] it's already been removed from testing for 2 years The simgear/flightgear/fgrun set was lacking maintenance for some time, but is now in the process of returning with a new maintainer; the problems that got it removed from testing have been fixed, but it can't be rebuilt yet because this bug makes libopenscenegraph-dev uninstallable. I now see that these [reverse dependencies] packages are 'sid only', They're sid-only because this transition stalled for long enough for its FTBFS bugs to trigger the autoremover. Is that an autoremover bug or a feature? Since the transition requested already mentions libopenscenegraph100, but 3.2.1 is not released, I think that it's actually more risky (or prone to more delays) if to tie the current transition to these future ones of OSG. The 99->100 soname bump is 3.2.0rc->3.2.0 not 3.2.0->3.2.1 and appears to be a standard OSG release procedure (possibly intended as a "don't use pre-releases in production" marker) rather than a real change (https://github.com/openscenegraph/osg/commits/OpenSceneGraph-3.2?page=2, scroll down to Jul 23), so I wouldn't _expect_ further breakage, but I agree it's always possible. (E.g. building with --as-needed, which you do (as recommended), is currently unreliable on ia64: #718047) Furthermore, Alioth is now expected to be down for days (http://lists.debian.org/debian-infrastructure-announce/2013/11/msg1.html), so just getting access to the 3.2.1 package might take some time. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728796: [Pkg-erlang-devel] Bug#728796: can not remove package
tags 728796 + moreinfo thanks Hi Arne, On Tue, Nov 5, 2013 at 7:41 PM, arne wrote: > > # dpkg -P --force all yaws > (Reading database ... 315953 files and directories currently installed.) > Removing yaws ... > Stopping yaws: invoke-rc.d: initscript yaws, action "stop" failed. > dpkg: error processing yaws (--purge): > subprocess installed pre-removal script returned error exit status 1 > Starting yaws: .. failedYaws web server. > Errors were encountered while processing: > yaws I can't reproduce this bug myself. Looks like the YAWS can't be stopped. Could you describe how did you install the yaws package, did you add/change its configuration? Also, the content of /var/log/yaws/report.log could be helpful. Cheers! -- Sergei Golovan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Pkg-erlang-devel] Bug#728796: can not remove package
Processing commands for cont...@bugs.debian.org: > tags 728796 + moreinfo Bug #728796 [yaws] can not remove package Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 728796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728361: Bug#729134: [Pkg-systemd-maintainers] Bug#729134: libpam-systemd wreaks havoc
On Tue, 2013-11-12 at 08:08 +0100, Julien Puydt wrote: > Notice that you focus on lightdm but that removing libpam-systemd > solved > other problems. Could you point to those other problems where lightdm was not involved at all? > > I have no clue how to reproduce it... I only have the system where I had > problems and solved them. Not sure about GNOME, but on an Xfce systems, it should just be a matter of install xfce4 and lightdm (with recommends), check that ck-list-session indeed list a session, check that in the logout session windows the various options (suspend/hibernate/shutdown/restart) are not greyed out. Then install libpam-systemd and check that they are now greyed out and that ck-list-session doesn't list anything. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
