Bug#739424: gnupg dies with gpg: out of secure memory [...] since 1.4.16-1
On Tue, 18 Feb 2014 18:26, r...@debian.org said: 10240-bit RSA key, ID 4A11C97A, created 2009-09-23 ^^ !!! gpg: (this may be caused by too many secret keys used simultaneously or due to excessive large key sizes) There are reasons why upstream gpg does not allow the creation of such stupidly long keys. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740808: strongswan-starter and openswan: error when trying to install together
Package: openswan,strongswan-starter Version: openswan/1:2.6.38-1 Version: strongswan-starter/5.1.1-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-03-05 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Preconfiguring packages ... Selecting previously unselected package libdb5.3:amd64. (Reading database ... 10947 files and directories currently installed.) Preparing to unpack .../libdb5.3_5.3.28-3_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28-3) ... Selecting previously unselected package libkeyutils1:amd64. Preparing to unpack .../libkeyutils1_1.5.6-1_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.6-1) ... Selecting previously unselected package libkrb5support0:amd64. Preparing to unpack .../libkrb5support0_1.12+dfsg-2_amd64.deb ... Unpacking libkrb5support0:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libk5crypto3:amd64. Preparing to unpack .../libk5crypto3_1.12+dfsg-2_amd64.deb ... Unpacking libk5crypto3:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libkrb5-3:amd64. Preparing to unpack .../libkrb5-3_1.12+dfsg-2_amd64.deb ... Unpacking libkrb5-3:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Preparing to unpack .../libgssapi-krb5-2_1.12+dfsg-2_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.12+dfsg-2) ... Selecting previously unselected package libsasl2-modules-db:amd64. Preparing to unpack .../libsasl2-modules-db_2.1.26.dfsg1-9_amd64.deb ... Unpacking libsasl2-modules-db:amd64 (2.1.26.dfsg1-9) ... Selecting previously unselected package libsasl2-2:amd64. Preparing to unpack .../libsasl2-2_2.1.26.dfsg1-9_amd64.deb ... Unpacking libsasl2-2:amd64 (2.1.26.dfsg1-9) ... Selecting previously unselected package libldap-2.4-2:amd64. Preparing to unpack .../libldap-2.4-2_2.4.31-1+nmu2+b1_amd64.deb ... Unpacking libldap-2.4-2:amd64 (2.4.31-1+nmu2+b1) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.1+dfsg1-3_amd64.deb ... Unpacking libxml2:amd64 (2.9.1+dfsg1-3) ... Selecting previously unselected package librtmp0:amd64. Preparing to unpack .../librtmp0_2.4+20121230.gitdf6c518-1_amd64.deb ... Unpacking librtmp0:amd64 (2.4+20121230.gitdf6c518-1) ... Selecting previously unselected package libssh2-1:amd64. Preparing to unpack .../libssh2-1_1.4.3-2_amd64.deb ... Unpacking libssh2-1:amd64 (1.4.3-2) ... Selecting previously unselected package libcurl3:amd64. Preparing to unpack .../libcurl3_7.35.0-1_amd64.deb ... Unpacking libcurl3:amd64 (7.35.0-1) ... Selecting previously unselected package libgeoip1:amd64. Preparing to unpack .../libgeoip1_1.6.0-1_amd64.deb ... Unpacking libgeoip1:amd64 (1.6.0-1) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a5.1.3+dfsg-1_amd64.deb ... Unpacking libgmp10:amd64 (2:5.1.3+dfsg-1) ... Selecting previously unselected package openssl. Preparing to unpack .../openssl_1.0.1f-1_amd64.deb ... Unpacking openssl (1.0.1f-1) ... Selecting previously unselected package libisc95. Preparing to unpack .../libisc95_1%3a9.9.5.dfsg-2_amd64.deb ... Unpacking libisc95 (1:9.9.5.dfsg-2) ... Selecting previously unselected package libdns100. Preparing to unpack .../libdns100_1%3a9.9.5.dfsg-2_amd64.deb ... Unpacking libdns100 (1:9.9.5.dfsg-2) ... Selecting previously unselected package libisccc90. Preparing to unpack .../libisccc90_1%3a9.9.5.dfsg-2_amd64.deb ... Unpacking libisccc90 (1:9.9.5.dfsg-2) ... Selecting previously unselected package libisccfg90. Preparing to unpack .../libisccfg90_1%3a9.9.5.dfsg-2_amd64.deb ... Unpacking libisccfg90 (1:9.9.5.dfsg-2) ... Selecting previously unselected package libbind9-90. Preparing to unpack .../libbind9-90_1%3a9.9.5.dfsg-2_amd64.deb ... Unpacking libbind9-90 (1:9.9.5.dfsg-2) ... Selecting previously unselected package liblwres90. Preparing to unpack .../liblwres90_1%3a9.9.5.dfsg-2_amd64.deb ... Unpacking liblwres90 (1:9.9.5.dfsg-2) ... Selecting previously unselected package bind9-host. Preparing to unpack .../bind9-host_1%3a9.9.5.dfsg-2_amd64.deb ... Unpacking bind9-host (1:9.9.5.dfsg-2) ... Selecting previously unselected package host. Preparing to unpack .../host_1%3a9.9.5.dfsg-2_all.deb ... Unpacking host (1:9.9.5.dfsg-2) ... Selecting previously unselected package openswan. Preparing to unpack .../openswan_1%3a2.6.38-1_amd64.deb ... Unpacking openswan (1:2.6.38-1) ... Selecting previously unselected package libstrongswan. Preparing to unpack .../libstrongswan_5.1.1-3_amd64.deb ... Unpacking libstrongswan (5.1.1-3) ... Selecting previously unselected package strongswan-starter. Preparing to unpack .../strongswan-starter_5.1.1-3_amd64.deb ... Unpacking strongswan-starter (5.1.1-3) ... dpkg: error processing archive /var/cache/apt/archives/strongswan-starter_5.1.1-3_amd64.deb
Bug#740807: slimit: homepage link outdated
Package: slimit Version: 0.7.4-1, 0.8.1-1 Severity: minor Dear TANIGUCHI, Dear Python Application Maintainers, the homepage is still given as slimit.org, a current request to that page shows that it does not carry the homepage anymore. archive.org confirms that this has been the case for at least a year. I recomment chaning the url in the .dsc to what pypy has: Home Page: http://slimit.readthedocs.org In addition it is probably a good idea to patch other places as well. Best Regards and thanks for maintaining slimit, Bernhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740799: ITP: libapp-ddflare-perl -- Provides ddflare, a command line Dynamic DNS utility that updates with the latest IP every 5 minutes
On Wed, 05 Mar 2014 04:47:27 +, Peter Roberts wrote: * Package name: libapp-ddflare-perl Version : 0.05 Upstream Author : Peter Roberts me+...@peter-r.co.uk * URL : http://metacpan.org/release/App-DDFlare * License : MIT Programming Lang: Perl Description : Provides ddflare, a CloudFlare command line Dynamic DNS utility Provides a command line utility, ddflare, which can be used to keep CloudFlare DNS records up to date automatically. If this is more an app than a library, I suggest to name the (source and binary) package ddflare. Cf. http://pkg-perl.alioth.debian.org/policy.html#package_naming_policy Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #189: SCSI's too wide. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740800: ITP: python-crontab -- Python module for reading and writing crontab files
Hello, On 5 March 2014 05:53, Jordan Metzmeier jmetzmeie...@gmail.com wrote: * Package name: python-crontab Version : 1.7.2 Upstream Author : Martin Owens docto...@gmail.com * URL : https://launchpad.net/python-crontab * License : GPL-3 Programming Lang: Python Description : Python module for reading and writing crontab files How does it compare with the crontab support python-reconfigure provides? I think it would be cool to merge missing features from both (if there are any). -- Cheers, Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740724: bluefish hangs while ptrobably waiting for a connection to the server
Package: bluefish Version: 2.2.5-3 Followup-For: Bug #740724 Dear Maintainer, nothing new, just mentioning that the program hangs, and would exit only with killall -9 bluefish. best regards, alex -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (300, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bluefish depends on: ii bluefish-data2.2.5-3 ii bluefish-plugins 2.2.5-3 ii gvfs-backends1.16.3-2 ii libc62.17-97 ii libcairo21.12.16-2 ii libenchant1c2a 1.6.0-10 ii libgdk-pixbuf2.0-0 2.30.5-1 ii libglib2.0-0 2.38.2-5 ii libgtk-3-0 3.10.7-1 ii libpango-1.0-0 1.36.0-1+b1 ii libpangocairo-1.0-0 1.36.0-1+b1 ii libxml2 2.9.1+dfsg1-3 bluefish recommends no packages. Versions of packages bluefish suggests: ii chromium [www-browser] 32.0.1700.123-1 pn csstidy none ii dos2unix6.0.4-1 ii epiphany-browser [www-browser] 3.8.2-5 ii iceweasel [www-browser] 27.0.1-1 ii libxml2-utils 2.9.1+dfsg1-3 ii lynx-cur [www-browser] 2.8.8pre5-1 ii midori [www-browser]0.4.3+dfsg-0.1 ii netsurf-gtk [www-browser] 2.9-2+b1 ii opera [www-browser] 12.11.1661 pn php-codesniffer none pn pylint none ii tidy20091223cvs-1.2 ii uzbl [www-browser] 0.0.0~git.20120514-1.1 ii weblint-perl [weblint] 2.20+dfsg-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740702: ITP: eso-midas -- European Southern Observatory Munich Image Data Analysis System
Dear Julian, On 04.03.2014 20:52, Julian Taylor wrote: midas is unsupported upstream and should die, I don't think there is much point in packaging it. What do you mean with unsupported? The current release is released on Jan 12, 2014. The latest history is: 13SEPpl1.2 - 2014-01-12 13SEPpl1.1 - 2013-11-02 13SEPpl1.0 - 2013-09-07 12FEBpl1.3 - 2012-06-23 12FEBpl1.2 - 2012-04-23 12FEBpl1.1 - 2012-04-02 12FEBpl1.0 - 2012-02-02 11SEPpl1.2 - 2011-12-06 11SEPpl1.1 - 2011-11-07 11SEPpl1.0 - 2011-10-07 which shows a regular (~yearly) version cycle with bugfix releases after each (including the latest one). Neither the web page nor the included documentation claim the end of maintenance. Just the direct Midas support ended in 2012: As of May 2012 there will be no more direct Midas support offered by ESO. Instead, users who have problems or questions concerning ESO-MIDAS running on their systems are advised to use the moderated mailing list midas-us...@eso.org for obtaining feedback and solutions to their questions from other users. This sounds like the normal case for a software package. Take eso-skycat as an example for a software unmaintained by ESO (but maintenance has taken over by Starlink, so it is still not dead). I agree that ESO-MIDAS is an old piece of software, with a design from the early nineties, quite ugly etc. However, is has its user base. And since I was asked for some help in installing ESO-MIDAS, I think it is still a good idea to have it packaged. When searching on the net, you also still find some recent tutorials on using ESO-MIDAS. Astronomers seem to be quite conservative when it comes to software tools: IRAF is 20 years old now, and still in use (and development). Skycat goes back to 1996, given up by ESO in 2008, and still somehow alive. Or have a look, on what packages SAOImage DS9 is based on (funtools, blt, tkhtml3): zombies everywhere. Heavily used today. Best regards Ole -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740795: problems installing debian without internet connection
Hi Jay, Jay Philips philip...@hotmail.com (2014-03-05): Package: debian-installer I was installing debian from the 7.4 64-bit xfce installer and chose not to setup my internet settings, but during the grub bootloader installation part, I got the following error The 'grub-pc' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot. There is already a report on this and it stated that it was fixed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672689 . I was installing from a 4gb usb. any chance you could switch to the 4th console to see if there are more accurate messages explaining what went wrong when installing grub? Maybe you suffered from the first item documented in errata[1] and grub failed to get set up on the installation medium? 1. https://www.debian.org/releases/wheezy/debian-installer/index.html#errata Mraw, KiBi. signature.asc Description: Digital signature
Bug#740809: RFP: notepadqq -- A lightweight FOSS editor which supports multiple programming languages, has syntax highlighting
Package: wnpp Severity: wishlist * Package name: notepadqq Version : v0.20.0 Upstream Author : Daniele Di Sarli daniele...@gmail.com * URL : http://notepadqq.altervista.org/ * License : GPLv3 Programming Lang: C++ Description : Notepadqq is a lightweight FOSS editor which supports multiple programming languages and syntax highlighting among other features. Notepadqq is a fork of the popular notepad++ source-code editor which supports various programming languages. It is based on the powerful editing component Scintilla. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740808: [Pkg-swan-devel] Bug#740808: strongswan-starter and openswan: error when trying to install together
On Wed, Mar 05, 2014 at 09:10:37AM +0100, Ralf Treinen wrote: Package: openswan,strongswan-starter Version: openswan/1:2.6.38-1 Version: strongswan-starter/5.1.1-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-03-05 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Unpacking strongswan-starter (5.1.1-3) ... dpkg: error processing archive /var/cache/apt/archives/strongswan-starter_5.1.1-3_amd64.deb (--unpack): trying to overwrite '/etc/ipsec.secrets', which is also in package openswan 1:2.6.38-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db (2.6.6-1) ... Errors were encountered while processing: /var/cache/apt/archives/strongswan-starter_5.1.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /etc/init.d/ipsec /etc/ipsec.conf /etc/ipsec.secrets /usr/lib/ipsec/_copyright /usr/lib/ipsec/_updown /usr/sbin/ipsec /usr/share/man/man5/ipsec.conf.5.gz /usr/share/man/man5/ipsec.secrets.5.gz /usr/share/man/man8/ipsec.8.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. Thanks for the report. openSwan is currently unmaintained: it's definitely unmaintained in Debian (last upload from 2012), and it's barely maintained upstream. I think openSwan should be removed altogether, but I can surely add a Conflicts since there's no change openSwan and strongSwan can work together. Regards, -- Yves-Alexis Perez signature.asc Description: Digital signature
Bug#740803: [monit] sysvinit should move from recommends to suggests
monit is not about its web gui. It is a system for proactive monitoring, and these features of monit can conflict with systemd's configuration (e.g. Restart=on-failure). Yes, I know that monit is really useful with stateless init systems. But it can also be useful with others. I don't know how the dependency solver handles this, but right now, monit will trigger sysvinit installation, but systemd-sysv will remove it, as it is referenced as a conflict. If systemd is a real problem for monit, it should be better to add systemd (or systemd-sysv) as a conflictual package. I am not trying to push systemd nor sysv. I am just trying to avoid a war for future users :) And I think monit still has some features that could be useful, even when services are not run by sysv, such as checking processes by sending them some TCP bytes and analyze the answer. Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740778: [Pkg-xfce-devel] Bug#740778: xfce4-netload-plugin: Does not display a menu when right-clicked
Control: tag -1 unreproducible moreinfo. On Tue, Mar 04, 2014 at 05:02:59PM -0500, David Z wrote: Package: xfce4-netload-plugin Version: 1.1.0-1+b1 Severity: normal Tags: upstream All other panel items do this, and I think it's important. Works for me. -- Yves-Alexis Perez signature.asc Description: Digital signature
Bug#740684: [Pkg-xfce-devel] Bug#740684: /usr/share/xfce4/helpers/thunderbird.desktop: mailto: links prepend mailto: to email address in iceweasel
This is not a support channel, so please keep the bug on CC, and make sure your mail are accepted by the BTS. On Tue, Mar 04, 2014 at 03:58:07PM -0600, Nathaniel Beaver wrote: On 03/04/2014 03:40 PM, Yves-Alexis Perez wrote: On Tue, Mar 04, 2014 at 03:24:29PM -0600, Nathaniel Beaver wrote: Bug is reproducible with xfce 4.10.1 on debian unstable with: evince 3.10.0-2 qpdfview 0.4.8-1 mupdf 1.3-1 But only in xfce. When I use a different desktop, I cannot reproduce. What happens when you manually call: exo-open f...@example.com To: f...@example.com exo-open mailto:f...@example.com To: mailto:f...@example.com So there's definitely something fishy with the command. Can you try to manually call thunderbird with the various variants? (I can't test as I'm not a thunderbird user). -- Yves-Alexis Perez signature.asc Description: Digital signature
Bug#740810: moc: Segmentation fault when trying to execute
Package: moc Version: 1:2.5.0~beta2-1 Severity: important Dear Maintainer, In last two days I can't execute mocp because I get a segmentation fault error. Tried with root user with same result. If you need more info, tell me. Thank you. -- David -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages moc depends on: ii libasound21.0.27.2-3 ii libc6 2.17-97 ii libcurl3-gnutls 7.35.0-1 ii libdb5.3 5.3.28-3 ii libfaad2 2.7-8 ii libflac8 1.3.0-2 ii libgcc1 1:4.8.2-16 ii libid3tag00.15.1b-10 ii libjack-jackd2-0 [libjack-0.116] 1.9.9.5+20130622git7de15e7a-1 ii libltdl7 2.4.2-1.7 ii libmad0 0.15.1b-8 ii libmagic1 1:5.17-0.1 ii libmodplug1 1:0.8.8.4-4 ii libmpcdec62:0.1~r459-4 ii libncursesw5 5.9+20140118-1 ii libogg0 1.3.1-1 ii libopusfile0 0.5-1 ii librcc0 0.2.9-3.1+b1 ii libresid-builder0c2a 2.1.1-14 ii libsamplerate00.1.8-7 ii libsidplay2 2.1.1-14 ii libsidutils0 2.1.1-14 ii libsndfile1 1.0.25-9 ii libspeex1 1.2~rc1.1-1 ii libstdc++64.8.2-16 ii libtagc0 1.9.1-2 ii libtinfo5 5.9+20140118-1 ii libvorbis0a 1.3.2-1.3 ii libvorbisfile31.3.2-1.3 ii libwavpack1 4.70.0-1 ii zlib1g1:1.2.8.dfsg-1 moc recommends no packages. Versions of packages moc suggests: ii moc-ffmpeg-plugin 1:2.5.0~beta2-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740811: xdotool seems not to be keyboard layout aware
Package: xdotool Version: 1:3.20130111.1-3.1 Hi, I am using german QWERTZ layout, and when I do xdotool type z, an y reaches the application. This is an xev output while testing xdotool. The first three entries are showing the output when sending the keypress with xdotool type y to xev, the other when directly pressing my y-key in xev. As you can see, the same keycode reaches the application in both cases, but they are mapped to different keysyms MappingNotify event, serial 142, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyPress event, serial 142, synthetic NO, window 0x1c1, root 0x260, subw 0x0, time 5916456, (76,126), root:(2000,132), state 0x10, keycode 52 (keysym 0x7a, z), same_screen YES, XLookupString gives 1 bytes: (7a) z XmbLookupString gives 1 bytes: (7a) z XFilterEvent returns: False KeyRelease event, serial 143, synthetic NO, window 0x1c1, root 0x260, subw 0x0, time 5916460, (76,126), root:(2000,132), state 0x10, keycode 52 (keysym 0x7a, z), same_screen YES, XLookupString gives 1 bytes: (7a) z XFilterEvent returns: False MotionNotify event, serial 143, synthetic NO, window 0x1c1, root 0x260, subw 0x0, time 5916687, (75,126), root:(1999,132), state 0x10, is_hint 0, same_screen YES MappingNotify event, serial 143, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyPress event, serial 143, synthetic NO, window 0x1c1, root 0x260, subw 0x0, time 5917590, (75,126), root:(1999,132), state 0x10, keycode 52 (keysym 0x79, y), same_screen YES, XLookupString gives 1 bytes: (79) y XmbLookupString gives 1 bytes: (79) y XFilterEvent returns: False KeyRelease event, serial 144, synthetic NO, window 0x1c1, root 0x260, subw 0x0, time 5917646, (75,126), root:(1999,132), state 0x10, keycode 52 (keysym 0x79, y), same_screen YES, XLookupString gives 1 bytes: (79) y XFilterEvent returns: False Kind Regards, Michael Stummvoll -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738981: Fwd: Bug#738981: Switch to use generic_fpu for ARM
On Tue, Mar 04, 2014 at 11:49:45AM +0100, Thomas Orgis wrote: In any case ... Riku: Care to run timings of MAD on your configurations? I'm interested in how fast it is producing that 24 bit output on limited CPUs. time madplay -d -o null: convergence_-_points_of_view/*.mp3 /dev/null Cortex A15: real0m33.154s user0m33.045s sys 0m0.110s ARMv5: real1m35.923s user1m18.290s sys 0m0.070s Seems mpg123 wins bragging rights :) thanks, awesome work! Riku -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740812: mysql-client-5.5: mysqlcheck does not handle tables with dots in their names correctly
Package: mysql-client-5.5 Version: 5.5.35+dfsg-2 Severity: normal see upstream bugreport http://bugs.mysql.com/68015 the issue is fixed for 5.6.17, 5.7.4 releases. see: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-4.html Could we backport the fix since the problem is also present in mysql5.5 (and so in wheezy version) Thanks, -- William -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740803: [monit] sysvinit should move from recommends to suggests
On Wed, Mar 05, 2014 at 10:02:31AM +0100, Adrien CLERC wrote: I don't know how the dependency solver handles this, but right now, monit will trigger sysvinit installation, but systemd-sysv will remove it, as it is referenced as a conflict. Only if you install recommends by default. If systemd is a real problem for monit, it should be better to add systemd (or systemd-sysv) as a conflictual package. Systemd configuration in the Debian on beta stage (or worse), there is no Debian policy about this and so on. Therefore I don't waste my time right now to examine whether default Debian's units use some dangerous options. Meanwhile, I'll change this recommends to suggests. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739865: handbrake: When encoding with presets for AppleTV2, container is set to mkv.
Am Mittwoch, den 05.03.2014, 08:54 +0530 schrieb Ramakrishnan Muthukrishnan: Sorry for the late report. Last weekend I used the package in experimental to encode two large files for viewing on AppleTV and it worked perfectly fine! :) Thank you very much for the work uploading the package to experimental and also to the upstream. Much appreciated. \o/ Thanks for testing! Seems high time to update the package description then. :) - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740814: kde-window-manager not available in experimental
Package: kde-window-manager Version: 4:4.11.7-1 Severity: wishlist Dear Maintainer, Altthough I use experimental for years and happily use kde 4.12.x from there, I have still a bunch of packages that are still 4.11.x on my system. The the list belows gives somes, kde-workspace also I wonder why there are not build for 4.12. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12.13 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Versions of packages kde-window-manager depends on: ii kde-runtime 4:4.12.3-1 ii kde-style-oxygen4:4.11.7-1 ii libc6 2.18-4 ii libegl1-mesa [libegl1-x11] 10.1.0~rc2-1 ii libgcc1 1:4.8.2-16 ii libgl1-mesa-glx [libgl1]10.1.0~rc2-1 ii libgles2-mesa [libgles2]10.1.0~rc2-1 ii libice6 2:1.0.8-2 ii libkactivities6 4:4.12.3-1 ii libkcmutils44:4.12.3-1 ii libkdeclarative54:4.12.3-1 ii libkdecorations4abi24:4.11.7-1 ii libkdecore5 4:4.12.3-1 ii libkdeui5 4:4.12.3-1 ii libkio5 4:4.12.3-1 ii libknewstuff3-4 4:4.12.3-1 ii libkwineffects1abi5 4:4.11.7-1 ii libkwinglesutils1 4:4.11.7-1 ii libkwinglutils1abi2 4:4.11.7-1 ii libkworkspace4abi2 4:4.11.7-1 ii libplasma3 4:4.12.3-1 ii libqt4-dbus 4:4.8.5+git209-g718fae5+dfsg-1 ii libqt4-declarative 4:4.8.5+git209-g718fae5+dfsg-1 ii libqt4-script 4:4.8.5+git209-g718fae5+dfsg-1 ii libqtcore4 4:4.8.5+git209-g718fae5+dfsg-1 ii libqtgui4 4:4.8.5+git209-g718fae5+dfsg-1 ii libsm6 2:1.2.1-2 ii libstdc++6 4.8.2-16 ii libx11-62:1.6.2-1 ii libx11-xcb1 2:1.6.2-1 ii libxcb-composite0 1.10-2 ii libxcb-damage0 1.10-2 ii libxcb-image0 0.3.9-1 ii libxcb-keysyms1 0.3.9-1 ii libxcb-randr0 1.10-2 ii libxcb-render0 1.10-2 ii libxcb-shape0 1.10-2 ii libxcb-sync11.10-2 ii libxcb-xfixes0 1.10-2 ii libxcb1 1.10-2 ii libxcursor1 1:1.1.14-1 ii libxext62:1.3.2-1 ii libxrandr2 2:1.4.2-1 ii libxxf86vm1 1:1.1.3-1 ii perl5.18.2-2+b1 kde-window-manager recommends no packages. kde-window-manager suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740813: wrong path for .cmake file
Package: libinsighttoolkit4-dev Version: 4.5.0-3 Severity: serious All *.cmake files (platform independent) should go under /usr/share/cmake as for other packages, not in /usr/lib/cmake. See shared-desktop-ontologies for instance. Also eventually consider an -all common package for them insted of distributing all those files in the -dev -any file. I'm not completely persuaded that current way of distributing cmake data for third-parties is coherent, so feel free to pass the ball to cmake maintainers. For instance, I don't know how/if the FindITK.cmake should cowork with the ITK4.5 .cmake stuff. I find the whole thing a bit confused/casual. Or at least not documented in usual places (/usr/share/doc/package) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/1 CPU core) 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 libinsighttoolkit4-dev depends on: ii libc6 2.18-4 ii libdcmtk2-dev 3.6.0-15+b1 ii libgcc1 1:4.8.2-16 ii libgdcm2-dev 2.4.1-2+b1 ii libgdcm2.42.4.1-2+b1 ii libinsighttoolkit4.5 4.5.0-3 ii libjpeg8 8d-2 ii libpng12-01.2.50-1 ii libstdc++64.8.2-16 ii libtiff5 4.0.3-8 ii zlib1g1:1.2.8.dfsg-1 Versions of packages libinsighttoolkit4-dev recommends: ii libfftw3-dev 3.3.3-7 ii uuid-dev 2.20.1-5.6 Versions of packages libinsighttoolkit4-dev suggests: pn insighttoolkit4-examples none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738981: Fwd: Bug#738981: Switch to use generic_fpu for ARM
On Tue, Mar 04, 2014 at 02:59:44AM +, peter green wrote: On Sun, Mar 02, 2014 at 09:06:44AM -0500, Reinhard Tartler wrote: That sounds like if the mpg123 package should use: on armel: --with-cpu=arm_nofpu on armhf: --with-cpu=arm_fpu Does this make sense to everybody? Seems sane to me. armv7 devices without neon are relatively uncommon so while it's important that they are supported it's IMO not vitally important to squeeze out every last drop of performance from them. I wonder what we should use on raspbian? I haven't tested on a Pi yet but it seems that on all tests i've seen so-far the generic fpu code is quite a bit slower than the arm nofpu code. Is there any quality difference from using a fpu vs nonfpu decoder? If so how much performance degredation do you beleive should be accepted in exchange for that quality improvement. I think nofpu would good for raspian. Any lost audio quality would unnoticable on the Rasberry's analog audio output ;) Peter, what's the recommended way to recognize raspbian in debian/rules ? Riku -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740803: [monit] sysvinit should move from recommends to suggests
Le 05/03/2014 10:29, Sergey B Kirpichev a écrit : Only if you install recommends by default. I think this is the case right now. But I can't confirm this, because I've written APT::Install-Recommends false; in my apt.conf a long time ago to avoid installing too much packages. Systemd configuration in the Debian on beta stage (or worse), there is no Debian policy about this and so on. Therefore I don't waste my time right now to examine whether default Debian's units use some dangerous options. Meanwhile, I'll change this recommends to suggests. You're absolutely right on this, it's not your job to check every corner case between init and monit. But I think that someone who install monit should have basic knowledge on how it interacts with init. Anyway, thanks for the change. Adrien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740427: 10mount uses --bind on kfreebsd
Robert Millan r...@debian.org writes: On 01/03/2014 13:14, Christoph Egger wrote: E: 10mount: + mount --bind /srv/chroot/sid /var/lib/schroot/mount/unstable-kfreebsd-amd64-sbuild-1393679326-19038 I don't have time to send a patch, but FTR that line ought to be: mount -t nullfs /srv/chroot/sid /var/lib/schroot/mount/unstable-kfreebsd-amd64-sbuild-1393679326-19038 Right. There's even code for this but for some reason $HOST_OS seems to be unset during execution of 10mount. Should it be set by schroot? Does 10mount miss a HOST_OS=`uname -a` somewhere near the top? Christoph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740815: zabbix-server-mysql: snmp monitoring not works if snmp MIBs are missing
Package: zabbix-server-mysql Version: 1:2.0.9+dfsg-1~bpo70+2 Severity: normal Please add 'snmp-mibs-downloader' as soft dependency. If snmp MIBs are missing, zabbix server fails to query snmp-monitored host. It looks like this (fragment from log): 8133:20140305:202326.714 SNMP item [sysUpTime] on host [rb2011] failed: first network error, wait for 15 seconds No log handling enabled - turning on stderr logging MIB search path: //.snmp/mibs:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp Cannot find module (SNMPv2-MIB): At line 1 in (none) snmp_build: unknown failure 8135:20140305:202341.823 SNMP item [sysUpTime] on host [rb2011] failed: another network error, wait for 15 seconds snmp_build: unknown failure 8135:20140305:202356.859 SNMP item [sysUpTime] on host [rb2011] failed: another network error, wait for 15 seconds snmp_build: unknown failure 8135:20140305:202411.895 SNMP item [sysUpTime] on host [rb2011] failed: another network error, wait for 15 seconds snmp_build: unknown failure 8135:20140305:202427.047 temporarily disabling SNMP checks on host [rb2011]: host unavailable After i install this package manually, everything begin works: 19292:20140305:203130.207 enabling SNMP checks on host [rb2011]: host became available I think, the same issue exists for 'zabbix-server-pgsql' package -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages zabbix-server-mysql depends on: ii adduser 3.113+nmu3 ii fping 3.2-1 ii libc6 2.13-38+deb7u1 ii libcurl3-gnutls 7.26.0-1+wheezy8 ii libiksemel3 1.2-4 ii libldap-2.4-2 2.4.31-1+nmu2 ii libmysqlclient18 5.5.35+dfsg-0+wheezy1 ii libodbc1 2.2.14p2-5 ii libopenipmi0 2.0.16-1.3 ii libsnmp15 5.4.3~dfsg-2.7 ii libssh2-1 1.4.2-1.1 ii lsb-base 4.1+Debian8+deb7u1 ii ucf 3.0025+nmu3 Versions of packages zabbix-server-mysql recommends: ii mysql-server 5.5.35+dfsg-0+wheezy1 pn snmpd none Versions of packages zabbix-server-mysql suggests: ii logrotate3.8.1-4 ii zabbix-frontend-php 1:2.0.9+dfsg-1~bpo70+2 -- Configuration Files: /etc/default/zabbix-server changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740816: gnome-control-center: ntpdate missing for network time
Package: gnome-control-center Version: 1:3.4.3.1-2 Severity: normal Tags: d-i Dear Maintainer, I installed a fresh Wheezy 7.4 system from a netinst.iso. After some days I got aware, that the clock on my computer was slow. I toggled network time to on, with no result. After I installed the ntpdate package, the clock adjusted itself. So I suggest to - either make the gnome-control-center package depend on the ntpdate package - or install the ntpdate package in the default installation Best regards Jan Michael Greiner -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-control-center depends on: ii accountsservice0.6.21-8 ii apg2.2.3.dfsg.1-2 ii desktop-file-utils 0.20-0.1 ii gnome-control-center-data 1:3.4.3.1-2 ii gnome-desktop3-data3.4.2-1 ii gnome-icon-theme 3.4.0-2 ii gnome-icon-theme-symbolic 3.4.0-2 ii gnome-menus3.4.2-5 ii gnome-settings-daemon 3.4.2+git20121218.7c1322-3+deb7u3 ii gsettings-desktop-schemas 3.4.2-3 ii libatk1.0-02.4.0-2 ii libc6 2.13-38+deb7u1 ii libcairo-gobject2 1.12.2-3 ii libcairo2 1.12.2-3 ii libcanberra-gtk3-0 0.28-6 ii libcanberra0 0.28-6 ii libcheese-gtk213.4.2-2 ii libcheese3 3.4.2-2 ii libclutter-1.0-0 1.10.8-2 ii libcogl-pango0 1.10.2-7 ii libcogl9 1.10.2-7 ii libcolord1 0.1.21-1 ii libcomerr2 1.42.5-1.1 ii libcups2 1.5.3-5+deb7u1 ii libdbus-1-31.6.8-1+deb7u1 ii libdbus-glib-1-2 0.100.2-1 ii libfontconfig1 2.9.0-7.1 ii libgcrypt111.5.0-5+deb7u1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgnome-bluetooth10 3.4.2-1 ii libgnome-desktop-3-2 3.4.2-1 ii libgnome-menu-3-0 3.4.2-5 ii libgnomekbd7 3.4.0.2-1 ii libgnutls262.12.20-8+deb7u1 ii libgoa-1.0-0 3.4.2-2 ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u1 ii libgstreamer0.10-0 0.10.36-1.2 ii libgtk-3-0 3.4.2-7 ii libgtop2-7 2.28.4-3 ii libjson-glib-1.0-0 0.14.2-1 ii libk5crypto3 1.10.1+dfsg-5+deb7u1 ii libkrb5-3 1.10.1+dfsg-5+deb7u1 ii libnm-glib40.9.4.0-10 ii libnm-gtk0 0.9.4.1-5 ii libnm-util20.9.4.0-10 ii libnotify4 0.7.5-1 ii libpango1.0-0 1.30.0-1 ii libpolkit-gobject-1-0 0.105-3 ii libpulse-mainloop-glib02.0-6.1 ii libpulse0 2.0-6.1 ii libsocialweb-client2 0.25.20-2.1 ii libupower-glib10.9.17-1 ii libwacom2 0.6-1 ii libx11-6 2:1.5.0-1+deb7u1 ii libxcomposite1 1:0.4.3-2 ii libxdamage11:1.1.3-2 ii libxext6 2:1.3.1-2+deb7u1 ii libxfixes3 1:5.0-4+deb7u1 ii libxi6 2:1.6.1-1+deb7u1 ii libxklavier16 5.2.1-1 ii libxml22.8.0+dfsg1-7+nmu2 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages gnome-control-center recommends: ii cups-pk-helper 0.2.3-3 ii gnome-online-accounts 3.4.2-2 ii gnome-session 3.4.2.1-4 ii gnome-user-guide 3.4.2-1+build1 ii iso-codes 3.41-1 ii mesa-utils 8.0.1-2+b3 ii mousetweaks3.4.2-1 ii policykit-1-gnome 0.105-2 Versions of packages gnome-control-center suggests: ii gnome-screensaver 3.4.1-1 ii gstreamer0.10-pulseaudio 0.10.31-3+nmu1 ii libcanberra-gtk-module0.28-6 ii x11-xserver-utils 7.7~3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740716: libwireshark-dev: please add pkg-config support for libwireshark-dev
tags 740716 confirmed upstream
forwarded 740716 https://code.wireshark.org/review/#/c/500/
thanks
Hi Sebastian,
2014-03-04 12:00 GMT+01:00 Sebastian Reichel s...@debian.org:
Package: libwireshark-diev
Version: 1.10.5-2
Severity: wishlist
Hi,
It would be nice to have a *.pc file for libwireshark-dev. It should
contain cflags and libs needed to build against libwireshark and the
plugin directory. For example the x86-64 could look similar to this:
/usr/lib/x86_64-linux-gnu/pkgconfig/wireshark.pc
---
prefix=/usr
exec_prefix=${prefix}
libdir=${prefix}/lib/x86_64-linux-gnu
sharedlibdir=${libdir}
includedir=${prefix}/include/wireshark
plugindir=${libdir}/wireshark/libwireshark3/plugins
Name: wireshark
Description: wireshark network packet dissection library
Version: 1.10.5
Requires:
Libs: -L${libdir} -L${sharedlibdir} -lwireshark
Cflags: -I${includedir}
---
It will be part of the next upload.
Thanks,
Balint
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On 05/03/14 09:09, Florian Ernst wrote: Hello all, On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: The rsyslog mongodb output module and the PHP mongodb modules are now in wheezy-backports. This would appear to be sufficient to do something like: rsyslog = mongodb = loganalyzer Has anybody else tried that or does anybody have any comments on it (or recommended alternatives)? That actually did work for a time, but something broke starting with rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. As I was merely experimenting with it I didn't follow up any further. Some of this looks like documentation bugs and/or problems with the default config rather than mongodb integration itself LogAnalyzer and rsyslog are from the same upstream too, so I would be surprised if they would not have them working together I had a look at the Git history for the ommongodb, does anything stand out here? https://github.com/rsyslog/rsyslog/commits/master/plugins/ommongodb You state the problem started with 7.4.0-1 - could you comment on the previous set of versions that you had working (both rsyslog and LogAnalyzer versions)? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
[dropping debian-devel] Am 05.03.2014 11:07, schrieb Daniel Pocock: On 05/03/14 09:09, Florian Ernst wrote: Hello all, On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: The rsyslog mongodb output module and the PHP mongodb modules are now in wheezy-backports. This would appear to be sufficient to do something like: rsyslog = mongodb = loganalyzer Has anybody else tried that or does anybody have any comments on it (or recommended alternatives)? That actually did work for a time, but something broke starting with rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. As I was merely experimenting with it I didn't follow up any further. Some of this looks like documentation bugs and/or problems with the default config rather than mongodb integration itself LogAnalyzer and rsyslog are from the same upstream too, so I would be surprised if they would not have them working together I had a look at the Git history for the ommongodb, does anything stand out here? https://github.com/rsyslog/rsyslog/commits/master/plugins/ommongodb You state the problem started with 7.4.0-1 - could you comment on the previous set of versions that you had working (both rsyslog and LogAnalyzer versions)? If the README.Debian (which was based on [1]) is no longer correct, please let me know. If you are using the 7.4.0 backport for wheezy, make sure to also use the libjson-c 0.11 backport. [1] http://git.adiscon.com/?p=rsyslog.git;a=blob;f=plugins/ommongodb/README;hb=HEAD -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On 05/03/14 11:26, Michael Biebl wrote: [dropping debian-devel] Am 05.03.2014 11:07, schrieb Daniel Pocock: On 05/03/14 09:09, Florian Ernst wrote: Hello all, On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: The rsyslog mongodb output module and the PHP mongodb modules are now in wheezy-backports. This would appear to be sufficient to do something like: rsyslog = mongodb = loganalyzer Has anybody else tried that or does anybody have any comments on it (or recommended alternatives)? That actually did work for a time, but something broke starting with rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. As I was merely experimenting with it I didn't follow up any further. Some of this looks like documentation bugs and/or problems with the default config rather than mongodb integration itself LogAnalyzer and rsyslog are from the same upstream too, so I would be surprised if they would not have them working together I had a look at the Git history for the ommongodb, does anything stand out here? https://github.com/rsyslog/rsyslog/commits/master/plugins/ommongodb You state the problem started with 7.4.0-1 - could you comment on the previous set of versions that you had working (both rsyslog and LogAnalyzer versions)? If the README.Debian (which was based on [1]) is no longer correct, please let me know. If you are using the 7.4.0 backport for wheezy, make sure to also use the libjson-c 0.11 backport. [1] http://git.adiscon.com/?p=rsyslog.git;a=blob;f=plugins/ommongodb/README;hb=HEAD Michael, thanks for the fast response on this In the bug report, it goes on to say that after correcting the first issue, I can dump data to mongodb again, though the format doesn't match previous entries. and then the email to debian-devel suggests that LogAnalyzer can no longer read the data (even though it is there) It is this latter issue that I am curious about - is it a deliberate schema change? Is it just the libjson-c version (and can you add that to the control file)? Does it require some newer version of LogAnalyzer (and is anyone aware if upstream is working on that, if it is unreleased, etc)? I also queried it upstream: https://github.com/rsyslog/rsyslog/issues/46 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740803: [monit] sysvinit should move from recommends to suggests
On 05 Mar 2014, at 10:02, Adrien CLERC bugs-deb...@antipoul.fr wrote: monit is not about its web gui. It is a system for proactive monitoring, and these features of monit can conflict with systemd's configuration (e.g. Restart=on-failure). Yes, I know that monit is really useful with stateless init systems. But it can also be useful with others. I don't know how the dependency solver handles this, but right now, monit will trigger sysvinit installation, but systemd-sysv will remove it, as it is referenced as a conflict. If systemd is a real problem for monit, it should be better to add systemd (or systemd-sysv) as a conflictual package. I am not trying to push systemd nor sysv. I am just trying to avoid a war for future users :) And I think monit still has some features that could be useful, even when services are not run by sysv, such as checking processes by sending them some TCP bytes and analyze the answer. Adrien Hi, Monit can work in systemd environment fine, you just need to use systemd's start/stop methods as Monit's start/stop program. You can then set Monit to check the process (including cpu usage, memory usage, network service test, etc.) and ask systemd to restart the process in case of failure (if Monit uses ... then restart action in the testing rule). Since Monit 5.7 there is also restart program, which is more straightforward then original restart=stop+start. Regards, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739490: iceweasel: compiled extensions can not be built with version in wheezy-sec
On 24 February 2014 09:58, Mike Hommey m...@glandium.org wrote: On Wed, Feb 19, 2014 at 10:33:09AM +0100, Raphael Geissert wrote: Package: iceweasel Version: 24.3.0esr-1~deb7u1 Severity: important Hi, As mentioned in a private email, binary extensions fail to build with the backported iceweasel/xulrunner in wheezy-sec, but they do build with the version in sid. An example that is easy to try is mozilla-gnome-keyring. It fails to find the mozilla-nspr pkg-config file, which results in a series of missing files and the build failure. There's also a cannot find -lmozglue error from the linker. Can you try this patch: It can not find prtime.h this time, attached is the relevant part of the build log plus the output of pkg-config. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net dpkg-source --before-build mozilla-gnome-keyring-0.6.9 debian/rules clean test -x debian/rules dh_testroot dh_clean dh_testdir dh_clean make -C debian -f Makefile.combined clean-all make[1]: Entering directory `/tmp/mozilla-gnome-keyring-0.6.9/debian' rm -rf link-xulrunner xpi-xulrunner link-icedove xpi-icedove xpi rm -f ../mozilla-gnome-keyring-0.6.9.xpi cd .. make -f Makefile clean-all make[2]: Entering directory `/tmp/mozilla-gnome-keyring-0.6.9' rm -f libgnomekeyring.so rm -f mozilla-gnome-keyring-0.6.9.xpi rm -f -r xpi rm -f *.xpi rm -f *.tar.gz rm -f config.vars xpcom_abi make[2]: Leaving directory `/tmp/mozilla-gnome-keyring-0.6.9' make[1]: Leaving directory `/tmp/mozilla-gnome-keyring-0.6.9/debian' debian/rules build test -x debian/rules mkdir -p . make -C debian -f Makefile.combined all make[1]: Entering directory `/tmp/mozilla-gnome-keyring-0.6.9/debian' mkdir -p link-xulrunner make -C link-xulrunner -f ../../Makefile VPATH=../.. \ XPI_TARGET=target.xpi make[2]: Entering directory `/tmp/mozilla-gnome-keyring-0.6.9/debian/link-xulrunner' CXX=g++ XUL_CFLAGS=`pkg-config --cflags libxul` XUL_LDFLAGS=`pkg-config --libs libxul` XPCOM_ABI_FLAGS=`pkg-config --libs-only-L libxul | sed -e 's/-L\(\S*\).*/ -Wl,-rpath=\1/' | sed -n -e 'p;s/^\(.*\)-devel\(.*\)\/lib$/\1\2/gp'` GNOME_CFLAGS=`pkg-config --cflags gnome-keyring-1` GNOME_LDFLAGS=`pkg-config --libs gnome-keyr ing-1` CXXFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -fno-rtti -fno-exceptions -fPIC -std=gnu++0x -D__STDC_LIMIT _MACROS LDFLAGS=-Wl,-z,relro sh ../../config.sh ../../GnomeKeyring.h ../../xpcom_abi.cpp ../../Makefile config.vars In file included from /usr/include/xulrunner-24.0/nsISupports.h:10:0, from /usr/include/xulrunner-24.0/nsILoginManagerStorage.h:10, from ../../GnomeKeyring.h:40, from stdin:1: /usr/include/xulrunner-24.0/nsrootidl.h:14:20: fatal error: prtime.h: No such file or directory compilation terminated. In file included from /usr/include/xulrunner-24.0/nsISupports.h:10:0, from /usr/include/xulrunner-24.0/nsIXULRuntime.h:10, from ../../xpcom_abi.cpp:4: /usr/include/xulrunner-24.0/nsrootidl.h:14:20: fatal error: prtime.h: No such file or directory compilation terminated. make[2]: *** [config.vars] Error 1 make[2]: Leaving directory `/tmp/mozilla-gnome-keyring-0.6.9/debian/link-xulrunner' make[1]: *** [link-xulrunner] Error 2 make[1]: Leaving directory `/tmp/mozilla-gnome-keyring-0.6.9/debian' make: *** [build/xul-ext-gnome-keyring] Error 2 $ pkg-config --libs libxul -L/usr/lib/xulrunner-devel-24.0/lib -lxpcomglue_s -lxul -lmozalloc -lplds4 -lplc4 -lnspr4 -lpthread -ldl To be more precise: $ pkg-config --libs mozilla-nspr -L/usr/lib/xulrunner-devel-24.0/lib -lplds4 -lplc4 -lnspr4 -lpthread -ldl
Bug#740818: Collected resources with a puppet master fail on Ruby 1.9.x
Package: puppet-common Version: 2.7.23-1~deb7u3 Severity: normal Tags: patch upstream Hi, filling as normal, as Ruby 1.9.x is not officially supported for Puppet 2.7. After an upgrade of our puppet master from squeeze+backports to wheezy, nodes that were collecting exported ressources started to fail with the following message: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::Compiler failed with error ArgumentError: wrong number of arguments (1 for 0) on node foobar.example.org This is reported upstream as [1] and fixed since 3.1.0 [2]. While I know that ruby 1.9.x is unsupported, I think backporting this (trivial) fix is useful, as Puppet 2.7 works with ruby 1.9.x quite okay otherwise :) A patch is attached. Regards Evgeni [1] http://projects.puppetlabs.com/issues/10963 [2] https://github.com/puppetlabs/puppet/commit/f60af044487c61c721d9008887ce982278b2f032 -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages puppet-common depends on: ii adduser3.113+nmu3 ii facter 1.6.10-1 ii libaugeas-ruby1.8 0.4.1-1.1 ii lsb-base 4.1+Debian8+deb7u1 ii ruby-shadow2.1.4-2 ii ruby1.81.8.7.358-7.1+deb7u1 ii sysv-rc2.88dsf-41+deb7u1 Versions of packages puppet-common recommends: ii debconf-utils 1.5.49 ii lsb-release4.1+Debian8+deb7u1 Versions of packages puppet-common suggests: pn librrd-ruby1.8 none pn ruby-selinuxnone -- Configuration Files: /etc/puppet/puppet.conf changed [not included] -- no debconf information From: Hunter Haugen h.hau...@gmail.com Date: Thu, 13 Dec 2012 12:52:46 -0800 Subject: [PATCH 1/5] (#10963) Collector overrides should work in Ruby 1.9 Increase arity of child_of? meta_def to 1 child_of? defined for Puppet::Resource::Type objects has an arity of 1, but the meta_def of the same function created by Puppet::Parser::Collector objects has an arity of 0. This throws errors when the meta_def method is called with arguments. This commit matches the arity so that this error will not be present. --- lib/puppet/parser/collector.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: puppet-2.7.23/lib/puppet/parser/collector.rb === --- puppet-2.7.23.orig/lib/puppet/parser/collector.rb 2013-08-14 23:40:30.0 +0200 +++ puppet-2.7.23/lib/puppet/parser/collector.rb 2014-03-05 11:36:03.0 +0100 @@ -31,7 +31,7 @@ # we have an override for the collected resources if @overrides and !objects.empty? # force the resource to be always child of any other resource - overrides[:source].meta_def(:child_of?) do + overrides[:source].meta_def(:child_of?) do |klass| true end
Bug#740814: kde-window-manager not available in experimental
On 03/05/2014 11:33 AM, Debian Bug Tracking System wrote: Upstream are not releasing any further feature updates in the 4.x series. 4.11 workspace is long term supported, and that's why you got a 4.11.7 there while the rest of the packages are at 4.12.x. Other modules will also at a later point stop their feature development in the 4.x series. Thus, closing this bug. I realized that when browsing kde announce for 4.12.3. There is still yet a thing that is not clear for me: the package comes from unstable not experimental. How is it compiled ? with the right includes or linked with the the right libraries. Having it coming from experimental would have been clearer. Thanks for the explanation anyway -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740822: ITP: colpack -- Graph vertex coloring library
Package: wnpp Severity: wishlist Owner: Barak A. Pearlmutter ba...@cs.nuim.ie * Package name: colpack Version : 1.0.9 Upstream Author : Alex Pothen apot...@purdue.edu * URL : http://www.cscapes.org/coloringpage/ * License : LGPL-3+ Programming Lang: C++ Description : Specialized graph vertex coloring library ColPack is a package comprising of implementation of algorithms for specialized vertex coloring problems that arise in sparse derivative computation. It is written in an object-oriented fashion heavily using the Standard Template Library (STL). It is designed to be simple, modular, extenable and efficient. Its primary application has been for use in automatic differentiation. It is already packaged in Fedora. The adolc library package can optionally use it, and my reason for wanting to package colpack is to allow me to enable that option in the debian adolc package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734218: spice: Please support powerpcspe (and maybe other architectures)
Where can I find the rationale for limiting the spice package to amd64 and i386 only? I need it on arm to use it with my Raspberry Pi, and fail to understand why the Debian package is missing there. According to URL: https://admin.fedoraproject.org/pkgdb/acls/name/ , the package is built for armv7hl on Fedora, so the source seem to handle it just fine. URL: http://koji.fedoraproject.org/koji/rpminfo?rpmID=4563258 got some patches, perhaps some of them are needed, but none of them seem arm related? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705607: 1.0 breaks alignment != left
Package: dunst Followup-For: Bug #705607 I upgraded again to dunst 1.0 today, and it seems that it has been resolved, suggesting some likely library issue. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dunst depends on: ii libc62.18-4 ii libcairo21.12.16-2 ii libdbus-1-3 1.8.0-2 ii libfreetype6 2.5.2-1 ii libglib2.0-0 2.38.2-5 ii libpango-1.0-0 1.36.2-2 ii libpangocairo-1.0-0 1.36.2-2 ii libx11-6 2:1.6.2-1 ii libxdg-basedir1 1.2.0-1 ii libxext6 2:1.3.2-1 ii libxft2 2.3.1-2 ii libxinerama1 2:1.1.3-1 ii libxss1 1:1.2.2-1 dunst recommends no packages. dunst suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740820: evolution-rss: RSS feeds with file:/// URLs are not updated
Package: evolution-rss Version: 0.3.91-2 Severity: normal After adding a RSS feed with a file:/// URL (because I needed to write a script to get the actual feed from the net, it required some unconventional authentication) I noticed that it never got updated. It was added under 'News and Blogs', and all the entries that were in the RSS file at the time of adding it were shown, but no new entries ever appeared. I could see that new entries appeared in the RSS file, but they never appeared in Evolution. I had set the update interval for the feed to one minute and waited much longer than that. -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.12-0.bpo.1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages evolution-rss depends on: ii evolution 3.4.4-3 ii evolution-data-server 3.4.4-3 ii gconf-service 3.2.5-1+build1 ii gconf2 3.2.5-1+build1 ii libatk1.0-0 2.4.0-2 ii libc6 2.17-92 ii libcairo-gobject2 1.12.2-3 ii libcairo2 1.12.2-3 ii libcamel-1.2-33 3.4.4-3 ii libebackend-1.2-2 3.4.4-3 ii libebook-1.2-13 3.4.4-3 ii libedataserver-1.2-16 3.4.4-3 ii libedataserverui-3.0-1 3.4.4-3 ii libenchant1c2a 1.6.0-7 ii libevolution3.4.4-3 ii libgcc1 1:4.7.2-5 ii libgconf-2-43.2.5-1+build1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-5 ii libgtk-3-0 3.4.2-7 ii libgtkhtml-4.0-04.4.4-1 ii libgtkhtml-editor-4.0-0 4.4.4-1 ii libjavascriptcoregtk-3.0-0 1.8.1-3.4 ii libnspr42:4.9.6-1~bpo70+1 ii libnss3 2:3.15.2-1~bpo70+1 ii libnss3-1d 2:3.15.2-1~bpo70+1 ii libpango1.0-0 1.30.0-1 ii libsoup-gnome2.4-1 2.38.1-2 ii libsoup2.4-12.38.1-2 ii libsqlite3-03.7.16.2-1~bpo70+1 ii libstdc++6 4.7.2-5 ii libwebkitgtk-3.0-0 1.8.1-3.4 ii libxml2 2.8.0+dfsg1-7+nmu2 evolution-rss recommends no packages. evolution-rss suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740821: Please set PassengerRuby /usr/bin/ruby1.8 in apache2.site.conf.tmpl
Package: puppetmaster-passenger Version: 2.7.23-1~deb7u3 Severity: minor Hi, Ruby 1.9.x is not supported for Puppet 2.7. However, it can happen, that /usr/bin/ruby is ruby 1.9 on wheezy. Passenger will use that to run Puppet under Apache, and this will probably fail. Explicitely adding PassengerRuby /usr/bin/ruby1.8 to the template will (hopefully) hint the admin to use the proper Ruby when deploying Puppet in Apache on Wheezy. Regards Evgeni -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740819: plymouth: Monitor goes off after running X session
Package: plymouth Version: 0.8.8-6+deb8u3 Severity: important Dear Maintainer, * What led up to the situation? Running X session with E17 and composite enabled * What exactly did you do (or not do) that was effective (or ineffective)? Boot system and run startx * What was the outcome of this action? Working X session but after quitting E17 the monitor goes off and I don't know how to make it go online again * What outcome did you expect instead? Monitor staying on and a display of the console currently using an ATI FireMV card the monitor goes offline after running an X session. I don't know quit correctly if this is plymouth's fault, but to report this bug, I file it against plymouth. After quitting E17 the monitor goes offline and I don't know how to resume it. The shell still seems to be there, but the monitor is off. I use Debian/testing with plymouth and E17, composite enabled. Thank you for your efforts. Adrian Immanuel KIEß -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plymouth depends on: ii initramfs-tools0.115 ii libc6 2.17-97 ii multiarch-support 2.17-97 plymouth recommends no packages. Versions of packages plymouth suggests: ii desktop-base 7.0.3 ii plymouth-drm 0.8.8-6+deb8u3 -- Configuration Files: /etc/plymouth/plymouthd.conf changed: [Daemon] Theme=fade-in -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740823: alignment=center|right doesn't work with width=0
Package: dunst Version: 1.0.0-2 Severity: minor With: [global] alignment = right geometry = -0-0 the text is not actually flushed right. The geometry here is aligning the frame to the top-right corner of the screen. Width is empty/0, which means automatic width. If I set a width manually: geometry = 100x-0-0 the text is actually centered/aligned right, suggesting that dunst is not taking the lenght of the longest message before performing the layout of the individual lines, which is what I would like it to do. This used to work in dunst 0.5. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dunst depends on: ii libc62.18-4 ii libcairo21.12.16-2 ii libdbus-1-3 1.8.0-2 ii libfreetype6 2.5.2-1 ii libglib2.0-0 2.38.2-5 ii libpango-1.0-0 1.36.2-2 ii libpangocairo-1.0-0 1.36.2-2 ii libx11-6 2:1.6.2-1 ii libxdg-basedir1 1.2.0-1 ii libxext6 2:1.3.2-1 ii libxft2 2.3.1-2 ii libxinerama1 2:1.1.3-1 ii libxss1 1:1.2.2-1 dunst recommends no packages. dunst suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#715179: spice-client: Please install an alternative for /usr/bin/spice-xpi-client
[Laurent Bigonville] Could you please add an alternative for /usr/bin/spice-xpi-client with a priority of 0 This would be needed for spice-xpi (ITP: #668284) virt-viewer already did the same, see bug #704217 Since today the spice-xpi package in unstable will run /usr/bin/spice-xpi-client when asked to show a SPICE console (See bug #739408). Perhaps time to review this bug report? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
Am 05.03.2014 11:26, schrieb Michael Biebl: [dropping debian-devel] Am 05.03.2014 11:07, schrieb Daniel Pocock: On 05/03/14 09:09, Florian Ernst wrote: Hello all, On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: The rsyslog mongodb output module and the PHP mongodb modules are now in wheezy-backports. This would appear to be sufficient to do something like: rsyslog = mongodb = loganalyzer Has anybody else tried that or does anybody have any comments on it (or recommended alternatives)? That actually did work for a time, but something broke starting with rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. As I was merely experimenting with it I didn't follow up any further. Some of this looks like documentation bugs and/or problems with the default config rather than mongodb integration itself Florian, have you followed the steps outlined in http://www.rsyslog.com/tag/ommongodb/ ? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#740814: kde-window-manager not available in experimental
On Wednesday 05 March 2014 11:41:01 VALETTE Eric OLNC/OLPS wrote: I realized that when browsing kde announce for 4.12.3. There is still yet a thing that is not clear for me: the package comes from unstable not experimental. How is it compiled ? with the right includes or linked with the the right libraries. Having it coming from experimental would have been clearer. There is no new functionality or new requirements in the new kde-workspace, so it compiles just as fine against kdelibs 4.11. ANd should also compile fine against 4.10, 4.9 and 4.8 or something like that. /Sune -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740824: Additional rules to match body and urgency
Package: dunst Version: 1.0.0-2 Severity: wishlist It seems that I cannot match on the urgency of a message (to format it in a different way only for a particular application), and also cannot match the body (which would be helpful to format messages without body). For the first request, this would be my use case: [rule] appname = test ... [rule-exception] appname = test match_urgency = critical script = call a different script so that I don't have to call the script for _every_ notification and do rule-checking again. 'urgency' is already use to _set_ the message urgency, so some new name should be used. Second request use case: [global] format = %s: %b [no-body] body = format = %s Pretty obvious. Thanks. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dunst depends on: ii libc62.18-4 ii libcairo21.12.16-2 ii libdbus-1-3 1.8.0-2 ii libfreetype6 2.5.2-1 ii libglib2.0-0 2.38.2-5 ii libpango-1.0-0 1.36.2-2 ii libpangocairo-1.0-0 1.36.2-2 ii libx11-6 2:1.6.2-1 ii libxdg-basedir1 1.2.0-1 ii libxext6 2:1.3.2-1 ii libxft2 2.3.1-2 ii libxinerama1 2:1.1.3-1 ii libxss1 1:1.2.2-1 dunst recommends no packages. dunst suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740385: rss2email: can't set verbosity in rss2email.cfg
tags 740385 + upstream forwarded 740385 https://github.com/wking/rss2email/issues/28 stop Thanks for the bug report, forwarding it in the upstream BTS (even though upstream is here too :)). -- Etienne Millon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740612: Bug#740810: moc: Segmentation fault when trying to execute
740810 severity grave reassign 740810 librcc-dev 0.2.9-3.1+b1 merge 740810 740612 thanks * David davi...@escomposlinux.org [2014-03-05 10:04 +0100]: Package: moc Version: 1:2.5.0~beta2-1 Severity: important Dear Maintainer, In last two days I can't execute mocp because I get a segmentation fault error. Tried with root user with same result. If you need more info, tell me. This is librcc's fault. See [0]. Elimar [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740612 -- .~. /V\ L I N U X /( )\ Phear the Penguin ^^-^^ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733480: bash 4.3-rc2 gcc-4.9 compiler very slow
Dear Maintainer, This issue is fixed after installing bash 4.3-1 (Sid), compiling with gcc-4.9 is no longer slow. This bug can be closed. Jos van Wolput http://homepages.onsneteindhoven.nl/~wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740825: RFP: xuserrun -- Run commands as the currently-active X11 user
Package: wnpp Severity: wishlist * Package name: xuserrun Version : - Upstream Author : Todd Partridge toddrpartri...@gmail.com, Brain Mattern https://github.com/rephormE * URL : https://github.com/Gen2ly/xuserrun * License : GPLv3+ Programming Lang: Bash Description : Run commands as the currently-active X11 user xuserrun allows a command to be run on the X.org user's display. It determines the DISPLAY and USER environmental variables of the logged-in user necessary to run a program through the X.org server display. Its primary use is to be able to run a X.org program from within another environment (different user, console, cron, boot script...). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740803: [monit] sysvinit should move from recommends to suggests
On Wed, Mar 05, 2014 at 11:35:49AM +0100, Martin Pala wrote: Monit can work in systemd environment fine, you just need to use systemd's start/stop methods as Monit's start/stop program. Yes, it can, if you are sure that your systemd's configuration doesn't use any dangerous features of this bloatware. An example was provided above (Restart option). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734218: spice: Please support powerpcspe (and maybe other architectures)
05.03.2014 15:02, Petter Reinholdtsen wrote: Where can I find the rationale for limiting the spice package to amd64 and i386 only? I need it on arm to use it with my Raspberry Pi, and fail to understand why the Debian package is missing there. http://www.spice-space.org/page/FAQ -- see the Which architecture can spice run on question. This is what upstream says. We may try to let it build on other arches, but not if this requires patches. Thanks, /mjt According to URL: https://admin.fedoraproject.org/pkgdb/acls/name/ , the package is built for armv7hl on Fedora, so the source seem to handle it just fine. URL: http://koji.fedoraproject.org/koji/rpminfo?rpmID=4563258 got some patches, perhaps some of them are needed, but none of them seem arm related? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734435: notmuch-emacs: Emacs cannot load package notmuch
Package: notmuch-emacs Version: 0.17-4 Followup-For: Bug #734435 I had similar bug after upgrading testing, upon M-x notmuch receiving an error message of “symbol's function definition is void: notmuch” David Bremner suggested to “dpkg-reconfigure emacsen-common”, which i did and it fixed the problem. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.11-2-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 notmuch-emacs depends on: ii emacs23 23.4+1-4.1+b1 ii notmuch 0.17-4 notmuch-emacs recommends no packages. notmuch-emacs suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686447: [Pkg-zfsonlinux-devel] any news/reply regarding ZFS in NEW?
On 02/03/14 06:56, Turbo Fredriksson wrote: On Mar 2, 2014, at 4:52 AM, Dimitri John Ledkov wrote: Hostile binary takeover is not allowed - that is two separate source packages should not build the same binary package names, even if on different architectures. Ok, sounds reasonable when you say it like that. I'd still appreciate a link to the policy for that. One possible example of theoretical breakage is to run the command apt-get source libzfs1, right now it downloads the kfreebsd/zfsutils sources, but I don't know what will happen when zfs-linux is allowed into the archives. Is apt intelligent enough to pick the source corresponding to the binary package of the host arch? signature.asc Description: OpenPGP digital signature
Bug#740815: zabbix-server-mysql: snmp monitoring not works if snmp MIBs are missing
On Wed, 5 Mar 2014 20:48:38 Alex 'AdUser' Z wrote: Please add 'snmp-mibs-downloader' as soft dependency. We can't Depend or Recommend non-free package although I think it is possible to Suggest it. Frankly I'm reluctant even to suggest it... Is there are any alternatives from main? -- Regards, Dmitry Smirnov GPG key : 4096R/53968D1B --- All that is necessary for the triumph of evil is that good men do nothing. signature.asc Description: This is a digitally signed message part.
Bug#740826: libjgrapht0.8-java: packaging should be jar not pom
Package: libjgrapht0.8-java Version: 0.8.3-4 Severity: important Hi, The POMs for libjgrapht0.8-java include the following: groupIdorg.jgrapht/groupId artifactIdjgrapht/artifactId packagingpom/packaging I think this latter should be jar not pom, since that's how the compiled java is supplied? mh_resolve_dependencies certainly complains otherwise. This is my fault, since I supplied the POM files in #740360 -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libjgrapht0.8-java depends on: ii libjgraph-java 5.12.4.2+dfsg-2 libjgrapht0.8-java recommends no packages. libjgrapht0.8-java suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740827: should not give 2xx response if database write fails
Package: davical Version: 1.1.1-1 Severity: serious I update a contact record in Evolution and save the record The Apache access.log shows the PUT request with a 204 response The error.log contains various errors The new data is not persisted to the database and there is no feedback in Evolution If Evolution tries to save the contact a second time (e.g. because of a second modification), it receives a 412 response from DAViCal The actual errors that occur in the database (and error.log of Apache) are below, although I would expect that for any error situation at all DAViCal should not be returning 204, I will open a second bug about the cause of this error: Query: QF: SQL error 22007 - ERROR: invalid input syntax for type timestamp with time zone: ... Query: QF: UPDATE caldav_data SET caldav_data=:dav_data, dav_etag=:etag, logged_user=:session_user, modified=:modified, user_no=:user_no, caldav_type='VCARD' WHERE dav_name=:dav_name Query: QF: SQL error 25P02 - ERROR: current transaction is aborted, commands ignored until end of transaction block Query: QF: DELETE FROM addressbook_address_email WHERE dav_id = :dav_id -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740725: [Pkg-haskell-maintainers] Bug#740725: xmonad spins between window when changing focus
Control: tag -1 + upstream Dear Nicolas, Am Dienstag, den 04.03.2014, 13:29 +0100 schrieb Nicolas Évrard: Package: xmonad Version: 0.11-6+b1 Severity: important Dear Maintainer, I use a specific layout for Firefox on my 0 workspace (that is a simpleTabbed noBorders layout). Sometimes (but not always I failed to find how to reproduce this behavior) xmonad goes in a loop when I switch from one firefox window to another. After I have ended this loop (by pressing again the keys that triggers the switch) the focus stays on one of the firefox window (although not the one currently displayed). The only way to break this state is to open a new firefox window. I have also this strange bug on other workspaces but less often. I have attached my xmonad.hs thanks for the report. This bug is most likely an upstream bug, and there is a higher chance to get it fixed if you report it directly at http://code.google.com/p/xmonad/issues/list Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#740826: libjgrapht0.8-java: packaging should be jar not pom
org.jgrapht:jgrapht is of type pom in Maven central, so we are consistent with the upstream artifact: http://search.maven.org/#search|ga|1|g%3A%22org.jgrapht%22 But the type of the artifact org.jgrapht:jgrapht-core is jar. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740296: SimpleITK
Hi, I would look into packaging the software and ask on debian-med for sponsoring, but only after Easter - in case someone else has time and wants to step forward with the packaging. I've seen that the latest versions are 0.7.1.post1 and 0.8rc1. I would ask you to stick to a version numbering that makes it easier to write a regexp for the watch file, i.e. 0.8rc1 should probably be 0.8.0-rc1 (cf [1]). many thanks, Gert [1] http://semver.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690911: [Pkg-ime-devel] Bug#690911: Chinese full stop: U+3002 or U+FF0E?
Control: tags -1 - patch + wontfix Hi, Since upstream maintainer [0] does not think this is a issue, so I just mark this as wontfix. Please discuss with upstream if you still think this patch is necessary, thanks. [0] https://github.com/hime-ime/hime/pull/486 -- ChangZhuo Chen (陳昌倬) czc...@gmail.com Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D signature.asc Description: Digital signature
Bug#740828: DAViCal expects timestamp in REV field of vCard
Package: davical Version: 1.1.1-1 Severity: serious I mark this as serious because DAViCal no longer interoperates with Evolution, the default contact/calendar client in Debian Evolution submits a vCard to DAViCal with a REV field like this: REV:d3b07384d113edec49eaa6238ad5ff00 In the RFCs it suggests it should be a time value and that Evolution may be at fault: http://tools.ietf.org/html/rfc2426#section-3.6.4 https://tools.ietf.org/html/rfc6350#section-6.7.4 DAViCal tries to put it in a timestamp column in PostgreSQL, where it is rejected: Query: QF: SQL error 22007 - ERROR: invalid input syntax for type timestamp with time zone: ... Query: QF: UPDATE caldav_data SET caldav_data=:dav_data, dav_etag=:etag, logged_user=:session_user, modified=:modified, user_no=:user_no, caldav_type='VCARD' WHERE dav_name=:dav_name If this is a fault in evolution, please confirm and reassign the bug there If clients are behaving like this, however, should DAViCal support them in some way? Related issues: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740827 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699353 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740829: ulatencyd: When set user.poison on plugin-container gnome-shell is put on psn_ group wo notice.
Package: ulatencyd
Version: 0.5.0-8
Severity: normal
Hi
On /etc/ulatencyd/simple.conf added on last line
plugin-containeruser.poison
Under /blkio is /psn_2275 which is gnome-shell not plugin-container.
-- System Information:
Debian Release: jessie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.11.0-17-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ulatencyd depends on:
ii dbus 1.8.0-1
ii dpkg 1.17.6
ii libc6 2.17-97
ii libdbus-1-31.8.0-1
ii libdbus-glib-1-2 0.102-1
ii libglib2.0-0 2.38.2-5
ii liblua5.1-05.1.5-5
ii libpolkit-gobject-1-0 0.105-4
ii libxau61:1.0.8-1
ii libxcb11.10-2
ii lua-posix 29-7
ii lua5.1 [lua] 5.1.5-5
Versions of packages ulatencyd recommends:
ii consolekit 0.4.6-4
ulatencyd suggests no packages.
-- Configuration Files:
/etc/init.d/ulatencyd [Errno 2] No such file or directory:
u'/etc/init.d/ulatencyd'
/etc/ulatencyd/scheduler/50-video_playback.lua changed:
--[[
Copyright 2010,2011 ulatencyd developers
This file is part of ulatencyd.
License: GNU General Public License 3 or later
]]--
SCHEDULER_MAPPING_VIDEO_PLAYBACK = {
info = {
description = a scheduler for video playback. EXPERIMENTAL,
hidden = true
}
}
-- cpu memory configuration
SCHEDULER_MAPPING_VIDEO_PLAYBACK[cpu] =
{
{
name = rt_tasks,
cgroups_name = rt_tasks,
param = { [cpu.shares]=3048, [?cpu.rt_runtime_us] = 949500 },
check = function(proc)
local rv = proc.received_rt or check_label({sched.rt}, proc) or
proc.vm_size == 0
return rv
end,
},
{
name = system_essential,
cgroups_name = sys_essential,
param = { [cpu.shares]=3048 },
label = { system.essential }
},
{
name = user,
cgroups_name = usr_${euid},
check = function(proc)
return ( proc.euid 999 )
end,
param = { [cpu.shares]=3048, [?cpu.rt_runtime_us] = 100 },
children = {
{
name = poison,
param = { [cpu.shares]=10 },
label = { user.poison },
cgroups_name = psn_${pid},
children = {
},
{
name = poison_group,
param = { [cpu.shares]=300 },
cgroups_name = pgr_${pgrp},
check = function(proc)
local rv = ulatency.find_flag(ulatency.list_flags(), {name =
user.poison.group,
value =
proc.pgrp})
return rv ~= nil
end,
},
{
name = media,
param = { [cpu.shares]=3000, [?cpu.rt_runtime_us] = 1},
label = { user.media },
},
{
name = bg_high,
param = { [cpu.shares]=500, [?cpu.rt_runtime_us] = 1},
label = { user.bg_high },
},
{
name = ui,
param = { [cpu.shares]=1000, [?cpu.rt_runtime_us] = 1},
label = { user.ui }
},
{
name = idle,
param = { [cpu.shares]=1},
label = { user.idle },
},
{
name = group,
param = { [cpu.shares]=50, [?cpu.rt_runtime_us] = 1},
cgroups_name = grp_${pgrp},
check = function(proc)
return true
end,
},
},
},
{
name = system,
cgroups_name = sys_idle,
label = { daemon.idle },
param = { [cpu.shares]=1},
},
{
name = system,
cgroups_name = sys_bg,
label = { daemon.bg },
param = { [cpu.shares]=600},
},
{
name = system,
cgroups_name = sys_daemon,
check = function(proc)
-- don't put kernel threads into a cgroup
return (proc.ppid ~= 0 or proc.pid == 1)
end,
param = { [cpu.shares]=800,
[?cpu.rt_runtime_us] = 1},
}
}
if ulatency.smp_num_cpus 1 then
local all_cpus = 0-..tostring((ulatency.smp_num_cpus-1 or 0))
local rest_cpu = 0
local media_label = { user.media }
-- use special cases for low number of processors
if ulatency.smp_num_cpus == 2 then
essential_cpu = 0
other_cpu = 0
media_cpu = 1
media_exc = 1
else
other_cpu = 0
media_label = { user.media, system.essential}
media_cpu = 1-..tostring((ulatency.smp_num_cpus-1))
media_exc = 1
end
SCHEDULER_MAPPING_VIDEO_PLAYBACK[cpuset] =
{
{
name = media,
param = { [?cpuset.mems] = 0,
[?cpuset.cpus] = media_cpu,
[?cpuset.cpu_exclusive] = media_exc,},
label = media_label,
},
{
name = essential,
param = { [?cpuset.mems] = 0,
[?cpuset.cpus] = essential_cpu,
Bug#740828: evolution package versions
Just to confirm the client system is running wheezy, evolution packages are all v3.4.4-3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740296: SimpleITK
Hi Gert, Thank you for your efforts! I am passing along the versioning requests to the SimpleITK release manager, Bradley Lowekamp. Thanks, Matt On Wed, Mar 5, 2014 at 7:44 AM, Gert Wollny gw.foss...@gmail.com wrote: Hi, I would look into packaging the software and ask on debian-med for sponsoring, but only after Easter - in case someone else has time and wants to step forward with the packaging. I've seen that the latest versions are 0.7.1.post1 and 0.8rc1. I would ask you to stick to a version numbering that makes it easier to write a regexp for the watch file, i.e. 0.8rc1 should probably be 0.8.0-rc1 (cf [1]). many thanks, Gert [1] http://semver.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738588: closed by Jeremy Lainé jeremy.la...@m4x.org (Bug#738588: fixed in asterisk 1:11.8.0~dfsg-1)
Source: asterisk Source-Version: 1:11.8.0~dfsg-1 We believe that the bug you reported is fixed in the latest version of asterisk, which is due to be installed in the Debian FTP archive. ...some hope that this fix will backported to wheezy, eg on some next point release? Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740833: get-orig-source fails for non hg snapshot versions
Source: xnbd
Version: 0.3.0
Severity: normal
Dear Arno,
xnbd's get-orig-source assumes that REPOSITORY_REV is not empty which would,
however, be the case for normal releases. This causes the hg archive run to be
erroneously called with an -r -t files.
An easy fix is to use something along the lines of:
--- snip ---
ifdef REPOSITORY_REV
HG_ARCHIVE_OPT := -g $(REPOSITORY_REV)
endif
get-orig-source:
# Version generated by: hg log -r . --template
'{latesttag}-hg{latesttagdistance}-{node|short}\n'
hg clone https://bitbucket.org/hirofuchi/xnbd xnbd-$(VERSION)-hg
cd xnbd-$(VERSION)-hg hg archive -X .hg_archival.txt -X .hgtags
$(HG_ARCHIVE_OPT) -t files ../xnbd-$(VERSION)
--- snip ---
but there are, naturally, many ways to conditionally use the -r
REPOSITORY_REV if one is indeed trying to get hold of that version. It might
also be argued that one could simply export HEAD, but the aforementioned code
works for both hg snapshots and normal releases.
Merci
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf-8, LC_CTYPE=en_GB.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740554: mangles classpath in upstream manifest
Le 04/03/2014 07:48, Daniel Pocock a écrit : When I search for Debian Java mvn packaging, Google had referred me to this wiki: https://wiki.debian.org/Java/MavenRepoHelper which suggested using libplexus-io-java as an example. That is using maven-ant-helper Good point, the wiki is confusing. libplexus-io-java is an example showing how to use maven-repo-helper, but it shouldn't lead to use maven-ant-helper. jsch is a better example for projects without a Maven build. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740815: zabbix-server-mysql: snmp monitoring not works if snmp MIBs are missing
On Wed, 5 Mar 2014 23:58:20 Alex 'AdUser' Z wrote: Another possible way - make a note in README.Debian. Makes sense, perhaps we can do both -- suggest and add a note to README.Debian. Thank you. -- Regards, Dmitry Smirnov. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740815: zabbix-server-mysql: snmp monitoring not works if snmp MIBs are missing
I think this data has no alternative free sources. I've found some packages, suggest on that package: - [alex@caspar ~]$ apt-cache rdepends snmp-mibs-downloader snmp-mibs-downloader Reverse Depends: libwireshark-data libsnmp-base libsmi2ldbl libsmi2-common cacti-spine - First two - from 'main' section. Another possible way - make a note in README.Debian. WBR, Alex On Wed, Mar 05, 2014 at 11:34:54PM +1100, Dmitry Smirnov wrote: On Wed, 5 Mar 2014 20:48:38 Alex 'AdUser' Z wrote: Please add 'snmp-mibs-downloader' as soft dependency. We can't Depend or Recommend non-free package although I think it is possible to Suggest it. Frankly I'm reluctant even to suggest it... Is there are any alternatives from main? -- Regards, Dmitry Smirnov GPG key : 4096R/53968D1B --- All that is necessary for the triumph of evil is that good men do nothing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/debian-bugs-dist
Bug#740824: Additional rules to match body and urgency
Package: dunst
Version: 1.0.0-2
Followup-For: Bug #740824
With the attached patch I provide a way to match on message urgency using
'msg_urgency' as a new filter.
I didn't notice that 'body' could already be used, sorry.
diff -rud dunst-1.0.0.Orig/dunstrc dunst-1.0.0/dunstrc
--- dunst-1.0.0.Orig/dunstrc 2014-03-05 12:41:03.274349758 +0100
+++ dunst-1.0.0/dunstrc 2014-03-05 14:18:34.002606394 +0100
@@ -166,7 +166,7 @@
# Every section that isn't one of the above is interpreted as a rules
# to override settings for certain messages.
-# Messages can be matched by 'appname', 'summary', 'body' or 'icon'
+# Messages can be matched by 'appname', 'summary', 'body', 'icon' or 'msg_urgency'.
# and you can override the 'timeout', 'urgency', 'foreground', 'background'
# and 'format'.
# Shell-like globbing will get expanded.
diff -rud dunst-1.0.0.Orig/rules.c dunst-1.0.0/rules.c
--- dunst-1.0.0.Orig/rules.c 2014-03-05 12:41:03.274349758 +0100
+++ dunst-1.0.0/rules.c 2014-03-05 14:20:56.246612633 +0100
@@ -49,6 +49,7 @@
r-body = NULL;
r-icon = NULL;
r-timeout = -1;
+r-msg_urgency = -1;
r-urgency = -1;
r-fg = NULL;
r-bg = NULL;
@@ -64,6 +65,7 @@
return ((!r-appname || !fnmatch(r-appname, n-appname, 0))
(!r-summary || !fnmatch(r-summary, n-summary, 0))
(!r-body || !fnmatch(r-body, n-body, 0))
- (!r-icon || !fnmatch(r-icon, n-icon, 0)));
+ (!r-icon || !fnmatch(r-icon, n-icon, 0))
+ (r-msg_urgency == -1 || r-msg_urgency == n-urgency));
}
/* vim: set ts=8 sw=8 tw=0: */
diff -rud dunst-1.0.0.Orig/rules.h dunst-1.0.0/rules.h
--- dunst-1.0.0.Orig/rules.h 2014-03-05 12:41:03.274349758 +0100
+++ dunst-1.0.0/rules.h 2014-03-05 14:21:44.014614729 +0100
@@ -13,6 +13,7 @@
char *summary;
char *body;
char *icon;
+int msg_urgency;
/* actions */
int timeout;
diff -rud dunst-1.0.0.Orig/settings.c dunst-1.0.0/settings.c
--- dunst-1.0.0.Orig/settings.c 2014-03-05 12:41:03.274349758 +0100
+++ dunst-1.0.0/settings.c 2014-03-05 14:21:23.242613817 +0100
@@ -31,6 +31,27 @@
}
+static int ini_get_urgency(char *section, char *key, int def)
+{
+int ret = def;
+char *urg = ini_get_string(section, key, );
+
+if (strlen(urg) 0) {
+if (strcmp(urg, low) == 0)
+ret = LOW;
+else if (strcmp(urg, normal) == 0)
+ret = NORM;
+else if (strcmp(urg, critical) == 0)
+ret = CRIT;
+else
+fprintf(stderr,
+unknown urgency: %s, ignoring\n,
+urg);
+free(urg);
+}
+return ret;
+}
+
void load_settings(char *cmdline_config_path)
{
@@ -280,22 +301,8 @@
r-body = ini_get_string(cur_section, body, r-body);
r-icon = ini_get_string(cur_section, icon, r-icon);
r-timeout = ini_get_int(cur_section, timeout, r-timeout);
-{
-char *urg = ini_get_string(cur_section, urgency, );
-if (strlen(urg) 0) {
-if (strcmp(urg, low) == 0)
-r-urgency = LOW;
-else if (strcmp(urg, normal) == 0)
-r-urgency = NORM;
-else if (strcmp(urg, critical) == 0)
-r-urgency = CRIT;
-else
-fprintf(stderr,
-unknown urgency: %s, ignoring\n,
-urg);
-free(urg);
-}
-}
+r-urgency = ini_get_urgency(cur_section, urgency, r-urgency);
+r-msg_urgency = ini_get_urgency(cur_section, msg_urgency, r-msg_urgency);
r-fg = ini_get_string(cur_section, foreground, r-fg);
r-bg = ini_get_string(cur_section, background, r-bg);
r-format = ini_get_string(cur_section, format, r-format);
Bug#715179: spice-client: Please install an alternative for /usr/bin/spice-xpi-client
On Wed, Mar 5, 2014 at 7:09 PM, Petter Reinholdtsen p...@hungry.com wrote: Since today the spice-xpi package in unstable will run /usr/bin/spice-xpi-client when asked to show a SPICE console (See bug #739408). Perhaps time to review this bug report? I'll install spice-xpi-client on the next upload. Thanks, -- Liang Guo http://guoliang.me/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740826: libjgrapht0.8-java: packaging should be jar not pom
On 05/03/14 12:43, Emmanuel Bourg wrote: org.jgrapht:jgrapht is of type pom in Maven central, so we are consistent with the upstream artifact: http://search.maven.org/#search|ga|1|g%3A%22org.jgrapht%22 But the type of the artifact org.jgrapht:jgrapht-core is jar. libjgrapht0.8-java is definitely a package of jgrapht not jgrapht-core. Looking at upstream, I think the split came with version 0.9? I think perhaps libjgrapht0.8-java should actually contain the net.sf.jgrapht.jgrapht pom file? http://search.maven.org/remotecontent?filepath=net/sf/jgrapht/jgrapht/0.8.3/jgrapht-0.8.3.pom Regards, Matthew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740829:
Here is modified content of 20-desktop.lua which correct this issue but
still need to work.
--[[
Copyright 2010,2011 ulatencyd developers
This file is part of ulatencyd.
License: GNU General Public License 3 or later
]]--
SCHEDULER_MAPPING_DESKTOP = {
info = {
description = a good default desktop configuration
}
}
-- cpu memory configuration
SCHEDULER_MAPPING_DESKTOP[cpu] =
{
{
name = rt_tasks,
cgroups_name = rt_tasks,
param = { [cpu.shares]=3048, [?cpu.rt_runtime_us] = 949500 },
check = function(proc)
local rv = proc.received_rt or check_label({sched.rt}, proc) or proc.vm_size == 0
return rv
end,
},
{
name = system_essential,
cgroups_name = sys_essential,
param = { [cpu.shares]=3048 },
label = { system.essential }
},
{
name = user,
cgroups_name = usr_${euid},
check = function(proc)
return ( proc.euid 999 )
end,
param = { [cpu.shares]=3048, [?cpu.rt_runtime_us] = 100 },
children = {
{
name = poison,
param = { [cpu.shares]=10 },
label = { user.poison },
cgroups_name = psn_${pid},
},
{
name = poison_group,
param = { [cpu.shares]=300 },
cgroups_name = pgr_${pgrp},
check = function(proc)
local rv = ulatency.find_flag(ulatency.list_flags(), {name = user.poison.group,
value = proc.pgrp})
return rv ~= nil
end,
},
{
name = bg_high,
param = { [cpu.shares]=1000, [?cpu.rt_runtime_us] = 1},
label = { user.bg_high },
},
{
name = media,
param = { [cpu.shares]=2600, [?cpu.rt_runtime_us] = 1},
label = { user.media },
},
{
name = ui,
param = { [cpu.shares]=2000, [?cpu.rt_runtime_us] = 1},
label = { user.ui }
},
{
name = active,
param = { [cpu.shares]=1500, [?cpu.rt_runtime_us] = 1},
check = function(proc)
return proc.is_active
end
},
{
name = idle,
param = { [cpu.shares]=200},
label = { user.idle },
},
{
name = group,
param = { [cpu.shares]=600, [?cpu.rt_runtime_us] = 1},
cgroups_name = grp_${pgrp},
check = function(proc)
return true
end,
},
},
},
{
name = system,
cgroups_name = sys_idle,
label = { daemon.idle },
param = { [cpu.shares]=1},
},
{
name = system,
cgroups_name = sys_bg,
label = { daemon.bg },
param = { [cpu.shares]=600},
},
{
name = system,
cgroups_name = sys_daemon,
check = function(proc)
-- don't put kernel threads into a cgroup
return (proc.ppid ~= 0 or proc.pid == 1)
end,
param = { [cpu.shares]=800,
[?cpu.rt_runtime_us] = 1},
}
}
SCHEDULER_MAPPING_DESKTOP[memory] =
{
{
name = system_essential,
cgroups_name = sys_essential,
param = { [?memory.swappiness] = 0 },
label = { system.essential }
},
{
name = user,
cgroups_name = usr_${euid},
check = function(proc)
return ( proc.euid 999 )
end,
children = {
{
name = poison,
label = { user.poison },
cgroups_name = psn_${pid},
adjust_new = function(cgroup, proc)
cgroup:add_task(proc.pid)
cgroup:commit()
bytes = cgroup:get_value(memory.usage_in_bytes)
if not bytes then
ulatency.log_warning(can't access memory subsystem)
return
end
bytes = math.floor(bytes*(tonumber(ulatency.get_config(memory, process_downsize)) or 0.95))
cgroup:set_value(memory.soft_limit_in_bytes, bytes)
-- we use soft limit, but without limit we can't set the memsw limit
local max_rss = math.floor(num_or_percent(ulatency.get_config(memory, max_rss),
Scheduler.meminfo.kb_main_total,
false) * 1024)
local total_limit = math.max(math.floor(num_or_percent(ulatency.get_config(memory, total_limit),
Scheduler.meminfo.kb_main_total + Scheduler.meminfo.kb_swap_total) * 1024),
max_rss)
ulatency.log_info(memory container created: .. cgroup.name .. max_rss: .. tostring(max_rss) .. max_total: .. tostring(total_limit) .. soft_limit:.. tostring(bytes))
cgroup:set_value(memory.limit_in_bytes, max_rss)
cgroup:set_value(?memory.memsw.limit_in_bytes, total_limit, max_rss)
cgroup:commit()
Bug#740801: zathura: Ligatures, like fi, are not rendered.
I just verified that it does happen with evince (from package evince-gtk 3.10.0-2), which claims to be using poppler/cairo (0.22.5), and with epdfview 0.1.8-3. On Wed, Mar 5, 2014 at 2:54 AM, Sebastian Ramacher sramac...@debian.orgwrote: Control: tags -1 + moreinfo Hi On 2014-03-05 00:14:44, Alex Rozenshteyn wrote: I tried to view a document in Zathura, and I noticed something weird about the text. Namely, the bigram fi was conspicuously absent. Attached is a screenshot of a section of the document ( http://arxiv.org/abs/1403.0749v1). Missing ligatures can be spotted in the following locations: * 3rd line, right of the middle: computation is [fi]xed a priori * 4th line, below priori: we de[fi]ne a notion * 5th line, beginning: prove that it satis[fi]es I suppose that also happens in any other poppler based PDF viewer (evince, okular, …)? Regards -- Sebastian Ramacher -- Alex R
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
Hello all, On Wed, Mar 05, 2014 at 11:26:23AM +0100, Michael Biebl wrote: [...] If the README.Debian (which was based on [1]) is no longer correct, please let me know. Hmm, I thought I did exactly that: reporting a bug against rsyslog-mongodb, stating that the instruction [sic] from README.Debian don't seem to work at all. Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721277#5 Cheers, Flo signature.asc Description: Digital signature
Bug#721277: Adiscon LogAnalyzer? rsyslog + mongodb?
On Wed, Mar 05, 2014 at 12:13:23PM +0100, Michael Biebl wrote: Am 05.03.2014 11:26, schrieb Michael Biebl: Am 05.03.2014 11:07, schrieb Daniel Pocock: On 05/03/14 09:09, Florian Ernst wrote: On Tue, Mar 04, 2014 at 03:49:25PM +0100, Daniel Pocock wrote: The rsyslog mongodb output module and the PHP mongodb modules are now in wheezy-backports. This would appear to be sufficient to do something like: rsyslog = mongodb = loganalyzer Has anybody else tried that or does anybody have any comments on it (or recommended alternatives)? That actually did work for a time, but something broke starting with rsyslog 7.4.0-1. Since then the format of the data dumped into mongodb doesn't match what tools like loganalyzer expect, cf. #721277 / #728827. As I was merely experimenting with it I didn't follow up any further. Some of this looks like documentation bugs and/or problems with the default config rather than mongodb integration itself Florian, have you followed the steps outlined in http://www.rsyslog.com/tag/ommongodb/ ? ITIYM http://www.rsyslog.com/using-mongodb-with-rsyslog-and-loganalyzer/ in particular? Not until now. Previously I followed http://www.rsyslog.com/doc/rsyslog_conf_modules.html/ommongodb.html (which now redirects to http://www.rsyslog.com/doc/ommongodb.html). I have now tried to implement the configuration mentioned there verbatim. This led to remote logs simply disappearing, i.e. not being logged on my syslog host. Thus I have reverted the change, for my current mongodb rsyslog configuration please see the other mail to Daniel. Cheers, Flo signature.asc Description: Digital signature
Bug#493784: libgc: please provide a build with --enable-large-config
This issue still afects inkscape on Debian wheezy. Would you mind to have a look when you have time, please? Thanks, Oriol -- Oriol Mula Valls Institut Català de Ciències del Clima (IC3) Doctor Trueta 203 - 08005 Barcelona Tel:+34 93 567 99 77 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740350: Acknowledgement (Bogus dependencies in installed POM file)
Hi, There's also an error in debian/ant-contrib.poms - the --has-package-version is incorrect and should be removed, otherwise if you build using maven, then mh_resolve_dependencies puts a versioned dependency on 1.0b5-SNAPSHOT into the package you're building, which isn't satisfiable. Regards, Matthew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709558: Bug#720655: file: stage build support
Daniel Schepler wrote... Here's an updated version of my patch, with some of Eleanor's patch merged in. Thanks, looks good. (I don't know why Eleanor's patch drops --fail-missing on bootstrap builds; I didn't have any issues on my test when I left it in.) Eleanor, I plan to upload this in one or two days. If you wish to comment, please do so soon. Christoph signature.asc Description: Digital signature
Bug#694351: lsof: Please downgrade the dependency on perl to Recommends
Package: lsof Version: 4.86+dfsg-1 Followup-For: Bug #694351 As far as I can tell, the lsof executable is perfectly usable, and very useful, without perl installed; and perl is only needed to run example scripts. Since - this bug has been open since 2012; - contrary to widespread belief, perl is not universally installed (e.g. name servers, ntp servers); - the dependence on perl bumps the disk requirements from 500 kB to ~27MB, which is plain unacceptable on tight systems; I propose to expedite its closing via a downgrade of the dependency from Depends: to Recommends:. Best regards, g1 -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages lsof depends on: ii libc6 2.13-38+deb7u1 ii perl 5.14.2-21+deb7u1 ii perl-modules [libperl4-corelibs-perl] 5.14.2-21+deb7u1 lsof recommends no packages. lsof suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705607: 1.0 breaks alignment != left
Package: dunst
Version: 1.0.0-2
Followup-For: Bug #705607
The problem is caused by pango not knowing the final layout width when
rendering.
The attached patch fixes the problem.
--- dunst-1.0.0.Orig/x.c 2014-03-05 12:41:03.274349758 +0100
+++ dunst-1.0.0/x.c 2014-03-05 14:46:01.670678667 +0100
@@ -160,6 +160,17 @@
}
+static void r_update_layouts_width(GSList *layouts, int width)
+{
+width -= 2 * settings.h_padding;
+width -= 2 * settings.frame_width;
+
+for (GSList *iter = layouts; iter; iter = iter-next) {
+colored_layout *cl = iter-data;
+pango_layout_set_width(cl-l, width * PANGO_SCALE);
+}
+}
+
static void free_colored_layout(void *data)
{
colored_layout *cl = data;
@@ -379,6 +390,10 @@
int width = dim.w;
int height = dim.h;
+ if (have_dynamic_width() settings.align != left) {
+r_update_layouts_width(layouts, width);
+}
+
cairo_t *c;
cairo_surface_t *image_surface = cairo_image_surface_create(CAIRO_FORMAT_ARGB32, width, height);
c = cairo_create(image_surface);
Bug#709269: file: Overbroad python related build-depends
Scott Kitterman wrote...
File currently build-deps on python-all-dev and python3-all-dev, but
doesn't having any compiled code related to python.
Thanks, will include this in the next upload which should happen
before the weekend.
Additionally, python-magic is an arch any package, even though it
doesn't have any architecture dependent content.
Yes, just some nitpicking: lintian doesn't like simple versioned
dependencies arch: all - arch: any. A workaround is available,
though:
Package: python-magic
Section: python
Priority: optional
-Architecture: any
+Architecture: all
Depends:
${misc:Depends}, ${shlibs:Depends}, ${python:Depends},
libmagic1 (= ${binary:Version})
-libmagic1 (= ${binary:Version}),
+libmagic1 (= ${binary:Version}),
+libmagic1 ( ${binary:Version}.1~),
Christoph
signature.asc
Description: Digital signature
Bug#740803: [monit] sysvinit should move from recommends to suggests
On 05 Mar 2014, at 12:46, Sergey B Kirpichev skirpic...@gmail.com wrote: On Wed, Mar 05, 2014 at 11:35:49AM +0100, Martin Pala wrote: Monit can work in systemd environment fine, you just need to use systemd's start/stop methods as Monit's start/stop program. Yes, it can, if you are sure that your systemd's configuration doesn't use any dangerous features of this bloatware. An example was provided above (Restart option). If you find some features dangerous, please explain which and why? The restart of process via Monit (both old and new way) is exactly the same risk as restarting it via systemd. Monit makes sure that the process stops during the restart before starting it again. The fact that systemd starts the process instead of old init scripts doesn't matter - the way the process existence is checked prevents any problems. I'm not sure what you mean by bloatware ... Monit always was and will be opensource GPL application, there are years of hard work behind it. If you don't like it, don't use it, but please stop abusing for no reason. I appreciate your work as a package maintainer a lot, but if you feel that you don't want to maintain the package anymore, i can take the responsibility over. Regards, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740834: Move to udisks2, udisks 1 is deprecated
Package: guymager Version: 0.7.3-2 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. guymager also still carries code for devicekit-disks (which hasn't existed for years) and hal (which has been dead for even longer), this can certainly be removed. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#740835: docker.io: Move source package related docs to README.source instead of README.Debian
Package: docker.io Version: 0.8.0+dfsg1-2 Severity: minor Dear Maintainer, IMHO, details about how to retrieve and rebuild the package aren't meant for README.Debian, and ought to be in debian/README.source instead. Not a big deal anyway. Thanks for packaging docker. Best regards, -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-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 docker.io depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.14 ii iptables 1.4.21-1 ii libc62.17-97 ii libdevmapper1.02.1 2:1.02.83-2 ii libsqlite3-0 3.8.3.1-1 ii lxc 0.9.0~alpha3-2+deb8u1 ii perl 5.18.2-2+b1 Versions of packages docker.io recommends: ii aufs-tools 1:3.2+20130722-1.1 ii ca-certificates 20130906 ii xz-utils 5.1.1alpha+20120614-2 docker.io suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740837: Move to udisks2, udisks 1 is deprecated
Package: mic2 Version: 0.24.12-1 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. The API is documented at http://udisks.freedesktop.org/docs/latest/ . Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#535427: Broken podcast feed causes episode to reappear
Hey Matt, Could you please still reproduce this issue with newer rhythmbox version like 2.97-2.1 or 3.0.1-1+b2 ? thanks regards althaser
Bug#740836: Move to udisks2, udisks 1 is deprecated
Package: linaro-image-tools Version: 2013.09-2 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. The API is documented at http://udisks.freedesktop.org/docs/latest/ . Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#740838: Move to udisks2, udisks 1 is deprecated
Package: quodlibet Version: 3.0.2-3 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. The API is documented at http://udisks.freedesktop.org/docs/latest/ . Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#740839: Move to udisks2, udisks 1 is deprecated
Package: dell-recovery Version: 1.30.1 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. The API is documented at http://udisks.freedesktop.org/docs/latest/ . Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#740840: Pausing dunst with visible notifications results in endless loop
Package: dunst
Version: 1.0.0-2
Severity: important
Tags: patch
Doing the following:
$ notify-send 'test'; notify-send DUNST_COMMAND_PAUSE
will cause dunst to enter an infinite loop.
Possibly related to bug #729690.
In the attached patch, we see how it's obvious that we keep popping from the
wrong queue.
Also in the patch, a double call to run(NULL) can be avoided while processing a
new notification (which I discovered while tracking down this bug).
Thanks.
diff -rud dunst-1.0.0.Orig/dbus.c dunst-1.0.0/dbus.c
--- dunst-1.0.0.Orig/dbus.c 2014-03-05 12:41:03.274349758 +0100
+++ dunst-1.0.0/dbus.c 2014-03-05 15:12:11.750747537 +0100
@@ -278,13 +278,11 @@
n-color_strings[ColBG] = bgcolor;
int id = notification_init(n, replaces_id);
-wake_up();
-
GVariant *reply = g_variant_new((u), id);
g_dbus_method_invocation_return_value(invocation, reply);
g_dbus_connection_flush(connection, NULL, NULL, NULL);
-run(NULL);
+wake_up();
}
static void onCloseNotification(GDBusConnection * connection,
diff -rud dunst-1.0.0.Orig/dunst.c dunst-1.0.0/dunst.c
--- dunst-1.0.0.Orig/dunst.c 2014-03-05 12:41:03.274349758 +0100
+++ dunst-1.0.0/dunst.c 2014-03-05 15:12:00.806747057 +0100
@@ -105,7 +105,7 @@
if (pause_display) {
while (displayed-length 0) {
-g_queue_insert_sorted(queue, g_queue_pop_head(queue),
+g_queue_insert_sorted(queue, g_queue_pop_head(displayed),
notification_cmp_data, NULL);
}
return;
Bug#740823: alignment=center|right doesn't work with width=0
Package: dunst
Version: 1.0.0-2
Followup-For: Bug #740823
I wrongly filed this fix under the wrong bug report before, sorry for the noise.
The problem is caused by pango not knowing the final layout width when
rendering.
The attached patch fixes the problem.
--- dunst-1.0.0.Orig/x.c 2014-03-05 12:41:03.274349758 +0100
+++ dunst-1.0.0/x.c 2014-03-05 14:46:01.670678667 +0100
@@ -160,6 +160,17 @@
}
+static void r_update_layouts_width(GSList *layouts, int width)
+{
+width -= 2 * settings.h_padding;
+width -= 2 * settings.frame_width;
+
+for (GSList *iter = layouts; iter; iter = iter-next) {
+colored_layout *cl = iter-data;
+pango_layout_set_width(cl-l, width * PANGO_SCALE);
+}
+}
+
static void free_colored_layout(void *data)
{
colored_layout *cl = data;
@@ -379,6 +390,10 @@
int width = dim.w;
int height = dim.h;
+ if (have_dynamic_width() settings.align != left) {
+r_update_layouts_width(layouts, width);
+}
+
cairo_t *c;
cairo_surface_t *image_surface = cairo_image_surface_create(CAIRO_FORMAT_ARGB32, width, height);
c = cairo_create(image_surface);
Bug#740841: Move to udisks2, udisks 1 is deprecated
Package: scolasync Version: 4.1-2 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. The API is documented at http://udisks.freedesktop.org/docs/latest/ . Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#740842: Move to udisks2, udisks 1 is deprecated
Package: libpam-usb Version: 0.5.0-4 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. The API is documented at http://udisks.freedesktop.org/docs/latest/ . Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#740843: apt: fails to upgrade the fglrx family of packages with multiarch
Package: apt Version: 0.9.7.9+deb7u1 Severity: normal unattended-upgrades was unable to upgrade the fglrx family of packages from one version to the next on SteamOS, and I've been able to reproduce a simpler form of the same situation with both apt-get and unattended-upgrades, in a Debian stable or testing chroot. == preconditions == The test set of packages are created by the attached files (put them all in the same directory and run make), and are a simplified version of the original situation involving fglrx: foo-driver amd64 installed Depends: libfoo (= VERSION) Recommends: libgl1-foo-glx (= VERSION) Breaks: libgl1-foo-glx ( VERSION) Breaks: libgl1-foo-glx ( VERSION) libgl1-foo-glx both amd64 and i386 installed Depends: libfoo (= VERSION) libfoo both amd64 and i386 installed The only configured apt repository at the time of the upgrade contains packages of the same names, with the same relationships, but a higher version. The Makefile rules for test_apt_in_chroot and test_uu_in_chroot indicate the specifics of how I tested this, in a small chroot environment (build-essential + aptitude + sudo + vim). == expected result == I would expect the problem resolution to involve temporarily deconfiguring foo-driver and libgl1-foo-glx, upgrading both flavours of libfoo, configuring libgl1-foo-glx, and finally configuring foo-driver. == actual result == However, what actually happens is that apt gets part-way through the upgrade, but does not deconfigure foo-driver in favour of the new libgl1-foo-glx: The following packages will be upgraded: foo-driver libfoo libfoo:i386 libgl1-foo-glx libgl1-foo-glx:i386 5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/3538 B of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] [...] (Reading database ... 16779 files and directories currently installed.) Preparing to unpack .../foo/libgl1-foo-glx_2_amd64.deb ... De-configuring libgl1-foo-glx:i386 (1) ... Unpacking libgl1-foo-glx:amd64 (2) over (1) ... Preparing to unpack .../foo/libgl1-foo-glx_2_i386.deb ... Unpacking libgl1-foo-glx:i386 (2) over (1) ... Preparing to unpack .../main/f/foo/libfoo_2_i386.deb ... De-configuring libfoo:amd64 (1) ... Unpacking libfoo:i386 (2) over (1) ... Preparing to unpack .../main/f/foo/libfoo_2_amd64.deb ... Unpacking libfoo:amd64 (2) over (1) ... Setting up libfoo:amd64 (2) ... Setting up libfoo:i386 (2) ... dpkg: dependency problems prevent configuration of libgl1-foo-glx:amd64: foo-driver (1) breaks libgl1-foo-glx ( 1) and is installed. Version of libgl1-foo-glx:amd64 to be configured is 2. dpkg: error processing package libgl1-foo-glx:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libgl1-foo-glx:i386: foo-driver (1) breaks libgl1-foo-glx ( 1) and is installed. Version of libgl1-foo-glx:i386 to be configured is 2. dpkg: error processing package libgl1-foo-glx:i386 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libgl1-foo-glx:amd64 libgl1-foo-glx:i386 This seems to be multiarch-related: not installing the i386 packages leads to the upgrade working fine. == applicability to real life == In the real situation on SteamOS, foo is replaced with fglrx throughout, the packages contain files, and there are additional dependencies on packages that are not involved in the problematic transaction. The failure mode appears to be the same. Package versions etc. below are from a wheezy/amd64 chroot that can reproduce the bug. S -- Package-specific info: -- apt-config dump -- APT ; APT::Architecture amd64; APT::Build-Essential ; APT::Build-Essential:: build-essential; APT::Install-Recommends 1; APT::Install-Suggests 0; APT::NeverAutoRemove ; APT::NeverAutoRemove:: ^firmware-linux.*; APT::NeverAutoRemove:: ^linux-firmware$; APT::NeverAutoRemove:: ^linux-image.*; APT::NeverAutoRemove:: ^kfreebsd-image.*; APT::NeverAutoRemove:: ^linux-restricted-modules.*; APT::NeverAutoRemove:: ^linux-ubuntu-modules-.*; APT::NeverAutoRemove:: ^gnumach$; APT::NeverAutoRemove:: ^gnumach-image.*; APT::Never-MarkAuto-Sections ; APT::Never-MarkAuto-Sections:: metapackages; APT::Never-MarkAuto-Sections:: restricted/metapackages; APT::Never-MarkAuto-Sections:: universe/metapackages; APT::Never-MarkAuto-Sections:: multiverse/metapackages; APT::Never-MarkAuto-Sections:: oldlibs; APT::Never-MarkAuto-Sections:: restricted/oldlibs; APT::Never-MarkAuto-Sections:: universe/oldlibs; APT::Never-MarkAuto-Sections:: multiverse/oldlibs; APT::Architectures ; APT::Architectures:: amd64; APT::Architectures:: i386; APT::Compressor ; APT::Compressor::. ; APT::Compressor::.::Name .; APT::Compressor::.::Extension ; APT::Compressor::.::Binary ; APT::Compressor::.::Cost 1; APT::Compressor::gzip ; APT::Compressor::gzip::Name
Bug#740844: Move to udisks2, udisks 1 is deprecated
Package: daisy-player Version: 8.5.1-1 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. The API is documented at http://udisks.freedesktop.org/docs/latest/ . daisy-player only calls the udisks command line program a few times, that should be easy to port to the corresponding udisksctl commands. However, note that most desktop environments mount hotpluggable storage automatically, so this shouldn't even be needed in most cases? Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#740826: libjgrapht0.8-java: packaging should be jar not pom
Le 05/03/2014 14:05, Matthew Vernon a écrit : I think perhaps libjgrapht0.8-java should actually contain the net.sf.jgrapht.jgrapht pom file? Yes, it looks like the right pom for this version. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740846: percona-toolkit: CVE-2014-2029
Package: percona-toolkit Severity: grave Tags: security Justification: user security hole This was assigned CVE-2014-2029: http://seclists.org/oss-sec/2014/q1/377 We should disable it in the Debian package. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740845: Move to udisks2, udisks 1 is deprecated
Package: basenji Version: 1.0.1-3 User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: udisks1-deprecation Hello, this package currently depends on/recommends udisks 1. That has been deprecated for a while now, in favor of udisks 2. Please port the package to udisks 2 and drop code that uses the old hal/devicekit-disks/udisks 1 bits. Please note that udisks2 also has a library interface (libudisks2-0) which is easier to use than raw D-BUS calls. It is also introspectable (gir1.2-udisks-2.0) so you can use it from languages like Python. However, for this C# case it's probably better to stick with raw D-BUS calls as AFAIK there is no current/maintained gobject-introspection support for Mono. The API is documented at http://udisks.freedesktop.org/docs/latest/ . Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#740847: unattended-upgrades: Exception: mark_install() got an unexpected keyword argument 'auto_install'
Package: unattended-upgrades
Version: 0.82.2
Severity: normal
There seems to be a problem with the code you added to
unattended-upgrades 0.82.2 to fix the rewind_cache() issue I reported
recently. When I get unattended-upgrades into a tricky situation by
trying to reproduce
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740843 (see that bug
for test packages and steps to reproduce), it crashes with:
applying set {'libfoo', 'foo-driver', 'libgl1-foo-glx',
'libgl1-foo-glx:i386', 'libfoo:i386'}
matching 'a'='inadvisable' against 'Origin component:'main'
archive:'inadvisable' origin:'my archive' label:'my label' site:''
isTrusted:True'
matching 'a'='inadvisable' against 'Origin component:'main'
archive:'inadvisable' origin:'my archive' label:'my label' site:''
isTrusted:True'
matching 'a'='inadvisable' against 'Origin component:'main'
archive:'inadvisable' origin:'my archive' label:'my label' site:''
isTrusted:True'
matching 'a'='inadvisable' against 'Origin component:'main'
archive:'inadvisable' origin:'my archive' label:'my label' site:''
isTrusted:True'
matching 'a'='inadvisable' against 'Origin component:'main'
archive:'inadvisable' origin:'my archive' label:'my label' site:''
isTrusted:True'
Exception: mark_install() got an unexpected keyword argument
'auto_install'
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages unattended-upgrades depends on:
ii apt0.9.15.5+b1
ii apt-utils 0.9.15.5+b1
ii debconf [debconf-2.0] 1.5.52
ii lsb-base 4.1+Debian12
ii lsb-release4.1+Debian12
ii python33.3.4-1
ii python3-apt0.9.3.1
ii ucf3.0027+nmu1
ii xz-utils 5.1.1alpha+20120614-2
unattended-upgrades recommends no packages.
Versions of packages unattended-upgrades suggests:
pn bsd-mailx none
pn mail-transport-agent none
-- debconf information:
unattended-upgrades/enable_auto_updates: false
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
