Bug#747471: libnss: Arbitrary key size limitation for client certificate authenticaton causing out-of-memory error
Source: iceweasel Severity: critical Tags: security upstream When using client certificate authentication with client certificates with keys of 4097 bit RSA or larger you always get a diagnostic from the SSL layer saying that no memory was available which is funny because usinga key of the same size for the SSL server works just fine. Also using a 4095 bit RSA client certificate works just fine as well. This breaks security in system where such keys are used and thus should be considered serious misbehaviour as cryptographic systems MUST NOT include an arbitrary limits on the key size of used cryptographic parameters. Please either remove this restriction completely or raise this to a much more sane value that is not limitting casually-paranoid configurations which use keys like 8192 Bit RSA for client authentication. A suggested increase could be 65536 Bit RSA, but better remove this limitation completely as it causes no real benefit. Furthermore RSA 8192 and up to RSA 16384 has to be considered as it corresponds roughly to 192-256 bit symmetric key sizes and thus properly configured systems enforcing 256 bit symmetric cryptography will also enforce asymmetric keys larger than 4096 bit for RSA or similarly for DSA and ECDSA. Kind regards, Benny Baumann -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (750, 'experimental'), (700, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/8 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
Bug#747453: Arbitrary key size limitations causing hard-to-diagnose problems when establishing a connection
On Fri, May 09, 2014 at 03:32:25AM +0200, Wilfried Klaebe wrote: Kurt Roeckx wrote: I don't see how the severity of this is critical. The severity level critical is defined as: makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. https://www.debian.org/Bugs/Developer Exactly. This bug makes unrelated software on the system break (e.g. ejabberd, no communication was possible until _both_ sides had the supplied patch applied), ejabberd is not unrelated since it makes use of openssl. It's also not totally broken that it can't be used, communication can be done under normal conditions. and also could introduce security holes, as clients might fall back to unencrypted communication. You can argue that this is a security hole or not. I see no reason to use such large keys in the first place. Kurt -- 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 747453 is important
Processing commands for cont...@bugs.debian.org: severity 747453 important Bug #747453 [src:openssl] Arbitrary key size limitations causing hard-to-diagnose problems when establishing a connection Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 747453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747453 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 747471 is important
Processing commands for cont...@bugs.debian.org: severity 747471 important Bug #747471 [src:iceweasel] libnss: Arbitrary key size limitation for client certificate authenticaton causing out-of-memory error Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 747471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747471 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#747442: [Aptitude-devel] Bug#747442: aptitude: progs run by aptitude (apt-listbugs, how-can-I-help block apt when they crash
On 9 May 2014 02:08, Stephen McGregor x...@stephen-mcgregor.com wrote: Package: aptitude Version: 0.6.10 Severity: grave Justification: renders package unusable Dear Maintainer, the specific situation: - [ already filed as #747406 against ruby] -a ruby corruption is crashing both apt-listbugs AND how-can-I-help - thus aptitude returns a failure and does NOT install the desired packages - the apt system is now completely broken: these packages can not be removed and no others can be installed. - apt-get is also affected and no longer works. the general case --- important - any program run by aptitude (such as apt-listbugs or how-can-I-help) that crashes will break the apt system. - this is a critical bug: any type of failure in sub-programs should have NO effect on aptitude. Not a bug, this is the intended and documented behaviour [1]. These hook programs are permitted to prevent an install action from proceeding by returning failure. In this case, the hook programs themselves fail to run, but it can not be assumed that it is the administrators wishes to proceed anyway. For example if the purpose of having apt-listbugs installed is to prevent buggy packages from being installed, that purpose _would_ be defeated. Do you trust to install packages without that program screening them first? If so, you can inform apt of this decision by removing the bothersome lines from apt.conf. [1] From apt.conf(5): Pre-Install-Pkgs This is a list of shell commands to run before invoking dpkg(1). Like options this must be specified in list notation. The commands are invoked in order using /bin/sh; *should any fail APT will abort*. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747397: policykit-1 forces using systemd and may break systems with sysvinit after update
Le Thu, 08 May 2014 20:30:02 +0400, Boris Pek tehnic...@yandex.ru a écrit : Hi, As explained on #747105 policykit-1 only depends against libpam-systemd which in turns depends against systemd-sysv | systemd-shim. But systemd package will be installed in any case. Not a big problem though... logind daemon is in the systemd package If you don't want to use systemd as PID1 you can install systemd-shim. Ok. But if I understand correctly policykit will be limited in functionality in this case. Which its functions will be lost? As long as you have a logind session registred, everything should work the same. Also please in the future report bugs about actual breakage not hypothetical ones, thanks. Sorry, but I am a very cautious during updating system, especially when some changes may do my system unbootable. Maybe I will find time to check this update in VirtualBox later. Thanks! Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747008: marked as done (probabel: FTBFS on mipsel (+ probably on alpha and on x32))
Your message dated Fri, 09 May 2014 07:34:25 + with message-id e1wifk5-0005hg...@franck.debian.org and subject line Bug#747008: fixed in probabel 0.4.3-2 has caused the Debian Bug report #747008, regarding probabel: FTBFS on mipsel (+ probably on alpha and on x32) 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.) -- 747008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: probabel Version: 0.4.3-1 Severity: serious Justification: fails to build from source (but built successfully in the past) From version 0.4.2-2 to version 0.4.3-1, probabel changed the architecture list from: | Architecture: any to | Architecture: amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 | mipsel alpha x32 This is not mentionned in the changelog and thus we don't know the reason. In addition multi-line fields are not supported in debian/control and thus the package fails to build on at least mipsel, but probably also on alpha and x32. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: mipsel (mips64) Kernel: Linux 3.2.0-4-5kc-malta Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Source: probabel Source-Version: 0.4.3-2 We believe that the bug you reported is fixed in the latest version of probabel, 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 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille ti...@debian.org (supplier of updated probabel 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: Fri, 09 May 2014 09:18:53 +0200 Source: probabel Binary: probabel probabel-examples Architecture: source amd64 all Version: 0.4.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: probabel - Toolset for Genome-Wide Association Analysis probabel-examples - Example files for ProbABEL Closes: 747008 Changes: probabel (0.4.3-2) unstable; urgency=medium . * Fix architecture field Closes: #747008 Checksums-Sha1: 8dc30a7cc45fc8bb9d3f7e94cb5f506e7dd46478 2289 probabel_0.4.3-2.dsc 7222948319eb0f5719e01eaf442c96637f94303c 6068 probabel_0.4.3-2.debian.tar.xz c734c340e27b6274a5ee59cff6d5b6f6f6afd12a 524388 probabel_0.4.3-2_amd64.deb a5b8051fbba5ede6c4f3dc9a7fe7b4780c5c2785 1604820 probabel-examples_0.4.3-2_all.deb Checksums-Sha256: 3deb50c29076d9f52679f6f56fa6381ab731d672b7ea9644b5fe9d221cf86b12 2289 probabel_0.4.3-2.dsc 6259101132622b37e390d53bd9f210c5ae4b3c9b439886eafb706a897bb7dbd2 6068 probabel_0.4.3-2.debian.tar.xz c6ce9071163c1121a96fbb1693669e81bdc3bf5ed21c06f16c21fc061480fa94 524388 probabel_0.4.3-2_amd64.deb 559cac2063b5638595844eeb00bcf75746a8cab6293e9fad8994c8ecfb68f60c 1604820 probabel-examples_0.4.3-2_all.deb Files: 8a7fd49313677941d34f20f037562ce6 524388 science optional probabel_0.4.3-2_amd64.deb b8869656f351c1d96c0d8adb7acf92ff 1604820 science optional probabel-examples_0.4.3-2_all.deb 9fedea3cb72b59e9d59f7aaa57c0240a 2289 science optional probabel_0.4.3-2.dsc e88f6470073e231403ddb5c613e1ebf6 6068 science optional probabel_0.4.3-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTbILNAAoJEFeKBJTRxkbRShkP/iV0zOxdUR4R04oZV1/BG3cO AoIWCLpcr5Pdy1PwEFhB3jDTYtNb1hkjHihfBeL/4jCCfRxX2zarAP7+OQiZ7EOk dYLEkryc9LOd8+nWr/qsG48dCoXH4/M2hjAsb+x7Pi/hdvX8IZe4SBLagfaN2yzT eGJcc/io+Sl4nojsPhS4lx1d+dgdwWddgibY6EBzC/nzc6btQKNyrS4tb2dZkVAy NM124CIZkuZBNowjlcgZt2itgejyUz0bF4UPJ9mKLmx9JG4VU/T/HUb/fkIPEnaC lYkC1wOYrd3imVc/7Bg/OCgRQVTBmqSvjDR6PEGSes59FH6tjJzWN13R0EioIQjo iNwRp3T7mj/RG/uPnnP3ZUp0jcwEuB5cWEPOUkzgdkbrpet1SnAqsFZa9FLxn6Vo I617tFlRqB77u3SKSCkv79oAlvzOxismyYnhELof0DCMsKMdWFB/G9dr9WHwxv8G UbDSMPIkMjCKeyOdP1IM/0KVbA+O4Qn/FiYrTJC/N6VufUiIYMJkhfZKEK7VSAqn Hah96mXHLGPnGTBfdKYRe7vaitC5nz9rXKHDHlSFU9vYB6jnIhKkWXdfkbACz2/0
Bug#746989: marked as done (FTBFS: chmod: cannot access '/«PKGBUILDDIR»/debian/autodock-test/usr/share/autodock/Tests/*': No such file or directory)
Your message dated Fri, 09 May 2014 07:48:28 + with message-id e1wifxg-0006lq...@franck.debian.org and subject line Bug#746989: fixed in autodocksuite 4.2.5.1-5 has caused the Debian Bug report #746989, regarding FTBFS: chmod: cannot access '/«PKGBUILDDIR»/debian/autodock-test/usr/share/autodock/Tests/*': No such file or directory 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.) -- 746989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: autodocksuite Version: 4.2.5.1-4 Severity: serious Justification: fails to build from source (but built successfully in the past) autodocksuite fails to build from source on all architectures: |dh_install -a |dh_installdocs -a |debian/rules override_dh_installchangelogs | make[1]: Entering directory `/«PKGBUILDDIR»' | dh_installchangelogs autodock/RELEASENOTES | make[1]: Leaving directory `/«PKGBUILDDIR»' |dh_installman -a |dh_lintian -a |dh_perl -a |dh_link -a |dh_compress -a |debian/rules override_dh_fixperms | make[1]: Entering directory `/«PKGBUILDDIR»' | dh_fixperms | chmod 644 /«PKGBUILDDIR»/debian/autodock-test/usr/share/autodock/Tests/* | chmod: cannot access '/«PKGBUILDDIR»/debian/autodock-test/usr/share/autodock/Tests/*': No such file or directory | make[1]: *** [override_dh_fixperms] Error 1 | make[1]: Leaving directory `/«PKGBUILDDIR»' | make: *** [binary-arch] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 A full build log can be found on buildd.debian.org, for example: https://buildd.debian.org/status/fetch.php?pkg=autodocksuitearch=i386ver=4.2.5.1-4stamp=1397669372 -- 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.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Source: autodocksuite Source-Version: 4.2.5.1-5 We believe that the bug you reported is fixed in the latest version of autodocksuite, 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. Andreas Tille ti...@debian.org (supplier of updated autodocksuite 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: Fri, 09 May 2014 09:22:50 +0200 Source: autodocksuite Binary: autodock autogrid autodock-test autogrid-test autodock-getdata Architecture: source amd64 all Version: 4.2.5.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: autodock - analysis of ligand binding to protein structure autodock-getdata - instructions for getData to collect compounds autodock-test - test files for AutoDock autogrid - pre-calculate binding of ligands to their receptor autogrid-test - test files for AutoGrid Closes: 746989 Changes: autodocksuite (4.2.5.1-5) unstable; urgency=medium . * Enable arch only builds Closes: #746989 Checksums-Sha1: 354213befa022f11b2ef452eacbfb005b3e956fd 2389 autodocksuite_4.2.5.1-5.dsc 211df5cf36166991e81480971c2694f6ab733c2a 17292 autodocksuite_4.2.5.1-5.debian.tar.xz 3c4b90067066b0ec2bdff4f3017f79f44e5e0825 180970 autodock_4.2.5.1-5_amd64.deb 682ee4a85d9d07cec40ab02868dd920fd7a4311b 49862 autogrid_4.2.5.1-5_amd64.deb 61d3bf41a5bb8f5093bbf3b6de57cde0a72a5dad 3208158 autodock-test_4.2.5.1-5_all.deb caec7059befe11c057b137b4e8f78975c62721a4 66706 autogrid-test_4.2.5.1-5_all.deb e2bedb5c16924910332f656011ef9df0b77cd9ce 16836 autodock-getdata_4.2.5.1-5_all.deb Checksums-Sha256: dd83b31e23f96e65a782e5ef01361f9f8699c56a08bbbd87f47b93a84a328e16 2389 autodocksuite_4.2.5.1-5.dsc 179521a68c5eed0412a3bd6ba5cf88c75a2541b8b63e2aa645841c9f57783f0f 17292 autodocksuite_4.2.5.1-5.debian.tar.xz 2cf3bd61cf5fe5cc0de0d3b7fee09efd75eca72d7b81962e63cd34ab607ea57c 180970
Bug#747397: policykit-1 forces using systemd and may break systems with sysvinit after update
Hi, If you don't want to use systemd as PID1 you can install systemd-shim. Ok. But if I understand correctly policykit will be limited in functionality in this case. Which its functions will be lost? As long as you have a logind session registred, everything should work the same. Great! Thank you for clarification. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746577: closed by Michael Biebl bi...@debian.org (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)
]] Zack Weinberg On 05/06/2014 08:08 AM, Tollef Fog Heen wrote: ]] Zack Weinberg On Mon, May 5, 2014 at 5:40 PM, Tollef Fog Heen tfh...@err.no wrote: ]] Zack Weinberg Fundamentally what I want is a bulletproof procedure for reverting to sysvinit in case something goes wrong. Sounds like you're arguing that sysvinit-core should no longer ship /sbin/init, then, so systemd-sysv doesn't have to conflict with it. Wouldn't that make the sysvinit implementation of /sbin/init completely unavailable? This is an earnest question. I do not have access to package contents right now. No, to revert you'd boot with init=/sbin/sysvinit. Ah, I understand now. Yes, this + systemd-sysv and upstart *also* stop shipping /sbin/init (it becomes a symlink under control of the administrator) + documentation would be a satisfactory conclusion as far as I'm concerned. If we were to also move 'reboot' and friends to a shared utilities package, that might make the systemd-sysv package unnecessary. I don't see any reason for the symlink being removed from systemd-sysv. After all, if you don't want that symlink, just use systemd, not -sysv. If you for some reason insist on having systemd-sysv installed, but /sbin/init pointing to something else, there's always dpkg-divert. I can't find any non-contrived reason to do that, though. Ideally, also, if systemd is installed on a system that is currently running sysvinit, that doesn't change what /sbin/init points to; the administrator has to do that as a separate operation. That is how it is today. If you want to change /sbin/init, you install systemd-sysv. I'm quite ok with what we're doing now: if you're installing something that depends on systemd-sysv | systemd-shim, you get the new default (systemd). If you don't like the new default, you get to take positive action to select what you would like to use instead. [...] I have still not seen any reason whatsoever for this to be a command rather than just changing a configuration file. I have no problem with that. I suggested a command because I thought the switch might be more complicated than just changing what /sbin/init is symlinked to, but right now it looks to me like that should be enough. Ok, good, then we're in agreement about that at least. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745901: cogl fglrx incompatibility bug
Hi, this bug was now reported as #722161 against cogl #745901 against fglrx-driver #744152 against gdm3 I posted a workaround to #745901 [1]. The bugs should be merged and linked to the affected packages with affects but I'm not sure if the bug is in cogl or fglrx. It should probably be fixed in cogl. Best, Tobias [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745901#41 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745901: fglrx-driver: fglrx update crashes totem, gdm, gnome-session and anything that uses clutter
Hello, I am experiencing the same issue. Please see xorg.log attached and following gdm3 logs. Package: fglrx-driver Version: 1:14.4-2 Package: gdm3 Version: 3.8.4-7 Package: libclutter-1.0-0 Version: 1.18.2-1 Package: libclutter-gtk-1.0.0 Version: 1.5.2-2 # cat /var/log/gdm3/:0-greeter.log gnome-session[2814]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary (gnome-shell:3461): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed (gnome-shell:3461): Clutter-CRITICAL **: Unable to initialize Clutter: The OpenGL version could not be determined Erreur du gestionnaire de fenêtres : Unable to initialize Clutter. # cat /var/log/gdm3/:0-slave.log gdm-simple-slave[1997]: Failed to give slave programs access to the display. Trying to proceed. gdm-launch-environment][2724]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) gdm-launch-environment][2724]: pam_ck_connector(gdm-launch-environment:session): nox11 mode, ignoring PAM_TTY :0 Thank you, Benjamin. X.Org X Server 1.15.1 Release Date: 2014-04-13 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.13-1-amd64 x86_64 Debian Current Operating System: Linux Larbin-1 3.14-1-amd64 #1 SMP Debian 3.14.2-1 (2014-04-28) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-1-amd64 root=UUID=32a08883-6f56-40db-b1f6-dee9c0bb796e ro quiet Build Date: 15 April 2014 06:58:36PM xorg-server 2:1.15.1-1 (http://www.debian.org/support) Current version of pixman: 0.32.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri May 9 09:52:45 2014 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (==) ServerLayout aticonfig Layout (**) |--Screen aticonfig-Screen[0]-0 (0) (**) | |--Monitor aticonfig-Monitor[0]-0 (**) | |--Device aticonfig-Device[0]-0 (==) Automatically adding devices (==) Automatically enabling devices (==) Automatically adding GPU devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (--) PCI:*(0:5:0:0) 1002:6759:1787:2308 rev 0, Mem @ 0xd000/268435456, 0xfeac/131072, I/O @ 0xd000/256, BIOS @ 0x/131072 Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension Present Initializing built-in extension DRI3 Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension XFree86-VidModeExtension Initializing built-in extension XFree86-DGA Initializing built-in extension XFree86-DRI Initializing built-in extension DRI2 (II) glx will be loaded by default. (II) Loading /usr/lib/xorg/modules/linux/libglx.so (II) Module glx: vendor=Advanced Micro Devices, Inc. compiled for 6.9.0, module version = 1.0.0 Loading extension GLX (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so (II) Module fglrx: vendor=FireGL - AMD Technologies Inc. compiled for 1.4.99.906, module version = 14.10.2 (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so (II) Module fglrxdrm: vendor=FireGL - AMD Technologies Inc. compiled for 1.4.99.906, module version = 14.10.2 (II) AMD Proprietary Linux Driver Version Identifier:14.10.2 (II) AMD Proprietary Linux Driver Release Identifier: 14.10.1006
Bug#747108: Reproduce
Hi Mathieu, could you please let me know how to reproduce the bug? jar xf /usr/share/java/vtk6.jar echo $? 0 I am not an expert in java, sorry for stupid question. Thanks Anton -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746373: marked as done (ruby-moneta: build on i386 doesn't terminate)
Your message dated Fri, 09 May 2014 09:20:52 +
with message-id e1wigz6-tp...@franck.debian.org
and subject line Bug#746373: fixed in ruby-moneta 0.7.20-2
has caused the Debian Bug report #746373,
regarding ruby-moneta: build on i386 doesn't terminate
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.)
--
746373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: ruby-moneta
Version: 0.7.20-1
Severity: serious
Tags: sid jessie
At least when building on i386, the build doesn't terminate after finishining.
I assume this is reproducible (I did see it first on the Ubuntu buildds, then on
a current i386 sid with a local build).
so the build log ends with:
[...]
## MONETA TESTSUITE SUCCEDED ##
generating gemspec at ${target}
Leaving dh_ruby --install
dh_installdocs -O--buildsystem=ruby
dh_installchangelogs -O--buildsystem=ruby
dh_perl -O--buildsystem=ruby
dh_link -O--buildsystem=ruby
dh_compress -X.rb -O--buildsystem=ruby
dh_fixperms -O--buildsystem=ruby
dh_installdeb -O--buildsystem=ruby
dh_gencontrol -O--buildsystem=ruby
dpkg-gencontrol: warning: Depends field of package ruby-moneta: unknown
substitution variable ${shlibs:Depends}
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is
not NFS-safe
dh_md5sums -O--buildsystem=ruby
dh_builddeb -O--buildsystem=ruby
dpkg-deb: warning: 'debian/ruby-moneta/DEBIAN/control' contains user-defined
field 'Ruby-Versions'
dpkg-deb: warning: ignoring 1 warning about the control file(s)
dpkg-deb: building package `ruby-moneta' in `../ruby-moneta_0.7.20-1_all.deb'.
dpkg-genchanges -b ../ruby-moneta_0.7.20-1_i386.changes
dpkg-genchanges: binary-only upload - not including any source code
dpkg-source --after-build ruby-moneta-0.7.20
signfile ruby-moneta_0.7.20-1_i386.changes
dpkg-buildpackage: binary-only upload (no source included)
gpg: skipped Jérémy Bobbio lu...@debian.org: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
dpkg-buildpackage: error: failed to sign .changes file
end then hangs. two mysqld processes are still running:
doko 24063 1.6 0.2 218776 42552 pts/9Sl+ 10:47 1:21
/usr/sbin/mysqld --no-defaults --user=mysql --bind-address=127.0.0.1 --port=3495
--socket=/tmp/moneta20140429-23533-s0zg29/mysql.sock
--datadir=/tmp/moneta20140429-23533-s0zg29
doko 4027 0.8 0.2 218680 42596 pts/9Sl+ 09:29 1:24
/usr/sbin/mysqld --no-defaults --user=mysql --bind-address=127.0.0.1 --port=3444
--socket=/tmp/moneta20140429-3963-1jvgm9p/mysql.sock
--datadir=/tmp/moneta20140429-3963-1jvgm9p
---End Message---
---BeginMessage---
Source: ruby-moneta
Source-Version: 0.7.20-2
We believe that the bug you reported is fixed in the latest version of
ruby-moneta, 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.
Jérémy Bobbio lu...@debian.org (supplier of updated ruby-moneta 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: Fri, 09 May 2014 09:51:19 +0200
Source: ruby-moneta
Binary: ruby-moneta
Architecture: source all
Version: 0.7.20-2
Distribution: unstable
Urgency: low
Maintainer: Joshua Timberman jos...@opscode.com
Changed-By: Jérémy Bobbio lu...@debian.org
Description:
ruby-moneta - Ruby interface to multiple key/value stores
Closes: 746373
Changes:
ruby-moneta (0.7.20-2) unstable; urgency=low
.
* Be more aggressive when shutting down MySQL test instances.
(Closes: #746373)
Checksums-Sha1:
d674f2be7c6f50c5917dbd315497af91ab58e83c 2287 ruby-moneta_0.7.20-2.dsc
f2b238d01db883895ffdb3778a9a405c788582fe 11000
ruby-moneta_0.7.20-2.debian.tar.xz
7160e90835da9eaae20dbeb99eeb28661960ccff 33888 ruby-moneta_0.7.20-2_all.deb
Checksums-Sha256:
8080f3f8f3afca3359f5f6543bfaf7f88096a195d8830f33a65b857b125ad5fc 2287
ruby-moneta_0.7.20-2.dsc
554d7704999d96a62200fc38a583b66af3ae182453307e63c7e05a4ae916a85a 11000
ruby-moneta_0.7.20-2.debian.tar.xz
243f4b263c986da56e61d82dc63664e1a92e0ec23a25ae64bb4dd86f1913d8d0 33888
Bug#747108: Reproduce
On Fri, May 9, 2014 at 11:21 AM, Anton Gladky gl...@debian.org wrote: Hi Mathieu, could you please let me know how to reproduce the bug? Sure: https://bugs.debian.org/747108#32 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744152: cogl fglrx incompatibility bug
Hi, On 2014-05-09 11:01:14 +0200, Tobias Hansen wrote: this bug was now reported as #722161 against cogl #745901 against fglrx-driver #744152 against gdm3 I posted a workaround to #745901 [1]. The bugs should be merged and linked to the affected packages with affects but I'm not sure if the bug is in cogl or fglrx. It should probably be fixed in cogl. FYI, I don't see any problem with gdm3 3.8.4-6, but I don't have any fglrx package installed. So, if the bug is in cogl, it appears only in some combination with other packages (fglrx...). Note that the problem I was seeing is entirely new in gdm3 3.8.4-7 (X server not always starting + sometimes graphic corruption in gdm3 when it can start). -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717131: marked as done (minidlna: CVE-2013-2745 CVE-2013-2738 CVE-2013-2739)
Your message dated Fri, 09 May 2014 11:04:31 + with message-id e1wiibp-0005du...@franck.debian.org and subject line Bug#717131: fixed in minidlna 1.1.2+dfsg-1 has caused the Debian Bug report #717131, regarding minidlna: CVE-2013-2745 CVE-2013-2738 CVE-2013-2739 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.) -- 717131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: minidlna Severity: grave Tags: security Justification: user security hole Please see http://www.securityfocus.com/archive/1/527299/30/0 Cheers, Moritz ---End Message--- ---BeginMessage--- Source: minidlna Source-Version: 1.1.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of minidlna, 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 717...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benoît Knecht benoit.kne...@fsfe.org (supplier of updated minidlna 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, 28 Apr 2014 12:05:41 +0200 Source: minidlna Binary: minidlna Architecture: source amd64 Version: 1.1.2+dfsg-1 Distribution: unstable Urgency: low Maintainer: Benoît Knecht benoit.kne...@fsfe.org Changed-By: Benoît Knecht benoit.kne...@fsfe.org Description: minidlna - lightweight DLNA/UPnP-AV server targeted at embedded systems Closes: 711234 717131 Changes: minidlna (1.1.2+dfsg-1) unstable; urgency=low . * New upstream version (Closes: #711234) * The new upstream version is no longer affected by CVE-2013-2745, CVE-2013-2738 or CVE-2013-2739 (Closes: #717131) * Use SIGUSR1 instead of SIGHUP to reopen the log file after a logrotate, since upstream is now using SIGHUP to reload the network interfaces * Update copyright information for upstream files * Bump Standards-Version to 3.9.5 (no changes required) * Override lintian warning debian-watch-may-check-gpg-signature, as upstream doesn't sign the source tarball Checksums-Sha1: 698c9f8a94cebf4db21af37a07512bff2820969e 1386 minidlna_1.1.2+dfsg-1.dsc f179345d826ea7db9dabf7b96e4d2c61d1e4d16c 302068 minidlna_1.1.2+dfsg.orig.tar.xz faa96d0391e7d0c227b59e9b68dfdf1351dbcc56 23316 minidlna_1.1.2+dfsg-1.debian.tar.xz 84f2987f7b867ec2cfc06d4695fcd1b26c35b653 133112 minidlna_1.1.2+dfsg-1_amd64.deb Checksums-Sha256: 6862042f4edc1c29e6ac12a56928d189bdb91b54f3ddeeaa4d9e3b2a454310b8 1386 minidlna_1.1.2+dfsg-1.dsc 60f9053a261043fef409439261e3bb92c523437a6113664be02fa0297eed27e8 302068 minidlna_1.1.2+dfsg.orig.tar.xz 2eff0c9479dd393d8b11db92f94b29e79b6f1bc718c1f191b15f03412b4a3eb3 23316 minidlna_1.1.2+dfsg-1.debian.tar.xz 5876a08fa0ea43a7c5eb2433c2037c1ca046afac9cd2143cc921bc56be8209ed 133112 minidlna_1.1.2+dfsg-1_amd64.deb Files: 8e508b803c59de192cbfadc67af16726 133112 net optional minidlna_1.1.2+dfsg-1_amd64.deb fc704bcf201f483493381d86f445e88c 1386 net optional minidlna_1.1.2+dfsg-1.dsc 3d364a502fdd6c60a9b7af38b1d83f9a 302068 net optional minidlna_1.1.2+dfsg.orig.tar.xz 260c7c36f0fc1bc6dd7c833b7dc1b7c3 23316 net optional minidlna_1.1.2+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlNssTYACgkQLARVQsm1XazAUgCfTvpuULGHw+p8A+Dk2gbtrZmV lGsAnR7jr7NBGrRTE26QoazEfLMjTVda =b7kt -END PGP SIGNATUREEnd Message---
Bug#747363: IO::Uncompress::Gunzip: Can no longer gunzip to in-memory file handle
severity 747363 normal forwarded 747363 https://rt.cpan.org/Public/Bug/Display.html?id=95494 thanks On Wed, May 07, 2014 at 10:28:55PM +0200, Christoph Biedl wrote: Package: perl-modules Version: 5.18.2-2 Severity: critical Justification: Breaks unreleated software IO-Compress 2.060 as bundled with Perl 5.18.2 introduces a regression over 2.033 (as in Debian wheezy) and older versions like 2.020 in squeeze: When uncompressing to a filehandle that is connected to an in-memory string with open $fh, '', \$buf the syswrite() in IO::Uncompress::Base::_rd2 (line 759) fails with $! set to Bad file descriptor. In previous versions, print was used instead which did not have this problem. Thanks for the report. I've forwarded this upstream as https://rt.cpan.org/Public/Bug/Display.html?id=95494 Programs using IO-Compress are not unrelated software, so the 'critical' severity is unwarranted. I'm lowering the severity. --- #!/usr/bin/perl use IO::Uncompress::Gunzip qw(gunzip $GunzipError); my $buf_out = ''; open my $fh_out, '', \$buf_out or die $!; gunzip ( '/usr/share/doc/perl-modules/changelog.Debian.gz', $fh_out ) or die Failed: $GunzipError, $!; print $buf_out; --- Note that you can uncompress to a scalar reference, which accomplishes the same thing: --- #!/usr/bin/perl use IO::Uncompress::Gunzip qw(gunzip $GunzipError); my $buf_out = ''; gunzip ( '/usr/share/doc/perl-modules/changelog.Debian.gz', \$buf_out ) or die Failed: $GunzipError, $!; print $buf_out; --- -- Niko Tyni nt...@debian.org -- 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#747363: IO::Uncompress::Gunzip: Can no longer gunzip to in-memory file handle
Processing commands for cont...@bugs.debian.org: severity 747363 normal Bug #747363 [perl-modules] IO::Uncompress::Gunzip: Can no longer gunzip to in-memory file handle Severity set to 'normal' from 'critical' forwarded 747363 https://rt.cpan.org/Public/Bug/Display.html?id=95494 Bug #747363 [perl-modules] IO::Uncompress::Gunzip: Can no longer gunzip to in-memory file handle Set Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=95494'. thanks Stopping processing here. Please contact me if you need assistance. -- 747363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747363 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#747500: libopencv2.4-java: Broken symlink for /usr/share/java/opencv.jar
Package: libopencv2.4-java Version: 2.4.8+dfsg1-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, The symbolic links for the jar files in /usr/share/java are broken because of a wrong version number (247 instead of 248): drwxr-xr-x root/root 0 2014-02-19 01:19 ./ drwxr-xr-x root/root 0 2014-02-19 01:19 ./usr/ drwxr-xr-x root/root 0 2014-02-19 01:19 ./usr/share/ drwxr-xr-x root/root 0 2014-02-19 01:19 ./usr/share/OpenCV/ drwxr-xr-x root/root 0 2014-02-19 01:19 ./usr/share/OpenCV/java/ - -rw-r--r-- root/root445463 2014-02-19 01:12 ./usr/share/OpenCV/java/opencv-248.jar drwxr-xr-x root/root 0 2014-02-19 01:19 ./usr/share/doc/ drwxr-xr-x root/root 0 2014-02-19 01:19 ./usr/share/doc/libopencv2.4-java/ - -rw-r--r-- root/root 8477 2014-02-17 22:10 ./usr/share/doc/libopencv2.4-java/changelog.Debian.gz - -rw-r--r-- root/root 3471 2014-01-28 05:10 ./usr/share/doc/libopencv2.4-java/copyright drwxr-xr-x root/root 0 2014-02-19 01:19 ./usr/share/java/ lrwxrwxrwx root/root 0 2014-02-19 01:19 ./usr/share/java/opencv.jar - ../OpenCV/java/opencv-247.jar lrwxrwxrwx root/root 0 2014-02-19 01:19 ./usr/share/java/opencv-247.jar - ../OpenCV/java/opencv-247.jar Thanks, _g. - -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-486 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 libopencv2.4-java depends on: ii libopencv2.4-jni 2.4.8+dfsg1-2 libopencv2.4-java recommends no packages. libopencv2.4-java suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTbMLIAAoJEO/obGx//s+DFEsH/0a5UWWz1O82A6NIm1KSs0Wp X6cUbKnbrgVDdw49PgudQX1mVINBBrJ4FjIo7j7cnmvfKTMRtRzUXDN17U57ANZt Y+52um88aaARg6Q+d4JOeOP2yF3iBg7sAbcI34tQHre3+DSFhEiiUgifGAilV593 Bj+vVNt0Odj+JYg16I9SErlZUeSopem31eoXywd/WRlTiBxejpqmJI4iz5CqjWUY 16RFez8l/jIBUgT/1Kz4RSk6daL7WjaXLTNxvSL808O5sZ8uKm0o9Gh9FK7Hva4S fMiPHQpOIPmuI5emwxHS4thn/NXkn+RlqKcuo0kddW+v+MNJS2cVTtP1bw2tsrc= =Ig+S -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747502: FTBFS: test failure in Catalyst-Plugin-SubRequest
Package: libcatalyst-modules-perl Version: 47 Severity: serious Forwarded: https://rt.cpan.org/Ticket/Display.html?id=94392 libcatalyst-modules-perl fails to build in sid with test failure in Catalyst-Plugin-SubRequest: make[2]: Entering directory '/tmp/buildd/libcatalyst-modules-perl-47/build-area/ 01/Catalyst-Plugin-SubRequest-0.20' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'inc', 'blib/lib', 'blib/arch') t/*.t t/01use.t .. ok # Failed test 'Normal request content' # at t/02subreq.t line 20. # got: '13' # expected: '11433' # Failed test 'Normal request content' # at t/02subreq.t line 44. # got: '3' # expected: 'foo33' # Failed test 'Normal Double request content' # at t/02subreq.t line 50. # got: '3' # expected: '1531633' # Looks like you failed 3 tests of 21. t/02subreq.t ... Dubious, test returned 3 (wstat 768, 0x300) Failed 3/21 subtests This is https://rt.cpan.org/Public/Bug/Display.html?id=94392 and possible patches seem to be available at https://gist.github.com/jjn1056/9947765 Given request to deprecate the module (https://rt.cpan.org/Public/Bug/Display.html?id=57544) and that the author seems to agree, I wonder if it would be best to drop the dist from the bundle. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741743: kicad: FTBFS: find: `debian/kicad-common/usr/share/kicad': No such file or directory
Hi,
It seams to me that the problem is in debian/rules file.
If package is being built with both arch specific and indep parts (fakeroot
debian/rules binary),
build finishes successfully .
If we build only arch specific parts of the package (binary-arch),
build fails on:
find debian/kicad-common/usr/share/kicad -name CMake* -exec rm {} \;
find: `debian/kicad-common/usr/share/kicad': No such file or directory
The reason for this is the fact that kicad-common is arch independent,
and should not be packed in this case.
In order to resolve this issue I split override_dh_install into
two parts:
override_dh_install-arch and override_dh_install-indep.
Changes needed for debian/rules are attached.
With this fix I was able to successfully build kicad for
mips, mipsel and amd64.
Regards,
Dejan
--- kicad-0.20140224+bzr4027.orig/debian/rules 2014-03-07 10:50:28.0 +
+++ kicad-0.20140224+bzr4027/debian/rules 2014-05-08 14:38:34.0 +
@@ -21,7 +21,7 @@
override_dh_compress:
dh_compress --exclude=.pdf
-override_dh_install:
+override_dh_install-arch:
convert bitmaps_png/icons/icon_kicad.xpm -resize 32x32 debian/tmp/icon_kicad.xpm
dh_install
# fix wrong permissions and link jnlp file to usr/share
@@ -29,6 +29,9 @@
chmod a-x $(COMMONDIR)/usr/share/kicad/internat/ja/*
ln -s ../share/kicad/freeroute.jnlp $(PKGDIR)/usr/bin
chmod a-x $(PKGDIR)/usr/share/kicad/freeroute.jnlp
+
+override_dh_install-indep:
+ dh_install
# remove out-of-topic files
find $(COMMONDIR)/usr/share/kicad -name CMake* -exec rm {} \;
Bug#747506: openjdk-6: cannot load libsikuli-script-java any more
Source: openjdk-6 Version: 6b31-1.13.3-1~deb7u1 Severity: critical Justification: breaks unrelated software Dear Maintainer, After upgrading the Java packages to 6b31-1.13.3-1~deb7u1 (from 6b27-1.12.6-1~deb7u1) I can no longer use libsikuli-script-java (1.0~x~rc3.tesseract3-dfsg1-5 from Wheezy). The fatal error I get is: no VisionProxy in java.library.path (UnsatisfiedLinkError) Downgrading to the following packages and versions fixes the issue for me: * icedtea-6-jre-cacao:amd64 6b27-1.12.6-1~deb7u1 * openjdk-6-jre-lib:amd64 6b27-1.12.6-1~deb7u1 * openjdk-6-jre-headless:amd64 6b27-1.12.6-1~deb7u1 * icedtea-6-jre-jamvm:amd64 6b27-1.12.6-1~deb7u1 * openjdk-6-jdk:amd64 6b27-1.12.6-1~deb7u1 * openjdk-6-jre:amd64 6b27-1.12.6-1~deb7u1 Cheers! -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (600, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.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 signature.asc Description: OpenPGP digital signature
Processed: easyspice: diff for NMU version 0.6.8-2.1
Processing commands for cont...@bugs.debian.org: tags 747052 + patch Bug #747052 [easyspice] FTBFS: undefined reference to symbol 'pow@@GLIBC_2.2.5' Added tag(s) patch. tags 747052 + pending Bug #747052 [easyspice] FTBFS: undefined reference to symbol 'pow@@GLIBC_2.2.5' Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 747052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747052 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#747052: easyspice: diff for NMU version 0.6.8-2.1
tags 747052 + patch tags 747052 + pending thanks Dear maintainer, I've prepared an NMU for easyspice (versioned as 0.6.8-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E diff -u easyspice-0.6.8/debian/changelog easyspice-0.6.8/debian/changelog --- easyspice-0.6.8/debian/changelog +++ easyspice-0.6.8/debian/changelog @@ -1,3 +1,11 @@ +easyspice (0.6.8-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Added missing math lib to link, fixing FTBFS (Closes: 747052). +- debian/patches/libm_underlinkage.patch: pick up from 0.6.8-2ubuntu1. + + -- HIGUCHI Daisuke (VDR dai) d...@debian.org Fri, 09 May 2014 22:09:33 +0900 + easyspice (0.6.8-2) unstable; urgency=low * Bump standards version to 3.7.3. No changes needed. diff -u easyspice-0.6.8/debian/patches/series easyspice-0.6.8/debian/patches/series --- easyspice-0.6.8/debian/patches/series +++ easyspice-0.6.8/debian/patches/series @@ -1 +1,2 @@ +libm_underlinkage.patch 01_docurl.diff only in patch2: unchanged: --- easyspice-0.6.8.orig/debian/patches/libm_underlinkage.patch +++ easyspice-0.6.8/debian/patches/libm_underlinkage.patch @@ -0,0 +1,31 @@ +Description: Added missing math lib to link, fixing FTBFS. +Author: Daniel T Chen crim...@ubuntu.com +Bug-Debian: https://bugs.debian.org/747052 +Last-Update: 2013-04-11 + +Index: easyspice-0.6.8/src/Makefile.am +=== +--- easyspice-0.6.8.orig/src/Makefile.am 2013-04-11 09:44:23.680002124 -0400 easyspice-0.6.8/src/Makefile.am 2013-04-11 09:44:34.571928687 -0400 +@@ -18,7 +18,7 @@ + spice.c \ + util.c + +-easy_spice_LDADD = @PACKAGE_LIBS@ $(INTLLIBS) ++easy_spice_LDADD = @PACKAGE_LIBS@ $(INTLLIBS) -lm + + localedir = @datadir@/locale + DEFS = -DLOCALEDIR=\$(localedir)\ @DEFS@ +Index: easyspice-0.6.8/src/Makefile.in +=== +--- easyspice-0.6.8.orig/src/Makefile.in 2013-04-11 09:44:17.416036093 -0400 easyspice-0.6.8/src/Makefile.in 2013-04-11 09:44:43.115859927 -0400 +@@ -181,7 +181,7 @@ + spice.c \ + util.c + +-easy_spice_LDADD = @PACKAGE_LIBS@ $(INTLLIBS) ++easy_spice_LDADD = @PACKAGE_LIBS@ $(INTLLIBS) -lm + AM_CFLAGS = -Wall + all: all-am + signature.asc Description: Digital signature
Bug#718004: paramiko: diff for NMU version 1.10.1-1.1
tags 718004 + patch
tags 718004 + pending
thanks
Dear maintainer,
I've prepared an NMU for paramiko (versioned as 1.10.1-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
--
Regards,
dai
GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E
diff -Nru paramiko-1.10.1/debian/changelog paramiko-1.10.1/debian/changelog
--- paramiko-1.10.1/debian/changelog 2013-06-28 11:59:08.0 +0900
+++ paramiko-1.10.1/debian/changelog 2014-05-09 22:43:55.0 +0900
@@ -1,3 +1,11 @@
+paramiko (1.10.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/control: add Breaks/Replaces fix fails to upgrade from wheezy.
+thanks Felix Geyer fge...@debian.org (Closes: #718004).
+
+ -- HIGUCHI Daisuke (VDR dai) d...@debian.org Fri, 09 May 2014 22:42:55 +0900
+
paramiko (1.10.1-1) unstable; urgency=low
* Imported Upstream version 1.10.1
diff -Nru paramiko-1.10.1/debian/control paramiko-1.10.1/debian/control
--- paramiko-1.10.1/debian/control 2013-05-27 14:07:38.0 +0900
+++ paramiko-1.10.1/debian/control 2014-05-09 22:42:50.0 +0900
@@ -17,6 +17,8 @@
Section: doc
Architecture: all
Depends: ${misc:Depends}
+Breaks: python-paramiko ( 1.10.1-1~)
+Replaces: python-paramiko ( 1.10.1-1~)
Description: Make ssh v2 connections with Python (Documentation)
This is a library for making SSH2 connections (client or server).
Emphasis is on using SSH2 as an alternative to SSL for making secure
signature.asc
Description: Digital signature
Processed: paramiko: diff for NMU version 1.10.1-1.1
Processing commands for cont...@bugs.debian.org: tags 718004 + patch Bug #718004 [paramiko-doc] paramiko-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/doc-base/python-paramiko Ignoring request to alter tags of bug #718004 to the same tags previously set tags 718004 + pending Bug #718004 [paramiko-doc] paramiko-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/doc-base/python-paramiko Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 718004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718004 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#747512: [grub-pc] Installation fails
Package: grub-pc Version: 2.02~beta2-10 Severity: grave --- Please enter the report below this line. --- I cannot install current grub-pc. I first noticed the issue when trying to update from synaptic, then apt. Here's what happens when I try to install grub-pc using dpkg: root@notebook4:~# LANG=C dpkg -i *.deb (Reading database ... 315047 files and directories currently installed.) Preparing to unpack grub-pc_2.02~beta2-10_amd64.deb ... Unpacking grub-pc (2.02~beta2-10) over (2.02~beta2-10) ... Preparing to unpack grub-pc-bin_2.02~beta2-10_amd64.deb ... Unpacking grub-pc-bin (2.02~beta2-10) over (2.02~beta2-10) ... Setting up grub-pc-bin (2.02~beta2-10) ... Setting up grub-pc (2.02~beta2-10) ... /var/lib/dpkg/info/grub-pc.postinst: line 195: /bin/uname: cannot execute binary file: Exec format error /var/lib/dpkg/info/grub-pc.postinst: line 195: /bin/uname: cannot execute binary file: Exec format error Installing for i386-pc platform. Installation finished. No error reported. Generating grub configuration file ... /bin/uname: 1: /bin/uname: Syntax error: ( unexpected dpkg: error processing package grub-pc (--install): subprocess installed post-installation script returned error exit status 2 Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: grub-pc --- System information. --- Architecture: amd64 Kernel: Debian Release: jessie/sid 500 unstableftp.de.debian.org --- Package information. --- Depends (Version) | Installed ==-+-== debconf (= 0.5) | 1.5.53 OR debconf-2.0| grub-common (= 2.02~beta2-10) | 2.02~beta2-10 grub2-common (= 2.02~beta2-10) | 2.02~beta2-10 grub-pc-bin (= 2.02~beta2-10) | 2.02~beta2-10 ucf| 3.0028 Package's Recommends field is empty. Package's Suggests field is empty. --- Output from package bug script --- *** BEGIN /proc/mounts /dev/mapper/universum-root / btrfs rw,relatime,ssd,discard,space_cache 0 0 /dev/sda1 /boot ext4 rw,relatime,discard,data=ordered 0 0 *** END /proc/mounts *** BEGIN /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s /grubenv ] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731823: Fixed in mentors, can anybody please sponsor?
Hi *
file vtkXYPlotActor.class
vtkXYPlotActor.class: compiled Java class data, version 49.0 (Java 1.5)
file vtkTypeInt16Array.class
vtkTypeInt16Array.class: compiled Java class data, version 49.0 (Java 1.5)
the trick was this patch
+--- a/CMake/vtkWrapJava.cmake
b/CMake/vtkWrapJava.cmake
+@@ -204,7 +204,7 @@ MACRO(VTK_GENERATE_JAVA_DEPENDENCIES TARGET)
+ ADD_CUSTOM_COMMAND(
+ OUTPUT ${driver}
+ COMMAND ${JAVA_COMPILE}
+- -source 5 -classpath
${javaPath} ${srcPath}/vtk${TARGET}Driver.java
++ -source 1.5 -target 1.5 -classpath ${javaPath}
${srcPath}/vtk${TARGET}Driver.java
+ DEPENDS ${sources}
+ )
+ ADD_CUSTOM_COMMAND(TARGET ${TARGET} SOURCE ${TARGET} DEPENDS ${driver})
So I started from jordi's patch, added this, rebuilt, checked the binary,
uploaded on mentors...
changestool for adding the orig tar.gz (sick, mentors wants it)
waiting for a sponsor ;)
cheers,
Gianfranco
Bug#747512: marked as done ([grub-pc] Installation fails)
Your message dated Fri, 9 May 2014 15:23:08 +0100 with message-id 20140509142308.gj7...@riva.ucam.org and subject line Re: Bug#747512: [grub-pc] Installation fails has caused the Debian Bug report #747512, regarding [grub-pc] Installation fails 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.) -- 747512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: grub-pc Version: 2.02~beta2-10 Severity: grave --- Please enter the report below this line. --- I cannot install current grub-pc. I first noticed the issue when trying to update from synaptic, then apt. Here's what happens when I try to install grub-pc using dpkg: root@notebook4:~# LANG=C dpkg -i *.deb (Reading database ... 315047 files and directories currently installed.) Preparing to unpack grub-pc_2.02~beta2-10_amd64.deb ... Unpacking grub-pc (2.02~beta2-10) over (2.02~beta2-10) ... Preparing to unpack grub-pc-bin_2.02~beta2-10_amd64.deb ... Unpacking grub-pc-bin (2.02~beta2-10) over (2.02~beta2-10) ... Setting up grub-pc-bin (2.02~beta2-10) ... Setting up grub-pc (2.02~beta2-10) ... /var/lib/dpkg/info/grub-pc.postinst: line 195: /bin/uname: cannot execute binary file: Exec format error /var/lib/dpkg/info/grub-pc.postinst: line 195: /bin/uname: cannot execute binary file: Exec format error Installing for i386-pc platform. Installation finished. No error reported. Generating grub configuration file ... /bin/uname: 1: /bin/uname: Syntax error: ( unexpected dpkg: error processing package grub-pc (--install): subprocess installed post-installation script returned error exit status 2 Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: grub-pc --- System information. --- Architecture: amd64 Kernel: Debian Release: jessie/sid 500 unstableftp.de.debian.org --- Package information. --- Depends (Version) | Installed ==-+-== debconf (= 0.5) | 1.5.53 OR debconf-2.0| grub-common (= 2.02~beta2-10) | 2.02~beta2-10 grub2-common (= 2.02~beta2-10) | 2.02~beta2-10 grub-pc-bin (= 2.02~beta2-10) | 2.02~beta2-10 ucf| 3.0028 Package's Recommends field is empty. Package's Suggests field is empty. --- Output from package bug script --- *** BEGIN /proc/mounts /dev/mapper/universum-root / btrfs rw,relatime,ssd,discard,space_cache 0 0 /dev/sda1 /boot ext4 rw,relatime,discard,data=ordered 0 0 *** END /proc/mounts *** BEGIN /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s /grubenv ] ---End Message--- ---BeginMessage--- On Fri, May 09, 2014 at 04:02:56PM +0200, Philipp Klaus Krause wrote: Setting up grub-pc (2.02~beta2-10) ... /var/lib/dpkg/info/grub-pc.postinst: line 195: /bin/uname: cannot execute binary file: Exec format error /var/lib/dpkg/info/grub-pc.postinst: line 195: /bin/uname: cannot execute binary file: Exec format error This is some strange problem with your system, and is not a bug in grub-pc. Perhaps try reinstalling the coreutils package? -- Colin Watson [cjwat...@debian.org]---End Message---
Bug#731823: Fixed in mentors, can anybody please sponsor?
Thanks Gianfranco, If you have some time, could you please help Anton with vtk6? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747108 -Dominique
Bug#747525: equalx: FTBFS: pkg-config: not found
Source: equalx Version: 0.6.0-1 Severity: serious Justification: fails to build from source Builds of equalx in minimal environments (as on the autobuilders) have been failing: dh_auto_configure -- PREFIX=/usr/bin sh: 1: pkg-config: not found Project ERROR: Package exempi-2.0 not found dh_auto_configure: qmake -makefile -nocache QMAKE_CFLAGS_RELEASE=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 QMAKE_CFLAGS_DEBUG=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 QMAKE_CXXFLAGS_RELEASE=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 QMAKE_CXXFLAGS_DEBUG=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 QMAKE_LFLAGS_RELEASE=-Wl,-z,relro QMAKE_LFLAGS_DEBUG=-Wl,-z,relro QMAKE_STRIP=: PREFIX=/usr PREFIX=/usr/bin returned exit code 2 make[1]: *** [override_dh_auto_configure] Error 2 Please declare a build dependency on pkg-config and confirm with pbuilder or the like that you haven't missed anything else. (It looks like you do already declare a proper dependency on libexempi-dev; qmake just can't actually detect it without pkg-config.) Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713612: marked as done (vdpau-video: FTBFS: utils_glx.h:163:5: error: unknown type name 'PFNGLMULTITEXCOORD2FPROC')
Your message dated Fri, 09 May 2014 15:35:32 + with message-id e1wimpg-00087p...@franck.debian.org and subject line Bug#713612: fixed in vdpau-video 0.7.4-1 has caused the Debian Bug report #713612, regarding vdpau-video: FTBFS: utils_glx.h:163:5: error: unknown type name 'PFNGLMULTITEXCOORD2FPROC' 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.) -- 713612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: vdpau-video Version: 0.7.3-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o vdpau_driver.lo vdpau_driver.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c vdpau_driver.c -fPIC -DPIC -o .libs/vdpau_driver.o In file included from vdpau_video_glx.h:26:0, from vdpau_driver.c:32: utils_glx.h:163:5: error: unknown type name 'PFNGLMULTITEXCOORD2FPROC' PFNGLMULTITEXCOORD2FPROC gl_multi_tex_coord_2f; ^ In file included from vdpau_driver.c:320:0: vdpau_driver_template.h: In function 'vdpau_Initialize_Current': vdpau_driver_template.h:640:45: warning: assignment from incompatible pointer type [enabled by default] vtable-vaBufferInfo= vdpau_BufferInfo; ^ make[3]: *** [vdpau_driver.lo] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/06/20/vdpau-video_0.7.3-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. ---End Message--- ---BeginMessage--- Source: vdpau-video Source-Version: 0.7.4-1 We believe that the bug you reported is fixed in the latest version of vdpau-video, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 713...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher sramac...@debian.org (supplier of updated vdpau-video 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: Fri, 09 May 2014 17:17:38 +0200 Source: vdpau-video Binary: vdpau-va-driver Architecture: source amd64 Version: 0.7.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Sebastian Ramacher sramac...@debian.org Description: vdpau-va-driver - VDPAU-based backend for VA API Closes: 713612 743561 Changes: vdpau-video (0.7.4-1) unstable; urgency=medium . * New upstream release. * debian/control: - Add myself to Uploaders. - Remove Andres Mejia from Uploaders since he is MIA. Thank you for maintaing vdpau-video. (Closes: #743561) - Point Homepage to the new home at freedesktop.org. - Bump Standards-Version to 3.9.5. - Add dh-autoreconf to Build-Depends. - Update Vcs-* to use canonical URLs. * debian/watch: Update watch file to fetch tarball from from the new home at freedesktop.org. Thanks to Ross Gammon. * debian/patches: - autoreconf.patch: Removed, no longer needed. - cast.patch: Fix build with libvdpau-dev = 0.7-2. Bump Build-Depends on libvdpau-dev accordingly. - GL-version-1_3.patch: Apply workaround from Ubuntu to fix build failure. (Closes: #713612) - libva-constants.patch: Apply patch from upstream to fix build with recent libva versions. * debian/copyright: Convert to Copyright Format 1.0. *
Bug#746077: marked as done (libdessert0.87: FTBFS: ld: cannot find -lpci)
Your message dated Fri, 09 May 2014 15:35:08 + with message-id e1wimpi-00083j...@franck.debian.org and subject line Bug#746077: fixed in libdessert0.87 0.87.2-1.1 has caused the Debian Bug report #746077, regarding libdessert0.87: FTBFS: ld: cannot find -lpci 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.) -- 746077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libdessert0.87 Version: 0.87.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140426 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): cc -ggdb -Wall -fPIC -DTARGET_LINUX -D_GNU_SOURCE -DSHLIB_VERSION=\0.87.2\ -DNETSNMP_ENABLE_IPV6 -fno-strict-aliasing -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DNETSNMP_USE_INLINE -Ulinux -Dlinux=linux -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fstack-protector -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl/5.18/CORE -D_FORTIFY_SOURCE=2 -I/usr/include -Wstrict-prototypes -dy -static-libgcc -lpthread -lpcap -lcli -Wl,-z,relro -Wl,-z,now -L/usr/lib/x86_64-linux-gnu -lnetsnmpmibs -lsensors -lpci -ldl -lnetsnmpagent -lwrap -Wl,-E -lnetsnmp -lcrypto -lm -shared -Wl,-soname,libdessert.so.0.87 -o libdessert.so.0.87.2 dessert_core.o dessert_log.o dessert_sysiface.o dessert_meshiface.o dessert_msg.o dessert_cli.o dessert_periodic.o dessert_agentx.o snmp/dessertObjects.o snmp/dessertMeshifTable.o snmp/dessertMeshifTable_data_get.o snmp/dessertMeshifTable_data_set.o snmp/dessertMeshifTable_data_access.o snmp/dessertMeshifTable_interface.o snmp/dessertSysifTable.o snmp/dessertSysifTable_data_get.o snmp/dessertSysifTable_data_set.o snmp/dessertSysifTable_data_access.o snmp/dessertSysifTable_interface.o snmp/dessertAppStatsTable.o snmp/dessertAppStatsTable_data_get.o snmp/dessertAppStatsTable_data_set.o snmp/dessertAppStatsTable_data_access.o snmp/dessertAppStatsTable_interface.o snmp/dessertAppParamsTable.o snmp/dessertAppParamsTable_data_get.o snmp/dessertAppParamsTable_data_set.o snmp/dessertAppParamsTable_data_access.o snmp/dessertAppParamsTable_interface.o /usr/bin/ld: cannot find -lpci collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/libdessert0.87_0.87.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: libdessert0.87 Source-Version: 0.87.2-1.1 We believe that the bug you reported is fixed in the latest version of libdessert0.87, 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. HIGUCHI Daisuke (VDR dai) d...@debian.org (supplier of updated libdessert0.87 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 04 May 2014 22:58:11 +0900 Source: libdessert0.87 Binary: libdessert0.87-dev libdessert0.87 Architecture: source amd64 Version: 0.87.2-1.1 Distribution: unstable Urgency: medium Maintainer: David Gutzmann gutzm...@inf.fu-berlin.de Changed-By: HIGUCHI Daisuke (VDR dai) d...@debian.org Description: libdessert0.87 - a simple and extensible routing-framework for testbeds libdessert0.87-dev - header file and documentation for libdessert0.87 Closes: 739563 746077 Changes: libdessert0.87 (0.87.2-1.1) unstable; urgency=medium . * Non-maintainer upload. * fix FTBFS with clang (Closes: #739563). - debian/patches/clang-ftbfs.diff: new file. thanks to Arthur Marble art...@info9.net. * fix FTBFS on amd64 (Closes: #746077). -
Bug#744010: marked as done (ruby-fog-core and ruby-fog: error when trying to install together)
Your message dated Fri, 09 May 2014 16:04:33 + with message-id e1winhl-0002gf...@franck.debian.org and subject line Bug#744010: fixed in ruby-fog 1.22.0-2 has caused the Debian Bug report #744010, regarding ruby-fog-core and ruby-fog: error when trying to install together 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.) -- 744010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-fog,ruby-fog-core Version: ruby-fog/1.19.0-1 Version: ruby-fog-core/1.21.1+gh-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-04-09 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libxml2:amd64. (Reading database ... 10937 files and directories currently installed.) Preparing to unpack .../libxml2_2.9.1+dfsg1-3_amd64.deb ... Unpacking libxml2:amd64 (2.9.1+dfsg1-3) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1~rc1+r3.0.13-12_amd64.deb ... Unpacking libffi6:amd64 (3.1~rc1+r3.0.13-12) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-2_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-2) ... Selecting previously unselected package libxslt1.1:amd64. Preparing to unpack .../libxslt1.1_1.1.28-2_amd64.deb ... Unpacking libxslt1.1:amd64 (1.1.28-2) ... Selecting previously unselected package libyaml-0-2:amd64. Preparing to unpack .../libyaml-0-2_0.1.4-3.2_amd64.deb ... Unpacking libyaml-0-2:amd64 (0.1.4-3.2) ... Selecting previously unselected package libjs-jquery. Preparing to unpack .../libjs-jquery_1.7.2+dfsg-3_all.deb ... Unpacking libjs-jquery (1.7.2+dfsg-3) ... Selecting previously unselected package libruby2.0:amd64. Preparing to unpack .../libruby2.0_2.0.0.484+really457-2_amd64.deb ... Unpacking libruby2.0:amd64 (2.0.0.484+really457-2) ... Selecting previously unselected package ruby2.0. Preparing to unpack .../ruby2.0_2.0.0.484+really457-2_amd64.deb ... Unpacking ruby2.0 (2.0.0.484+really457-2) ... Selecting previously unselected package ruby. Preparing to unpack .../ruby_1%3a2.0.0.1_all.deb ... Unpacking ruby (1:2.0.0.1) ... Selecting previously unselected package ruby-blankslate. Preparing to unpack .../ruby-blankslate_2.1.2.4-4_all.deb ... Unpacking ruby-blankslate (2.1.2.4-4) ... Selecting previously unselected package ruby-builder. Preparing to unpack .../ruby-builder_3.2.2-1_all.deb ... Unpacking ruby-builder (3.2.2-1) ... Selecting previously unselected package ruby-excon. Preparing to unpack .../ruby-excon_0.31.0-1_all.deb ... Unpacking ruby-excon (0.31.0-1) ... Selecting previously unselected package ruby-formatador. Preparing to unpack .../ruby-formatador_0.2.1-1_all.deb ... Unpacking ruby-formatador (0.2.1-1) ... Selecting previously unselected package ruby-hmac. Preparing to unpack .../ruby-hmac_0.4.0-4_all.deb ... Unpacking ruby-hmac (0.4.0-4) ... Selecting previously unselected package ruby-mime-types. Preparing to unpack .../ruby-mime-types_1.25-1_all.deb ... Unpacking ruby-mime-types (1.25-1) ... Selecting previously unselected package ruby-multi-json. Preparing to unpack .../ruby-multi-json_1.8.0-1_all.deb ... Unpacking ruby-multi-json (1.8.0-1) ... Selecting previously unselected package ruby-net-ssh. Preparing to unpack .../ruby-net-ssh_1%3a2.6.8-1_all.deb ... Unpacking ruby-net-ssh (1:2.6.8-1) ... Selecting previously unselected package ruby-net-scp. Preparing to unpack .../ruby-net-scp_1.1.1-1_all.deb ... Unpacking ruby-net-scp (1.1.1-1) ... Selecting previously unselected package ruby-nokogiri. Preparing to unpack .../ruby-nokogiri_1.6.1+ds-2_amd64.deb ... Unpacking ruby-nokogiri (1.6.1+ds-2) ... Selecting previously unselected package ruby-fog. Preparing to unpack .../ruby-fog_1.19.0-1_all.deb ... Unpacking ruby-fog (1.19.0-1) ... Selecting previously unselected package ruby-fog-core. Preparing to unpack .../ruby-fog-core_1.21.1+gh-1_all.deb ... Unpacking ruby-fog-core (1.21.1+gh-1) ... dpkg: error processing archive /var/cache/apt/archives/ruby-fog-core_1.21.1+gh-1_all.deb (--unpack): trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/support.rb', which is also in package ruby-fog 1.19.0-1 Processing triggers for man-db (2.6.6-1) ... Errors were encountered while processing: /var/cache/apt/archives/ruby-fog-core_1.21.1+gh-1_all.deb E: Sub-process /usr/bin/dpkg
Bug#746123: marked as done (ruby-fog must depend on ruby-fog-core)
Your message dated Fri, 09 May 2014 16:04:33 + with message-id e1winhl-0002gl...@franck.debian.org and subject line Bug#746123: fixed in ruby-fog 1.22.0-2 has caused the Debian Bug report #746123, regarding ruby-fog must depend on ruby-fog-core 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.) -- 746123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-asset-sync Version: 1.0.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140426 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.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- fog/core (LoadError) from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/vendor_ruby/fog.rb:7:in `top (required)' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /«PKGBUILDDIR»/lib/asset_sync.rb:1:in `top (required)' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /«PKGBUILDDIR»/spec/spec_helper.rb:12:in `top (required)' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /«PKGBUILDDIR»/spec/integration/aws_integration_spec.rb:1:in `top (required)' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `load' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `block in load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `each' from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:896:in `load_spec_files' from /usr/lib/ruby/vendor_ruby/rspec/core/command_line.rb:22:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:80:in `run' from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:17:in `block in autorun' Loading simplecov-html failed, install ruby-simplecov-html /usr/bin/ruby2.0 -S rspec ./spec/integration/aws_integration_spec.rb ./spec/unit/asset_sync_spec.rb ./spec/unit/google_spec.rb ./spec/unit/multi_mime_spec.rb ./spec/unit/rackspace_spec.rb ./spec/unit/railsless_spec.rb ./spec/unit/storage_spec.rb failed ERROR: Test ruby2.0 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ruby-asset-sync_1.0.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: ruby-fog Source-Version: 1.22.0-2 We believe that the bug you reported is fixed in the latest version of ruby-fog, 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. Cédric Boutillier bou...@debian.org (supplier of updated ruby-fog 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: Fri, 09 May 2014 17:29:41 +0200 Source: ruby-fog Binary: ruby-fog Architecture: source all Version: 1.22.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Cédric Boutillier bou...@debian.org Description: ruby-fog - Ruby cloud services library Closes: 744010 746123 Changes: ruby-fog (1.22.0-2) unstable; urgency=medium . * Team upload. * Depend on ruby-fog-core, ruby-fog-json and ruby-fog-brightbox. (Closes: #746123) * Drop
Processed: downgrade 739235
Processing commands for cont...@bugs.debian.org: # sparc is no longer in jessie severity 739235 important Bug #739235 [scilab-full-bin] scilab-full-bin: missing java dependency (broken on sparc) Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 739235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739235 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#747532: iceowl-extension: aptitude dist-upgrade fails due to wrong use of Conflicts:
Package: iceowl-extension Version: 24.0~b3-1 Severity: critical Justification: breaks unrelated software -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Source package iceweasel used to build both of binary packages iceowl-extension and calendar-timezones. Since 24.0~b3-1 binary package calendar-timezones was dropped, iceowl-extension has had provides/replaces/conflicts against calendar-timezones, with the following in changelog: remove package calendar-timezones. The calendar-timezones related files are now inside the lightning package. According to Debian Policy § 7.4, breaks should used when moving a file from one package to another, whereas conflicts should be used when two packages provide the same file and will continue to do so. I believe in this case the conflicts should be changed to breaks. This bug may seem rather harmless in itself, but since stable-security has included 24.5.0-1~deb7u1, systems with iceowl-extension installed will fail to auto-upgrade systems (e.g. with unattended-upgrades or by executing aptitude upgrade) and if executing aptitude dist-upgrade the default solution is to remove iceowl-extension rather than to remove calendar-timezones as was intended. I therefore - at least for stable - consider this as breaks unrelated software and therefore tag it as critical. Concretely, the Debian Blend DebianParl was critically affected by is in that the non-auto-resolvable conflict caused other security updates to not get applied, including an upgrade to enigmail resulting in Icedove silently stopping to auto-sign emails as configured. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJTbP/oXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vW5sQH/A4osWwfgqVihlhpLNuJ9ogS EAtY/5QmYDmPLDh/sQIBcIY2LKvcV62V/5rwbX/d+lbe/2QY/+iy2BU8gS1JVohN huCM+zzkHOrzQ5Of5cPsON3lQ5CXarjkaRwq9iFIB8LFyuVSVHxZvtsowpNJPfAp G7BGaYp0OcDuoFBdx+Ong0cK4Fd6iVkpgmLy9DKN8NtTJl/13q4MmSBj3mWNtHNO A4jFuKAhmg2w3AxFSawTJI25iiIoLGBW9N6E5/xEUYjCPGwOoK3P19x2VgyfCVJu AfCwr+xhLzyz5IGUJ/0MNinWBFjIIMHpC96meyFG/lDBx8YE50Y2NNd98D7ohDE= =EjXE -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747108: I: Fixed in mentors, can anybody please sponsor?
Hi *
Like for the other bug 731823 I did the same trick for this RC bug.
However I'm not sure if the TCL patches from Jordi should be applied here too
or not.
the trick was this patch
--- vtk6-6.0.0.orig/Wrapping/Java/CMakeLists.txt
+++ vtk6-6.0.0/Wrapping/Java/CMakeLists.txt
@@ -237,7 +237,7 @@
add_custom_command(
OUTPUT ${VTK_BINARY_DIR}/java/javac_stamp.txt
DEPENDS ${VTK_JAVA_SOURCE_FILES}
COMMAND ${JAVA_COMPILE} ${JAVAC_OPTIONS}
- -source 1.5 -classpath
${VTK_JAVA_HOME}/..${SEPARATOR}${ECLIPSE_SWT_LIBRARIES} -sourcepath
${VTK_SOURCE_DIR}/Wrapping/Java/ -d ${VTK_BINARY_DIR}/java
+ -source 1.5 -target 1.5 -classpath
${VTK_JAVA_HOME}/..${SEPARATOR}${ECLIPSE_SWT_LIBRARIES} -sourcepath
${VTK_SOURCE_DIR}/Wrapping/Java/ -d ${VTK_BINARY_DIR}/java
${VTK_BINARY_DIR}/java/vtk/*.java
${VTK_BINARY_DIR}/java/vtk/rendering/*.java
${VTK_BINARY_DIR}/java/vtk/rendering/awt/*.java ${SWT_FILES}
COMMAND ${CMAKE_COMMAND} -E touch ${VTK_BINARY_DIR}/java/javac_stamp.txt
COMMENT Compiling Java Classes
waiting for a sponsor on mentors;)
cheers,
Gianfranco
Bug#747535: systemd-sysv: Ask before installing when upgrading to/installing jessie
Package: systemd-sysv Version: 204 Severity: serious When upgrading an old system installing certain packages, like network-manager and gdm3 systemd is installed changing the init system. These packages depend on libpam-systemd, which depends on systemd-sysv | systemd-shim. If systemd-shim is not installed systemd-sysv is, and the init system changes the default to systemd. This should be warned about loudly by debconf, since not all users want to change init system. Of course this should not happen without informing the user about that during the upgrade. For new installations the situation is different, systemd is the default init system. Nevertheless, perhaps even for new installations the user should be given a choice. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718004: paramiko: diff for NMU version 1.10.1-1.1
On 09.05.2014 09:48, d...@debian.org wrote: tags 718004 + patch tags 718004 + pending thanks Dear maintainer, I've prepared an NMU for paramiko (versioned as 1.10.1-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. If this work was not done through the very public, very accessible Git repo that is used to manage the package then it has wasted your time and made mine harder as I've already been working on 1.10.1. So for wasting the time that I do have I thank you. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746577: closed by Michael Biebl bi...@debian.org (Re: Bug#746577: systemd-sysv: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable)
On Fri, May 9, 2014 at 4:48 AM, Tollef Fog Heen tfh...@err.no wrote: ]] Zack Weinberg Ah, I understand now. Yes, this + systemd-sysv and upstart *also* stop shipping /sbin/init (it becomes a symlink under control of the administrator) + documentation would be a satisfactory conclusion as far as I'm concerned. If we were to also move 'reboot' and friends to a shared utilities package, that might make the systemd-sysv package unnecessary. I don't see any reason for the symlink being removed from systemd-sysv. After all, if you don't want that symlink, just use systemd, not -sysv. ... I'm quite ok with what we're doing now: if you're installing something that depends on systemd-sysv | systemd-shim, you get the new default (systemd). If you don't like the new default, you get to take positive action to select what you would like to use instead. Right, I think this is the heart of the remaining disagreement. I don't think this is good enough, because in the common case, a system upgraded from wheezy to jessie will have at least one package that depends on libpam-systemd and therefore systemd-sysv|systemd-shim. It will be left with systemd-sysv installed, systemd-shim not installed, and sysvinit-core removed. Therefore, if the system fails to boot under systemd, the admin will have to install packages to recover. I want it to be that, in the common case, a system upgraded from wheezy to jessie is left with ALL THREE of systemd-sysv, systemd-shim, and sysvinit-core installed. This is currently not possible because of the file conflicts between systemd-sysv and sysvinit-core. Most of those could go away if we had a shared implementation of reboot and friends, but there would still be the fundamental conflict over the /sbin/init symlink. I also think it would be better if /sbin/init continued to point to /sbin/sysvinit until manually changed; but this is secondary. zw -- 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#629547: encfs: --reverse option broken (Upstream bug 81)
Processing commands for cont...@bugs.debian.org: forwarded 629547 http://code.google.com/p/encfs/issues/detail?id=81 Bug #629547 [encfs] encfs: --reverse option broken (Upstream bug 81) Set Bug forwarded-to-address to 'http://code.google.com/p/encfs/issues/detail?id=81'. thanks Stopping processing here. Please contact me if you need assistance. -- 629547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629547 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#629547: marked as done (encfs: --reverse option broken (Upstream bug 81))
Your message dated Fri, 09 May 2014 22:50:54 +0300 with message-id 1399664805.221303140.risyq...@frv40.fwdcdn.com and subject line Re: Bug#629547: encfs: --reverse option broken (Upstream bug 81) has caused the Debian Bug report #629547, regarding encfs: --reverse option broken (Upstream bug 81) 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.) -- 629547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: encfs Version: 1.7.2-1 Severity: normal Tags: upstream patch Scenario: * Mount a folder A to mount point B with the --reverse option (create encfs configuration) * Unmount folder A * Mount folder A to mount point B with the --reverse option again * Copy files from folder B to destination C * Copy A/.encfs6.xml to destination C * Mount folder C to mount point D (in normal mode, not using --reverse) Expected: * content of D is equal to content of A What happens: * filenames in D equal file names in A * content of files in D is garbage This is a typical scenario for encrypted backups! The bug is already reported upstream and a oneline patch is available: http://code.google.com/p/encfs/issues/detail?id=81 -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32 (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 Versions of packages encfs depends on: ii fuse-utils 2.8.4-1.1Filesystem in USErspace (utilities ii libboost-filesystem1.42 1.42.0-4 filesystem operations (portable pa ii libboost-serialization1 1.42.0-4 serialization library for C++ ii libboost-system1.42.0 1.42.0-4 Operating system (e.g. diagnostics ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libfuse22.8.4-1.1Filesystem in USErspace library ii libgcc1 1:4.4.5-8GCC support library ii librlog51.4-1flexible message logging library ii libssl0.9.8 0.9.8o-4squeeze1 SSL shared libraries ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 encfs recommends no packages. encfs suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- forwarded 629547 http://code.google.com/p/encfs/issues/detail?id=81 thanks Fixed in 1.7.3, so closing the bug. Best wishes, Bob---End Message---
Processed: (Без теми)
Processing commands for cont...@bugs.debian.org: tags 736066 security upstream Bug #736066 [encfs] multiple security issues discovered in encfs Added tag(s) upstream and security. thanks Stopping processing here. Please contact me if you need assistance. -- 736066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736066 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#746121: marked as done (ruby-em-hiredis: FTBFS: ERROR: Test ruby2.0 failed)
Your message dated Fri, 9 May 2014 22:58:33 +0200 with message-id 20140509205833.GA12250@spin and subject line not reproducible here either has caused the Debian Bug report #746121, regarding ruby-em-hiredis: FTBFS: ERROR: Test ruby2.0 failed 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.) -- 746121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-em-hiredis Version: 0.2.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140426 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): RuntimeError: Protocol error, got H as reply type byte # ./lib/em-hiredis/connection.rb:25:in `gets' # ./lib/em-hiredis/connection.rb:25:in `receive_data' # ./spec/support/connection_helper.rb:5:in `connect' # ./spec/base_client_spec.rb:76:in `block (2 levels) in top (required)' Finished in 10.78 seconds 152 examples, 5 failures Failed examples: rspec ./spec/base_client_spec.rb:17 # EventMachine::Hiredis::BaseClient should emit an event on reconnect failure, with the retry count rspec ./spec/base_client_spec.rb:38 # EventMachine::Hiredis::BaseClient should fail the client deferrable after 4 unsuccessful attempts rspec ./spec/base_client_spec.rb:53 # EventMachine::Hiredis::BaseClient should fail commands immediately when in failed state rspec ./spec/base_client_spec.rb:64 # EventMachine::Hiredis::BaseClient should fail queued commands when entering failed state rspec ./spec/base_client_spec.rb:75 # EventMachine::Hiredis::BaseClient should allow reconfiguring the client at runtime /usr/bin/ruby2.0 -S rspec ./spec/base_client_spec.rb ./spec/connection_spec.rb ./spec/live_redis_protocol_spec.rb ./spec/pubsub_spec.rb ./spec/redis_commands_spec.rb ./spec/url_param_spec.rb failed ERROR: Test ruby2.0 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ruby-em-hiredis_0.2.1-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. ---End Message--- ---BeginMessage--- Hi, I could not reproduce this bug either with sbuild or pbuilder. See attached log for pbuilder. I am therefore closing this bug. Please reopen if it occurs again. Cheers, Cédric dpkg-checkbuilddeps: Unmet build dependencies: ruby-hiredis W: Unmet build-dependency in source dpkg-buildpackage: source package ruby-em-hiredis dpkg-buildpackage: source version 0.2.1-2 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Per Andersson avtob...@gmail.com dpkg-source --before-build ruby-em-hiredis dpkg-source: info: using options from ruby-em-hiredis/debian/source/local-options: --unapply-patches dpkg-source: info: applying 0001-Remove-git-calls-in-gemspec.patch dpkg-source: info: applying 0002-Update-WRONGTYPE-error-message-test.patch dpkg-checkbuilddeps: Unmet build dependencies: ruby-hiredis dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future fakeroot debian/rules clean dh clean --buildsystem=ruby --with ruby dh_testdir -O--buildsystem=ruby debian/rules override_dh_auto_clean make[1]: Entering directory '/home/boutil/debian/pkg-ruby-extras/ruby-em-hiredis' dh_auto_clean Entering dh_ruby --clean Leaving dh_ruby --clean rm -rf doc debian/stop-redis-server.sh || true pkill: killing pid 907 failed: Operation not permitted make[1]: Leaving directory '/home/boutil/debian/pkg-ruby-extras/ruby-em-hiredis' dh_clean -O--buildsystem=ruby dpkg-source -b ruby-em-hiredis dpkg-source: info: using options from ruby-em-hiredis/debian/source/local-options: --unapply-patches dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building ruby-em-hiredis using existing ./ruby-em-hiredis_0.2.1.orig.tar.gz dpkg-source: info: building ruby-em-hiredis in ruby-em-hiredis_0.2.1-2.debian.tar.xz dpkg-source: info: building ruby-em-hiredis in ruby-em-hiredis_0.2.1-2.dsc dpkg-genchanges -S
Bug#747108: I: Fixed in mentors, can anybody please sponsor?
Hi Gianfranco,
thanks for the help! I integrated your fix into the next upload.
Regards
Anton
2014-05-09 19:03 GMT+02:00 Gianfranco Costamagna
costamagnagianfra...@yahoo.it:
Hi *
Like for the other bug 731823 I did the same trick for this RC bug.
However I'm not sure if the TCL patches from Jordi should be applied here
too or not.
the trick was this patch
--- vtk6-6.0.0.orig/Wrapping/Java/CMakeLists.txt
+++ vtk6-6.0.0/Wrapping/Java/CMakeLists.txt
@@ -237,7 +237,7 @@ add_custom_command(
OUTPUT ${VTK_BINARY_DIR}/java/javac_stamp.txt
DEPENDS ${VTK_JAVA_SOURCE_FILES}
COMMAND ${JAVA_COMPILE} ${JAVAC_OPTIONS}
--source 1.5 -classpath
${VTK_JAVA_HOME}/..${SEPARATOR}${ECLIPSE_SWT_LIBRARIES} -sourcepath
${VTK_SOURCE_DIR}/Wrapping/Java/ -d ${VTK_BINARY_DIR}/java
+-source 1.5 -target 1.5 -classpath
${VTK_JAVA_HOME}/..${SEPARATOR}${ECLIPSE_SWT_LIBRARIES} -sourcepath
${VTK_SOURCE_DIR}/Wrapping/Java/ -d ${VTK_BINARY_DIR}/java
${VTK_BINARY_DIR}/java/vtk/*.java
${VTK_BINARY_DIR}/java/vtk/rendering/*.java
${VTK_BINARY_DIR}/java/vtk/rendering/awt/*.java ${SWT_FILES}
COMMAND ${CMAKE_COMMAND} -E touch ${VTK_BINARY_DIR}/java/javac_stamp.txt
COMMENT Compiling Java Classes
waiting for a sponsor on mentors;)
cheers,
Gianfranco
--
debian-science-maintainers mailing list
debian-science-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747108: marked as done (incompatible-java-bytecode-format)
Your message dated Fri, 09 May 2014 21:45:34 + with message-id e1wisbm-8r...@franck.debian.org and subject line Bug#747108: fixed in vtk6 6.0.0-7 has caused the Debian Bug report #747108, regarding incompatible-java-bytecode-format 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.) -- 747108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libvtk-java Severity: serious I cannot import vtk.jar (from gdcm). Compilation states that: ... warning: /usr/share/java/vtk.jar(vtk/vtkAbstractArray.class): major version 51 is newer than 50, the highest major version supported by this compiler. It is recommended that the compiler be upgraded. ... vtk.jar should be compiled with -target 1.5 (see also: #729515 or #729513). Thanks, ---End Message--- ---BeginMessage--- Source: vtk6 Source-Version: 6.0.0-7 We believe that the bug you reported is fixed in the latest version of vtk6, 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 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky gl...@debian.org (supplier of updated vtk6 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: Fri, 09 May 2014 20:25:28 +0200 Source: vtk6 Binary: libvtk6 libvtk6-dev libvtk6-java python-vtk6 tcl-vtk6 vtk6 vtk6-doc vtk6-examples Architecture: source amd64 all Version: 6.0.0-7 Distribution: unstable Urgency: medium Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Anton Gladky gl...@debian.org Description: libvtk6- Visualization Toolkit - A high level 3D visualization library - r libvtk6-dev - VTK header files for building C++ code libvtk6-java - Visualization Toolkit - A high level 3D visualization library - j python-vtk6 - Python bindings for VTK tcl-vtk6 - Tcl bindings for VTK vtk6 - Binaries for VTK6 vtk6-doc - VTK class reference documentation vtk6-examples - C++, Tcl and Python example programs/scripts for VTK Closes: 747108 Changes: vtk6 (6.0.0-7) unstable; urgency=medium . * [9796292] Add some more entries in Depends section of libvtk6-dev. * [781eb7c] Remove old unused patches. * [a0f2514] Compile java module with -target 1.5. Thanks to Gianfranco Costamagna costamagnagianfra...@yahoo.it. (Closes: #747108) * [15c0d26] Inject -Wl,--as-needed LDFLAGS. Checksums-Sha1: 6342a47727d88b348e32067fff20fbbf28e98f64 3207 vtk6_6.0.0-7.dsc 3bd977492461a4b97ade6b80aade971272296865 20216 vtk6_6.0.0-7.debian.tar.xz 7efb3b0c45386311fcd0eddad988162a42b2fe96 19132696 libvtk6_6.0.0-7_amd64.deb 9c30f3631b1b6b0f2b88f5d2c37cfa0367c77a93 15709660 libvtk6-dev_6.0.0-7_amd64.deb f994dc0d15b18ee466f14fa0d30823f6f92dc721 3149978 libvtk6-java_6.0.0-7_amd64.deb 16c82d2c31dde02479fb240e967793ab7462e8fc 187932 python-vtk6_6.0.0-7_amd64.deb a7384a30910008658913b2971d84764bf3469a70 118374 tcl-vtk6_6.0.0-7_amd64.deb 6fca046d95ebccefc4b4bcaee5a37b27d84a11d9 160842 vtk6_6.0.0-7_amd64.deb 9ec898827239b3d553b10c1eed070ba4b768e7d1 65622 vtk6-doc_6.0.0-7_all.deb 76d93df91d4e6e209b631b3ba4b022a7096f3927 578130 vtk6-examples_6.0.0-7_all.deb Checksums-Sha256: 1ed81efd9bc53e462f755246d11268b8315f57695f8ecae6acc8c2277f71f07c 3207 vtk6_6.0.0-7.dsc 684f894338533c4f0e23ecefef99c4676c9e389eaa762cc2c4390778b304e70a 20216 vtk6_6.0.0-7.debian.tar.xz 35cd4a4beba74ea89762a94e5f0fde9d869c569f7a648fe4e60601b490544fb0 19132696 libvtk6_6.0.0-7_amd64.deb 716f915a8208ca0e2002f904c1d994da843f4333b3eebf0a7174033509bf4e7b 15709660 libvtk6-dev_6.0.0-7_amd64.deb 9ec0cb6aff8257196389eedca0523bbf74cd97360de6ca8ac9c43476c8ab79cb 3149978 libvtk6-java_6.0.0-7_amd64.deb ae931926a578dcd8fc7c40b01cb5e63710f7f7aaa74ca1c3e4f2a67972cd116a 187932 python-vtk6_6.0.0-7_amd64.deb 0483aa2cf65645f9ea768321368375706f38d8214c4cd1170c25e4d33afd4a1f 118374 tcl-vtk6_6.0.0-7_amd64.deb 7a881ae4889bbbc505f3908c22b46d9d9a3ba90f8f20d25bf34ed776576f6375 160842 vtk6_6.0.0-7_amd64.deb b731ca8b86cff8a92e01d2d3b86f76c6460393469aa7327fddc3264ce3f8f109 65622 vtk6-doc_6.0.0-7_all.deb
Processed: notfound 747535 in 204, found 747535 in 204-8
Processing commands for cont...@bugs.debian.org: notfound 747535 204 Bug #747535 [systemd-sysv] systemd-sysv: Ask before installing when upgrading to/installing jessie There is no source info for the package 'systemd-sysv' at version '204' with architecture '' Unable to make a source version for version '204' No longer marked as found in versions 204. found 747535 204-8 Bug #747535 [systemd-sysv] systemd-sysv: Ask before installing when upgrading to/installing jessie Marked as found in versions systemd/204-8. thanks Stopping processing here. Please contact me if you need assistance. -- 747535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747535 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#747108: I: Fixed in mentors, can anybody please sponsor?
Hi Anton,
Thanks to you for the upload!
Since you are in the debian science team, can you please also upload vtk?
http://bugs.debian.org/731823
and also, do you think the vtk tcl fixes should be cherry picked to vtk6 too?
cheers,
Gianfranco
Il Venerdì 9 Maggio 2014 23:36, Anton Gladky gl...@debian.org ha scritto:
Hi Gianfranco,
thanks for the help! I integrated your fix into the next upload.
Regards
Anton
2014-05-09 19:03 GMT+02:00 Gianfranco Costamagna
costamagnagianfra...@yahoo.it:
Hi *
Like for the other bug 731823 I did the same trick for this RC bug.
However I'm not sure if the TCL patches from Jordi should be applied here
too or not.
the trick was this patch
--- vtk6-6.0.0.orig/Wrapping/Java/CMakeLists.txt
+++ vtk6-6.0.0/Wrapping/Java/CMakeLists.txt
@@ -237,7 +237,7 @@ add_custom_command(
OUTPUT ${VTK_BINARY_DIR}/java/javac_stamp.txt
DEPENDS ${VTK_JAVA_SOURCE_FILES}
COMMAND ${JAVA_COMPILE} ${JAVAC_OPTIONS}
- -source 1.5 -classpath
${VTK_JAVA_HOME}/..${SEPARATOR}${ECLIPSE_SWT_LIBRARIES} -sourcepath
${VTK_SOURCE_DIR}/Wrapping/Java/ -d ${VTK_BINARY_DIR}/java
+ -source 1.5 -target 1.5 -classpath
${VTK_JAVA_HOME}/..${SEPARATOR}${ECLIPSE_SWT_LIBRARIES} -sourcepath
${VTK_SOURCE_DIR}/Wrapping/Java/ -d ${VTK_BINARY_DIR}/java
${VTK_BINARY_DIR}/java/vtk/*.java
${VTK_BINARY_DIR}/java/vtk/rendering/*.java
${VTK_BINARY_DIR}/java/vtk/rendering/awt/*.java ${SWT_FILES}
COMMAND ${CMAKE_COMMAND} -E touch ${VTK_BINARY_DIR}/java/javac_stamp.txt
COMMENT Compiling Java Classes
waiting for a sponsor on mentors;)
cheers,
Gianfranco
--
debian-science-maintainers mailing list
debian-science-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Processed: notfound 747535 in 204-8, found 747535 in 204-9
Processing commands for cont...@bugs.debian.org: notfound 747535 204-8 Bug #747535 [systemd-sysv] systemd-sysv: Ask before installing when upgrading to/installing jessie No longer marked as found in versions systemd/204-8. found 747535 204-9 Bug #747535 [systemd-sysv] systemd-sysv: Ask before installing when upgrading to/installing jessie Marked as found in versions systemd/204-9. thanks Stopping processing here. Please contact me if you need assistance. -- 747535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747535 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#745901: fglrx-driver: fglrx update crashes totem, gdm, gnome-session and anything that uses clutter
On Sat, May 03, 2014 at 06:26:51PM +0200, Tobias Hansen wrote: together. I had to switch to lightdm since gdm3 doesn't work and use this ~/.xsession: I can confirm that putting that in my xsession makes gnome-session and other programs such as totem work correctly again. As somoepne said pn the referenced pafe, its a pretty huge kludge, but at least things work again. Hopefully cogl gets fixed properly soon. Thanks for the work-around note Tobias. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747555: ruby-fog-core: trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/version.rb', which is also in package ruby-fog 1.22.0-1
Package: ruby-fog,ruby-fog-core Version: ruby-fog-core/1.21.1+gh-1 Version: ruby-fog/1.22.0-1 Severity: serious This is a very similar issue to https://bugs.debian.org/744010 but with a different file: Selecting previously unselected package ruby-fog-core. Preparing to unpack .../ruby-fog-core_1.21.1+gh-1_all.deb ... Unpacking ruby-fog-core (1.21.1+gh-1) ... dpkg: error processing archive /var/cache/apt/archives/ruby-fog-core_1.21.1+gh-1_all.deb (--unpack): trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/version.rb', which is also in package ruby-fog 1.22.0-1 Selecting previously unselected package ruby-fog-json. Preparing to unpack .../ruby-fog-json_1.0.0-1_all.deb ... Unpacking ruby-fog-json (1.0.0-1) ... Selecting previously unselected package ruby-fog-brightbox. Preparing to unpack .../ruby-fog-brightbox_0.0.2-1_all.deb ... Unpacking ruby-fog-brightbox (0.0.2-1) ... Preparing to unpack .../ruby-fog_1.22.0-2_all.deb ... Unpacking ruby-fog (1.22.0-2) over (1.22.0-1) ... Processing triggers for debian-security-support (2014.04.28) ... Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/ruby-fog-core_1.21.1+gh-1_all.deb Looks like a missing Replaces header or similar. Happened on both, amd64 as well as kfreebsd-i386. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (400, 'stable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-trunk-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ruby-fog-core depends on: ii ruby 1:2.0.0.2 ii ruby-builder 3.2.2-1 ii ruby-excon0.32.1-1 ii ruby-formatador 0.2.1-2 ii ruby-mime-types 1.25-1 ii ruby-net-scp 1.1.1-2 ii ruby-net-ssh 1:2.6.8-2 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-2 ii ruby2.0 [ruby-interpreter]2.0.0.484+really457-3 ii ruby2.1 [ruby-interpreter]2.1.1-4 ruby-fog-core recommends no packages. ruby-fog-core 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#747405: marked as done (missing license in debian/copyright)
Your message dated Fri, 09 May 2014 22:34:32 + with message-id e1witna-0007wy...@franck.debian.org and subject line Bug#747405: fixed in ruby-gnome2 2.2.0-2 has caused the Debian Bug report #747405, regarding missing license in debian/copyright 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.) -- 747405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-gnome2 Version: 2.2.0-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing license of: goocanvas/sample/demo-fifteen.rb goocanvas/sample/demo-primitives.rb goocanvas/sample/demo.rb to debian/copyright. Thanks! Thorsten ---End Message--- ---BeginMessage--- Source: ruby-gnome2 Source-Version: 2.2.0-2 We believe that the bug you reported is fixed in the latest version of ruby-gnome2, 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 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul van Tilburg pau...@debian.org (supplier of updated ruby-gnome2 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: Sat, 10 May 2014 00:06:41 +0200 Source: ruby-gnome2 Binary: ruby-atk ruby-atk-dbg ruby-cairo-gobject ruby-cairo-gobject-dbg ruby-clutter ruby-clutter-gstreamer ruby-clutter-gtk ruby-gdk-pixbuf2 ruby-gdk-pixbuf2-dbg ruby-gdk3 ruby-gdk3-dbg ruby-gio2 ruby-gio2-dbg ruby-glib2 ruby-glib2-dbg ruby-gnome2 ruby-gnome2-dev ruby-gobject-introspection ruby-gobject-introspection-dbg ruby-gstreamer ruby-gstreamer-dbg ruby-gtk2 ruby-gtk2-dbg ruby-gtk3 ruby-gtk3-dbg ruby-gtksourceview2 ruby-gtksourceview2-dbg ruby-gtksourceview3 ruby-gtksourceview3-dbg ruby-pango ruby-pango-dbg ruby-poppler ruby-poppler-dbg ruby-rsvg2 ruby-rsvg2-dbg ruby-vte ruby-vte-dbg ruby-vte3 ruby-vte3-dbg ruby-webkit-gtk ruby-webkit-gtk2 Architecture: source amd64 all Version: 2.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Paul van Tilburg pau...@debian.org Description: ruby-atk - ATK bindings for the Ruby language ruby-atk-dbg - ATK bindings for the Ruby language (debugging symbols) ruby-cairo-gobject - CairoGObject bindings for the Ruby language ruby-cairo-gobject-dbg - CairoGObject bindings for the Ruby language (debugging symbols) ruby-clutter - Clutter bindings for the Ruby language ruby-clutter-gstreamer - Clutter-GStreamer bindings for the Ruby language ruby-clutter-gtk - Clutter-Gtk bindings for the Ruby language ruby-gdk-pixbuf2 - Gdk-Pixbuf 2 bindings for the Ruby language ruby-gdk-pixbuf2-dbg - Gdk-Pixbuf 2 bindings for the Ruby language (debugging symbols) ruby-gdk3 - GDK 3 bindings for the Ruby language ruby-gdk3-dbg - GDK 3 bindings for the Ruby language (debugging symbols) ruby-gio2 - GIO bindings for the Ruby language ruby-gio2-dbg - GIO bindings for the Ruby language (debugging symbols) ruby-glib2 - GLib 2 bindings for the Ruby language ruby-glib2-dbg - GLib 2 bindings for the Ruby language (debugging symbols) ruby-gnome2 - GNOME-related bindings for the Ruby language ruby-gnome2-dev - GNOME-related bindings for the Ruby language (development files) ruby-gobject-introspection - GObject Introspection bindings for the Ruby language ruby-gobject-introspection-dbg - GObject Introspection bindings for the Ruby (debugging symbols) ruby-gstreamer - GStreamer bindings for the Ruby language ruby-gstreamer-dbg - GStreamer bindings for the Ruby language (debugging symbols) ruby-gtk2 - GTK+ 2 bindings for the Ruby language ruby-gtk2-dbg - GTK+ 2 bindings for the Ruby language (debugging symbols) ruby-gtk3 - GTK+ 3 bindings for the Ruby language ruby-gtk3-dbg - GTK+ 3 bindings for the Ruby language (debugging symbols) ruby-gtksourceview2 - GtkSourceView2 bindings for the Ruby language ruby-gtksourceview2-dbg - GtkSourceView2 bindings for the Ruby language (debugging symbols) ruby-gtksourceview3 - GtkSourceView3 bindings for the Ruby language
Bug#745945: marked as done (libtracker-miner-1.0-dev: Missing dependency against libmediaart-1.0-dev)
Your message dated Fri, 09 May 2014 22:49:38 + with message-id e1witbm-00013d...@franck.debian.org and subject line Bug#745945: fixed in tracker 1.0.1-2 has caused the Debian Bug report #745945, regarding libtracker-miner-1.0-dev: Missing dependency against libmediaart-1.0-dev 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.) -- 745945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libtracker-miner-1.0-dev Version: 1.0.0-1 Severity: serious Hello, The tracker-miner-1.0.pc file has a dependency against libmediaart-1.0 which is not translated in a Depends on the pkg. This should probably be added Cheers, Laurent Bigonville -- 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.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: tracker Source-Version: 1.0.1-2 We believe that the bug you reported is fixed in the latest version of tracker, 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 745...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated tracker 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: Sat, 10 May 2014 00:34:48 +0200 Source: tracker Binary: tracker libtracker-sparql-1.0-0 libtracker-sparql-1.0-dev libtracker-sparql-doc libtracker-miner-1.0-0 libtracker-miner-1.0-dev libtracker-miner-doc libtracker-control-1.0-0 libtracker-control-1.0-dev libtracker-control-doc gir1.2-tracker-1.0 tracker-utils tracker-gui tracker-extract tracker-miner-fs tracker-dbg Architecture: source amd64 all Version: 1.0.1-2 Distribution: unstable Urgency: medium Maintainer: Michael Biebl bi...@debian.org Changed-By: Michael Biebl bi...@debian.org Description: gir1.2-tracker-1.0 - GObject introspection data for Tracker libtracker-control-1.0-0 - library to control/monitor tracker miners libtracker-control-1.0-dev - library to control/monitor tracker miners - development files libtracker-control-doc - library to control/monitor tracker miners - API documentation libtracker-miner-1.0-0 - tracker data miner library libtracker-miner-1.0-dev - tracker data miner library - development files libtracker-miner-doc - tracker data miner library - API documentation libtracker-sparql-1.0-0 - metadata database, indexer and search tool - library libtracker-sparql-1.0-dev - metadata database, indexer and search tool - development files libtracker-sparql-doc - metadata database, indexer and search tool - API documentation tracker- metadata database, indexer and search tool tracker-dbg - metadata database, indexer and search tool - debugging symbols tracker-extract - metadata database, indexer and search tool - metadata extractors tracker-gui - metadata database, indexer and search tool - GNOME frontends tracker-miner-fs - metadata database, indexer and search tool - filesystem indexer tracker-utils - metadata database, indexer and search tool - commandline tools Closes: 745945 Changes: tracker (1.0.1-2) unstable; urgency=medium . * Upload to unstable. * Add missing dependency on libmediaart-1.0-dev to libtracker-miner-1.0-dev. (Closes: #745945) Checksums-Sha1: 3d1625fde6d2943077121e157820fe20818cf251 3763 tracker_1.0.1-2.dsc bed13db40b7b4bc5e30ff3661fb030e568693096 18596 tracker_1.0.1-2.debian.tar.xz 05fe63e16433d032c744da28ef6fd2a0d1c1d150 843200 tracker_1.0.1-2_amd64.deb 1a75a0d0c5e339760f7bf6ef2cc6c07e1344adc0 580328 libtracker-sparql-1.0-0_1.0.1-2_amd64.deb 0b90612e1d01657e14f38c7799f8cac0aa6e47ae 314054 libtracker-sparql-1.0-dev_1.0.1-2_amd64.deb 40d696d1421dc71cab7064aec293454d0d22ef1b 1533444 libtracker-sparql-doc_1.0.1-2_all.deb 8944becf300a3cad371bf8129449aba3ed674f2f 367114 libtracker-miner-1.0-0_1.0.1-2_amd64.deb 61ba10422f71b19f9e7129fdbd0cad165a3b2b5c 321532
Bug#747557: adabrowse: depends on conflicting gnat, gnat-4.6 and gnat-4.9
Package: adabrowse Version: 4.0.3-5+b1 Severity: serious Justification: FTBFS Hello, A rebuild of adacontrol was scheduled, but it can not be built because it depend on both gnat (which now depends on gnat-4.9) and gnat-4.6, and gnat-4.6 oncflicts with gnat-4.9. Samuel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.0 (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/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747558: adacontrol: depends on conflicting gnat, gnat-4.6 and gnat-4.9
Package: adacontrol Version: 1.12r4-3+b1 Severity: serious Justification: FTBFS Hello, A rebuild of adacontrol was scheduled, but it can not be built because it depend on both gnat (which now depends on gnat-4.9) and gnat-4.6, and gnat-4.6 oncflicts with gnat-4.9. Samuel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.0 (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/bash -- Samuel Q: How do you play religious roulette? A: You stand around in a circle and blaspheme and see who gets struck by lightning first. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710194: marked as done (Uses deprecated HAL on non-Linux)
Your message dated Sat, 10 May 2014 00:48:37 + with message-id e1wivsv-0006ee...@franck.debian.org and subject line Bug#710194: fixed in gxine 0.5.908-1 has caused the Debian Bug report #710194, regarding Uses deprecated HAL on non-Linux 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.) -- 710194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gxine Version: 0.5.907-2 Severity: serious User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: halectomy Hi, HAL has been deprecated and dead upstream for many years now so I'm going to request its removal from Debian [1]. Your package build with HAL support on non-Linux plattforms. Please disable HAL support on those plattforms. Regards, Michael [1] http://wiki.debian.org/HALRemoval -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: gxine Source-Version: 0.5.908-1 We believe that the bug you reported is fixed in the latest version of gxine, 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 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Darren Salt devs...@moreofthesa.me.uk (supplier of updated gxine 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: Sat, 10 May 2014 01:03:32 +0100 Source: gxine Binary: gxine gxineplugin Architecture: source amd64 Version: 0.5.908-1 Distribution: unstable Urgency: low Maintainer: Darren Salt devs...@moreofthesa.me.uk Changed-By: Darren Salt devs...@moreofthesa.me.uk Description: gxine - the xine video player, GTK+/Gnome user interface gxineplugin - the xine video player, GTK+/Gnome; launcher plugin for Mozilla Closes: 710194 Changes: gxine (0.5.908-1) unstable; urgency=low . * New upstream release. - All patches are present upstream. * Don't depend on HAL. (Closes: #710194) * Remove obsolete DM upload header. * Bump standards version to 3.9.5. No changes. Checksums-Sha1: 013eb9eac59d98e1f82c69a07d75cb8b1a643ae8 1472 gxine_0.5.908-1.dsc 542e723c9c2d396a1da68272fae4cec762cb086f 917780 gxine_0.5.908.orig.tar.xz 72022f684e2da43f59c2eacc32189f8ff7887338 11460 gxine_0.5.908-1.debian.tar.xz d8975f74307fcb1388302867cbae26c27707d9dd 389444 gxine_0.5.908-1_amd64.deb 5116845d6d46fe2f7bda1d3fdbbed1b7d0e296c7 6440 gxineplugin_0.5.908-1_amd64.deb Checksums-Sha256: 6cc55a0b16a8b7624ae9effc10c6bd86cddd9f9a7ed20e3044710886b13aae26 1472 gxine_0.5.908-1.dsc 832e47136ec68a573b22b6cc1c1d57607e78b05712ba9fb8e64464b5201ed9e7 917780 gxine_0.5.908.orig.tar.xz 7253ff5d70095bed782dd395a6411fa2bbbc415e8c96aaf218b58d4955b403e6 11460 gxine_0.5.908-1.debian.tar.xz 7e3c80353f880ac87211c06f0ab3dd58d36c51d84a8a3c3481e09271ca74648c 389444 gxine_0.5.908-1_amd64.deb eac91a03a942fdcc78b5065cf2b69b9df8764bf5ba1087e74f08b017ff3e05ad 6440 gxineplugin_0.5.908-1_amd64.deb Files: fee26dd928f7e58c7b0f05f0876a218d 389444 video optional gxine_0.5.908-1_amd64.deb 09748f38d62730fabbd455f34af300af 6440 video optional gxineplugin_0.5.908-1_amd64.deb 6fb2cc7c85be1c8a1eee2c71ee3b719d 1472 video optional gxine_0.5.908-1.dsc a49618d8d1fdad9e7d15aee4cc5fd15f 917780 video optional gxine_0.5.908.orig.tar.xz e8019be3618920399ddfb5f8d6097208 11460 video optional gxine_0.5.908-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlNtcz8ACgkQsBKtjPGfWZ++awCfdMH1k4aE4B+OMd5E5T7XXjQm 2QIAn1j4pPbQyQ8yeJwA8HlDWkXc30T5 =dyO9 -END PGP SIGNATUREEnd Message---
Bug#747563: Missing dependency on gnome-online-miners
Package: gnome-documents Version: 3.12.0-1 Severity: serious Starting with gnome-documents 3.10, the miners were split out into a separate module called gnome-online-miners [0]. We need to package this module before moving gnome-documents 3.12 to unstable. [0] https://bugzilla.gnome.org/show_bug.cgi?id=703852 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-documents depends on: ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2 ii gir1.2-evince-3.03.12.1-1 ii gir1.2-gdata-0.0 0.15.0-3 ii gir1.2-glib-2.0 1.40.0-2 ii gir1.2-gnomedesktop-3.0 3.8.4-2 ii gir1.2-goa-1.0 3.12.1-1 ii gir1.2-gtk-3.0 3.12.1-1 ii gir1.2-tracker-0.16 0.16.2-1+b2 ii gir1.2-webkit-3.02.4.1-2 ii gir1.2-zpj-0.0 0.0.3-1+b1 ii gjs 1.36.1-2 ii libatk1.0-0 2.12.0-1 ii libc62.18-5 ii libcairo21.12.16-2 ii libevdocument3-4 3.12.1-1 ii libevview3-3 3.12.1-1 ii libgdata19 0.15.0-3 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgnome-desktop-3-7 3.8.4-2 ii libgoa-1.0-0b3.12.1-1 ii libgtk-3-0 3.12.1-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libtracker-miner-0.16-0 0.16.2-1+b2 ii libtracker-sparql-0.16-0 0.16.2-1+b2 ii libzapojit-0.0-0 0.0.3-1+b1 ii tracker 1.0.0-1 Versions of packages gnome-documents recommends: ii gnome-user-guide 3.8.2-1 ii unoconv 0.6-6 gnome-documents 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#747565: FTBFS on i386: failing test-suite
Source: libvirt Version: 1.2.4-1 Severity: serious libvirt FTBFS on i386 when running the test-suite. The failing test is FAIL: securityselinuxlabeltest Full build log at https://buildd.debian.org/status/fetch.php?pkg=libvirtarch=i386ver=1.2.4-1stamp=1399379486 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (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
Bug#747564: FTBFS on kfreebsd-*
Source: libvirt Version: 1.2.4-1 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd libvirt 1.2.4-1 FTBFS on kfreebsd-* # Add empty dirs so dh_install doesn't fail on kFreebsd until we have # Polkit/Systemd/systemtap/apparmor support mkdir -p debian/tmp/usr/share/polkit-1 \ debian/tmp/lib/systemd/system \ debian/tmp/usr/share/systemtap \ debian/tmp/etc/apparmor.d/ make[1]: Leaving directory `/«PKGBUILDDIR»' debian/rules override_dh_install make[1]: Entering directory `/«PKGBUILDDIR»' dh_install cp: cannot stat 'debian/tmp/usr/lib/libvirt/virt-aa-helper': No such file or directory dh_install: cp -a debian/tmp/usr/lib/libvirt/virt-aa-helper debian/libvirt-bin//usr/lib/libvirt/ returned exit code 1 make[1]: *** [override_dh_install] Error 2 make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [binary-arch] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=libvirtarch=kfreebsd-amd64ver=1.2.4-1stamp=1399379583 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (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: tracker 1.0 uploaded to unstable
Processing commands for cont...@bugs.debian.org: severity 741427 serious Bug #741427 [src:bognor-regis] bognor-regis: Please update for tracker-0.18 Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 741427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741427 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#714585: bug already been fixed
It seems that the bug has already been fixed. I think it can be closed now. Thank you anyway.
Processed: severity of 747535 is wishlist
Processing commands for cont...@bugs.debian.org: severity 747535 wishlist Bug #747535 [systemd-sysv] systemd-sysv: Ask before installing when upgrading to/installing jessie Severity set to 'wishlist' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 747535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747535 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#747555: [DRE-maint] Bug#747555: ruby-fog-core: trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/version.rb', which is also in package ruby-fog 1.22.0-1
Hi Axel, On Sat, May 10, 2014 at 12:26:00AM +0200, Axel Beckert wrote: Package: ruby-fog,ruby-fog-core Version: ruby-fog-core/1.21.1+gh-1 Version: ruby-fog/1.22.0-1 Severity: serious This is a very similar issue to https://bugs.debian.org/744010 but with a different file: Selecting previously unselected package ruby-fog-core. Preparing to unpack .../ruby-fog-core_1.21.1+gh-1_all.deb ... Unpacking ruby-fog-core (1.21.1+gh-1) ... dpkg: error processing archive /var/cache/apt/archives/ruby-fog-core_1.21.1+gh-1_all.deb (--unpack): trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/version.rb', which is also in package ruby-fog 1.22.0-1 Selecting previously unselected package ruby-fog-json. Preparing to unpack .../ruby-fog-json_1.0.0-1_all.deb ... Unpacking ruby-fog-json (1.0.0-1) ... Selecting previously unselected package ruby-fog-brightbox. Preparing to unpack .../ruby-fog-brightbox_0.0.2-1_all.deb ... Unpacking ruby-fog-brightbox (0.0.2-1) ... Preparing to unpack .../ruby-fog_1.22.0-2_all.deb ... Unpacking ruby-fog (1.22.0-2) over (1.22.0-1) ... Processing triggers for debian-security-support (2014.04.28) ... Processing triggers for man-db (2.6.7.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/ruby-fog-core_1.21.1+gh-1_all.deb Looks like a missing Replaces header or similar. Happened on both, amd64 as well as kfreebsd-i386. Thanks for the report. The file conflict between ruby-fog and ruby-fog-core has been fixed in ruby-fog 1.22.0-2. I am uploading a ruby-fog-core with Breaks/Replaces ruby-fog 1.22.0-1 to fix the upgrade path. Cheers, Cédric signature.asc Description: Digital signature
Bug#726817: marked as done (chrony: GPL-2-only program linking GPL-3+ libreadline6 on amd64)
Your message dated Sat, 10 May 2014 07:47:23 +0200 with message-id 536dbd6b.2070...@debian.org and subject line chrony in squeeze (amd64) has caused the Debian Bug report #726817, regarding chrony: GPL-2-only program linking GPL-3+ libreadline6 on amd64 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.) -- 726817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: chrony Severity: serious Version: 1.24-3+squeeze1 X-Debbugs-Cc: t...@security.debian.org, debian-rele...@lists.debian.org The security update for chrony links against libreadline6 on amd64. However chrony is licensed under GPL-2-only and libreadline6 is GPL-3-or-later. The buildd uploads still link against libreadline5 (GPL-2+). So it looks like the amd64 version was built in an unclean environment. So chrony needs either a, a binNMU on amd64 for the next point release, leaving the current version on security.d.o, or b, a sourceful upload that changes the build-depends to libreadline-gplv2-dev with no alternative (to require the GPL-2+ version). This could also replace the version currently in the security archive. Ansgar ---End Message--- ---BeginMessage--- Version: 1.24-3+squeeze1+b1 chrony in squeeze on amd64 was binNMU-ed (on 2013-10-22) and the rebuild package is in squeeze. Paul signature.asc Description: OpenPGP digital signature ---End Message---
