Bug#746029: ejabberd: only admin can connect after upgrade
Package: ejabberd Version: 2.1.11-1 Severity: grave Justification: renders package unusable Dear Maintainer, After an apt-get upgrade, no one except admin can connect to the ejabberd server. All users except admin get Fehler beim Einlesen von XML-Dateien. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ejabberd depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.52 ii erlang-asn11:17.0-dfsg-1 ii erlang-base [erlang-abi-15.b] 1:17.0-dfsg-1 ii erlang-crypto 1:17.0-dfsg-1 ii erlang-inets 1:17.0-dfsg-1 ii erlang-mnesia 1:17.0-dfsg-1 ii erlang-odbc1:17.0-dfsg-1 ii erlang-public-key 1:17.0-dfsg-1 ii erlang-ssl 1:17.0-dfsg-1 ii erlang-syntax-tools1:17.0-dfsg-1 ii libc6 2.18-4 ii libexpat1 2.1.0-4 ii libpam0g 1.1.8-3 ii libssl1.0.01.0.1g-3 ii openssl1.0.1g-3 ii ucf3.0027+nmu1 ii zlib1g 1:1.2.8.dfsg-1 ejabberd recommends no packages. Versions of packages ejabberd suggests: ii imagemagick 8:6.7.7.10+dfsg-1 pn libunix-syslog-perl none -- debconf information: ejabberd/password: (password omitted) ejabberd/verify: (password omitted) ejabberd/user: ejabberd/nomatch: ejabberd/hostname: localhost -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742990: News?
2014-04-26 20:36 GMT+02:00 Bastien ROUCARIES roucaries.bast...@gmail.com: On Fri, Apr 25, 2014 at 10:02 AM, Mathieu Parent math.par...@gmail.com wrote: Hello, Is anybody working on this bug? As ckeditor is marked for autoremoval from testing on 2014-05-13. NB: I have already uploaded the previous RC fix, but don't have enough time currently (already maintaining too many packages) It is quite harder than expected they use ckbuilder jar for building that is not open source and not released... That's unfortunate. But can't we use the upstream SVN as source without minifying the JS (or minifying using a tool already in the archive)? I'm afraid: if ckeditor is removed from testing, horde will lack its mail client (IMP). Regards -- Mathieu -- 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#742405: zookeeper ftbfs without openjdk
Processing control commands: severity -1 important Bug #742405 [src:zookeeper] zookeeper: ftbfs when gcj is default jdk Severity set to 'important' from 'serious' -- 742405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742405 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#742405: zookeeper ftbfs without openjdk
Control: severity -1 important Hi, On Sun, Mar 30, 2014 at 10:15:43PM +0100, Steven Chamberlain wrote: On 30/03/14 20:28, Tim Retout wrote: Right, but this does not comply with the Java policy, which requires default-jdk as the build dependency Thanks for pointing this out. I hadn't seen the rest of the thread on debian-java@. The versioned dependency and the removal of kfreebsd-* and sparc binaries makes sense now. Though, I hope default-jdk on kfreebsd can be changed back to openjdk-7 someday. The binaries were removed and zookeeper migrated to testing, so the severity of this bug can be lowered. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746032: systemd: Prevent system to boot
Package: systemd Version: 204-9 Severity: critical Justification: breaks the whole system Trying systemd for the frst time this moring and it breaks. It boots, mount the filesystem and then hang for 2or 3 mins and then I have the rescue prompt. I looked at the log as per indicated in the help message. Last message was that a binary /bin/ was missing but I do not remember whch one. Managed to start network (add to do ifdown eth0; ifup eth0) and reinstalled sysvinit-core and booted again. Tell me what information you need but I have no clue on how systemd works. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12.18 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-55 ii libacl1 2.2.52-1 ii libaudit11:2.3.6-1 ii libc62.18-4 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.0-3 ii libgcrypt11 1.5.3-4 ii libkmod2 16-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.2.2-1 ii libsystemd-daemon0 204-9 ii libsystemd-journal0 204-9 ii libsystemd-login0204-9 ii libudev1 204-9 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-55 ii udev 204-9 ii util-linux 2.20.1-5.7 Versions of packages systemd recommends: pn libpam-systemd none Versions of packages systemd suggests: pn systemd-ui none -- no debconf information 0 overridden configuration files found. == /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/anacron.service == /var/lib/systemd/deb-systemd-helper-enabled/cups.socket.dsh-also == /etc/systemd/system/sockets.target.wants/cups.socket == /var/lib/systemd/deb-systemd-helper-enabled/printer.target.wants/cups.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/binfmt-support.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups-browsed.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/dns-clean.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/privoxy.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/pppd-dns.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lm-sensors.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/avahi-daemon.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service == == /var/lib/systemd/deb-systemd-helper-enabled/sshd.service == == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.Avahi.service == == /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.socket.dsh-also == /etc/systemd/system/sockets.target.wants/avahi-daemon.socket == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/pcscd.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket == == /var/lib/systemd/deb-systemd-helper-enabled/pppd-dns.service.dsh-also == /etc/systemd/system/multi-user.target.wants/pppd-dns.service == /var/lib/systemd/deb-systemd-helper-enabled/privoxy.service.dsh-also == /etc/systemd/system/multi-user.target.wants/privoxy.service == /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also == /etc/systemd/system/multi-user.target.wants/ssh.service /etc/systemd/system/sshd.service == /var/lib/systemd/deb-systemd-helper-enabled/pcscd.socket.dsh-also == /etc/systemd/system/sockets.target.wants/pcscd.socket == /var/lib/systemd/deb-systemd-helper-enabled/atd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/atd.service == /var/lib/systemd/deb-systemd-helper-enabled/cups.path.dsh-also == /etc/systemd/system/multi-user.target.wants/cups.path == /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also == /etc/systemd/system/multi-user.target.wants/rsyslog.service /etc/systemd/system/syslog.service
Bug#746032: [Pkg-systemd-maintainers] Bug#746032: systemd: Prevent system to boot
Am 27.04.2014 10:40, schrieb Eric Valette: Package: systemd Version: 204-9 Severity: critical Justification: breaks the whole system Trying systemd for the frst time this moring and it breaks. It boots, mount the filesystem and then hang for 2or 3 mins and then I have the rescue prompt. I looked at the log as per indicated in the help message. Last message was that a binary /bin/ was missing but I do not remember whch one. Managed to start network (add to do ifdown eth0; ifup eth0) and reinstalled sysvinit-core and booted again. Tell me what information you need but I have no clue on how systemd works. Do all the filesystems listed in /etc/fstab actually exist? Do keep in mind that the no-auto fstab parameter is unknown to systemd, you should use noauto or nofail for devices which shouldn't block the boot process. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: found 714045 in 0.8.5-2.1
Processing commands for cont...@bugs.debian.org: found 714045 0.8.5-2.1 Bug #714045 [blcr-dkms] blcr-dkms: blcr module is not built on kernel 3.9.1 Marked as found in versions blcr/0.8.5-2.1. thanks Stopping processing here. Please contact me if you need assistance. -- 714045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714045 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#746032: [Pkg-systemd-maintainers] Bug#746032: systemd: Prevent system to boot
On 27/04/2014 10:54, Michael Biebl wrote: Am 27.04.2014 10:40, schrieb Eric Valette: Package: systemd Version: 204-9 Severity: critical Justification: breaks the whole system Trying systemd for the frst time this moring and it breaks. It boots, mount the filesystem and then hang for 2or 3 mins and then I have the rescue prompt. I looked at the log as per indicated in the help message. Last message was that a binary /bin/ was missing but I do not remember whch one. Managed to start network (add to do ifdown eth0; ifup eth0) and reinstalled sysvinit-core and booted again. Tell me what information you need but I have no clue on how systemd works. Do all the filesystems listed in /etc/fstab actually exist? No not the BACKUP file system Do keep in mind that the no-auto fstab parameter is unknown to systemd, you should use noauto or nofail for devices which shouldn't block the boot process. Michael Ok will replace no-auto with noauto and restart. BTW I created the /var/log/journald directory but apprently its a binary file. How can I see its content? -- eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 714045 is forwarded to https://upc-bugs.lbl.gov/bugzilla/show_bug.cgi?id=3199
Processing commands for cont...@bugs.debian.org: forwarded 714045 https://upc-bugs.lbl.gov/bugzilla/show_bug.cgi?id=3199 Bug #714045 [blcr-dkms] blcr-dkms: blcr module is not built on kernel 3.9.1 Set Bug forwarded-to-address to 'https://upc-bugs.lbl.gov/bugzilla/show_bug.cgi?id=3199'. thanks Stopping processing here. Please contact me if you need assistance. -- 714045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714045 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#746032: [Pkg-systemd-maintainers] Bug#746032: systemd: Prevent system to boot
On 27/04/2014 11:05, Eric Valette wrote: Do keep in mind that the no-auto fstab parameter is unknown to systemd, you should use noauto or nofail for devices which shouldn't block the boot process. Ok will replace no-auto with noauto and restart. BTW I created the /var/log/journald directory but apprently its a binary file. How can I see its content? That indeed fixed the boot problem. I have an error message saying /bin/plymouth does not exist but it does not harm. -- eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745956: marked as done (snmpd: new version of startup script fails on VPS which obviously do not have /proc/bus/pci)
Your message dated Sun, 27 Apr 2014 09:23:01 + with message-id e1welib-00048e...@franck.debian.org and subject line Bug#745956: fixed in net-snmp 5.7.2.1~dfsg-5 has caused the Debian Bug report #745956, regarding snmpd: new version of startup script fails on VPS which obviously do not have /proc/bus/pci 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.) -- 745956: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: snmpd Version: latest jessie Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading system got error installing snmpd. Trying to uninstall report weird problem deleting /run/snmpd.pid. Touch'ed it and only then got it uninstalled, weird. Trying to install back: root@de:~# apt-get install snmpd Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libpci3 libsnmp30 Suggested packages: snmptrapd The following NEW packages will be installed: libpci3 libsnmp30 snmpd 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/2263 kB of archives. After this operation, 5045 kB of additional disk space will be used. Do you want to continue? [Y/n] Preconfiguring packages ... Selecting previously unselected package libpci3:amd64. (Reading database ... 34626 files and directories currently installed.) Preparing to unpack .../libpci3_1%3a3.2.1-2_amd64.deb ... Unpacking libpci3:amd64 (1:3.2.1-2) ... Selecting previously unselected package libsnmp30:amd64. Preparing to unpack .../libsnmp30_5.7.2.1~dfsg-3_amd64.deb ... Unpacking libsnmp30:amd64 (5.7.2.1~dfsg-3) ... Selecting previously unselected package snmpd. Preparing to unpack .../snmpd_5.7.2.1~dfsg-3_amd64.deb ... Unpacking snmpd (5.7.2.1~dfsg-3) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up libpci3:amd64 (1:3.2.1-2) ... Setting up libsnmp30:amd64 (5.7.2.1~dfsg-3) ... Setting up snmpd (5.7.2.1~dfsg-3) ... adduser: Warning: The home directory `/var/lib/snmp' does not belong to the user you are currently creating. [] Starting SNMP services::pcilib: Cannot open /proc/bus/pci pcilib: Cannot find any working access method. invoke-rc.d: initscript snmpd, action start failed. dpkg: error processing package snmpd (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.18-4) ... Errors were encountered while processing: snmpd E: Sub-process /usr/bin/dpkg returned an error code (1) Trying to uninstall: root@de:~# dpkg -r snmpd (Reading database ... 34669 files and directories currently installed.) Removing snmpd (5.7.2.1~dfsg-3) ... [] Stopping SNMP services::start-stop-daemon: unable to stat //--retry (No such file or directory) rm: cannot remove '/run/snmpd.pid': No such file or directory invoke-rc.d: initscript snmpd, action stop failed. dpkg: error processing package snmpd (--remove): subprocess installed pre-removal script returned error exit status 1 [] Starting SNMP services::pcilib: Cannot open /proc/bus/pci pcilib: Cannot find any working access method. invoke-rc.d: initscript snmpd, action start failed. dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: snmpd -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.41-042stab085.20 (SMP w/1 CPU core) Locale: LANG=ru_RU.UTF-8, LC_CTYPE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages snmpd depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.52 ii libc6 2.18-4 ii libsnmp-base 5.7.2.1~dfsg-3 pn libsnmp30 none ii lsb-base 4.1+Debian12 snmpd recommends no packages. Versions of packages snmpd suggests: pn snmptrapd none ---End Message--- ---BeginMessage--- Source: net-snmp Source-Version: 5.7.2.1~dfsg-5 We believe that the bug you reported is fixed in the latest version of net-snmp, 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
Bug#746034: chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive
Package: chromium
Version: 33.0.1750.152-1
Justification: renders package unusable
Severity: grave
Dear Maintainer,
I cannot install the update 34.0.1847.116-1~deb7u1 because
it depends on libudev0 and libudev0 is no longer in the Debian testing
archive. I have marked the bug as grave as almost everybody who has
removed libudev0 would not be able to install this package.
$ aptitude search libudev
i A libudev-dev -
libudev development files
i A libudev1-
libudev shared library
As can be seen it's not there in the archive. I cannot update because
of the libudev0 dependancy. It should give dependancy as libudev1.
sudo aptitude install chromium chromium-inspector
The following packages will be upgraded:
chromium{b} chromium-inspector
2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 49.9 MB/50.6 MB of archives. After unpacking 12.7 MB will be freed.
The following packages have unmet dependencies:
chromium : Depends: libudev0 (= 146) which is a virtual package.
The following actions will resolve these dependencies:
Remove the following packages:
1) chromium
Leave the following dependencies unresolved:
2) chromium-inspector recommends chromium (= 10)
Accept this solution? [Y/n/q/?] q
$ aptitude show chromium=34.0.1847.116-1~deb7u1
Package: chromium
State: not installed
Automatically installed: no
Version: 34.0.1847.116-1~deb7u1
Priority: optional
Section: web
Maintainer: Debian Chromium Maintainers
pkg-chromium-ma...@lists.alioth.debian.org
Architecture: amd64
Uncompressed Size: 133 M
Depends: gconf-service, libasound2 (= 1.0.16), libatk1.0-0 (=
1.12.4), libc6 (= 2.11), libcairo2 (= 1.6.0), libcap2 (= 2.10),
libcups2 (= 1.4.0), libdbus-1-3 (= 1.2.14), libexpat1 (= 2.0.1),
libfontconfig1 (= 2.9.0), libfreetype6 (= 2.3.9), libgcc1 (=
1:4.1.1), libgconf-2-4 (= 2.31.1), libgcrypt11 (= 1.4.5),
libgdk-pixbuf2.0-0 (= 2.22.0), libglib2.0-0 (= 2.26.0),
libgnome-keyring0 (=3.2.2-2~), libgtk2.0-0 (= 2.24.0), libjpeg8
(= 8c), libnspr4 (= 2:4.9-2~), libnss3 (= 2:3.14.3), libpango1.0-0
(= 1.22.0), libspeechd2, libspeex1 (= 1.2~beta3-1), libstdc++6 (=
4.6), libudev0 (= 146), libx11-6 (= 2:1.4.99.1), libxcomposite1 (=
1:0.3-1), libxdamage1 (= 1:1.1), libxext6, libxfixes3, libxi6 (=
2:1.2.99.4), libxml2 (= 2.7.4), libxrender1, libxslt1.1 (= 1.1.25),
libxss1, libxtst6, xdg-utils, chromium-inspector
Suggests: chromium-l10n
Conflicts: chromium-browser ( 10.0.648.82~r75062-1~),
chromium-codecs-ffmpeg, chromium-codecs-ffmpeg-extra,
chromium-testsuite
Replaces: chromium-browser ( 10.0.648.82~r75062-1~),
chromium-codecs-ffmpeg, chromium-codecs-ffmpeg-extra,
chromium-testsuite
Provides: chromium-testsuite, gnome-www-browser, www-browser
Description: Google's open source chromium web browser
Chromium is an open-source browser project that aims to build a
safer, faster, and more stable way for all Internet users to
experience the
web.
Chromium serves as a base for Google Chrome, which is Chromium
rebranded (name and logo) with very few additions such as usage
tracking and an
auto-updater system.
This package contains the Chromium browser.
Homepage: http://www.chromium.org/Home
Tags: devel::interpreter, devel::lang:ecmascript, devel::runtime,
devel::web, implemented-in::c++, implemented-in::ecmascript,
interface::x11, network::client, protocol::TODO, protocol::ftp,
protocol::gopher, protocol::http, protocol::ipv6, protocol::ssl,
role::program, scope::application, uitoolkit::TODO, uitoolkit::gtk,
use::browsing, use::downloading, use::viewing, web::browser,
web::scripting, works-with-format::TODO, works-with-format::gif,
works-with-format::html, works-with-format::jpg,
works-with-format::json, works-with-format::mp3,
works-with-format::oggtheora, works-with-format::oggvorbis,
works-with-format::plaintext, works-with-format::png,
works-with-format::svg, works-with-format::xml,
works-with-format::xml:rss, works-with-format::xml:xslt,
works-with::audio, works-with::image, works-with::image:raster,
works-with::image:vector, works-with::text, works-with::video,
x11::application
Looking forward to the solution.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (600, 'testing'), (500, 'testing-updates'), (1,
'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 33.0.1750.152-1
ii gconf-service3.2.6-2
ii libasound2 1.0.27.2-3
ii libatk1.0-0 2.12.0-1
ii libc62.18-4
ii libcairo21.12.16-2
ii libcap2 1:2.22-1.2
ii libcups2 1.7.2-1
ii libdbus-1-3 1.8.0-3
ii libexpat12.1.0-4
ii libfontconfig1
Bug#745307: FTBFS with ocamlgraph 1.8.4
Le 2014-04-20 13:13, Stéphane Glondu a écrit : Source: dose3 Version: 3.1.3-7 Severity: serious Dear Maintainer, dose3 fails to build with the latest version of ocamlgraph (1.8.4). It seems that ocamlgraph's upstream reverted the specific part that changed its API. Thus, dose3 should build just fine now using the newly released ocamlgraph 1.8.5, which I just uploaded. I'll close this bug later, when ocamlgraph/1.8.5 will be available on all archs. -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746032: marked as done (systemd: Prevent system to boot)
Your message dated Sun, 27 Apr 2014 11:35:41 +0200 with message-id 535ccf6d.2090...@debian.org and subject line Re: Bug#746032: [Pkg-systemd-maintainers] Bug#746032: systemd: Prevent system to boot has caused the Debian Bug report #746032, regarding systemd: Prevent system to boot 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.) -- 746032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 204-9 Severity: critical Justification: breaks the whole system Trying systemd for the frst time this moring and it breaks. It boots, mount the filesystem and then hang for 2or 3 mins and then I have the rescue prompt. I looked at the log as per indicated in the help message. Last message was that a binary /bin/ was missing but I do not remember whch one. Managed to start network (add to do ifdown eth0; ifup eth0) and reinstalled sysvinit-core and booted again. Tell me what information you need but I have no clue on how systemd works. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12.18 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-55 ii libacl1 2.2.52-1 ii libaudit11:2.3.6-1 ii libc62.18-4 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.0-3 ii libgcrypt11 1.5.3-4 ii libkmod2 16-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.2.2-1 ii libsystemd-daemon0 204-9 ii libsystemd-journal0 204-9 ii libsystemd-login0204-9 ii libudev1 204-9 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-55 ii udev 204-9 ii util-linux 2.20.1-5.7 Versions of packages systemd recommends: pn libpam-systemd none Versions of packages systemd suggests: pn systemd-ui none -- no debconf information 0 overridden configuration files found. == /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/anacron.service == /var/lib/systemd/deb-systemd-helper-enabled/cups.socket.dsh-also == /etc/systemd/system/sockets.target.wants/cups.socket == /var/lib/systemd/deb-systemd-helper-enabled/printer.target.wants/cups.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/binfmt-support.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups-browsed.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/dns-clean.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/privoxy.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/pppd-dns.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lm-sensors.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/avahi-daemon.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service == == /var/lib/systemd/deb-systemd-helper-enabled/sshd.service == == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.Avahi.service == == /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.socket.dsh-also == /etc/systemd/system/sockets.target.wants/avahi-daemon.socket == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/pcscd.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket == == /var/lib/systemd/deb-systemd-helper-enabled/pppd-dns.service.dsh-also == /etc/systemd/system/multi-user.target.wants/pppd-dns.service ==
Processed: retitle 746032 to missing filesystems with no-auto option block boot, systemd only understands noauto or nofail
Processing commands for cont...@bugs.debian.org:
retitle 746032 missing filesystems with no-auto option block boot, systemd
only understands noauto or nofail
Bug #746032 {Done: Michael Biebl bi...@debian.org} [systemd] systemd: Prevent
system to boot
Changed Bug title to 'missing filesystems with no-auto option block boot,
systemd only understands noauto or nofail' from 'systemd: Prevent system to
boot'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
746032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746032
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#746035: systemd: Systemd prevents to reboot
Package: systemd Version: 204-9 Severity: critical Justification: breaks unrelated software After the boot, the shutdown/restart. I just get a blinking cursor forever and I shall press the reset button. Bad for disks as I have no clue where it fails as nothing is printed on console. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12.18 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-55 ii libacl1 2.2.52-1 ii libaudit11:2.3.6-1 ii libc62.18-4 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.0-3 ii libgcrypt11 1.5.3-4 ii libkmod2 16-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.2.2-1 ii libsystemd-daemon0 204-9 ii libsystemd-journal0 204-9 ii libsystemd-login0204-9 ii libudev1 204-9 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-55 ii udev 204-9 ii util-linux 2.20.1-5.7 Versions of packages systemd recommends: pn libpam-systemd none Versions of packages systemd suggests: pn systemd-ui none -- no debconf information 0 overridden configuration files found. systemctl-dump.txt Description: inode/empty == /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also == /etc/systemd/system/multi-user.target.wants/anacron.service == /var/lib/systemd/deb-systemd-helper-enabled/cups.socket.dsh-also == /etc/systemd/system/sockets.target.wants/cups.socket == /var/lib/systemd/deb-systemd-helper-enabled/printer.target.wants/cups.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/binfmt-support.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups-browsed.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/dns-clean.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/privoxy.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/pppd-dns.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lm-sensors.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/avahi-daemon.service == == /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service == == /var/lib/systemd/deb-systemd-helper-enabled/sshd.service == == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.Avahi.service == == /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.socket.dsh-also == /etc/systemd/system/sockets.target.wants/avahi-daemon.socket == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/pcscd.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket == == /var/lib/systemd/deb-systemd-helper-enabled/pppd-dns.service.dsh-also == /etc/systemd/system/multi-user.target.wants/pppd-dns.service == /var/lib/systemd/deb-systemd-helper-enabled/privoxy.service.dsh-also == /etc/systemd/system/multi-user.target.wants/privoxy.service == /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also == /etc/systemd/system/multi-user.target.wants/ssh.service /etc/systemd/system/sshd.service == /var/lib/systemd/deb-systemd-helper-enabled/pcscd.socket.dsh-also == /etc/systemd/system/sockets.target.wants/pcscd.socket == /var/lib/systemd/deb-systemd-helper-enabled/atd.service.dsh-also == /etc/systemd/system/multi-user.target.wants/atd.service == /var/lib/systemd/deb-systemd-helper-enabled/cups.path.dsh-also == /etc/systemd/system/multi-user.target.wants/cups.path == /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also == /etc/systemd/system/multi-user.target.wants/rsyslog.service /etc/systemd/system/syslog.service /etc/systemd/system/multi-user.target.wants/rsyslog.service /etc/systemd/system/syslog.service == /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also == /etc/systemd/system/sockets.target.wants/ssh.socket == /var/lib/systemd/deb-systemd-helper-enabled/cups-browsed.service.dsh-also
Bug#746036: iceowl-extension: Event not shown when calendar view refreshed.
Package: iceowl-extension Version: 24.4.0-1 Severity: grave Justification: renders package unusable Using the default local calendar (home), I create an event and save it. It is shown in the Week view. If I switch tabs, synchronise, switch views, and the return to the view, it has disappeared. It seems that any refresh of the view causes the event to disappear. If I select it from the events list above the view and resave it, the event reappears until the next refresh. The event remains visible in the Multiweek view, but shows the disappearing behaviour in Day, Week and Month views. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iceowl-extension depends on: ii icedove 24.4.0-1 ii libc62.18-4 ii libgcc1 1:4.8.2-16 ii libnspr4 2:4.10.4-1 ii libnspr4-0d 2:4.10.4-1 ii libstdc++6 4.8.2-16 Versions of packages iceowl-extension recommends: ii calendar-google-provider 24.4.0-1 Versions of packages iceowl-extension suggests: ii fonts-lyx 2.0.6-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 744921 is normal
Processing commands for cont...@bugs.debian.org: severity 744921 normal Bug #744921 [spamassassin] spamassassin: Daily cron script wants to set a shared library world writable Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 744921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744921 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#746035: unmounting /var and /usr fails on journal
Looking at the log I just found theses messages. As I created /var/log/journal to be able to read the log after failing boot I may understand for /var but I have no clue if it will be sufficient to remove it. On the other hand if I have to remove persistent log how to debug shutdown? -- eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 746020
Processing commands for cont...@bugs.debian.org: tags 746020 + pending Bug #746020 [gmp] gmp: FTBFS on hppa: incorrect symbols Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 746020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746020 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#745895: marked as done (does not compile against Varnish 4.0.0)
Your message dated Sun, 27 Apr 2014 10:20:28 + with message-id e1wemcc-0004as...@franck.debian.org and subject line Bug#745895: fixed in nagios-plugins-contrib 10.20140427 has caused the Debian Bug report #745895, regarding does not compile against Varnish 4.0.0 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.) -- 745895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nagios-plugins-contrib Version: 9.20140106 Severity: serious Varnish 4 changed its API. nagios-plugins-contrib needs to be adjusted to compile against the current libvarnishapi-dev in unstable. ---End Message--- ---BeginMessage--- Source: nagios-plugins-contrib Source-Version: 10.20140427 We believe that the bug you reported is fixed in the latest version of nagios-plugins-contrib, 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. Bernd Zeimetz b...@debian.org (supplier of updated nagios-plugins-contrib 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, 27 Apr 2014 11:25:11 +0200 Source: nagios-plugins-contrib Binary: nagios-plugins-contrib Architecture: source amd64 Version: 10.20140427 Distribution: unstable Urgency: medium Maintainer: Debian Nagios Maintainer Group pkg-nagios-de...@lists.alioth.debian.org Changed-By: Bernd Zeimetz b...@debian.org Description: nagios-plugins-contrib - Plugins for nagios compatible monitoring systems Closes: 727468 742877 744248 744922 745895 Changes: nagios-plugins-contrib (10.20140427) unstable; urgency=medium . [ Jan Wagner ] * [0029d09d] check_email_delivery: Use full binary path instead of $ macro in command definition . [ Evgeni Golov ] * [1028de53] use = instead of == in shell comparisons fixes /bin/sh: 4: [: dh_auto_clean: unexpected operator for /bin/sh != /bin/bash . [ Bernd Zeimetz ] * [6bc6ae0e] Merge pull request #39 from evgeni/no-bashisms use = instead of == in shell comparisons . [ Jan Wagner ] * [92a64933] check_raid: Update to latest git version * [646ae3cf] check_ssl_cert: Update to 1.16.0 * [5810c290] check_whois: Update to 1.15 * [62ed2f18] check_httpd_status: Update to rev148 * [b5c5becf] check_mongodb: Update copyright file. Include full copyright to make lintian happy. * [64e5aa8b] check_mysql_health: Update copyright file. Add reference to GPL license file * [ab9066d2] check_hpasm: Update copyright file. Add reference to GPL license file * [a0a47d2a] check_memory: Update copyright file. Update FSF address * [0bbd4521] check_rbl: Update copyright file. Cosmetical changes * [0f533e19] Add '--with autoreconf' to dh calls (Closes: #727468) - Build-depend on dh-autoreconf - Add check_varnish/automake_foreign patch - Specify autoreconf (sub-)dirs in debian/autoreconf * [19c052cc] check_multipath: Update to 0.2.0 * [5c94f9c5] Add Travis-CI configuration . [ Stanislav German-Evtushenko ] * [b04bdeb0] check_drbd: add check for oos and cosmetic. 1) add check for out of sync sectors (report WARNING for non-zero value) 2) cosmetic: sort device list while processing * [13ace27b] small fix: oos is in KiB and not sectors . [ Jan Wagner ] * [bc434662] check_mongo: Update to latest git version * [dbd5989c] check_raid: Update to latest git version * [3100e689] check_ssl_cert: Update to 1.16.1 (No source changes) * [a7e727c8] check_raid: Update to latest git version (Closes: #742877) * [8fcc4d95] check_ssl_cert: Update to 1.16.1 (No source changes) * [1d17b5da] Update VCS-* field to uncanonical URI * [5529d605] check_memory: Update to new upstream source * [18a708fb] check_memory: Update to version 1.0.1 * [b88fd4ae] check_snmp_time: Preventing to use first person in package description * [dfbe25c3] Merge 0f533e1959 and f4cc012a82 into debian/control.in * [5a2dff52] Updating debian/copyright and debian/control * [dfb170cb] Updating standards version to 3.9.5, no changes needed
Bug#742515: blktap-dkms: diff for NMU version 2.0.93-0.2
tags 742515 + patch tags 742515 + pending thanks Dear maintainer, I've prepared an NMU for blktap-dkms (versioned as 2.0.93-0.2) and uploaded it directly to the archive as discussed on IRC. Regards. diff -Nru blktap-dkms-2.0.93/debian/changelog blktap-dkms-2.0.93/debian/changelog --- blktap-dkms-2.0.93/debian/changelog 2013-11-18 15:37:48.0 +0100 +++ blktap-dkms-2.0.93/debian/changelog 2014-04-27 12:13:50.0 +0200 @@ -1,3 +1,11 @@ +blktap-dkms (2.0.93-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * Add patch from upstream to support Linux kernels = 3.7. +Closes: #742515 + + -- Evgeni Golov evg...@debian.org Sun, 27 Apr 2014 12:10:36 +0200 + blktap-dkms (2.0.93-0.1) unstable; urgency=high * Non-maintainer upload. diff -Nru blktap-dkms-2.0.93/debian/patches/fix-vm-reserved.patch blktap-dkms-2.0.93/debian/patches/fix-vm-reserved.patch --- blktap-dkms-2.0.93/debian/patches/fix-vm-reserved.patch 1970-01-01 01:00:00.0 +0100 +++ blktap-dkms-2.0.93/debian/patches/fix-vm-reserved.patch 2014-04-27 12:10:30.0 +0200 @@ -0,0 +1,43 @@ +From: Vincent Bernardoff vincent.bernard...@citrix.com +Date: Tue, 26 Feb 2013 16:03:35 + +Origin: upstream, https://github.com/xen-org/blktap-dkms/commit/3bd35d662de12139b7ed5b6dc1076a231a651d10 +Bug-Debian: https://bugs.debian.org/742515 +Subject: [PATCH] Changed flag VM_RESERVED to VM_DONTDUMP to provide + compatibility with Linux 3.7 onwards. + +Index: blktap-dkms-2.0.93/ring.c +=== +--- blktap-dkms-2.0.93.orig/ring.c 2014-04-27 12:10:05.858102759 +0200 blktap-dkms-2.0.93/ring.c 2014-04-27 12:10:05.854102721 +0200 +@@ -28,6 +28,13 @@ + #include linux/mman.h + #include linux/mm.h + ++/* VM_RESERVED has disappeared starting from Linux 3.7 and has been ++ * replaced by VM_DONTDUMP since then. ++ */ ++#ifndef VM_DONTDUMP ++#define VM_DONTDUMP VM_RESERVED ++#endif ++ + #include blktap.h + + int blktap_ring_major; +@@ -436,7 +443,7 @@ + } + + vma-vm_flags |= VM_DONTCOPY; +- vma-vm_flags |= VM_RESERVED; ++ vma-vm_flags |= VM_DONTDUMP; + + return 0; + } +@@ -472,7 +479,7 @@ + vma-vm_private_data = tap; + + vma-vm_flags |= VM_DONTCOPY; +- vma-vm_flags |= VM_RESERVED; ++ vma-vm_flags |= VM_DONTDUMP; + + vma-vm_ops = blktap_ring_vm_operations; + diff -Nru blktap-dkms-2.0.93/debian/patches/series blktap-dkms-2.0.93/debian/patches/series --- blktap-dkms-2.0.93/debian/patches/series 2013-11-18 15:27:56.0 +0100 +++ blktap-dkms-2.0.93/debian/patches/series 2014-04-27 12:07:43.0 +0200 @@ -1 +1,2 @@ fixes-DEST_MODULE_LOCATION-in-dkms.conf.patch +fix-vm-reserved.patch
Processed: blktap-dkms: diff for NMU version 2.0.93-0.2
Processing commands for cont...@bugs.debian.org: tags 742515 + patch Bug #742515 [blktap-dkms] blktap-dkms: blktapblktap kernel module failed to build Added tag(s) patch. tags 742515 + pending Bug #742515 [blktap-dkms] blktap-dkms: blktapblktap kernel module failed to build Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 742515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#746035: systemd: Systemd prevents to reboot
Processing commands for cont...@bugs.debian.org: tags 746035 moreinfo Bug #746035 [systemd] systemd: Systemd prevents to reboot Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 746035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746035 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#742515: marked as done (blktap-dkms: blktapblktap kernel module failed to build)
Your message dated Sun, 27 Apr 2014 10:33:37 + with message-id e1wemov-0008m6...@franck.debian.org and subject line Bug#742515: fixed in blktap-dkms 2.0.93-0.2 has caused the Debian Bug report #742515, regarding blktap-dkms: blktapblktap kernel module failed to build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 742515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: blktap-dkms Version: 2.0.93-0.1 Severity: serious Justification: fails to build from source (but built successfully in the past) blktap fails to build on kernel 3.13 and probably older kernels as well. According to this bug: https://bugs.launchpad.net/ubuntu/+source/blktap-dkms/+bug/1245009 VM_RESERVED is deprecated as of 3.7. Building with the patch described in that bug allows for blktap to build properly. Diff for reference: --- ring.c.orig 2013-10-26 23:53:39.3 +0900 +++ ring.c 2013-10-26 20:35:26.30100 +0900 @@ -39,6 +39,10 @@ */ #define RING_PAGES 1 +#ifndef VM_RESERVED +# define VM_RESERVED (VM_DONTEXPAND | VM_DONTDUMP) +#endif + #define BLKTAP_INFO_SIZE_AT(_memb) \ offsetof(struct blktap_device_info, _memb) + \ sizeof(((struct blktap_device_info*)0)-_memb) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages blktap-dkms depends on: ii dkms2.2.0.3-1.2 ii libc6-dev 2.18-4 ii linux-libc-dev 3.13.5-1 Versions of packages blktap-dkms recommends: ii linux-headers-amd64 3.13+56 blktap-dkms suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: blktap-dkms Source-Version: 2.0.93-0.2 We believe that the bug you reported is fixed in the latest version of blktap-dkms, 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 742...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Evgeni Golov evg...@debian.org (supplier of updated blktap-dkms package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 27 Apr 2014 12:10:36 +0200 Source: blktap-dkms Binary: blktap-dkms Architecture: source amd64 Version: 2.0.93-0.2 Distribution: unstable Urgency: medium Maintainer: Debian Xen Team pkg-xen-de...@lists.alioth.debian.org Changed-By: Evgeni Golov evg...@debian.org Description: blktap-dkms - Xen API blktap kernel component DKMS package Closes: 742515 Changes: blktap-dkms (2.0.93-0.2) unstable; urgency=medium . * Non-maintainer upload. * Add patch from upstream to support Linux kernels = 3.7. Closes: #742515 Checksums-Sha1: c80db10b53ff540aec502fdd5a896b7fd846d993 1979 blktap-dkms_2.0.93-0.2.dsc a0a1b630913195b3b1c23f3f46e02b19423b180f 5844 blktap-dkms_2.0.93-0.2.debian.tar.xz d7e4ca5432f262a88a4a74bf650a85e291fa51c2 18068 blktap-dkms_2.0.93-0.2_amd64.deb Checksums-Sha256: 05e967a84b8d9fda1532923a81091d3c38b94cd5d5c5dc8069e623fb0028b38f 1979 blktap-dkms_2.0.93-0.2.dsc 6427012bc33996e93bb4216ff7482f2c712d492d4399bf4d9e37ffd2be411121 5844 blktap-dkms_2.0.93-0.2.debian.tar.xz 3e3d9f9ecb42add329cf088844045ed8b9a5a1190938d341d6cf07488f28188c 18068 blktap-dkms_2.0.93-0.2_amd64.deb Files: 684a8a2bc71cfc8b249da6122b40d88a 18068 kernel optional blktap-dkms_2.0.93-0.2_amd64.deb f89a3811324d2f34953c200ece1a024e 1979 kernel optional blktap-dkms_2.0.93-0.2.dsc 779bf067739e561ef7fbfaad8020ec12 5844 kernel optional blktap-dkms_2.0.93-0.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTXNp1AAoJEKGwm0IzOWHonOYP/2+RSfxYf5qMuDTxPcpYmrUv YOsjLcpEUWTsrM3WlA76w/Ajns7mWVan6glUfHNLsB4L5cChzBZVCNJ9lWsUxStF g3Q/6zIquHUUMKDrGesTEqxbG3zOWXCZGQySBgrxbqwwKzX978ktot8Cmlf0cAcW YdXNi/h2sFVXYQUVIHQYGQ53cqTkQr4HJ7h9mf2SP5R8sar7y6ekPGn2qGBWVVO4 fnOnbQtHAVEucob82i38NY3tED3vkR8OzuFtKbHsTUWhOgG8wN+g8JCkSdAPXLcp hWbG1IRAIR4/pfqb+za5dR6tNr/birN+y/xCpBpiCAzbRfPtuy7U7goRxYvbwjtY
Bug#746035: systemd: Systemd prevents to reboot
tags 746035 moreinfo thanks Am 27.04.2014 11:42, schrieb Eric Valette: Package: systemd Version: 204-9 Severity: critical Justification: breaks unrelated software After the boot, the shutdown/restart. I just get a blinking cursor forever and I shall press the reset button. Bad for disks as I have no clue where it fails as nothing is printed on console. Please remove the quite kernel command line to get a more verbose log. I'd also suggest to enable the debug-shell.service. You can then switch to vt9 on shutdown and examine where the system hangs with systemctl list-jobs. The upstream wiki [0] has a section about Diagnosing Shutdown Problems http://freedesktop.org/wiki/Software/systemd/Debugging/ Please follow those instructions and let us know at which service/unit the system blocks. There should be a timeout on shutdown, so it shouldn't block forever. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#746039: xul-ext-sieve: version in wheezy is not compatible with new icedove
Package: xul-ext-sieve Version: 0.1.14-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, With the latest security update for for icedove, the user interface items for managing sieve scripts aren't there, even though the extension is installed. On jessie it works with the newer version of the package. -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xul-ext-sieve depends on: ii icedove 24.4.0-1~deb7u1 xul-ext-sieve recommends no packages. xul-ext-sieve 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#745307: FTBFS with ocamlgraph 1.8.4
On Sun, Apr 27, 2014 at 11:19:40AM +0200, Mehdi Dogguy wrote: Le 2014-04-20 13:13, Stéphane Glondu a écrit : Source: dose3 Version: 3.1.3-7 Severity: serious Dear Maintainer, dose3 fails to build with the latest version of ocamlgraph (1.8.4). It seems that ocamlgraph's upstream reverted the specific part that changed its API. Thus, dose3 should build just fine now using the newly released ocamlgraph 1.8.5, which I just uploaded. I'll close this bug later, when ocamlgraph/1.8.5 will be available on all archs. OK, merci. The next upload of dose3 will exclude in its build-dependency libocamlgraph-ocaml-dev 1.8.4-1 (since this will also be needed for dose 3.2). Cheers -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745307: FTBFS with ocamlgraph 1.8.4
Le 2014-04-27 12:41, Ralf Treinen a écrit : On Sun, Apr 27, 2014 at 11:19:40AM +0200, Mehdi Dogguy wrote: Le 2014-04-20 13:13, Stéphane Glondu a écrit : Source: dose3 Version: 3.1.3-7 Severity: serious Dear Maintainer, dose3 fails to build with the latest version of ocamlgraph (1.8.4). It seems that ocamlgraph's upstream reverted the specific part that changed its API. Thus, dose3 should build just fine now using the newly released ocamlgraph 1.8.5, which I just uploaded. I'll close this bug later, when ocamlgraph/1.8.5 will be available on all archs. OK, merci. The next upload of dose3 will exclude in its build-dependency libocamlgraph-ocaml-dev 1.8.4-1 (since this will also be needed for dose 3.2). Can you be more specific about the will exclude in its build-dependency libocamlgraph-ocaml-dev 1.8.4-1 part please? What does it mean technically? IMHO, it is enough to bump the build-dep to 1.8.5-1~ and not do anything else. Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746035: systemd: Systemd prevents to reboot
On 27/04/2014 12:43, Michael Biebl wrote: Please remove the quite kernel command line to get a more verbose log. I'd also suggest to enable the debug-shell.service. You can then switch to vt9 on shutdown and examine where the system hangs with systemctl list-jobs. The upstream wiki [0] has a section about Diagnosing Shutdown Problems http://freedesktop.org/wiki/Software/systemd/Debugging/ Please follow those instructions and let us know at which service/unit the system blocks. Actually its samba. I have a message that says something along a LSB startup job is running and it points to smbd and nmbd. Actually even with sysv init system there is a problem on shutdown as samba stop script seems to be called twice. Its a bug in samba start stop logic that was introduced with samba4 probably as I have it actaully on all my debian machines (more than 5...). I bet it has something to do with network up script but cannot find where. There should be a timeout on shutdown, so it shouldn't block forever. Yes indeed. But it is unusually long! -- eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tribler: diff for NMU version 6.2.0+git20130731.149555fa-1.1
Processing commands for cont...@bugs.debian.org: tags 721108 + patch Bug #721108 [tribler] tribler: depends on ffmpeg which is going away Added tag(s) patch. tags 721108 + pending Bug #721108 [tribler] tribler: depends on ffmpeg which is going away Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 721108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721108 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#721108: tribler: diff for NMU version 6.2.0+git20130731.149555fa-1.1
tags 721108 + patch tags 721108 + pending thanks Dear maintainer, I've prepared an NMU for tribler (versioned as 6.2.0+git20130731.149555fa-1.1) and will ask some DD to upload it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru tribler-6.2.0+git20130731.149555fa/debian/changelog tribler-6.2.0+git20130731.149555fa/debian/changelog --- tribler-6.2.0+git20130731.149555fa/debian/changelog 2013-09-20 18:13:07.0 +0200 +++ tribler-6.2.0+git20130731.149555fa/debian/changelog 2014-04-26 14:16:14.0 +0200 @@ -1,3 +1,11 @@ +tribler (6.2.0+git20130731.149555fa-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Use avconf instead of ffmpeg. See patch use-libav-instead-of-ffmpeg.patch +(Closes: #721108) and change dependency accordingly to libav-tools + + -- Tobias Frost t...@coldtobi.de Sat, 26 Apr 2014 14:15:52 +0200 + tribler (6.2.0+git20130731.149555fa-1) unstable; urgency=low * New upstream release diff -Nru tribler-6.2.0+git20130731.149555fa/debian/control tribler-6.2.0+git20130731.149555fa/debian/control --- tribler-6.2.0+git20130731.149555fa/debian/control 2013-09-20 20:36:12.0 +0200 +++ tribler-6.2.0+git20130731.149555fa/debian/control 2014-04-26 14:00:37.0 +0200 @@ -12,7 +12,7 @@ Package: tribler Architecture: all -Depends: ffmpeg, +Depends: libav-tools, libjs-mootools, python-apsw, python-feedparser, diff -Nru tribler-6.2.0+git20130731.149555fa/debian/patches/series tribler-6.2.0+git20130731.149555fa/debian/patches/series --- tribler-6.2.0+git20130731.149555fa/debian/patches/series1970-01-01 01:00:00.0 +0100 +++ tribler-6.2.0+git20130731.149555fa/debian/patches/series2014-04-26 13:59:17.0 +0200 @@ -0,0 +1 @@ +use-libav-instead-of-ffmpeg.patch diff -Nru tribler-6.2.0+git20130731.149555fa/debian/patches/use-libav-instead-of-ffmpeg.patch tribler-6.2.0+git20130731.149555fa/debian/patches/use-libav-instead-of-ffmpeg.patch --- tribler-6.2.0+git20130731.149555fa/debian/patches/use-libav-instead-of-ffmpeg.patch 1970-01-01 01:00:00.0 +0100 +++ tribler-6.2.0+git20130731.149555fa/debian/patches/use-libav-instead-of-ffmpeg.patch 2014-04-26 14:04:08.0 +0200 @@ -0,0 +1,16 @@ +Description: Use libav-tools instead of ffmpeg +Forwarded: not-needed +Applied-Upstream: https://github.com/whirm/tribler/commit/00a03bf882eff81865a61c5415b45adfc91f3660 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/Tribler/Core/SessionConfig.py b/Tribler/Core/SessionConfig.py +@@ -49,7 +49,7 @@ + if sys.platform == 'win32': + ffmpegname = ffmpeg.exe + else: +-ffmpegname = ffmpeg ++ffmpegname = avconv + + ffmpegpath = find_prog_in_PATH(ffmpegname) + if ffmpegpath is None: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746025: libsemanage: FTBFS: ruby.h: No such file or directory
control: tags -1 +patch
Hi,
gem2deb has already drop ruby1.9.1 and it causes this FTBFS.
Attached patch would fix this, could you check and apply it, please?
--
Regards,
Hideki Yamane henrich @ debian.or.jp/org
http://wiki.debian.org/HidekiYamane
diff -Nru libsemanage-2.2/debian/changelog libsemanage-2.2/debian/changelog
--- libsemanage-2.2/debian/changelog 2013-11-02 07:24:45.0 +0900
+++ libsemanage-2.2/debian/changelog 2014-04-27 20:23:45.0 +0900
@@ -1,3 +1,12 @@
+libsemanage (2.2-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/{rules,ruby-semanage.install}
+- remove ruby1.9.1 (however, it's just a workaround since it specifies
+ only ruby2.0, and we'll move to ruby2.1)
+
+ -- Hideki Yamane henr...@debian.org Sun, 27 Apr 2014 20:13:32 +0900
+
libsemanage (2.2-1) unstable; urgency=low
* Team upload.
diff -Nru libsemanage-2.2/debian/ruby-semanage.install libsemanage-2.2/debian/ruby-semanage.install
--- libsemanage-2.2/debian/ruby-semanage.install 2013-11-02 07:24:45.0 +0900
+++ libsemanage-2.2/debian/ruby-semanage.install 2014-04-27 20:19:07.0 +0900
@@ -1,2 +1 @@
-usr/lib/ruby/vendor_ruby/*/*/semanage.so
usr/lib/*/ruby/vendor_ruby/*/semanage.so
diff -Nru libsemanage-2.2/debian/rules libsemanage-2.2/debian/rules
--- libsemanage-2.2/debian/rules 2013-11-02 07:24:45.0 +0900
+++ libsemanage-2.2/debian/rules 2014-04-27 20:13:30.0 +0900
@@ -25,9 +25,6 @@
PYPREFIX=python-$$version; \
done;
- $(MAKE) -C src rubywrap RUBY=ruby1.9.1 RUBYLIBVER=1.9.1 \
- RUBYINC=-I/usr/include/ruby-1.9.1/ -I/usr/include/ruby-1.9.1/\$${RUBYPLATFORM}/
-
$(MAKE) -C src rubywrap RUBY=ruby2.0 RUBYLIBVER=2.0.0 \
RUBYINC=-I/usr/include/ruby-2.0.0/ -I/usr/include/\$${RUBYPLATFORM}/ruby-2.0.0/
endif
@@ -44,9 +41,6 @@
PYPREFIX=python-$$version; \
done;
- $(MAKE) -C src install-rubywrap RUBY=ruby1.9.1 RUBYLIBVER=1.9.1 DESTDIR=${CURDIR}/debian/tmp \
- RUBYINSTALL=${CURDIR}/debian/tmp/usr/lib/ruby/vendor_ruby/\$${RUBYLIBVER}/\$${RUBYPLATFORM};
-
$(MAKE) -C src install-rubywrap RUBY=ruby2.0 RUBYLIBVER=2.0.0 DESTDIR=${CURDIR}/debian/tmp \
RUBYINSTALL=${CURDIR}/debian/tmp/usr/lib/\$${RUBYPLATFORM}/ruby/vendor_ruby/\$${RUBYLIBVER};
endif
Processed: Re: libsemanage: FTBFS: ruby.h: No such file or directory
Processing control commands: tags -1 +patch Bug #746025 [src:libsemanage] libsemanage: FTBFS: ruby.h: No such file or directory Added tag(s) patch. -- 746025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746025 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#746035: systemd: Systemd prevents to reboot
Am 27.04.2014 13:12, schrieb Eric Valette: Actually its samba. I have a message that says something along a LSB startup job is running and it points to smbd and nmbd. Actually even with sysv init system there is a problem on shutdown as samba stop script seems to be called twice. Its a bug in samba start stop logic that was introduced with samba4 probably as I have it actaully on all my debian machines (more than 5...). I bet it has something to do with network up script but cannot find where. This bug is known bug in samba, debugged and filed as [0] Michael [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739887 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: libkolab: diff for NMU version 0.4.2-7.1
Processing commands for cont...@bugs.debian.org: tags 745598 + patch Bug #745598 [src:libkolab] src:libkolab: FTBFS in dh_python2 (missing Build-Conflicts?) Added tag(s) patch. tags 745598 + pending Bug #745598 [src:libkolab] src:libkolab: FTBFS in dh_python2 (missing Build-Conflicts?) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 745598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745598 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#745598: libkolab: diff for NMU version 0.4.2-7.1
tags 745598 + patch tags 745598 + pending thanks Dear maintainer, The problem is that cmake finds Python 3 and prefers that over Python 2 when building the extension. Build-Conflicting python3-dev would be a solution. Or we could tell cmake to use Python 2.7, which I prefer, as Build-Conflics are ugly ;) I've prepared an NMU for libkolab (versioned as 0.4.2-7.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should cancel it, if you want the conflicts fix instead. Regards. diff -Nru libkolab-0.4.2/debian/changelog libkolab-0.4.2/debian/changelog --- libkolab-0.4.2/debian/changelog 2013-08-28 20:21:32.0 +0200 +++ libkolab-0.4.2/debian/changelog 2014-04-27 13:16:32.0 +0200 @@ -1,3 +1,11 @@ +libkolab (0.4.2-7.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build explicitely against Python 2.7, even if 3.x is installed. +Closes: #745598 + + -- Evgeni Golov evgeni.go...@credativ.de Sun, 27 Apr 2014 13:15:28 +0200 + libkolab (0.4.2-7) unstable; urgency=low * Fix saving of pictures to kabc resources (Closes: #721099) diff -Nru libkolab-0.4.2/debian/patches/series libkolab-0.4.2/debian/patches/series --- libkolab-0.4.2/debian/patches/series 2013-08-28 20:21:32.0 +0200 +++ libkolab-0.4.2/debian/patches/series 2014-04-27 13:13:14.0 +0200 @@ -3,3 +3,4 @@ simpler_cmake_test.patch libkolab-0.3.1-php-paths.patch add-linker-flags.patch +use-python2-only.patch diff -Nru libkolab-0.4.2/debian/patches/use-python2-only.patch libkolab-0.4.2/debian/patches/use-python2-only.patch --- libkolab-0.4.2/debian/patches/use-python2-only.patch 1970-01-01 01:00:00.0 +0100 +++ libkolab-0.4.2/debian/patches/use-python2-only.patch 2014-04-27 13:24:36.0 +0200 @@ -0,0 +1,12 @@ +Index: libkolab-0.4.2/CMakeLists.txt +=== +--- libkolab-0.4.2.orig/CMakeLists.txt 2014-04-27 12:29:12.0 +0200 libkolab-0.4.2/CMakeLists.txt 2014-04-27 13:24:32.599020139 +0200 +@@ -62,6 +62,7 @@ + find_package(KdepimLibs 4.8 REQUIRED) + endif() + ++set(PythonLibs_FIND_VERSION 2.7) + find_package(SWIG) + + #Show summary of found libraries
Processed: Re: libselinux: FTBFS: ruby.h: No such file or directory
Processing control commands: tags -1 +patch Bug #746024 [src:libselinux] libselinux: FTBFS: ruby.h: No such file or directory Added tag(s) patch. -- 746024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746024 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#746024: libselinux: FTBFS: ruby.h: No such file or directory
control: tags -1 +patch
Hi,
As same as Bug#746025, gem2deb has already drop ruby1.9.1 and it causes
this FTBFS. Attached patch would fix this (and also deal with ruby2.1).
Could you check and apply it, please?
--
Regards,
Hideki Yamane henrich @ debian.or.jp/org
http://wiki.debian.org/HidekiYamane
diff -Nru libselinux-2.2.2/debian/changelog libselinux-2.2.2/debian/changelog
--- libselinux-2.2.2/debian/changelog 2014-01-12 02:45:02.0 +0900
+++ libselinux-2.2.2/debian/changelog 2014-04-27 20:46:33.0 +0900
@@ -1,3 +1,11 @@
+libselinux (2.2.2-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/{ruby.mk,ruby-selinux.install}
+- drop related to ruby1.9.1 and add ruby2.1.0 instead (Closes: #746024)
+
+ -- Hideki Yamane henr...@debian.org Sun, 27 Apr 2014 20:45:31 +0900
+
libselinux (2.2.2-1) unstable; urgency=medium
* Team upload.
diff -Nru libselinux-2.2.2/debian/ruby-selinux.install libselinux-2.2.2/debian/ruby-selinux.install
--- libselinux-2.2.2/debian/ruby-selinux.install 2014-01-12 02:45:02.0 +0900
+++ libselinux-2.2.2/debian/ruby-selinux.install 2014-04-27 20:42:33.0 +0900
@@ -1,2 +1 @@
-usr/lib/ruby*
usr/lib/*/ruby
diff -Nru libselinux-2.2.2/debian/ruby.mk libselinux-2.2.2/debian/ruby.mk
--- libselinux-2.2.2/debian/ruby.mk 2014-01-12 02:45:02.0 +0900
+++ libselinux-2.2.2/debian/ruby.mk 2014-04-27 20:38:37.0 +0900
@@ -4,7 +4,7 @@
RUBYINSTALL ?= $(LIBDIR)/ruby/site_ruby/$(RUBYLIBVER)/$(RUBYPLATFORM)
## Default target
-RUBY_VERSIONS := ruby1.9.1 ruby2.0
+RUBY_VERSIONS := ruby2.0 ruby2.1
all: $(RUBY_VERSIONS)
## Targets share the same output files, so must be run serially
@@ -23,11 +23,11 @@
extra_ruby_args += RUBYINSTALL=$(DESTDIR)$(RUBY_VENDOR_ARCHLIB)
## How to build and install each individually-versioned copy
-ruby1.9.1: ruby%:
- +$(MAKE) $(extra_ruby_args) clean-rubywrap
- +$(MAKE) $(extra_ruby_args) RUBYINC=-I/usr/include/ruby-1.9.1/ -I/usr/include/ruby-1.9.1/\$${RUBYPLATFORM}/ install-rubywrap
-
ruby2.0: ruby%:
+$(MAKE) $(extra_ruby_args) clean-rubywrap
+$(MAKE) $(extra_ruby_args) RUBYINC=-I/usr/include/ruby-2.0.0/ -I/usr/include/\$${RUBYPLATFORM}/ruby-2.0.0/ \
RUBYINSTALL=$(DESTDIR)/usr/lib/$(RUBY_PLATFORM)/ruby/vendor_ruby/2.0.0/ install-rubywrap
+ruby2.1: ruby%:
+ +$(MAKE) $(extra_ruby_args) clean-rubywrap
+ +$(MAKE) $(extra_ruby_args) RUBYINC=-I/usr/include/ruby-2.1.0/ -I/usr/include/\$${RUBYPLATFORM}/ruby-2.1.0/ \
+ RUBYINSTALL=$(DESTDIR)/usr/lib/$(RUBY_PLATFORM)/ruby/vendor_ruby/2.1.0/ install-rubywrap
Bug#746025: libsemanage: FTBFS: ruby.h: No such file or directory
I forgot to add bug number to changelog, patch updated.
--
Regards,
Hideki Yamane henrich @ debian.or.jp/org
http://wiki.debian.org/HidekiYamane
diff -Nru libsemanage-2.2/debian/changelog libsemanage-2.2/debian/changelog
--- libsemanage-2.2/debian/changelog 2013-11-02 07:24:45.0 +0900
+++ libsemanage-2.2/debian/changelog 2014-04-27 20:23:45.0 +0900
@@ -1,3 +1,12 @@
+libsemanage (2.2-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/{rules,ruby-semanage.install}
+- remove ruby1.9.1 (however, it's just a workaround since it specifies
+ only ruby2.0, and we'll move to ruby2.1) (Closes: #746025)
+
+ -- Hideki Yamane henr...@debian.org Sun, 27 Apr 2014 20:13:32 +0900
+
libsemanage (2.2-1) unstable; urgency=low
* Team upload.
diff -Nru libsemanage-2.2/debian/ruby-semanage.install libsemanage-2.2/debian/ruby-semanage.install
--- libsemanage-2.2/debian/ruby-semanage.install 2013-11-02 07:24:45.0 +0900
+++ libsemanage-2.2/debian/ruby-semanage.install 2014-04-27 20:19:07.0 +0900
@@ -1,2 +1 @@
-usr/lib/ruby/vendor_ruby/*/*/semanage.so
usr/lib/*/ruby/vendor_ruby/*/semanage.so
diff -Nru libsemanage-2.2/debian/rules libsemanage-2.2/debian/rules
--- libsemanage-2.2/debian/rules 2013-11-02 07:24:45.0 +0900
+++ libsemanage-2.2/debian/rules 2014-04-27 20:13:30.0 +0900
@@ -25,9 +25,6 @@
PYPREFIX=python-$$version; \
done;
- $(MAKE) -C src rubywrap RUBY=ruby1.9.1 RUBYLIBVER=1.9.1 \
- RUBYINC=-I/usr/include/ruby-1.9.1/ -I/usr/include/ruby-1.9.1/\$${RUBYPLATFORM}/
-
$(MAKE) -C src rubywrap RUBY=ruby2.0 RUBYLIBVER=2.0.0 \
RUBYINC=-I/usr/include/ruby-2.0.0/ -I/usr/include/\$${RUBYPLATFORM}/ruby-2.0.0/
endif
@@ -44,9 +41,6 @@
PYPREFIX=python-$$version; \
done;
- $(MAKE) -C src install-rubywrap RUBY=ruby1.9.1 RUBYLIBVER=1.9.1 DESTDIR=${CURDIR}/debian/tmp \
- RUBYINSTALL=${CURDIR}/debian/tmp/usr/lib/ruby/vendor_ruby/\$${RUBYLIBVER}/\$${RUBYPLATFORM};
-
$(MAKE) -C src install-rubywrap RUBY=ruby2.0 RUBYLIBVER=2.0.0 DESTDIR=${CURDIR}/debian/tmp \
RUBYINSTALL=${CURDIR}/debian/tmp/usr/lib/\$${RUBYPLATFORM}/ruby/vendor_ruby/\$${RUBYLIBVER};
endif
Bug#746034: marked as done (chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive)
Your message dated Sun, 27 Apr 2014 13:53:19 +0200
with message-id 535cefaf.9050...@googlemail.com
and subject line Re: Bug#746034: chromium 34.0.1847.116-1~deb7u1 depends on
libudev0 which is no longer in the testing archive
has caused the Debian Bug report #746034,
regarding chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no
longer in the testing archive
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.)
--
746034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: chromium
Version: 33.0.1750.152-1
Justification: renders package unusable
Severity: grave
Dear Maintainer,
I cannot install the update 34.0.1847.116-1~deb7u1 because
it depends on libudev0 and libudev0 is no longer in the Debian testing
archive. I have marked the bug as grave as almost everybody who has
removed libudev0 would not be able to install this package.
$ aptitude search libudev
i A libudev-dev -
libudev development files
i A libudev1-
libudev shared library
As can be seen it's not there in the archive. I cannot update because
of the libudev0 dependancy. It should give dependancy as libudev1.
sudo aptitude install chromium chromium-inspector
The following packages will be upgraded:
chromium{b} chromium-inspector
2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 49.9 MB/50.6 MB of archives. After unpacking 12.7 MB will be freed.
The following packages have unmet dependencies:
chromium : Depends: libudev0 (= 146) which is a virtual package.
The following actions will resolve these dependencies:
Remove the following packages:
1) chromium
Leave the following dependencies unresolved:
2) chromium-inspector recommends chromium (= 10)
Accept this solution? [Y/n/q/?] q
$ aptitude show chromium=34.0.1847.116-1~deb7u1
Package: chromium
State: not installed
Automatically installed: no
Version: 34.0.1847.116-1~deb7u1
Priority: optional
Section: web
Maintainer: Debian Chromium Maintainers
pkg-chromium-ma...@lists.alioth.debian.org
Architecture: amd64
Uncompressed Size: 133 M
Depends: gconf-service, libasound2 (= 1.0.16), libatk1.0-0 (=
1.12.4), libc6 (= 2.11), libcairo2 (= 1.6.0), libcap2 (= 2.10),
libcups2 (= 1.4.0), libdbus-1-3 (= 1.2.14), libexpat1 (= 2.0.1),
libfontconfig1 (= 2.9.0), libfreetype6 (= 2.3.9), libgcc1 (=
1:4.1.1), libgconf-2-4 (= 2.31.1), libgcrypt11 (= 1.4.5),
libgdk-pixbuf2.0-0 (= 2.22.0), libglib2.0-0 (= 2.26.0),
libgnome-keyring0 (=3.2.2-2~), libgtk2.0-0 (= 2.24.0), libjpeg8
(= 8c), libnspr4 (= 2:4.9-2~), libnss3 (= 2:3.14.3), libpango1.0-0
(= 1.22.0), libspeechd2, libspeex1 (= 1.2~beta3-1), libstdc++6 (=
4.6), libudev0 (= 146), libx11-6 (= 2:1.4.99.1), libxcomposite1 (=
1:0.3-1), libxdamage1 (= 1:1.1), libxext6, libxfixes3, libxi6 (=
2:1.2.99.4), libxml2 (= 2.7.4), libxrender1, libxslt1.1 (= 1.1.25),
libxss1, libxtst6, xdg-utils, chromium-inspector
Suggests: chromium-l10n
Conflicts: chromium-browser ( 10.0.648.82~r75062-1~),
chromium-codecs-ffmpeg, chromium-codecs-ffmpeg-extra,
chromium-testsuite
Replaces: chromium-browser ( 10.0.648.82~r75062-1~),
chromium-codecs-ffmpeg, chromium-codecs-ffmpeg-extra,
chromium-testsuite
Provides: chromium-testsuite, gnome-www-browser, www-browser
Description: Google's open source chromium web browser
Chromium is an open-source browser project that aims to build a
safer, faster, and more stable way for all Internet users to
experience the
web.
Chromium serves as a base for Google Chrome, which is Chromium
rebranded (name and logo) with very few additions such as usage
tracking and an
auto-updater system.
This package contains the Chromium browser.
Homepage: http://www.chromium.org/Home
Tags: devel::interpreter, devel::lang:ecmascript, devel::runtime,
devel::web, implemented-in::c++, implemented-in::ecmascript,
interface::x11, network::client, protocol::TODO, protocol::ftp,
protocol::gopher, protocol::http, protocol::ipv6, protocol::ssl,
role::program, scope::application, uitoolkit::TODO, uitoolkit::gtk,
use::browsing, use::downloading, use::viewing, web::browser,
web::scripting, works-with-format::TODO, works-with-format::gif,
works-with-format::html, works-with-format::jpg,
works-with-format::json, works-with-format::mp3,
works-with-format::oggtheora, works-with-format::oggvorbis,
works-with-format::plaintext, works-with-format::png,
works-with-format::svg, works-with-format::xml,
Bug#744917: luajit: diff for NMU version 2.0.3+dfsg-2.1
On 04/25/2014 09:42 PM, Evgeni Golov wrote: As the Makefile defines LDCONFIG=ldconfig, and not LDCONFIG?=ldconfig, I can not :/ We could add the PATH in debian/rules instead. Shall we cancel the NMU for this fix? Greets -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745599: src:libkolabxml: FTBFS with undefined reference to symbol '_ZTVN5boost6detail16thread_data_baseE'
control: tags -1 + moreinfo unreproducible Hi, On Wed, Apr 23, 2014 at 09:32:19AM +0200, Ondřej Surý wrote: while doing the package recompilation with PHP 5.6 your package failed to build: Linking CXX executable conversiontest cd /tmp/buildd/libkolabxml/libkolabxml-0.8.4/obj-x86_64-linux-gnu/tests /usr/bin/cmake -E cmake_link_script CMakeFiles/conversiontest.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -fpermissive -Wl,--no-undefined -Wl,-z,relro -Wl,--as-needed CMakeFiles/conversiontest.dir/conversiontest.cpp.o -o conversiontest -rdynamic -lQtTest -lQtCore ../src/libkolabxml.so.0.8.4 -lxerces-c -Wl,-rpath,/tmp/buildd/libkolabxml/libkolabxml-0.8.4/obj-x86_64-linux-gnu/src /usr/bin/ld.bfd.real: CMakeFiles/conversiontest.dir/conversiontest.cpp.o: undefined reference to symbol '_ZTVN5boost6detail16thread_data_baseE' //usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[3]: *** [tests/conversiontest] Error 1 make[3]: Leaving directory `/tmp/buildd/libkolabxml/libkolabxml-0.8.4/obj-x86_64-linux-gnu' make[2]: *** [tests/CMakeFiles/conversiontest.dir/all] Error 2 make[2]: Leaving directory `/tmp/buildd/libkolabxml/libkolabxml-0.8.4/obj-x86_64-linux-gnu' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/libkolabxml/libkolabxml-0.8.4/obj-x86_64-linux-gnu' dh_auto_build: make -j1 returned exit code 2 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 This builds fine for me, both in a clean sid cowbuilder, and when pulling in PHP 5.6 from Experimental. Did you do anything more to produce this? Regards Evgeni -- 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#745599: src:libkolabxml: FTBFS with undefined reference to symbol '_ZTVN5boost6detail16thread_data_baseE'
Processing control commands: tags -1 + moreinfo unreproducible Bug #745599 [src:libkolabxml] src:libkolabxml: FTBFS with undefined reference to symbol '_ZTVN5boost6detail16thread_data_baseE' Added tag(s) unreproducible and moreinfo. -- 745599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745599 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: update affected versions for 746034
Processing commands for cont...@bugs.debian.org:
notfound 746034 33.0.1750.152-1
Bug #746034 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no
longer in the testing archive
No longer marked as found in versions chromium-browser/33.0.1750.152-1.
found 746034 34.0.1847.116-1~deb7u1
Bug #746034 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no
longer in the testing archive
Marked as found in versions chromium-browser/34.0.1847.116-1~deb7u1.
tags 746034 jessie
Bug #746034 {Done: Andreas Cadhalpun andreas.cadhal...@googlemail.com}
[chromium] chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no
longer in the testing archive
Added tag(s) jessie.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
746034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746034
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#746035: systemd: Systemd prevents to reboot
On 27/04/2014 13:35, Michael Biebl wrote: Am 27.04.2014 13:12, schrieb Eric Valette: This bug is known bug in samba, debugged and filed as [0] Michael [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739887 I applied the suggested patch, rerun insserv -v but it is still called twice on shutdown via sysv init. Dunno if it will change anything for systemd but it still wrong for sysv init. I added an info for the bug you just pointed out. Thanks for your time and patience! -- eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745599: src:libkolabxml: FTBFS with undefined reference to symbol '_ZTVN5boost6detail16thread_data_baseE'
Hi, I had all build-deps for php5 rev-build-deps installed. e.g. apt-get build-dep on all packages listed here: https://bugs.debian.org/745603 O. -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server On 27. 4. 2014, at 14:17, Evgeni Golov evg...@debian.org wrote: control: tags -1 + moreinfo unreproducible Hi, On Wed, Apr 23, 2014 at 09:32:19AM +0200, Ondřej Surý wrote: while doing the package recompilation with PHP 5.6 your package failed to build: Linking CXX executable conversiontest cd /tmp/buildd/libkolabxml/libkolabxml-0.8.4/obj-x86_64-linux-gnu/tests /usr/bin/cmake -E cmake_link_script CMakeFiles/conversiontest.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -fpermissive -Wl,--no-undefined -Wl,-z,relro -Wl,--as-needed CMakeFiles/conversiontest.dir/conversiontest.cpp.o -o conversiontest -rdynamic -lQtTest -lQtCore ../src/libkolabxml.so.0.8.4 -lxerces-c -Wl,-rpath,/tmp/buildd/libkolabxml/libkolabxml-0.8.4/obj-x86_64-linux-gnu/src /usr/bin/ld.bfd.real: CMakeFiles/conversiontest.dir/conversiontest.cpp.o: undefined reference to symbol '_ZTVN5boost6detail16thread_data_baseE' //usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[3]: *** [tests/conversiontest] Error 1 make[3]: Leaving directory `/tmp/buildd/libkolabxml/libkolabxml-0.8.4/obj-x86_64-linux-gnu' make[2]: *** [tests/CMakeFiles/conversiontest.dir/all] Error 2 make[2]: Leaving directory `/tmp/buildd/libkolabxml/libkolabxml-0.8.4/obj-x86_64-linux-gnu' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/libkolabxml/libkolabxml-0.8.4/obj-x86_64-linux-gnu' dh_auto_build: make -j1 returned exit code 2 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 This builds fine for me, both in a clean sid cowbuilder, and when pulling in PHP 5.6 from Experimental. Did you do anything more to produce this? Regards Evgeni
Bug#745307: FTBFS with ocamlgraph 1.8.4
On Sun, Apr 27, 2014 at 12:55:18PM +0200, Mehdi Dogguy wrote: Le 2014-04-27 12:41, Ralf Treinen a écrit : OK, merci. The next upload of dose3 will exclude in its build-dependency libocamlgraph-ocaml-dev 1.8.4-1 (since this will also be needed for dose 3.2). Can you be more specific about the will exclude in its build-dependency libocamlgraph-ocaml-dev 2.8.4-1 part please? What does it mean technically? Build-Depends: [...] libocamlgraph-ocaml-dev (= 1.8.5-1) | libocamlgraph-ocaml-dev ( 1.8.4-1), -Ralf. -- 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#746038: linux-headers-amd64: configure error in linux-headers
Processing control commands: reassign -1 blcr-dkms 0.8.5-2 Bug #746038 [linux-headers-amd64] linux-headers-amd64: configure error in linux-headers Bug reassigned from package 'linux-headers-amd64' to 'blcr-dkms'. No longer marked as found in versions linux-latest/56. Ignoring request to alter fixed versions of bug #746038 to the same values previously set Bug #746038 [blcr-dkms] linux-headers-amd64: configure error in linux-headers Marked as found in versions blcr/0.8.5-2. forcemerge 714045 -1 Bug #714045 [blcr-dkms] blcr-dkms: blcr module is not built on kernel 3.9.1 Bug #746038 [blcr-dkms] linux-headers-amd64: configure error in linux-headers Set Bug forwarded-to-address to 'https://upc-bugs.lbl.gov/bugzilla/show_bug.cgi?id=3199'. Severity set to 'grave' from 'important' Marked as found in versions blcr/0.8.5-2.1. Added tag(s) sid and jessie. Merged 714045 746038 -- 714045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714045 746038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746038 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#733435: Patch to fix FTBFS
Control: tags -1 + patch Hi, This patch removes the bootstrapping of distribute, which fixes the building the package. Regards, Johannes Brandstätter Description: Remove bootstrapping of distribute. Author: Johannes Brandstätter jbran...@2ds.eu Bug-Debian: http://bugs.debian.org/733435 Last-Update: 2014-04-27 --- pyowncloud-0.3.1.orig/setup.py +++ pyowncloud-0.3.1/setup.py @@ -1,5 +1,3 @@ -from distribute_setup import use_setuptools -use_setuptools() from setuptools import setup, find_packages import csync.version as ver setup( signature.asc Description: OpenPGP digital signature
Processed: Patch to fix FTBFS
Processing control commands: tags -1 + patch Bug #733435 [src:pyowncloud] pyowncloud: FTBFS: dpkg-buildpackage: error: dpkg-source: error: unrepresentable changes to source Added tag(s) patch. -- 733435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733435 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#731156: marked as done (libupsclient3: Library is containing undefined references)
Your message dated Sun, 27 Apr 2014 13:00:06 + with message-id e1weogg-0004bi...@franck.debian.org and subject line Bug#731156: fixed in nut 2.7.2-1 has caused the Debian Bug report #731156, regarding libupsclient3: Library is containing undefined references 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.) -- 731156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libupsclient3 Version: 2.7.1-1 Severity: grave Justification: renders package unusable Hi, So the new library is containing undefined references: /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libupsclient.so: undefined reference to `upsdebugx' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libupsclient.so: undefined reference to `xmalloc' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libupsclient.so: undefined reference to `xstrdup' /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libupsclient.so: undefined reference to `upslogx' And this is preventing to rebuild the rdeps :/ I'm opening this bug to track this in debian 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.11-2-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: nut Source-Version: 2.7.2-1 We believe that the bug you reported is fixed in the latest version of nut, 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 731...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville bi...@debian.org (supplier of updated nut package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Apr 2014 22:46:12 +0200 Source: nut Binary: nut nut-server nut-client nut-cgi nut-snmp nut-ipmi nut-xml nut-powerman-pdu nut-doc libupsclient4 libupsclient-dev python-nut nut-monitor libups-nut-perl Architecture: source all amd64 Version: 2.7.2-1 Distribution: unstable Urgency: low Maintainer: Arnaud Quette aque...@debian.org Changed-By: Laurent Bigonville bi...@debian.org Description: libups-nut-perl - network UPS tools - Perl bindings for NUT server libupsclient-dev - network UPS tools - development files libupsclient4 - network UPS tools - client library nut- network UPS tools - metapackage nut-cgi- network UPS tools - web interface nut-client - network UPS tools - clients nut-doc- network UPS tools - documentation nut-ipmi - network UPS tools - IPMI driver nut-monitor - network UPS tools - GUI application to monitor UPS status nut-powerman-pdu - network UPS tools - PowerMan PDU driver nut-server - network UPS tools - core system nut-snmp - network UPS tools - SNMP driver nut-xml- network UPS tools - XML/HTTP driver python-nut - network UPS tools - Python bindings for NUT server Closes: 731156 733189 Changes: nut (2.7.2-1) unstable; urgency=low . * New upstream release - Fix the undefined references (Closes: #731156) - debian/patches/0004-fix-systemd-service.patch: Refreshed - Drop d/p/0005-Provide-retry-options-for-upsdrvctl-and-drivers.patch: Merged upstream - debian/nut-server.install: Upstream is now installing upsdrvctl /sbin - Rename package libupsclient3 to libupsclient4, soname got bumped again * debian/rules, debian/control, d/p/0004-fix-systemd-service.patch: Use a symlink instead of an Alias= to mask the SysV initscript * debian/control: Bump Standards-Version to 3.9.5 (no further changes) * debian/tests/control: Add lsb-release and netcat to the dependencies (Closes: #733189) * debian/control, debian/rules: Call dh-autoreconf and pass LDFLAGS to minimize runtime dependencies * debian/patches/0008-drop-w3c-icons.patch: Remove the link to external W3C icons to prevent privacy breach (privacy-breach-w3c-valid-html) * debian/nut-server.install,
Bug#746049: gucharmap: FTBFS: Gucharmap-2.90.gir:1424.7-1424.33: error: The type name `Atk.TableCell' could not be found
Source: gucharmap Version: 1:3.12.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): g-ir-scanner: link: /bin/bash ../libtool --mode=link --tag=CC cc -o /«PKGBUILDDIR»/gucharmap/tmp-introspectbUBoeD/Gucharmap-2.90 -export-dynamic /«PKGBUILDDIR»/gucharmap/tmp-introspectbUBoeD/Gucharmap-2.90.o -L. libgucharmap_2_90.la -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 libtool: link: cc -o /«PKGBUILDDIR»/gucharmap/tmp-introspectbUBoeD/.libs/Gucharmap-2.90 /«PKGBUILDDIR»/gucharmap/tmp-introspectbUBoeD/Gucharmap-2.90.o -Wl,--export-dynamic -pthread -Wl,--export-dynamic -L. ./.libs/libgucharmap_2_90.so -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 /usr/lib/x86_64-linux-gnu/libcairo-gobject.so /usr/lib/x86_64-linux-gnu/libcairo.so -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -pthread (process:17698): GLib-GObject-WARNING **: invalid class cast from 'GucharmapChartableAccessible' to 'GtkAccessible' gucharmap-chapters-model.c:133: Warning: Gucharmap: gucharmap_chapters_model_id_to_iter: unknown parameter 'chapters_model' in documentation comment, should be 'model' /usr/bin/g-ir-compiler --includedir=. --includedir=. Gucharmap-2.90.gir -o Gucharmap-2.90.typelib /usr/bin/vapigen-0.24 --library gucharmap-2.90 --metadatadir . --vapidir /usr/share/vala/vapi --pkg glib-2.0 --pkg pango --pkg gdk-3.0 --pkg gtk+-3.0 Gucharmap-2.90.gir Gucharmap-2.90.gir:1424.7-1424.33: error: The type name `Atk.TableCell' could not be found implements name=Atk.TableCell/ ^^^ Generation failed: 1 error(s), 0 warning(s) make[4]: *** [gucharmap-2.90.vapi] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/gucharmap_3.12.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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746050: macopix: FTBFS: ld: cannot find -lgcrypt
Source: macopix Version: 1.7.4-4.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): gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include -DLOCALEDIR=\/usr/share/locale\ -DCOMMON_DIR=\/usr/share/macopix/\ -DPREFIX_DIR=\/usr/share/\ -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o dnd.o dnd.c /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,-z,relro -lX11 -o macopix main.o callbacks.o pixmap.o gui.o balloon.o clock.o configfile.o utils.o mail.o pop.o md5c.o md5ify.o nokkari.o bmp.o bmpwrite.o sockmsg.o codeconv.o unmime.o base64.o quoted-printable.o unlha.o untar.o trayicon.o alpha.o ssl.o sslmanager.o dnd.o -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lfontconfig -lfreetype -lgthread-2.0 -pthread -lglib-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lgnutls -lgcrypt -lgnutls-openssl libtool: link: gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wl,-z -Wl,relro -o macopix main.o callbacks.o pixmap.o gui.o balloon.o clock.o configfile.o utils.o mail.o pop.o md5c.o md5ify.o nokkari.o bmp.o bmpwrite.o sockmsg.o codeconv.o unmime.o base64.o quoted-printable.o unlha.o untar.o trayicon.o alpha.o ssl.o sslmanager.o dnd.o -pthread -lX11 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 /usr/lib/x86_64-linux-gnu/libcairo.so -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lfontconfig /usr/lib/x86_64-linux-gnu/libfreetype.so -lgthread-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lgnutls -lgcrypt -lgnutls-openssl -pthread /usr/bin/ld: cannot find -lgcrypt collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/macopix_1.7.4-4.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746053: couchdb: FTBFS: configure: error: The installed Erlang version must be = R14B (erts-5.8.1) and R17 (erts-5.11)
Source: couchdb
Version: 1.4.0-3
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):
checking ICU_CFLAGS... -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -Wall -std=c99 -Wall -pedantic -Wshadow
-Wpointer-arith -Wmissing-prototypes -Wwrite-strings
checking ICU_CXXFLAGS... -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -Wall -W -Wall -pedantic -Wpointer-arith
-Wwrite-strings -Wno-long-long --std=c++0x
checking ICU_LIBS... -Wl,-z,relro -ldl -lm -L/usr/lib/x86_64-linux-gnu
-licui18n -licuuc -licudata -ldl -lm
checking for curl-config... /usr/bin/curl-config
checking for curl (7.36.0) = 7.18.0... yes
configure: error: The installed Erlang version must be = R14B (erts-5.8.1)
and R17 (erts-5.11)
checking Erlang version compatibility... == config.log ==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by Apache CouchDB configure 1.4.0, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--libdir=${prefix}/lib/x86_64-linux-gnu
--libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking
## - ##
## Platform. ##
## - ##
hostname = ip-172-31-7-86
uname -m = x86_64
uname -r = 2.6.32-5-xen-amd64
uname -s = Linux
uname -v = #1 SMP Sun Sep 23 13:49:30 UTC 2012
[cutted here]
configure:17869: result: no
configure:18004: checking for icu-config
configure:18022: found /usr/bin/icu-config
configure:18035: result: /usr/bin/icu-config
configure:18051: checking for ICU = 3.4.1
configure:18055: result: yes
configure:18059: checking ICU_CPPFLAGS
configure:18062: result: -D_FORTIFY_SOURCE=2 -D_REENTRANT -DU_HAVE_ELF_H=1
-DU_HAVE_ATOMIC=1 -I/usr/include
configure:18065: checking ICU_CFLAGS
configure:18068: result: -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -Wall -std=c99 -Wall -pedantic -Wshadow
-Wpointer-arith -Wmissing-prototypes -Wwrite-strings
configure:18071: checking ICU_CXXFLAGS
configure:18074: result: -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -Wall -W -Wall -pedantic -Wpointer-arith
-Wwrite-strings -Wno-long-long --std=c++0x
configure:18077: checking ICU_LIBS
configure:18080: result: -Wl,-z,relro -ldl -lm -L/usr/lib/x86_64-linux-gnu
-licui18n -licuuc -licudata -ldl -lm
configure:18192: checking for curl-config
configure:18210: found /usr/bin/curl-config
configure:18222: result: /usr/bin/curl-config
configure:18278: checking for curl (7.36.0) = 7.18.0
configure:18313: result: yes
configure:18381: checking Erlang version compatibility
configure:18391: error: The installed Erlang version must be = R14B
(erts-5.8.1) and R17 (erts-5.11)
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/04/26/couchdb_1.4.0-3_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.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746051: pillow: FTBFS: debian/python-pil/usr/lib/python2.7/dist-packages/PIL/_imagingtk.so not found
Source: pillow
Version: 2.3.0-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):
byte-compiling
/«PKGBUILDDIR»/debian/python-sane/usr/lib/python2.7/dist-packages/sane.py to
sane.pyc
running install_egg_info
Writing
/«PKGBUILDDIR»/debian/python-sane/usr/lib/python2.7/dist-packages/pysane-2.0.egg-info
mkdir -p debian/python-pil/usr/include/python2.7
install -o root -g root -m 644 \
libImaging/Imaging.h \
libImaging/ImPlatform.h \
libImaging/ImDib.h \
debian/python-pil/usr/include/python2.7
dh_movefiles -ppython-pil.imagetk \
--sourcedir=debian/python-pil \
usr/lib/python2.7/$(basename $(_py_=2.7; python${_py_#python*}
-c 'from distutils import sysconfig;
print(sysconfig.get_python_lib())'))/PIL/_imagingtk.so \
usr/lib/python2.7/$(basename $(_py_=2.7; python${_py_#python*}
-c 'from distutils import sysconfig;
print(sysconfig.get_python_lib())'))/PIL/ImageTk.py
dh_movefiles:
debian/python-pil/usr/lib/python2.7/dist-packages/PIL/_imagingtk.so not found
(supposed to put it in python-pil.imagetk)
make: *** [install-python2.7] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/04/26/pillow_2.3.0-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746052: libxfont: FTBFS: ../../../src/util/patcache.c:130:1: error: conflicting types for 'CacheFontPattern'
Source: libxfont Version: 1:1.4.7-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): /bin/bash ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../../src/util -I../.. -I../../include/X11/fonts -I../../../include -I../../../src/stubs -D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -D_XOPEN_SOURCE -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o patcache.lo ../../../src/util/patcache.c libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../../src/util -I../.. -I../../include/X11/fonts -I../../../include -I../../../src/stubs -D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -D_XOPEN_SOURCE -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c ../../../src/util/patcache.c -fPIC -DPIC -o .libs/patcache.o ../../../src/util/patcache.c:130:1: error: conflicting types for 'CacheFontPattern' CacheFontPattern (FontPatternCachePtr cache, ^ In file included from /usr/include/X11/fonts/fontstruct.h:28:0, from ../../../src/util/patcache.c:35: /usr/include/X11/fonts/font.h:141:18: note: previous declaration of 'CacheFontPattern' was here extern void CacheFontPattern ( ^ ../../../src/util/patcache.c:176:1: error: conflicting types for 'FindCachedFontPattern' FindCachedFontPattern (FontPatternCachePtr cache, ^ In file included from /usr/include/X11/fonts/fontstruct.h:28:0, from ../../../src/util/patcache.c:35: /usr/include/X11/fonts/font.h:151:21: note: previous declaration of 'FindCachedFontPattern' was here extern FontPtr FindCachedFontPattern ( ^ make[5]: *** [patcache.lo] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/libxfont_1.4.7-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746056: pycode-browser: FTBFS: Latex errors
Source: pycode-browser
Version: 20120614+git+b041dd2-5
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/share/texlive/texmf-dist/tex/context/base/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty))
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/grfext.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty))
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/etexcmds.sty)))
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
pics/ylm20.png, id=1, 566.115pt x 468.75125pt use pics/ylm20.png
[1{/var/li
b/texmf/fonts/map/pdftex/updmap/pdftex.map} ./pics/ylm20.png (PNG copy)]
[2]
No file mapy.toc.
[3]
Chapter 1.
kpathsea: Running mktextfm tcrm1000
mkdir: cannot create directory '././sbuild-nonexistent': Permission denied
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode;
input tcrm1000
This is METAFONT, Version 2.718281 (TeX Live 2013/Debian)
kpathsea: Running mktexmf tcrm1000
! I can't find file `tcrm1000'.
* ...ljfour; mag:=1; nonstopmode; input tcrm1000
Please type another input file name
! Emergency stop.
* ...ljfour; mag:=1; nonstopmode; input tcrm1000
Transcript written on mfput.log.
grep: tcrm1000.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input
tcrm1000' failed to make tcrm1000.tfm.
kpathsea: Appending font creation commands to missfont.log.
[4]
! Font TS1/cmr/m/n/10=tcrm1000 at 10.0pt not loadable: Metric (TFM) file not
fo
und.
to be read again
relax
l.249 \item S
ingle user, single process systems like MS DOS. Only one process
?
! Emergency stop.
to be read again
relax
l.249 \item S
ingle user, single process systems like MS DOS. Only one process
! == Fatal error occurred, no output PDF file produced!
Transcript written on mapy.log.
make[2]: *** [mapy.pdf] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/04/26/pycode-browser_20120614+git+b041dd2-5_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.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746055: ruby-fakeweb: FTBFS: ERROR: Test ruby2.1 failed
Source: ruby-fakeweb
Version: 1.3.0+dfsg1-3
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):
Running tests for ruby2.1 using debian/ruby-tests.rb...
Run options:
# Running tests:
.F.FF..
Finished tests in 0.851353s, 219.6503 tests/s, 348.8564 assertions/s.
1) Failure:
TestFakeWeb#test_real_http_request [/usr/lib/ruby/2.1.0/net/http.rb:881]:
unexpected invocation: #Mock:TCPSocket.setsockopt(6, 1, 1)
unsatisfied expectations:
- expected at least once, not yet invoked:
#Mock:TCPSocket.read_nonblock(any_parameters)
- expected exactly once, not yet invoked:
#Mock:TCPSocket.write(all_of(includes('GET /main/rss/hotnews/hotnews.rss
HTTP/1.1'), includes('Host: images.apple.com')))
- expected at least once, not yet invoked: Socket.===(#Mock:TCPSocket)
satisfied expectations:
- allowed any number of times, not yet invoked:
#Mock:TCPSocket.close(any_parameters)
- allowed any number of times, not yet invoked:
#Mock:TCPSocket.closed?(any_parameters)
- expected at least once, invoked once: TCPSocket.open('images.apple.com',
80, nil, nil)
2) Failure:
TestFakeWeb#test_real_http_request_with_undocumented_full_uri_argument_style
[/usr/lib/ruby/2.1.0/net/http.rb:881]:
unexpected invocation: #Mock:TCPSocket.setsockopt(6, 1, 1)
unsatisfied expectations:
- expected at least once, not yet invoked:
#Mock:TCPSocket.read_nonblock(any_parameters)
- expected exactly once, not yet invoked:
#Mock:TCPSocket.write(all_of(includes('GET
http://images.apple.com/main/rss/hotnews/hotnews.rss HTTP/1.1'),
includes('Host: images.apple.com')))
- expected at least once, not yet invoked: Socket.===(#Mock:TCPSocket)
satisfied expectations:
- allowed any number of times, not yet invoked:
#Mock:TCPSocket.close(any_parameters)
- allowed any number of times, not yet invoked:
#Mock:TCPSocket.closed?(any_parameters)
- expected at least once, invoked once: TCPSocket.open('images.apple.com',
80, nil, nil)
3) Failure:
TestFakeWeb#test_real_https_request [/usr/lib/ruby/2.1.0/net/http.rb:881]:
unexpected invocation: #Mock:SSLSocket.setsockopt(6, 1, 1)
unsatisfied expectations:
- expected at least once, not yet invoked:
#Mock:SSLSocket.read_nonblock(any_parameters)
- expected exactly once, not yet invoked:
#Mock:SSLSocket.write(all_of(includes('GET /main/rss/hotnews/hotnews.rss
HTTP/1.1'), includes('Host: images.apple.com')))
- expected at least once, not yet invoked: #Mock:SSLSocket.session()
- expected at least once, not yet invoked: #Mock:SSLSocket.connect()
- expected at least once, not yet invoked:
OpenSSL::SSL::SSLSocket.new(#Mock:SSLSocket,
instance_of(OpenSSL::SSL::SSLContext))
- expected at least once, not yet invoked:
OpenSSL::SSL::SSLSocket.===(#Mock:SSLSocket)
satisfied expectations:
- allowed any number of times, not yet invoked:
#Mock:SSLSocket.close(any_parameters)
- allowed any number of times, not yet invoked:
#Mock:SSLSocket.closed?(any_parameters)
- allowed any number of times, not yet invoked:
#Mock:SSLSocket.sync_close=(any_parameters)
- expected at least once, invoked once: TCPSocket.open('images.apple.com',
443, nil, nil)
4) Failure:
TestFakeWeb#test_real_post_with_body_sets_the_request_body
[/usr/lib/ruby/2.1.0/net/http.rb:881]:
unexpected invocation: #Mock:TCPSocket.setsockopt(6, 1, 1)
unsatisfied expectations:
- expected at least once, not yet invoked:
#Mock:TCPSocket.read_nonblock(any_parameters)
- expected exactly once, not yet invoked:
#Mock:TCPSocket.write('title=Test')
- expected exactly once, not yet invoked:
#Mock:TCPSocket.write(all_of(includes('POST /posts HTTP/1.1'),
includes('Host: images.apple.com')))
- expected at least once, not yet invoked: Socket.===(#Mock:TCPSocket)
satisfied expectations:
- allowed any number of times, not yet invoked:
#Mock:TCPSocket.close(any_parameters)
- allowed any number of times, not yet invoked:
#Mock:TCPSocket.closed?(any_parameters)
- expected at least once, invoked once: TCPSocket.open('images.apple.com',
80, nil, nil)
5) Failure:
TestFakeWeb#test_real_request_on_same_domain_as_mock
[/usr/lib/ruby/2.1.0/net/http.rb:881]:
unexpected invocation: #Mock:TCPSocket.setsockopt(6, 1, 1)
unsatisfied expectations:
- expected at least once, not yet invoked:
#Mock:TCPSocket.read_nonblock(any_parameters)
- expected exactly once, not yet invoked:
#Mock:TCPSocket.write(all_of(includes('GET /main/rss/hotnews/hotnews.rss
HTTP/1.1'), includes('Host: images.apple.com')))
- expected at least once, not yet invoked: Socket.===(#Mock:TCPSocket)
satisfied expectations:
-
Bug#746057: frogr: FTBFS: configure: error: Unrecognized YELP_HELP_INIT option 3.1.1
Source: frogr Version: 0.9-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): checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl = 5.8.1... 5.18.2 checking for XML::Parser... ok configure: error: Unrecognized YELP_HELP_INIT option 3.1.1 checking whether ln -s works... yes The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/frogr_0.9-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746054: twinkle: FTBFS: configure: error: Library requirements (libzrtpcpp = 1.3.0) not met
Source: twinkle Version: 1:1.4.2-4 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): checking for speex/speex_preprocess.h... yes checking speex/speex_echo.h usability... yes checking speex/speex_echo.h presence... yes checking for speex/speex_echo.h... yes checking for libzrtpcpp = 1.3.0... Package libcrypto was not found in the pkg-config search path. Perhaps you should add the directory containing `libcrypto.pc' to the PKG_CONFIG_PATH environment variable Package 'libcrypto', required by 'libzrtpcpp', not found configure: error: Library requirements (libzrtpcpp = 1.3.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/twinkle_1.4.2-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746058: sqlite: FTBFS: /bin/sh: 1: tclsh: not found
Source: sqlite
Version: 2.8.17-10
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):
ar cru .libs/libtclsqlite.a tclsqlite.o
ranlib .libs/libtclsqlite.a
creating libtclsqlite.la
(cd .libs rm -f libtclsqlite.la ln -s ../libtclsqlite.la
libtclsqlite.la)
cat ./src/attach.c ./src/auth.c ./src/btree.c ./src/btree.h ./src/btree_rb.c
./src/build.c ./src/copy.c ./src/date.c ./src/delete.c ./src/encode.c
./src/expr.c ./src/func.c ./src/hash.c ./src/hash.h ./src/insert.c
./src/main.c ./src/os.c ./src/pager.c ./src/pager.h ./src/parse.y
./src/pragma.c ./src/printf.c ./src/random.c ./src/select.c ./src/shell.c
./src/sqlite.h.in ./src/sqliteInt.h ./src/table.c ./src/tclsqlite.c
./src/tokenize.c ./src/trigger.c ./src/update.c ./src/util.c ./src/vacuum.c
./src/vdbe.c ./src/vdbeaux.c ./src/vdbe.h ./src/where.c | grep '$Id: ' | sort
+4 | tail -1 \
| awk '{print $5,$6}' last_change
sort: cannot read: +4: No such file or directory
tclsh ./www/index.tcl `cat ./VERSION` index.html
/bin/sh: 1: tclsh: not found
make[2]: *** [index.html] Error 127
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/04/26/sqlite_2.8.17-10_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.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746059: ruby-oauth2: FTBFS: ERROR: Test ruby2.0 failed
Source: ruby-oauth2
Version: 0.9.1-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):
Failure/Error: expect(subject.connection.ssl).to eq({:ca_file =
'foo.pem'})
expected: {:ca_file=foo.pem}
got: #Faraday::SSLOptions ca_file=foo.pem
(compared using ==)
Diff:
@@ -1,2 +1,13 @@
-:ca_file = foo.pem
+#struct Faraday::SSLOptions
+ verify=nil,
+ ca_file=foo.pem,
+ ca_path=nil,
+ verify_mode=nil,
+ cert_store=nil,
+ client_cert=nil,
+ client_key=nil,
+ certificate=nil,
+ private_key=nil,
+ verify_depth=nil,
+ version=nil
# ./spec/oauth2/client_spec.rb:184:in `block (3 levels) in top
(required)'
Finished in 0.31091 seconds
158 examples, 2 failures
Failed examples:
rspec ./spec/oauth2/client_spec.rb:37 # OAuth2::Client#initialize leaves
Faraday::Connection#ssl unset
rspec ./spec/oauth2/client_spec.rb:183 # OAuth2::Client with SSL options
passes the SSL options along to Faraday::Connection#ssl
/usr/bin/ruby2.0 -S rspec ./spec/oauth2/access_token_spec.rb
./spec/oauth2/client_spec.rb ./spec/oauth2/response_spec.rb
./spec/oauth2/strategy/assertion_spec.rb
./spec/oauth2/strategy/auth_code_spec.rb ./spec/oauth2/strategy/base_spec.rb
./spec/oauth2/strategy/client_credentials_spec.rb
./spec/oauth2/strategy/implicit_spec.rb
./spec/oauth2/strategy/password_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-oauth2_0.9.1-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.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746070: ruby-capybara: FTBFS: E: ruby1.9.1 is not supported by gem2deb anymore
Source: ruby-capybara Version: 2.1.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): fakeroot debian/rules binary dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby Entering dh_ruby --install E: ruby1.9.1 is not supported by gem2deb anymore dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-capybara returned exit code 1 make: *** [binary] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ruby-capybara_2.1.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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746065: keepalived: FTBFS: configure: error: incorrect CFLAGS from net-snmp-config
Source: keepalived Version: 1:1.2.9-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): checking for nl_socket_alloc in -lnl-3... yes checking for kernel version... 3.13.10 checking for IPVS syncd support... yes checking for kernel macvlan support... yes checking for net-snmp-config... /usr/bin/net-snmp-config configure: error: incorrect CFLAGS from net-snmp-config checking whether C compiler supports flag -Wl,-z,relro -Wl,-z,now -L/usr/lib/x86_64-linux-gnu -lnetsnmpmibs -lsensors -lpci -ldl -lnetsnmpagent -lwrap -Wl,-E -lnetsnmp -lcrypto -lm from Net-SNMP... no The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/keepalived_1.2.9-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746069: music123: FTBFS: /usr/share/ada/debian_packaging.mk: No such file or directory
Source: music123 Version: 16.3-4 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): fakeroot debian/rules clean debian/rules:7: /usr/share/ada/debian_packaging.mk: No such file or directory make: *** No rule to make target `/usr/share/ada/debian_packaging.mk'. Stop. dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 Build finished at 20140426-2224 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/music123_16.3-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746061: libplack-middleware-debug-perl: FTBFS: Tests failures
Source: libplack-middleware-debug-perl Version: 0.16-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): debian/rules build dh build dh_testdir dh_auto_configure Creating new 'Build' script for 'Plack-Middleware-Debug' version '0.16' dh_auto_build cp lib/Plack/Middleware/Debug.pm blib/lib/Plack/Middleware/Debug.pm cp lib/Plack/Middleware/Debug/Session.pm blib/lib/Plack/Middleware/Debug/Session.pm cp share/debug_toolbar/toolbar.min.css blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/toolbar.min.css cp share/debug_toolbar/toolbar.min.js blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/toolbar.min.js cp lib/Plack/Middleware/Debug/PerlConfig.pm blib/lib/Plack/Middleware/Debug/PerlConfig.pm cp lib/Plack/Middleware/Debug/Base.pm blib/lib/Plack/Middleware/Debug/Base.pm cp lib/Plack/Middleware/Debug/Timer.pm blib/lib/Plack/Middleware/Debug/Timer.pm cp share/debug_toolbar/back_hover.png blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/back_hover.png cp share/debug_toolbar/jquery.js blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/jquery.js cp lib/Plack/Middleware/Debug/Panel.pm blib/lib/Plack/Middleware/Debug/Panel.pm cp lib/Plack/Middleware/Debug/Environment.pm blib/lib/Plack/Middleware/Debug/Environment.pm cp lib/Plack/Middleware/Debug/ModuleVersions.pm blib/lib/Plack/Middleware/Debug/ModuleVersions.pm cp share/debug_toolbar/close.png blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/close.png cp share/debug_toolbar/panel_bg.png blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/panel_bg.png cp lib/Plack/Middleware/Debug/Response.pm blib/lib/Plack/Middleware/Debug/Response.pm cp share/debug_toolbar/indicator.png blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/indicator.png cp lib/Plack/Middleware/Debug/CatalystLog.pm blib/lib/Plack/Middleware/Debug/CatalystLog.pm cp share/debug_toolbar/back.png blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/back.png cp share/debug_toolbar/toolbar.css blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/toolbar.css cp share/debug_toolbar/toolbar.js blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/toolbar.js cp lib/Plack/Middleware/Debug/TrackObjects.pm blib/lib/Plack/Middleware/Debug/TrackObjects.pm cp share/debug_toolbar/jquery.cookie.js blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/jquery.cookie.js cp share/debug_toolbar/close_hover.png blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/close_hover.png cp share/debug_toolbar/information.gif blib/lib/auto/share/dist/Plack-Middleware-Debug/debug_toolbar/information.gif cp lib/Plack/Middleware/Debug/DBITrace.pm blib/lib/Plack/Middleware/Debug/DBITrace.pm cp lib/Plack/Middleware/Debug/Parameters.pm blib/lib/Plack/Middleware/Debug/Parameters.pm cp lib/Plack/Middleware/Debug/Memory.pm blib/lib/Plack/Middleware/Debug/Memory.pm dh_auto_test t/01_basic.t ok Can't locate Test/Requires.pm in @INC (you may need to install the Test::Requires module) (@INC contains: /«PKGBUILDDIR»/blib/arch /«PKGBUILDDIR»/blib/lib /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at t/parameters-leak.t line 4. BEGIN failed--compilation aborted at t/parameters-leak.t line 4. t/parameters-leak.t . Dubious, test returned 2 (wstat 512, 0x200) No subtests run t/release-pod-syntax.t .. skipped: these tests are for release candidate testing t/utf8.t ok Test Summary Report --- t/parameters-leak.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=4, Tests=13, 1 wallclock secs ( 0.05 usr 0.04 sys + 0.35 cusr 0.12 csys = 0.56 CPU) Result: FAIL dh_auto_test: perl Build test returned exit code 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/libplack-middleware-debug-perl_0.16-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746067: rgtk2: FTBFS: gioManuals.c:197:39: error: format not a string literal and no format arguments [-Werror=format-security]
Source: rgtk2 Version: 2.20.27-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): gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG -g -D_R_=1 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I. -DHAVE_UINTPTR_T -fpic -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g -c gioManuals.c -o gioManuals.o gioManuals.c: In function 'S_g_simple_async_report_error_in_idle': gioManuals.c:197:39: error: format not a string literal and no format arguments [-Werror=format-security] format); ^ cc1: some warnings being treated as errors make[1]: *** [gioManuals.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/rgtk2_2.20.27-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746063: nagios-plugins-contrib: FTBFS: check_varnish.c:46:17: fatal error: vsc.h: No such file or directory
Source: nagios-plugins-contrib Version: 9.20140106 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): gcc -DHAVE_CONFIG_H -I.-include config.h -I/usr/include/varnish -g -O2 -c -o check_varnish-check_varnish.o `test -f 'check_varnish.c' || echo './'`check_varnish.c check_varnish.c:46:17: fatal error: vsc.h: No such file or directory #include vsc.h ^ compilation terminated. make[3]: *** [check_varnish-check_varnish.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/nagios-plugins-contrib_9.20140106_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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746062: libhtml-formfu-model-dbic-perl: FTBFS: Tests failures
Source: libhtml-formfu-model-dbic-perl Version: 1.02-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): t/update/null_if_empty.t .. ok t/update/opt_accessor.t ... ok t/update/opt_accessor_nested.t ok t/update/unchecked_not_null_checkbox.t ok t/x_roundtrip/checkbox_false2true.t ... ok t/x_roundtrip/checkbox_true2false.t ... ok Test Summary Report --- t/constraints/dbic_unique.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 15 tests but ran 0. t/constraints/dbic_unique_repeatable_id_field.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 8 tests but ran 0. Files=94, Tests=584, 182 wallclock secs ( 0.46 usr 0.63 sys + 166.50 cusr 15.18 csys = 182.77 CPU) Result: FAIL Failed 2/94 test programs. 0/584 subtests failed. make[1]: *** [test_dynamic] Error 255 dh_auto_test: make -j1 test returned exit code 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/libhtml-formfu-model-dbic-perl_1.02-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746060: lldpd: FTBFS: configure: error: *** incorrect CFLAGS from net-snmp-config
Source: lldpd Version: 0.7.7-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): checking for history.h... no checking readline/history.h usability... yes checking readline/history.h presence... yes checking for readline/history.h... yes checking for net-snmp-config... /usr/bin/net-snmp-config configure: error: *** incorrect CFLAGS from net-snmp-config checking whether C compiler supports flag -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 -DNETSNMP_NO_INLINE -Wl,-z,relro -Wl,-z,now -L/usr/lib/x86_64-linux-gnu -lnetsnmpmibs -lsensors -lpci -ldl -lnetsnmpagent -lwrap -Wl,-E -lnetsnmp -lcrypto -lm from Net-SNMP... no The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/lldpd_0.7.7-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746066: python-steadymark: FTBFS: Tests failures
Source: python-steadymark Version: 0.4.5-3 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): make[2]: Entering directory `/«PKGBUILDDIR»' Cleaning up files that are already in .gitignore... OK! Running unit tests SteadyMark should find python code and use the previous header as title ... FAIL SteadyMark should find docstrings and use the previous header as title ... FAIL SteadyMark should find all the tests under the same header (title) ... FAIL SteadyMark should skip tests with the 'ignore' modeline ... ok SteadyMark should find doctest and use the previous header as title ... ok SteadyMark should find python code and use the previous header as title ... ok SteadyMark should accumulate the scope throughout the python code snippets ... ok == FAIL: SteadyMark should find python code and use the previous header as title -- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/nose/case.py, line 197, in runTest self.test(*self.arg) File /«PKGBUILDDIR»/tests/unit/test_parser.py, line 70, in test_find_python_code_with_titles eval.when.called_with(test1.code).should.throw(AssertionError, boom!) File /usr/lib/python2.7/dist-packages/sure/__init__.py, line 376, in wrapper value = func(self, *args, **kw) File /usr/lib/python2.7/dist-packages/sure/__init__.py, line 790, in throw return _that.raises(*args, **kw) File /usr/lib/python2.7/dist-packages/sure/old.py, line 130, in raises self._src, exc, e.__class__, traceback.format_exc(e))) AssertionError: built-in function eval should raise type 'exceptions.AssertionError', but raised type 'exceptions.TypeError': ORIGINAL EXCEPTION: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/sure/old.py, line 118, in raises self._src(*self._callable_args, **self._callable_kw) TypeError: eval expected at least 1 arguments, got 0 == FAIL: SteadyMark should find docstrings and use the previous header as title -- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/nose/case.py, line 197, in runTest self.test(*self.arg) File /«PKGBUILDDIR»/tests/unit/test_parser.py, line 124, in test_find_inline_doctests_with_titles eval.when.called_with(test2.code).should.throw(AssertionError, uh yeah) File /usr/lib/python2.7/dist-packages/sure/__init__.py, line 376, in wrapper value = func(self, *args, **kw) File /usr/lib/python2.7/dist-packages/sure/__init__.py, line 790, in throw return _that.raises(*args, **kw) File /usr/lib/python2.7/dist-packages/sure/old.py, line 130, in raises self._src, exc, e.__class__, traceback.format_exc(e))) AssertionError: built-in function eval should raise type 'exceptions.AssertionError', but raised type 'exceptions.TypeError': ORIGINAL EXCEPTION: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/sure/old.py, line 118, in raises self._src(*self._callable_args, **self._callable_kw) TypeError: eval expected at least 1 arguments, got 0 == FAIL: SteadyMark should find all the tests under the same header (title) -- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/nose/case.py, line 197, in runTest self.test(*self.arg) File /«PKGBUILDDIR»/tests/unit/test_parser.py, line 154, in test_use_same_title_for_all_tests eval.when.called_with(test1.code).should.throw(AssertionError, FIRST) File /usr/lib/python2.7/dist-packages/sure/__init__.py, line 376, in wrapper value = func(self, *args, **kw) File /usr/lib/python2.7/dist-packages/sure/__init__.py, line 790, in throw return _that.raises(*args, **kw) File /usr/lib/python2.7/dist-packages/sure/old.py, line 130, in raises self._src, exc, e.__class__, traceback.format_exc(e))) AssertionError: built-in function eval should raise type 'exceptions.AssertionError', but raised type 'exceptions.TypeError': ORIGINAL EXCEPTION: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/sure/old.py, line 118, in raises self._src(*self._callable_args, **self._callable_kw) TypeError: eval expected at least 1 arguments, got 0 -- Ran 7 tests in 0.013s FAILED (failures=3) make[2]: *** [unit] Error 1 The full build log is available from:
Bug#746068: 389-admin: FTBFS: configure: error: ADMINUTIL not found, specify with --with-adminutil.
Source: 389-admin
Version: 1.1.30-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):
using system ICU
checking for genrb... 1
configure: checking for ADMINUTIL...
checking for --with-adminutil... no
checking for adminutil with pkg-config... checking for pkg-config... (cached)
/usr/bin/pkg-config
configure: error: ADMINUTIL not found, specify with --with-adminutil.
dh_auto_configure: ../configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--libdir=${prefix}/lib/x86_64-linux-gnu
--libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking --disable-rpath --with-openldap
--with-httpd=/usr/sbin/apache2 --with-initddir=/etc/init.d
--with-apxs=/usr/bin/apxs2 returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 2
make[1]: Leaving directory `/«PKGBUILDDIR»'
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/04/26/389-admin_1.1.30-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.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746064: libtype-tiny-perl: FTBFS: Tests failures
Source: libtype-tiny-perl
Version: 0.022-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):
ok 19 - use Type::Tiny::Union;
ok 20 - use Type::Utils;
ok 21 - use Type::Params;
1..21
ok
# Failed test 'Moose::Meta::TypeConstraint API:
TestType-can('_compile_hand_optimized_type_constraint')'
# at t/02-api.t line 107.
Bailout called. Further testing stopped: Further tests rely on the
Type::Tiny and Type::Coercion APIs.
# Tests were run but no plan was declared and done_testing() was not seen.
FAILED--Further testing stopped: Further tests rely on the Type::Tiny and
Type::Coercion APIs.
make[1]: *** [test_dynamic] Error 255
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/04/26/libtype-tiny-perl_0.022-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.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746074: ruby-kramdown: FTBFS: ruby1.9.1 is not supported by gem2deb anymore
Source: ruby-kramdown Version: 1.3.3-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): make[1]: Entering directory `/«PKGBUILDDIR»' rdoc1.9.1 --all --line-numbers \ -o /«PKGBUILDDIR»/debian/ruby-kramdown/usr/share/doc/ruby-kramdown/rdoc lib README.md make[1]: rdoc1.9.1: Command not found make[1]: *** [override_dh_installdocs] Error 127 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ruby-kramdown_1.3.3-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746075: transfig: FTBFS: LaTeX Error: File `pgfcore.sty' not found.
Source: transfig Version: 1:3.2.5.e-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): LaTeX2e 2011/06/27 Babel 3.9k and hyphenation patterns for 7 languages loaded. (/usr/share/texlive/texmf-dist/tex/latex/beamer/beamer.cls (/usr/share/texlive/texmf-dist/tex/latex/beamer/beamerbasercs.sty) Document Class: beamer 2013/12/02 3.33 A class for typesetting presentations (r cs-revision 332bfd3ce558) (/usr/share/texlive/texmf-dist/tex/latex/beamer/beamerbasemodes.sty (/usr/share/texlive/texmf-dist/tex/latex/beamer/beamerbasedecode.sty)) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty) (/usr/share/texlive/texmf-dist/tex/latex/beamer/beamerbaseoptions.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)) (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty) (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)) (/usr/share/texlive/texmf-dist/tex/latex/base/size11.clo) ! LaTeX Error: File `pgfcore.sty' not found. Type X to quit or RETURN to proceed, or enter new name. (Default extension: sty) Enter file name: ! Emergency stop. read * l.359 ^^M ! == Fatal error occurred, no output PDF file produced! Transcript written on sample-presentation.log. make[2]: *** [sample-presentation.pdf] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/transfig_3.2.5.e-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746071: librg-blast-parser-perl: FTBFS: blast-parser-driver.h:25:39: fatal error: rostlab/rostlab_stdexcept.h: No such file or directory
Source: librg-blast-parser-perl Version: 0.03-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): g++ -c -I. -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fstack-protector -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DVERSION=\0.03\ -DXS_VERSION=\0.03\ -fPIC -I/usr/lib/perl/5.18/CORE Parser.c In file included from Parser.xs:15:0: /usr/include/rostlab/blast-parser-driver.h:25:39: fatal error: rostlab/rostlab_stdexcept.h: No such file or directory #include rostlab/rostlab_stdexcept.h ^ compilation terminated. make[1]: *** [Parser.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/librg-blast-parser-perl_0.03-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746076: threadscope: FTBFS: Ambiguous occurrence `Region'
Source: threadscope Version: 0.2.2-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): [26 of 35] Compiling GUI.Timeline.Activity ( GUI/Timeline/Activity.hs, dist-ghc/build/threadscope/threadscope-tmp/GUI/Timeline/Activity.o ) [27 of 35] Compiling GUI.Timeline.Render ( GUI/Timeline/Render.hs, dist-ghc/build/threadscope/threadscope-tmp/GUI/Timeline/Render.o ) GUI/Timeline/Render.hs:37:15: Ambiguous occurrence `Region' It could refer to either `Graphics.UI.Gtk.Region', imported from `Graphics.UI.Gtk' at GUI/Timeline/Render.hs:23:1-22 (and originally defined in `Graphics.UI.Gtk.Gdk.Region') or `Graphics.Rendering.Cairo.Region', imported from `Graphics.Rendering.Cairo' at GUI/Timeline/Render.hs:24:1-31 (and originally defined in `Graphics.Rendering.Cairo.Types') GUI/Timeline/Render.hs:54:65: Ambiguous occurrence `height' It could refer to either `GUI.Types.height', imported from `GUI.Types' at GUI/Timeline/Render.hs:19:1-16 (and originally defined at GUI/Types.hs:30:12-17) or `Graphics.Rendering.Cairo.height', imported from `Graphics.Rendering.Cairo' at GUI/Timeline/Render.hs:24:1-31 (and originally defined in `Graphics.Rendering.Cairo.Types') GUI/Timeline/Render.hs:68:11: Ambiguous occurrence `width' It could refer to either `GUI.Types.width', imported from `GUI.Types' at GUI/Timeline/Render.hs:19:1-16 (and originally defined at GUI/Types.hs:30:5-9) or `Graphics.Rendering.Cairo.width', imported from `Graphics.Rendering.Cairo' at GUI/Timeline/Render.hs:24:1-31 (and originally defined in `Graphics.Rendering.Cairo.Types') GUI/Timeline/Render.hs:68:32: Ambiguous occurrence `width' It could refer to either `GUI.Types.width', imported from `GUI.Types' at GUI/Timeline/Render.hs:19:1-16 (and originally defined at GUI/Types.hs:30:5-9) or `Graphics.Rendering.Cairo.width', imported from `Graphics.Rendering.Cairo' at GUI/Timeline/Render.hs:24:1-31 (and originally defined in `Graphics.Rendering.Cairo.Types') GUI/Timeline/Render.hs:69:11: Ambiguous occurrence `height' It could refer to either `GUI.Types.height', imported from `GUI.Types' at GUI/Timeline/Render.hs:19:1-16 (and originally defined at GUI/Types.hs:30:12-17) or `Graphics.Rendering.Cairo.height', imported from `Graphics.Rendering.Cairo' at GUI/Timeline/Render.hs:24:1-31 (and originally defined in `Graphics.Rendering.Cairo.Types') GUI/Timeline/Render.hs:69:32: Ambiguous occurrence `height' It could refer to either `GUI.Types.height', imported from `GUI.Types' at GUI/Timeline/Render.hs:19:1-16 (and originally defined at GUI/Types.hs:30:12-17) or `Graphics.Rendering.Cairo.height', imported from `Graphics.Rendering.Cairo' at GUI/Timeline/Render.hs:24:1-31 (and originally defined in `Graphics.Rendering.Cairo.Types') GUI/Timeline/Render.hs:74:34: Ambiguous occurrence `width' It could refer to either `GUI.Types.width', imported from `GUI.Types' at GUI/Timeline/Render.hs:19:1-16 (and originally defined at GUI/Types.hs:30:5-9) or `Graphics.Rendering.Cairo.width', imported from `Graphics.Rendering.Cairo' at GUI/Timeline/Render.hs:24:1-31 (and originally defined in `Graphics.Rendering.Cairo.Types') GUI/Timeline/Render.hs:251:33: Ambiguous occurrence `width' It could refer to either `GUI.Types.width', imported from `GUI.Types' at GUI/Timeline/Render.hs:19:1-16 (and originally defined at GUI/Types.hs:30:5-9) or `Graphics.Rendering.Cairo.width', imported from `Graphics.Rendering.Cairo' at GUI/Timeline/Render.hs:24:1-31 (and originally defined in
Bug#746072: routino: FTBFS: ld: cannot find -lz
Source: routino Version: 2.7-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): gcc xsd-to-xmlparser.o ../xmlparse.o -o xsd-to-xmlparser -lm -pthread -lpthread -lbz2 -lz /usr/bin/ld: cannot find -lz collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/routino_2.7-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746073: ejabberd: FTBFS: can't find include lib ssl/include/PKIX1Explicit88.hrl
Source: ejabberd Version: 2.1.11-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/bin/erlc -W -pa . ejabberd_loglevel.erl /usr/bin/erlc -W -pa . ejabberd_node_groups.erl /usr/bin/erlc -W -pa . ejabberd_piefxis.erl /usr/bin/erlc -W -pa . ejabberd_rdbms.erl /usr/bin/erlc -W -pa . ejabberd_receiver.erl /usr/bin/erlc -W -pa . ejabberd_regexp.erl /usr/bin/erlc -W -pa . ejabberd_router.erl /usr/bin/erlc -W -pa . ejabberd_s2s.erl /usr/bin/erlc -W -pa . ejabberd_s2s_in.erl ejabberd_s2s_in.erl:62: can't find include lib ssl/include/PKIX1Explicit88.hrl ejabberd_s2s_in.erl:63: can't find include lib ssl/include/PKIX1Implicit88.hrl ejabberd_s2s_in.erl:733: undefined macro 'id-at-commonName' ejabberd_s2s_in.erl:344: function get_cert_domains/1 undefined make[1]: *** [ejabberd_s2s_in.beam] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ejabberd_2.1.11-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746077: libdessert0.87: FTBFS: ld: cannot find -lpci
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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746081: ruby-dbi: FTBFS: ERROR: Test ruby2.1 failed: wrong number of arguments (3 for 1..2)
Source: ruby-dbi Version: 0.4.5-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): Running tests for ruby2.1 with test file list from debian/ruby-test-files.yaml ... test/unit warning: method TC_DBI_Date#test_constructor is redefined test/unit warning: method TC_DBI_Date#test_to_date is redefined test/unit warning: method TC_DBI_Date#test_to_time is redefined test/unit warning: method TC_DBI_Date#test_to_s is redefined test/unit warning: method TC_DBI_Date#test_day is redefined test/unit warning: method TC_DBI_Date#test_mday is redefined test/unit warning: method TC_DBI_Date#test_month is redefined test/unit warning: method TC_DBI_Date#test_mon is redefined test/unit warning: method TC_DBI_Date#test_year is redefined Run options: # Running tests: F Finished tests in 0.032940s, 3309.0124 tests/s, 15330.7455 assertions/s. 1) Failure: TC_DBI_ColumnInfo#test_constructor [/«PKGBUILDDIR»/test/dbi/tc_columninfo.rb:42]: [TypeError] exception expected, not Class: ArgumentError Message: wrong number of arguments (3 for 1..2) ---Backtrace--- /«PKGBUILDDIR»/lib/dbi/columninfo.rb:63:in `method_missing' /«PKGBUILDDIR»/lib/dbi/columninfo.rb:40:in `block in initialize' /«PKGBUILDDIR»/lib/dbi/columninfo.rb:36:in `each' /«PKGBUILDDIR»/lib/dbi/columninfo.rb:36:in `initialize' /«PKGBUILDDIR»/test/dbi/tc_columninfo.rb:43:in `new' /«PKGBUILDDIR»/test/dbi/tc_columninfo.rb:43:in `block in test_constructor' /usr/lib/ruby/2.1.0/minitest/unit.rb:362:in `assert_raises' /«PKGBUILDDIR»/test/dbi/tc_columninfo.rb:42:in `test_constructor' /usr/lib/ruby/2.1.0/test/unit.rb:869:in `run_test' /usr/lib/ruby/2.1.0/minitest/unit.rb:1265:in `run' /usr/lib/ruby/2.1.0/test/unit/testcase.rb:17:in `run' /usr/lib/ruby/2.1.0/minitest/unit.rb:940:in `block in _run_suite' /usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `map' /usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `_run_suite' /usr/lib/ruby/2.1.0/test/unit.rb:663:in `block in _run_suites' /usr/lib/ruby/2.1.0/test/unit.rb:661:in `each' /usr/lib/ruby/2.1.0/test/unit.rb:661:in `_run_suites' /usr/lib/ruby/2.1.0/minitest/unit.rb:884:in `_run_anything' /usr/lib/ruby/2.1.0/minitest/unit.rb:1092:in `run_tests' /usr/lib/ruby/2.1.0/minitest/unit.rb:1079:in `block in _run' /usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `each' /usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `_run' /usr/lib/ruby/2.1.0/minitest/unit.rb:1066:in `run' /usr/lib/ruby/2.1.0/test/unit.rb:27:in `run' /usr/lib/ruby/2.1.0/test/unit.rb:780:in `run' /usr/lib/ruby/2.1.0/test/unit.rb:372:in `block (2 levels) in autorun' /usr/lib/ruby/2.1.0/test/unit.rb:33:in `run_once' /usr/lib/ruby/2.1.0/test/unit.rb:371:in `block in autorun' --- 109 tests, 505 assertions, 1 failures, 0 errors, 0 skips ruby -v: ruby 2.1.1p76 (2014-02-24) [x86_64-linux-gnu] ERROR: Test ruby2.1 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ruby-dbi_0.4.5-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746079: ruby-excon: FTBFS: ERROR: Test ruby2.0 failed: no implicit conversion from nil to integer (TypeError)
Source: ruby-excon Version: 0.32.1-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): no implicit conversion from nil to integer (TypeError) /«PKGBUILDDIR»/tests/test_helper.rb:286:in `kill' /«PKGBUILDDIR»/tests/test_helper.rb:286:in `ensure in with_unicorn' /«PKGBUILDDIR»/tests/test_helper.rb:291:in `with_unicorn' /«PKGBUILDDIR»/tests/basic_tests.rb:105:in `block in top (required)' /usr/lib/ruby/vendor_ruby/shindo.rb:79:in `instance_eval' /usr/lib/ruby/vendor_ruby/shindo.rb:79:in `tests' /usr/lib/ruby/vendor_ruby/shindo.rb:38:in `initialize' /usr/lib/ruby/vendor_ruby/shindo.rb:13:in `new' /usr/lib/ruby/vendor_ruby/shindo.rb:13:in `tests' /«PKGBUILDDIR»/tests/basic_tests.rb:101:in `top (required)' /usr/lib/ruby/vendor_ruby/shindo/bin.rb:61:in `load' /usr/lib/ruby/vendor_ruby/shindo/bin.rb:61:in `block (2 levels) in run_in_thread' /usr/lib/ruby/vendor_ruby/shindo/bin.rb:58:in `each' /usr/lib/ruby/vendor_ruby/shindo/bin.rb:58:in `block in run_in_thread' rake aborted! -e:1:in `main' Tasks: TOP = default = tests (See full trace by running task with --trace) ERROR: Test ruby2.0 failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ruby-excon_0.32.1-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746080: erlang-cherly: FTBFS: ERROR: OTP release 17 does not match required regex R14B04|R15B02|R15B03|R16B
Source: erlang-cherly Version: 0.12.8+dfsg-3 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): debian/rules build dh build --buildsystem=rebar --with rebar dh_testdir -O--buildsystem=rebar dh_auto_configure -O--buildsystem=rebar make[1]: Nothing to be done for `configure'. dh_auto_build -O--buildsystem=rebar rebar_compile rebar compile skip_deps=true -vv == erlang-cherly-0.12.8+dfsg (compile) ERROR: OTP release 17 does not match required regex R14B04|R15B02|R15B03|R16B make[1]: *** [rebar_compile] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/erlang-cherly_0.12.8+dfsg-3_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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746090: httraqt: FTBFS: options.cpp:295:10: error: 'httrackp' has no member named 'mms_maxtime'
Source: httraqt Version: 1.3.1-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/bin/c++ -DDISABLE_QT3SUPPORT -DNO_QT3SUPPORT -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_PROJECT -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -I/usr/include/httrack -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtScriptTools -isystem /usr/include/qt4/QtDBus -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg -I/usr/include/qt4/Qt3Support -isystem /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtCore -I/usr/share/qt4/mkspecs/default -isystem /usr/include/qt4 -I/«PKGBUILDDIR» -I/«PKGBUILDDIR»//sources/options/includes -I/«PKGBUILDDIR»//sources/main/includes -I/«PKGBUILDDIR»/obj-x86_64-linux-gnu -o CMakeFiles/httraqt.dir/sources/main/options.cpp.o -c /«PKGBUILDDIR»/sources/main/options.cpp /«PKGBUILDDIR»/sources/main/options.cpp: In member function 'void cOptions::getOptStruct(httrackp*)': /«PKGBUILDDIR»/sources/main/options.cpp:295:10: error: 'httrackp' has no member named 'mms_maxtime' opt-mms_maxtime = -1; ^ make[3]: *** [CMakeFiles/httraqt.dir/sources/main/options.cpp.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/httraqt_1.3.1-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746086: tiemu: FTBFS: configure: error: Package requirements (ticalcs2 = 1.0.7) were not met
Source: tiemu Version: 3.03-nogdb+dfsg-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): checking whether to use NLS... yes checking where the gettext function comes from... libc checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for TICABLES... yes configure: error: Package requirements (ticalcs2 = 1.0.7) were not met Package 'libarchive', required by 'tifiles2', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables TICALCS_CFLAGS and TICALCS_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/tiemu_3.03-nogdb+dfsg-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746091: frama-c: FTBFS: Error: Signature mismatch
Source: frama-c Version: 20130601+fluorine3+dfsg-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): Warning 41: Never_tried belongs to several types: consolidated_status status The first one was selected. Please disambiguate if this is wrong. File src/logic/property_status.ml, line 839, characters 9-20: Warning 41: Never_tried belongs to several types: consolidated_status status The first one was selected. Please disambiguate if this is wrong. File src/logic/property_status.ml, line 881, characters 9-20: Warning 41: Never_tried belongs to several types: consolidated_status status The first one was selected. Please disambiguate if this is wrong. File src/logic/property_status.ml, line 964, characters 6-17: Warning 41: Never_tried belongs to several types: consolidated_status status The first one was selected. Please disambiguate if this is wrong. File src/logic/property_status.ml, line 1235, characters 35-46: Warning 41: Never_tried belongs to several types: t status The first one was selected. Please disambiguate if this is wrong. File src/logic/property_status.ml, line 1392, characters 4-1999: Error: Signature mismatch: ... Values do not match: val vertex_attributes : v - [ `Color of int | `Label of string | `Shape of [ `Box | `Diamond ] | `Style of [ `Bold | `Filled ] | `Width of float ] list is not included in val vertex_attributes : V.t - Graph.Graphviz.DotAttributes.vertex list File src/logic/property_status.ml, line 1425, characters 16-33: Actual declaration make[1]: *** [src/logic/property_status.cmo] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/frama-c_20130601+fluorine3+dfsg-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746089: elastix: FTBFS: make[3]: *** No rule to make target `/usr/lib/x86_64-linux-gnu/libfftw3.so', needed by `bin/elastix'. Stop.
Source: elastix Version: 4.7-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): /«PKGBUILDDIR»/src/Core/Kernel/elxElastixTemplate.hxx:463:5: required from 'int elastix::ElastixTemplateTFixedImage, TMovingImage::ApplyTransform() [with TFixedImage = itk::Imagefloat, 2u; TMovingImage = itk::Imagefloat, 2u]' /«PKGBUILDDIR»/src/Core/Install/elxComponentLoader.cxx:189:1: required from here /«PKGBUILDDIR»/src/Common/itkImageFileCastWriter.h:36:7: warning: 'itk::ImageFileCastWriteritk::Imagefloat, 2u ' declared with greater visibility than the type of its field 'itk::ImageFileCastWriteritk::Imagefloat, 2u ::anonymous' [-Wattributes] /«PKGBUILDDIR»/src/Common/itkImageFileCastWriter.h:36:7: warning: 'itk::ImageFileCastWriteritk::Imagefloat, 2u ' declared with greater visibility than its base 'itk::ImageFileWriteritk::Imagefloat, 2u ' [-Wattributes] make[3]: *** No rule to make target `/usr/lib/x86_64-linux-gnu/libfftw3.so', needed by `bin/elastix'. Stop. make[3]: Leaving directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' make[2]: *** [Core/CMakeFiles/elastix.dir/all] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/elastix_4.7-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746087: centerim: FTBFS: libgadu.h:53:28: fatal error: gnutls/openssl.h: No such file or directory
Source: centerim Version: 4.22.10-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): x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -Wall -g -O1 -MT libgadu.o -MD -MP -MF .deps/libgadu.Tpo -c -o libgadu.o libgadu.c In file included from libgadu.c:55:0: libgadu.h:53:28: fatal error: gnutls/openssl.h: No such file or directory #include gnutls/openssl.h ^ compilation terminated. make[3]: *** [libgadu.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/centerim_4.22.10-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746083: haskell-hsmagick: FTBFS: The pkg-config package lcms is required but it could not be found
Source: haskell-hsmagick Version: 0.5-3 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): debian/rules build test -x debian/rules mkdir -p . /usr/share/cdbs/1/rules/buildcore.mk:109: WARNING: DEB_COMPRESS_EXCLUDE is a deprecated variable if test ! -e Setup.lhs -a ! -e Setup.hs; then echo No setup script found!; exit 1; fi for setup in Setup.lhs Setup.hs; do if test -e $setup; then ghc --make $setup -o debian/hlibrary.setup; exit 0; fi; done [1 of 1] Compiling Main ( Setup.lhs, Setup.o ) Linking debian/hlibrary.setup ... debian/hlibrary.setup configure --ghc -v2 \ --prefix=/usr --libdir=/usr/lib/haskell-packages/ghc/lib \ --builddir=dist-ghc \ --haddockdir=/usr/lib/ghc-doc/haddock/hsmagick-0.5/ --datasubdir=hsmagick\ --htmldir=/usr/share/doc/libghc-hsmagick-doc/html/ --enable-library-profiling \ Configuring hsmagick-0.5... Dependency base 5: using base-4.6.0.1 Dependency bytestring -any: using bytestring-0.10.0.2 Dependency directory -any: using directory-1.2.0.1 Dependency filepath -any: using filepath-1.3.0.1 Dependency pretty -any: using pretty-1.1.1.0 Dependency process -any: using process-1.1.0.2 hlibrary.setup: The pkg-config package lcms is required but it could not be found. Dependency GraphicsMagick =1.3.3: using version 1.3.18 make: *** [dist-ghc] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/haskell-hsmagick_0.5-3_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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746082: libalog: FTBFS: error: aws-net-std__gnat.adb must be compiled
Source: libalog Version: 0.4.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): make[2]: Entering directory `/«PKGBUILDDIR»' ar rv obj/lib/libglue.a obj/full/lib/dynamic/glue_syslog.o r - obj/full/lib/dynamic/glue_syslog.o gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/tests/runner_full.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/tests/facility_tests.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/tests/facility_tests-pgsql.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/tests/facility_tests-smtp.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/tests/facility_tests-xmpp.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog.ads gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-facilities.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-facilities-file_descriptor.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-facilities-pgsql.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-log_request.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-facilities-smtp.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-facilities-xmpp.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-policy_db.adb gcc-4.6 -c -g -gnatygAdISuxo -gnatVa -gnat05 -gnatwal -gnatf -fstack-check -gnato -I- -gnatA /«PKGBUILDDIR»/src/alog-maps.adb gnatbind -shared -E -I- -x /«PKGBUILDDIR»/obj/full/runner_full.ali error: aws-net-std__gnat.adb must be compiled error: (/usr/lib/ada/adalib/aws/aws-net-std__gnat.ali is obsolete and read-only) error: g-socket.adb must be compiled error: (/usr/lib/gcc/x86_64-linux-gnu/4.6/adalib/g-socket.ali is obsolete and read-only) error: g-soliop.ads must be compiled error: (/usr/lib/gcc/x86_64-linux-gnu/4.6/adalib/g-soliop.ali is obsolete and read-only) error: g-socthi.adb must be compiled error: (/usr/lib/gcc/x86_64-linux-gnu/4.6/adalib/g-socthi.ali is obsolete and read-only) error: g-sothco.adb must be compiled error: (/usr/lib/gcc/x86_64-linux-gnu/4.6/adalib/g-sothco.ali is obsolete and read-only) error: g-soccon.ads must be compiled error: (/usr/lib/gcc/x86_64-linux-gnu/4.6/adalib/g-soccon.ali is obsolete and read-only) gnatmake: *** bind failed. make[2]: *** [build_tests] Error 4 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/libalog_0.4.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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746092: libwx-scintilla-perl: FTBFS: (.text+0x20): undefined reference to `main'
Source: libwx-scintilla-perl Version: 0.38-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 -o scintilladll_XPM.o CC -o scintilladll_PlatWX.o CC -o scintilladll_ScintillaWX.o CC -o scintilladll_scintilla.o CC -o libwx_gtk2u_scintilla-3.0.0.so /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/crt1.o: In function `_start': (.text+0x20): undefined reference to `main' collect2: error: ld returned 1 exit status The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/libwx-scintilla-perl_0.38-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746085: ardesia: FTBFS: configure: error: Test for GTK3+ failed
Source: ardesia Version: 1.1-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): checking for pkg-config... /usr/bin/pkg-config checking for GTK+ - version = 2.99.3... no *** Could not run GTK+ test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means GTK+ is incorrectly installed. configure: error: Test for GTK3+ failed. See the file 'INSTALL' for help. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ardesia_1.1-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746084: rake-compiler: FTBFS: ERROR: Test ruby2.1 failed: Failure/Error: Rake::Task.should have_defined('compile:universal-known')
Source: rake-compiler
Version: 0.9.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):
Failure/Error: Rake::Task.should have_defined('compile:universal-known')
expected Rake::Task to have defined compile:universal-known
# ./spec/lib/rake/extensiontask_spec.rb:454:in `block (5 levels) in top
(required)'
Finished in 0.2249 seconds
84 examples, 10 failures, 4 pending
Failed examples:
rspec ./spec/lib/rake/extensiontask_spec.rb:396 # Rake::ExtensionTask (tasks)
(cross platform tasks) (cross for 'universal-unknown' platform) fake should
chain fake task to Makefile generation
rspec ./spec/lib/rake/extensiontask_spec.rb:402 # Rake::ExtensionTask (tasks)
(cross platform tasks) (cross for 'universal-unknown' platform) rbconfig
should chain rbconfig tasks to Makefile generation
rspec ./spec/lib/rake/extensiontask_spec.rb:406 # Rake::ExtensionTask (tasks)
(cross platform tasks) (cross for 'universal-unknown' platform) rbconfig
should take rbconfig from rake-compiler configuration
rspec ./spec/lib/rake/extensiontask_spec.rb:412 # Rake::ExtensionTask (tasks)
(cross platform tasks) (cross for 'universal-unknown' platform) mkmf should
chain mkmf tasks to Makefile generation
rspec ./spec/lib/rake/extensiontask_spec.rb:416 # Rake::ExtensionTask (tasks)
(cross platform tasks) (cross for 'universal-unknown' platform) mkmf should
take mkmf from rake-compiler configuration
rspec ./spec/lib/rake/extensiontask_spec.rb:423 # Rake::ExtensionTask (tasks)
(cross platform tasks) (cross for 'universal-unknown' platform)
compile:universal-unknown should be defined
rspec ./spec/lib/rake/extensiontask_spec.rb:427 # Rake::ExtensionTask (tasks)
(cross platform tasks) (cross for 'universal-unknown' platform)
compile:universal-unknown should depend on
'compile:extension_one:universal-unknown'
rspec ./spec/lib/rake/extensiontask_spec.rb:433 # Rake::ExtensionTask (tasks)
(cross platform tasks) (cross for 'universal-unknown' platform)
native:universal-unknown should be defined
rspec ./spec/lib/rake/extensiontask_spec.rb:437 # Rake::ExtensionTask (tasks)
(cross platform tasks) (cross for 'universal-unknown' platform)
native:universal-unknown should depend on 'native:my_gem:universal-unknown'
rspec ./spec/lib/rake/extensiontask_spec.rb:453 # Rake::ExtensionTask (tasks)
(cross platform tasks) (cross for multiple platforms) should define task for
each supplied platform
/usr/bin/ruby2.1 -S rspec ./spec/lib/rake/extensiontask_spec.rb
./spec/lib/rake/javaextensiontask_spec.rb failed
ERROR: Test ruby2.1 failed:
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/04/26/rake-compiler_0.9.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.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746088: scilab-metanet: FTBFS: cp: cannot stat 'debian/tmp/loader.sce': No such file or directory
Source: scilab-metanet Version: 0.6-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): fakeroot debian/rules binary test -x debian/rules dh_testroot dh_prep dh_installdirs -A mkdir -p . Adding cdbs dependencies to debian/scilab-metanet.substvars dh_installdirs -pscilab-metanet mkdir -p /«PKGBUILDDIR»/debian/scilab-metanet/usr/lib/scilab-metanet/ mkdir -p /«PKGBUILDDIR»/debian/scilab-metanet/usr/share/scilab/contrib/ cd /«PKGBUILDDIR»/debian/scilab-metanet/usr/share/scilab/contrib/; \ rm -f scilab-metanet; \ ln -s ../../../lib/scilab-metanet/ metanet dh_installdocs -pscilab-metanet dh_installexamples -pscilab-metanet dh_installman -pscilab-metanet dh_installinfo -pscilab-metanet dh_installmenu -pscilab-metanet dh_installcron -pscilab-metanet dh_installinit -pscilab-metanet dh_installdebconf -pscilab-metanet dh_installemacsen -pscilab-metanet dh_installcatalogs -pscilab-metanet dh_installpam -pscilab-metanet dh_installlogrotate -pscilab-metanet dh_installlogcheck -pscilab-metanet dh_installchangelogs -pscilab-metanet dh_installudev -pscilab-metanet dh_lintian -pscilab-metanet dh_bugfiles -pscilab-metanet dh_install -pscilab-metanet cp: cannot stat 'debian/tmp/loader.sce': No such file or directory dh_install: cp -a debian/tmp/loader.sce debian/scilab-metanet/usr/lib/scilab-metanet/ returned exit code 1 make: *** [binary-install/scilab-metanet] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/scilab-metanet_0.6-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746094: eliom: FTBFS: Error while running external preprocessor
Source: eliom Version: 3.0.3-4 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): make[5]: Entering directory `/«PKGBUILDDIR»/src/server' ocamlfind ocamldoc -thread -ppopt o -ppopt -printer -syntax camlp4o -I private -I extensions -package ocsigenserver -package ocsigenserver.ext -package js_of_ocaml.deriving -package react -package calendar -package tyxml -package lwt.react -package cryptokit -package js_of_ocaml.deriving.syntax -package lwt.syntax -package tyxml.syntax -ppopt ../syntax/pa_include.cmo -dump eliom_lib.odoc eliom_lib.mli Error: don't know what to do with o Use option -help for usage Preprocessing error Error while running external preprocessor Command line: camlp4 '-I' '/usr/lib/ocaml/camlp4' '-I' '/usr/lib/ocaml' '-I' '/usr/lib/ocaml/deriving-ocsigen' '-I' '/usr/lib/ocaml/js_of_ocaml' '-I' '/usr/lib/ocaml/lwt' '-I' '/usr/lib/ocaml/lwt' '-I' '/usr/lib/ocaml/tyxml' '-parser' 'o' '-parser' 'op' '-printer' 'p' 'unix.cma' 'pa_deriving.cma' 'pa_deriving_Json.cmo' 'lwt-syntax-options.cma' 'lwt-syntax.cma' 'pa_tyxml.cmo' 'o' '-printer' '../syntax/pa_include.cmo' 'eliom_lib.mli' /tmp/ocamlpp88a78f make[5]: *** [eliom_lib.odoc] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/eliom_3.0.3-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- 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 725070 is serious
Processing commands for cont...@bugs.debian.org: severity 725070 serious Bug #725070 [taglog] taglog: FTBFS after alternatives for /usr/bin/tclsh will be dropped Severity set to 'serious' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 725070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725070 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#746098: ruby-packetfu: FTBFS: E: ruby1.9.1 is not supported by gem2deb anymore
Source: ruby-packetfu Version: 1.1.8-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): fakeroot debian/rules binary dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby Entering dh_ruby --install E: ruby1.9.1 is not supported by gem2deb anymore dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-packetfu returned exit code 1 make: *** [binary] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ruby-packetfu_1.1.8-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746099: ibus-cangjie: FTBFS: Tests failures
Source: ibus-cangjie Version: 2.1-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): make[8]: Entering directory `/«PKGBUILDDIR»' make[8]: Leaving directory `/«PKGBUILDDIR»' make[7]: Leaving directory `/«PKGBUILDDIR»' make[6]: Leaving directory `/«PKGBUILDDIR»' Testsuite summary for ibus-cangjie 2.1 # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to https://github.com/Cangjians/ibus-cangjie/issues make[5]: *** [test-suite.log] Error 1 make[5]: Leaving directory `/«PKGBUILDDIR»' make[4]: *** [check-TESTS] Error 2 make[4]: Leaving directory `/«PKGBUILDDIR»' make[3]: *** [check-am] Error 2 make[2]: *** [check-recursive] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: *** [check] Error 2 dh_auto_test: make -j1 check returned exit code 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/ibus-cangjie_2.1-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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746101: claws-mail: FTBFS: dh_install: claws-mail-gdata-plugin missing files (usr/lib/*/claws-mail/plugins/gdata.so), aborting
Source: claws-mail Version: 3.9.3-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): make[4]: Entering directory `/«PKGBUILDDIR»' make[4]: Leaving directory `/«PKGBUILDDIR»' make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' dh_install -O--parallel dh_install: claws-mail-gdata-plugin missing files (usr/lib/*/claws-mail/plugins/gdata.so), aborting make: *** [binary] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/claws-mail_3.9.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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
