Bug#767193: mbt: 3.2.10-5 must not be in jessie
Package: mbt Version: 3.2.10-5 Severity: serious This package of mbt should not be in jessie: a library transition in the mbt/timbl/dimbl/frog/libfolia/ticcutils/ucto - suite is upcoming. This transition will take place in unstable; transitioned packages are targeted for zurg. There is no time for proper testing before the freeze of jessie. Thanks, Bye, Joost On Tue, Oct 28, 2014 at 11:04:32PM +, Debian FTP Masters wrote: Accepted: Source: mbt Binary: mbt libmbt1-dev libmbt1 Architecture: source amd64 Version: 3.2.10-5 Distribution: unstable Urgency: low Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Joost van Baal-Ilić joos...@debian.org Description: libmbt1- memory-based tagger-generator and tagger - runtime libmbt1-dev - memory-based tagger-generator and tagger - development mbt- memory-based tagger-generator and tagger Changes: mbt (3.2.10-5) unstable; urgency=low . * debian/control: migrated version control from Subversion to git (still on Debian's Alioth). * debian/*: change version control tags from Subversion to git. * debian/watch: more strict. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767201: virtualbox: After update to 4.3.18-dfsg-1 guests doesn't start
Package: virtualbox Version: 4.3.18-dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, After I updated to 4.3.18-dfsg-1 none of my guests starts. No error message found anywhere, just quits. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virtualbox depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.13 ii libc62.19-12 ii libcurl3 7.38.0-2 ii libgcc1 1:4.9.1-16 ii libgsoap52.8.17-1 ii libpng12-0 1.2.50-2 ii libpython2.7 2.7.8-10 ii libsdl1.2debian 1.2.15-10 ii libssl1.0.0 1.0.1j-1 ii libstdc++6 4.9.1-16 ii libvncserver00.9.9+dfsg-6+b2 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxcursor1 1:1.1.14-1 ii libxext6 2:1.3.3-1 ii libxml2 2.9.1+dfsg1-4 ii libxmu6 2:1.1.2-1 ii libxt6 1:1.1.4-1 ii python 2.7.8-1 ii python2.72.7.8-10 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages virtualbox recommends: ii libgl1-mesa-glx [libgl1] 10.3.1-1 ii libqt4-opengl 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii virtualbox-dkms 4.3.18-dfsg-1 ii virtualbox-qt 4.3.18-dfsg-1 Versions of packages virtualbox suggests: ii vde22.3.2+r586-1 ii virtualbox-guest-additions-iso 4.3.18-1 -- 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#747785: src:curtain: use dh-autoreconf to fix FTBFS on ppc64el
Package: curtain Version: 0.3-1 Followup-For: Bug #747785 Tags: patch X-Debbugs-Cc: bren...@br.ibm.com User: debian-powe...@lists.debian.org Usertags: ppc64el User: debian-de...@lists.debian.org Usertags: autoreconf Dear Maintainer, In the ppc64el architecture, we need new libtool macros, and hence a full autoreconf is required. In ppc64el, the following patch was able to resolve the build issue. Thanks for considering the patch! Brahadambal Srinivasan -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16-trunk-powerpc64le (SMP w/32 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash diff -ruN curtain-0.3.orig/debian/control curtain-0.3/debian/control --- curtain-0.3.orig/debian/control 2014-10-29 08:49:18.0 + +++ curtain-0.3/debian/control 2014-10-29 08:49:51.0 + @@ -4,6 +4,7 @@ Maintainer: Andrea Colangelo war...@debian.org Build-Depends: debhelper (= 9), autotools-dev, + dh-autoreconf, intltool, pkg-config, libgtk-3-dev diff -ruN curtain-0.3.orig/debian/rules curtain-0.3/debian/rules --- curtain-0.3.orig/debian/rules 2014-10-29 08:49:30.0 + +++ curtain-0.3/debian/rules2014-10-29 08:50:01.0 + @@ -2,4 +2,4 @@ #export DH_VERBOSE=1 %: - dh $@ --with autotools_dev + dh $@ --with autotools_dev,autoreconf
Bug#762790: powerpc-utils: maintainer address bounces
Hi Michael, On Wed, 29 Oct 2014 08:30:15 +1300 Michael Schmitz schmitz...@gmail.com wrote: Hi, sorry about the bounce - I had been assured mail forwarding would be set up when the mailserver handling that address was retired. Shall I prepare a source-only upload to correct the address? Yes, and you can also ACK the NMU. :-) It is probably good idea to avoid big changes since the package will have to migrate to testing manually, after the freeze. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763006: [pkg-cli-apps-team] Bug#763006: Will 0.95.2 be pushed to Ubuntu 14.10 repos?
On Tue, Oct 28, 2014 at 09:34:13PM -0400, Vic Kumar wrote: ... Currently, the version in the repos is 0.95.1. I saw the issue looks to be fixed in 0.95.2. Was wondering if this will be pushed into the repo's for Ubuntu 14.10. I know, I know. It's only been 2 days since the issue was resolved, but I like gnome-do. It is already fixed there. https://launchpad.net/ubuntu/+source/gnome-do/0.95.1-1ubuntu1 -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: Digital signature
Bug#607969: sqlite: Still useful?
Hi, On Mon, 4 Aug 2014 20:08:21 +0100 Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: Control: severity -1 serious Hi, I stumbled upon this bug by chance when looking at why it did not compile in some new ports. Raising severity so at the very least it gets auto-removed from testing and thus it does not get included in the next stable release (it already was included in the last, despite opinions in this bug about the contrary). I guess that it's better to just ask FTP masters to remove the package, but I'll leave that to other people, since they were interested in doing that in the past (all in copy now). Filing bugs against reverse dependencies to migrate to sqlite 3 would be a better start IMO. Probably it is too late to convert everything for Jessie: $ apt-cache rdepends sqlite sqlite Reverse Depends: phpbb3 |movabletype-opensource sqlite:i386 sqlite-doc qsf phpbb3 lire imms-common csync2 beancounter Dear Release Team, should this package be released with Jessie? Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765371: owfs is marked for autoremoval from testing
On 29/10/2014 05:39, Debian testing autoremoval watch wrote: owfs 2.9p5-1.1 is marked for autoremoval from testing on 2014-11-13 It is affected by these RC bugs: 765371: python-ow: Import fails - error parsing version (fixed upstream) Hi, This bug is fixed in unstable. I did not take time to initially downgrade the bug severity as I did a quick upload to unstable. However, due to problem with FreeBSD, I will probably need to ask for a freeze exception. But, in any case, this bug is not a grave one. Python bindings are only a very little aspect of owfs and a such a bug do not justify such a severity. Regards, Vincent -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 765371 is important
Processing commands for cont...@bugs.debian.org:
severity 765371 important
Bug #765371 {Done: Vincent Danjean vdanj...@debian.org} [python-ow] Import
fails - error parsing version (fixed upstream)
Severity set to 'important' from 'grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
765371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765371
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#763961: Pitivi doesn't start, please update from upstream
Ubuntu has a set of cherry-picked patches on top of 0.93-4 that make it usable: https://launchpad.net/ubuntu/+source/pitivi/0.93-4ubuntu1 These would be probably enough for jessie. -Timo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607969: sqlite: Still useful?
On Wed, Oct 29, 2014 at 10:33:32 +0100, Balint Reczey wrote: Dear Release Team, should this package be released with Jessie? The only way I can see us not shipping it is if we remove it along with the remaining rdeps. Now is not the time to migrate them over to sqlite3 in jessie. Cheers, Julien signature.asc Description: Digital signature
Bug#607969: sqlite: Still useful?
On Wed, Oct 29, 2014 at 10:33 AM, Balint Reczey bal...@balintreczey.hu wrote: On Mon, 4 Aug 2014 20:08:21 +0100 Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: I stumbled upon this bug by chance when looking at why it did not compile in some new ports. It should compile on all of them by now. The buildd archive shows that arm64 and ppc64el are fine, even mips and sparc. I guess that it's better to just ask FTP masters to remove the package, but I'll leave that to other people, since they were interested in doing that in the past (all in copy now). Yes, I was about to ask its removal as upstream no longer supports it. But it works correctly and I got personal mails that they would still use it on low-end (embedded?) machines where sqlite3 would require more CPU and/or memory. Filing bugs against reverse dependencies to migrate to sqlite 3 would be a better start IMO. I've mailed all of them some years ago, but there are still some use it. Probably it is too late to convert everything for Jessie: It is late. Dear Release Team, should this package be released with Jessie? I'm open for everything, but please do note that the removal would mean removing the dependent packages as well. Cheers, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767203: postfix: default install vulnerable for POODLE TLS attack
package: postfix version: 2.9.6-2 tag: upstream severity: critical Hi, The Postfix Debian package ships with a default list of supported TLS protocols which makes it vulnerable to the POODLE TLS attack: % postconf smtp_tls_mandatory_protocols smtp_tls_mandatory_protocols = !SSLv2 This is the upstream default: % postconf -d smtp_tls_mandatory_protocols smtp_tls_mandatory_protocols = !SSLv2 Other vulnerable daemon settings are: lmtp_tls_mandatory_protocols = !SSLv2 lmtp_tls_protocols = !SSLv2 smtp_tls_mandatory_protocols = !SSLv2 smtp_tls_protocols = !SSLv2 smtpd_tls_mandatory_protocols = !SSLv2 It would be nice if postfix would ship with a /etc/postfix/main.cf which features tls_protocols = !SSLv2, !SSLv3 smtp_tls_protocols = $tls_protocols smtp_tls_mandatory_protocols = $tls_protocols lmtp_tls_protocols = $tls_protocols lmtp_tls_mandatory_protocols = $tls_protocols smtpd_tls_protocols = $tls_protocols smtpd_tls_mandatory_protocols = $tls_protocols tlsproxy_tls_protocols = $tls_protocols tlsproxy_tls_mandatory_protocols = $tls_protocols This would make the default install no longer vulnerable for POODLE. Thanks to Wessel Dankers for reporting the problem to me, and suggesting the mentioned fixes. Thanks for maintaining the Postfix package, Bye, Joost PS: this bug is somewhat related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729188#103 PPS FWIW: on https://blog.surfnet.nl/?p=3290 there's a more elaborate list of current sane defaults. Currently, tls_ciphers = ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA lmtp_tls_ciphers = $tls_ciphers lmtp_tls_mandatory_ciphers = $tls_ciphers smtp_tls_ciphers = $tls_ciphers smtp_tls_mandatory_ciphers = $tls_ciphers smtpd_tls_ciphers = $tls_ciphers smtpd_tls_mandatory_ciphers = $tls_ciphers tlsproxy_tls_ciphers = $tls_ciphers tlsproxy_tls_mandatory_ciphers = $tls_ciphers is sane too (but not future-proof). signature.asc Description: Digital signature
Bug#607969: sqlite: Still useful?
Hi Julien, 2014-10-29 10:48 GMT+01:00 Julien Cristau jcris...@debian.org: On Wed, Oct 29, 2014 at 10:33:32 +0100, Balint Reczey wrote: Dear Release Team, should this package be released with Jessie? The only way I can see us not shipping it is if we remove it along with the remaining rdeps. Now is not the time to migrate them over to sqlite3 in jessie. I fully agree. How about marking this bug jessie-ignore or decreasing the severity? I periodically look for RC bugs to fix (like hopefully many others :-)) and those would make that bug stop appearing on the list. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744753: anacron: Anacron not triggered when system resumes under systemd
Le Tue, 28 Oct 2014 13:24:53 +0100, Laurent Bigonville bi...@debian.org a écrit : severity 744753 serious thanks Hello, IMHO this bug should be serious as anacron is more or less useless without this. Do we have a consensus on a solution here? Michael was proposing another solution. Instead of waking anacron at boot and just after sleep, we could run it every hour. So it would be quite unlikely that anacron is not run at all at least once a day on the machine of the user. I personally don't have strong feeling about this. Looking at Fedora they are doing this too apparently. Any thoughts? Cheers, Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: jessie
Processing commands for cont...@bugs.debian.org:
tags 767115 + sid jessie
Bug #767115 {Done: Emmanuel Bourg ebo...@apache.org} [src:libfreemarker-java]
libfreemarker-java: Declares a parent pom not packaged in Debian
Added tag(s) sid and jessie.
tags 726593 + sid jessie
Bug #726593 [egg] egg: Emacs 24 support
Added tag(s) sid and jessie.
tags 744753 + wheezy-ignore
Bug #744753 [anacron] anacron: Anacron not triggered when system resumes under
systemd
Bug #767092 [anacron] anacron fails to run when laptop goes out of sleep
Added tag(s) wheezy-ignore.
Added tag(s) wheezy-ignore.
End of message, stopping processing here.
Please contact me if you need assistance.
--
726593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726593
744753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744753
767092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767092
767115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767115
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
Processed: Re: Bug#767203: postfix: default install vulnerable for POODLE TLS attack
Processing control commands: severity -1 normal Bug #767203 [postfix] postfix: default install vulnerable for POODLE TLS attack Severity set to 'normal' from 'critical' -- 767203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767203 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#767203: postfix: default install vulnerable for POODLE TLS attack
Control: severity -1 normal On Wed, Oct 29, 2014 at 10:45:59 +0100, Joost van Baal-Ilić wrote: package: postfix version: 2.9.6-2 tag: upstream severity: critical Hi, The Postfix Debian package ships with a default list of supported TLS protocols which makes it vulnerable to the POODLE TLS attack: The postfix debian package uses libssl, which has disabled sslv3 in 1.0.1j-1. Cheers, Julien signature.asc Description: Digital signature
Bug#765834: marked as done (pitivi: dependancies requierement unsuffisant)
Your message dated Wed, 29 Oct 2014 10:20:22 + with message-id e1xjqmy-0004cm...@franck.debian.org and subject line Bug#760710: fixed in pitivi 0.93-4.2 has caused the Debian Bug report #760710, regarding pitivi: dependancies requierement unsuffisant 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.) -- 760710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: pitivi: dependancies requierement unsuffisant Package: pitivi Version: 0.93-4.1 Justification: renders package unusable Severity: grave When launching on old installation, PiTiVi doesn't start with following error message : ERROR - The following hard dependencies are unmet: == - Clutter version 1.10.8 is installed but Pitivi requires at least version 1.12.0 - Gtk version 3.4.2 is installed but Pitivi requires at least version 3.8.0 Missing soft dependency: - pycanberra not found on the system - active les notifications sonores lorsque le rendu est terminé Missing soft dependency: - GnomeDesktop not found on the system - file thumbnails provided by GNOME's thumbnailers Missing soft dependency: - Notify not found on the system - active les notifications visuelles lorsque le rendu est terminé Missing soft dependency: - libav not found on the system - codecs multimédias supplémentaires de la bibliothèque Libav Please add requierement version for packages gir1.2-gtk-3.0 and gir1.2-clutter-1.0 . Thanks -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (100, 'experimental'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pitivi depends on: ii gir1.2-clutter-1.0 1.18.2-2 ii gir1.2-clutter-gst-2.0 2.0.12-1 ii gir1.2-gdkpixbuf-2.02.30.7-1 ii gir1.2-ges-1.0 1.2.1-1 ii gir1.2-glib-2.0 1.40.0-2 ii gir1.2-gst-plugins-base-1.0 1.4.3-1 ii gir1.2-gstreamer-1.01.4.3-1 ii gir1.2-gtk-3.0 3.12.2-1+b1 ii gir1.2-gtkclutter-1.0 1.6.0-1 ii gir1.2-pango-1.01.36.3-1 ii gnome-icon-theme3.12.0-1 ii gstreamer1.0-gnonlin1.2.1-1 ii gstreamer1.0-plugins-base 1.4.0-1 ii gstreamer1.0-plugins-good [gstreamer1.0-videosink] 1.4.0-1 pn gstreamer1.0-pulseaudio | gstreamer1.0-audiosinknone ii gstreamer1.0-x [gstreamer1.0-videosink] 1.4.0-1 ii libc6 2.19-9 ii libcairo2 1.12.16-3 ii python 2.7.8-1 ii python-cairo1.8.8-1+b2 ii python-dbus 1.2.0-2+b3 ii python-gi 3.12.1-1+b1 ii python-gi-cairo 3.12.1-1+b1 ii python-gst-1.0 1.2.1-1.1 ii python-matplotlib 1.3.1-2 ii python-numpy1:1.8.2-2 ii python-xdg 0.25-4 pitivi recommends no packages. Versions of packages pitivi suggests: pn frei0r-plugins none pn gir1.2-gnomedesktop-3.0none pn gir1.2-notify-0.7 none pn gstreamer1.0-libav none pn gstreamer1.0-plugins-bad none pn gstreamer1.0-plugins-ugly none -- no debconf information ---End Message--- ---BeginMessage--- Source: pitivi Source-Version: 0.93-4.2 We believe that the bug you reported is fixed in the latest version of pitivi, 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 760...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Jyrinki t...@debian.org (supplier of updated pitivi package)
Bug#760710: marked as done (pitivi : Missing pycanberra module)
Your message dated Wed, 29 Oct 2014 10:20:22 + with message-id e1xjqmy-0004cm...@franck.debian.org and subject line Bug#760710: fixed in pitivi 0.93-4.2 has caused the Debian Bug report #760710, regarding pitivi : Missing pycanberra module 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.) -- 760710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: pitivi version: 0.93-4.1 severity: serious Hi Here's is the stack when launching pitivi just upgraded from experimental : Missing soft dependency: - pycanberra not found on the system - enables sound notifications when rendering is complete /usr/lib/python2.7/dist-packages/gi/overrides/__init__.py:175: Warning: The property GSettings:schema is deprecated and shouldn't be used anymore. It will be removed in a future version. return super_init_func(self, **new_kwargs) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/mainwindow.py:340: Warning: The property GtkMisc:xalign is deprecated and shouldn't be used anymore. It will be removed in a future version. self.menu = self.uimanager.get_widget(/MainMenuBar) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/mainwindow.py:340: Warning: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version. self.menu = self.uimanager.get_widget(/MainMenuBar) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/medialibrary.py:136: Warning: The property GtkWidget:margin-left is deprecated and shouldn't be used anymore. It will be removed in a future version. builder.add_from_file(os.path.join(get_ui_dir(), medialibrary.ui)) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/medialibrary.py:183: Warning: The property GtkTreeView:rules-hint is deprecated and shouldn't be used anymore. It will be removed in a future version. self.treeview.set_property(rules_hint, True) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/titleeditor.py:605: Warning: The property GtkToolButton:stock-id is deprecated and shouldn't be used anymore. It will be removed in a future version. builder.add_from_file(os.path.join(get_ui_dir(), titleeditor.ui)) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/titleeditor.py:605: Warning: The property GtkColorButton:color is deprecated and shouldn't be used anymore. It will be removed in a future version. builder.add_from_file(os.path.join(get_ui_dir(), titleeditor.ui)) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/titleeditor.py:605: Warning: The property GtkWidget:margin-right is deprecated and shouldn't be used anymore. It will be removed in a future version. builder.add_from_file(os.path.join(get_ui_dir(), titleeditor.ui)) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/titleeditor.py:605: Warning: The property GtkAlignment:left-padding is deprecated and shouldn't be used anymore. It will be removed in a future version. builder.add_from_file(os.path.join(get_ui_dir(), titleeditor.ui)) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/viewer.py:194: Warning: The property GtkAlignment:xscale is deprecated and shouldn't be used anymore. It will be removed in a future version. boxalign = Gtk.Alignment(xalign=0.5, yalign=0.5, xscale=0.0, yscale=0.0) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/viewer.py:194: Warning: The property GtkAlignment:yalign is deprecated and shouldn't be used anymore. It will be removed in a future version. boxalign = Gtk.Alignment(xalign=0.5, yalign=0.5, xscale=0.0, yscale=0.0) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/viewer.py:194: Warning: The property GtkAlignment:yscale is deprecated and shouldn't be used anymore. It will be removed in a future version. boxalign = Gtk.Alignment(xalign=0.5, yalign=0.5, xscale=0.0, yscale=0.0) (pitivi:11969): Gdk-WARNING **: gdk_window_set_icon_list: icons too large /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/dialogs/startupwizard.py:61: Warning: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version. self.builder.add_from_file(os.path.join(get_ui_dir(), startupwizard.ui)) /usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/dialogs/startupwizard.py:61: Warning: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version. self.builder.add_from_file(os.path.join(get_ui_dir(), startupwizard.ui)) Traceback (most recent call last): File /usr/bin/pitivi, line 136, in module _run_pitivi() File /usr/bin/pitivi, line 123, in _run_pitivi
Bug#763961: marked as done (pitivi: Pitivi doesn't start, please update from upstream)
Your message dated Wed, 29 Oct 2014 10:20:22 + with message-id e1xjqmy-0004cz...@franck.debian.org and subject line Bug#763961: fixed in pitivi 0.93-4.2 has caused the Debian Bug report #763961, regarding pitivi: Pitivi doesn't start, please update from upstream 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.) -- 763961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pitivi Version: 0.93-4.1 Severity: grave Justification: renders package unusable pitivi is currently unusable due to the following bug: https://bugzilla.gnome.org/show_bug.cgi?id=735529 It's fixed upstream, please release a new minor version of 0.93. Thanks Federico -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pitivi depends on: ii gir1.2-clutter-1.0 1.20.0-1 ii gir1.2-clutter-gst-2.0 2.0.12-1 ii gir1.2-gdkpixbuf-2.02.30.8-1+b1 ii gir1.2-ges-1.0 1.2.1-1 ii gir1.2-glib-2.0 1.42.0-2 ii gir1.2-gst-plugins-base-1.0 1.4.3-1 ii gir1.2-gstreamer-1.01.4.3-1 ii gir1.2-gtk-3.0 3.14.1-1 ii gir1.2-gtkclutter-1.0 1.6.0-1 ii gir1.2-pango-1.01.36.8-1 ii gnome-icon-theme3.12.0-1 ii gstreamer1.0-gnonlin1.2.1-1 ii gstreamer1.0-plugins-bad [gstreamer1.0-videosink] 1.4.3-1 ii gstreamer1.0-plugins-base 1.4.3-1 ii gstreamer1.0-plugins-good [gstreamer1.0-videosink] 1.4.3-1 ii gstreamer1.0-pulseaudio [gstreamer1.0-audiosink]1.4.3-1 ii gstreamer1.0-x [gstreamer1.0-videosink] 1.4.3-1 ii libc6 2.19-11 ii libcairo2 1.12.16-5 ii python 2.7.8-1 ii python-cairo1.8.8-1+b2 ii python-dbus 1.2.0-2+b3 ii python-gi 3.14.0-1 ii python-gi-cairo 3.14.0-1 ii python-gst-1.0 1.2.1-1.1 ii python-matplotlib 1.3.1-2 ii python-numpy1:1.8.2-2 ii python-xdg 0.25-4 pitivi recommends no packages. Versions of packages pitivi suggests: pn frei0r-plugins none ii gir1.2-gnomedesktop-3.03.14.0-1 ii gir1.2-notify-0.7 0.7.6-2 ii gstreamer1.0-libav 1.4.3-1 ii gstreamer1.0-plugins-bad 1.4.3-1 ii gstreamer1.0-plugins-ugly 1.4.3-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: pitivi Source-Version: 0.93-4.2 We believe that the bug you reported is fixed in the latest version of pitivi, 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 763...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Jyrinki t...@debian.org (supplier of updated pitivi 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, 29 Oct 2014 12:06:05 +0200 Source: pitivi Binary: pitivi Architecture: source i386 Version: 0.93-4.2 Distribution: unstable Urgency: medium Maintainer: Loic Minier l...@dooz.org Changed-By: Timo Jyrinki t...@debian.org Description: pitivi - non-linear audio/video editor using GStreamer Closes: 760710 763961 Changes: pitivi (0.93-4.2) unstable; urgency=medium . * Non-maintainer upload. * Import Ubuntu patches to fix issues (Closes: #763961) (Closes: #760710) -
Bug#767209: bibletime: FTBFS on s390x (relocation truncated to fit)
Source: bibletime Version: 2.10.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on the s390x buildd: /usr/bin/c++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -ggdb -Wl,-z,relro CMakeFiles/bibletime.dir/src/backend/btmoduletreeitem.cpp.o CMakeFiles/bibletime.dir/src/backend/cswordmodulesearch.cpp.o CMakeFiles/bibletime.dir/src/backend/btinstallbackend.cpp.o CMakeFiles/bibletime.dir/src/backend/btinstallmgr.cpp.o CMakeFiles/bibletime.dir/src/backend/btinstallthread.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/btbookshelffiltermodel.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/btbookshelfmodel.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/btbookshelftreemodel.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/categoryitem.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/indexingitem.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/item.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/languageitem.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/moduleitem.cpp.o CMakeFiles/bibletime.dir/src/backend/config/btconfig.cpp.o CMakeFiles/bibletime.dir/src/backend/config/btconfigcore.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordbiblemoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordbookmoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordcommentarymoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordlexiconmoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordmoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/gbftohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/osistohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/plaintohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/teitohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/thmltohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/thmltoplain.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/btosismorphsegmentation.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordkey.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordldkey.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordtreekey.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordversekey.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cbookdisplay.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cchapterdisplay.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cdisplayrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/centrydisplay.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/chtmlexportrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cplaintextexportrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/ctextrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/btstringmgr.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/cdisplaytemplatemgr.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/clanguagemgr.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/cswordbackend.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/referencemanager.cpp.o CMakeFiles/bibletime.dir/src/util/cresmgr.cpp.o CMakeFiles/bibletime.dir/src/util/directory.cpp.o CMakeFiles/bibletime.dir/src/util/btmodules.cpp.o CMakeFiles/bibletime.dir/src/util/geticon.cpp.o CMakeFiles/bibletime.dir/src/util/tool.cpp.o CMakeFiles/bibletime.dir/src/bibletime.cpp.o CMakeFiles/bibletime.dir/src/bibletime_dbus.cpp.o CMakeFiles/bibletime.dir/src/bibletime_dbus_adaptor.cpp.o CMakeFiles/bibletime.dir/src/bibletime_init.cpp.o CMakeFiles/bibletime.dir/src/bibletime_slots.cpp.o CMakeFiles/bibletime.dir/src/bibletimeapp.cpp.o CMakeFiles/bibletime.dir/src/btglobal.cpp.o CMakeFiles/bibletime.dir/src/main.cpp.o CMakeFiles/bibletime.dir/src/frontend/btaboutdialog.cpp.o CMakeFiles/bibletime.dir/src/frontend/btaboutmoduledialog.cpp.o CMakeFiles/bibletime.dir/src/frontend/btbookshelfdockwidget.cpp.o CMakeFiles/bibletime.dir/src/frontend/btbookshelfgroupingmenu.cpp.o CMakeFiles/bibletime.dir/src/frontend/btbookshelfview.cpp.o CMakeFiles/bibletime.dir/src/frontend/btbookshelfwidget.cpp.o CMakeFiles/bibletime.dir/src/frontend/btmenuview.cpp.o CMakeFiles/bibletime.dir/src/frontend/btmodulechooserdialog.cpp.o CMakeFiles/bibletime.dir/src/frontend/btmoduleindexdialog.cpp.o CMakeFiles/bibletime.dir/src/frontend/btopenworkaction.cpp.o CMakeFiles/bibletime.dir/src/frontend/cexportmanager.cpp.o CMakeFiles/bibletime.dir/src/frontend/cinfodisplay.cpp.o CMakeFiles/bibletime.dir/src/frontend/cmdiarea.cpp.o CMakeFiles/bibletime.dir/src/frontend/cprinter.cpp.o CMakeFiles/bibletime.dir/src/frontend/crossrefrendering.cpp.o CMakeFiles/bibletime.dir/src/frontend/messagedialog.cpp.o
Bug#767210: matplotlib: FTBFS on kfreebsd-i386 and s390x
Source: matplotlib Version: 1.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on the kfreebsd-i386 and s390x buildds: Build killed with signal TERM after 150 minutes of inactivity See the logs at https://buildd.debian.org/status/logs.php?pkg=matplotlibver=1.4.2-1suite=sid Cheers, Julien signature.asc Description: Digital signature
Bug#767212: pillow: FTBFS on mips (hang during tests)
Source: pillow Version: 2.6.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package failed to build on the mips buildd: BEGIN python2.7-dbg tests cd tmp python2.7-dbg ../debian/test-built.py --processes=1 --process-timeout=90 Tests/test_imagecolor.py Tests/test_pyroma.py Tests/test_imagesequence.py Tests/test_file_webp_alpha.py Tests/test_imagecms.py Tests/test_image_tobitmap.py Tests/test_imageqt.py Tests/test_file_ppm.py Tests/test_image_putalpha.py Tests/test_file_webp_metadata.py Tests/test_file_eps.py Tests/test_image_filter.py Tests/test_file_fli.py Tests/test_000_sanity.py Tests/test_imagefile.py Tests/test_file_icns.py Tests/test_image_array.py Tests/test_decompression_bomb.py Tests/test_image_getbands.py Tests/test_image.py Tests/test_file_tiff.py Tests/test_lib_pack.py Tests/test_image_getim.py Tests/test_image_putdata.py Tests/test_file_webp_lossless.py Tests/test_imageshow.py Tests/test_lib_image.py Tests/test_file_psd.py Tests/test_imagetk.py Tests/test_image_frombytes.py Tests/test_image_getcolors.py Tests/test_file_png.py Tests/test_image_getextrema.py Tests/test_image_getdata.py Tests/test_imageops.py Tests/test_image_getpalette.py Tests/test_image_putpalette.py Tests/test_image_transform.py Tests/test_file_jpeg2k.py Tests/test_file_libtiff.py Tests/test_format_lab.py Tests/test_locale.py Tests/test_file_gimpgradient.py Tests/test_image_thumbnail.py Tests/test_file_sgi.py Tests/test_file_xpm.py Tests/test_image_getprojection.py Tests/test_image_histogram.py Tests/test_imageops_usm.py Tests/test_file_mpo.py Tests/test_imagepalette.py Tests/test_image_mode.py Tests/test_image_copy.py Tests/test_file_pdf.py Tests/test_file_tar.py Tests/test_image_transpose.py Tests/test_file_sun.py Tests/test_imagefileio.py Tests/test_file_webp.py Tests/test_imagepath.py Tests/test_imagestat.py Tests/test_file_gif.py Tests/test_bmp_reference.py Tests/test_mode_i16.py Tests/test_file_palm.py Tests/test_imagedraw.py Tests/test_image_tobytes.py Tests/test_imageenhance.py Tests/test_image_point.py Tests/test_file_tga.py Tests/test_file_tiff_metadata.py Tests/test_file_cur.py Tests/test_imagemorph.py Tests/test_format_hsv.py Tests/test_imagefont.py Tests/test_shell_injection.py Tests/test_imagewin.py Tests/test_image_getpixel.py Tests/test_image_putpixel.py Tests/test_file_xbm.py Tests/test_image_offset.py Tests/test_image_rotate.py Tests/test_file_msp.py Tests/test_imagechops.py Tests/test_file_dcx.py Tests/test_file_spider.py Tests/test_file_iptc.py Tests/test_file_ico.py Tests/test_file_libtiff_small.py Tests/test_image_resize.py Tests/test_image_getbbox.py Tests/test_olefileio.py Tests/test_font_pcf.py Tests/test_image_draft.py Tests/test_font_bdf.py Tests/test_numpy.py Tests/test_imagegrab.py Tests/test_cffi.py Tests/test_image_split.py Tests/test_scipy.py Tests/test_util.py Tests/test_image_crop.py Tests/test_file_jpeg.py Tests/test_file_bmp.py Tests/test_image_load.py Tests/test_pickle.py Tests/test_image_convert.py Tests/test_imagemath.py Tests/test_image_quantize.py Tests/test_file_pcx.py ..S...make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs make: *** wait: No child processes. Stop. Build killed with signal TERM after 300 minutes of inactivity See the build log at https://buildd.debian.org/status/fetch.php?pkg=pillowarch=mipsver=2.6.1-1stamp=1414045002 Cheers, Julien signature.asc Description: Digital signature
Bug#766956: postgresql: 9.4 not released upstream
On Mon, Oct 27, 2014 at 11:48:37AM +0100, Christoph Berg wrote: If so that'd solve the apparent problem. It won't prevent the following scenario though: - Jessie is released with PG 9.4.betaX - PG releases 9.4.betaX+1 which requires a dump/restore cycle due to a catalog bump (PG doesn't guarantuee catalog stability across betas as much as across released minors) - now people running PG on Debian STABLE need to dump/restore their clusters This was the last 9.4 catversion bump. Just FYI: Andrew Dunstan pushed: - Correct volatility markings of a few json functions. json_agg and json_object_agg and their associated transition functions should have been marked as stable rather than immutable, as they call IO functions indirectly. Changing this probably isn't going to make much difference, as you can't use an aggregate function in an index expression, but we should be correct nevertheless. json_object, on the other hand, should be marked immutable rather than stable, as it does not call IO functions. As discussed on -hackers, this change is being made without bumping the catalog version, as we don't want to do that at this stage of the cycle, and the changes are very unlikely to affect anyone. http://git.postgresql.org/pg/commitdiff/af2b8fd057213f4b1918b9581c63e0b00427573c So it's not like it can't happen. Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767210: matplotlib: FTBFS on kfreebsd-i386 and s390x
Hello Julien, thanks for the report. On Wed, Oct 29, 2014 at 10:38 AM, Julien Cristau jcris...@debian.org wrote: Source: matplotlib Version: 1.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on the kfreebsd-i386 and s390x buildds: Build killed with signal TERM after 150 minutes of inactivity See the logs at https://buildd.debian.org/status/logs.php?pkg=matplotlibver=1.4.2-1suite=sid I saw that happening before during the first round of 1.4.x uploads, but it seems it was fixed just by giving it back? https://buildd.debian.org/status/logs.php?pkg=matplotlibarch=kfreebsd-i386 failed in 1.4.1~rc1 with the same error and then succeeded https://buildd.debian.org/status/logs.php?pkg=matplotlibarch=s390x succeeded with 1.4.1~rc1 but failed in the last 2 uploads https://buildd.debian.org/status/logs.php?pkg=matplotlib 1.4.1~rc1 also failed on i386 and then went on correctly on the other upload I will look into it, but could it be something specific to those build machines and or build setup? Thanks, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767216: There is not enough free space on the device to save file
Package: bless Version: 0.6.0-4 Severity: grave AFAIK there is no way to use bless to edit and save a file. Steps from a jessie/amd64 setup: $ wget http://www.ece.rice.edu/~wakin/images/lena512.pgm $ bless lena512.pgm Directory '/home/mathieu/.config/bless/plugins' not found. Directory '/home/mathieu/.config/bless/plugins' not found. Directory '/home/mathieu/.config/bless/plugins' not found. Could not find file /home/mathieu/.config/bless/export_patterns. - Hit 'Suppr' (why not) - Hit 'Ctrl+S' A message box comes up saying: [...] Error saving file '/tmp/lena512.pgm' There is not enough free space on the device to save file 'auhnfpnt.bless' [...] Marking as grave since writing edited file, quite important for user (render package mostly unusable). Regards. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Alternate file ok
Processing control commands: severity -1 important Bug #767216 [bless] There is not enough free space on the device to save file Severity set to 'important' from 'grave' -- 767216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767216 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#622394: Fix works on NFS clients but breaks NFS servers
Hi, I applied the fix given in message #10 to a few of our Jessie systems. I can confirm that it fixes the boot order problem on NFS clients that mount remote filesystems on boot (before the fix, it was trying to mount an NFS /home directory before rpcbind was started, which failed). However, the same fix seems to break NFS servers because it tries to start statd before rpcbind: Oct 29 09:48:49 drbl nfs-common[140]: Starting NFS common utilities: statd Oct 29 09:48:49 drbl nfs-common[140]: Not starting: portmapper is not running ... (warning). This failure to start later manifested as lockd: cannot monitor client errors. -- Chris Butler Zedcore Systems Ltd -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767216: Alternate file ok
Control: severity -1 important
Actually I can save to a dummy file instead ('Save As') and it just
works. Would be nice to have in-place editing working though. Lowering
severity.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767210: matplotlib: FTBFS on kfreebsd-i386 and s390x
On 29/10/14 11:54, Sandro Tosi wrote: Hello Julien, thanks for the report. On Wed, Oct 29, 2014 at 10:38 AM, Julien Cristau jcris...@debian.org wrote: Source: matplotlib Version: 1.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on the kfreebsd-i386 and s390x buildds: Build killed with signal TERM after 150 minutes of inactivity See the logs at https://buildd.debian.org/status/logs.php?pkg=matplotlibver=1.4.2-1suite=sid I saw that happening before during the first round of 1.4.x uploads, but it seems it was fixed just by giving it back? https://buildd.debian.org/status/logs.php?pkg=matplotlibarch=kfreebsd-i386 failed in 1.4.1~rc1 with the same error and then succeeded https://buildd.debian.org/status/logs.php?pkg=matplotlibarch=s390x succeeded with 1.4.1~rc1 but failed in the last 2 uploads https://buildd.debian.org/status/logs.php?pkg=matplotlib 1.4.1~rc1 also failed on i386 and then went on correctly on the other upload I will look into it, but could it be something specific to those build machines and or build setup? This also failed on i386 recently: https://buildd.debian.org/status/fetch.php?pkg=matplotlibarch=i386ver=1.4.1~rc1-1stamp=1413455146 It may be a race and not something specific to the buildds. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760476: concerning 760476
Hi Nikos, hi Andreas, On Tue, 28 Oct 2014 19:11:28 +0100 Andreas Metzler wrote: On 2014-10-28 Nikos Mavrogiannopoulos n...@gnutls.org wrote: I think that the issue should be reassigned to cups and it should be modified to close the known file descriptors (stdin/stdout/stderr) instead of all open descriptors. Thanks for the explanation. re-assigning. (I will subscribe to the bug-report to keep me updated) Thanks to you two for the investigation; I've brought the issue back up to CUPS's bugtracker, where Michael Sweet wrote on https://www.cups.org/str.php?L4484 : So it looks like you also need to fix GNU TLS to only open /dev/urandom when gnutls_global_init() is called and not before. It appears there's a disagreement between CUPS and GnuTLS on how the file descriptors should be managed. It would be nice if one of you could have the conversation with Michael directly on the CUSP tracker, without me playing the messenger. Nikos: would that be imaginable? TIA, cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767225: regex: don't deref NULL upon heap allocation failure
Package: libc6 Version: 2.19-11 Severity: serious please backport the fix for https://sourceware.org/bugzilla/show_bug.cgi?id=17150 -- Mit freundlichen Grüßen Bernd Zeimetz Systems Engineer Debian Developer conova communications GmbH Web| http://www.conova.com/ E-Mail | b.zeim...@conova.com Zentrale Salzburg Karolingerstraße 36A 5020 Salzburg Tel | +43 (0) 662 22 00 - 313 Fax | +43 (0) 662 22 00 - 209 Es gelten die Allgemeinen Geschäftsbedingungen der conova communications GmbH, http://www.conova.com/de/agb/ smime.p7s Description: S/MIME cryptographic signature
Processed: Re: reclass: ABI changed: should not enter testing before reverse dependency adapted
Processing commands for cont...@bugs.debian.org: retitle 766903 reclass: accidental ABI change: all rdepends need new ABI Bug #766903 [reclass] reclass: ABI changed: should not enter testing before reverse dependency adapted Changed Bug title to 'reclass: accidental ABI change: all rdepends need new ABI' from 'reclass: ABI changed: should not enter testing before reverse dependency adapted' found 766903 1.3-2 Bug #766903 [reclass] reclass: accidental ABI change: all rdepends need new ABI Marked as found in versions reclass/1.3-2. notfound 766903 1.4-1 Bug #766903 [reclass] reclass: accidental ABI change: all rdepends need new ABI No longer marked as found in versions reclass/1.4-1. thanks Stopping processing here. Please contact me if you need assistance. -- 766903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766903 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#766903: marked as done (reclass: accidental ABI change: all rdepends need new ABI)
Your message dated Wed, 29 Oct 2014 01:55:47 +0100 with message-id 20141029005547.15411.75...@bastian.jones.dk and subject line Re: reclass: ABI changed: should not enter testing before reverse dependency adapted has caused the Debian Bug report #766903, regarding reclass: accidental ABI change: all rdepends need new ABI 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.) -- 766903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: reclass Version: 1.4-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Reclass 1.4 changes backwards-incompatibly its data format - specifically changing default class name from index to . This change is not mentioned in upstream changelog at http://reclass.pantsfullofunix.net/changelog.html but documented in the commit https://github.com/madduck/reclass/commit/15e72de: Use init as directory index The docs mentioned 'init' (which is consistent with Salt and Python), but somehow I made that 'index' in the code. The package reeclass has one reverse dependency, boxer, which is a build-dependency of two source packages debian-design and debian-parl, both of which FTBFS as a consequence of this change. Reclass 1.4-1 should therefore not enter testing before its reverse dependency has been adapted to use the new ABI. Alternatively, reclass could be adapted to support the previous index as fallback when init does not exist: That would be adequate for use by boxer, since the new init happens to not be used in the boxer-data classes currently in Debian. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUTTn8XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWgVUIAJmH1DbjqaWUNTMhU+uSc5ZK +FttTFVdUePwTJeMJCs0oLoWWm0X9yj/2zXIvWLk2VCk9f8C38cPUuYggZnGGk1D Wp7cdBwKNB2xoX55QRZWgQC4mfFHcRENhTYsTMLRQV1qlAGKeWUzYJFqumX7A+oO NTYC4QlNeP599tZjhbRwGQcypETGdSqhXdPFIIgzyNnevp2AmTfifAZXXvb2R6tj rNOmCQMYPo4YpZFa0PS6JKpHVLn/WLDu2HV4tLOGsx81rr7YmQXfC8C7UDde+yqs OZ64qrMN330zuQ7Z+rVdgg3fmAyNNXMSN/LaFiTDw+veXu+tylW7rpSpiJsnx+Q= =Mdv/ -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- retitle 766903 reclass: accidental ABI change: all rdepends need new ABI found 766903 1.3-2 notfound 766903 1.4-1 thanks Quoting Jonas Smedegaard (2014-10-26 20:50:27) Quoting Jonas Smedegaard (2014-10-26 19:14:23) Reclass 1.4 changes backwards-incompatibly its data format - specifically changing default class name from index to . [...] Reclass 1.4-1 should therefore not enter testing before its reverse dependency has been adapted to use the new ABI. Alternatively, reclass could be adapted to support the previous index as fallback when init does not exist: That would be adequate for use by boxer, since the new init happens to not be used in the boxer-data classes currently in Debian. Update: I now released boxer-data 6 adapted to reclass 1.4 ABI. I suggest the following plan: 1) We keep this bug open and at high severity until we can reasonably estimate which packages will enter testing before freeze. (Release team probably announces when freze - 10 days is passed) 2a) If likely that both reclass and boxer-data will make it in time, we close this bugreport. 2b) If likely that reclass will make it in time but not boxer-data, we keep this bugreport open and request freeze exception, referring to this bugreport as the reason. 3) If estimate turned out to be wrong, we reopen this bugreport and request freeze exception. Change of plan: Seems boxer-data 6 will make it in time, which means it now require new ABI - and a bug in reclass 1.4-1 required an update that won't make it without help, so tag this bug to indicate the opposite status as originally: Old version is broken, new is correct. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature ---End Message---
Bug#713331: sphinxsearch: FTBFS: [automake-1.13 warning: linking libraries using a, non-POSIX]
On Tue, 21 Oct 2014 18:36:58 +0530 Brahadambal Srinivasan la...@linux.vnet.ibm.com wrote: Package: sphinxsearch Version: 2.0.4-1.1 Followup-For: Bug #713331 Tags: patch X-Debbugs-Cc: bren...@br.ibm.com User: debian-powe...@lists.debian.org Usertags: ppc64el User: debian-de...@lists.debian.org Usertags: autoreconf Dear Maintainer, The package sphinxsearch fails to build on ppc64le, because of changes required in libtool, aclocal.m4 and configure.ac. This patch includes autotools-dev and a couple of changes in configure.ac to the package so that it builds correctly. Thanks for considering the patch! I tested your patch on mips64el, it works well. Thanks and regards, Brahadambal -- System Information: *** End of the template - remove these template lines *** Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16-trunk-powerpc64le (SMP w/32 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760476: concerning 760476
On Wed, Oct 29, 2014 at 1:02 PM, Didier 'OdyX' Raboud o...@debian.org wrote: Hi Nikos, hi Andreas, On Tue, 28 Oct 2014 19:11:28 +0100 Andreas Metzler wrote: On 2014-10-28 Nikos Mavrogiannopoulos n...@gnutls.org wrote: I think that the issue should be reassigned to cups and it should be modified to close the known file descriptors (stdin/stdout/stderr) instead of all open descriptors. Thanks for the explanation. re-assigning. (I will subscribe to the bug-report to keep me updated) Thanks to you two for the investigation; I've brought the issue back up to CUPS's bugtracker, where Michael Sweet wrote on https://www.cups.org/str.php?L4484 : So it looks like you also need to fix GNU TLS to only open /dev/urandom when gnutls_global_init() is called and not before. It appears there's a disagreement between CUPS and GnuTLS on how the file descriptors should be managed. It would be nice if one of you could have the conversation with Michael directly on the CUSP tracker, without me playing the messenger. Nikos: would that be imaginable? Ok, I'll try to. I really hate that register to reply. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767156: marked as done (imagemagick: FTBFS: B-D on inkscape problematic)
Your message dated Wed, 29 Oct 2014 14:40:56 +0100 with message-id CAE2SPAZUyXgDBa+NhO+XUq+sVwVJTk=vyydmyrvy-dwwm9n...@mail.gmail.com and subject line Done has caused the Debian Bug report #767156, regarding imagemagick: FTBFS: B-D on inkscape problematic 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.) -- 767156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: imagemagick Version: 8:6.8.9.9-1 Severity: serious Justification: fails to build from source (but built successfully in the past) imagemagick declares a build dependency on inkscape, which in turn depends on libmagick*-6.q16-*. This B-D is a problem even when inkscape is already available: imagemagick build-depends on: - inkscape inkscape depends on: - libmagick++-6.q16-5 (= 8:6.8.9.6) libmagick++-6.q16-5 depends on: - libmagickcore-6.q16-2 (= 8:6.8.9.6) libmagickcore-6.q16-2 depends on missing: - imagemagick-common (= 8:6.8.9.6-4) It looks like the autobuilders could only find imagemagick-common 8:6.8.9.9-1. Perhaps the relevant infrastructure (on incoming.d.o?) should be configured to keep architecture-independent packages in sync with architecture-dependent packages from the same source. However, this circularity would still require manual intervention when boostrapping. I'd suggest moving inkscape to Build-Depends-Indep, so that it will still show up in the delegates.xml on user systems. Could you please take a look? Thanks! ---End Message--- ---BeginMessage--- Version: 8:6.8.9.9-2 Closed with newer imagemagick version---End Message---
Bug#767230: bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0
Package: bitlbee-plugin-otr Version: 3.2.2-2 Severity: grave Justification: renders package unusable After the latest bitlbee-plugin-otr upgrade, bitlbee no longer starts. In syslog I see the following line: bitlbee[3405]: Starting BitlBee IRC/IM gateway: bitlbeeExpected libotr API version 4.1.0 incompatible with actual version 4.0.0. Aborting. Looks like bitlbee-plugin-otr misses a properly versioned dependency against libotr5. libotr5 4.1.0 is only available in unstable but not in testing. Cheers -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-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 bitlbee-plugin-otr depends on: ii bitlbee 3.2.2-2+b1 ii bitlbee-common 3.2.2-2 ii libc6 2.19-12 ii libotr5 4.0.0-3+b1 bitlbee-plugin-otr recommends no packages. bitlbee-plugin-otr suggests no packages. -- no debconf information -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#741451: Bugfix
On Tue, Oct 28, 2014 at 7:13 PM, Tomasz Buchert tomasz.buch...@inria.fr wrote: Hi, I've worked on that bug today's evening and I found a fairly simple fix. Thanks Tomasz ! Jay, are you going to submit the debdiff as-is ? Are you forwarding the issue upstream ? I do not have the time to prepare an NMU ATM, sorry. -M -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767230: bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0
This should fix itself when libotr5 4.1 enters testing. I'm told that irssi-otr and pidgin have exactly the same issue. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+ signature.asc Description: Digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags 741451 patch Bug #741451 [libtiff-tools] tiffcp: malloc(): memory corruption: 0x7f732ee68d90 Added tag(s) patch. End of message, stopping processing here. Please contact me if you need assistance. -- 741451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741451 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#750857: NMU debdiff for mod-gnutls_0.6-1.1
Hello, I am preparing a patch for this. Regards, Jurica
Processed: Three security bug in imagemagick
Processing control commands: tag -1 + security Bug #767240 [imagemagick] Three security bug in imagemagick Added tag(s) security. -- 767240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767240 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#752514: Bug #752514: ruby-fftw3: FTBFS on armhf
The build failure on the buildds may be caused by this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767138 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767240: Three security bug in imagemagick
package: imagemagick version: 8:6.6.0.4-3 severity: serious control: tag -1 + security This is a bug for tracking : TEMP-000-77B6EF buffer overflow in PCX and DCM coder TEMP-000-3CE5AC Off-by-one count when parsing an 8BIM profile TEMP-000-1800A5 Don't clone a 0x0 image breaking some assumption Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767230: bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0
Control: reassign -1 libotr5 4.1.0-1
Control: tags -1 + patch
Control: affects -1 bitlbee-plugin-otr
On 2014-10-29 13:48:00, Wilmer van der Gaast wrote:
This should fix itself when libotr5 4.1 enters testing. I'm told that
irssi-otr and pidgin have exactly the same issue.
Oh, I see. The check is in libotr. src/proto.c has the following lines
in otrl_init:
if (ver_major != OTRL_VERSION_MAJOR || ver_minor OTRL_VERSION_MINOR) {
»»fprintf(stderr, Expected libotr API version %u.%u.%u incompatible
with actual version %u.%u.%u. Aborting.\n,
ver_major, ver_minor, ver_sub,
OTRL_VERSION_MAJOR, OTRL_VERSION_MINOR, OTRL_VERSION_SUB);
»»return gcry_error(GPG_ERR_INV_VALUE);
}
and in src/proto.h:
#define OTRL_INIT do { \
»»if (otrl_init(OTRL_VERSION_MAJOR, OTRL_VERSION_MINOR, \
OTRL_VERSION_SUB)) { \
»»exit(1); \
»»} \
} while(0)
Calling OTRL_INIT is apparently the recommend way to initialize libotr.
However, this causes issues if a program is built against libotr 4.1 but
used with libotr 4.0 as it just happend to bitlbee-plugin-otr. The
package built against libotr 4.1.0 migrated to testing before libotr
4.1.0-1 since the appropriate versioned dependencies are missing.
The attached patch uses shlibs to generate the proper dependencies.
Cheers
--
Sebastian Ramacher
diff -Nru libotr-4.1.0/debian/changelog libotr-4.1.0/debian/changelog
--- libotr-4.1.0/debian/changelog 2014-10-21 22:26:51.0 +0200
+++ libotr-4.1.0/debian/changelog 2014-10-29 15:29:55.0 +0100
@@ -1,3 +1,11 @@
+libotr (4.1.0-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Generate tighter dependencies on libotr5 since the API version is checked
+during runtime.
+
+ -- Sebastian Ramacher sramac...@debian.org Wed, 29 Oct 2014 15:29:35 +0100
+
libotr (4.1.0-1) unstable; urgency=medium
* New upstream release.
diff -Nru libotr-4.1.0/debian/rules libotr-4.1.0/debian/rules
--- libotr-4.1.0/debian/rules 2014-10-21 22:26:51.0 +0200
+++ libotr-4.1.0/debian/rules 2014-10-29 15:31:56.0 +0100
@@ -12,3 +12,6 @@
$(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags
--export=configure)
override_dh_install:
dh_install --fail-missing -X.la
+
+override_dh_makeshlibs:
+ dh_makeshlibs -plibotr5 -V 'libotr5 (= 4.1.0)'
signature.asc
Description: Digital signature
Processed: Re: Bug#767230: bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0
Processing control commands: reassign -1 libotr5 4.1.0-1 Bug #767230 [bitlbee-plugin-otr] bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0 Bug reassigned from package 'bitlbee-plugin-otr' to 'libotr5'. No longer marked as found in versions bitlbee/3.2.2-2. Ignoring request to alter fixed versions of bug #767230 to the same values previously set Bug #767230 [libotr5] bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0 Marked as found in versions libotr/4.1.0-1. tags -1 + patch Bug #767230 [libotr5] bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0 Added tag(s) patch. affects -1 bitlbee-plugin-otr Bug #767230 [libotr5] bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0 Added indication that 767230 affects bitlbee-plugin-otr -- 767230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767230 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#767210: matplotlib: FTBFS on kfreebsd-i386 and s390x
control: forwarded -1 https://github.com/matplotlib/matplotlib/issues/3738 On Wed, Oct 29, 2014 at 11:19 AM, Emilio Pozuelo Monfort po...@debian.org wrote: This also failed on i386 recently: https://buildd.debian.org/status/fetch.php?pkg=matplotlibarch=i386ver=1.4.1~rc1-1stamp=1413455146 It may be a race and not something specific to the buildds. it might indeed, forwarded upstream. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#767210: matplotlib: FTBFS on kfreebsd-i386 and s390x
Processing control commands: forwarded -1 https://github.com/matplotlib/matplotlib/issues/3738 Bug #767210 [src:matplotlib] matplotlib: FTBFS on kfreebsd-i386 and s390x Set Bug forwarded-to-address to 'https://github.com/matplotlib/matplotlib/issues/3738'. -- 767210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767210 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#763769: Thanks
Gregor, I can confirm that the patch you posted fixes at least the reported bug (File/New - crash). Thank you. Since this bug report had seen no activity for almost a month, a non-delayed NMU should be fine. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 767230 is important
Processing commands for cont...@bugs.debian.org: severity 767230 important Bug #767230 [libotr5] bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0 Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 767230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767230 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#761001: Gnome3/Gdm3 gone :-)
Hi Kurt, What is your system (CPU/GPU)? Do you see the same kind of syslog as I quote below? I see linux-kernel mesa and mutter are updated on my system yesterday. Maybe one of these are causing this. Here is my situation. * GDM3 crashes after upgrade yesterday (testing). upgrading to unstable version does not fix. gdm3 3.14.0-1 MIGRATED to testing 2014-10-18 *** suspicious but ... * Logging into GNOME3 (normal and fall back) from KDM crashes. * Logging into XFce (GTK3+) and KDE (Qt) works as long as KDM or lightdm are used. * xorg has not changed since 2014-04-07. So they are not to be blamed. * systemd (logind) has not changed since [2014-10-06] So they are not to be blamed. I have Intel integrated graphics (on Haswell i5) Something specific in the lower level of GNOME3 broke this system. If gdm3 was the real cause, this breakage should have happened before. I found the following in my syslog when GDM3 failed. This is strange. Oct 29 20:19:58 goofy gdm3[639]: Failed to give slave programs access to the display. Trying to proceed. ... Oct 29 20:19:58 goofy /usr/bin/dbus-launch[1020]: Xlib: extension GLX missing on display :0. Oct 29 20:19:58 goofy /usr/bin/dbus-launch[1020]: Xlib: extension GLX missing on display :0. Oct 29 20:19:58 goofy /usr/bin/dbus-launch[1020]: Xlib: extension GLX missing on display :0. Oct 29 20:19:58 goofy /usr/bin/dbus-launch[1020]: gnome-session-is-accelerated: No hardware 3D support. Oct 29 20:19:58 goofy /usr/bin/dbus-launch[1020]: Xlib: extension GLX missing on display :0. Oct 29 20:19:58 goofy /usr/bin/dbus-launch[1020]: gnome-session-check-accelerated: Helper exited with code 256 Looking into apt log: Start-Date: 2014-10-27 01:04:40 Commandline: apt-get dist-upgrade -y Install: linux-image-3.16-3-amd64:amd64 (3.16.5-1, automatic) Upgrade: valac:amd64 (0.26.0-1, 0.26.1-1), empathy-common:amd64 (3.12.6-1, 3.12.7-1), empathy:amd64 (3.12.6-1, 3.12.7-1), gir1.2-evince-3.0:amd64 (3.14.0-2, 3.14.1-1), libblas-common:amd64 (1.2.20110419-9, 1.2.20110419-10), libgee-0.8-dev:amd64 (0.14.0-3, 0.16.1-1), iw:amd64 (3.14-1, 3.17-1), valac-0.26-vapi:amd64 (0.26.0-1, 0.26.1-1), evince:amd64 (3.14.0-2, 3.14.1-1), libblas3:amd64 (1.2.20110419-9, 1.2.20110419-10), valac-0.26:amd64 (0.26.0-1, 0.26.1-1), libgee-0.8-2:amd64 (0.14.0-3, 0.16.1-1), gir1.2-gee-0.8:amd64 (0.14.0-3, 0.16.1-1), gnome-backgrounds:amd64 (3.14.0-1, 3.14.1-1), liblapack3:amd64 (3.5.0-3, 3.5.0-4), evince-common:amd64 (3.14.0-2, 3.14.1-1), libldap-2.4-2:amd64 (2.4.39-1.1+b1, 2.4.40-2), baobab:amd64 (3.14.0-1, 3.14.1-1), dictionaries-common:amd64 (1.23.12, 1.23.14), libevview3-3:amd64 (3.14.0-2, 3.14.1-1), linux-image-amd64:amd64 (3.16+61, 3.16+62), manpages-dev:amd64 (3.71-1, 3.74-1), libvala-0.26-0:amd64 (0.26.0-1, 0.26.1-1), manpages:amd64 (3.71-1, 3.74-1), libevdocument3-4:amd64 (3.14.0-2, 3.14.1-1), linux-libc-dev:amd64 (3.16.3-2, 3.16.5-1), whois:amd64 (5.2.0, 5.2.1) End-Date: 2014-10-27 01:05:23 Start-Date: 2014-10-27 01:05:23 Commandline: apt-get autoremove -y Remove: linux-image-3.14-2-amd64:amd64 (3.14.15-2), libgnutls26:amd64 (2.12.23-17) End-Date: 2014-10-27 01:05:25 Start-Date: 2014-10-27 23:09:26 Commandline: apt-get dist-upgrade Install: libllvm3.5:amd64 (3.5-6, automatic) Upgrade: libio-socket-ssl-perl:amd64 (1.998-1, 2.002-1), libfontembed1:amd64 (1.0.59-1, 1.0.61-2), libegl1-mesa:amd64 (10.2.8-1, 10.3.1-1), libopenvg1-mesa:amd64 (10.2.8-1, 10.3.1-1), libegl1-mesa-drivers:amd64 (10.2.8-1, 10.3.1-1), foomatic-db-compressed-ppds:amd64 (20140730-1, 20141016-1), libgl1-mesa-dri:amd64 (10.2.8-1, 10.3.1-1), openprinting-ppds:amd64 (20140730-1, 20141016-1), libglapi-mesa:amd64 (10.2.8-1, 10.3.1-1), gir1.2-mutter-3.0:amd64 (3.14.0-1, 3.14.1-1), cups-browsed:amd64 (1.0.59-1, 1.0.61-2), libgl1-mesa-glx:amd64 (10.2.8-1, 10.3.1-1), cups-filters-core-drivers:amd64 (1.0.59-1, 1.0.61-2), libxatracker2:amd64 (10.2.8-1, 10.3.1-1), libwayland-egl1-mesa:amd64 (10.2.8-1, 10.3.1-1), cups-filters:amd64 (1.0.59-1, 1.0.61-2), libgbm1:amd64 (10.2.8-1, 10.3.1-1), mutter-common:amd64 (3.14.0-1, 3.14.1-1), libmutter0e:amd64 (3.14.0-1, 3.14.1-1), libcupsfilters1:amd64 (1.0.59-1, 1.0.61-2) End-Date: 2014-10-27 23:09:38 Start-Date: 2014-10-27 23:15:48 Install: locales:amd64 (2.19-11) Remove: libllvm3.4:amd64 (3.4.2-10) End-Date: 2014-10-27 23:15:52 Regards, Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767248: roundcube-core: upgrade sets permissions of debian-db.php to root:root
Package: roundcube Version: 0.9.5+dfsg1-4.1 Severity: grave Justification: renders package unusable The recent upgrade of the package broke roundcube with a permission problem upon reading its configuration. The file /etc/roundcube/debian-db.php was identified as being the culprit. This file is generated by dbconfig-common and should be owned by root:www-data with permissions 0640. After the upgrade, however, it was owned by root:root with permissions 0640 (reproducible on two systems), making it unreadable by the webserver. I got the idea that it might be related to #720517 somehow… As a workaround, this solves the issue: # chown :www-data /etc/roundcube/debian-db.php Credits to Simon Bruder simon.bru...@teckids.org, our 10 year-old infrastructure admin, for stumbling upon this in a dist-upgrade, identifying the origin of the failure in the server logs and helping find out it is dbconfig-common related by reading the postinst script ;). You rock, fellow ☺! Cheers, Nik -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages roundcube-core depends on: ii dbconfig-common1.8.47+nmu2 ii debconf [debconf-2.0] 1.5.53 ii libapache2-mod-php55.6.2+dfsg-1 ii libjs-jquery 1.7.2+dfsg-3.2 ii libmagic1 1:5.19-2 ii php-auth 1.6.4-1 ii php-mail-mime 1.8.9-1 ii php-net-smtp 1.6.2-2 ii php-net-socket 1.0.14-1 ii php5 5.6.2+dfsg-1 ii php5-common5.6.2+dfsg-1 ii php5-intl 5.6.2+dfsg-1 ii php5-json 1.3.6-1 ii php5-mcrypt5.6.2+dfsg-1 ii roundcube-sqlite3 0.9.5+dfsg1-4.1 ii tinymce3.4.8+dfsg0-1 ii ucf3.0030 Versions of packages roundcube-core recommends: ii apache2 [httpd-cgi] 2.4.10-5 ii apache2-mpm-prefork [httpd-cgi] 2.4.10-5 ii apache2-mpm-worker [httpd-cgi] 2.4.10-5 ii php5-gd 5.6.2+dfsg-1 ii php5-pspell 5.6.2+dfsg-1 Versions of packages roundcube-core suggests: ii php-auth-sasl 1.0.6-1 pn php-crypt-gpg none ii roundcube-plugins 0.9.5+dfsg1-4.1 roundcube depends on no packages. -- Configuration Files: /etc/roundcube/apache.conf changed [not included] -- debconf information: roundcube/internal/reconfiguring: false roundcube/remote/newhost: roundcube/reconfigure-webserver: apache2, lighttpd roundcube/mysql/admin-user: root roundcube/db/app-user: * roundcube/database-type: sqlite3 roundcube/db/basepath: /var/lib/dbconfig-common/sqlite3/roundcube roundcube/dbconfig-reinstall: false roundcube/pgsql/changeconf: false roundcube/pgsql/no-empty-passwords: roundcube/mysql/method: unix socket roundcube/pgsql/authmethod-admin: ident roundcube/remote/host: roundcube/pgsql/authmethod-user: password roundcube/dbconfig-upgrade: true roundcube/db/dbname: roundcube roundcube/pgsql/method: unix socket roundcube/missing-db-package-error: abort roundcube/upgrade-backup: true roundcube/purge: false roundcube/hosts: roundcube/language: de_DE roundcube/passwords-do-not-match: roundcube/pgsql/admin-user: postgres roundcube/remove-error: abort roundcube/internal/skip-preseed: false * roundcube/dbconfig-install: true roundcube/pgsql/manualconf: roundcube/install-error: abort roundcube/upgrade-error: abort roundcube/remote/port: roundcube/restart-webserver: true roundcube/dbconfig-remove: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766359: gnome-shell: gdm shows a black screen when upgrading to 3.14.1-1
I'm not certain this bug has been resolved. After upgrading to the mentioned latest packages on sid after login the interface just freezes. Nothing responds. Sometimes 2 black boxes show up (on in the center and one top-left) but the interface is non-responsive non the less. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767240: marked as done (Three security bug in imagemagick)
Your message dated Wed, 29 Oct 2014 16:23:31 +0100 with message-id CAE2SPAbrqdv3=9zhqmdtcvh+xgucnfrqir4jcz1xaqzsyb-...@mail.gmail.com and subject line Fixed in unstable has caused the Debian Bug report #767240, regarding Three security bug in imagemagick 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.) -- 767240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: imagemagick version: 8:6.6.0.4-3 severity: serious control: tag -1 + security This is a bug for tracking : TEMP-000-77B6EF buffer overflow in PCX and DCM coder TEMP-000-3CE5AC Off-by-one count when parsing an 8BIM profile TEMP-000-1800A5 Don't clone a 0x0 image breaking some assumption Bastien ---End Message--- ---BeginMessage--- Version: 8:6.8.9.9-2 Note that TEMP-000-3CE5AC does not affect wheezy and squeeze---End Message---
Bug#767248: roundcube-core: upgrade sets permissions of debian-db.php to root:root
❦ 29 octobre 2014 16:13 +0100, Dominik George dominik.geo...@teckids.org : The recent upgrade of the package broke roundcube with a permission problem upon reading its configuration. The file /etc/roundcube/debian-db.php was identified as being the culprit. This file is generated by dbconfig-common and should be owned by root:www-data with permissions 0640. After the upgrade, however, it was owned by root:root with permissions 0640 (reproducible on two systems), making it unreadable by the webserver. I got the idea that it might be related to #720517 somehow… As a workaround, this solves the issue: # chown :www-data /etc/roundcube/debian-db.php Credits to Simon Bruder simon.bru...@teckids.org, our 10 year-old infrastructure admin, for stumbling upon this in a dist-upgrade, identifying the origin of the failure in the server logs and helping find out it is dbconfig-common related by reading the postinst script ;). You rock, fellow ☺! The postinst script has already a lot of that in it: roundcube-core.postinst:dbc_generate_include_owner=root:www-data roundcube-core.postinst:dbc_dbfile_owner=www-data:www-data. Could you confirm when you did upgrade roundcube? Is it before or after the upgrade of dbconfig-common to 1.8.47+nmu2? -- Document your data layouts. - The Elements of Programming Style (Kernighan Plauger) signature.asc Description: PGP signature
Processed: reassign 767248 to dbconfig-common ...
Processing commands for cont...@bugs.debian.org: reassign 767248 dbconfig-common 1.8.47+nmu2 Bug #767248 [roundcube] roundcube-core: upgrade sets permissions of debian-db.php to root:root Bug reassigned from package 'roundcube' to 'dbconfig-common'. No longer marked as found in versions roundcube/0.9.5+dfsg1-4.1. Ignoring request to alter fixed versions of bug #767248 to the same values previously set Bug #767248 [dbconfig-common] roundcube-core: upgrade sets permissions of debian-db.php to root:root Marked as found in versions dbconfig-common/1.8.47+nmu2. retitle 767248 dbconfig-common: removes any permissions from generated include files on upgrade Bug #767248 [dbconfig-common] roundcube-core: upgrade sets permissions of debian-db.php to root:root Changed Bug title to 'dbconfig-common: removes any permissions from generated include files on upgrade' from 'roundcube-core: upgrade sets permissions of debian-db.php to root:root' thanks Stopping processing here. Please contact me if you need assistance. -- 767248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767248 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#767212: pillow: FTBFS on mips (hang during tests)
On Oct 29, 2014, at 3:41 AM, Julien Cristau jcris...@debian.org wrote: Source: pillow Version: 2.6.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package failed to build on the mips buildd: BEGIN python2.7-dbg tests cd tmp python2.7-dbg ../debian/test-built.py --processes=1 --process-timeout=90 Tests/test_imagecolor.py Tests/test_pyroma.py Tests/test_imagesequence.py Tests/test_file_webp_alpha.py Tests/test_imagecms.py Tests/test_image_tobitmap.py Tests/test_imageqt.py Tests/test_file_ppm.py Tests/test_image_putalpha.py Tests/test_file_webp_metadata.py Tests/test_file_eps.py Tests/test_image_filter.py Tests/test_file_fli.py Tests/test_000_sanity.py Tests/test_imagefile.py Tests/test_file_icns.py Tests/test_image_array.py Tests/test_decompression_bomb.py Tests/test_image_getbands.py Tests/test_image.py Tests/test_file_tiff.py Tests/test_lib_pack.py Tests/test_image_getim.py Tests/test_image_putdata.py Tests/test_file_webp_lossless.py Tests/test_imageshow.py Tests/test_lib_image.py Tests/test_file_psd.py Tests/test_imagetk.py Tests/test_image_frombytes.py Tests/test_image_getcolors.py Tests/test_file_png.py Tests/test_image_getextrema.py Tests/test_image_getdata.py Tests/test_imageops.py Tests/test_image_getpalette.py Tests/test_image_putpalette.py Tests/test_image_transform.py Tests/test_file_jpeg2k.py Tests/test_file_libtiff.py Tests/test_format_lab.py Tests/test_locale.py Tests/test_file_gimpgradient.py Tests/test_image_thumbnail.py Tests/test_file_sgi.py Tests/test_file_xpm.py Tests/test_image_getprojection.py Tests/test_image_histogram.py Tests/test_imageops_usm.py Tests/test_file_mpo.py Tests/test_imagepalette.py Tests/test_image_mode.py Tests/test_image_copy.py Tests/test_file_pdf.py Tests/test_file_tar.py Tests/test_image_transpose.py Tests/test_file_sun.py Tests/test_imagefileio.py Tests/test_file_webp.py Tests/test_imagepath.py Tests/test_imagestat.py Tests/test_file_gif.py Tests/test_bmp_reference.py Tests/test_mode_i16.py Tests/test_file_palm.py Tests/test_imagedraw.py Tests/test_image_tobytes.py Tests/test_imageenhance.py Tests/test_image_point.py Tests/test_file_tga.py Tests/test_file_tiff_metadata.py Tests/test_file_cur.py Tests/test_imagemorph.py Tests/test_format_hsv.py Tests/test_imagefont.py Tests/test_shell_injection.py Tests/test_imagewin.py Tests/test_image_getpixel.py Tests/test_image_putpixel.py Tests/test_file_xbm.py Tests/test_image_offset.py Tests/test_image_rotate.py Tests/test_file_msp.py Tests/test_imagechops.py Tests/test_file_dcx.py Tests/test_file_spider.py Tests/test_file_iptc.py Tests/test_file_ico.py Tests/test_file_libtiff_small.py Tests/test_image_resize.py Tests/test_image_getbbox.py Tests/test_olefileio.py Tests/test_font_pcf.py Tests/test_image_draft.py Tests/test_font_bdf.py Tests/test_numpy.py Tests/test_imagegrab.py Tests/test_cffi.py Tests/test_image_split.py Tests/test_scipy.py Tests/test_util.py Tests/test_image_crop.py Tests/test_file_jpeg.py Tests/test_file_bmp.py Tests/test_image_load.py Tests/test_pickle.py Tests/test_image_convert.py Tests/test_imagemath.py Tests/test_image_quantize.py Tests/test_file_pcx.py ..S...make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs make: *** wait: No child processes. Stop. Build killed with signal TERM after 300 minutes of inactivity See the build log at https://buildd.debian.org/status/fetch.php?pkg=pillowarch=mipsver=2.6.1-1stamp=1414045002 Cheers, Julien (upstream dev here) There’s not a lot to go on there — I can’t even tell which test is hanging/failing. I could figure it out with either access to a mips machine or more verbose logging, perhaps with -s -v flags on the test runner. eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Changes
Processing commands for cont...@bugs.debian.org: reassign 767248 dbconfig-common 1.8.47+nmu2 Bug #767248 [dbconfig-common] dbconfig-common: removes any permissions from generated include files on upgrade Ignoring request to reassign bug #767248 to the same package Bug #767248 [dbconfig-common] dbconfig-common: removes any permissions from generated include files on upgrade Ignoring request to alter found versions of bug #767248 to the same values previously set retitle 767248 dbconfig-common: removes permissions of include files on Bug #767248 [dbconfig-common] dbconfig-common: removes any permissions from generated include files on upgrade Changed Bug title to 'dbconfig-common: removes permissions of include files on' from 'dbconfig-common: removes any permissions from generated include files on upgrade' upgrade Unknown command or malformed arguments to command. kthxbye Stopping processing here. Please contact me if you need assistance. -- 767248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767248 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
Processed: Re: dbconfig-common: removes any permissions from generated include files on upgrade
Processing control commands: tags -1 + patch Bug #767248 [dbconfig-common] dbconfig-common: removes permissions of include files on Added tag(s) patch. -- 767248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767248 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#767248: dbconfig-common: removes any permissions from generated include files on upgrade
Control: tags -1 + patch The origin of the bug is in line 411 of dbconfig-generate-include. On upgrade, any new file is written to a temp file, which has default permissions (as in, those of the user running the script, normally root, and their umask). Attached is a patch that replicates the permissions of any old configuration to the tempfile so they do not get lost. Cheers, Nik -- Dominik George (Vorstandsvorsitzender, Pädagogischer Leiter) Teckids e.V. - Erkunden, Entdecken, Erfinden. https://www.teckids.org diff -Nru dbconfig-common-1.8.47+nmu2/dbconfig-generate-include dbconfig-common-1.8.47+nmu3/dbconfig-generate-include --- dbconfig-common-1.8.47+nmu2/dbconfig-generate-include 2014-10-13 21:05:57.0 +0200 +++ dbconfig-common-1.8.47+nmu3/dbconfig-generate-include 2014-10-29 16:38:09.0 +0100 @@ -408,6 +408,10 @@ ucf --debconf-ok $tmpout $outputfile 2 rm -f $tmpout else + # Replicate permissions of original file to temp file + # so it doesn't get lost + chmod --reference=$outputfile $tmpout + chown --reference=$outputfile $tmpout mv $tmpout $outputfile fi check_permissions diff -Nru dbconfig-common-1.8.47+nmu2/debian/changelog dbconfig-common-1.8.47+nmu3/debian/changelog --- dbconfig-common-1.8.47+nmu2/debian/changelog2014-10-13 21:31:13.0 +0200 +++ dbconfig-common-1.8.47+nmu3/debian/changelog2014-10-29 16:43:27.0 +0100 @@ -1,3 +1,11 @@ +dbconfig-common (1.8.47+nmu3) unstable; urgency=medium + + * Non-maintainer upload. + * Do not remove permissions from include files on upgrade, +thanks to Simon Bruder. (Closes: #767248) + + -- Dominik George n...@naturalnet.de Wed, 29 Oct 2014 16:38:19 +0100 + dbconfig-common (1.8.47+nmu2) unstable; urgency=low * Non-maintainer upload. diff -Naupr dbconfig-common-1.8.47+nmu2.old/dbconfig-generate-include dbconfig-common-1.8.47+nmu3/dbconfig-generate-include --- dbconfig-common-1.8.47+nmu2.old/dbconfig-generate-include 2014-10-13 21:05:57.0 +0200 +++ dbconfig-common-1.8.47+nmu3/dbconfig-generate-include 2014-10-29 16:49:01.505051762 +0100 @@ -408,6 +408,12 @@ if [ $outputfile ]; then ucf --debconf-ok $tmpout $outputfile 2 rm -f $tmpout else + # Replicate permissions of original file to temp file + # so it doesn't get lost + if [ -e $outputfile ]; then + chmod --reference=$outputfile $tmpout + chown --reference=$outputfile $tmpout + fi mv $tmpout $outputfile fi check_permissions diff -Naupr dbconfig-common-1.8.47+nmu2.old/debian/changelog dbconfig-common-1.8.47+nmu3/debian/changelog --- dbconfig-common-1.8.47+nmu2.old/debian/changelog 2014-10-13 21:31:13.0 +0200 +++ dbconfig-common-1.8.47+nmu3/debian/changelog 2014-10-29 16:43:27.677039956 +0100 @@ -1,3 +1,11 @@ +dbconfig-common (1.8.47+nmu3) unstable; urgency=medium + + * Non-maintainer upload. + * Do not remove permissions from include files on upgrade, +thanks to Simon Bruder. (Closes: #767248) + + -- Dominik George n...@naturalnet.de Wed, 29 Oct 2014 16:38:19 +0100 + dbconfig-common (1.8.47+nmu2) unstable; urgency=low * Non-maintainer upload. signature.asc Description: OpenPGP digital signature
Processed: Re: kmail: KMail goes bonkers following Qt update
Processing control commands: reassign 727800 akonadi Bug #727800 [kmail] kmail: KMail goes bonkers following Qt update Bug reassigned from package 'kmail' to 'akonadi'. No longer marked as found in versions kdepim/4:4.10.5-2. Ignoring request to alter fixed versions of bug #727800 to the same values previously set -- 727800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727800 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#727800: kmail: KMail goes bonkers following Qt update
Control: reassign 727800 akonadi Hey, there are some newer versions and the bug you mentioned is marked as resolved fixed. The biggest issue with akonadi is, that older akonadi databases are often in kind of a broken state (something like 1.10). That is/was not visible in ( KDE 4.9), 'cause only kaddressbook uses akonadi so far. So for many users the upgrade process is kind of crual, and they have to reset akonadi database + config. Unfortunatelly the package system can't help here 'cause these are living inside the home folder... Well speaking as an upstream dev, hunting update errors is one of the hard ones. 'Cause normally users can't give you the state from before the upgrade and mail setups are so different... But something was synchronizing, so I let it go. When it was done (didn't follow closely, but ~20 minutes later) it had restored my mails -- sort of. Yes akonadi has to index all mails. It managed to forget the read status of ~3 months of mails, so I suddenly had more than 4000 unread mails in my inbox. The 3 months weren't the last ones, but mid April to mid July; I suspect these were the first 3 months of KMail2 on this system. what kind of email folder do you use? imap, maildir, mboxes I never heard about this issue. I have ~20 filters, most of them just send messages to different folders. When I looked at the filter configuration, I realized all the filter target folders were wrong. It wasn't too hard to resotre them, but it had to be done manually. Well the same can/is true for sent/draft folders for identities etc. I know it is annoying, but you to do it only once. A) There was real (though minor) data loss -- the read status, and the filters configurations; B) There was what looked like data loss -- at first, seeing the empty mail folders was scary; it is very easy to panic and kill the program at that stage, which is likely to cause more serious data loss. if you keep akonadi running everything will sync correctly :) btw. akonadi only indexes first and not touching the mails. So no you won't end up in a serios data loss. But I would advertise backuping all pim data before upgrade kdepim-kdepim 4.14. And yes leaving akonadi time to sync is also a good idea :) Regards, sandro signature.asc Description: This is a digitally signed message part.
Processed: tagging 766920
Processing commands for cont...@bugs.debian.org: tags 766920 - moreinfo Bug #766920 [initramfs-tools] initramfs-tools: update-initramfs makes system unbootable due to missing rootfs Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 766920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766920 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#761001: Gnome3/Gdm3 gone :-)
Hi, Looking at the date of OP's situation, problem may be different. Booting with the older kernel linux-image-3.16-2-amd64 did not fix my situation. My problem may be mutter or mesa. Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754755: libinline-java-perl: FTBFS on mips: test suite issues
Hello, I have tried to build libinline-java-perl_0.53-3 from Debian on mips. Package FTBFS on mips. But same package (libinline-java-perl_0.53-3) can be built from same source manually with following commands: perl Makefile.PL J2SDK=/usr/ make make test If built manually all tests pass on mips. Can someone please help with this issue? Thank you! Regards, Jurica
Bug#764386: libefivar0: Segmentation fault in vars_get_variable() (vars.c:165)
On Mon, Oct 06, 2014 at 06:14:59PM -0500, Jan Echternach wrote: Package: libefivar0 Version: 0.12-1 Severity: critical Justification: breaks the whole system Upgrading libefivar0 from version 0.10-5 to 0.12-1 causes a segmentation fault when running efibootmgr without arguments (I tried it with both efibootmgr 0.7.0-2 and 0.9.0-1). I'm not quite sure if severity critical is justified, but I think a broken efibootmgr is at least potentially able to break the whole system. gdb pointed to libefivar.so.0 which has no debugging symbols, so I built my own and that one crashes in vars.c line 165 with var == NULL. The last two lines in an strace log before the crash are open(/sys/firmware/efi/vars/Boot0005-8be4[...]/raw_var, O_RDONLY) = 3 read(3, [...], 4096) = -1 EIO (Input/output error) (Sorry, no copypaste, just readtype; the system in question has only very limited network connectivity at the moment and I'm sending this report from a different system.) var is apparently returned from a call to read_file() a few lines above. The source code history shows that read_fd() has recently been replaced by read_file(), but they behave differently after read errors. In particular, read_file() resets the buffer to NULL whereas read_fd() didn't. Jan, Can you confirm whether this is still an issue for you? New versions of libefivar0 are in testing and unstable. Please test against them. --Jared -- Jared Domínguez Server OS Engineering Dell | Enterprise Solutions Group -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to gnustep-dl2, tagging 759832
Processing commands for cont...@bugs.debian.org: limit source gnustep-dl2 Limiting to bugs with field 'source' containing at least one of 'gnustep-dl2' Limit currently set to 'source':'gnustep-dl2' tags 759832 + pending Bug #759832 [src:gnustep-dl2] gnustep-dl2: FTBFS: Palette.h:26:40: fatal error: InterfaceBuilder/IBPalette.h: No such file or directory Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 759832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759832 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#607969: sqlite: Still useful?
Hi Laszlo, On Wed, 29 Oct 2014 10:52:02 +0100 =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= g...@debian.org wrote: On Wed, Oct 29, 2014 at 10:33 AM, Balint Reczey bal...@balintreczey.hu wrote: On Mon, 4 Aug 2014 20:08:21 +0100 Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: I stumbled upon this bug by chance when looking at why it did not compile in some new ports. It should compile on all of them by now. The buildd archive shows that arm64 and ppc64el are fine, even mips and sparc. I guess that it's better to just ask FTP masters to remove the package, but I'll leave that to other people, since they were interested in doing that in the past (all in copy now). Yes, I was about to ask its removal as upstream no longer supports it. But it works correctly and I got personal mails that they would still use it on low-end (embedded?) machines where sqlite3 would require more CPU and/or memory. In this case I think this bug could be simply closed by answering the question (Yes.). :-) Having reverse dependencies is actually useful to keep the code tested. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763220: Bug#766244: RFS: dwb/20140702hg-1.1 [RC]
On 27.10.2014 18:29, gregor herrmann wrote: On Sun, 26 Oct 2014 16:04:57 +0100, Mateusz Łukasik wrote: On 26.10.2014 15:27, Sebastian Ramacher wrote: * Patch work: - Add from Fedora: dwb-gtk-deprecated.patch --fix FTBFS. (Closes: #763220) Okay. Please send a message to #763220 saying that there is a patch available and that you intend to NMU. OK. Done Well, not really, there's only the note that the patch exists, but nothing about the NMU candidate on mentors and the sponsorship-bug. (I stumbled across #763220 while looking at RC bugs and the PTS told me about the package on mentors, and then I manually looked into the sponsorship-requests bugs ...) Anyway, original bug CC'd now to have the info there :) Cheers, gregor OK. I need make a affects for this two bugs. Mateusz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761211: [Pkg-electronics-devel] Bug#746003: Bug#760986: RM: guile-1.8 -- ROM; replaced by guile-2.0
tag 761211 + patch quit On Sun, Oct 12, 2014 at 09:51:12PM -0500, Rob Browning wrote: Luca Falavigna dktrkr...@debian.org writes: guile-gnome-platform [1] No response wrt 2.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761211 ---end quoted text--- The attached patch (which is just a sync from Ubuntu), migrates guile-gnome-platform to guile 2.0. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 diff -Nru guile-gnome-platform-2.16.2/debian/changelog guile-gnome-platform-2.16.2/debian/changelog --- guile-gnome-platform-2.16.2/debian/changelog2014-02-11 10:59:12.0 +0200 +++ guile-gnome-platform-2.16.2/debian/changelog2014-10-29 19:09:14.0 +0200 @@ -1,3 +1,20 @@ +guile-gnome-platform (2.16.2-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Sync changes from Ubuntu. (Closes: #761211) + + -- أحمد المحمودي (Ahmed El-Mahmoudy) aelmahmo...@users.sourceforge.net Wed, 29 Oct 2014 19:08:36 +0200 + +guile-gnome-platform (2.16.2-1.1ubuntu1) trusty; urgency=medium + + * Switch to guile-2.0-dev. + * Backport build fix from upstream to use absolute paths and handle +GUILE_LOAD_PATH being unset. + * Handle the Automake parallel test harness. + * Use dh-autoreconf to help apply these changes. + + -- Colin Watson cjwat...@ubuntu.com Tue, 25 Mar 2014 11:51:05 + + guile-gnome-platform (2.16.2-1.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru guile-gnome-platform-2.16.2/debian/control guile-gnome-platform-2.16.2/debian/control --- guile-gnome-platform-2.16.2/debian/control 2012-06-02 16:32:20.0 +0200 +++ guile-gnome-platform-2.16.2/debian/control 2014-03-25 13:51:04.0 +0200 @@ -1,12 +1,13 @@ Source: guile-gnome-platform Section: lisp Priority: extra -Maintainer: Andreas Rottmann ro...@debian.org +Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com +XSBC-Original-Maintainer: Andreas Rottmann ro...@debian.org Standards-Version: 3.9.3 Homepage: http://www.gnu.org/software/guile-gnome/ Build-Depends: cdbs (= 0.4.49), debhelper ( 7), - automake, libtool, xvfb, xauth, xfonts-base, stx2any, - guile-1.8-dev, guile-library (= 0.1.6), + dh-autoreconf, xvfb, xauth, xfonts-base, stx2any, + guile-2.0-dev, guile-library (= 0.1.6), g-wrap (= 1.9.14-1), guile-g-wrap (= 1.9.14-1), libgwrap-runtime-dev (= 1.9.11), guile-cairo-dev (= 1.4.0), libglib2.0-dev (= 2.12.13), libgtk2.0-dev (= 2.10.13), libgconf2-dev (= 2.18.0), diff -Nru guile-gnome-platform-2.16.2/debian/patches/fixes/automake-parallel-tests.patch guile-gnome-platform-2.16.2/debian/patches/fixes/automake-parallel-tests.patch --- guile-gnome-platform-2.16.2/debian/patches/fixes/automake-parallel-tests.patch 1970-01-01 02:00:00.0 +0200 +++ guile-gnome-platform-2.16.2/debian/patches/fixes/automake-parallel-tests.patch 2014-03-25 13:49:55.0 +0200 @@ -0,0 +1,47 @@ +Description: Handle Automake parallel test harness +Author: Colin Watson cjwat...@ubuntu.com +Forwarded: no +Last-Update: 2014-03-25 + +Index: b/glib/test-suite/Makefile.am +=== +--- a/glib/test-suite/Makefile.am b/glib/test-suite/Makefile.am +@@ -36,7 +36,8 @@ + gw_module_name = (gnome gw $(wrapset_stem)) + extra_module_names = + wrapset_modules = ($(top_module_name) $(gw_module_name) $(extra_module_names)) +-TESTS_ENVIRONMENT=\ ++LOG_COMPILER=\ ++ env \ + API_FILE=$(srcdir)/gobject.api \ + DOC_SCM=$(srcdir)/../doc/gobject/guile-gnome-gobject.scm \ + WRAPSET_MODULES=$(wrapset_modules) \ +@@ -64,7 +65,7 @@ + $(top_builddir)/dev-environ $(GUILE) --debug -e update-api -s $(srcdir)/wrapset.scm + + %.check: % +- $(TESTS_ENVIRONMENT) $(srcdir)/$* ++ $(LOG_COMPILER) $(srcdir)/$* + + EXTRA_DIST+=gobject.api api.scm wrapset.api wrapset.scm + +Index: b/tests.mk +=== +--- a/tests.mk b/tests.mk +@@ -33,12 +33,12 @@ + WRAPSET_TESTS_ENV = WRAPSET_MODULES=$(wrapset_modules) WRAPSET_API_FILE=$(srcdir)/wrapset.api + DEV_ENV = $(top_builddir)/dev-environ + +-TESTS_ENVIRONMENT=$(WRAPSET_TESTS_ENV) $(DEV_ENV) $(GUILE) $(GUILE_FLAGS) -e main -s ++LOG_COMPILER=env $(WRAPSET_TESTS_ENV) $(DEV_ENV) $(GUILE) $(GUILE_FLAGS) -e main -s + + wrapset.api.update: + $(WRAPSET_TESTS_ENV) $(DEV_ENV) $(GUILE) -e update-api -s $(srcdir)/wrapset.scm + + %.check: % +- $(TESTS_ENVIRONMENT) $(srcdir)/$* ++ $(LOG_COMPILER) $(srcdir)/$* + + TESTS = wrapset.scm diff -Nru guile-gnome-platform-2.16.2/debian/patches/fixes/build-absolute-paths.patch guile-gnome-platform-2.16.2/debian/patches/fixes/build-absolute-paths.patch --- guile-gnome-platform-2.16.2/debian/patches/fixes/build-absolute-paths.patch 1970-01-01 02:00:00.0 +0200 +++
Processed: Re: [Pkg-electronics-devel] Bug#746003: Bug#760986: RM: guile-1.8 -- ROM; replaced by guile-2.0
Processing commands for cont...@bugs.debian.org: tag 761211 + patch Bug #761211 [guile-gnome-platform] guile-gnome-platform: please migrate to guile-2.0 Added tag(s) patch. quit Stopping processing here. Please contact me if you need assistance. -- 761211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761211 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#765145: marked as done (globus-simple-ca: FTBFS: Tests failures)
Your message dated Wed, 29 Oct 2014 19:10:19 + with message-id e1xjydq-00089e...@franck.debian.org and subject line Bug#765145: fixed in globus-simple-ca 4.14-2 has caused the Debian Bug report #765145, regarding globus-simple-ca: FTBFS: Tests failures 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.) -- 765145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: globus-simple-ca Version: 4.14-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141012 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[5]: Entering directory '/«PKGBUILDDIR»/test' make[5]: Nothing to be done for 'all'. make[5]: Leaving directory '/«PKGBUILDDIR»/test' Testsuite summary for globus_simple_ca 4.14 # TOTAL: 2 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See test/test-suite.log Please report to https://globus.atlassian.net/ make[4]: *** [test-suite.log] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/10/12/globus-simple-ca_4.14-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--- ---BeginMessage--- Source: globus-simple-ca Source-Version: 4.14-2 We believe that the bug you reported is fixed in the latest version of globus-simple-ca, 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 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattias Ellert mattias.ell...@fysast.uu.se (supplier of updated globus-simple-ca 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, 27 Oct 2014 17:13:00 +0100 Source: globus-simple-ca Binary: globus-simple-ca Architecture: source all Version: 4.14-2 Distribution: unstable Urgency: medium Maintainer: Mattias Ellert mattias.ell...@fysast.uu.se Changed-By: Mattias Ellert mattias.ell...@fysast.uu.se Description: globus-simple-ca - Globus Toolkit - Simple CA Utility Closes: 765145 Changes: globus-simple-ca (4.14-2) unstable; urgency=medium . * Move make check to build target (Closes: #765145) * Drop patch globus-simple-ca-id.patch (not needed with above change) Checksums-Sha1: 12a726aa110ff1e0f2f1a1fe39c05a943e7a6251 1977 globus-simple-ca_4.14-2.dsc 1fe3e85d4b96169214df31b1b8c90a3941e122a2 2392 globus-simple-ca_4.14-2.debian.tar.xz 67703c4f6f613e6b13aa4806047ad888417230f4 22770 globus-simple-ca_4.14-2_all.deb Checksums-Sha256: 263ed8bc79201870580d3191173ae8d5005646917608d18303c6886f2b352e7d 1977 globus-simple-ca_4.14-2.dsc 31a07c36d67f0e93e8012221aa1a7b527bb7932a3f2e3cf4cb9171fe9196564d 2392 globus-simple-ca_4.14-2.debian.tar.xz 491689484da9f49885cf770af3234d2054c658d29cd80124f75a63a61a9c0028 22770 globus-simple-ca_4.14-2_all.deb Files: d30bfea53a0fbda97d04acf39bbf11f4 1977 net optional globus-simple-ca_4.14-2.dsc da6519e977c7b9c266343d09d096b93c 2392 net optional globus-simple-ca_4.14-2.debian.tar.xz a985d0b5d1bc18c0cbdb5e578877e5c4 22770 net optional globus-simple-ca_4.14-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUUTcpAAoJEOiuwv874alLlW4QAIAlUTzv8wWO6NFTV8nHL0ak 0gGzyH5Wh9B9O9KDpvUjPZsW1tBqx7lQ/+VTxSEhvRRUmDk8wYt7/ps1QQSmTol0 C7pHqhxROP7mu+ugm7UejMGKKp/ZwpENy9NgDareqGGru2u8u6YODe8ecmTIILg9 XAMJfH2sAV9Q5Lt7XNrnxXNO7FAl1f8RbIgmspDsrY4/0HL+1V2bEEV1sbTriewY LxTleyAG0bMnU7gBaKyjPIP5VLRWesC5tfOvTXZSZoIhOF13qOcAFy5QUgyOd1Bd
Processed: unreproducible here
Processing control commands: tag -1 unreproducible Bug #765113 [src:ruby-webmock] ruby-webmock: FTBFS: ERROR: Test ruby2.1 failed Added tag(s) unreproducible. -- 765113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765113 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#765113: unreproducible here
Control: tag -1 unreproducible Hi David, I tried to reproduce this bug in various environments but I failed. Can you check if it still applies on your side? Cheers, Cédric signature.asc Description: Digital signature
Bug#765722: marked as done (CVE-2014-3660 libxml2 billion laugh variant)
Your message dated Wed, 29 Oct 2014 19:34:50 + with message-id e1xjz18-0003nl...@franck.debian.org and subject line Bug#765722: fixed in libxml2 2.7.8.dfsg-2+squeeze10 has caused the Debian Bug report #765722, regarding CVE-2014-3660 libxml2 billion laugh variant 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.) -- 765722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libxml2 Severity: serious Tags: security patch Hi, The Netherlands Cyber Security Center announced an issue in libxml2. https://www.ncsc.nl/actueel/nieuwsberichten/kwetsbaarheid-ontdekt-in-libxml2.html It seems to be a variant of the classic 'billion laughs' vulnerability. Upstream has fixed this in 2.9.2: https://git.gnome.org/browse/libxml2/commit/?id=be2a7edaf289c5da74a4f9ed3a0b6c733e775230 Cheers, Thijs ---End Message--- ---BeginMessage--- Source: libxml2 Source-Version: 2.7.8.dfsg-2+squeeze10 We believe that the bug you reported is fixed in the latest version of libxml2, 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 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz deb...@alteholz.de (supplier of updated libxml2 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, 28 Oct 2014 18:00:28 +0100 Source: libxml2 Binary: libxml2 libxml2-utils libxml2-dev libxml2-dbg libxml2-doc python-libxml2 python-libxml2-dbg Architecture: source i386 all Version: 2.7.8.dfsg-2+squeeze10 Distribution: squeeze-lts Urgency: high Maintainer: Debian XML/SGML Group debian-xml-sgml-p...@lists.alioth.debian.org Changed-By: Thorsten Alteholz deb...@alteholz.de Description: libxml2- GNOME XML library libxml2-dbg - Debugging symbols for the GNOME XML library libxml2-dev - Development files for the GNOME XML library libxml2-doc - Documentation for the GNOME XML library libxml2-utils - XML utilities python-libxml2 - Python bindings for the GNOME XML library python-libxml2-dbg - Python bindings for the GNOME XML library (debug extension) Closes: 762864 765722 Changes: libxml2 (2.7.8.dfsg-2+squeeze10) squeeze-lts; urgency=high . * Non-maintainer upload by the Squeeze LTS Team. * Fix wrongly applied patch for CVE-2014-0191 (Closes: #762864) * Add patch for CVE-2014-3660 (Closes: #765722) Checksums-Sha1: a3e519ddeb9fdbe342cc4a5db1fa20edb84b0521 2311 libxml2_2.7.8.dfsg-2+squeeze10.dsc bf481743478da6899a65507a34b67731466960dd 3509930 libxml2_2.7.8.dfsg.orig.tar.gz e57d4ca4635f7d652f241332cc5e51e3eef79eff 124159 libxml2_2.7.8.dfsg-2+squeeze10.diff.gz 7936822eafd70dbb3d5ca244e695d5fa0ca2121d 829480 libxml2_2.7.8.dfsg-2+squeeze10_i386.deb 1be0736c4d5f3c08ff70beccb65635a5cd91cedb 90910 libxml2-utils_2.7.8.dfsg-2+squeeze10_i386.deb 107133b4ebf8bfca5c4a0d5a6b33feca47183042 753492 libxml2-dev_2.7.8.dfsg-2+squeeze10_i386.deb be561dddffa0afb47516c08ce6b22f8f954bb9e1 991394 libxml2-dbg_2.7.8.dfsg-2+squeeze10_i386.deb 29527627f5b593a47dc0060722c85b50c04adbcd 1382264 libxml2-doc_2.7.8.dfsg-2+squeeze10_all.deb f69baf3d4f5e1abb55224238d3b04f40f171d0cd 310586 python-libxml2_2.7.8.dfsg-2+squeeze10_i386.deb f2f3f70fb7be9dd8b4dacaeea7f6b1fe42d38470 823254 python-libxml2-dbg_2.7.8.dfsg-2+squeeze10_i386.deb Checksums-Sha256: a7eac158f88480083b15cb05c5879ec4c2346d8beebb694cf256dfc489cf42a4 2311 libxml2_2.7.8.dfsg-2+squeeze10.dsc 9f5262963fda356708903b42ff862a816c714582d0cf41477a8b3839945f0e43 3509930 libxml2_2.7.8.dfsg.orig.tar.gz 9579fe3a12d3ed3f90e62fe304bad6813cc1462ad4cdaa7e15f7dd23b4f33eb6 124159 libxml2_2.7.8.dfsg-2+squeeze10.diff.gz 0450ea20ef210affd223d55418906cb1efb31874040730de5f96bfeebba5ef51 829480 libxml2_2.7.8.dfsg-2+squeeze10_i386.deb d3c35c1ecc4d6f3ef7030ce0821aa218678980a380684afa1292b70d75b3d29d 90910 libxml2-utils_2.7.8.dfsg-2+squeeze10_i386.deb 175833cf5cf4f27804ec6e5bb556f22580ad03ef108c56d3052f792eace7fb8f 753492 libxml2-dev_2.7.8.dfsg-2+squeeze10_i386.deb 31b9f3e087c5d202a6de5012371a70f6e485b92bf72b388aef90afa20c64f1e4 991394 libxml2-dbg_2.7.8.dfsg-2+squeeze10_i386.deb
Bug#767280: gnome-session: screen freezes after login
Package: gnome-session Version: 3.14.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? I upgraded this unstable system after being away for 2 weeks. After rebooting I could no longer use the system after log in. The screen looks ok, the mouse is moving, but I cannot click anywhere nor does the usual behavior take place when the mouse is entering the upper left corner. * What exactly did you do (or not do) that was effective (or ineffective)? Logging in. The greeter is working ok, mouse is working normally. * What was the outcome of this action? I am logged in without being able to do any mouse related work. No opening of windows, no starting of applications, not even logging out again. * What outcome did you expect instead? A normal working desktop. I attach the journal lines containing gnome-session entries. Oct 29 18:18:40 jupiter.fkoop.de gnome-session[5052]: WARNING: Could not parse desktop file xfconf-migration-4.6.desktop or it references a not found TryExec binary Oct 29 18:18:40 jupiter.fkoop.de gnome-session[5052]: WARNING: Could not parse desktop file xfce4-settings-helper-autostart.desktop or it references a not found TryExec binary Oct 29 18:18:40 jupiter.fkoop.de gnome-session[5052]: gnome-session[5052]: WARNING: Could not parse desktop file xfconf-migration-4.6.desktop or it references a not found TryExec binary Oct 29 18:18:40 jupiter.fkoop.de gnome-session[5052]: gnome-session[5052]: WARNING: Could not parse desktop file xfce4-settings-helper-autostart.desktop or it references a not found TryExec binary Oct 29 18:18:40 jupiter.fkoop.de gnome-session[5052]: WARNING: Could not parse desktop file update-notifier.desktop or it references a not found TryExec binary Oct 29 18:18:40 jupiter.fkoop.de gnome-session[5052]: gnome-session[5052]: WARNING: Could not parse desktop file update-notifier.desktop or it references a not found TryExec binary Oct 29 18:18:41 jupiter.fkoop.de gnome-session[5052]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1 Oct 29 18:18:41 jupiter.fkoop.de gnome-session[5052]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1 Oct 29 18:18:41 jupiter.fkoop.de gnome-session[5052]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Oct 29 18:18:41 jupiter.fkoop.de gnome-session[5052]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1 Oct 29 18:18:41 jupiter.fkoop.de gnome-session[5052]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Oct 29 18:18:41 jupiter.fkoop.de gnome-session[5052]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1 Oct 29 18:18:41 jupiter.fkoop.de gnome-session[5052]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Oct 29 18:18:41 jupiter.fkoop.de gnome-session[5052]: Fehlgeschlagen: Modulinitialisierung fehlgeschlagen Oct 29 18:18:41 jupiter.fkoop.de gnome-session[5052]: WARNING: App 'pulseaudio.desktop' exited with code 1 Oct 29 18:18:41 jupiter.fkoop.de gnome-session[5052]: gnome-session[5052]: WARNING: App 'pulseaudio.desktop' exited with code 1 Oct 29 18:18:43 jupiter.fkoop.de gnome-session[5052]: Gjs-Message: JS LOG: Failed to launch ibus-daemon: Kindprozess »ibus-daemon« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) Oct 29 18:18:44 jupiter.fkoop.de gnome-session[5052]: Entering running state Oct 29 18:18:44 jupiter.fkoop.de gnome-session[5052]: (uint32 1,) Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: Starting Dropbox... Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: (gnome-shell:5172): Gjs-WARNING **: JS ERROR: Exception in callback for signal: startup-complete: Error: Requiring GSystem, version none: Typelib file for namespace 'GSystem' (any version) not found Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: _initializeUI/@resource:///org/gnome/shell/ui/main.js:218 Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: _emit@resource:///org/gnome/gjs/modules/signals.js:124 Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: LayoutManager._startupAnimationComplete@resource:///org/gnome/shell/ui/layout.js:700 Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: wrapper@resource:///org/gnome/gjs/modules/lang.js:169 Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: _addHandler/params[name]@resource:///org/gnome/shell/ui/tweener.js:91 Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: _callOnFunction@resource:///org/gnome/gjs/modules/tweener/tweener.js:203 Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: _updateTweenByIndex@resource:///org/gnome/gjs/modules/tweener/tweener.js:333 Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: _updateTweens@resource:///org/gnome/gjs/modules/tweener/tweener.js:345 Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: _onEnterFrame@resource:///org/gnome/gjs/modules/tweener/tweener.js:360 Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]: _emit@resource:///org/gnome/gjs/modules/signals.js:124 Oct 29 18:18:45 jupiter.fkoop.de gnome-session[5052]:
Bug#741075: user-mode-linux: diff for NMU version 3.16-1um-0.1
Control: tags 765132 + patch pending
Control: tags 741075 + pending
Control: tags 741077 + pending
Dear maintainer,
I've prepared an NMU for user-mode-linux (versioned as 3.16-1um-0.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I should delay
it longer.
--
Jakub Wilk
diffstat for user-mode-linux-3.13-1um user-mode-linux-3.16-1um
config.amd64 | 95 ++
config.i386 | 96 +++
debian/changelog | 14
debian/control |2 -
debian/rules |2 -
5 files changed, 181 insertions(+), 28 deletions(-)
Control files: lines which differ (wdiff format)
Build-Depends: debhelper ( 5.0.0), quilt, [-linux-source-3.13,-] {+linux-source-3.16,+} docbook-to-man, xz-utils, m4, module-init-tools, libvdeplug2-dev, libpcap-dev, bc, dpkg (= 1.16.2)
diff -Nru user-mode-linux-3.13-1um/config.amd64 user-mode-linux-3.16-1um/config.amd64
--- user-mode-linux-3.13-1um/config.amd64 2014-04-15 15:04:08.0 +0200
+++ user-mode-linux-3.16-1um/config.amd64 2014-10-28 23:44:23.0 +0100
@@ -1,6 +1,6 @@
#
# Automatically generated file; DO NOT EDIT.
-# User Mode Linux/x86_64 3.13.7 Kernel Configuration
+# User Mode Linux/x86_64 3.16.5 Kernel Configuration
#
CONFIG_UML=y
CONFIG_MMU=y
@@ -57,12 +57,13 @@
CONFIG_NEED_BOUNCE_POOL=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
-CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_NEED_PER_CPU_KM=y
CONFIG_CLEANCACHE=y
CONFIG_FRONTSWAP=y
# CONFIG_ZBUD is not set
# CONFIG_ZSWAP is not set
+CONFIG_ZSMALLOC=m
+# CONFIG_PGTABLE_MAPPING is not set
CONFIG_LD_SCRIPT_DYN=y
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
@@ -94,8 +95,11 @@
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
+CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
+CONFIG_USELIB=y
CONFIG_AUDIT=y
+CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y
@@ -164,9 +168,7 @@
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
-CONFIG_UIDGID_STRICT_TYPE_CHECKS=y
# CONFIG_SCHED_AUTOGROUP is not set
-CONFIG_MM_OWNER=y
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
@@ -183,6 +185,8 @@
CONFIG_HAVE_UID16=y
# CONFIG_EXPERT is not set
CONFIG_UID16=y
+# CONFIG_SGETMASK_SYSCALL is not set
+CONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
CONFIG_PRINTK=y
@@ -206,8 +210,11 @@
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
+# CONFIG_SYSTEM_TRUSTED_KEYRING is not set
# CONFIG_PROFILING is not set
+# CONFIG_UPROBES is not set
CONFIG_HAVE_64BIT_ALIGNED_ACCESS=y
+# CONFIG_CC_STACKPROTECTOR is not set
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_MODULES_USE_ELF_RELA=y
@@ -218,7 +225,6 @@
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
-# CONFIG_SYSTEM_TRUSTED_KEYRING is not set
CONFIG_MODULES=y
CONFIG_MODULE_FORCE_LOAD=y
CONFIG_MODULE_UNLOAD=y
@@ -308,6 +314,7 @@
#
# Generic Driver Options
#
+CONFIG_UEVENT_HELPER=y
CONFIG_UEVENT_HELPER_PATH=/sbin/hotplug
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
@@ -330,6 +337,9 @@
# CONFIG_MTD is not set
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_NULL_BLK=m
+CONFIG_ZRAM=m
+# CONFIG_ZRAM_LZ4_COMPRESS is not set
+# CONFIG_ZRAM_DEBUG is not set
CONFIG_BLK_DEV_UBD=y
# CONFIG_BLK_DEV_UBD_SYNC is not set
CONFIG_BLK_DEV_COW_COMMON=y
@@ -393,6 +403,7 @@
#
# Intel MIC Card Driver
#
+CONFIG_ECHO=m
#
# SCSI device support
@@ -470,6 +481,7 @@
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_THIN_PROVISIONING=m
# CONFIG_DM_CACHE is not set
+CONFIG_DM_ERA=m
CONFIG_DM_MIRROR=m
CONFIG_DM_LOG_USERSPACE=m
CONFIG_DM_RAID=m
@@ -507,7 +519,6 @@
CONFIG_NETCONSOLE=m
# CONFIG_NETCONSOLE_DYNAMIC is not set
CONFIG_NETPOLL=y
-# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_TUN=m
CONFIG_VETH=m
@@ -535,9 +546,9 @@
CONFIG_NET_VENDOR_INTEL=y
CONFIG_NET_VENDOR_I825XX=y
CONFIG_NET_VENDOR_MARVELL=y
-# CONFIG_MVMDIO is not set
CONFIG_NET_VENDOR_NATSEMI=y
CONFIG_NET_VENDOR_8390=y
+CONFIG_NET_VENDOR_SAMSUNG=y
CONFIG_NET_VENDOR_VIA=y
CONFIG_PHYLIB=m
@@ -554,6 +565,7 @@
CONFIG_VITESSE_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_BROADCOM_PHY=m
+CONFIG_BCM7XXX_PHY=m
CONFIG_BCM87XX_PHY=m
CONFIG_ICPLUS_PHY=m
CONFIG_REALTEK_PHY=m
@@ -610,10 +622,15 @@
CONFIG_I2C_STUB=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
+CONFIG_SPMI=m
CONFIG_HSI=m
CONFIG_HSI_BOARDINFO=y
#
+# HSI controllers
+#
+
+#
# HSI clients
#
CONFIG_HSI_CHAR=m
@@ -654,6 +671,7 @@
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
+# CONFIG_XILINX_WATCHDOG is not set
CONFIG_UML_WATCHDOG=y
# CONFIG_REGULATOR is not set
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
@@ -676,8 +694,16 @@
# CONFIG_STAGING is not set
#
+# SOC (System On Chip) specific Drivers
+#
+
+#
# Hardware Spinlock drivers
#
+#
Processed: user-mode-linux: diff for NMU version 3.16-1um-0.1
Processing control commands: tags 765132 + patch pending Bug #765132 [src:user-mode-linux] user-mode-linux: FTBFS: build-dependency not installable: linux-source-3.13 Added tag(s) pending and patch. tags 741075 + pending Bug #741075 [user-mode-linux] user-mode-linux: Occasional memory corruption on startup under high load Added tag(s) pending. tags 741077 + pending Bug #741077 [user-mode-linux] user-mode-linux: UML dies under expect Added tag(s) pending. -- 741075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741075 741077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741077 765132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765132 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
Processed: user-mode-linux: diff for NMU version 3.16-1um-0.1
Processing control commands: tags 765132 + patch pending Bug #765132 [src:user-mode-linux] user-mode-linux: FTBFS: build-dependency not installable: linux-source-3.13 Ignoring request to alter tags of bug #765132 to the same tags previously set tags 741075 + pending Bug #741075 [user-mode-linux] user-mode-linux: Occasional memory corruption on startup under high load Ignoring request to alter tags of bug #741075 to the same tags previously set tags 741077 + pending Bug #741077 [user-mode-linux] user-mode-linux: UML dies under expect Ignoring request to alter tags of bug #741077 to the same tags previously set -- 741075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741075 741077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741077 765132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765132 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
Processed: user-mode-linux: diff for NMU version 3.16-1um-0.1
Processing control commands: tags 765132 + patch pending Bug #765132 [src:user-mode-linux] user-mode-linux: FTBFS: build-dependency not installable: linux-source-3.13 Ignoring request to alter tags of bug #765132 to the same tags previously set tags 741075 + pending Bug #741075 [user-mode-linux] user-mode-linux: Occasional memory corruption on startup under high load Ignoring request to alter tags of bug #741075 to the same tags previously set tags 741077 + pending Bug #741077 [user-mode-linux] user-mode-linux: UML dies under expect Ignoring request to alter tags of bug #741077 to the same tags previously set -- 741075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741075 741077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741077 765132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765132 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#759745: done?
Hi, As far as I understand it, this bug should be fixed. If anyone does still encounter it, please respond and let us know. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765132: user-mode-linux: diff for NMU version 3.16-1um-0.1
* Jakub Wilk jw...@debian.org, 2014-10-29, 20:48: I've prepared an NMU for user-mode-linux (versioned as 3.16-1um-0.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Blargh, I just realized that I accidentally made this package native. I'll reupload a fixed package (with the identical debdiff, but non-native) to DELAYED/5 shortly. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#766732: For clarification: re non serious data loss
Processing control commands: severity -1 important Bug #766732 [nautilus] libc: Segfault in libc (from process pool) accessing files shared via DAV across ethernet on another machine Severity set to 'important' from 'grave' -- 766732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766732 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#766732: For clarification: re non serious data loss
Control: severity -1 important Hi, Brian Drummond wrote (25 Oct 2014 12:32:42 GMT) : The non serious data loss may be a misnomer. It is my assessment because, if one assumes that a copy finished correctly when it actually terminated, the client machine is left with an incomplete data set. Indeed, in my book this doesn't qualify as RC = downgrading severity. (And: thanks for the detailed debugging!) Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765154: [Pkg-electronics-devel] Bug#746003: Bug#760986: RM: guile-1.8 -- ROM; replaced by guile-2.0
reopen 746003 tag 746003 + help quit Hello, I tried to compile gwave against g-wrap 1.9.14-2.1 [1] guile-gnome-platform 2.16.2-1.2 [2] I had to add a patch for gwave package [3] to update the used header. Now when I attempted to build gwave, I got stuck with the following build error: scwm_guile.c: In function 'scwm_handle_error': scwm_guile.c:332:30: error: 'scm_the_last_stack_fluid_var' undeclared (first use in this function) fl = SCM_VARIABLE_REF (scm_the_last_stack_fluid_var); Can someone help me with this issue please ? Thanks... [1] It has been in git (https://anonscm.debian.org/cgit/collab-maint/g-wrap.git) since 8 months ago, yet Hideki Yamane forgot to upload for some reason, hopefully he will upload it soon. [2] Debdiff available on: https://bugs.debian.org/761211 [3] http://anonscm.debian.org/gitweb/?p=pkg-electronics/gwave.git -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: Digital signature
Bug#745836: wget: certificate revocation is not checked
Control: found -1 1.16-1 Control: tag -1 + upstream Control: clone -1 -2 Control: severity -1 wishlist Control: retitle -2 wget manpage doesn't warn that certificate revocation lists are not checked Hi, [hoping I got all the Control stanzas right..] Vincent Lefevre wrote (28 Apr 2014 09:11:42 GMT) : It's a bug because it doesn't behave as documented [...] OK, thanks for the clarification. Then, keeping #745836 as a wishlist bug to track the missing feature, and creating a clone about the more important (and more likely to be fixed here) documentation bug. Regarding the missing feature, you might have better chances of seeing this resolved by reporting it upstream :) (I've checked there [1] and could not find it.) [1] https://savannah.gnu.org/bugs/?group=wget This makes the user (who cares about certificate validity) assume that without the --no-check-certificate option, the site's authenticity is guaranteed, while this is currently absolutely wrong with the lack of revocation checking. There's no such thing as guaranteed wrt. IT security in general, and even less so when one is relying on known-broken systems like the CA cartel to authenticate remote parties. Therefore, I personally don't think that the doc bug should be RC, but I'm not interested in severity ping-pong, so I'll let it to the maintainer to judge, and to the release team to decide if it should be ignored for Jessie. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#745836: wget: certificate revocation is not checked
Processing control commands: found -1 1.16-1 Bug #745836 [wget] wget: certificate revocation is not checked Marked as found in versions wget/1.16-1. tag -1 + upstream Bug #745836 [wget] wget: certificate revocation is not checked Added tag(s) upstream. clone -1 -2 Bug #745836 [wget] wget: certificate revocation is not checked Bug 745836 cloned as bug 767283 severity -1 wishlist Bug #745836 [wget] wget: certificate revocation is not checked Severity set to 'wishlist' from 'grave' retitle -2 wget manpage doesn't warn that certificate revocation lists are not checked Bug #767283 [wget] wget: certificate revocation is not checked Changed Bug title to 'wget manpage doesn't warn that certificate revocation lists are not checked' from 'wget: certificate revocation is not checked' -- 745836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745836 767283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767283 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#765870: systemd-logind brings system to knees with RAM consumption
Hi, John Goerzen wrote (26 Oct 2014 19:02:28 GMT) : root@hephaestus:/var/log# grep logind * didn't return anything except my sudo killalll systemd-logind commands! Neither did zgrep -i logind * Thanks. What's the output of: # systemctl status systemd-logind.service ? (I'll soon be out of clues, so if one of the maintainers wants to take it from here, don't hesitate.) Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767287: trafficserver: ftbfs on kfreebsd
package: trafficserver version: 5.1.0-1 severity: serious Hi, The latest upload of trafficserver ftbfs on kfreebsd, where it build fine before. This prevents migration to testing. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767291: blitz++: FTBFS on mips
package: blitz++ version: 1:0.10-2 severity: serious Hi, It seems the latest upload of blitz++ failed on mips, but it built fine before. This prevents migration to testing. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
Control: owner -1 ! On 29-10-14 16:50, Dominik George wrote: The origin of the bug is in line 411 of dbconfig-generate-include. Arggg, so by fixing a very similar issue (bug 720517) for the case above (with ufc) I introduced an RC bug for the non-ufc case. Terribly sorry about that. On upgrade, any new file is written to a temp file, which has default permissions (as in, those of the user running the script, normally root, and their umask). Attached is a patch that replicates the permissions of any old configuration to the tempfile so they do not get lost. I think this patch doesn't work when installing a new package (it does work on upgrades). So I think the two added lines need to be within an 'if [ -e $outputfile ] ; then' statement. Unfortunately, I can't check further today, but I will try to work on this tomorrow evening (CET) and make the release team aware of the fix. Paul signature.asc Description: OpenPGP digital signature
Bug#761170: upstream
OK, I'm about to request an upload of 0.21.2. Seems that it's still failing on kfreebsd. 1) Failure: repo::init::extended_1 [/home/russell/libgit2-0.21.2/tests/repo/init.c:340] Function call failed: (git_repository_init_ext(_repo, root/b/c.git, opts)) error -1 - Failed to set permissions on 'root/b/c.git': Operation not permitted 2) Failure: repo::init::extended_with_template_and_shared_mode [/home/russell/libgit2-0.21.2/tests/repo/init.c:489] Function call failed: (git_repository_init_ext(_repo, init_shared_from_tpl, opts)) error -1 - Failed to set permissions on 'init_shared_from_tpl/.git': Operation not permitted I can't test the sparc so I'm hoping that these problems have been fixed. But I can't confirm. I have been unable to replicate the rebuild issues with the package, so it's unlikely that they have been fixed. http://aws-logs.debian.net/ftbfs-logs/2014/09/13/libgit2_0.21.1-1_unstable.log http://aws-logs.debian.net/ftbfs-logs/2014/09/26/libgit2_0.21.1-1_unstable.log http://aws-logs.debian.net/ftbfs-logs/2014/10/12/libgit2_0.21.1-1_unstable.log 1) Failure: clone::nonetwork::local_absolute_path [/«PKGBUILDDIR»/tests/clone/nonetwork.c:91] Function call failed: (git_clone(g_repo, local_src, ./foo, g_options)) error -1 - git_path_direach callback returned -1 -- Cheers, Russell -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
Processing control commands: owner -1 ! Bug #767248 [dbconfig-common] dbconfig-common: removes permissions of include files on Owner recorded as Paul Gevers elb...@debian.org. -- 767248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767248 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#767302: gwrite: GWrite crashes when pressing save button
Package: gwrite Version: 0.5.1-2 Severity: grave Justification: causes non-serious data loss Dear Maintainer, when clicking the „Save“ button, I expected GWrite to save my content. What I did not expect was GWrite crashing immediately, sigabrt style. ---snib--- /usr/lib/pymodules/python2.7/gwrite/gwrite.py:916: GtkWarning: gtk_menu_attach_to_widget(): menu already attached to GtkImageMenuItem toolbutton_open.set_menu(menu_recent) Attempt to unlock mutex that was not locked abort ---snab--- Note that GWrite still saves the HTML content if a file has been opened. For a new file, information is lost when using the “Save” button. This seems pretty ｅｄｇｙ to me, if you know what I mean. (ノಠ益ಠ)ノ彡┻━┻ -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (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 gwrite depends on: ii mimetex 1.74-1 ii python 2.7.8-1 ii python-gtk2 2.24.0-4 ii python-jswebkit 0.0.3-2 ii python-support 1.0.15 ii python-webkit1.1.8-3 ii wv 1.2.9-4 gwrite recommends no packages. gwrite 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: fixed 757057 in 3:6.03~pre19+dfsg-1
Processing commands for cont...@bugs.debian.org:
fixed 757057 3:6.03~pre19+dfsg-1
Bug #757057 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[extlinux] lack of depency on syslinux-stuff breaks extlinux on kernel upgrade
Marked as fixed in versions syslinux/3:6.03~pre19+dfsg-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
757057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757057
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#766884: libxml2: lots of validity error : ID ... already defined errors with xmllint --valid
Hi Vincent, Vincent Lefevre wrote (26 Oct 2014 22:00:30 GMT) : Severity: grave Justification: renders package unusable Does this bug really make libxml2 unusable for everybody? I see it has a lot of reverse-dependencies, so it should be easy to check. If that were not the case, then I think this bug should have severity important: a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. Simple testcase: [...] $ xmllint --noent --noout tst.xml tst.xml:2: element item: validity error : ID a already defined I can reproduce this failure in a clean sid chroot. I can't in a clean Jessie chroot. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763769: Thanks
tag 763769 + pending I've been pretty busy during the last weeks and the last time I looked at this bug, the upstream patch didn't exist yet. I will prepare a 3.2.0 upload including the upstream patch. -- ceterum censeo microsoftem esse delendam. signature.asc Description: PGP signature
Processed (with 3 errors): Re: Bug#763769: Thanks
Processing commands for cont...@bugs.debian.org: tag 763769 + pending Bug #763769 [glabels] glabels exists with Abort when creating a new document Added tag(s) pending. I've been pretty busy during the last weeks and the last time I looked Unknown command or malformed arguments to command. at this bug, the upstream patch didn't exist yet. Unknown command or malformed arguments to command. I will prepare a 3.2.0 upload including the upstream patch. Unknown command or malformed arguments to command. -- Stopping processing here. Please contact me if you need assistance. -- 763769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763769 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#747802: epiphany-browser: FTBFS: error Headers webkit2/webkit2.h and webkit2/webkit-web-extension.h cannot be included together.
Hi, Vincent Bernat wrote (10 Oct 2014 08:48:43 GMT) : I also get this error with a more recent version of the package. I can't reproduce this error when building 3.14.1-1 (up-to-date sid chroot, pbuilder, DEB_BUILD_OPTIONS=parallel=5; same with parallel=1). Maybe the problem only arises in some specific build environments? Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
