Bug#770404: systemd: breaks lightdm, does not start anymore
Actually, I think we can settle it that way (which would help fixing fixing bug #770633: Everytime we have a service which provided an alternative, we declare an Alias=this alternative.service name. Then, we patch systemctl to update the alternative file (if it exists) on this alias name for those units having an alias. That's fixing the systemctl enable service - put in sync the alternative. Then, we patch update-alternative to look for a correspond .service name, and if any (and systemctl installed), we call systemctl enable --force service (and need to find a way to not have the circular dependency on both, like checking the alternatives file directly) That's fixing the update-alternative command - syncing on systemctl state. With this, we can even remove the tweaked postinst for the DMs as the normal alternative prompts will do the right thing. That of course wouldn't fix people changing the alternatives file by hand, but I'm unsure we can gracefully handle this. What do you think? Didier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764630: missing JNI path in jarwrapper
On Tue, Nov 25, 2014 at 12:49 AM, Emmanuel Bourg ebo...@apache.org wrote: Le 21/11/2014 17:12, Mathieu Malaterre a écrit : Maybe this is time to change the Java policy §2.4 Java libraries This means that dicomscope package would install only the `jar` file, and the x86 or x86_64 native lib (*.so) can be installed whether the user want the 32bits or the 64bits version. Comments ? The policy change is certainly a good idea, but it will not solve this specific issue. For example, let say we are on an amd64 system and we install the package libfoo-java that depends on libfoo-jni. libfoo-jni installs its .so in a multiarch path (/usr/lib/x86_64-linux-gnu). We install the 32 bits JRE from Oracle and set it as the default JRE. Then we run foo with jarwrapper. jarwrapper tries to build the library path, and seeing we are on amd64 set it to /usr/lib:/usr/lib/x86_64-linux-gnu. foo fails because we tried loading a 64 bits library from a 32 bits VM. That is the correct behavior. When I want to run an x86 executable (apps are not co-installable) but install the default amd64 (x86_64) it does not work (the amd64 is used instead). So to run an x86 you need to explicitly install libfoo-jni:i386, that is the intended behavior. Actually jarwrapper has to guess the 32/64 bits architecture of the VM and build the library path accordingly (at least for the architectures where Oracle provides a JVM, that's amd64/i386 and maybe the arm variants). So the logic would be: Are we running on amd64/i386? - Yes : Check if the VM is 32 or 64 bits (by parsing the output of java -d32 -version and java -d64 -version) - 32 bits : set the library path to /usr/lib:/usr/lib/i386-linux-gnu - 64 bits : set the library path to /usr/lib:/usr/lib/x86_64-linux-gnu - No : this is a Debian VM and the path is ok by default, do nothing Building a proper library path for an Oracle JRE is maybe outside of debian policy ? and beyond debian-java responsabilities ? Maybe what was not clear is that jexec does have the proper behavior, jarwrapper should only be used only if the first binfmts (=jexec) fails to execute. In summary: 1. Make jexec the default binfmts (before jarwrapper) 2. Update jarwrapper to use the above mentionned `java -d32|64` trick to build the library path. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767907: marked as done (too lax shlibs dependency? (newly added pcre_stack_guard needs = 1:8.35))
Your message dated Mon, 24 Nov 2014 23:49:23 + with message-id e1xt3nj-0006xx...@franck.debian.org and subject line Bug#767903: fixed in pcre3 1:8.36-1 has caused the Debian Bug report #767907, regarding too lax shlibs dependency? (newly added pcre_stack_guard needs = 1:8.35) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mariadb-server-10.0 Version: 10.0.14-2 Severity: normal Dear Maintainer, Installing mariadb-server from Jessie on Wheezy fails: /usr/sbin/mysqld: symbol lookup error: /usr/sbin/mysqld: undefined symbol: pcre_stack_guard Upgrading libpcre3 from 1:8.30-5 to 1:8.35-3.1 solves the issue. -- System Information: Debian Release: 7.7 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 3.2.33-x15 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mariadb-server-10.0 depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii libaio1 0.3.109-3 ii libc6 2.19-12 ii libdbi-perl 1.622-1+deb7u1 ii libpam0g 1.1.3-7.1 ii libstdc++64.9.1-16 ii lsb-base 4.1+Debian8+deb7u1 ii mariadb-client-10.0 10.0.14-2 ii mariadb-common10.0.14-2 ii mariadb-server-core-10.0 10.0.14-2 ii passwd1:4.1.5.1-1 ii perl 5.14.2-21+deb7u2 ii psmisc22.19-1+deb7u1 ii zlib1g1:1.2.7.dfsg-13 Versions of packages mariadb-server-10.0 recommends: ii libhtml-template-perl 2.91-1 Versions of packages mariadb-server-10.0 suggests: ii bsd-mailx [mailx] 8.1.2-0.2006cvs-1 pn mariadb-test none pn tinyca none -- debconf information: mysql-server/error_setting_password: mysql-server-10.0/nis_warning: mariadb-server-10.0/really_downgrade: false mysql-server-10.0/postrm_remove_databases: false * mariadb-server/oneway_migration: true mysql-server/password_mismatch: mysql-server/no_upgrade_when_using_ndb: ---End Message--- ---BeginMessage--- Source: pcre3 Source-Version: 1:8.36-1 We believe that the bug you reported is fixed in the latest version of pcre3, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Baker m...@mnb.org.uk (supplier of updated pcre3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 24 Nov 2014 22:41:12 + Source: pcre3 Binary: libpcre3 libpcre3-udeb libpcrecpp0 libpcre3-dev libpcre3-dbg pcregrep Architecture: source amd64 Version: 1:8.36-1 Distribution: unstable Urgency: medium Maintainer: Mark Baker m...@mnb.org.uk Changed-By: Mark Baker m...@mnb.org.uk Description: libpcre3 - Perl 5 Compatible Regular Expression Library - runtime files libpcre3-dbg - Perl 5 Compatible Regular Expression Library - debug symbols libpcre3-dev - Perl 5 Compatible Regular Expression Library - development files libpcre3-udeb - Perl 5 Compatible Regular Expression Library - runtime files (ude (udeb) libpcrecpp0 - Perl 5 Compatible Regular Expression Library - C++ runtime files pcregrep - grep utility that uses perl 5 compatible regexes. Closes: 767903 770478 Changes: pcre3 (1:8.36-1) unstable; urgency=medium . * New upstream release * Upped shlibs dependency to 8.35 (Closes: #767903) * Upstream patch for heap buffer overflow, CVE-2014-8964 (Closes: #770478) Checksums-Sha1: 91ad676818070411883ebfbd56f73a45482bcced 1262 pcre3_8.36-1.dsc 9a074e9cbf3eb9f05213fd9ca5bc188644845ccc 1533818 pcre3_8.36.orig.tar.bz2 5ad4309642f66890d11f4d0b8b7f3b6a2bbc2beb 19579 pcre3_8.36-1.debian.tar.gz c67547cdd54937ae678cda2c04a30ad3ea0a4c72 339516 libpcre3_8.36-1_amd64.deb b559c4ee082b79587fd52cee6b62725c340bb4e6 142586 libpcre3-udeb_8.36-1_amd64.udeb 385ee0ffdbd885680d1593ad3a6c7ab7f30e0ffd 144280
Bug#767903: fixed in pcre3 1:8.36-1
Control: reopen -1 Hi, On Mon, Nov 24, 2014 at 11:49:23PM +, Mark Baker wrote: To: 767903-cl...@bugs.debian.org pcre3 (1:8.36-1) unstable; urgency=medium . * New upstream release Did you read the freeze policy? This part will need to be reverted. * Upped shlibs dependency to 8.35 (Closes: #767903) This part of the issue is actually #767907, not #767903 * Upstream patch for heap buffer overflow, CVE-2014-8964 (Closes: #770478) Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767653:
Hi Tobi, * Tobias Frost t...@debian.org [2014-11-24 22:12]: Ok, pulled from the git and comparing to the version currently in Jessie: As we are in the freeze, you need to create targeted fixes for RC Bugs only.* So the doxygen one isn't. This seems to be coming from a new Doxygen version and is only needed for debclean , but I can revert it without problems. And be more detailed in freeze time: Will do. I'd write Do not ship but create at install time the files ... Is the register modules change needed for 767653? (I assume yes, but then the changelog should make that clear too) That's actually all part of one change, but ended up in two commits, so git-dch made two lines out of it. Will change the changelog. Why are you moving the util-binaries to the libary package? I would find it better to depend on the utils package instead, (especially as you should consider implement multi-arch for Jessie+1) openni-utils contains sample applications depending on libopenni0. Leaving niReg/niLicense in there would generate a circular dependency, as we need them in the libopenni0 postinst. Is there an other option? Declaring a circular dependency is not a problem here and well handled by dpkg. When postinst is called, both packages are guaranteed to be unpacked, so the library / binaries are in place at this point of time. (See Policy §7.2) Cheers Jochen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#767903: fixed in pcre3 1:8.36-1
Processing control commands:
reopen -1
Bug #767903 {Done: Mark Baker m...@mnb.org.uk} [mariadb-server-10.0]
mariadb-server-10.0: missing versioned dependency on libpcre3 =1:8.35
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pcre3/1:8.36-1.
--
767903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770908: [Aptitude-devel] Bug#770908: aptitude does not know about the new _apt user. Must use apt-get update as a workaround
Control: forcemerge -1 764506 Control: tag -1 + stretch Hi Dan, 積丹尼 Dan Jacobson wrote: Severity: grave aptitude does not know about the new _apt user in e.g., apt 1.1~exp8. Why should that be grave (in the current situation)? aptitude does not work well with apt from experimental yet, yes, see #764506 and #762846. But since it's apt from experimental, it's not release-critical for Jessie. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767653:
Hi Tobi, * Tobias Frost t...@debian.org [2014-11-24 22:12]: Ok, pulled from the git and comparing to the version currently in Jessie: As we are in the freeze, you need to create targeted fixes for RC Bugs only.* So the doxygen one isn't. This seems to be coming from a new Doxygen version and is only needed for debclean , but I can revert it without problems. And be more detailed in freeze time: Will do. I'd write Do not ship but create at install time the files ... Is the register modules change needed for 767653? (I assume yes, but then the changelog should make that clear too) That's actually all part of one change, but ended up in two commits, so git-dch made two lines out of it. Will change the changelog. Why are you moving the util-binaries to the libary package? I would find it better to depend on the utils package instead, (especially as you should consider implement multi-arch for Jessie+1) openni-utils contains sample applications depending on libopenni0. Leaving niReg/niLicense in there would generate a circular dependency, as we need them in the libopenni0 postinst. Is there an other option? Declaring a circular dependency is not a problem here and well handled by dpkg. When postinst is called, both packages are guaranteed to be unpacked, so the library / binaries are in place at this point of time. (See Policy §7.2) Cheers Jochen I wanted to point you to Policy §8.2 as well, but forgot in the rush. -- it is actually forbidden to have the binaries in the libary package. (-- some simpications applied; the Policy has details.) -- tobi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Aptitude-devel] Bug#770908: aptitude does not know about the new _apt user. Must use apt-get update as a workaround
Processing control commands: forcemerge -1 764506 Bug #770908 [aptitude] aptitude does not know about the new _apt user. Must use apt-get update as a workaround Bug #764506 [aptitude] aptitude: aptitude update no more works with apt 1.1~exp4 Severity set to 'grave' from 'normal' Severity set to 'grave' from 'normal' Bug #764601 [aptitude] Could not open file /var/lib/apt/lists/...Packages.IndexDiff - open (2: No such file or directory) Merged 764506 764601 770908 tag -1 + stretch Bug #770908 [aptitude] aptitude does not know about the new _apt user. Must use apt-get update as a workaround Bug #764506 [aptitude] aptitude: aptitude update no more works with apt 1.1~exp4 Bug #764601 [aptitude] Could not open file /var/lib/apt/lists/...Packages.IndexDiff - open (2: No such file or directory) Added tag(s) stretch. Added tag(s) stretch. Added tag(s) stretch. -- 764506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764506 764601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764601 770908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 764506 is normal
Processing commands for cont...@bugs.debian.org: severity 764506 normal Bug #764506 [aptitude] aptitude: aptitude update no more works with apt 1.1~exp4 Bug #764601 [aptitude] Could not open file /var/lib/apt/lists/...Packages.IndexDiff - open (2: No such file or directory) Bug #770908 [aptitude] aptitude does not know about the new _apt user. Must use apt-get update as a workaround Severity set to 'normal' from 'grave' Severity set to 'normal' from 'grave' Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 764506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764506 764601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764601 770908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770916: failed to find asset during precompile
package: ruby-handlebars-assets version: 0.15-2 severity: grave I think this is an upstream bug (config.root is not respected) ** Execute assets:precompile I, [2014-11-25T08:23:13.301523 #17268] INFO -- : Writing /usr/share/diaspora/public/assets/mobile-9c8138c58dc33879dd5b438b97865c58.js I, [2014-11-25T08:23:13.745973 #17268] INFO -- : Writing /usr/share/diaspora/public/assets/profile-bd746989c4a102d4699cd598683f9f58.js rake aborted! Errno::ENOENT: No such file or directory @ rb_sysopen - /usr/lib/ruby/vendor/assets/javascripts/handlebars.js (in /usr/share/diaspora/app/assets/templates/activity-streams-photo_tpl.jst.hbs) /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:35:in `read' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:35:in `read' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:35:in `source' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:27:in `apply_patches_to_source' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:31:in `context' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:10:in `precompile' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars_template.rb:76:in `compile_default' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars_template.rb:65:in `evaluate' /usr/lib/ruby/vendor_ruby/tilt/template.rb:103:in `render' /usr/lib/ruby/vendor_ruby/sprockets/context.rb:197:in `block in evaluate' /usr/lib/ruby/vendor_ruby/sprockets/context.rb:194:in `each' /usr/lib/ruby/vendor_ruby/sprockets/context.rb:194:in `evaluate' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:12:in `initialize' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:379:in `new' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:379:in `block in build_asset' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:400:in `circular_call_protection' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:378:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:94:in `block in build_asset' /usr/lib/ruby/vendor_ruby/sprockets/caching.rb:58:in `cache_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:93:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:287:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:61:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:111:in `block in resolve_dependencies' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:105:in `each' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:105:in `resolve_dependencies' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:97:in `build_required_assets' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:16:in `initialize' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:379:in `new' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:379:in `block in build_asset' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:400:in `circular_call_protection' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:378:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:94:in `block in build_asset' /usr/lib/ruby/vendor_ruby/sprockets/caching.rb:58:in `cache_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:93:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:287:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:61:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/bundled_asset.rb:16:in `initialize' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:382:in `new' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:382:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:94:in `block in build_asset' /usr/lib/ruby/vendor_ruby/sprockets/caching.rb:58:in `cache_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:93:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:287:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:61:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:211:in `block in find_asset' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:257:in `benchmark' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:210:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:119:in `block in compile' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:118:in `each' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:118:in `compile' /usr/lib/ruby/vendor_ruby/sprockets/rails/task.rb:61:in `block (3 levels) in define' /usr/lib/ruby/vendor_ruby/rake/sprocketstask.rb:146:in `with_logger' /usr/lib/ruby/vendor_ruby/sprockets/rails/task.rb:60:in `block (2 levels) in define' /usr/lib/ruby/vendor_ruby/rake/task.rb:240:in `call' /usr/lib/ruby/vendor_ruby/rake/task.rb:240:in `block in execute' /usr/lib/ruby/vendor_ruby/rake/task.rb:235:in `each' /usr/lib/ruby/vendor_ruby/rake/task.rb:235:in `execute' /usr/lib/ruby/vendor_ruby/rake/task.rb:179:in `block in invoke_with_call_chain' /usr/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize' /usr/lib/ruby/vendor_ruby/rake/task.rb:172:in `invoke_with_call_chain' /usr/lib/ruby/vendor_ruby/rake/task.rb:165:in `invoke' /usr/lib/ruby/vendor_ruby/rake/application.rb:150:in `invoke_task'
Bug#770918: Two CVEs against FLAC
Package: flac Version: 1.3.0-2+b1 Severity: serious Tags: security From: http://lists.xiph.org/pipermail/flac-dev/2014-November/005226.html Google Security Team member, Michele Spagnuolo, recently found two potential problems in the FLAC code base. They are : CVE-2014-9028 : Heap buffer write overflow CVE-2014-8962 : Heap buffer read overflow For Linux distributions, the specific fixes for these two CVEs are available from Git here: https://git.xiph.org/?p=flac.git;a=commit;h=fcf0ba06ae12ccd7c67cee3c8d948df15f946b85 https://git.xiph.org/?p=flac.git;a=commit;h=5b3033a2b355068c11fe637e14ac742d273f076e and are simple enough that they should apply cleanly to the last official release 1.3.0 and possibly even the previous one, 1.2.1. A pre-release (version 1.3.1pre1) for the next version which includes these fixes and more is available here: http://downloads.xiph.org/releases/flac/beta/ A full release (version 1.3.1) will be available in the next couple of days. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17-rc5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages flac depends on: ii libc6 2.19-13 ii libflac8 1.3.0-2+b1 flac recommends no packages. flac suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766670: RC bug in stable and oldstable for getmail4
Hi, On Sun, 23 Nov 2014, Osamu Aoki wrote: By the way, I uploaded getmail4_4.46.0-1~bpo70+1_amd64 We can consider a new upstream version for squeeze-lts and we can ask the security team's opinion for wheezy. Would you like to prepare a 4.46.0-1~deb6u1.dsc working in squeeze and submit it for review to debian-...@lists.debian.org ? It would be nice if you could test it though, because we don't have many testers before release... https://ftp-master.debian.org/new/getmail4_4.46.0-1~bpo70%2B1.html This can probably be renumbered 4.46.0-1~deb7u1.dsc and submitted to the security team ? Or does it depend on other packages from backports ? Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770913: marked as done (ruby-bootstrap-sass does not ship any assets)
Your message dated Tue, 25 Nov 2014 09:20:36 + with message-id e1xtciw-0006j5...@franck.debian.org and subject line Bug#770913: fixed in ruby-bootstrap-sass 2.3.1.0-4 has caused the Debian Bug report #770913, regarding ruby-bootstrap-sass does not ship any assets to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: ruby-bootstrap-sass version: 2.3.1.0-3 severity: grave while precompiling assets for diaspora, which uses bootstrap-sass, I found this package does not ship the assets. ** Execute assets:precompile rake aborted! Sprockets::FileNotFound: couldn't find file 'bootstrap-tooltip' steps to reproduce this error https://wiki.debian.org/Diaspora signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: ruby-bootstrap-sass Source-Version: 2.3.1.0-4 We believe that the bug you reported is fixed in the latest version of ruby-bootstrap-sass, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen prav...@debian.org (supplier of updated ruby-bootstrap-sass package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Nov 2014 13:33:31 +0530 Source: ruby-bootstrap-sass Binary: ruby-bootstrap-sass compass-bootstrap-sass-plugin Architecture: source all Version: 2.3.1.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Pirate Praveen prav...@debian.org Description: compass-bootstrap-sass-plugin - Compass plugin implementing Twitter's Bootstrap ruby-bootstrap-sass - Twitter's Bootstrap, converted to Sass Closes: 770913 Changes: ruby-bootstrap-sass (2.3.1.0-4) unstable; urgency=medium . * Ship assets (closes: #770913) Checksums-Sha1: 9cff444b3a1ff793a97d2064a6d946dc1f638687 2263 ruby-bootstrap-sass_2.3.1.0-4.dsc 34168f0d267188c49911836a179c7db896dae8c4 2632 ruby-bootstrap-sass_2.3.1.0-4.debian.tar.xz 969c76845e108ecfd6d92ea993a712255f83b8b7 72774 ruby-bootstrap-sass_2.3.1.0-4_all.deb 8a5bb80d87d968f946599604dc58810f3ca96a85 67748 compass-bootstrap-sass-plugin_2.3.1.0-4_all.deb Checksums-Sha256: be9074cce975f3fdf2278d95a0ff95a56496928de694dfd6728914b2b0cfc3b6 2263 ruby-bootstrap-sass_2.3.1.0-4.dsc 469a81a2548e28b34b8d5f35c8d70c7c2913158c187b143d68be16e8a0a8e006 2632 ruby-bootstrap-sass_2.3.1.0-4.debian.tar.xz 81c19542b0deec1c3e41383a2e078de1172924a5ab75b64eef34c2897e4c154e 72774 ruby-bootstrap-sass_2.3.1.0-4_all.deb 8a6ffc19bb710d51524df59bcec026ea6214b3812151456aa93160234777ee76 67748 compass-bootstrap-sass-plugin_2.3.1.0-4_all.deb Files: c401f8a32cc6568e622c531c85ac456a 2263 ruby optional ruby-bootstrap-sass_2.3.1.0-4.dsc 7a696c3687f7571ea3152d1a68e897a2 2632 ruby optional ruby-bootstrap-sass_2.3.1.0-4.debian.tar.xz 28b8ce97c8a6e91200d2cbcf0126210f 72774 ruby optional ruby-bootstrap-sass_2.3.1.0-4_all.deb f50047070a56336a0f9e52afc79b6906 67748 ruby optional compass-bootstrap-sass-plugin_2.3.1.0-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUdDgUAAoJEM4fnGdFEsIqyyoQAJ04R3rFeqXguUz1A2+0ARWF O9eJDCnWOj/iV0ehkK2hXilIZyJ/aKkVO0Bt8THJ2nANzaF3exSiAMQmIE8W1mqk I2J9ZpnkyTYzXTml6jBb9zx0Fhe4zHp9tPNdxeYhfObDf7GDXScVXCTaJMxRvdaC g/WJAQtPg5jb1sjO2EOTkqjgLFJLVosH3/PvJmRaKONgxfJBlWlUC05djePxJK1n nVYzTEO9UNKjh+dssjuokg36sppVCfkiQK/3YkeSjc8kV/cAxEavDsiVw79Nal8l OLe50y5CI3mHWo0d2oBYvCHSlzz908GPbbKuUcxnCrQLDUe9V6+BYnKq0oLN2ic3 Zcc0u015zx9ByTQ1roILUP0xNPVDOO6Oy6kBKkhH7EG/c3axvimv9JstGwuSvhBK wLGBMnO5CIdnkhLgtpbzlwcWRuXaUJnWcURtqoyVOdE+BXWIgEUiVkk1rQtTljPI 5J2EBtDaiO9VLl4MJ8NlCqoI7X37cBoTA4H8WmG+kc+O8FyE1t1R0NOKxa1dSvAO i16vVEtwc06U5bJhIXUDd2JfzANauseGFwrj4nNyHPWii9RU32P8aVCVQR5DaM2r hAOiEP1I3h06jcm9kaAoU/U8eHH9kbg9Bs5uun/dwDZ+d6ynhndMOUeNqrQ5ytji d4nQFnTeG83Eywd/vQvJ =Yyz3 -END PGP SIGNATUREEnd Message---
Processed: user debian-secur...@lists.debian.org, tagging 770918, usertagging 770918
Processing commands for cont...@bugs.debian.org: user debian-secur...@lists.debian.org Setting user to debian-secur...@lists.debian.org (was car...@debian.org). tags 770918 + upstream Bug #770918 [flac] Two CVEs against FLAC Added tag(s) upstream. usertags 770918 + tracked There were no usertags set. Usertags are now: tracked. thanks Stopping processing here. Please contact me if you need assistance. -- 770918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forwarded
Processing commands for cont...@bugs.debian.org: forwarded 768658 https://github.com/alexott/ecb/issues/26 Bug #768658 [ecb] ecb: install upgrade fails Set Bug forwarded-to-address to 'https://github.com/alexott/ecb/issues/26'. forwarded 768751 https://github.com/alexott/ecb/issues/26 Bug #768751 [src:ecb] ecb: FTBFS in jessie Set Bug forwarded-to-address to 'https://github.com/alexott/ecb/issues/26'. tags 768658 upstream confirmed Bug #768658 [ecb] ecb: install upgrade fails Added tag(s) upstream and confirmed. tags 768751 upstream confirmed Bug #768751 [src:ecb] ecb: FTBFS in jessie Added tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 768658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768658 768751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768695: Bug #768695: statsmodels: FTBFS in jessie: ImportError: cannot import name DateRange
On Sun, Nov 23, 2014 at 07:13:07PM +0100, Michael Banck wrote: Hi have uploaded the attached debdiff targetted at testing-proposed-updates to DELAYED/3-day. See also the pre-approval/unblock bug for relesae.debian.org, #770730. Unfortunately, it FTBFS on i386 still, there are a couple of test suite failures: https://buildd.debian.org/status/fetch.php?pkg=statsmodelsarch=i386ver=0.4.2-1.1stamp=1416885423 Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766187: /etc/inittab - base-files?
Hi, the problem of having to cope with a non-existing inittab would imho be solved if the inittab file could be transplanted to base-files. But then, sysvinit would need to be modified to patch an existing inittab, instead of simply installing its basic known-good version. I am not sure that this will not simply open a different can of worms. The decision then becomes, which entries to keep, and which to overwrite. It also looks like the keys in the inittab are agreed upon by convention, not by standard - right? Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#770751: adt-run fail with ValueError: Invalid version string '10.1.1-1]'
Processing control commands: severity -1 normal Bug #770751 [autopkgtest] adt-run fail with ValueError: Invalid version string '10.1.1-1]' Severity set to 'normal' from 'grave' tag -1 moreinfo Bug #770751 [autopkgtest] adt-run fail with ValueError: Invalid version string '10.1.1-1]' Added tag(s) moreinfo. -- 770751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770751: adt-run fail with ValueError: Invalid version string '10.1.1-1]'
Control: severity -1 normal Control: tag -1 moreinfo Hello, Pirate Praveen [2014-11-24 1:21 +0530]: pravi@savannah:~/forge/debian/git/pkg-ruby-extras/ruby-jwt $ adt-run -B .// --- null I checked current ruby-jwt git and there's no autopkgtest there, so I suppose you didn't commit that yet. raise ValueError(Invalid version string %r % version) ValueError: Invalid version string '10.1.1-1]' This looks like a typo in your debian/tests/control, you seem to have an extra ']' there. If that's not it, can you please attach your file or the complete test so that I can reproduce? Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#770932: ruby2.1: CVE-2014-8090
Package: ruby2.1 Severity: grave Tags: security Hi, please see https://www.ruby-lang.org/en/news/2014/11/13/rexml-dos-cve-2014-8090/ for details. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768707: getting this into jessie?
Hi, as far as I can see, the one problem is that these two small dependencies, python-sphinx-testing and python3-sphinx-testing, are not in Jessie, which apparently prevents several packages from going into Jessie. I can see two ways forward: One, make an exception for python*-sphinx-testing, and the other, patching the testing code out of the builds for the sphinx-* packages. Which one do you prefer? Cheers, --Toni++ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766187: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2
I noticed that my last mail about 766187 being related to 768657 didn't actually go to the bug report. (which was about this bug being related) Anyway, both of these bugs seem to be about providing /etc/inittab in one form or another. Please see KiBi's last entry about providing it via D-I which has gone unanswered. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768657 I'm only sharing this as it would appear there are two separate conversations happening about the same problem. (and i'm assuming that a solution should / would solve both) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770330: how to change UID_MIN, UID_MAX, FIRST_GID, LAST_GID, etc.?
android-permissions integrates the Android permissions into a Debian chroot running on Android. This package should only ever run on a Debian chroot running with an Android kernel. It should modify things like GID_MAX or LAST_GID in /etc/login.defs and /etc/adduser.conf to reflect the hard-coded Android UIDs and GIDs, but it is a policy violation for a package to modify those files. Any suggestions as how to best tackle this issue? signature.asc Description: OpenPGP digital signature
Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
Package: needrestart
Version: 1.2-5
Severity: grave
Justification: data loss
Hi Thomas and Patrick,
recently, it happened twice that needrestart killed my X session which
was started by wdm and is running the awesome window manager via
~/.Xsession.
I don't think it's the new upload but rather the recent dbus updates. I
can't exactly remember if the second-last case was at the time when dbus
was updated (and if so, needrestart would have been at version 1.2-4),
but the case today definitely had a dbus update included.
According to the logs it also restarted systemd itself.
Despite there is
$nrconf{override_rc} = {
# DBus
q(^dbus) = 0,
[…]
}
in the (used) default config, systemd restarted dbus:
Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus...
A more verbose log excerpt of what seems relevant to me:
Nov 25 11:18:57 c-cactus systemd[1]: Reexecuting.
Nov 25 11:18:57 c-cactus systemd[1]: systemd 215 running in system mode. (+PAM
+AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP
-APPARMOR)
Nov 25 11:18:57 c-cactus systemd[1]: Detected architecture 'x86-64'.
Nov 25 11:18:57 c-cactus systemd[1]: Started ACPI event daemon.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /var.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /home.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /boot.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /.
Nov 25 11:18:57 c-cactus systemd[1]: Started File System Check on
/dev/disk/by-uuid/….
[…]
Nov 25 11:18:57 c-cactus systemd[1]: Activated swap /dev/…/swap.
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Accounts Service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Bluetooth service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Regular background program
processing daemon...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Regular background program
processing daemon...
Nov 25 11:18:57 c-cactus systemd[1]: Started Regular background program
processing daemon.
Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Accounts Service...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Bluetooth service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping OpenBSD Secure Shell server...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Journal Service...
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Default.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Default.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Basic System.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Basic System.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Paths.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Paths.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Timers.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Timers.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Sockets.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Sockets.
Nov 25 11:18:57 c-cactus systemd[1641]: Starting Shutdown.
Nov 25 11:18:57 c-cactus systemd[1641]: Reached target Shutdown.
Nov 25 11:18:57 c-cactus systemd[1641]: Starting Exit the Session...
Nov 25 11:18:57 c-cactus systemd[1]: Starting OpenBSD Secure Shell server...
Nov 25 11:18:57 c-cactus systemd[1]: Started OpenBSD Secure Shell server.
Nov 25 11:18:57 c-cactus systemd[1641]: Received SIGRTMIN+24 from PID 12082
(kill).
Nov 25 11:18:57 c-cactus systemd[1]: Started Trigger Flushing of Journal to
Persistent Storage.
Nov 25 11:18:57 c-cactus systemd[1]: Starting Daemon for power management...
Nov 25 11:18:57 c-cactus systemd[1]: Starting LSB: Starts and stops Wicd...
Nov 25 11:18:57 c-cactus systemd[1]: Starting D-Bus System Message Bus...
Nov 25 11:18:57 c-cactus systemd[1]: Started D-Bus System Message Bus.
Nov 25 11:18:57 c-cactus systemd[1]: Started Bluetooth service.
Nov 25 11:18:57 c-cactus systemd[1]: Starting Hostname Service...
Nov 25 11:18:57 c-cactus systemd[1]: Started Accounts Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started Daemon for power management.
Nov 25 11:18:57 c-cactus systemd[1]: Starting User Manager for UID 1000...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Login Service...
Nov 25 11:18:57 c-cactus systemd[1]: Started Hostname Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started Login Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started User Manager for UID 1000.
Nov 25 11:18:58 c-cactus systemd[1]: Starting Session c1 of user abe.
Nov 25 11:18:58 c-cactus systemd[1]: Started Session c1 of user abe.
Nov 25 11:18:59 c-cactus systemd[1]: Starting LSB: start or stop the WINGs
display manager...
Nov 25 11:18:59 c-cactus systemd[1]: Started LSB: start or stop the WINGs
display manager.
Nov 25 11:18:59 c-cactus systemd[1]: Starting X11 Display Manager.
Nov 25 11:18:59 c-cactus systemd[1]: Reached target X11 Display Manager.
I can send an even more complete journal log by private e-mail.
-- Package-specific
Processed: Bug#766879 marked as pending
Processing commands for cont...@bugs.debian.org: tag 766879 pending Bug #766879 [python-caja] Strange behaviour after update of python-caja in Debian (from 1.8.0-1/testing to 1.8.1-1/unstable) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 766879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766879: marked as pending
tag 766879 pending thanks Hello, Bug #766879 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-mate/python-caja.git;a=commitdiff;h=02829d0 --- commit 02829d0630d1c6edf745894ba355b552ef79dd1c Author: Mike Gabriel mike.gabr...@das-netzwerkteam.de Date: Tue Nov 25 12:01:20 2014 +0100 update changelog from Git history diff --git a/debian/changelog b/debian/changelog index 5f471fd..927db9a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,18 @@ +python-caja (1.8.1-2) UNRELEASED; urgency=medium + + [ Vangelis Mouhtsis ] + * debian/control: ++ Fix typo in python-caja-dbg LONG_DESCRIPTION. (Closes: #768819, #768820). + + [ Mike Gabriel ] + * debian/patches: ++ Add 1002_dont-install-xsl-files.patch. Stop attempting to install XSL + docbook source files into bin:package. (Closes: #770927). ++ Add 2001_debian-python-multiarch.patch. Enforce usage of multiarch path + for PY_LIB_LOC. (Closes: 766879, LP: #1170017). + + -- Vangelis Mouhtsis vange...@gnugr.org Tue, 25 Nov 2014 09:42:56 +0100 + python-caja (1.8.1-1) unstable; urgency=medium [ Vangelis Mouhtsis ] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770939: opensmtpd: fails to install: subprocess installed post-installation script returned error exit status 1
Package: opensmtpd Version: 5.4.2p1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package opensmtpd. (Reading database ... 7423 files and directories currently installed.) Preparing to unpack .../opensmtpd_5.4.2p1-3_amd64.deb ... Unpacking opensmtpd (5.4.2p1-3) ... Setting up opensmtpd (5.4.2p1-3) ... dpkg: error processing package opensmtpd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: opensmtpd Rerunning the test manually and debugging it afterwards: set -x, DEBCONF_DEBUG=developer # dpkg --configure --pending Setting up opensmtpd (5.4.2p1-3) ... + set -e + . /usr/share/debconf/confmodule + [ ! ] + PERL_DL_NONLAZY=1 + export PERL_DL_NONLAZY + [ ] + exec /usr/share/debconf/frontend /var/lib/dpkg/info/opensmtpd.postinst configure debconf (developer): frontend started debconf (developer): frontend running, package name is opensmtpd debconf (developer): starting /var/lib/dpkg/info/opensmtpd.config configure debconf (developer): -- FGET opensmtpd/mailname seen debconf (developer): -- 0 false dpkg: error processing package opensmtpd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: opensmtpd cheers, Andreas opensmtpd_5.4.2p1-3.log.gz Description: application/gzip
Bug#767653:
Hi Tobi, thanks for the clearifications, I've pushed a new version. Can you have a look again? Cheers Jochen signature.asc Description: Digital signature
Bug#770941: nova-common - Overrides database config in nova.conf
Package: nova-common Version: 2014.1.3-6 Severity: serious A simple upgrade or re-install of nova-common overrides the database settings in nova.conf: | diff -ur nova/nova.conf /etc/nova/nova.conf | --- nova/nova.conf 2014-10-02 15:09:04.672855761 +0200 | +++ /etc/nova/nova.conf 2014-11-25 12:02:37.194997496 +0100 | @@ -349,7 +349,7 @@ | # DATABASE # | | [database] | -connection = postgresql:///nova | +connection = postgresql://novacommon:X@localhost/novadb | | | # This violates §10.7.3 of the Debian policy: local changes must be preserved. Bastian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 770918 in 1.2.1-6
Processing commands for cont...@bugs.debian.org: found 770918 1.2.1-6 Bug #770918 [flac] Two CVEs against FLAC Marked as found in versions flac/1.2.1-6. thanks Stopping processing here. Please contact me if you need assistance. -- 770918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770330: ideas from #debian-devel
The package android-permissions integrates the Android permissions into a Debian chroot running on Android. Android permissions are implemented in Android's Linux kernel using UIDs and GIDs. Therefore, this package should only ever run on a Debian chroot running with an Android kernel. It adds all of the hard-coded users and groups to Debian. It should also modify things like GID_MAX or LAST_GID in /etc/login.defs and /etc/adduser.conf to reflect the hard-coded Android UIDs and GIDs. One idea for a solution was to make a debootstrap variant, but I'm not sure that cdebootstrap supports that. The idea is rather than having the package do these changes directly, it provides a script that does the changes to a specified root directory. Then this script is run as part of the variant. Another idea is to create /etc/login.defs.d and /etc/adduser.conf.d so that packages can add definitions there. I'm not sure yet whether either approach is good. signature.asc Description: OpenPGP digital signature
Bug#770918: patches
Attached patches from upstream, which apply to 1.2.1-6. DSA should be created.
---
Henri Salo
--- src/libFLAC/stream_decoder.c.orig 2014-11-25 13:41:50.280032892 +0200
+++ src/libFLAC/stream_decoder.c 2014-11-25 13:48:39.697566936 +0200
@@ -94,7 +94,7 @@
*
***/
-static FLAC__byte ID3V2_TAG_[3] = { 'I', 'D', '3' };
+static const FLAC__byte ID3V2_TAG_[3] = { 'I', 'D', '3' };
/***
*
@@ -1386,6 +1386,10 @@
id = 0;
continue;
}
+
+ if(id = 3)
+ return false;
+
if(x == ID3V2_TAG_[id]) {
id++;
i = 0;
--- src/libFLAC/stream_decoder.c.orig 2014-11-25 13:41:50.280032892 +0200
+++ src/libFLAC/stream_decoder.c 2014-11-25 13:46:21.862277460 +0200
@@ -2726,7 +2726,8 @@
if(decoder-private_-frame.header.blocksize predictor_order) {
send_error_to_client_(decoder, FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC);
decoder-protected_-state = FLAC__STREAM_DECODER_SEARCH_FOR_FRAME_SYNC;
- return true;
+ /* We have received a potentially malicious bt stream. All we can do is error out to avoid a heap overflow. */
+ return false;
}
}
else {
signature.asc
Description: Digital signature
Processed: tagging 770918
Processing commands for cont...@bugs.debian.org: tags 770918 + patch Bug #770918 [flac] Two CVEs against FLAC Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 770918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770942: kernel panic from wlc_ioctl
Package: broadcom-sta-dkms Version: 6.30.223.248-2 Severity: critical this bug report is about a kernel panic that happens pretty reproducibly on two systems with different broadcom card models and kernel builds. in both cases, it does not happen during normal network traffic, but only when the instant messenger gajim is started. i'll call the affected systems by their hostnames. hephaistos has a BCM43142 wifi card and uses the 3.16-1~exp1 kernel. here's a transcript a screenshot's relevant parts (can provide full screenshot if it helps): BUG: unable to handle kernel NULL pointer dereference at 0360 IP: [a062e963] wlc_ioctl+0x21/0x168 [wl] [...] CPU: 1 PID: 21221 Comm: gajim Tainted: P O 3.16-trunk-amd64 #1 Debian 3.16-1~exp1 [...] Call Trace: wl_proc_read+0x40/0xa0 [wl] proc_read_reg+0x34/0x70 vfs_read+0x8e/0x170 SyS_read+0x3d/0xa0 system_call_fast_compare_end+0x10/0x15 hephaistos has been on sid plus some experimental since long, and the behavior first appeared around 2014-10-29. i blamed it on failing hardware (graphics card behaved oddly at the same time) and replaced the device. artemis has a BCM4313, and was recently (around 2014-11-20) upgraded from wheezy to jessie. it has a 3.16.0-4-amd64 kernel. its backtrace only differs in gajim PID, kernel taint (there's an additional W), kernel version (3.16.0-4-amd64 #1 Debian 3.16.7-2) and the details of the call trace (the +0x00 part is larger by 5 for all but system_call_fast_compare_end). i'll try to further narrow down which kernel versions are affected, and what kind of traffic causes the issue (my first wild guess would be multicasting, which gajim probably does for lan-local autodiscovery). is there any further information i can provide to find a solution for this? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages broadcom-sta-dkms depends on: ii dkms 2.2.0.3-2 Versions of packages broadcom-sta-dkms recommends: ii wireless-tools 30~pre9-8 broadcom-sta-dkms suggests no packages. -- To use raw power is to make yourself infinitely vulnerable to greater powers. -- Bene Gesserit axiom signature.asc Description: Digital signature
Processed: retitle 770918 to flac: CVE-2014-8962/CVE-2014-9028: heap buffer overflows
Processing commands for cont...@bugs.debian.org: retitle 770918 flac: CVE-2014-8962/CVE-2014-9028: heap buffer overflows Bug #770918 [flac] Two CVEs against FLAC Changed Bug title to 'flac: CVE-2014-8962/CVE-2014-9028: heap buffer overflows' from 'Two CVEs against FLAC' thanks Stopping processing here. Please contact me if you need assistance. -- 770918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770941: neutron-common - Overrides database config in neutron.conf and fails to upgrade
Control: clone -1 -2 Control: reassign -2 neutron-common 2014.1.3-6 Hi The same is true for neutron-common. However it have the additional problem that postinst actually fails: | Installing new version of config file /etc/neutron/rootwrap.d/l3.filters ... | Installing new version of config file /etc/neutron/policy.json ... | Installing new version of config file /etc/logrotate.d/neutron-common ... | PKG-Openstack now calling: dbc_go neutron-common configure 2014.1.2-1~bpo70+1 | dbconfig-common: writing config to /etc/dbconfig-common/neutron-common.conf | dbconfig-common: flushing administrative password | No handlers could be found for logger neutron.common.legacy | Traceback (most recent call last): | File /usr/bin/neutron-db-manage, line 10, in module | sys.exit(main()) | File /usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py, line 169, in main | CONF.command.func(config, CONF.command.name) | File /usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py, line 82, in do_upgrade_downgrade | do_alembic_command(config, cmd, revision, sql=CONF.command.sql) | File /usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py, line 60, in do_alembic_command | getattr(alembic_command, cmd)(config, *args, **kwargs) | File /usr/lib/python2.7/dist-packages/alembic/command.py, line 124, in upgrade | script.run_env() | File /usr/lib/python2.7/dist-packages/alembic/script.py, line 199, in run_env | util.load_python_file(self.dir, 'env.py') | File /usr/lib/python2.7/dist-packages/alembic/util.py, line 199, in load_python_file | module = load_module(module_id, path) | File /usr/lib/python2.7/dist-packages/alembic/compat.py, line 55, in load_module | mod = imp.load_source(module_id, path, fp) | File /usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py, line 103, in module | run_migrations_online() | File /usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py, line 78, in run_migrations_online | connection = engine.connect() | File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 1641, in connect | return self._connection_cls(self, **kwargs) | File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 59, in __init__ | self.__connection = connection or engine.raw_connection() | File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 1699, in raw_connection | return self.pool.unique_connection() | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 220, in unique_connection | return _ConnectionFairy(self).checkout() | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 431, in __init__ | rec = self._connection_record = pool._do_get() | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 871, in _do_get | return self._create_connection() | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 225, in _create_connection | return _ConnectionRecord(self) | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 318, in __init__ | self.connection = self.__connect() | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 379, in __connect | connection = self.__pool._creator() | File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/strategies.py, line 80, in connect | return dialect.connect(*cargs, **cparams) | File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py, line 283, in connect | return self.dbapi.connect(*cargs, **cparams) | File /usr/lib/python2.7/dist-packages/psycopg2/__init__.py, line 179, in connect | connection_factory=connection_factory, async=async) | sqlalchemy.exc.OperationalError: (OperationalError) could not connect to server: Connection refused | Is the server running on host localhost (127.0.0.1) and accepting | TCP/IP connections on port 5432? | None None | dpkg: error processing neutron-common (--configure): | subprocess installed post-installation script returned error exit status 1 | dpkg: dependency problems prevent configuration of neutron-server: -- Bastian Blank Berater Telefon: +49 2161 / 4643-194 E-Mail: bastian.bl...@credativ.de credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 Hohenzollernstr. 133, 41061 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: neutron-common - Overrides database config in neutron.conf and fails to upgrade
Processing control commands: clone -1 -2 Bug #770941 [nova-common] nova-common - Overrides database config in nova.conf Bug 770941 cloned as bug 770944 reassign -2 neutron-common 2014.1.3-6 Bug #770944 [nova-common] nova-common - Overrides database config in nova.conf Bug reassigned from package 'nova-common' to 'neutron-common'. No longer marked as found in versions nova/2014.1.3-6. Ignoring request to alter fixed versions of bug #770944 to the same values previously set Bug #770944 [neutron-common] nova-common - Overrides database config in nova.conf Marked as found in versions neutron/2014.1.3-6. -- 770941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770941 770944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769191: Bug#769072: , #769191, #770588: nvidia-opencl-icd breaking non-nvidia systems
On 2014-11-24 22:47, Rebecca N. Palmer wrote: First of all, many thanks for analyzing the problem and keeping track of the many duplicates! (Should we merge these bugs? Also, #767803 looks like another instance of this, though it doesn't have the apt log to confirm it yet) and perhaps move the discussion to one of these bugs and trim the Cc list a bit ... If you merge them, please reassign them to src:nvidia-driver and add Affects for the packages where they have been reported. * nvidia-kernel-dkms: Switch to Recommends: nvidia-driver | libcuda1 to break the chain libcuda1 - nvidia-kernel-dkms - nvidia-driver. ...or drop this Recommends: entirely That Recommends has been there since nvidia-kernel-dkms was added in 2010. I thinks its main purpose is for people that try to install the wrong package (i.e. nvidia-kernel-dkms instead of nvidia-driver (or nvidia-glx back then)) to get a working NVIDIA driver installation (well, still needs some manual configuration, but debconf will tell you that). I don't want to touch (as in remove) that right now. (IIRC circular Depends/Recommends are discouraged because they confuse apt's autoremover, though I can't find where I saw that). I don't want to workaround bugs in unrelated packages Cutting the chain here (tested with apt-get install nvidia-libopencl1 nvidia-driver-, the - after a package means remove/don't install) does still allow much of nvidia-* (including nvidia-kernel-dkms and glx-alternative-nvidia) to be installed, but that appears to be harmless and you get the full set of lib*GL* diversions, too ... this and some more are needed to allow switching between nvidia-opencl-icd and nvidia$LEGACY-opencl-icd which will become available once I fork off (and backport) nvidia-graphics-drivers-legacy-340xx after the jessie release. without libgl1-nvidia-glx (at least on my Intel IvyBridge M GT2, both graphics and OpenCL continue to work after rebooting). That would be a bug otherwise :-) Given that the error on loading nvidia-opencl-icd in a non-Nvidia system is modprobe: ERROR: could not insert 'nvidia_current': No such device it is plausible that nvidia-opencl-icd uses the nvidia kernel module (i.e. nvidia-kernel-dkms | nvidia-kernel-version) and as such _should_ pull it in (whether or not it also needs libcuda1), In wheezy all this OpenCL stuff was rather new and only proprietary implementations were available ... as a result installing nvidia-opencl-icd was harmless (due to lack of dependencies) but also useless (due to lack of dependencies) unless you had nvidia-driver installed, too. This I wanted to fix in jessie :-) while #768185 suggests that nvidia-opencl-icd works without the graphics side (can someone check that?), I'm pretty sure NVIDIA CUDA and OpenCL work in headless setups, i.e. without X server running. They just need the kernel module to be loaded (and the corresponding device to be created). (Contrary to AMD which needs X to communicate with the GPU for doing OpenCL) making this the more correct place to cut the chain. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746259: marked as done (fish: CVE-2014-2905 CVE-2014-2906 CVE-2014-2914 CVE-2014-3219 CVE-2014-3856)
Your message dated Tue, 25 Nov 2014 12:18:57 + with message-id e1xtf57-000300...@franck.debian.org and subject line Bug#746259: fixed in fish 2.1.1-1 has caused the Debian Bug report #746259, regarding fish: CVE-2014-2905 CVE-2014-2906 CVE-2014-2914 CVE-2014-3219 CVE-2014-3856 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 746259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: fish Version: 1.23.1-2 Severity: grave Tags: security upstream Hi, the following vulnerabilities were published for fish. CVE-2014-2905[0]: permission bypass leading to privilege escalation CVE-2014-2906[1]: unsafe temporary file creationg leading to privilege escalation CVE-2014-2914[2]: remote code execution More details are in [3]. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2014-2905 [1] https://security-tracker.debian.org/tracker/CVE-2014-2906 [2] https://security-tracker.debian.org/tracker/CVE-2014-2914 [3] http://www.openwall.com/lists/oss-security/2014/04/28/4 Regards, Salvatore ---End Message--- ---BeginMessage--- Source: fish Source-Version: 2.1.1-1 We believe that the bug you reported is fixed in the latest version of fish, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 746...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gustavo Noronha Silva k...@debian.org (supplier of updated fish package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Nov 2014 14:09:15 -0200 Source: fish Binary: fish fish-dbg Architecture: source amd64 Version: 2.1.1-1 Distribution: unstable Urgency: medium Maintainer: Gustavo Noronha Silva k...@debian.org Changed-By: Gustavo Noronha Silva k...@debian.org Description: fish - friendly interactive shell fish-dbg - friendly interactive shell (debugging symbols) Closes: 746259 Changes: fish (2.1.1-1) unstable; urgency=medium . * New upstream release - includes fixes for the following security issues (Closes: #746259): + CVE-2014-2905 + CVE-2014-2906 + CVE-2014-2914 + CVE-2014-3219 + CVE-2014-3856 Checksums-Sha1: 0aac958d1ac7158a868056c11a9021a465a4d13a 1541 fish_2.1.1-1.dsc 8f97f39b92ea7dfef1f464b18e304045bf37546d 1681744 fish_2.1.1.orig.tar.gz 41f94f41607deef3c41c3127829b7aac89721ab5 11783 fish_2.1.1-1.diff.gz 270d8ecc52a90defdac7371bcf460f47d69e9e4e 830156 fish_2.1.1-1_amd64.deb e12df7f0df8abe0e6e9af4a67f3ee598121fefe1 2641196 fish-dbg_2.1.1-1_amd64.deb Checksums-Sha256: 6aaf576d15d78ffdc9af1272676bbda48b37b6560491cbc190c4d1580f0344f5 1541 fish_2.1.1-1.dsc b7e4d3c3d55fc3859edcb20462fcf0d14ab26e920eddcd503072e8105284d924 1681744 fish_2.1.1.orig.tar.gz 31f876fce4e61ca25de1b386d8792a0fb73fdcca83d9127e5cf77a2b5b7f4926 11783 fish_2.1.1-1.diff.gz 85c1b3129b063a8580ff4553c6888c06a6a567a663848f99b041507a269819ff 830156 fish_2.1.1-1_amd64.deb 89178ee384187897f0ef8196d6fcff76f0904259bb08e2ace496ead7f640fcd5 2641196 fish-dbg_2.1.1-1_amd64.deb Files: 7f79bbef7d356346c830ae177d4db7ec 1541 shells optional fish_2.1.1-1.dsc 0251e6e5f25d1f326e071425ea1dee22 1681744 shells optional fish_2.1.1.orig.tar.gz 510d47c6a359e72415779c6811f2aae3 11783 shells optional fish_2.1.1-1.diff.gz 1b1b06144f4054ba58e4b3d50b4eec4c 830156 shells optional fish_2.1.1-1_amd64.deb 5a0e0d33eb158eb85188f896d823c325 2641196 debug extra fish-dbg_2.1.1-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUc1tMAAoJENIA6zCg+12mUcMH/1pgyx3vKyw8ZC2nY2Q3c/w+ QaVMYQ9XyKn3w4MH27QbWXRYMljGZG1I5ykBmwGAKtquQaTK1FSKlcNA4SbIt8b2 JMhReTMCeMuRoJm4qMKzw4lI8vKqHSgBLUrDoi7CdFBun19MndYO9O9BrkKj4azQ tJZxwLuLUjqeDlT+iWD0PjAIOURlDX2zyhVybpQUCfpqZP254myP+V9JSPnn8EUh zXhYnfD1SOfM7xVBXve+ItNZhiOLuD8rfsYfqojREq8FaTeNpKWctpGFwWQO6uKI lsFkEo0CVYQrnJQVjovM/i3qI6ii07G3rxsBXZZ2kKboax4Ui7LvTOd3D+RvMPM= =soeB -END PGP SIGNATUREEnd Message---
Bug#770328: (no subject)
Thanks for the patch, I'm working on including it now. Unfortunately, android-platform-system-core_21-4 does not fix the other related bug: https://bugs.debian.org/769251 I'm working on that still, that fix will be in a different package: android-platform-frameworks-native .hc signature.asc Description: OpenPGP digital signature
Bug#770328: marked as done (android-liblog-dev: fails to upgrade from 'testing' - trying to overwrite /usr/lib/android/liblog.so)
Your message dated Tue, 25 Nov 2014 12:33:57 + with message-id e1xtfjd-00071m...@franck.debian.org and subject line Bug#770328: fixed in android-platform-system-core 21-5 has caused the Debian Bug report #770328, regarding android-liblog-dev: fails to upgrade from 'testing' - trying to overwrite /usr/lib/android/liblog.so to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: android-liblog-dev Version: 21-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to unpack .../android-liblog-dev_21-4_amd64.deb ... Unpacking android-liblog-dev (21-4) over (21-3) ... dpkg: error processing archive /var/cache/apt/archives/android-liblog-dev_21-4_amd64.deb (--unpack): trying to overwrite '/usr/lib/android/liblog.so', which is also in package android-liblog 21-3 Preparing to unpack .../android-liblog_21-4_amd64.deb ... Unpacking android-liblog (21-4) over (21-3) ... Errors were encountered while processing: /var/cache/apt/archives/android-liblog-dev_21-4_amd64.deb cheers, Andreas android-liblog-dev_21-4.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: android-platform-system-core Source-Version: 21-5 We believe that the bug you reported is fixed in the latest version of android-platform-system-core, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hans-Christoph Steiner h...@eds.org (supplier of updated android-platform-system-core package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Nov 2014 12:43:50 +0100 Source: android-platform-system-core Binary: android-system-dev android-liblog android-liblog-dev android-libcutils android-libcutils-dev android-libzipfile android-libzipfile-dev Architecture: source amd64 Version: 21-5 Distribution: unstable Urgency: low Maintainer: Android tools Maintainer android-tools-de...@lists.alioth.debian.org Changed-By: Hans-Christoph Steiner h...@eds.org Description: android-libcutils - Android utils library for C android-libcutils-dev - Android utils library for C - Development files android-liblog - Android logging library android-liblog-dev - Android logging library - Development files android-libzipfile - Android zipfile library android-libzipfile-dev - Android zipfile library - Development files android-system-dev - Android system development headers Closes: 770328 Changes: android-platform-system-core (21-5) unstable; urgency=low . [Simon McVittie] * For each library where libwhatever.so moved from android-libwhatever to android-libwhatever-dev, the -dev Breaks/Replaces the runtime library (Closes: #770328) Checksums-Sha1: ed8feaf6915e435255914e30ab4a5609d10facea 2752 android-platform-system-core_21-5.dsc d414c6e71811ec01d865f7be5943c84b485d4f75 13884 android-platform-system-core_21-5.debian.tar.xz c2e75e0d2ec659186f67ba504f1af597002a9d80 24390 android-system-dev_21-5_amd64.deb fdbb15234e6f95000286a8397c4292f047312e94 15704 android-liblog_21-5_amd64.deb 4aedf021450683e8947c145106135e4d4b5d8951 21728 android-liblog-dev_21-5_amd64.deb 5d095587bfaaf15004eeff4fa18a04b8cc1091e1 22984 android-libcutils_21-5_amd64.deb 750d71347480ba61b13874120d72cb24fd2e88f0 38770 android-libcutils-dev_21-5_amd64.deb a4435a99849f00fc90b6af1c9153db12737edcfe 7542 android-libzipfile_21-5_amd64.deb 434326488a73e5904ccc9bccee2199a24bf9583d 6968 android-libzipfile-dev_21-5_amd64.deb Checksums-Sha256: ee1aedc7fa3ef1eb8a1341fdc93415f906b510da1d885820cca435cd8ce4e4e1 2752
Bug#770259: marked as done (RM: debian-installer [sparc] -- out of date, doesn't build)
Your message dated Tue, 25 Nov 2014 12:36:01 + with message-id e1xtfld-0007yw...@franck.debian.org and subject line Bug#770259: Removed package(s) from unstable has caused the Debian Bug report #770259, regarding RM: debian-installer [sparc] -- out of date, doesn't build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: eglibc Version: 2.17-97 Severity: serious From my pbuilder build log: ... checking for ld... ld checking version of ld... 2.24.90, ok checking for x86_64-linux-gnu-gcc... (cached) x86_64-linux-gnu-gcc-4.7 checking version of x86_64-linux-gnu-gcc-4.7... 4.7.4, ok checking for gnumake... no checking for gmake... no checking for make... make checking version of make... 4.0, bad checking for gnumsgfmt... no checking for gmsgfmt... no checking for msgfmt... msgfmt checking version of msgfmt... 0.19.3, ok checking for makeinfo... : checking version of :... v. ?.??, bad checking for sed... sed checking version of sed... 4.2.2, ok checking for gawk... gawk checking version of gawk... 4.1.1, ok checking for x86_64-linux-gnu-nm... x86_64-linux-gnu-nm checking for autoconf... false checking whether false works... no configure: error: *** These critical programs are missing or too old: make *** Check the INSTALL file for required versions. debian/rules.d/build.mk:31: recipe for target '/tmp/buildd/eglibc-2.17/stamp-dir/configure_libc' failed make: *** [/tmp/buildd/eglibc-2.17/stamp-dir/configure_libc] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Given that src:eglibc is pretty much obsoleted by src:glibc now, I'd guess the easiest way to fix this would be to just request the removal of src:eglibc from sid. -- Daniel Schepler ---End Message--- ---BeginMessage--- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: debian-installer | 20131211 | sparc --- Reason --- out of date, doesn't build -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/770259 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)---End Message---
Bug#766670: RC bug in stable and oldstable for getmail4
On Tue, Nov 25, 2014 at 10:04:34AM +0100, Raphael Hertzog wrote: Hi, On Sun, 23 Nov 2014, Osamu Aoki wrote: By the way, I uploaded getmail4_4.46.0-1~bpo70+1_amd64 We can consider a new upstream version for squeeze-lts and we can ask the security team's opinion for wheezy. Would you like to prepare a 4.46.0-1~deb6u1.dsc working in squeeze and submit it for review to debian-...@lists.debian.org ? See below. It does not look like simple re-versioning and safe backporting without careful review. It would be nice if you could test it though, because we don't have many testers before release... I only use this package for POP3. Most of the changes are in IMAP4 code so my test with POP3 is useless. Henrique's test on my backported package is the good reference. https://ftp-master.debian.org/new/getmail4_4.46.0-1~bpo70%2B1.html I build this under pure wheezy chroot. This can probably be renumbered 4.46.0-1~deb7u1.dsc and submitted to the security team ? Or does it depend on other packages from backports ? This package is one of those python package using debian/rules as: %: dh $@ --with python2 Since I build this jessie package in the old jessie/sid environment which is very similar to released wheezy, I was not asked to add the dh-python dependency to the debian/control. In wheezy, --with python2 is supported via python package, as I understood. So building for wheezy point release is simple and safe with bumping version to 4.46.0-1~deb7u1. I am not quite sure what change is needed for backporting python package with older python helper scripts. Also, I do not know if compat 8 is supported by squeeze. (as for debhelper, I see no major issue as long as compat7 is provided.) Thus, squeeze is a bit more complicated and requires more testing. FYI: I moved to current packaging style in 2011-07 with 4.20.3-1 The oldstable package oldstable 4.20.0-1 was made with different python helper script in 2010-07. (If I do this backport as my job, I will probably keep old packaging style.) For all practical purpose, if someone needs to use this package under oldstable, he should do so by just dpkg -i newpackage since python helper script does not matter for binary packages. I am not really motivated to do this Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769830: (no subject)
source is included for these minified javascripts, in the debian directory. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#769947: mate-terminal: Segfaults after update
Processing control commands: severity -1 grave Bug #769947 [mate-terminal] mate-terminal: Segfaults after update Severity set to 'grave' from 'important' tag -1 moreinfo Bug #769947 [mate-terminal] mate-terminal: Segfaults after update Added tag(s) moreinfo. -- 769947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768095: openvswitch-datapath-dkms fails to build on Debian 7.7 3.2.0-4-amd64 (3.2.63-2+deb7u1)
On 11/25/2014 12:32 AM, Jonathan Dupart wrote: Hi, I am looking for a sponsor for the package openvswitch to correct bug #768095. This bug prevents building the openvswitch kernel module with the last stable kernel. As openvswitch maintainer requested an NMU, i built a package [1] with the patch already used by Ubuntu to fix the same bug [2] (i use this fix since 10 days on live servers). I attached a full debdiff of the changes. [1]: http://mentors.debian.net/package/openvswitch http://mentors.debian.net/debian/pool/main/o/openvswitch/openvswitch_1.4.2+git20120612-9.1~deb7u1.1.dsc [2]: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1379201 Regards, Hi Jonathan, Before uploading such an update, this has to be discussed with the release team, as part of the stable-proposed-updates procedure. Please open a bug against the release.debian.org pseudo-package, and get approval by the release team (when writing such bug report, you must send a debdiff between the version in Wheezy and the proposed version). When the release team has approved your change, then I can sponsor it. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: forcibly merging 770425 770949
Processing commands for cont...@bugs.debian.org:
forcemerge 770425 770949
Bug #770425 {Done: Craig Small csm...@debian.org} [src:wordpress] wordpress:
4.0.1 security release
Bug #770425 {Done: Craig Small csm...@debian.org} [src:wordpress] wordpress:
4.0.1 security release
Marked as found in versions wordpress/3.6.1+dfsg-1~deb7u4.
Bug #770949 [src:wordpress] wordpress: Please update to fix security bug
Severity set to 'grave' from 'important'
Marked Bug as done
Marked as fixed in versions wordpress/4.0.1+dfsg-1.
Marked as found in versions wordpress/3.6.1+dfsg-1.
Added tag(s) upstream, security, and fixed-upstream.
Merged 770425 770949
thanks
Stopping processing here.
Please contact me if you need assistance.
--
770425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770425
770949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770327: update from gajim strace
merge 770942 770327
thanks
i just did a test run on artemis, where i logged into a console and had
`strace gajim` run.
the last lines before the BUG: were:
open(/proc/brcm_monitor0, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_Size=0, ...}) = 0
fstat(3, {st_mode=S_IFREG|0644, st_Size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x...
read(3, [ 268.089355] BUG: unable to handle kernel NULL pointer
dereference...
i have no idea why gajim would want to deal with a device-specific file,
but be it how it be, /proc/brcm_monitor0 is a reasonable culprit. given
what is described in #770327, i'm merging those bugs.
as a workaround, i've added a line
chmod 000 /proc/brcm_monitor0
to /etc/rc.local.
best regards
chrysn
signature.asc
Description: Digital signature
Processed: update from gajim strace
Processing commands for cont...@bugs.debian.org: merge 770942 770327 Bug #770942 [broadcom-sta-dkms] kernel panic from wlc_ioctl Bug #770942 [broadcom-sta-dkms] kernel panic from wlc_ioctl Added tag(s) upstream and security. Bug #770327 [broadcom-sta-dkms] non-root induced DoS via /proc/brcm_monitor0 Merged 770327 770942 thanks Stopping processing here. Please contact me if you need assistance. -- 770327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770327 770942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770941: marked as done (nova-common - Overrides database config in nova.conf)
Your message dated Tue, 25 Nov 2014 22:01:51 +0800 with message-id 54748bcf.5080...@debian.org and subject line Re: [PKG-Openstack-devel] Bug#770941: nova-common - Overrides database config in nova.conf has caused the Debian Bug report #770941, regarding nova-common - Overrides database config in nova.conf to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nova-common Version: 2014.1.3-6 Severity: serious A simple upgrade or re-install of nova-common overrides the database settings in nova.conf: | diff -ur nova/nova.conf /etc/nova/nova.conf | --- nova/nova.conf 2014-10-02 15:09:04.672855761 +0200 | +++ /etc/nova/nova.conf 2014-11-25 12:02:37.194997496 +0100 | @@ -349,7 +349,7 @@ | # DATABASE # | | [database] | -connection = postgresql:///nova | +connection = postgresql://novacommon:X@localhost/novadb | | | # This violates §10.7.3 of the Debian policy: local changes must be preserved. Bastian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On 11/25/2014 07:37 PM, Bastian Blank wrote: Package: nova-common Version: 2014.1.3-6 Severity: serious A simple upgrade or re-install of nova-common overrides the database settings in nova.conf: | diff -ur nova/nova.conf /etc/nova/nova.conf | --- nova/nova.conf 2014-10-02 15:09:04.672855761 +0200 | +++ /etc/nova/nova.conf 2014-11-25 12:02:37.194997496 +0100 | @@ -349,7 +349,7 @@ | # DATABASE # | | [database] | -connection = postgresql:///nova | +connection = postgresql://novacommon:X@localhost/novadb | | | # This violates §10.7.3 of the Debian policy: local changes must be preserved. Bastian Hi Bastian, Thanks for your bug report. However, unless I'm mistaking, the above connection = postgresql:///nova is *not* a valide DSN, so it's not surprising that it got replaced. I don't consider this a bug, especially that there's all the logic in place to read an actual valid configuration. Thomas---End Message---
Processed: Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware
Processing commands for cont...@bugs.debian.org: reassign 769072 src:nvidia-graphics-drivers Bug #769072 [libgl1-nvidia-glx] libgl1-nvidia-glx and xserver-xorg-core but no xserver-xorg-video-nvidia breaks OpenGL Bug reassigned from package 'libgl1-nvidia-glx' to 'src:nvidia-graphics-drivers'. Ignoring request to alter found versions of bug #769072 to the same values previously set Ignoring request to alter fixed versions of bug #769072 to the same values previously set reassign 769191 src:nvidia-graphics-drivers Bug #769191 [xorg] xorg: apt-get dist-upgrade somehow reconfigured my system to use the nvidia driver, even though I have no nvidia hardware Bug #769481 [xorg] [wine] The wine applications do not start Bug reassigned from package 'xorg' to 'src:nvidia-graphics-drivers'. Bug reassigned from package 'xorg' to 'src:nvidia-graphics-drivers'. No longer marked as found in versions xorg/1:7.7+7. No longer marked as found in versions xorg/1:7.7+7. Ignoring request to alter fixed versions of bug #769191 to the same values previously set Ignoring request to alter fixed versions of bug #769481 to the same values previously set reassign 770588 src:nvidia-graphics-drivers Bug #770588 [nvidia-driver] nvidia-driver automatically installed in eeepc with no nvidia card Bug reassigned from package 'nvidia-driver' to 'src:nvidia-graphics-drivers'. No longer marked as found in versions nvidia-graphics-drivers/340.46-4. Ignoring request to alter fixed versions of bug #770588 to the same values previously set forcemerge 769072 769191 770588 Bug #769072 [src:nvidia-graphics-drivers] libgl1-nvidia-glx and xserver-xorg-core but no xserver-xorg-video-nvidia breaks OpenGL Bug #769481 [src:nvidia-graphics-drivers] [wine] The wine applications do not start Severity set to 'important' from 'critical' Severity set to 'important' from 'critical' Bug #769191 [src:nvidia-graphics-drivers] xorg: apt-get dist-upgrade somehow reconfigured my system to use the nvidia driver, even though I have no nvidia hardware Bug #770588 [src:nvidia-graphics-drivers] nvidia-driver automatically installed in eeepc with no nvidia card Merged 769072 769191 769481 770588 severity 769072 critical Bug #769072 [src:nvidia-graphics-drivers] libgl1-nvidia-glx and xserver-xorg-core but no xserver-xorg-video-nvidia breaks OpenGL Bug #769191 [src:nvidia-graphics-drivers] xorg: apt-get dist-upgrade somehow reconfigured my system to use the nvidia driver, even though I have no nvidia hardware Bug #769481 [src:nvidia-graphics-drivers] [wine] The wine applications do not start Bug #770588 [src:nvidia-graphics-drivers] nvidia-driver automatically installed in eeepc with no nvidia card Severity set to 'critical' from 'important' Severity set to 'critical' from 'important' Severity set to 'critical' from 'important' Severity set to 'critical' from 'important' affects 769072 glx-diversions xorg gdm3 xserver-xorg Bug #769072 [src:nvidia-graphics-drivers] libgl1-nvidia-glx and xserver-xorg-core but no xserver-xorg-video-nvidia breaks OpenGL Bug #769191 [src:nvidia-graphics-drivers] xorg: apt-get dist-upgrade somehow reconfigured my system to use the nvidia driver, even though I have no nvidia hardware Bug #769481 [src:nvidia-graphics-drivers] [wine] The wine applications do not start Bug #770588 [src:nvidia-graphics-drivers] nvidia-driver automatically installed in eeepc with no nvidia card Added indication that 769072 affects glx-diversions, xorg, gdm3, and xserver-xorg Added indication that 769191 affects glx-diversions, xorg, gdm3, and xserver-xorg Added indication that 769481 affects glx-diversions, xorg, gdm3, and xserver-xorg Added indication that 770588 affects glx-diversions, xorg, gdm3, and xserver-xorg retitle 769072 Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #769072 [src:nvidia-graphics-drivers] libgl1-nvidia-glx and xserver-xorg-core but no xserver-xorg-video-nvidia breaks OpenGL Bug #769191 [src:nvidia-graphics-drivers] xorg: apt-get dist-upgrade somehow reconfigured my system to use the nvidia driver, even though I have no nvidia hardware Bug #769481 [src:nvidia-graphics-drivers] [wine] The wine applications do not start Bug #770588 [src:nvidia-graphics-drivers] nvidia-driver automatically installed in eeepc with no nvidia card Changed Bug title to 'Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware' from 'libgl1-nvidia-glx and xserver-xorg-core but no xserver-xorg-video-nvidia breaks OpenGL' Changed Bug title to 'Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware' from 'xorg: apt-get dist-upgrade somehow reconfigured my system to use the nvidia driver, even though I have no nvidia hardware' Changed Bug title to 'Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware' from '[wine] The wine applications do not start' Changed Bug title to 'Broken graphics due to libgl1-nvidia-glx auto-install on
Bug#770941: closed by Thomas Goirand z...@debian.org (Re: [PKG-Openstack-devel] Bug#770941: nova-common - Overrides database config in nova.conf)
Control: reopen -1 On Tue, Nov 25, 2014 at 02:03:06PM +, Debian Bug Tracking System wrote: However, unless I'm mistaking, the above connection = postgresql:///nova is *not* a valide DSN, so it's not surprising that it got replaced. I don't consider this a bug, especially that there's all the logic in place to read an actual valid configuration. It is a valid DSN. And even if not, it must not change it. Bastian -- Bastian Blank Berater Telefon: +49 2161 / 4643-194 E-Mail: bastian.bl...@credativ.de credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 Hohenzollernstr. 133, 41061 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#770941 closed by Thomas Goirand z...@debian.org (Re: [PKG-Openstack-devel] Bug#770941: nova-common - Overrides database config in nova.conf)
Processing control commands:
reopen -1
Bug #770941 {Done: Thomas Goirand z...@debian.org} [nova-common] nova-common
- Overrides database config in nova.conf
Bug reopened
Ignoring request to alter fixed versions of bug #770941 to the same values
previously set
--
770941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734599: libsnappy-java: Fails with FAILED_TO_LOAD_NATIVE_LIBRARY
snappy-java doesn't build its JNI bindings. SnappyNative.cpp should be compiled as a libsnappyjava.so shared library and installed in a libsnappy-java package. The missing maxCompressedLength method reported by Oliver is actually defined in SnappyNative.cpp. I'll prepare an update with these changes. Any objection to move the Git repository under pkg-java? Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#769419: Arch-dependent files in /usr
Processing control commands: severity -1 serious Bug #769419 [mate-notification-daemon] Arch-dependent files in /usr Severity set to 'serious' from 'important' -- 769419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#769417: Arch-dependent files in /usr/share
Processing control commands: severity -1 serious Bug #769417 [mate-netbook] Arch-dependent files in /usr/share Severity set to 'serious' from 'important' -- 769417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#769423: Arch-dependent files in /usr/share
Processing control commands: severity -1 serious Bug #769423 [mate-power-manager] Arch-dependent files in /usr/share Severity set to 'serious' from 'important' -- 769423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#769422: Arch-dependent files in /usr/share
Processing control commands: severity -1 serious Bug #769422 [mate-panel] Arch-dependent files in /usr/share Severity set to 'serious' from 'important' -- 769422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#769419: Arch-dependent files in /usr/share
Processing control commands: severity -1 serious Bug #769419 [mate-notification-daemon] Arch-dependent files in /usr Ignoring request to change severity of Bug 769419 to the same value. retitle -1 Arch-dependent files in /usr/share Bug #769419 [mate-notification-daemon] Arch-dependent files in /usr Changed Bug title to 'Arch-dependent files in /usr/share' from 'Arch-dependent files in /usr' -- 769419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#769418: Arch-dependent files in /usr/share
Processing control commands: severity -1 serious Bug #769418 [mate-gnome-main-menu-applet] Arch-dependent files in /usr/share Severity set to 'serious' from 'important' -- 769418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770962: X2Go Client: session profile dialog box too big
Package: x2goclient Version: 4.0.3.0-1 Severity: grave X-Debbugs-Cc: o.schney...@phoca-gmbh.de On smaller screens (1152x864 and below) or for people that run X11 sessions with high DPI values (a11y) it is impossible to properly edit X2Go Session profiles with X2Go Client. Reason: the Settings tab of the session profile dialog box got clobbered with too many (new) session settings. I already discussed this issue with upstream (Oleksandr Shneyder) and I am still waiting for a fixing commit to the upstream Git of X2Go Client. For X2Go Client it is essential that one can thoroughly edit the session profile's Settings tab, thus marking this issue as grave. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgp0YtfVsxJSE.pgp Description: Digitale PGP-Signatur
Bug#769419: Arch-dependent files in /usr/share
Control: severity -1 serious Control: retitle -1 Arch-dependent files in /usr/share On Do 13 Nov 2014 15:25:09 CET, Vangelis Mouhtsis wrote: Package: mate-notification-daemon Version: 1.8.1-1 Severity: important reported by Jakub Wilk with text: I found a number of arch!=all packages shipping /usr/share files that vary with architecture in a way indicating an FHS violation. DD-list of the affected binary packages is attached, and diff between i386 and s390x is here: https://people.debian.org/~jwilk/qa/20141101-usr-share.diff Please fix your packages. Thanks gnugr This is a FHS violoation, raising severity. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgphX8DEH8UVO.pgp Description: Digitale PGP-Signatur
Bug#770963: X2Go Client: desktop sharing broken
Package: x2goclient Version: 4.0.3.0-1 Severity: grave Tag: patch Recently in upstream we discovered that X2Go Client's desktop sharing feature is completely broken in 4.0.3.0 of X2Go Client (since the new clipboard mode feature got added). A fix is available upstream [1]. Mike [1] http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=b6d31bace19ea693486f5db7c76314bea071fb58 -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpkqmXU1lDph.pgp Description: Digitale PGP-Signatur
Bug#770965: phonon: Causes FTBS of subsurface on Hurd
Package: phonon Version: 4:4.8.0-3 Severity: critical Justification: breaks unrelated software Dear Maintainer, the dependencies of phonon cause subsurface to fail compiling on Hurd. This happens because there is no phonon-backend-vlc package on that arch. It can probably solved by adding an | phonon-backend-null. I have noticed that phonon depends on phonon-backend, but for some reason that is not being selected and the build is failing. Feel free to reassign to apt if you feel that the bug belongs there. Best. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.2d (SMP w/4 CPU cores; PREEMPT) 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 phonon depends on: ii debconf [debconf-2.0] 1.5.53 ii libphonon4 4:4.8.0-3 ii phonon-backend-gstreamer [phonon-backend] 4:4.8.0-3 ii phonon-backend-vlc [phonon-backend]1:0.8.1-dmo1 phonon recommends no packages. Versions of packages phonon suggests: ii phonon-backend-gstreamer 4:4.8.0-3 pn phonon-backend-mplayernone ii phonon-backend-vlc1:0.8.1-dmo1 -- debconf information: phonon-backend-null/isnt_functional: phonon-backend-null/isnt_functional_title: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: try again with better summary
Processing commands for cont...@bugs.debian.org: summary 769072 0 Summary replaced with message bug 769072 message 178 Summary replaced with message bug 769072 message 178 Summary replaced with message bug 769072 message 178 Summary replaced with message bug 769072 message 178 thanks Stopping processing here. Please contact me if you need assistance. -- 769072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769072 769191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769191 769481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769481 770588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769947: mate-terminal: Segfaults after update
Hi,
I just reinstalled a system today and managed to find the issue- I replace
marco with xmonad and that makes mate-terminal segfault.
I basically do:
dconf write /org/mate/desktop/session/required-components/windowmanager
'xmonad'
to do this.
So this is probably not RC by a long shot.
Thanks,
Álex
On Tue, Nov 25, 2014 at 1:53 PM, Mike Gabriel
mike.gabr...@das-netzwerkteam.de wrote:
Control: severity -1 grave
Control: tag -1 moreinfo
Hi all,
On Mo 17 Nov 2014 21:09:15 CET, Alex Corcoles wrote:
Package: mate-terminal
Version: 1.8.1+dfsg1-2
Severity: important
Hi,
After my latest apt-get upgrade, mate-terminal segfaults on start.
$ gdb mate-terminal
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
(gdb) run
Starting program: /usr/bin/mate-terminal [Thread debugging using
libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/
libthread_db.so.1.
Program received signal SIGSEGV, Segmentation fault.
get_initial_workspace () at terminal.c:539
539 terminal.c: No such file or directory.
(gdb) where
#0 get_initial_workspace () at terminal.c:539
#1 main (argc=1, argv=0x7fffe388) at terminal.c:645
(gdb) continue
Continuing.
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) where
No stack.
(gdb) quit
(I'm afraid my gdb skills are pretty much non-existent)
Cheers,
Alex
Raising severity to RC bug status for now. It would be good if either of
you (Alex, Ben) could provide more info on how you use mate-terminal
(locale, with MATE desktop, in some other X11 context, what theme, etc.).
As I personally can not reproduce this bug, I am unsure how to narrow down
its cause. Is there a way for me to reproduce this issue on a freshly
installed system? Any recipe that you can give?
Greets,
Mike
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-
netzwerkteam.de.xfb
--
___mail: alex at corcoles dot net
{~._.~} ICQ: 66791436
( Y )MSN: koalillo at fastmail dot fm
()~*~()Y!: koalillo
(_)-(_) http://alex.corcoles.net/
Processed (with 2 errors): Re: Bug#770477: mate-themes: dark themes make parts of libreoffice unreadable
Processing control commands: severity -1 grave Bug #770477 [mate-themes] mate-themes: dark themes make parts of libreoffice unreadable Severity set to 'grave' from 'minor' user -1 debian-accessibil...@lists.debian.org Unknown command or malformed arguments to command. usertags -1 a11y Unknown command or malformed arguments to command. -- 770477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770972: libksba: buffer overflow in ksba_oid_to_str
Source: libksba Version: 1.3.1-1 Severity: grave Tags: security upstream patch fixed-upstream Hi all, Today a new upstream release for Libksba was announced, addressing in particular the following: Impact of the security bug == By using special crafted S/MIME messages or ECC based OpenPGP data, it is possible to create a buffer overflow. The bug is not easy to exploit because there only 80 possible values which can be used to overwrite memory. However, a denial of service is possible and someone may come up with other clever attacks. Thus this should be fix. Affected versions: All Libksba versions 1.3.2 Background: Yesterday Hanno Böck found an invalid memory access in the 2.1 branch of GnuPG by conveying a malformed OID as part of an ECC key. It turned out that this bug has also been in libksba ever since and affects at least gpgsm and dirmngr. The code to convert an OID to its string representation has an obvious error of not considering an invalid encoding for arc-2. A first byte of 0x80 can be used to make a value of less then 80 and we then subtract 80 from it as required by the OID encoding rules. Due to the use of an unsigned integer this results in a pretty long value which won't fit anymore into the allocated buffer. The actual fix for lib Libksba is commit f715b9e. Announce: http://lists.gnupg.org/pipermail/gnupg-announce/2014q4/000359.html Upstream fix: http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libksba.git;a=commit;h=f715b9e156dfa99ae829fc694e5a0abd23ef97d7 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770330: [Android-tools-devel] Bug#770330: how to change UID_MIN, UID_MAX, FIRST_GID, LAST_GID, etc.?
On Tue, Nov 25, 2014 at 12:05 PM, Hans-Christoph Steiner h...@eds.org wrote: android-permissions integrates the Android permissions into a Debian chroot running on Android. This package should only ever run on a Debian chroot running with an Android kernel. It should modify things like GID_MAX or LAST_GID in /etc/login.defs and /etc/adduser.conf to reflect the hard-coded Android UIDs and GIDs, but it is a policy violation for a package to modify those files. Any suggestions as how to best tackle this issue? I need to investigate, but I think policy only forbids modification of the these files on a normal system. If you or the package create a chroot and modify these files in it, then it's normal if I ask me now. You can check if chrooted with the following code snippet (run as root): -- cut -- if [ $(stat -c %d:%i /) != $(stat -c %d:%i /proc/1/root/.) ]; then echo We are chrooted! else echo Business as usual fi -- cut -- I think if you run on an Android device, then 'getprop ro.build.version.release' should give you its version number, otherwise should be empty or getprop not even installed. These should help you, can't test it right now. Regards, Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766879: marked as done (Strange behaviour after update of python-caja in Debian (from 1.8.0-1/testing to 1.8.1-1/unstable))
Your message dated Tue, 25 Nov 2014 15:20:24 + with message-id e1xthui-0003dr...@franck.debian.org and subject line Bug#766879: fixed in python-caja 1.8.1-2 has caused the Debian Bug report #766879, regarding Strange behaviour after update of python-caja in Debian (from 1.8.0-1/testing to 1.8.1-1/unstable) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 766879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-caja Severity: grave Version: 1.8.1-1 Dear Debian developers! As you may know from GitHub (mate-desktop / caja / 322 https://github.com/mate-desktop/caja/issues/322) and from LP: #1170017 https://bugs.launchpad.net/bugs/1170017 I'm trying to port TortoiseHG extension from Nautilus to Caja (see comment 18 https://bugs.launchpad.net/ubuntu/+source/nautilus-python/+bug/1170017/comments/18 from the bug). I placed my python extension script in my BitBucket repository https://bitbucket.org/nrbrtx/caja-thg. For integration with Caja my script should be copied to ~/.local/share/caja-python/extensions/caja-thg.py after that Caja should be relaunched with caja -q. I tested it in Debian 8 (jessie/sid) with python-caja 1.8.0-1 - it works as expected (there are green star icon on a folder and TortoiseHG drop-down menus - see screenshot). But if install new python-caja 1.8.1-1 from unstable my extension does not work. My caja-thg.py is the same (unchanged), there are no errors in ~/.xsession-errors and manual launch of the script (with python ~/.local/share/caja-python/extensions/caja-thg.py) does not produce any errors. So I'm stuck. Could you please help me to determine the problem? With best regards, Norbert. ---End Message--- ---BeginMessage--- Source: python-caja Source-Version: 1.8.1-2 We believe that the bug you reported is fixed in the latest version of python-caja, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 766...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel sunwea...@debian.org (supplier of updated python-caja package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Nov 2014 14:51:43 +0100 Source: python-caja Binary: python-caja python-caja-dbg Architecture: source amd64 Version: 1.8.1-2 Distribution: unstable Urgency: medium Maintainer: MATE Packaging Team pkg-mate-t...@lists.alioth.debian.org Changed-By: Mike Gabriel sunwea...@debian.org Description: python-caja - Python binding for Caja components python-caja-dbg - Python binding for Caja components (debugging symbols) Closes: 766879 768819 768820 770927 Changes: python-caja (1.8.1-2) unstable; urgency=medium . [ Vangelis Mouhtsis ] * debian/control: + Fix typo in python-caja-dbg LONG_DESCRIPTION. (Closes: #768819, #768820). . [ Mike Gabriel ] * debian/patches: + Add 1002_dont-install-xsl-files.patch. Stop attempting to install XSL docbook source files into bin:package. (Closes: #770927). + Add 2001_debian-python-multiarch.patch. Enforce usage of multiarch path for PY_LIB_LOC. (Closes: 766879, LP: #1170017). * lintian: + Add overrides for debhelper's erroneously triggered makeshlibs script. Checksums-Sha1: 0ef9133083df660e97d519453326fd4d09e15068 2221 python-caja_1.8.1-2.dsc 39614bd338f913a811ce9f9c794de2d58cca2bbf 4060 python-caja_1.8.1-2.debian.tar.xz 5a13e5e8f4744ce74bed0b718399e0c69c6c2759 26394 python-caja_1.8.1-2_amd64.deb 2683c9b59374a2540bfb527cab3f0e129a9bf374 30614 python-caja-dbg_1.8.1-2_amd64.deb Checksums-Sha256: 6ccb0450719e23aa875f2c2570d91ad512e9e319e2b9c3d83ef48fe8a07af118 2221 python-caja_1.8.1-2.dsc d03bfdd7b1eb050d54dad975a539869b73fc62de658bfad063085238ad4121ea 4060 python-caja_1.8.1-2.debian.tar.xz 63ebc17079541b8d0b6602ba390d36186071b903bc13089b2b9a2836c1d31e58 26394 python-caja_1.8.1-2_amd64.deb 1e001a3a709a54236c21529c55478667ae40b152d8d278bcdddb5e4e8fa6be41 30614 python-caja-dbg_1.8.1-2_amd64.deb Files: 94463e5fdafe9c13df5eb5880cb0db78 2221 python optional python-caja_1.8.1-2.dsc 34b63cf2c41aa4b366f148b6679b7dee 4060 python optional
Processed: found 770434 in 4.3.0-1, found 770424 in 4.3.0-1
Processing commands for cont...@bugs.debian.org:
found 770434 4.3.0-1
Bug #770434 {Done: Romain Francoise rfranco...@debian.org} [tcpdump] tcpdump:
CVE-2014-8767: tcpdump denial of service in verbose mode using malformed OLSR
payload
Marked as found in versions tcpdump/4.3.0-1.
found 770424 4.3.0-1
Bug #770424 {Done: Romain Francoise rfranco...@debian.org} [tcpdump] tcpdump:
CVE-2014-8769: unreliable output using malformed AOVD payload
Marked as found in versions tcpdump/4.3.0-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
770424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770424
770434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769947: mate-terminal: Segfaults after update
Hi Alex, On Di 25 Nov 2014 15:55:31 CET, Alex Corcoles wrote: Hi, I just reinstalled a system today and managed to find the issue- I replace marco with xmonad and that makes mate-terminal segfault. I basically do: dconf write /org/mate/desktop/session/required-components/windowmanager 'xmonad' to do this. So this is probably not RC by a long shot. I just tested xmonad with MATE, following this configuration file: https://raw.githubusercontent.com/bsnux/xmonad-config/master/mate/xmonad.hs No problem whatsoever with a crashing MATE terminal (not crashing, that is). Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgppa3LNIkcKY.pgp Description: Digitale PGP-Signatur
Processed: found 770972 in 1.2.0-2
Processing commands for cont...@bugs.debian.org: found 770972 1.2.0-2 Bug #770972 [src:libksba] libksba: buffer overflow in ksba_oid_to_str Marked as found in versions libksba/1.2.0-2. thanks Stopping processing here. Please contact me if you need assistance. -- 770972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: pinentry-gtk2: icedove + enigmail + pinentry doesn't respond to keyboard input
Processing commands for cont...@bugs.debian.org: severity 750521 grave Bug #750521 [pinentry-gtk2] pinentry-gtk2: icedove + enigmail + pinentry doesn't respond to keyboard input Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 750521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734599: libsnappy-java: Fails with FAILED_TO_LOAD_NATIVE_LIBRARY
Le Tue Nov 25 2014 at 3:29:13 PM, Emmanuel Bourg ebo...@apache.org a écrit : snappy-java doesn't build its JNI bindings. SnappyNative.cpp should be compiled as a libsnappyjava.so shared library and installed in a libsnappy-java package. The missing maxCompressedLength method reported by Oliver is actually defined in SnappyNative.cpp. I'll prepare an update with these changes. Any objection to move the Git repository under pkg-java? for me this is fine, this package is not specific to our fields. Emmanuel Bourg
Processed: retitle 770944 to Overrides database config in nova.conf
Processing commands for cont...@bugs.debian.org: retitle 770944 Overrides database config in nova.conf Bug #770944 [neutron-common] nova-common - Overrides database config in nova.conf Changed Bug title to 'Overrides database config in nova.conf' from 'nova-common - Overrides database config in nova.conf' thanks Stopping processing here. Please contact me if you need assistance. -- 770944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770976: X2Go desktop sharing broken
Package: python-x2go Version: 0.5.0.1-1 Severity: grave X2Go desktop sharing is broken in Python X2Go 0.5.0.1 upstream. A fix is available upstream, as well [1]. Mike [1] http://code.x2go.org/gitweb?p=python-x2go.git;a=commitdiff;h=d5472a9ce4bbffd5c32248135452796ea4f9d0c1 -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976148 GnuPG Key ID 0x25771B13 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770978: pytest: Fails to build from source
Source: pytest
Version: 2.6.3-2
Severity: serious
Justification: fails to build from source
Dear Maintainer,
I was trying to do a rebuild of some of the packages in jessie, and
pytest fails the testsuite for python3.4 as far as I can tell.
I used debootstrap --variant=buildd to create a jessie chroot, then
installed the build-dep's of pytest and build-essential, and ran
dpkg-buildpackage, and the testsuite failed so the package did not build.
I believe this is the relevant bits from the build:
...
1093 passed, 23 skipped, 10 xfailed in 117.86 seconds =
+ PYTHONPATH=/root/pytest-2.6.3 python3.4 -m pytest testing
= test session starts ==
platform linux -- Python 3.4.2 -- py-1.4.25 -- pytest-2.6.3
collected 1126 items
testing/acceptance_test.py x...
testing/test_argcomplete.py ..
testing/test_assertinterpret.py ...ss..s
testing/test_assertion.py
testing/test_assertrewrite.py ...
testing/test_capture.py
...x..s.s...s.s..
testing/test_collection.py ...x.
testing/test_config.py xs...
testing/test_conftest.py
testing/test_core.py ..FF..
testing/test_doctest.py ..
testing/test_genscript.py s.s.ss.
testing/test_helpconfig.py
testing/test_junitxml.py
testing/test_mark.py ..x...x.
testing/test_monkeypatch.py .
testing/test_nose.py ...
testing/test_parseopt.py s
testing/test_pastebin.py ...
testing/test_pdb.py .s
testing/test_pytester.py x...
testing/test_recwarn.py
testing/test_resultlog.py ..
testing/test_runner.py ..sss.....x...
testing/test_runner_xunit.py .
testing/test_session.py
testing/test_skipping.py ...s.
testing/test_terminal.py
...s.s.
testing/test_tmpdir.py ...
testing/test_unittest.py ....
testing/cx_freeze/tests/test_doctest.txt .
testing/cx_freeze/tests/test_trivial.py ..
testing/python/collect.py
testing/python/fixture.py
...x..
testing/python/integration.py ...
testing/python/metafunc.py ...x
testing/python/raises.py .
=== FAILURES ===
___ TestBootstrapping.test_import_plugin_importname
self = test_core.TestBootstrapping object at 0xf64aa14c
testdir = TmpTestdir
local('/tmp/pytest-65/testdir/test_import_plugin_importname0')
def test_import_plugin_importname(self, testdir):
pluginmanager = PluginManager()
pytest.raises(ImportError, 'pluginmanager.import_plugin(qweqwex.y)')
pytest.raises(ImportError,
'pluginmanager.import_plugin(pytest_qweqwx.y)')
testdir.syspathinsert()
pluginname = pytest_hello
testdir.makepyfile(**{pluginname: })
pluginmanager.import_plugin(pytest_hello)
/root/pytest-2.6.3/testing/test_core.py:114:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/root/pytest-2.6.3/_pytest/core.py:222: in import_plugin
return self.import_plugin(modname[7:])
/root/pytest-2.6.3/_pytest/core.py:217: in import_plugin
mod = importplugin(modname)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
importspec = 'hello'
def importplugin(importspec):
name = importspec
try:
mod = _pytest. + name
__import__(mod)
return sys.modules[mod]
except ImportError:
__import__(importspec)
E ImportError: No module named 'hello'
/root/pytest-2.6.3/_pytest/core.py:275: ImportError
___ TestBootstrapping.test_import_plugin_dotted_name ___
self = test_core.TestBootstrapping object at 0xf649ce6c
testdir = TmpTestdir
local('/tmp/pytest-65/testdir/test_import_plugin_dotted_name0')
def test_import_plugin_dotted_name(self, testdir):
pluginmanager = PluginManager()
pytest.raises(ImportError, 'pluginmanager.import_plugin(qweqwex.y)')
pytest.raises(ImportError,
'pluginmanager.import_plugin(pytest_qweqwex.y)')
testdir.syspathinsert()
Bug#770977: pytest: Fails to build from source
Source: pytest
Version: 2.6.3-2
Severity: serious
Justification: fails to build from source
Dear Maintainer,
I was trying to do a rebuild of some of the packages in jessie, and
pytest fails the testsuite for python3.4 as far as I can tell.
I used debootstrap --variant=buildd to create a jessie chroot, then
installed the build-dep's of pytest and build-essential, and ran
dpkg-buildpackage, and the testsuite failed so the package did not build.
I believe this is the relevant bits from the build:
...snip...
1093 passed, 23 skipped, 10 xfailed in 117.86 seconds =
+ PYTHONPATH=/root/pytest-2.6.3 python3.4 -m pytest testing
= test session starts ==
platform linux -- Python 3.4.2 -- py-1.4.25 -- pytest-2.6.3
collected 1126 items
testing/acceptance_test.py x...
testing/test_argcomplete.py ..
testing/test_assertinterpret.py ...ss..s
testing/test_assertion.py
testing/test_assertrewrite.py ...
testing/test_capture.py
...x..s.s...s.s..
testing/test_collection.py ...x.
testing/test_config.py xs...
testing/test_conftest.py
testing/test_core.py ..FF..
testing/test_doctest.py ..
testing/test_genscript.py s.s.ss.
testing/test_helpconfig.py
testing/test_junitxml.py
testing/test_mark.py ..x...x.
testing/test_monkeypatch.py .
testing/test_nose.py ...
testing/test_parseopt.py s
testing/test_pastebin.py ...
testing/test_pdb.py .s
testing/test_pytester.py x...
testing/test_recwarn.py
testing/test_resultlog.py ..
testing/test_runner.py ..sss.....x...
testing/test_runner_xunit.py .
testing/test_session.py
testing/test_skipping.py ...s.
testing/test_terminal.py
...s.s.
testing/test_tmpdir.py ...
testing/test_unittest.py ....
testing/cx_freeze/tests/test_doctest.txt .
testing/cx_freeze/tests/test_trivial.py ..
testing/python/collect.py
testing/python/fixture.py
...x..
testing/python/integration.py ...
testing/python/metafunc.py ...x
testing/python/raises.py .
=== FAILURES ===
___ TestBootstrapping.test_import_plugin_importname
self = test_core.TestBootstrapping object at 0xf64aa14c
testdir = TmpTestdir
local('/tmp/pytest-65/testdir/test_import_plugin_importname0')
def test_import_plugin_importname(self, testdir):
pluginmanager = PluginManager()
pytest.raises(ImportError, 'pluginmanager.import_plugin(qweqwex.y)')
pytest.raises(ImportError,
'pluginmanager.import_plugin(pytest_qweqwx.y)')
testdir.syspathinsert()
pluginname = pytest_hello
testdir.makepyfile(**{pluginname: })
pluginmanager.import_plugin(pytest_hello)
/root/pytest-2.6.3/testing/test_core.py:114:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/root/pytest-2.6.3/_pytest/core.py:222: in import_plugin
return self.import_plugin(modname[7:])
/root/pytest-2.6.3/_pytest/core.py:217: in import_plugin
mod = importplugin(modname)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
importspec = 'hello'
def importplugin(importspec):
name = importspec
try:
mod = _pytest. + name
__import__(mod)
return sys.modules[mod]
except ImportError:
__import__(importspec)
E ImportError: No module named 'hello'
/root/pytest-2.6.3/_pytest/core.py:275: ImportError
___ TestBootstrapping.test_import_plugin_dotted_name ___
self = test_core.TestBootstrapping object at 0xf649ce6c
testdir = TmpTestdir
local('/tmp/pytest-65/testdir/test_import_plugin_dotted_name0')
def test_import_plugin_dotted_name(self, testdir):
pluginmanager = PluginManager()
pytest.raises(ImportError, 'pluginmanager.import_plugin(qweqwex.y)')
pytest.raises(ImportError,
'pluginmanager.import_plugin(pytest_qweqwex.y)')
testdir.syspathinsert()
Processed: Merge accidental duplicate bug
Processing commands for cont...@bugs.debian.org: merge 770977 770978 Bug #770977 [src:pytest] pytest: Fails to build from source Bug #770978 [src:pytest] pytest: Fails to build from source Merged 770977 770978 thank you Stopping processing here. Please contact me if you need assistance. -- 770977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770977 770978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 734599
Processing commands for cont...@bugs.debian.org: tags 734599 + pending Bug #734599 [libsnappy-java] libsnappy-java: Fails with FAILED_TO_LOAD_NATIVE_LIBRARY Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 734599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770982: libwebcam0-dev: dynctrl-logitech.h is missing in libwebcam0-dev
Package: libwebcam0-dev Version: 0.2.4-1 Severity: grave Justification: renders package unusable Dear Maintainer, I needed to include webcam.h, however during the compilation, the following error occured: --- /usr/include/webcam.h:32:30: fatal error: dynctrl-logitech.h: No such file or directory #include dynctrl-logitech.h ^ compilation terminated. --- A quick search using apt-file shows that no debian package contains that particular header file. This bug is quite bad, as anything that include webcam.h cannot be compiled. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libwebcam0-dev depends on: ii libwebcam0 0.2.4-1 libwebcam0-dev recommends no packages. libwebcam0-dev suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770972: libksba: buffer overflow in ksba_oid_to_str
Hi
Attached both debdiffs for wheezy-security and unstable using the
upstream patch.
Regards,
Salvatore
diff -Nru libksba-1.2.0/debian/changelog libksba-1.2.0/debian/changelog
--- libksba-1.2.0/debian/changelog 2011-06-19 14:03:02.0 +0200
+++ libksba-1.2.0/debian/changelog 2014-11-25 16:49:50.0 +0100
@@ -1,3 +1,11 @@
+libksba (1.2.0-2+deb7u1) wheezy-security; urgency=high
+
+ * Non-maintainer upload by the Security Team.
+ * Add 0001-Fix-buffer-overflow-in-ksba_oid_to_str.patch patch.
+Fix buffer overflow in ksba_oid_to_str. (Closes: #770972)
+
+ -- Salvatore Bonaccorso car...@debian.org Tue, 25 Nov 2014 16:43:46 +0100
+
libksba (1.2.0-2) unstable; urgency=low
* Build for multi-arch.
diff -Nru
libksba-1.2.0/debian/patches/0001-Fix-buffer-overflow-in-ksba_oid_to_str.patch
libksba-1.2.0/debian/patches/0001-Fix-buffer-overflow-in-ksba_oid_to_str.patch
---
libksba-1.2.0/debian/patches/0001-Fix-buffer-overflow-in-ksba_oid_to_str.patch
1970-01-01 01:00:00.0 +0100
+++
libksba-1.2.0/debian/patches/0001-Fix-buffer-overflow-in-ksba_oid_to_str.patch
2014-11-25 16:49:50.0 +0100
@@ -0,0 +1,209 @@
+Description: Fix buffer overflow in ksba_oid_to_str
+ The code has an obvious error by not considering invalid encoding for
+ arc-2. A first byte of 0x80 can be used to make a value of less then
+ 80 and we then subtract 80 from that value as required by the OID
+ encoding rules. Due to the unsigned integer this results in a pretty
+ long value which won't fit anymore into the allocated buffer.
+ .
+ The fix is obvious. Also added a few simple test cases. Note that we
+ keep on using sprintf instead of snprintf because managing the
+ remaining length of the buffer would probably be more error prone than
+ assuring that the buffer is large enough. Getting rid of sprintf
+ altogether by using direct conversion along with membuf_t like code
+ might be possible.
+Origin: backport,
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libksba.git;a=commit;h=f715b9e156dfa99ae829fc694e5a0abd23ef97d7
+Bug-Debian: https://bugs.debian.org/770972
+Forwarded: not-needed
+Author: Salvatore Bonaccorso car...@debian.org
+Last-Update: 2014-11-25
+Applied-Upstream: 1.3.2
+
+--- a/tests/t-dnparser.c
b/tests/t-dnparser.c
+@@ -144,7 +144,7 @@ main (int argc, char **argv)
+ if (!feof (stdin))
+ fail (read error or input too large);
+
+- fail (no yet implemented);
++ fail (not yet implemented);
+
+ }
+ else if (argc == 2 !strcmp (argv[1], --to-der) )
+--- a/tests/t-oid.c
b/tests/t-oid.c
+@@ -27,6 +27,9 @@
+
+ #include ../src/ksba.h
+
++#define PGM t-oid
++#define BADOID 1.3.6.1.4.1.11591.2.12242973
++
+
+ static void *
+ read_into_buffer (FILE *fp, size_t *r_length)
+@@ -68,23 +71,104 @@ read_into_buffer (FILE *fp, size_t *r_le
+ }
+
+
++static void
++test_oid_to_str (void)
++{
++ struct {
++unsigned int binlen;
++unsigned char *bin;
++char *str;
++ } tests[] = {
++
++{ 7, \x02\x82\x06\x01\x0A\x0C\x00,
++ 0.2.262.1.10.12.0
++},
++{ 7, \x02\x82\x06\x01\x0A\x0C\x01,
++ 0.2.262.1.10.12.1
++},
++{ 7, \x2A\x86\x48\xCE\x38\x04\x01,
++ 1.2.840.10040.4.1
++},
++{ 7, \x2A\x86\x48\xCE\x38\x04\x03,
++ 1.2.840.10040.4.3
++},
++{ 10, \x2B\x06\x01\x04\x01\xDA\x47\x02\x01\x01,
++ 1.3.6.1.4.1.11591.2.1.1
++},
++{ 3, \x55\x1D\x0E,
++ 2.5.29.14
++},
++{ 9, \x80\x02\x70\x50\x25\x46\xfd\x0c\xc0,
++ BADOID
++},
++{ 1, \x80,
++ BADOID
++},
++{ 2, \x81\x00,
++ 2.48
++},
++{ 2, \x81\x01,
++ 2.49
++},
++{ 2, \x81\x7f,
++ 2.175
++},
++{ 2, \x81\x80, /* legal encoding? */
++ 2.48
++},
++{ 2, \x81\x81\x01, /* legal encoding? */
++ 2.49
++},
++{ 0, ,
++
++},
++
++{ 0, NULL, NULL }
++ };
++ int tidx;
++ char *str;
++
++ for (tidx=0; tests[tidx].bin; tidx++)
++{
++ str = ksba_oid_to_str (tests[tidx].bin, tests[tidx].binlen);
++ if (!str)
++{
++ perror (ksba_oid_to_str failed);
++ exit (1);
++}
++ if (strcmp (tests[tidx].str, str))
++{
++ fprintf (stderr, ksba_oid_to_str test %d failed\n, tidx);
++ fprintf (stderr, got=%s\n, str);
++ fprintf (stderr, want=%s\n, tests[tidx].str);
++ exit (1);
++}
++}
++}
++
+
+ int
+ main (int argc, char **argv)
+ {
+ gpg_error_t err;
++
+ if (argc)
+ {
+ argc--;
+ argv++;
+ }
+
+- if (argc)
++
++ if (!argc)
++{
++ test_oid_to_str ();
++}
++ else if (!strcmp (*argv, --from-str))
+ {
+ unsigned char *buffer;
+ size_t n, buflen;
+
+- for ( ;argc ; argc--, argv++)
++ for (argv++,argc-- ; argc; argc--, argv++)
+ {
+ err = ksba_oid_from_str (*argv, buffer, buflen);
+ if (err)
+@@ -100,18 +184,25 @@ main
Bug#759919: marked as done (ruby-bootstrap-sass: FTBFS: ERROR: Test ruby2.1 failed: /usr/lib/ruby/2.1.0/test/unit.rb:676:in `class:Runner': undefined method `_run_suite' for class `Test::Unit::Run
Your message dated Tue, 25 Nov 2014 18:20:02 + with message-id e1xtkiy-mb...@franck.debian.org and subject line Bug#759919: fixed in ruby-bootstrap-sass 2.3.1.0-5 has caused the Debian Bug report #759919, regarding ruby-bootstrap-sass: FTBFS: ERROR: Test ruby2.1 failed: /usr/lib/ruby/2.1.0/test/unit.rb:676:in `class:Runner': undefined method `_run_suite' for class `Test::Unit::Runner' (NameError) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 759919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-bootstrap-sass Version: 2.3.1.0-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): /usr/lib/ruby/2.1.0/test/unit.rb:676:in `class:Runner': undefined method `_run_suite' for class `Test::Unit::Runner' (NameError) from /usr/lib/ruby/2.1.0/test/unit.rb:261:in `module:Unit' from /usr/lib/ruby/2.1.0/test/unit.rb:15:in `module:Test' from /usr/lib/ruby/2.1.0/test/unit.rb:7:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /«PKGBUILDDIR»/test/test_helper.rb:3:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /«PKGBUILDDIR»/test/compilation_test.rb:1:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in main' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `main' rake aborted! Command failed with status (1): [ruby -Ilib:test -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/compilation_test.rb ] -e:1:in `main' Tasks: TOP = default = test (See full trace by running task with --trace) ERROR: Test ruby2.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/ruby-bootstrap-sass_2.3.1.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. The build was done with DEB_BUILD_OPTIONS=parallel=4, so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. ---End Message--- ---BeginMessage--- Source: ruby-bootstrap-sass Source-Version: 2.3.1.0-5 We believe that the bug you reported is fixed in the latest version of ruby-bootstrap-sass, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 759...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen prav...@debian.org (supplier of updated ruby-bootstrap-sass package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Nov 2014 23:31:58 +0530 Source: ruby-bootstrap-sass Binary: ruby-bootstrap-sass compass-bootstrap-sass-plugin Architecture: source all Version: 2.3.1.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Pirate Praveen prav...@debian.org Description: compass-bootstrap-sass-plugin - Compass plugin implementing Twitter's Bootstrap ruby-bootstrap-sass - Twitter's Bootstrap, converted to Sass Closes: 739783 759919 Changes: ruby-bootstrap-sass (2.3.1.0-5) unstable; urgency=medium .
Bug#768695: Bug #768695: statsmodels: FTBFS in jessie: ImportError: cannot import name DateRange
On 25/11/14 10:57, Michael Banck wrote: On Sun, Nov 23, 2014 at 07:13:07PM +0100, Michael Banck wrote: Hi have uploaded the attached debdiff targetted at testing-proposed-updates to DELAYED/3-day. See also the pre-approval/unblock bug for relesae.debian.org, #770730. Unfortunately, it FTBFS on i386 still, there are a couple of test suite failures: https://buildd.debian.org/status/fetch.php?pkg=statsmodelsarch=i386ver=0.4.2-1.1stamp=1416885423 Michael Oh no. This is a bit weird, though - these failures are only due to some precision problems. One would think that operations on i386 and amd64 would follow IEEE 754 and give the same result. The testsuite is really, really fragile! I'll take a look later today. Cheers, Tomasz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 770762
Processing commands for cont...@bugs.debian.org: tags 770762 + pending Bug #770762 [src:libinline-java-perl] libinline-java-perl: Build dependencies are too loose Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 770762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 770845
Processing commands for cont...@bugs.debian.org: tags 770845 + pending Bug #770845 [src:libinline-java-perl] [libinline-java-perl] FTBFS: Assumes a decimal point during the tests Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 770845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 770844
Processing commands for cont...@bugs.debian.org: tags 770844 + pending Bug #770844 [src:libinline-java-perl] [libinline-java-perl] FTBFS twice in a row Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 770844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769337: marked as done (mysql-5.5: version in jessie/sid lower than in wheezy-security)
Your message dated Tue, 25 Nov 2014 18:49:20 + with message-id e1xtlau-0004cs...@franck.debian.org and subject line Bug#769337: fixed in mysql-5.5 5.5.40-1 has caused the Debian Bug report #769337, regarding mysql-5.5: version in jessie/sid lower than in wheezy-security to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mysql-5.5 Version: 5.5.39-1 Severity: serious The mysql-5.5 version in jessie/sid is lower than in wheezy, meaning that people upgrading from wheezy will still use the wheezy version, while people installing jessie will get a version with security bugs. Therefore, please upload mysql version 5.5.40 to unstable. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: mysql-5.5 Source-Version: 5.5.40-1 We believe that the bug you reported is fixed in the latest version of mysql-5.5, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Page james.p...@ubuntu.com (supplier of updated mysql-5.5 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Nov 2014 16:31:57 + Source: mysql-5.5 Binary: libmysqlclient18 libmysqld-pic libmysqld-dev libmysqlclient-dev mysql-common mysql-client-5.5 mysql-server-core-5.5 mysql-server-5.5 mysql-server mysql-client mysql-testsuite mysql-testsuite-5.5 mysql-source-5.5 Architecture: source all amd64 Version: 5.5.40-1 Distribution: unstable Urgency: medium Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org Changed-By: James Page james.p...@ubuntu.com Description: libmysqlclient-dev - MySQL database development files libmysqlclient18 - MySQL database client library libmysqld-dev - MySQL embedded database development files libmysqld-pic - PIC version of MySQL embedded server development files mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.5 - MySQL database client binaries mysql-common - MySQL database common files, e.g. /etc/mysql/my.cnf mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.5 - MySQL database server binaries and system database setup mysql-server-core-5.5 - MySQL database server binaries mysql-source-5.5 - MySQL source mysql-testsuite - MySQL testsuite mysql-testsuite-5.5 - MySQL testsuite Closes: 765663 769337 Changes: mysql-5.5 (5.5.40-1) unstable; urgency=medium . * SECURITY UPDATE: Update to 5.5.40 to fix security issues: - http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html - CVE-2012-5615, CVE-2014-4274, CVE-2014-4287, CVE-2014-6463, CVE-2014-6464, CVE-2014-6469, CVE-2014-6478, CVE-2014-6484, CVE-2014-6491, CVE-2014-6494, CVE-2014-6495, CVE-2014-6496, CVE-2014-6500, CVE-2014-6505, CVE-2014-6507, CVE-2014-6520, CVE-2014-6530, CVE-2014-6551, CVE-2014-6555, CVE-2014-6559 (Closes: #765663, #769337) * d/p/fix-mysqlhotcopy-test-failure.patch: Add return code 255 to the list of allowable return codes for mysqlhotcopy tests. * d/rules: Enable parallel builds. Checksums-Sha1: e83d506983071c4e4b4a191ce9bdbffbe6cfc319 3065 mysql-5.5_5.5.40-1.dsc b93a1b14ab2de390014e99b4293e7835da133196 21727672 mysql-5.5_5.5.40.orig.tar.gz edd9b0fe2b260620cdab76ae3811fb369e9635ce 231548 mysql-5.5_5.5.40-1.debian.tar.xz 05e601930e4f94f59f3657908950f13e076f9e00 76294 mysql-common_5.5.40-1_all.deb 102f2bcf8f7ae544f759aac9dd50df107d417409 74540 mysql-server_5.5.40-1_all.deb 2b18784934bd356ab343cff31b850893a216f389 74420 mysql-client_5.5.40-1_all.deb 71f122f3ade79858aec5e15a028f22579d6b57c5 74386 mysql-testsuite_5.5.40-1_all.deb
Bug#765663: marked as done (mysql-5.5: Multiple security fixes from October 2014 CPU)
Your message dated Tue, 25 Nov 2014 18:49:19 + with message-id e1xtlat-0004cm...@franck.debian.org and subject line Bug#765663: fixed in mysql-5.5 5.5.40-1 has caused the Debian Bug report #765663, regarding mysql-5.5: Multiple security fixes from October 2014 CPU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 765663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mysql-5.5 Version: 5.5.23-2 Severity: grave Tags: security upstream fixed-upstream Hi Please see: http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html#AppendixMSQL Regards, Salvatore ---End Message--- ---BeginMessage--- Source: mysql-5.5 Source-Version: 5.5.40-1 We believe that the bug you reported is fixed in the latest version of mysql-5.5, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Page james.p...@ubuntu.com (supplier of updated mysql-5.5 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Nov 2014 16:31:57 + Source: mysql-5.5 Binary: libmysqlclient18 libmysqld-pic libmysqld-dev libmysqlclient-dev mysql-common mysql-client-5.5 mysql-server-core-5.5 mysql-server-5.5 mysql-server mysql-client mysql-testsuite mysql-testsuite-5.5 mysql-source-5.5 Architecture: source all amd64 Version: 5.5.40-1 Distribution: unstable Urgency: medium Maintainer: Debian MySQL Maintainers pkg-mysql-ma...@lists.alioth.debian.org Changed-By: James Page james.p...@ubuntu.com Description: libmysqlclient-dev - MySQL database development files libmysqlclient18 - MySQL database client library libmysqld-dev - MySQL embedded database development files libmysqld-pic - PIC version of MySQL embedded server development files mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.5 - MySQL database client binaries mysql-common - MySQL database common files, e.g. /etc/mysql/my.cnf mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.5 - MySQL database server binaries and system database setup mysql-server-core-5.5 - MySQL database server binaries mysql-source-5.5 - MySQL source mysql-testsuite - MySQL testsuite mysql-testsuite-5.5 - MySQL testsuite Closes: 765663 769337 Changes: mysql-5.5 (5.5.40-1) unstable; urgency=medium . * SECURITY UPDATE: Update to 5.5.40 to fix security issues: - http://www.oracle.com/technetwork/topics/security/cpuoct2014-1972960.html - CVE-2012-5615, CVE-2014-4274, CVE-2014-4287, CVE-2014-6463, CVE-2014-6464, CVE-2014-6469, CVE-2014-6478, CVE-2014-6484, CVE-2014-6491, CVE-2014-6494, CVE-2014-6495, CVE-2014-6496, CVE-2014-6500, CVE-2014-6505, CVE-2014-6507, CVE-2014-6520, CVE-2014-6530, CVE-2014-6551, CVE-2014-6555, CVE-2014-6559 (Closes: #765663, #769337) * d/p/fix-mysqlhotcopy-test-failure.patch: Add return code 255 to the list of allowable return codes for mysqlhotcopy tests. * d/rules: Enable parallel builds. Checksums-Sha1: e83d506983071c4e4b4a191ce9bdbffbe6cfc319 3065 mysql-5.5_5.5.40-1.dsc b93a1b14ab2de390014e99b4293e7835da133196 21727672 mysql-5.5_5.5.40.orig.tar.gz edd9b0fe2b260620cdab76ae3811fb369e9635ce 231548 mysql-5.5_5.5.40-1.debian.tar.xz 05e601930e4f94f59f3657908950f13e076f9e00 76294 mysql-common_5.5.40-1_all.deb 102f2bcf8f7ae544f759aac9dd50df107d417409 74540 mysql-server_5.5.40-1_all.deb 2b18784934bd356ab343cff31b850893a216f389 74420 mysql-client_5.5.40-1_all.deb 71f122f3ade79858aec5e15a028f22579d6b57c5 74386 mysql-testsuite_5.5.40-1_all.deb 3ccc09ae0cf4760b284324d06083994a80cc70ae 668914 libmysqlclient18_5.5.40-1_amd64.deb 4b000ad053b19b5de93fff0dc46a94a8bfec3eed 3258578 libmysqld-pic_5.5.40-1_amd64.deb c5c6c972b47f9c333bafe66191da99aea96ffb6f 3257224 libmysqld-dev_5.5.40-1_amd64.deb 1772d228c20a398cc4955be7971b9ce8634b4c1a 945808 libmysqlclient-dev_5.5.40-1_amd64.deb 856dcf1c48acbd83abed4efd4209dfa0ecdb4c15 1819300 mysql-client-5.5_5.5.40-1_amd64.deb
Bug#770965: phonon: Causes FTBS of subsurface on Hurd
On Tue, 25 Nov 2014 15:50:44 +0100 Salvo Tomaselli tipos...@tiscali.it wrote: Package: phonon Version: 4:4.8.0-3 Severity: critical Not on a release arch, so not RC. Adjusting severity accordingly. Scott K signature.asc Description: This is a digitally signed message part.
Processed: severity of 770965 is normal
Processing commands for cont...@bugs.debian.org: severity 770965 normal Bug #770965 [phonon] phonon: Causes FTBS of subsurface on Hurd Severity set to 'normal' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 770965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769214: dmtcp: FTBFS in jessie: test failures
On Wed, 12 Nov 2014 08:52:42 +0100, Lucas Nussbaum wrote: == Tests == ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp3 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp4 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp5 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsyscall-tester ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDfile1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcpaware1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDplugin-sleep2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDplugin-example-db ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDgettimeofday ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsigchild ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDshared-fd ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDstale-fd ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpoll ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDforkexec ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDwaitpid ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDclient-server ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDfrisbee ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDshared-memory ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-shm1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-shm2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-sem ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsysv-msg ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDposix-mq1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDposix-mq2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpty2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDtimer ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDclock ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdlopen1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread3 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread4 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpthread5 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDgzip ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDperl ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpython ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDbash ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdash ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDscript ckpt: FAILED script root-pids: [23184] msg: checkpoint error, 4 expected, 0 found, running=0 Trying once again ckpt: FAILED openmp-1 root-pids: [23208] msg: checkpoint error, 4 expected, 0 found, running=0 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDopenmp-2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSED == Summary == ip-172-31-15-17: 42 of 43 tests passed make: *** [build-stamp] Error 1 The tests fail for me as well, but even earlier: == Tests == ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp3 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp4 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcp5 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsyscall-tester ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDfile1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDdmtcpaware1 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDplugin-sleep2 ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDplugin-example-db ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDgettimeofday ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDsigchild ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDshared-fd ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDstale-fd ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDpoll ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDforkexec ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDwaitpid ckpt:PASSED rstr:PASSED; ckpt:PASSED rstr:PASSEDclient-server ckpt:PASSED rstr:FAILED (first process exited: oldstatus 99) retry: Trying to kill old coordinator, and launch new one on same port FAILED client-server root-pids: [8817] msg: restart error, 2 expected, 1 found, running=0 Trying to kill old coordinator, and launch new one on same port Trying once again ckpt:PASSED rstr:FAILED (first process exited: oldstatus 99) retry: Trying to kill old coordinator, and launch new one on same port FAILED frisbeeroot-pids: [11034] msg: restart error, 2 expected, 1 found, running=0 Trying to kill old coordinator, and launch new one on same port ckpt:PASSED rstr:FAILED (first
Bug#770972: marked as done (libksba: buffer overflow in ksba_oid_to_str)
Your message dated Tue, 25 Nov 2014 19:19:37 + with message-id e1xtled-00080t...@franck.debian.org and subject line Bug#770972: fixed in libksba 1.3.2-1 has caused the Debian Bug report #770972, regarding libksba: buffer overflow in ksba_oid_to_str to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libksba Version: 1.3.1-1 Severity: grave Tags: security upstream patch fixed-upstream Hi all, Today a new upstream release for Libksba was announced, addressing in particular the following: Impact of the security bug == By using special crafted S/MIME messages or ECC based OpenPGP data, it is possible to create a buffer overflow. The bug is not easy to exploit because there only 80 possible values which can be used to overwrite memory. However, a denial of service is possible and someone may come up with other clever attacks. Thus this should be fix. Affected versions: All Libksba versions 1.3.2 Background: Yesterday Hanno Böck found an invalid memory access in the 2.1 branch of GnuPG by conveying a malformed OID as part of an ECC key. It turned out that this bug has also been in libksba ever since and affects at least gpgsm and dirmngr. The code to convert an OID to its string representation has an obvious error of not considering an invalid encoding for arc-2. A first byte of 0x80 can be used to make a value of less then 80 and we then subtract 80 from it as required by the OID encoding rules. Due to the use of an unsigned integer this results in a pretty long value which won't fit anymore into the allocated buffer. The actual fix for lib Libksba is commit f715b9e. Announce: http://lists.gnupg.org/pipermail/gnupg-announce/2014q4/000359.html Upstream fix: http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libksba.git;a=commit;h=f715b9e156dfa99ae829fc694e5a0abd23ef97d7 Regards, Salvatore ---End Message--- ---BeginMessage--- Source: libksba Source-Version: 1.3.2-1 We believe that the bug you reported is fixed in the latest version of libksba, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler ametz...@debian.org (supplier of updated libksba package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Nov 2014 20:05:54 +0100 Source: libksba Binary: libksba-dev libksba8 Architecture: source i386 Version: 1.3.2-1 Distribution: unstable Urgency: high Maintainer: Debian GnuTLS Maintainers pkg-gnutls-ma...@lists.alioth.debian.org Changed-By: Andreas Metzler ametz...@debian.org Description: libksba-dev - X.509 and CMS support library - development files libksba8 - X.509 and CMS support library Closes: 770972 Changes: libksba (1.3.2-1) unstable; urgency=high . * New upstream security release, fixing a buffer overflow in ksba_oid_to_str in Libksba. Closes: #770972 Checksums-Sha1: d5165f6d4f8ca8a5d88b655b007c3557f3fa903b 2127 libksba_1.3.2-1.dsc 37d0893a587354af2b6e49f6ae701ca84f52da67 600952 libksba_1.3.2.orig.tar.bz2 bba5d33ba9dfb59840b67505cc0177fa131e07b8 11324 libksba_1.3.2-1.debian.tar.xz 914d767238659833f977bbcac284c7a019845c90 133742 libksba-dev_1.3.2-1_i386.deb 18d4f801c3e709b272a9b4996b8c0bcbc6e69a13 101922 libksba8_1.3.2-1_i386.deb Checksums-Sha256: 811e285985f02c50d021796114bbf9bd7eeef1526da4a9d29f1d5217bfa22d9b 2127 libksba_1.3.2-1.dsc eb95537955dfc2845690a4cc3836074fa6d0a2c2ca2cbf1759364d3bd9868406 600952 libksba_1.3.2.orig.tar.bz2 dc774944eb5dd0fab3799846cfcea50284360dcc6056c547c96005ff7ecae88b 11324 libksba_1.3.2-1.debian.tar.xz 43125f48f365ee0021d6a3c12a956fdfa0d0456353de29cbaf46546934839dff 133742 libksba-dev_1.3.2-1_i386.deb 5fa7d0ed41b2e914426eebb7ead1c08752a07d2c7f7a7653db2704768ed60bc6 101922 libksba8_1.3.2-1_i386.deb Files: cd604ad5bc8aeb4e974a342e184c25f3 2127 libs optional libksba_1.3.2-1.dsc c3c9a66e22d87fe3ae59865250b8a09c 600952 libs optional libksba_1.3.2.orig.tar.bz2 e0dc4e60eb83a4c46dc64d3f4b8da1e6 11324 libs optional
Processed: raise severity, policy violation
Processing control commands: severity -1 serious Bug #760676 [mate-icon-theme-faenza] mate-icon-theme-faenza: Icon theme is illegal/in conflict with it's license Severity set to 'serious' from 'important' -- 760676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
Hi Axel, restarting dbus kills any graphical user session. On 11/25/2014 11:58 AM, Axel Beckert wrote: recently, it happened twice that needrestart killed my X session which was started by wdm and is running the awesome window manager via ~/.Xsession. sorry :-( I don't think it's the new upload but rather the recent dbus updates. I can't exactly remember if the second-last case was at the time when dbus was updated (and if so, needrestart would have been at version 1.2-4), but the case today definitely had a dbus update included. According to the logs it also restarted systemd itself. This happens if needrestart detects systemd using outdated libs. needrestart suggests to run `systemctl daemon-reexec` if it detects that pid 1 uses outdated binaries (if systemd was detected). in the (used) default config, systemd restarted dbus: Are you able to kill your X session by calling `systemctl daemon-reexec` manually? Nov 25 11:18:57 c-cactus systemd[1]: Reexecuting. Nov 25 11:18:57 c-cactus systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR) Nov 25 11:18:57 c-cactus systemd[1]: Detected architecture 'x86-64'. Nov 25 11:18:57 c-cactus systemd[1]: Started ACPI event daemon. Nov 25 11:18:57 c-cactus systemd[1]: Mounted /var. Nov 25 11:18:57 c-cactus systemd[1]: Mounted /home. Nov 25 11:18:57 c-cactus systemd[1]: Mounted /boot. Nov 25 11:18:57 c-cactus systemd[1]: Mounted /. Nov 25 11:18:57 c-cactus systemd[1]: Started File System Check on /dev/disk/by-uuid/…. […] Nov 25 11:18:57 c-cactus systemd[1]: Activated swap /dev/…/swap. At this point `systemctl reexec` should have been finished. Nov 25 11:18:57 c-cactus systemd[1]: Stopping Accounts Service... Nov 25 11:18:57 c-cactus systemd[1]: Stopping Avahi mDNS/DNS-SD Stack... Nov 25 11:18:57 c-cactus systemd[1]: Stopping Bluetooth service... Nov 25 11:18:57 c-cactus systemd[1]: Stopping Regular background program processing daemon... Nov 25 11:18:57 c-cactus systemd[1]: Starting Regular background program processing daemon... Nov 25 11:18:57 c-cactus systemd[1]: Started Regular background program processing daemon. Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus... Nov 25 11:18:57 c-cactus systemd[1]: Starting Accounts Service... Nov 25 11:18:57 c-cactus systemd[1]: Starting Bluetooth service... Nov 25 11:18:57 c-cactus systemd[1]: Stopping OpenBSD Secure Shell server... Nov 25 11:18:57 c-cactus systemd[1]: Stopping Journal Service... Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Default. Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Default. Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Basic System. Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Basic System. Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Paths. Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Paths. Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Timers. Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Timers. Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Sockets. Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Sockets. Nov 25 11:18:57 c-cactus systemd[1641]: Starting Shutdown. Nov 25 11:18:57 c-cactus systemd[1641]: Reached target Shutdown. Nov 25 11:18:57 c-cactus systemd[1641]: Starting Exit the Session... Nov 25 11:18:57 c-cactus systemd[1]: Starting OpenBSD Secure Shell server... Nov 25 11:18:57 c-cactus systemd[1]: Started OpenBSD Secure Shell server. Nov 25 11:18:57 c-cactus systemd[1641]: Received SIGRTMIN+24 from PID 12082 (kill). Nov 25 11:18:57 c-cactus systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. Nov 25 11:18:57 c-cactus systemd[1]: Starting Daemon for power management... Nov 25 11:18:57 c-cactus systemd[1]: Starting LSB: Starts and stops Wicd... Nov 25 11:18:57 c-cactus systemd[1]: Starting D-Bus System Message Bus... Nov 25 11:18:57 c-cactus systemd[1]: Started D-Bus System Message Bus. Nov 25 11:18:57 c-cactus systemd[1]: Started Bluetooth service. Nov 25 11:18:57 c-cactus systemd[1]: Starting Hostname Service... Nov 25 11:18:57 c-cactus systemd[1]: Started Accounts Service. Nov 25 11:18:57 c-cactus systemd[1]: Started Daemon for power management. Nov 25 11:18:57 c-cactus systemd[1]: Starting User Manager for UID 1000... Nov 25 11:18:57 c-cactus systemd[1]: Starting Login Service... Nov 25 11:18:57 c-cactus systemd[1]: Started Hostname Service. Nov 25 11:18:57 c-cactus systemd[1]: Started Login Service. Nov 25 11:18:57 c-cactus systemd[1]: Started User Manager for UID 1000. Nov 25 11:18:58 c-cactus systemd[1]: Starting Session c1 of user abe. Nov 25 11:18:58 c-cactus systemd[1]: Started Session c1 of user abe. Nov 25 11:18:59 c-cactus systemd[1]: Starting LSB: start or stop the WINGs display manager... Nov 25 11:18:59 c-cactus systemd[1]: Started LSB: start or stop the WINGs display manager. Nov 25 11:18:59 c-cactus systemd[1]: Starting X11 Display Manager. Nov 25
Bug#769947: mate-terminal: Segfaults after update
More or less, doing some trial and error I discovered that using
desktopConfig instead of defaultConfig fixes magically the problem.
https://github.com/alexpdp7/xmonad.pdp7/commit/037a44a8f7541fb3983ade528e34b4cfa0ea81a5
. I suppose there's some bug somewhere, but I'm happy for now- don't know
if Ben Whyall has the same problem or not.
--
___mail: alex at corcoles dot net
{~._.~} ICQ: 66791436
( Y )MSN: koalillo at fastmail dot fm
()~*~()Y!: koalillo
(_)-(_) http://alex.corcoles.net/
Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
Hi Thomas,
Thomas Liske wrote:
restarting dbus kills any graphical user session.
I wouldn't say that. But it's probably true for most modern desktop
environments and systemd -- unfortunately.
in the (used) default config, systemd restarted dbus:
Are you able to kill your X session by calling `systemctl
daemon-reexec` manually?
Nope, can still work in that session. :-)
Nov 25 11:18:57 c-cactus systemd[1]: Activated swap /dev/…/swap.
At this point `systemctl reexec` should have been finished.
That's also where the log ended after the manual systemctl
daemon-reexec.
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Accounts Service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Bluetooth service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Regular background program
processing daemon...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Regular background program
processing daemon...
Nov 25 11:18:57 c-cactus systemd[1]: Started Regular background program
processing daemon.
Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Accounts Service...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Bluetooth service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping OpenBSD Secure Shell server...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Journal Service...
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Default.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Default.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Basic System.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Basic System.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Paths.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Paths.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Timers.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Timers.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Sockets.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Sockets.
Nov 25 11:18:57 c-cactus systemd[1641]: Starting Shutdown.
Nov 25 11:18:57 c-cactus systemd[1641]: Reached target Shutdown.
Nov 25 11:18:57 c-cactus systemd[1641]: Starting Exit the Session...
Nov 25 11:18:57 c-cactus systemd[1]: Starting OpenBSD Secure Shell server...
Nov 25 11:18:57 c-cactus systemd[1]: Started OpenBSD Secure Shell server.
Nov 25 11:18:57 c-cactus systemd[1641]: Received SIGRTMIN+24 from PID 12082
(kill).
Nov 25 11:18:57 c-cactus systemd[1]: Started Trigger Flushing of Journal to
Persistent Storage.
Nov 25 11:18:57 c-cactus systemd[1]: Starting Daemon for power management...
Nov 25 11:18:57 c-cactus systemd[1]: Starting LSB: Starts and stops Wicd...
Nov 25 11:18:57 c-cactus systemd[1]: Starting D-Bus System Message Bus...
Nov 25 11:18:57 c-cactus systemd[1]: Started D-Bus System Message Bus.
Nov 25 11:18:57 c-cactus systemd[1]: Started Bluetooth service.
Nov 25 11:18:57 c-cactus systemd[1]: Starting Hostname Service...
Nov 25 11:18:57 c-cactus systemd[1]: Started Accounts Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started Daemon for power management.
Nov 25 11:18:57 c-cactus systemd[1]: Starting User Manager for UID 1000...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Login Service...
Nov 25 11:18:57 c-cactus systemd[1]: Started Hostname Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started Login Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started User Manager for UID 1000.
Nov 25 11:18:58 c-cactus systemd[1]: Starting Session c1 of user abe.
Nov 25 11:18:58 c-cactus systemd[1]: Started Session c1 of user abe.
Nov 25 11:18:59 c-cactus systemd[1]: Starting LSB: start or stop the WINGs
display manager...
Nov 25 11:18:59 c-cactus systemd[1]: Started LSB: start or stop the WINGs
display manager.
Nov 25 11:18:59 c-cactus systemd[1]: Starting X11 Display Manager.
Nov 25 11:18:59 c-cactus systemd[1]: Reached target X11 Display Manager.
It might be an dependency issue... X11 Display Manager depends on
something that needrestart did suggest to restart.
Compared to modern login managers, wdm's dependencies are rather lightweight:
Depends: libc6 (= 2.11), libpam0g (= 0.99.7.1), libselinux1 (=
1.32), libwings2 (= 0.95.0), libwraster3 (= 0.95.0), libwutil2 (=
0.95.0), libx11-6, libxau6, libxdmcp6, libxinerama1, libxmu6, debconf
(= 1.5.20) | debconf-2.0, libpam-runtime (= 0.76-13.1),
libpam-modules, psmisc, x11-apps, x11-common, x11-xserver-utils,
x11-utils
Are you able to remember which service were selected?
Not at all, because I had set $nrconf{restart} = 'a' and systemd
doesn't care to tell me what it does -- compared to needrestart on a
system with good old sysvinit. Meh.
If you did not run needrestart in the meanwhile you might find your
selection still in debconf:
$ grep -A 8 'needrestart/ui-query_pkgs$' /var/cache/debconf/config.dat
This looks very suspicious:
→ grep -A 8 'needrestart/ui-query_pkgs$'
Bug#767653:
Hi Jochen built uploaded! Please apply for the unblock. (Note that I s/UNRELEASED/unstable in d/changelog; make sure to do this to in your repository) -- tobi Am Dienstag, den 25.11.2014, 12:21 +0100 schrieb Jochen Sprickerhof: Hi Tobi, thanks for the clearifications, I've pushed a new version. Can you have a look again? Cheers Jochen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
