Bug#729321: marked as done (keyboard-configuration: changes /etc/default/keyboard upon upgrade without asking)
Your message dated Mon, 04 Aug 2014 06:19:33 + with message-id e1xebcl-0002xp...@franck.debian.org and subject line Bug#729321: fixed in console-setup 1.110 has caused the Debian Bug report #729321, regarding keyboard-configuration: changes /etc/default/keyboard upon upgrade without asking 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.) -- 729321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: keyboard-configuration Version: 1.103 Severity: serious After upgrading keyboard-configuration from 1.102 to 1.103, /etc/default/keyboard was changed (perhaps to some old state?). The state before was: | # KEYBOARD CONFIGURATION FILE | | # Consult the keyboard(5) manual page. | | XKBMODEL=pc105 | XKBLAYOUT=de | XKBVARIANT=nodeadkeys | XKBOPTIONS=compose:rwin,terminate:ctrl_alt_bksp,caps:none | | BACKSPACE=guess Afterwards the caps:none was gone. There were no questions asked while upgrading. -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Kernel: Linux 3.11-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages keyboard-configuration depends on: ii debconf 1.5.52 ii initscripts 2.88dsf-43 ii liblocale-gettext-perl 1.05-7+b2 keyboard-configuration recommends no packages. keyboard-configuration suggests no packages. Versions of packages console-setup depends on: ii console-setup-linux 1.103 ii debconf 1.5.52 ii xkb-data 2.5.1-3 Versions of packages console-setup suggests: ii locales 2.17-94 ii lsb-base 4.1+Debian12 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-1 Versions of packages console-setup-linux suggests: ii console-setup 1.103 Versions of packages keyboard-configuration is related to: pn console-common none pn console-datanone pn console-tools none ii kbd 1.15.5-1 -- debconf information: * keyboard-configuration/layoutcode: de * keyboard-configuration/optionscode: compose:rwin,terminate:ctrl_alt_bksp debian-installer/console-setup-udeb/title: * keyboard-configuration/layout: * keyboard-configuration/switch: No temporary switch * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages * console-setup/fontsize-fb47: 8x16 * keyboard-configuration/modelcode: pc105 keyboard-configuration/unsupported_layout: true console-setup/framebuffer_only: * keyboard-configuration/unsupported_config_options: false * keyboard-configuration/variantcode: nodeadkeys * keyboard-configuration/toggle: No toggling * console-setup/charmap47: UTF-8 console-setup/store_defaults_in_debconf_db: true * keyboard-configuration/altgr: The default for the keyboard layout * keyboard-configuration/compose: Right Logo key * keyboard-configuration/other: console-setup/use_system_font: * keyboard-configuration/variant: German - German (eliminate dead keys) * console-setup/fontface47: Fixed * keyboard-configuration/model: Generic 105-key (Intl) PC * keyboard-configuration/ctrl_alt_bksp: true keyboard-configuration/unsupported_options: true console-setup/codesetcode: Lat15 keyboard-configuration/unsupported_config_layout: true * keyboard-configuration/xkb-keymap: de(nodeadkeys) * keyboard-configuration/store_defaults_in_debconf_db: true console-setup/fontsize: 8x16 console-setup/fontsize-text47: 8x16 console-setup/guess_font: ---End Message--- ---BeginMessage--- Source: console-setup Source-Version: 1.110 We believe that the bug you reported is fixed in the latest version of console-setup, 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 729...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Perrier bubu...@debian.org (supplier of updated console-setup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 03 Aug 2014 09:00:30 +0200 Source: console-setup Binary: keyboard-configuration console-setup console-setup-mini console-setup-linux console-setup-freebsd bdf2psf
Bug#753121: [Pkg-libvirt-maintainers] Bug#753121: libvirt: diff for NMU version 1.2.4-3.1
On Sun, Aug 03, 2014 at 07:27:27PM +0200, Guido Günther wrote: Are you done with your parted transition? Seems 3.1-4 entered testing? Just wanted to be sure I'm not going to screw your work with libvirt 1.2.7. Yes, that's all done, so go ahead. Thanks for checking. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 756097
Processing commands for cont...@bugs.debian.org: tags 756097 + pending Bug #756097 [systemd] FTBFS: sys/xattr.h:32:3: error: expected identifier before numeric constant Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 756097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756097 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#744215: wvdial: Segmentation fault during modem initialization
Package: wvdial Followup-For: Bug #744215 Dear Maintainer, I've currently using wvdial since many year on my system and it never ever occurs the error reported in this bug report. The connection on my usb GSM-modem works smoothly. The system has always be updated regularly. Maybe the bug is specific to the previous user installation (like maybe the Architecture). Therefore I would suggest to update the severity of the bug in order to let it get into the testing reposiory. Thank you, Risca. Here some additional information: -- Launching wvdial: --- $ wvdial connect -- WvDial: Internet dialer version 1.61 -- Cannot get information for serial port. -- Initializing modem. -- Sending: ATZ OK -- Sending: ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 OK -- Modem initialized. -- Sending: ATDT*99# -- Waiting for carrier. ATDT*99# CONNECT 1440 ~~ -- Carrier detected. Starting PPP immediately. -- Starting pppd at Mon Aug 4 08:00:35 2014 -- Pid of pppd: 4082 -- Using interface ppp0 -- pppd: [18]�P [08]�P -- pppd: [18]�P [08]�P -- pppd: [18]�P [08]�P -- pppd: [18]�P [08]�P -- local IP address 10.13.17.183 -- pppd: [18]�P [08]�P -- remote IP address 10.0.0.1 -- pppd: [18]�P [08]�P -- primary DNS address 193.70.152.25 -- pppd: [18]�P [08]�P -- secondary DNS address 212.52.97.25 -- pppd: [18]�P [08]�P -- Configuration of /etc/wvdial: [Dialer Defaults] Stupid Mode = on Modem Type = USB Modem New PPPD = yes Auto Reconnect = on [Dialer signal] Modem = /dev/ttyACM0 Init1 = AT+CSQ Init2 = AT+COPS? [Dialer connect] Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 ISDN = 0 Phone = *99# Modem = /dev/ttyACM1 Username = Wind Password = Wind Baud = 460800 - -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (915, 'stable-updates'), (910, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 wvdial depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38+deb7u1 ii libgcc1 1:4.7.2-5 ii libstdc++6 4.7.2-5 ii libuniconf4.6 4.6.1-5 ii libwvstreams4.6-base4.6.1-5 ii libwvstreams4.6-extras 4.6.1-5 ii ppp 2.4.5-5.1+b1 wvdial recommends no packages. wvdial suggests no packages. -- debconf information: wvdial/phone: wvdial/passphrases_mismatch: wvdial/wvdialconf: true wvdial/login: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749347: marked as done (ledgersmb: fails to install)
Your message dated Mon, 04 Aug 2014 07:33:48 + with message-id e1xecmc-0003qr...@franck.debian.org and subject line Bug#749347: fixed in ledgersmb 1.3.40-1 has caused the Debian Bug report #749347, regarding ledgersmb: fails to install 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.) -- 749347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ledgersmb Version: 1.3.39-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package ledgersmb. (Reading database ... 13616 files and directories currently installed.) Preparing to unpack .../ledgersmb_1.3.39-1_all.deb ... Unpacking ledgersmb (1.3.39-1) ... Setting up ledgersmb (1.3.39-1) ... cp: cannot stat '/usr/share/ledgersmb/ledgersmb-http-2.4.conf.template': No such file or directory dpkg: error processing package ledgersmb (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: ledgersmb E: Sub-process /usr/bin/dpkg returned an error code (1) 0m45.3s ERROR: Command failed (status=100): ['chroot', '/srv/piuparts.debian.org/tmp/tmpGQdCwW', 'apt-get', '-y', 'install', 'ledgersmb=1.3.39-1'] cheers, Holger Start: 2014-05-18 05:20:19 UTC Package: ledgersmb Version: 1.3.39-1 Installed-Size: 11030 Maintainer: Debian LedgerSMB Team pkg-sql-ledger-discuss...@lists.alioth.debian.org Architecture: all Replaces: ledger-smb Depends: apache2 | httpd-cgi, dbconfig-common, libcgi-simple-perl, libconfig-any-perl, libconfig-std-perl, libdatetime-perl, libdbd-pg-perl, libdbi-perl, liberror-perl, libfile-mimeinfo-perl, libhtml-parser-perl, libio-stringy-perl, liblocale-maketext-lexicon-perl (= 0.62-1), liblog-log4perl-perl, libmime-lite-perl, libtemplate-perl (= 2.14-1), perl (= 5.8.1-1), postgresql-client, postgresql-contrib, debconf (= 0.5) | debconf-2.0 Recommends: default-mta | mail-transport-agent, libmath-bigint-gmp-perl, libopenoffice-oodoc-perl, libparse-recdescent-perl, libtemplate-plugin-latex-perl, texlive-latex-recommended Suggests: latex-cjk-all, libimage-size-perl, libnet-tclink-perl, libplack-perl, postgresql, lpr Conflicts: ledger-smb Description: financial accounting and ERP program Homepage: http://www.ledgersmb.org/ Description-md5: 0e44af624a279cda54f6947f69798626 Section: web Priority: optional Filename: pool/main/l/ledgersmb/ledgersmb_1.3.39-1_all.deb Size: 1880184 MD5sum: 9ec277bbd301c6095425618889d8052a SHA1: e0d099405834b90d30870a5d75be309ad369ef6d SHA256: ce47c510d7950c452dfafaffe7222d6193db77a52bb71ac7343cc49b0cb182b3 Executing: sudo env PYTHONPATH=/srv/piuparts.debian.org/lib/python2.7/dist-packages timeout -s INT -k 5m 35m /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt ledgersmb=1.3.39-1 0m0.0s INFO: -- 0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile. 0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ 0m0.0s INFO: The FAQ also explains how to contact us in case you think piuparts is wrong. 0m0.0s INFO: -- 0m0.0s INFO: piuparts version 0.59~201405171014~0.58-17-g007fbc6 starting up. 0m0.0s INFO: Command line arguments: /srv/piuparts.debian.org/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --scriptsdir /etc/piuparts/scripts --no-eatmydata --allow-database --warn-on-leftovers-after-purge --mirror 'http://mirror.bm.debian.org/debian/ main' --tmpdir /srv/piuparts.debian.org/tmp --arch amd64 -b /srv/piuparts.debian.org/slave/basetgz/jessie_amd64.tar.gz -d jessie --no-upgrade-test --apt ledgersmb=1.3.39-1 0m0.0s INFO: Running on: Linux piu-slave-bm-a 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u1 x86_64 0m0.0s DEBUG: Created temporary directory /srv/piuparts.debian.org/tmp/tmpGQdCwW 0m0.0s DEBUG: Unpacking
Processed: Re: gnome-shell: Gnome-Shell 3.13-1 hangs at GDM
Processing control commands: tags -1 + moreinfo Bug #756941 [gnome-shell] gnome-shell: Gnome-Shell 3.13-1 hangs at GDM Added tag(s) moreinfo. -- 756941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756941 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#756941: gnome-shell: Gnome-Shell 3.13-1 hangs at GDM
Control: tags -1 + moreinfo Hello! Justification: renders package unusable I'm running this version, so I have to disagree. I looked at the logs see that Gnome-session should be updated also. Could you please provide the logs? Everything works here with gnome-session 3.12. (There was no gnome-session 3.13.1 release at all, so would be very hard to upgrade to it.) Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756780: [Help] Need help for architecture specific code (Was: Bug#756780: bowtie: FTBFS almost everywhere)
Hi,
on arm*, powerpc, sparc and s390x architectures the build problem is:
third_party/cpuid.h: In constructor 'EbwtTStr::Ebwt(int, int32_t, int32_t,
int32_t, int32_t, int32_t, const string, bool, bool, uint32_t, uint32_t,
uint32_t, int, std::vectorFileBuf*, std::vectorRefRecord,
std::vectorunsigned int, uint32_t, const RefReadInParams, uint32_t,
int32_t, int32_t, bool, bool, bool) [with TStr =
seqan::Stringseqan::SimpleTypeunsigned char, seqan::Dna_, seqan::Alloc ;
int32_t = int; std::string = std::basic_stringchar; uint32_t = unsigned int]':
third_party/cpuid.h:162:46: error: impossible constraint in 'asm'
__cpuid (__ext, __eax, __ebx, __ecx, __edx);
^
third_party/cpuid.h:185:52: error: impossible constraint in 'asm'
__cpuid (__level, *__eax, *__ebx, *__ecx, *__edx);
^
make[2]: *** [bowtie-build] Error 1
on mips* the problem is:
/tmp/cciY8R8w.s:161449: Error: unrecognized opcode `push{l} $14'
/tmp/cciY8R8w.s:161450: Error: unrecognized opcode `popf{l|d}'
/tmp/cciY8R8w.s:161451: Error: unrecognized opcode `pushf{l|d}'
/tmp/cciY8R8w.s:161452: Error: unrecognized opcode `pop{l} $14'
/tmp/cciY8R8w.s:161453: Error: unrecognized opcode `popf{l|d}'
/tmp/cciY8R8w.s:161585: Error: unrecognized opcode `cpuid'
/tmp/cciY8R8w.s:161606: Error: unrecognized opcode `cpuid'
make[2]: *** [bowtie-build] Error 1
and on *-i386 the problem seems to be
typedef typename ValueTStr::Type TAlphabet;
^
ebwt.h: Assembler messages:
ebwt.h:1909: Error: invalid instruction suffix for `popcnt'
ebwt.h:1909: Error: invalid instruction suffix for `popcnt'
ebwt.h:1909: Error: invalid instruction suffix for `popcnt'
ebwt.h:1909: Error: invalid instruction suffix for `popcnt'
make[2]: *** [bowtie-build] Error 1
make[1]: *** [override_dh_auto_build] Error 2
Makefile:211: recipe for target 'bowtie-build' failed
I admit I do not have the slightest idea how to deal with issues
like this. Any (also partial help) is welcome.
Kind regards
Andreas.
On Fri, Aug 01, 2014 at 06:20:13PM +0200, Sebastian Ramacher wrote:
Source: bowtie
Version: 1.0.1-1
Severity: serious
Justification: fails to build from source
bowtie failed to build on almost every architecture. Please take a look
at https://buildd.debian.org/status/package.php?p=bowtie
Cheers
--
Sebastian Ramacher
___
Debian-med-packaging mailing list
debian-med-packag...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747506: openjdk-6: cannot load libsikuli-script-java any more
Thank you for the bug report. Do you think you could provide a test case to reproduce this error please? Do you know if it also fails with openjdk-7? Emmanuel Bourg signature.asc Description: OpenPGP digital signature
Bug#756780: [Help] Need help for architecture specific code (Was: Bug#756780: bowtie: FTBFS almost everywhere)
On Mon, Aug 4, 2014 at 3:48 PM, Andreas Tille wrote: third_party/cpuid.h No idea about this problem but here is what I could figure out based on the filename and the errors, using packages.d.o, codesearch.d.n and a quick look at wikipedia. third_party/cpuid.h looks like an outdated copy of the cpuid.h header from gcc, please ask upstream to remove it and just use the normal one. The cpuid.h header seems to be only/mainly on x86 based platforms: https://packages.debian.org/search?arch=anysearchon=contentskeywords=cpuid.h If upstream was using autotools, they could detect if the header is present and only then enable the cpuid stuff. The bowtie2 package appears to only be available on *-amd64 (same issue I guess, some code seems similar): https://buildd.debian.org/status/package.php?p=bowtie2suite=unstable Looking at some valgrind code (thanks to codesearch) it seems you have to use popcntq on amd64 and popcnt on non-amd64 platforms. http://sources.debian.net/src/valgrind/latest/none/tests/amd64/sse4-64.c#L2039 BTW, what is the difference between bowtie and bowtie2? Do we need both in the archive? -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753589: systemd: missing pre-dependencies for runlevel(8) etc.
Policy says new Pre-Depends should be discussed on debian-devel so let's
try that. (Please do not derail this thread into discussing whether
systemd is a good thing or not, everyone is tired of that.)
Quick summary of #753589 for debian-devel readers: Essential:yes packages are
expected to provide their functionality while merely unpacked, even when
not yet configured. The new init package is Essential:yes, and the
functionality it represents includes sysvinit-compatible implementations
of runlevel(8), shutdown(8), halt(8), telinit(8), poweroff(8) and reboot(8).
At least runlevel(8) is actively used via invoke-rc.d in maintainer scripts,
leading to #753589.
(Side point: I'm also going to open a bug asking that invoke-rc.d stop
trying to determine the runlevel under systemd, because it's rather
meaningless. The same is probably true of Upstart.)
init pre-depends on a sysv-compatible init implementation to provide
those tools: sysvinit-core | systemd-sysv | upstart. This makes those tools
transitively Essential, so they are also expected to function when
merely unpacked.
Under systemd-sysv, all of those tools are symlinks to /bin/systemctl.
Michael's proposed patch is simple:
diff --git a/debian/rules b/debian/rules
...
+# the SysV compat tools (which are symlinks to systemctl) are quasi-essential
+# so we add the depencencies of systemctl to Pre-Depends
+# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753589
+override_dh_shlibdeps:
+ dh_shlibdeps -psystemd -- -dPre-Depends -edebian/systemd/bin/systemctl
-dDepends
+ dh_shlibdeps --remaining-packages
resulting in:
Control files: lines which differ (wdiff format)
Depends: libacl1 (= 2.2.51-8), libaudit1 (= 1:2.2.1), libblkid1 (=
2.17.2), [-libc6 (= 2.17),-] libcap2 (= 2.10), libcryptsetup4 (= 2:1.4.3),
libdbus-1-3 (= 1.1.1), [-libgcrypt11 (= 1.5.1),-] libkmod2 (= 5~),
[-liblzma5 (= 5.1.1alpha+20120614),-] libpam0g (= 0.99.7.1), libselinux1
(= 2.1.9), [-libsystemd-daemon0 (= 208-5),-] libsystemd-journal0 (= 208-5),
libudev1 (= 189), libwrap0 (= 7.6-4~), libsystemd-login0 (= 208-5),
util-linux (= 2.19.1-2), initscripts (= 2.88dsf-17), sysv-rc, udev, acl,
adduser, libcap2-bin
{+Pre-Depends: libc6 (= 2.17), libdbus-1-3 (= 1.0.2), libgcrypt11 (=
1.5.1), liblzma5 (= 5.1.1alpha+20120614), libselinux1 (= 2.0.65),
libsystemd-daemon0 (= 208-5)+}
Expanded dependency tree:
libc6 is already quasi-Essential, via e.g. coreutils
libdbus-1-3 Depends: libc6 (= 2.17)
libgcrypt11 Depends: libc6 (= 2.15)
libgcrypt11 Depends: libgpg-error0 (= 1.10), already satisfied in stable
libgpg-error0 Depends: libc6 (= 2.14)
liblzma5 Depends: libc6 (= 2.4), already satisfied in stable
libselinux1 is already quasi-Essential, via coreutils
libsystemd-daemon0 Depends: libc6 (= 2.8), already satisfied in stable
Michael wrote:
The Pre-Depends list is still a bit long.
But I guess there is no way around to it.
I don't think that list looks too bad: all the libraries added to it
are quite self-contained. The only way I can see to reduce that list
would be to reimplement the sysv compatibility tools as one or more
separate binaries, in which case the question would be: how much
of their functionality is Essential? I don't see any reason why
it would be reasonable for a maintainer script to do anything
with those tools except runlevel, telinit q, or telinit u.
S
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 753589 to systemd: needs Pre-Depends for transitively Essential functionality of systemd-sysv
Processing commands for cont...@bugs.debian.org: retitle 753589 systemd: needs Pre-Depends for transitively Essential functionality of systemd-sysv Bug #753589 [systemd] systemd: Missing dependency on glibc? Changed Bug title to 'systemd: needs Pre-Depends for transitively Essential functionality of systemd-sysv' from 'systemd: Missing dependency on glibc?' thanks Stopping processing here. Please contact me if you need assistance. -- 753589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753589 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#756992: upstart: needs Pre-Depends for transitively Essential functionality
Source: upstart Version: 1.11-3 Severity: serious Justification: Policy 3.8 It looks as though Upstart has the same issue as systemd-sysv bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753589. The runlevel(8) interface (and possibly others) is transitively Essential, so it is expected to work when the init package is merely unpacked, and not necessarily configured. As a result, it is likely to need Pre-Depends on the libraries used by runlevel, currently libnih1 and libc6. -- System Information: Debian Release: jessie/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746170: Additional info
I noticed that although nfs-common, rpcbind and all have been changed , I still have the links in rc2.d, rc3.d and so on. Maybe the update-rc.d install default does not clear the links and before it a update-rc.d remove should be issued. I deleted them manually and reinstalled this version and it seems to work: reinstalling nfs-common did not seem to crash. --eric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753117: marked as done (flickrbackup: Package broke after Flickr forces the use of https connections)
Your message dated Mon, 04 Aug 2014 09:19:27 + with message-id e1xeeqr-000812...@franck.debian.org and subject line Bug#753117: fixed in flickrbackup 0.2-3.1 has caused the Debian Bug report #753117, regarding flickrbackup: Package broke after Flickr forces the use of https connections 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.) -- 753117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flickrbackup Version: 0.2-3 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, * What led up to the situation? flickrbackup does not work at all anymore after: https://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june- 27th-2014/ I changed the http calls to https calls in the code, and the package works fine again. I'm attaching a patch. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13.1 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages flickrbackup depends on: ii python 2.7.6-2 ii python-pyexiv2 0.3.2-6+b1 flickrbackup recommends no packages. flickrbackup suggests no packages. -- no debconf information --- flickrbackup.orig 2011-11-05 00:00:00.0 +0100 +++ flickrbackup 2014-06-29 13:42:00.0 +0200 @@ -54,7 +54,7 @@ hash = hashlib.md5(string).digest().encode(hex) # Formulate the request -url= http://api.flickr.com/services/rest/?method=flickr.auth.getFrob; +url= https://api.flickr.com/services/rest/?method=flickr.auth.getFrob; url += api_key= + API_KEY + api_sig= + hash try: @@ -84,7 +84,7 @@ hash = hashlib.md5(string).digest().encode(hex) # Formulate the request -url= http://api.flickr.com/services/auth/?; +url= https://api.flickr.com/services/auth/?; url += api_key= + API_KEY + perms= + perms url += frob= + frob + api_sig= + hash @@ -109,7 +109,7 @@ hash = hashlib.md5(string).digest().encode(hex) # Formulate the request -url= http://api.flickr.com/services/rest/?method=flickr.auth.getToken; +url= https://api.flickr.com/services/rest/?method=flickr.auth.getToken; url += api_key= + API_KEY + frob= + frob url += api_sig= + hash @@ -162,7 +162,7 @@ def getphoto(id, token, filename): try: # Contruct a request to find the sizes -url = http://api.flickr.com/services/rest/?method=flickr.photos.getSizes; +url = https://api.flickr.com/services/rest/?method=flickr.photos.getSizes; url += photo_id= + id # Sign the request @@ -207,7 +207,7 @@ def getmetadata(id, token): try: # Contruct a request to find the sizes -url = http://api.flickr.com/services/rest/?method=flickr.photos.getInfo; +url = https://api.flickr.com/services/rest/?method=flickr.photos.getInfo; url += photo_id= + id # Sign the request @@ -313,7 +313,7 @@ cache.close() # Now, construct a query for the list of photo sets -url = http://api.flickr.com/services/rest/?method=flickr.photosets.getList; +url = https://api.flickr.com/services/rest/?method=flickr.photosets.getList; url += user_id= + config[user] url = flickrsign(url, config[token]) @@ -334,7 +334,7 @@ dir = normalizeToASCII(dir) # Build the list of photos -url = http://api.flickr.com/services/rest/?method=flickr.photosets.getPhotos; +url = https://api.flickr.com/services/rest/?method=flickr.photosets.getPhotos; url += photoset_id= + pid # Append to our list of urls @@ -344,11 +344,11 @@ dom.unlink() # Add the photos which are not in any set -url = http://api.flickr.com/services/rest/?method=flickr.photos.getNotInSet; +url = https://api.flickr.com/services/rest/?method=flickr.photos.getNotInSet; urls.append( (url, No Set) ) # Add the user's Favourites -url = http://api.flickr.com/services/rest/?method=flickr.favorites.getList; +url = https://api.flickr.com/services/rest/?method=flickr.favorites.getList; urls.append( (url, Favourites) ) # Time to get the photos ---End Message--- ---BeginMessage--- Source: flickrbackup Source-Version: 0.2-3.1 We believe that the bug you reported is fixed in the latest version of flickrbackup,
Bug#755404: marked as done (libept1.4.12: /usr/lib/libept.so.1.0.5.4.12 is a dangling symlink)
Your message dated Mon, 04 Aug 2014 09:19:42 + with message-id e1xeeqg-00088x...@franck.debian.org and subject line Bug#755404: fixed in goplay 0.5-1.2 has caused the Debian Bug report #755404, regarding libept1.4.12: /usr/lib/libept.so.1.0.5.4.12 is a dangling symlink 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.) -- 755404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: goplay Version: 0.5-1.1 Severity: serious Goplay do not start, the following error is printed: goplay: error while loading shared libraries: libept.so.1.0.5.4.12: cannot open shared object file: No such file or directory --- System information. --- Architecture: amd64 Kernel: Linux 3.14-1-amd64 -- Best wishes, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part. ---End Message--- ---BeginMessage--- Source: goplay Source-Version: 0.5-1.2 We believe that the bug you reported is fixed in the latest version of goplay, 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 755...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Russell Coker russ...@coker.com.au (supplier of updated goplay package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 28 Jul 2014 16:45:05 +1000 Source: goplay Binary: goplay Architecture: source amd64 Version: 0.5-1.2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Russell Coker russ...@coker.com.au Description: goplay - games (and more) package browser using DebTags Closes: 755404 Changes: goplay (0.5-1.2) unstable; urgency=medium . * Non-maintainer upload. * Build against latest libept Closes: #755404 Checksums-Sha1: aca8d64147b7abb797f2d3670df0d4f94065bddf 1365 goplay_0.5-1.2.dsc 6504595ecc5e10d9636817aa4f988d7f232453ba 6040 goplay_0.5-1.2.debian.tar.xz df34e5356c0b22be4283b7a5bb328083457f53c5 215644 goplay_0.5-1.2_amd64.deb Checksums-Sha256: 80ad7f4e0b7ce4db7759f9dfa8f5b43f1fd21a307cd061b614ded2ec01f4120b 1365 goplay_0.5-1.2.dsc edd608ba508be47a488cb2fbbdddaf4b53efaa9e3576c5b087b5329cc037 6040 goplay_0.5-1.2.debian.tar.xz 66afdfa1aa2bd194f1a356f86324f6c38cbfd3b59feeb592dab02c84a8226668 215644 goplay_0.5-1.2_amd64.deb Files: 0c1936a91c0858125851660ccfc0d24f 215644 admin extra goplay_0.5-1.2_amd64.deb 0c50f593c15893ae99421efd2034ca90 1365 admin extra goplay_0.5-1.2.dsc 13a4339e8f09c8dc74b464fce60d04b7 6040 admin extra goplay_0.5-1.2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlPV+eEACgkQwrB5/PXHUlaEEgCfcFQ59OaM5P28f1/JOFfOVan8 uz4An3u2yz83rjksOxrzVsXcjn1UhJO7 =zPNP -END PGP SIGNATUREEnd Message---
Bug#747506: openjdk-6: cannot load libsikuli-script-java any more
Hi, Emmanuel Bourg wrote (03 Aug 2014 23:27:46 GMT) : Do you think you could attach a test case to reproduce this error please? Not sure I'll have time to extract a minimal test case any time soon. Maybe the submitter can. anonym? Do you know if it also fails with openjdk-7? It works fine with openjdk-7. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756272: glib2.0: FTBFS from svn: ERROR: gvariant - exited with status 134 (terminated by signal 6?)
fixed 756272 2.41.1-2 forwarded 756272 https://git.gnome.org/browse/glib/commit/?id=f727c820b823178285d90b3f033f7d2a4d3cdf9f tags 756272 + fixed-upstream patch pending thanks On Mon, 28 Jul 2014 at 11:33:23 +0100, Simon McVittie wrote: PASS: gvariant 28 /gvariant/error-quark # Start of serialiser tests Aborted (core dumped) ok 29 /gvariant/serialiser/maybe PASS: gvariant 29 /gvariant/serialiser/maybe ERROR: gvariant - missing test plan ERROR: gvariant - exited with status 134 (terminated by signal 6?) This appears to be the same issue Iain Lane patched in 2.41.1-2. I have committed the same upstream patch to the unstable branch. S -- 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#756273: glib2.0: FTBFS from svn: gapplication.c:564:test_quit: assertion failed: (activated)
Processing commands for cont...@bugs.debian.org: severity 756273 important Bug #756273 [src:glib2.0] glib2.0: FTBFS from svn: gapplication.c:564:test_quit: assertion failed: (activated) Severity set to 'important' from 'serious' tags 756273 + unreproducible Bug #756273 [src:glib2.0] glib2.0: FTBFS from svn: gapplication.c:564:test_quit: assertion failed: (activated) Added tag(s) unreproducible. thanks Stopping processing here. Please contact me if you need assistance. -- 756273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756273 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#756273: glib2.0: FTBFS from svn: gapplication.c:564:test_quit: assertion failed: (activated)
severity 756273 important tags 756273 + unreproducible thanks On Mon, 28 Jul 2014 at 11:39:34 +0100, Simon McVittie wrote: GLib-GIO:ERROR:/«PKGBUILDDIR»/./gio/tests/gapplication.c:564:test_quit: assertion failed: (activated) I can't reproduce this any more. Let's see what the buildds make of it. S -- 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#756272: glib2.0: FTBFS from svn: ERROR: gvariant - exited with status 134 (terminated by signal 6?)
Processing commands for cont...@bugs.debian.org: fixed 756272 2.41.1-2 Bug #756272 [src:glib2.0] glib2.0: FTBFS from svn: ERROR: gvariant - exited with status 134 (terminated by signal 6?) Marked as fixed in versions glib2.0/2.41.1-2. forwarded 756272 https://git.gnome.org/browse/glib/commit/?id=f727c820b823178285d90b3f033f7d2a4d3cdf9f Bug #756272 [src:glib2.0] glib2.0: FTBFS from svn: ERROR: gvariant - exited with status 134 (terminated by signal 6?) Set Bug forwarded-to-address to 'https://git.gnome.org/browse/glib/commit/?id=f727c820b823178285d90b3f033f7d2a4d3cdf9f'. tags 756272 + fixed-upstream patch pending Bug #756272 [src:glib2.0] glib2.0: FTBFS from svn: ERROR: gvariant - exited with status 134 (terminated by signal 6?) Added tag(s) pending, fixed-upstream, and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 756272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756272 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#755439: pcre3: DFA matching behaviour changed, breaking glib2.0 tests
Processing commands for cont...@bugs.debian.org: tags 755439 + pending Bug #755439 [libpcre3,glib2.0] pcre3: DFA matching behaviour changed, breaking glib2.0 tests Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 755439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755439 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#755439: pcre3: DFA matching behaviour changed, breaking glib2.0 tests
tags 755439 + pending thanks On Mon, 28 Jul 2014 at 11:17:54 +0100, Simon McVittie wrote: I would really appreciate opinions from GLib maintainers on which solution to the DFA-matching thing is most correct, and whether the specific patches I sent upstream are OK. I have committed these changes to the unstable branch. If you don't want me (or some other team member) to upload them, speak now. If you *do* want me (or some other team member) to upload them, please comment on the upstream GLib bug and say the changes look good to you. https://bugzilla.gnome.org/show_bug.cgi?id=733325 If I don't hear anything either way I will upload what's in svn at some point. These tests pass, but I get a failure in an unrelated test (opening another bug now). One FTBFS was fixed by an upstream patch from the 2.41 branch, I can't reproduce the other. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756997: segfaults on i386
Package: critterding
Version: 1.0-beta14-1
Severity: grave
It segfaults right away once launched. Attached backtrace.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.16-rc6-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages critterding depends on:
ii libboost-filesystem1.55.0 1.55.0+dfsg-2
ii libboost-iostreams1.55.0 1.55.0+dfsg-2
ii libboost-system1.55.0 1.55.0+dfsg-2
ii libc6 2.19-7
ii libfreetype6 2.5.2-1
ii libgcc11:4.9.1-1
ii libgl1-mesa-glx [libgl1] 10.2.4-1
ii libglu1-mesa [libglu1] 9.0.0-2
ii libgomp1 4.9.1-1
ii libice62:1.0.9-1
ii libqt4-declarative 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-network 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-opengl 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-script 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-sql 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-svg 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-xml 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-xmlpatterns 4:4.8.6+git49-gbc62005+dfsg-1
ii libqtcore4 4:4.8.6+git49-gbc62005+dfsg-1
ii libqtgui4 4:4.8.6+git49-gbc62005+dfsg-1
ii libsdl1.2debian1.2.15-10
ii libsm6 2:1.2.2-1
ii libstdc++6 4.9.1-1
ii libx11-6 2:1.6.2-2
ii libxext6 2:1.3.2-1
critterding recommends no packages.
critterding suggests no packages.
-- no debconf information
--
G..e
Reading symbols from /usr/bin/critterding...Reading symbols from
/usr/lib/debug/.build-id/e7/651942b65be0630d7703ca5900d03f3a08af34.debug...done.
done.
Starting program: /usr/bin/critterding
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need set solib-search-path or set sysroot?
[Thread debugging using libthread_db enabled]
Using host libthread_db library
/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1.
Program received signal SIGSEGV, Segmentation fault.
0x in ?? ()
#0 0x in ?? ()
No symbol table info available.
#1 0x0813973d in BeTexture::generateMipmap (this=0x8364748) at
/tmp/buildd/critterding-1.0-beta14/src/graphics/be_texture.cpp:48
No locals.
#2 0x0815bcb8 in BeTexture2DResource
(path=/usr/bin/../share/critterding/critter/textures/skin2_UV_rgb2.jpg,
this=0x8364588) at
/tmp/buildd/critterding-1.0-beta14/src/./resource/be_texture_2d_resource.h:88
image = {px = 0x844ab10, pn = {pi_ = 0x8367468}}
#3 Texturestore::load (this=0x83661b4,
filename=/usr/bin/../share/critterding/critter/textures/skin2_UV_rgb2.jpg) at
/tmp/buildd/critterding-1.0-beta14/src/utils/texturestore.cpp:12
t = {px = 0xbfffdbb8, pn = {pi_ = 0xb5ff8128 operator
delete(void*)+24}}
#4 0x0813e3fc in BeGraphicsModel::upload (this=0x83d4938, textureStore=...) at
/tmp/buildd/critterding-1.0-beta14/src/common/be_model_system.cpp:53
No locals.
#5 0x0813e6e5 in BeGraphicsModelResource (transform=..., scale=...,
graphicsModelSystem=..., graphicsSystem=...,
path=/usr/bin/../share/critterding/critter/sphere-critter.obj,
filesystem=..., this=0x83671e0) at
/tmp/buildd/critterding-1.0-beta14/src/./resource/be_graphics_model_resource.h:54
No locals.
#6 BeGraphicsModelSystem::load (this=0x83661b0,
filename=/usr/bin/../share/critterding/critter/sphere-critter.obj,
graphicsSystem=..., instance=..., scale=..., transform=...) at
/tmp/buildd/critterding-1.0-beta14/src/common/be_model_system.cpp:570
m = optimized out
#7 0x0811d5e5 in WorldB::WorldB (this=0x83cfe40, system=..., fileSystem=...,
textverbosemessage=..., lock_axis=true) at
/tmp/buildd/critterding-1.0-beta14/src/scenes/critterding/entities/worldb.cpp:405
m = optimized out
m_starttime = 1406970687
hn = jessie01, '\000' repeats 247 times
worldAabbMin = {m_floats = {-1000, -1000, -1000, 0}}
worldAabbMax = {m_floats = {1000, 1000, 1000, 0}}
ident = incomplete type
distance = 818
t = {m_basis = {m_el = {{m_floats = {1, -0, 0, 0}}, {m_floats = {0,
0.87758255, 0.47942555, 0}}, {m_floats = {-0, -0.47942555, 0.87758255, 0,
m_origin = {m_floats = {0, 0, 0, 0}}}
#8 0x080dac61 in Evolution::Evolution (this=0xbfffebf0, filesystem=...) at
/tmp/buildd/critterding-1.0-beta14/src/scenes/critterding/evolution.cpp:106
textverbosemessage = {px = 0x8390b80, pn = {pi_ = 0x83653f8}}
befileControls = {m_filename = , m_directory = , m_fullfilename =
error reading variable: Cannot access memory at address 0xf, m_content =
incomplete type}
#9 0x080d19f4 in main (argc=1, argv=0xb234) at
Processed: reopening 755404, notfixed 755404 in goplay/0.5-1.2
Processing commands for cont...@bugs.debian.org:
reopen 755404
Bug #755404 {Done: Russell Coker russ...@coker.com.au} [libept1.4.12]
libept1.4.12: /usr/lib/libept.so.1.0.5.4.12 is a dangling symlink
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions goplay/0.5-1.2.
notfixed 755404 goplay/0.5-1.2
Bug #755404 [libept1.4.12] libept1.4.12: /usr/lib/libept.so.1.0.5.4.12 is a
dangling symlink
Ignoring request to alter fixed versions of bug #755404 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
755404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755404
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: retitle 756997 to critterding: segfaults on i386
Processing commands for cont...@bugs.debian.org: retitle 756997 critterding: segfaults on i386 Bug #756997 [critterding] segfaults on i386 Changed Bug title to 'critterding: segfaults on i386' from 'segfaults on i386' thanks Stopping processing here. Please contact me if you need assistance. -- 756997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756997 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#756780: [Help] Need help for architecture specific code (Was: Bug#756780: bowtie: FTBFS almost everywhere)
Hi Ben, I recently updated the bowtie package in Debian to version 1.0.1. Unfortunately this package failed to build on most of the architectures in Debian. When discussion this issue I've got the following response which I would like to bring to your attention hereby. On Mon, Aug 04, 2014 at 04:34:17PM +0800, Paul Wise wrote: On Mon, Aug 4, 2014 at 3:48 PM, Andreas Tille wrote: third_party/cpuid.h No idea about this problem but here is what I could figure out based on the filename and the errors, using packages.d.o, codesearch.d.n and a quick look at wikipedia. third_party/cpuid.h looks like an outdated copy of the cpuid.h header from gcc, please ask upstream to remove it and just use the normal one. Do you have any specific reason to use this outdated copy of cpuid.h? The cpuid.h header seems to be only/mainly on x86 based platforms: https://packages.debian.org/search?arch=anysearchon=contentskeywords=cpuid.h If upstream was using autotools, they could detect if the header is present and only then enable the cpuid stuff. It might make sense to use autotools to create the makefile and by doing so simplify porting to different architectures. Do you intend to do something like this or would you appreciate help / patches to migrate to autotools? The bowtie2 package appears to only be available on *-amd64 (same issue I guess, some code seems similar): https://buildd.debian.org/status/package.php?p=bowtie2suite=unstable Looking at some valgrind code (thanks to codesearch) it seems you have to use popcntq on amd64 and popcnt on non-amd64 platforms. http://sources.debian.net/src/valgrind/latest/none/tests/amd64/sse4-64.c#L2039 This remark boils down to the question whether it might be possible to support bowtie2 also on other architectures. BTW, what is the difference between bowtie and bowtie2? Do we need both in the archive? This question was asked by a non-biologist and I personally do also not have any background in biology. I guess that bowtie2 is not fully replacing bowtie version 1 but it might be good to know your long term plans for both versions. Kind regards and thanks for providing bowtie as free software Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747506: libsikuli-script-java
Control: reassign -1 src:openjdk-6 On Sun, 03 Aug 2014 15:30:28 +0200 Matthias Klose d...@ubuntu.com wrote: seeing #752738, this might be an issue with an incomplete java library path in sikuli. Nope. This is #517338. Running sikuli with LD_LIBRARY_PATH=/usr/lib/multiarch/jni works fine. Thanks, _g. signature.asc Description: OpenPGP digital signature
Processed: Re: libsikuli-script-java
Processing control commands: reassign -1 src:openjdk-6 Bug #747506 [libsikuli-script-java] openjdk-6: cannot load libsikuli-script-java any more Bug reassigned from package 'libsikuli-script-java' to 'src:openjdk-6'. Ignoring request to alter found versions of bug #747506 to the same values previously set Ignoring request to alter fixed versions of bug #747506 to the same values previously set -- 747506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747506 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#756485: [Pkg-acpi-devel] Bug#756485: acpid: Unable to upgrade/downgrade
Upgrade to this version resulted in the inability to stop package Please, pretty please, give us at least some output to see what may be happening on your system. My cystal ball is currently not working. :) 1. AFter first upgrade (previous version to this one) moved /etc/sysctl.d directory, so upgrade would continue. From this version to next (or previous) failes completely as acpid won't stop. (or at least stop script exits with error) I have no idea what /etc/sysctl.d has to do with acpid, sorry. Please run stop script with set -x and send the output. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747506: libsikuli-script-java
Hi, Gilles Filippini wrote (04 Aug 2014 10:49:32 GMT) : Nope. This is #517338. Running sikuli with LD_LIBRARY_PATH=/usr/lib/multiarch/jni works fine. Do you mean the library path was changed between 6b27-1.12.6-1~deb7u1 and 6b31-1.13.3-1~deb7u1, as part of a security update in stable? Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: pdl: diff for NMU version 1:2.007-2.1
Processing commands for cont...@bugs.debian.org: tags 752351 + pending Bug #752351 [src:pdl] pdl: hardcodes /usr/lib/perl5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 752351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752351 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: your mail
Processing commands for cont...@bugs.debian.org: tags 753759 +pending Bug #753759 [lcms] Non free icc profile Added tag(s) pending. tags 742749 +pending Bug #742749 [lcms] lcms: Adding a watchfile Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 742749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742749 753759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753759 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#752351: pdl: diff for NMU version 1:2.007-2.1
tags 752351 + pending
thanks
Dear maintainer,
I've prepared an NMU for pdl (versioned as 1:2.007-2.1) using gregor's
patch and uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
dam
diff -Nru pdl-2.007/debian/changelog pdl-2.007/debian/changelog
--- pdl-2.007/debian/changelog 2013-11-12 15:43:07.0 +0200
+++ pdl-2.007/debian/changelog 2014-08-04 10:54:29.0 +0300
@@ -1,3 +1,16 @@
+pdl (1:2.007-2.1) unstable; urgency=medium
+
+ [ gregor herrmann ]
+ * Non-maintainer upload.
+ * Fix hardcodes /usr/lib/perl5:
+- rename files in debian/ which contain /usr/lib/perl5 to .in, replace
+ /usr/lib/perl5 with a variable
+- create original files from debian/rules, replacing the variable with
+ the current value of $Config{vendorarch}
+(Closes: #752351)
+
+ -- Damyan Ivanov d...@debian.org Mon, 04 Aug 2014 07:54:19 +
+
pdl (1:2.007-2) unstable; urgency=low
* successfully built with gcc 4.8 (closes: #701335, #713346)
diff -Nru pdl-2.007/debian/pdl.install pdl-2.007/debian/pdl.install
--- pdl-2.007/debian/pdl.install 2012-05-25 18:18:47.0 +0300
+++ pdl-2.007/debian/pdl.install 1970-01-01 02:00:00.0 +0200
@@ -1,3 +0,0 @@
-Doc/scantree.pl usr/lib/perl5/PDL/Doc/
-Doc/mkhtmldoc.pl usr/lib/perl5/PDL/Doc/
-debian/dh_pdl usr/bin
diff -Nru pdl-2.007/debian/pdl.install.in pdl-2.007/debian/pdl.install.in
--- pdl-2.007/debian/pdl.install.in 1970-01-01 02:00:00.0 +0200
+++ pdl-2.007/debian/pdl.install.in 2014-08-04 10:53:15.0 +0300
@@ -0,0 +1,3 @@
+Doc/scantree.pl @vendorarch@/PDL/Doc/
+Doc/mkhtmldoc.pl @vendorarch@/PDL/Doc/
+debian/dh_pdl usr/bin
diff -Nru pdl-2.007/debian/pdl.links pdl-2.007/debian/pdl.links
--- pdl-2.007/debian/pdl.links 2012-02-19 11:23:33.0 +0200
+++ pdl-2.007/debian/pdl.links 1970-01-01 02:00:00.0 +0200
@@ -1,4 +0,0 @@
-/var/lib/pdl/Index.pod /usr/lib/perl5/PDL/Index.pod
-/var/lib/pdl/pdldoc.db /usr/lib/perl5/PDL/pdldoc.db
-/var/lib/pdl/html /usr/share/doc/pdl/html
-/usr/share/man/man3/PDL.3pm.gz /usr/share/man/man1/pdl.1.gz
diff -Nru pdl-2.007/debian/pdl.links.in pdl-2.007/debian/pdl.links.in
--- pdl-2.007/debian/pdl.links.in 1970-01-01 02:00:00.0 +0200
+++ pdl-2.007/debian/pdl.links.in 2014-08-04 10:53:15.0 +0300
@@ -0,0 +1,4 @@
+/var/lib/pdl/Index.pod /@vendorarch@/PDL/Index.pod
+/var/lib/pdl/pdldoc.db /@vendorarch@/PDL/pdldoc.db
+/var/lib/pdl/html /usr/share/doc/pdl/html
+/usr/share/man/man3/PDL.3pm.gz /usr/share/man/man1/pdl.1.gz
diff -Nru pdl-2.007/debian/pdl.lintian-overrides pdl-2.007/debian/pdl.lintian-overrides
--- pdl-2.007/debian/pdl.lintian-overrides 2013-11-07 17:00:20.0 +0200
+++ pdl-2.007/debian/pdl.lintian-overrides 1970-01-01 02:00:00.0 +0200
@@ -1,9 +0,0 @@
-# HG: the html doc is generated in the postinst maintainer script, so lintian
-# just does not see it
-pdl: doc-base-file-references-missing-file pdl:12 /var/lib/pdl/html/Index.html
-pdl: doc-base-file-references-missing-file pdl:13 /var/lib/pdl/html/*.html
-# there is one long code line in the manpage, which cannot be broken
-pdl: manpage-has-errors-from-man usr/share/man/man3/PDL::FFT.3pm.gz 232: warning [p 2, 3.3i]: can't break line
-# these two images neeed to be in usr/lib
-pdl: image-file-in-usr-lib usr/lib/perl5/PDL/Transform/Cartography/earth_day.jpg
-pdl: image-file-in-usr-lib usr/lib/perl5/PDL/Transform/Cartography/earth_night.jpg
diff -Nru pdl-2.007/debian/pdl.lintian-overrides.in pdl-2.007/debian/pdl.lintian-overrides.in
--- pdl-2.007/debian/pdl.lintian-overrides.in 1970-01-01 02:00:00.0 +0200
+++ pdl-2.007/debian/pdl.lintian-overrides.in 2014-08-04 10:53:15.0 +0300
@@ -0,0 +1,9 @@
+# HG: the html doc is generated in the postinst maintainer script, so lintian
+# just does not see it
+pdl: doc-base-file-references-missing-file pdl:12 /var/lib/pdl/html/Index.html
+pdl: doc-base-file-references-missing-file pdl:13 /var/lib/pdl/html/*.html
+# there is one long code line in the manpage, which cannot be broken
+pdl: manpage-has-errors-from-man usr/share/man/man3/PDL::FFT.3pm.gz 232: warning [p 2, 3.3i]: can't break line
+# these two images neeed to be in usr/lib
+pdl: image-file-in-usr-lib @vendorarch@/PDL/Transform/Cartography/earth_day.jpg
+pdl: image-file-in-usr-lib @vendorarch@/PDL/Transform/Cartography/earth_night.jpg
diff -Nru pdl-2.007/debian/pdl.postinst pdl-2.007/debian/pdl.postinst
--- pdl-2.007/debian/pdl.postinst 2013-11-08 10:17:49.0 +0200
+++ pdl-2.007/debian/pdl.postinst 1970-01-01 02:00:00.0 +0200
@@ -1,44 +0,0 @@
-#! /bin/sh
-# postinst script for pdl
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#* postinst `configure' most-recently-configured-version
-#* old-postinst `abort-upgrade' new version
-#* conflictor's-postinst `abort-remove' `in-favour' package
-# new-version
-#* deconfigured's-postinst `abort-deconfigure'
Processed: rrdtool: diff for NMU version 1.4.8-1.1
Processing commands for cont...@bugs.debian.org: tags 752813 + pending Bug #752813 [src:rrdtool] rrdtool: hardcodes /usr/lib/perl5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 752813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752813 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#747506: libsikuli-script-java
intrigeri a écrit , Le 04/08/2014 13:00: Hi, Gilles Filippini wrote (04 Aug 2014 10:49:32 GMT) : Nope. This is #517338. Running sikuli with LD_LIBRARY_PATH=/usr/lib/multiarch/jni works fine. Do you mean the library path was changed between 6b27-1.12.6-1~deb7u1 and 6b31-1.13.3-1~deb7u1, as part of a security update in stable? It seems that after this update openjdk-6 doesn't search for JNI libs into the multiarch path anymore. See this excerpt from the strace log: $ grep libVisionProxy strace.log [pid 5326] stat64(/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386/libVisionProxy.so, 0xb6ac4760) = -1 ENOENT (No such file or directory) [pid 5326] stat64(/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386/client/libVisionProxy.so, 0xb6ac4760) = -1 ENOENT (No such file or directory) [pid 5326] stat64(/usr/lib/jvm/java-6-openjdk-i386/jre/lib/i386/libVisionProxy.so, 0xb6ac4760) = -1 ENOENT (No such file or directory) [pid 5326] stat64(/usr/lib/jvm/java-6-openjdk-i386/jre/../lib/i386/libVisionProxy.so, 0xb6ac4760) = -1 ENOENT (No such file or directory) [pid 5326] stat64(/usr/java/packages/lib/i386/libVisionProxy.so, 0xb6ac4760) = -1 ENOENT (No such file or directory) [pid 5326] stat64(/usr/lib/jni/libVisionProxy.so, 0xb6ac4760) = -1 ENOENT (No such file or directory) [pid 5326] stat64(/lib/libVisionProxy.so, 0xb6ac4760) = -1 ENOENT (No such file or directory) [pid 5326] stat64(/usr/lib/libVisionProxy.so, 0xb6ac4760) = -1 ENOENT (No such file or directory) Thanks, _g. signature.asc Description: OpenPGP digital signature
Bug#752813: rrdtool: diff for NMU version 1.4.8-1.1
tags 752813 + pending
thanks
Dear maintainer,
I've prepared an NMU for rrdtool (versioned as 1.4.8-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
dam
diff -u rrdtool-1.4.8/debian/changelog rrdtool-1.4.8/debian/changelog
--- rrdtool-1.4.8/debian/changelog
+++ rrdtool-1.4.8/debian/changelog
@@ -1,3 +1,15 @@
+rrdtool (1.4.8-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix failure to build with perl 5.20 from experimental
+Closes: #752813
++ convert librrds-perl.install to executable script using
+ $Config{vendorarch} instead of hardcoding /usr/lib/perl5
++ bump debhelper build-dependency and compat level to 9, needed for having
+ an executable .install
+
+ -- Damyan Ivanov d...@debian.org Mon, 04 Aug 2014 11:16:56 +
+
rrdtool (1.4.8-1) unstable; urgency=medium
[ Sebastian Harl ]
diff -u rrdtool-1.4.8/debian/compat rrdtool-1.4.8/debian/compat
--- rrdtool-1.4.8/debian/compat
+++ rrdtool-1.4.8/debian/compat
@@ -1 +1 @@
-5
+9
diff -u rrdtool-1.4.8/debian/control rrdtool-1.4.8/debian/control
--- rrdtool-1.4.8/debian/control
+++ rrdtool-1.4.8/debian/control
@@ -4,7 +4,7 @@
Maintainer: Debian RRDtool Team rrdt...@ml.snow-crash.org
Uploaders: Sebastian Harl tok...@debian.org, Alexander Wirt formo...@debian.org, Bernd Zeimetz b...@debian.org
Standards-Version: 3.9.5
-Build-Depends: debhelper (= 5.0.38), groff, autotools-dev, dh-autoreconf, gettext, quilt,
+Build-Depends: debhelper (= 9), groff, autotools-dev, dh-autoreconf, gettext, quilt,
zlib1g-dev, libpng12-dev, libcairo2-dev, libpango1.0-dev, libfreetype6-dev,
libdbi0-dev,
libxml2-dev,
diff -u rrdtool-1.4.8/debian/librrds-perl.install rrdtool-1.4.8/debian/librrds-perl.install
--- rrdtool-1.4.8/debian/librrds-perl.install
+++ rrdtool-1.4.8/debian/librrds-perl.install
@@ -1,3 +1,8 @@
-usr/lib/perl5/auto/RRDs
-usr/lib/perl5/RRDs.pm
-usr/share/man/man3/RRDs.3pm
+#!/usr/bin/perl
+use Config;
+# omit the leading '/'
+my $vendorarch = substr( $Config{vendorarch}, 1 );
+
+print $vendorarch/auto/RRDs\n;
+print $vendorarch/RRDs.pm\n;
+print usr/share/man/man3/RRDs.3pm\n;
diff -u rrdtool-1.4.8/debian/rules rrdtool-1.4.8/debian/rules
--- rrdtool-1.4.8/debian/rules
+++ rrdtool-1.4.8/debian/rules
@@ -154,6 +154,7 @@
make install DESTDIR=$(CURDIR)/debian/tmp
# we don't want .txt and .pod documentation in the package
rm -rf debian/tmp/usr/share/doc/rrdtool/txt
+ chmod a+x debian/librrds-perl.install
dh_install --sourcedir=$(CURDIR)/debian/tmp -X.la --fail-missing
# remove duplicates
rm debian/rrdtool/usr/bin/rrdcached
Bug#757006: rrdtool: maintainer address bounces
Source: rrdtool Severity: serious Tags: sid X-Debbugs-Cc: tok...@debian.org, formo...@debian.org, b...@debian.org The maintainer address for rrdtool bounces, see below. Ansgar On 08/04/2014 13:30, Mail Delivery System wrote: This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: rrdt...@ml.snow-crash.org SMTP error from remote mail server after RCPT TO:rrdt...@ml.snow-crash.org: host apu.snow-crash.org [2a01:4f8:130:53c9::2]: 550 5.1.1 rrdt...@ml.snow-crash.org: Recipient address rejected: User unknown in local recipient table -- This is a copy of the message, including all the headers. -- Return-path: dak-unp...@franck.debian.org Received: from franck.debian.org ([138.16.160.12]) from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP CA,CN=franck.debian.org,EMAIL=hostmas...@franck.debian.org (verified) by mailly.debian.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from dak-unp...@franck.debian.org) id 1XEGTf-0006iw-4b for rrdt...@ml.snow-crash.org; Mon, 04 Aug 2014 11:30:55 + Received: from dak-unpriv by franck.debian.org with local (Exim 4.80) (envelope-from dak-unp...@franck.debian.org) id 1XEGTd-0007uk-Mu for rrdt...@ml.snow-crash.org; Mon, 04 Aug 2014 11:30:53 + To: rrdt...@ml.snow-crash.org From: Debian FTP Masters ftpmas...@ftp-master.debian.org Subject: Processing of rrdtool_1.4.8-1.1_amd64.changes Date: Mon, 04 Aug 2014 11:30:53 + X-Debian: DAK X-DAK: DAK Precedence: bulk Auto-Submitted: auto-generated X-Debian-Package: rrdtool Message-Id: e1xegtd-0007uk...@franck.debian.org Sender: unprivileged ftp-master role account dak-unp...@franck.debian.org rrdtool_1.4.8-1.1_amd64.changes uploaded successfully to localhost along with the files: rrdtool_1.4.8-1.1_amd64.deb rrdcached_1.4.8-1.1_amd64.deb rrdtool-dbg_1.4.8-1.1_amd64.deb librrd4_1.4.8-1.1_amd64.deb librrd-dev_1.4.8-1.1_amd64.deb librrds-perl_1.4.8-1.1_amd64.deb rrdtool-tcl_1.4.8-1.1_amd64.deb python-rrdtool_1.4.8-1.1_amd64.deb ruby-rrd_1.4.8-1.1_amd64.deb liblua5.1-rrd0_1.4.8-1.1_amd64.deb liblua5.1-rrd-dev_1.4.8-1.1_amd64.deb librrdp-perl_1.4.8-1.1_all.deb librrd-ruby_1.4.8-1.1_all.deb librrd-ruby1.8_1.4.8-1.1_all.deb librrd-ruby1.9.1_1.4.8-1.1_all.deb rrdtool_1.4.8-1.1.dsc rrdtool_1.4.8-1.1.diff.gz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756997: critterding: segfaults on i386
On Mon, Aug 04, 2014 at 12:03:47PM +0200, Gabriele Giacone wrote: It segfaults right away once launched. Attached backtrace. Attaching lshw and glxinfo outputs. *-display description: VGA compatible controller product: G72M [Quadro NVS 110M/GeForce Go 7300] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:46 memory:ed00-edff memory:d000-dfff memory:ee00-eeff memory:ef00-ef01 name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: nouveau OpenGL renderer string: Gallium 0.4 on NV46 OpenGL version string: 2.1 Mesa 10.2.4 OpenGL shading language version string: 1.20 OpenGL extensions: GL_AMD_shader_trinary_minmax, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_elements_base_vertex, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_separate_shader_objects, GL_ARB_shader_objects, GL_ARB_shading_language_100, GL_ARB_shadow, GL_ARB_sync, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_mirror_clamp_to_edge, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, GL_ARB_texture_storage, GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_transpose_matrix, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_attrib_binding, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_window_pos, GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, GL_ATI_separate_stencil, GL_ATI_texture_env_combine3,
Bug#757008: critterding: segfaults on amd64, NV98
Package: critterding
Version: 1.0-beta14+dfsg-1
Severity: grave
It segfaults right away. Attaching backtrace, glxinfo and lshw outputs.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-3-amd64 (SMP w/3 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages critterding depends on:
ii critterding-common 1.0-beta14+dfsg-1
ii libboost-filesystem1.55.0 1.55.0+dfsg-2
ii libboost-iostreams1.55.0 1.55.0+dfsg-2
ii libboost-system1.55.0 1.55.0+dfsg-2
ii libbulletcollision2.82 2.82-r2704+dfsg-2
ii libbulletdynamics2.82 2.82-r2704+dfsg-2
ii libbulletsoftbody2.82 2.82-r2704+dfsg-2
ii libc6 2.19-7
ii libfreetype6 2.5.2-1
ii libftgl2 2.1.3~rc5-4+nmu1
ii libgcc11:4.9.1-1
ii libgl1-mesa-glx [libgl1] 10.2.4-1
ii libglew1.101.10.0-3
ii libglu1-mesa [libglu1] 9.0.0-2
ii libgomp1 4.9.1-1
ii liblinearmath2.82 2.82-r2704+dfsg-2
ii libqt4-declarative 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-network 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-opengl 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-script 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-sql 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-svg 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-xml 4:4.8.6+git49-gbc62005+dfsg-1
ii libqt4-xmlpatterns 4:4.8.6+git49-gbc62005+dfsg-1
ii libqtcore4 4:4.8.6+git49-gbc62005+dfsg-1
ii libqtgui4 4:4.8.6+git49-gbc62005+dfsg-1
ii libsdl1.2debian1.2.15-10
ii libstdc++6 4.9.1-1
ii libtinyxml2.6.22.6.2-2
ii libx11-6 2:1.6.2-2
ii libxext6 2:1.3.2-1
critterding recommends no packages.
critterding suggests no packages.
-- no debconf information
Reading symbols from /usr/bin/critterding...Reading symbols from
/usr/lib/debug/.build-id/70/0e45715b4e77945d9d6a2b63d7b2d54ec64953.debug...done.
done.
Starting program: /usr/bin/critterding
warning: no loadable sections found in added symbol-file system-supplied DSO at
0x77ffa000
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need set solib-search-path or set sysroot?
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Program received signal SIGSEGV, Segmentation fault.
0x in ?? ()
Quit
Thread 1 (Thread 0x77f96980 (LWP 12542)):
#0 0x in ?? ()
No symbol table info available.
#1 0x004ce7d9 in uniform (this=optimized out, value=0,
location=optimized out) at
/tmp/buildd/critterding-1.0-beta14+dfsg/src/graphics/be_shader.h:66
No locals.
#2 uniformint (value=0, name=0x52ef87 Tex0, this=0x13815f0) at
/tmp/buildd/critterding-1.0-beta14+dfsg/src/graphics/be_shader.h:55
No locals.
#3 ScGraphics::ScGraphics (this=0xf18550, graphicsSystem=..., filesystem=...)
at /tmp/buildd/critterding-1.0-beta14+dfsg/src/graphics/sc_graphics.cpp:102
No locals.
#4 0x004649d7 in Evolution::initGLSL (this=0xd,
this@entry=0x7fffd950) at
/tmp/buildd/critterding-1.0-beta14+dfsg/src/scenes/critterding/evolution.cpp:269
No locals.
#5 0x0045d2d0 in Evolution::Evolution (this=0x7fffd950,
filesystem=...) at
/tmp/buildd/critterding-1.0-beta14+dfsg/src/scenes/critterding/evolution.cpp:248
textverbosemessage = {px = 0x873180, pn = {pi_ = 0x8cb2f0}}
befileControls = {m_filename = settings.xml, m_directory =
/usr/bin/../share/critterding/, m_fullfilename =
/usr/bin/../share/critterding/settings.xml, m_content = incomplete type}
#6 0x0044bdc1 in main (argc=1, argv=0x7fffe0b8) at
/tmp/buildd/critterding-1.0-beta14+dfsg/src/scenes/critterding/critterding.cpp:253
buf3 =
/usr/bin/critterding\000\000\000\000\360\333\377\377\377\177\000\000(}\203\361\377\177\000\000@??\361\377\177\000\000\000\000\000\000\000\000\000\000`\330\373\367\377\177\000\000\020\334\377\377\377\177\000\000\000\334\377\377\377\177\000\000\314?\f\257\000\000\000\000\203\202\374\363\377\177\000\000\377\377\377\377\000\000\000\000\320|\374\363\377\177\000\000\250\215\203\361\377\177\000\000??\373\367\377\177\000\000\000\000\000\000\001\000\000\000\001\003\000\000\001\000\000\000xO\367\355\377\177\000\000\060\331\371\367\377\177\000\000\220\335\377\377\377\177\000\000`\330\373\367\377\177\000\000\004\000\000\000\377\177\000\000`\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\061\000\000\000\000\000\000\000...
evolution = {BeScene = {_vptr.BeScene = 0x526e90 vtable for
Evolution+16, m_exitscene = false}, world = 0x8c78e0, settings = 0x75d580
Settings::Instance()::t,
Processed: openbabel: diff for NMU version 2.3.2+dfsg-1.2
Processing commands for cont...@bugs.debian.org: tags 752800 + pending Bug #752800 [openbabel] openbabel: hardcodes /usr/lib/perl5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 752800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752800 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#757008: critterding: segfaults on amd64, NV98
forcemerge 757008 756997 retitle 756997 Segfaults on start thanks On 04/08/2014 14:07, Gabriele Giacone wrote: Package: critterding Version: 1.0-beta14+dfsg-1 Severity: grave It segfaults right away. Attaching backtrace, glxinfo and lshw outputs. One bug is enough. No need to report a bug per arch. Sylvestre -- 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#757008: critterding: segfaults on amd64, NV98
Processing commands for cont...@bugs.debian.org: forcemerge 757008 756997 Bug #757008 [critterding] critterding: segfaults on amd64, NV98 Bug #756997 [critterding] critterding: segfaults on i386 There is no source info for the package 'critterding' at version '1.0-beta14+dfsg-1' with architecture '' Unable to make a source version for version '1.0-beta14+dfsg-1' There is no source info for the package 'critterding' at version '1.0-beta14-1' with architecture '' Unable to make a source version for version '1.0-beta14-1' Marked as found in versions 1.0-beta14+dfsg-1. Bug #757008 [critterding] critterding: segfaults on amd64, NV98 There is no source info for the package 'critterding' at version '1.0-beta14+dfsg-1' with architecture '' Unable to make a source version for version '1.0-beta14+dfsg-1' There is no source info for the package 'critterding' at version '1.0-beta14-1' with architecture '' Unable to make a source version for version '1.0-beta14-1' Marked as found in versions 1.0-beta14-1. Merged 756997 757008 retitle 756997 Segfaults on start Bug #756997 [critterding] critterding: segfaults on i386 Bug #757008 [critterding] critterding: segfaults on amd64, NV98 Changed Bug title to 'Segfaults on start' from 'critterding: segfaults on i386' Changed Bug title to 'Segfaults on start' from 'critterding: segfaults on amd64, NV98' thanks Stopping processing here. Please contact me if you need assistance. -- 756997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756997 757008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757008 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: your mail
Processing commands for cont...@bugs.debian.org: found 747506 1.0~x~rc3.tesseract3-dfsg1-5 Bug #747506 [src:openjdk-6] openjdk-6: cannot load libsikuli-script-java any more The source 'openjdk-6' and version '1.0~x~rc3.tesseract3-dfsg1-5' do not appear to match any binary packages Marked as found in versions openjdk-6/1.0~x~rc3.tesseract3-dfsg1-5. severity 747506 normal Bug #747506 [src:openjdk-6] openjdk-6: cannot load libsikuli-script-java any more Severity set to 'normal' from 'critical' tags 747506 moreinfo Bug #747506 [src:openjdk-6] openjdk-6: cannot load libsikuli-script-java any more Added tag(s) moreinfo. End of message, stopping processing here. Please contact me if you need assistance. -- 747506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747506 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#752800: openbabel: diff for NMU version 2.3.2+dfsg-1.2
tags 752800 + pending
thanks
Dear maintainer,
I've uploaded the NMU for openbabel prepared by gregor (versioned as
2.3.2+dfsg-1.2) to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
dam
diff -Nru openbabel-2.3.2+dfsg/debian/changelog openbabel-2.3.2+dfsg/debian/changelog
--- openbabel-2.3.2+dfsg/debian/changelog 2014-01-16 20:06:35.0 +0200
+++ openbabel-2.3.2+dfsg/debian/changelog 2014-08-04 14:31:08.0 +0300
@@ -1,3 +1,15 @@
+openbabel (2.3.2+dfsg-1.2) unstable; urgency=medium
+
+ [ gregor herrmann ]
+ * Non-maintainer upload.
+ * Fix hardcodes /usr/lib/perl5:
+- remove debian/libchemistry-openbabel-perl.install
+- pass perl directory to dh_install in debian/rules,
+ expanded from $Config{vendorarch}
+(Closes: #752800)
+
+ -- Damyan Ivanov d...@debian.org Mon, 04 Aug 2014 11:31:02 +
+
openbabel (2.3.2+dfsg-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru openbabel-2.3.2+dfsg/debian/rules openbabel-2.3.2+dfsg/debian/rules
--- openbabel-2.3.2+dfsg/debian/rules 2013-05-22 20:06:32.0 +0300
+++ openbabel-2.3.2+dfsg/debian/rules 2014-08-04 14:30:37.0 +0300
@@ -5,6 +5,7 @@
-include /usr/share/python/python.mk
PYVERS=$(shell pyversions -vs)
+PERL_ARCHLIB := $(shell perl -MConfig -e 'print $$Config{vendorarch}')
export CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS)
export CFLAGS := $(shell dpkg-buildflags --get CFLAGS) $(CPPFLAGS)
@@ -43,7 +44,8 @@
done
override_dh_install:
- dh_install -Xperllocal.pod --list-missing
+ dh_install --list-missing -Nlibchemistry-openbabel-perl
+ dh_install --list-missing -plibchemistry-openbabel-perl -Xperllocal.pod --autodest $(PERL_ARCHLIB)
override_dh_installdocs:
dh_installdocs -Xjquery.js
Processed: qpid-cpp: diff for NMU version 0.16-7.2
Processing commands for cont...@bugs.debian.org: tags 752808 + pending Bug #752808 [src:qpid-cpp] qpid-cpp: hardcodes /usr/lib/perl5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 752808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752808 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: qt4-perl: diff for NMU version 4.8.4-1.1
Processing commands for cont...@bugs.debian.org: tags 752809 + pending Bug #752809 [src:qt4-perl] qt4-perl: hardcodes /usr/lib/perl5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 752809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752809 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#752809: qt4-perl: diff for NMU version 4.8.4-1.1
tags 752809 + pending thanks Dear maintainer, I've uploaded an NMU by gregor for qt4-perl (versioned as 4.8.4-1.1) to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, dam diff -Nru qt4-perl-4.8.4/debian/changelog qt4-perl-4.8.4/debian/changelog --- qt4-perl-4.8.4/debian/changelog 2012-06-21 00:52:20.0 +0300 +++ qt4-perl-4.8.4/debian/changelog 2014-08-04 15:20:09.0 +0300 @@ -1,3 +1,14 @@ +qt4-perl (4.8.4-1.1) unstable; urgency=medium + + [ gregor herrmann ] + * Non-maintainer upload. + * Fix hardcodes /usr/lib/perl5: +dynamically create debian/*.install files with the correct path from +debian/rules during build +(Closes: #752809) + + -- Damyan Ivanov d...@debian.org Mon, 04 Aug 2014 12:20:06 + + qt4-perl (4.8.4-1) unstable; urgency=low * New upstream release diff -Nru qt4-perl-4.8.4/debian/libqtcore4-perl.install qt4-perl-4.8.4/debian/libqtcore4-perl.install --- qt4-perl-4.8.4/debian/libqtcore4-perl.install 2010-07-07 16:46:05.0 +0300 +++ qt4-perl-4.8.4/debian/libqtcore4-perl.install 1970-01-01 02:00:00.0 +0200 @@ -1,7 +0,0 @@ -usr/lib/perl5/auto/QtCore4/QtCore4.so -usr/lib/perl5/QtCore4/classinfo.pm -usr/lib/perl5/QtCore4/isa.pm -usr/lib/perl5/QtCore4/signals.pm -usr/lib/perl5/QtCore4/debug.pm -usr/lib/perl5/QtCore4/slots.pm -usr/lib/perl5/QtCore4.pm diff -Nru qt4-perl-4.8.4/debian/libqtcore4-perl.install.in qt4-perl-4.8.4/debian/libqtcore4-perl.install.in --- qt4-perl-4.8.4/debian/libqtcore4-perl.install.in 1970-01-01 02:00:00.0 +0200 +++ qt4-perl-4.8.4/debian/libqtcore4-perl.install.in 2014-08-04 15:14:17.0 +0300 @@ -0,0 +1,7 @@ +@ARCHLIB@/auto/QtCore4/QtCore4.so +@ARCHLIB@/QtCore4/classinfo.pm +@ARCHLIB@/QtCore4/isa.pm +@ARCHLIB@/QtCore4/signals.pm +@ARCHLIB@/QtCore4/debug.pm +@ARCHLIB@/QtCore4/slots.pm +@ARCHLIB@/QtCore4.pm diff -Nru qt4-perl-4.8.4/debian/libqtgui4-perl.install qt4-perl-4.8.4/debian/libqtgui4-perl.install --- qt4-perl-4.8.4/debian/libqtgui4-perl.install 2010-07-13 11:56:06.0 +0300 +++ qt4-perl-4.8.4/debian/libqtgui4-perl.install 1970-01-01 02:00:00.0 +0200 @@ -1,3 +0,0 @@ -usr/lib/perl5/QtGui4.pm -usr/lib/perl5/auto/QtGui4/QtGui4.so -usr/bin/puic4 diff -Nru qt4-perl-4.8.4/debian/libqtgui4-perl.install.in qt4-perl-4.8.4/debian/libqtgui4-perl.install.in --- qt4-perl-4.8.4/debian/libqtgui4-perl.install.in 1970-01-01 02:00:00.0 +0200 +++ qt4-perl-4.8.4/debian/libqtgui4-perl.install.in 2014-08-04 15:16:45.0 +0300 @@ -0,0 +1,3 @@ +@ARCHLIB@/QtGui4.pm +@ARCHLIB@/auto/QtGui4/QtGui4.so +usr/bin/puic4 diff -Nru qt4-perl-4.8.4/debian/libqtnetwork4-perl.install qt4-perl-4.8.4/debian/libqtnetwork4-perl.install --- qt4-perl-4.8.4/debian/libqtnetwork4-perl.install 2010-07-13 11:56:10.0 +0300 +++ qt4-perl-4.8.4/debian/libqtnetwork4-perl.install 1970-01-01 02:00:00.0 +0200 @@ -1,2 +0,0 @@ -usr/lib/perl5/QtNetwork4.pm -usr/lib/perl5/auto/QtNetwork4/QtNetwork4.so diff -Nru qt4-perl-4.8.4/debian/libqtnetwork4-perl.install.in qt4-perl-4.8.4/debian/libqtnetwork4-perl.install.in --- qt4-perl-4.8.4/debian/libqtnetwork4-perl.install.in 1970-01-01 02:00:00.0 +0200 +++ qt4-perl-4.8.4/debian/libqtnetwork4-perl.install.in 2014-08-04 15:14:28.0 +0300 @@ -0,0 +1,2 @@ +@ARCHLIB@/QtNetwork4.pm +@ARCHLIB@/auto/QtNetwork4/QtNetwork4.so diff -Nru qt4-perl-4.8.4/debian/libqttest4-perl.install qt4-perl-4.8.4/debian/libqttest4-perl.install --- qt4-perl-4.8.4/debian/libqttest4-perl.install 2010-07-13 11:56:14.0 +0300 +++ qt4-perl-4.8.4/debian/libqttest4-perl.install 1970-01-01 02:00:00.0 +0200 @@ -1,2 +0,0 @@ -usr/lib/perl5/QtTest4.pm -usr/lib/perl5/auto/QtTest4/QtTest4.so diff -Nru qt4-perl-4.8.4/debian/libqttest4-perl.install.in qt4-perl-4.8.4/debian/libqttest4-perl.install.in --- qt4-perl-4.8.4/debian/libqttest4-perl.install.in 1970-01-01 02:00:00.0 +0200 +++ qt4-perl-4.8.4/debian/libqttest4-perl.install.in 2014-08-04 15:14:28.0 +0300 @@ -0,0 +1,2 @@ +@ARCHLIB@/QtTest4.pm +@ARCHLIB@/auto/QtTest4/QtTest4.so diff -Nru qt4-perl-4.8.4/debian/libqtxml4-perl.install qt4-perl-4.8.4/debian/libqtxml4-perl.install --- qt4-perl-4.8.4/debian/libqtxml4-perl.install 2010-07-13 11:56:17.0 +0300 +++ qt4-perl-4.8.4/debian/libqtxml4-perl.install 1970-01-01 02:00:00.0 +0200 @@ -1,2 +0,0 @@ -usr/lib/perl5/QtXml4.pm -usr/lib/perl5/auto/QtXml4/QtXml4.so diff -Nru qt4-perl-4.8.4/debian/libqtxml4-perl.install.in qt4-perl-4.8.4/debian/libqtxml4-perl.install.in --- qt4-perl-4.8.4/debian/libqtxml4-perl.install.in 1970-01-01 02:00:00.0 +0200 +++ qt4-perl-4.8.4/debian/libqtxml4-perl.install.in 2014-08-04 15:14:28.0 +0300 @@ -0,0 +1,2 @@ +@ARCHLIB@/QtXml4.pm +@ARCHLIB@/auto/QtXml4/QtXml4.so diff -Nru qt4-perl-4.8.4/debian/rules qt4-perl-4.8.4/debian/rules --- qt4-perl-4.8.4/debian/rules 2010-07-07 17:21:36.0 +0300 +++ qt4-perl-4.8.4/debian/rules 2014-08-04 15:19:09.0 +0300 @@ -3,3 +3,13 @@ include
Bug#757008: critterding: segfaults on amd64, NV98
On Mon, Aug 4, 2014 at 2:15 PM, Sylvestre Ledru sylves...@debian.org wrote: forcemerge 757008 756997 retitle 756997 Segfaults on start thanks On 04/08/2014 14:07, Gabriele Giacone wrote: Package: critterding Version: 1.0-beta14+dfsg-1 Severity: grave It segfaults right away. Attaching backtrace, glxinfo and lshw outputs. One bug is enough. No need to report a bug per arch. Most probably arch is not relevant but segfaults are not the same. i386 one is on an old laptop which probably lacks of graphic power (NV46), whereas amd64 one on more recent and powerful machine (NV98). Both with nouveau driver. -- G..e -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752808: qpid-cpp: diff for NMU version 0.16-7.2
tags 752808 + pending
thanks
Dear maintainer,
I've uploaded an NMU by gregor for qpid-cpp (versioned as 0.16-7.2) to
DELAYED/5. Please feel free to tell me if I should delay it longer.
Note that the .install file needs to be executable, which may not be
represented in the diff.
Regards,
dam
diff -Nru qpid-cpp-0.16/debian/changelog qpid-cpp-0.16/debian/changelog
--- qpid-cpp-0.16/debian/changelog 2014-04-30 02:07:42.0 +0300
+++ qpid-cpp-0.16/debian/changelog 2014-08-04 14:56:19.0 +0300
@@ -1,3 +1,14 @@
+qpid-cpp (0.16-7.2) unstable; urgency=medium
+
+ [ gregor herrmann ]
+ * Non-maintainer upload.
+ * Fix hardcodes /usr/lib/perl5:
+make debian/libqpid-perl.install executable, and use $Config{vendorarch}
+to get the perl library path
+(Closes: #752808)
+
+ -- Damyan Ivanov d...@debian.org Mon, 04 Aug 2014 11:56:12 +
+
qpid-cpp (0.16-7.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru qpid-cpp-0.16/debian/libqpid-perl.install qpid-cpp-0.16/debian/libqpid-perl.install
--- qpid-cpp-0.16/debian/libqpid-perl.install 2012-09-29 01:32:22.0 +0300
+++ qpid-cpp-0.16/debian/libqpid-perl.install 2014-08-04 14:56:00.0 +0300
@@ -1 +1,3 @@
-usr/lib/perl5
+#!/usr/bin/perl -w
+use Config;
+print substr($Config{vendorarch}, 1) . \n;
Bug#752425: [Pkg-xfce-devel] Bug#752425: Bug#752425: xfce4-session: upower-1.0 transition
My concern was lack of a suspend (or hibernate) button in the logout dialog after recent dist-upgrades. Testing in a VM, I can confirm that installing xfce4-session 4.10.1-7 restores the missing suspend and hibernate buttons, and that downgrading to 4.10.1-6 causes the suspend and hibernate buttons to go missing from the logout dialog again. Short form: upgrading to 4.10.1-7 fixes my frustrating logout dialog button problem after logging out and back in again; thank you maintainers! -- Andrew Chadwick
Processed: redhat-cluster: diff for NMU version 3.1.8-1.2
Processing commands for cont...@bugs.debian.org: tags 752811 + pending Bug #752811 [src:redhat-cluster] redhat-cluster: hardcodes /usr/lib/perl5 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 752811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752811 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#752811: redhat-cluster: diff for NMU version 3.1.8-1.2
tags 752811 + pending
thanks
Dear maintainer,
I've uploaded NMU by gregor for redhat-cluster (versioned as
3.1.8-1.2) to DELAYED/5. Please feel free to tell me if I should delay
it longer.
Note that file mode changes aren't represented by 'diff' and
debian/libccs-perl.install needs to be made executable after diff
application.
Regards,
dam
diff -Nru redhat-cluster-3.1.8/debian/changelog redhat-cluster-3.1.8/debian/changelog
--- redhat-cluster-3.1.8/debian/changelog 2013-01-11 20:40:29.0 +0200
+++ redhat-cluster-3.1.8/debian/changelog 2014-08-04 15:35:20.0 +0300
@@ -1,3 +1,14 @@
+redhat-cluster (3.1.8-1.2) unstable; urgency=medium
+
+ [ gregor herrmann ]
+ * Non-maintainer upload.
+ * Fix hardcodes /usr/lib/perl5:
+make debian/libccs-perl.install executable and use $Config{vendorarch} to
+get dynamic path
+(Closes: #752811)
+
+ -- Damyan Ivanov d...@debian.org Mon, 04 Aug 2014 12:34:59 +
+
redhat-cluster (3.1.8-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru redhat-cluster-3.1.8/debian/libccs-perl.install redhat-cluster-3.1.8/debian/libccs-perl.install
--- redhat-cluster-3.1.8/debian/libccs-perl.install 2013-01-11 20:40:29.0 +0200
+++ redhat-cluster-3.1.8/debian/libccs-perl.install 2014-08-04 15:34:49.0 +0300
@@ -1,3 +1,9 @@
-usr/lib/perl5/auto/Cluster/CCS/CCS.so
-usr/lib/perl5/Cluster/CCS.pm
-usr/share/man/man3/*CCS.3pm*
+#!/usr/bin/perl -w
+
+use Config;
+
+my $vendorarch = substr($Config{vendorarch}, 1);
+
+print $vendorarch/auto/Cluster/CCS/CCS.so\n;
+print $vendorarch/Cluster/CCS.pm\n;
+print usr/share/man/man3/*CCS.3pm*\n;
Bug#757014: crosshurd: Fails to install GNU/Hurd due to bumped libparted SONAME
Package: crosshurd Version: 1.7.46 Severity: serious Tags: patch Hi! While updating the .deb format support, I noticed that the program fails to install GNU/Hurd due to a bumped SONAME in libparted. Here's a trivial patch fixing this. Thanks, Guillem From 8e9d1d5f1629877a7308bd5292feaceff307410f Mon Sep 17 00:00:00 2001 From: Guillem Jover guil...@debian.org Date: Mon, 4 Aug 2014 14:14:21 +0200 Subject: [PATCH 1/4] Switch from libparted0debian1 to libparted2 --- makehurddir.sh | 4 ++-- packages/gnu | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/makehurddir.sh b/makehurddir.sh index 8caf06a..4f3670e 100755 --- a/makehurddir.sh +++ b/makehurddir.sh @@ -48,8 +48,8 @@ if [ -e $TARGET/var/cache/apt/archives/libbz2-1.0_* ] ; then extract libbz2-1.0 fi -if [ -e $TARGET/var/cache/apt/archives/libparted0debian1_* ] ; then -extract libparted0debian1 +if [ -e $TARGET/var/cache/apt/archives/libparted2_* ] ; then +extract libparted2 fi x_feign_install dpkg diff --git a/packages/gnu b/packages/gnu index c7bc014..ae805a9 100644 --- a/packages/gnu +++ b/packages/gnu @@ -1,6 +1,6 @@ gnumach-image-1-486 hurd -libparted0debian1 +libparted2 libuuid1 libc0.3 inetutils-tools -- 2.0.1.570.gc6b0718
Bug#757006: marked as done (rrdtool: maintainer address bounces)
Your message dated Mon, 04 Aug 2014 16:51:05 +0200 with message-id 53df9dd9.7000...@bzed.de and subject line not bouncing anymore. has caused the Debian Bug report #757006, regarding rrdtool: maintainer address bounces 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.) -- 757006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: rrdtool Severity: serious Tags: sid X-Debbugs-Cc: tok...@debian.org, formo...@debian.org, b...@debian.org The maintainer address for rrdtool bounces, see below. Ansgar On 08/04/2014 13:30, Mail Delivery System wrote: This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: rrdt...@ml.snow-crash.org SMTP error from remote mail server after RCPT TO:rrdt...@ml.snow-crash.org: host apu.snow-crash.org [2a01:4f8:130:53c9::2]: 550 5.1.1 rrdt...@ml.snow-crash.org: Recipient address rejected: User unknown in local recipient table -- This is a copy of the message, including all the headers. -- Return-path: dak-unp...@franck.debian.org Received: from franck.debian.org ([138.16.160.12]) from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP CA,CN=franck.debian.org,EMAIL=hostmas...@franck.debian.org (verified) by mailly.debian.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from dak-unp...@franck.debian.org) id 1XEGTf-0006iw-4b for rrdt...@ml.snow-crash.org; Mon, 04 Aug 2014 11:30:55 + Received: from dak-unpriv by franck.debian.org with local (Exim 4.80) (envelope-from dak-unp...@franck.debian.org) id 1XEGTd-0007uk-Mu for rrdt...@ml.snow-crash.org; Mon, 04 Aug 2014 11:30:53 + To: rrdt...@ml.snow-crash.org From: Debian FTP Masters ftpmas...@ftp-master.debian.org Subject: Processing of rrdtool_1.4.8-1.1_amd64.changes Date: Mon, 04 Aug 2014 11:30:53 + X-Debian: DAK X-DAK: DAK Precedence: bulk Auto-Submitted: auto-generated X-Debian-Package: rrdtool Message-Id: e1xegtd-0007uk...@franck.debian.org Sender: unprivileged ftp-master role account dak-unp...@franck.debian.org rrdtool_1.4.8-1.1_amd64.changes uploaded successfully to localhost along with the files: rrdtool_1.4.8-1.1_amd64.deb rrdcached_1.4.8-1.1_amd64.deb rrdtool-dbg_1.4.8-1.1_amd64.deb librrd4_1.4.8-1.1_amd64.deb librrd-dev_1.4.8-1.1_amd64.deb librrds-perl_1.4.8-1.1_amd64.deb rrdtool-tcl_1.4.8-1.1_amd64.deb python-rrdtool_1.4.8-1.1_amd64.deb ruby-rrd_1.4.8-1.1_amd64.deb liblua5.1-rrd0_1.4.8-1.1_amd64.deb liblua5.1-rrd-dev_1.4.8-1.1_amd64.deb librrdp-perl_1.4.8-1.1_all.deb librrd-ruby_1.4.8-1.1_all.deb librrd-ruby1.8_1.4.8-1.1_all.deb librrd-ruby1.9.1_1.4.8-1.1_all.deb rrdtool_1.4.8-1.1.dsc rrdtool_1.4.8-1.1.diff.gz Greetings, Your Debian queue daemon (running on host franck.debian.org) ---End Message--- ---BeginMessage--- -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F---End Message---
Processed: [gpsd/master] Set GPSD_SOCKET to the default location.
Processing commands for cont...@bugs.debian.org: tag 756488 pending Bug #756488 [gpsd] gpsd: hotplug is broken with systemd due to wrong GPSD_SOCKET Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 756488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756488 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#756488: [gpsd/master] Set GPSD_SOCKET to the default location.
tag 756488 pending thanks Date: Mon Aug 4 17:15:58 2014 +0200 Author: Bernd Zeimetz be...@bzed.de Commit ID: 7b5a981146f52735404102617b4b9b538313b225 Commit URL: http://git.recluse.de/?p=debian/pkg-gpsd.git;a=commitdiff;h=7b5a981146f52735404102617b4b9b538313b225 Patch URL: http://git.recluse.de/?p=debian/pkg-gpsd.git;a=commitdiff_plain;h=7b5a981146f52735404102617b4b9b538313b225 Set GPSD_SOCKET to the default location. Closes: #756488 Thanks: Jeremy Laine -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756488: marked as done (gpsd: hotplug is broken with systemd due to wrong GPSD_SOCKET)
Your message dated Mon, 04 Aug 2014 15:34:36 + with message-id e1xekhu-0005ec...@franck.debian.org and subject line Bug#756488: fixed in gpsd 3.10+dev3~d6b65b48-2 has caused the Debian Bug report #756488, regarding gpsd: hotplug is broken with systemd due to wrong GPSD_SOCKET 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.) -- 756488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gpsd Version: 3.10+dev3~d6b65b48-1 Severity: grave Justification: renders package unusable Since the switch to systemd, gpsd's support for hotplug of USB devices is broken using the default configuration. This means that for most users, just installing gpsd and plugging in a GPS does not work, and it breaks working installations upon upgrade. The problem is that the udev hotplug script and gpsd have diverging views of what the control socket path is. When gpsd is installed on jessie, it is launched by systemd as follows: gpsd -N = it uses gpsd's default control socket path: /var/run/gpsd.sock This is confirmed by running lsof -p `pidof gpsd` gpsd5271 gpsd3u unix 0x8800a10127c0 0t0 71137 /var/run/gpsd.sock The udev hotplug script on the other hand reads /etc/default/gpsd to determine the path of the control socket, and the default value is: # gpsd control socket location. GPSD_SOCKET=/run/gpsd/gpsd.sock As a result of this, when the GPS is plugged in, the hotplug script thinks gpsd is not running, and launches a new instance of gpsd. This new instance of gpsd does not work as the port on which gpsd listens is already taken by the first process. Please either change the default value of GPSD_SOCKET in /etc/default/gpsd or change the systemd launch script so that it respects GPSD_SOCKET. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gpsd depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.20 ii libbluetooth35.21-1 ii libc62.19-7 ii libdbus-1-3 1.8.6-1 ii libgps21 3.10+dev3~d6b65b48-1 ii libusb-1.0-0 2:1.0.19-1 ii lsb-base 4.1+Debian13 ii netbase 5.2 ii systemd-sysv 208-6 Versions of packages gpsd recommends: ii python 2.7.8-1 ii udev208-6 Versions of packages gpsd suggests: ii dbus 1.8.6-1 pn gpsd-clients none -- no debconf information ---End Message--- ---BeginMessage--- Source: gpsd Source-Version: 3.10+dev3~d6b65b48-2 We believe that the bug you reported is fixed in the latest version of gpsd, 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 756...@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 gpsd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Aug 2014 17:19:32 +0200 Source: gpsd Binary: gpsd gpsd-dbg gpsd-clients python-gps libgps21 libgps-dev libqgpsmm21 libqgpsmm-dev Architecture: source amd64 Version: 3.10+dev3~d6b65b48-2 Distribution: unstable Urgency: medium Maintainer: Bernd Zeimetz b...@debian.org Changed-By: Bernd Zeimetz b...@debian.org Description: gpsd - Global Positioning System - daemon gpsd-clients - Global Positioning System - clients gpsd-dbg - Global Positioning System - debugging symbols libgps-dev - Global Positioning System - development files libgps21 - Global Positioning System - library libqgpsmm-dev - Global Positioning System - Qt wrapper for libgps (development) libqgpsmm21 - Global Positioning System - Qt wrapper for libgps python-gps - Global Positioning System - Python libraries Closes: 756488 Changes: gpsd (3.10+dev3~d6b65b48-2) unstable; urgency=medium . * [7b5a9811] Set GPSD_SOCKET to the default location. Thanks to Jeremy Laine (Closes: #756488) Checksums-Sha1:
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 714234 grave Bug #714234 [dump] dump: restore #157 dump fails to restore incremental if directory was removed Severity set to 'grave' from 'important' tags 714234 +upstream patch Bug #714234 [dump] dump: restore #157 dump fails to restore incremental if directory was removed Added tag(s) upstream and patch. forwarded 714234 http://sourceforge.net/p/dump/bugs/157/ Bug #714234 [dump] dump: restore #157 dump fails to restore incremental if directory was removed Set Bug forwarded-to-address to 'http://sourceforge.net/p/dump/bugs/157/'. quit Stopping processing here. Please contact me if you need assistance. -- 714234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714234 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#722293: Proposed patch upstream
Processing control commands: severity -1 grave Bug #722293 [imagination] Port to avconv Severity set to 'grave' from 'important' retitle -1 Fails to generate video due to the lack of ffmpeg command Bug #722293 [imagination] Port to avconv Changed Bug title to 'Fails to generate video due to the lack of ffmpeg command' from 'Port to avconv' -- 722293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722293 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#754633: marked as done (icedove: FTBFS on armel: Error: selected processor does not support ARM mode […])
Your message dated Mon, 04 Aug 2014 16:21:42 +
with message-id e1xel14-0003ey...@franck.debian.org
and subject line Bug#754633: fixed in icedove 31.0-1
has caused the Debian Bug report #754633,
regarding icedove: FTBFS on armel: Error: selected processor does not support
ARM mode […]
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.)
--
754633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: icedove
Version: 31.0~b1-2
Severity: serious
Justification: FTBFS
Hi,
your package no longer builds on armel:
| gcc -o nestegg.o -c -fvisibility=hidden -DMOZ_GLUE_IN_PROGRAM
-DNO_NSPR_10_SUPPORT -I/«PKGBUILDDIR»/mozilla/media/libnestegg/src -I.
-I../../../dist/include -I/usr/include/nspr -I/usr/include/nss
-I/«PKGBUILDDIR»/obj-icedove/mozilla/dist/include -I/usr/include
-I/usr/include/pixman-1-fPIC -D_FORTIFY_SOURCE=2 -include
../../../mozilla-config.h -DMOZILLA_CLIENT -MD -MP -MF .deps/nestegg.o.pp
-D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith -Wdeclaration-after-statement
-Werror=return-type -Werror=int-to-pointer-cast -Wtype-limits -Wempty-body
-Wsign-compare -Wno-unused -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Werror=format-security -std=gnu99 -fgnu89-inline -fno-strict-aliasing
-ffunction-sections -fdata-sections -fno-math-errno -pthread -pipe -DNDEBUG
-DTRIMMED -g -Os -freorder-blocks -fomit-frame-pointer
/«PKGBUILDDIR»/mozilla/media/libnestegg/src/nestegg.c
| /«PKGBUILDDIR»/mozilla/media/libnestegg/src/nestegg.c: In function
'ne_read_simple':
| /«PKGBUILDDIR»/mozilla/media/libnestegg/src/nestegg.c:983:6: warning: 'r' may
be used uninitialized in this function [-Wmaybe-uninitialized]
|if (r == 1)
| ^
| {standard input}: Assembler messages:
| {standard input}:528: Error: selected processor does not support ARM mode
`smulbb r2,r2,r7'
| {standard input}:1128: Error: selected processor does not support ARM mode
`smulbb r3,r2,r3'
| make[8]: *** [A2NLSF.o] Error 1
| make[7]: *** [../../media/libopus_libs] Error 2
| make[7]: *** Waiting for unfinished jobs
| /«PKGBUILDDIR»/mozilla/config/rules.mk:969: recipe for target 'A2NLSF.o'
failed
Full build log:
https://buildd.debian.org/status/fetch.php?pkg=icedovearch=armelver=31.0~b1-2stamp=1403489996
Mraw,
KiBi.
---End Message---
---BeginMessage---
Source: icedove
Source-Version: 31.0-1
We believe that the bug you reported is fixed in the latest version of
icedove, 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 754...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Goehre ch...@sigxcpu.org (supplier of updated icedove package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 04 Aug 2014 10:23:09 -0400
Source: icedove
Binary: icedove icedove-dev icedove-dbg iceowl-extension
calendar-google-provider
Architecture: source amd64 all
Version: 31.0-1
Distribution: unstable
Urgency: low
Maintainer: Christoph Goehre ch...@sigxcpu.org
Changed-By: Christoph Goehre ch...@sigxcpu.org
Description:
calendar-google-provider - Google Calendar support for lightning- and
iceowl-extension
icedove- mail/news client with RSS and integrated spam filter support
icedove-dbg - Debug Symbols for Icedove
icedove-dev - Development files for Icedove
iceowl-extension - Calendar Extension for Thunderbird/Icedove
Closes: 754633 756769
Changes:
icedove (31.0-1) unstable; urgency=low
.
[ Carsten Schoenert ]
* [b7cdeb4] Imported Upstream version 31.0 (Closes: #756769)
* [1f2ff0b] debian/rules: fixing file permissions in iceowl-extension
* [c8d2036] adding fix for skia on armel
* [77093e2] fixing FTBFS on armel (Closes: #754633)
* [a458959] debian/control: increase b-d on libsqlite-dev
* [a98ebca] fix runtime error on alpha while jemalloc run
* [6f6b576] disable optimization on alpha while linking
Checksums-Sha1:
be67fd33d84ff8c3fbe09d0937846e0e4925f540 2905 icedove_31.0-1.dsc
75ef26f289f6d7c527ae260dee484e3b3d472187 140903476 icedove_31.0.orig.tar.xz
f0d071c8846ba6dcc811dedd30d6f3fd81e00684 37
Bug#751277: python-biopython: FTBFS on mips* powerpc s390x
Hello, I took a look at test failures on mips/mipsel. Test that fails is based on a result of dnal tool. dnal is part of a debian package wise. In file: Bio/Wise/__init__.py, an error was raised because the return value from dnal is greater than 1. If you look at dnal.c: alb = make_align_dnaalign(one,two,mat,dse,-gap,-ext,-gap,-ext,dpri); printf(Score %d\n,alb-score); if( alb == NULL ) fatal(Could not build alignment!); if( show_pretty == TRUE ) write_pretty_seq_align(alb,one,two,12,60,stdout); if( show_alb == TRUE ) dump_ascii_AlnBlock(alb,stdout); } you can see that there is no return statement. In this case the return value of dnal usually will be the return value of last used function. This behavior is mutable. It can not be guaranteed on all architectures, or if different optimization flags are used. Further, using dnal with different options, last used function could be changed. Adding return 0; at the end of main function in dnal.c, test_align (test_Wise.TestWise) successfully passes on mips/mipsel. With this fix, package python-biopython successfully builds for mipsel. Patch that includes this fix is attached. Unfortunately, on mips (BE) test test_Cluster.py failed under Python 3.4. Any progress on this issue? Best Regards, Dejan --- wise-2.4.1.orig/src/models/dnal.c 2004-11-24 16:26:11.0 + +++ wise-2.4.1/src/models/dnal.c 2014-07-31 14:53:54.0 + @@ -75,6 +75,8 @@ if( show_alb == TRUE ) dump_ascii_AlnBlock(alb,stdout); + + return 0; }
Bug#751277: python-biopython: FTBFS on mips* powerpc s390x
On Mon, Aug 4, 2014 at 6:10 PM, Dejan Latinovic dejan.latino...@imgtec.com wrote: Hello, I took a look at test failures on mips/mipsel. Test that fails is based on a result of dnal tool. dnal is part of a debian package wise. ... With this fix, package python-biopython successfully builds for mipsel. Patch that includes this fix is attached. That sounds useful for the wise package :) Unfortunately, on mips (BE) test test_Cluster.py failed under Python 3.4. Any progress on this issue? No. See discussion on https://github.com/biopython/biopython/pull/340 Peter -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753589: systemd: missing pre-dependencies for runlevel(8) etc.
On 2014-08-04 Simon McVittie smcv-8fiuurrzop0dnm+yrof...@public.gmane.org
wrote:
Control files: lines which differ (wdiff format)
Depends: libacl1 (= 2.2.51-8), libaudit1 (= 1:2.2.1), libblkid1 (=
2.17.2), [-libc6 (= 2.17),-] libcap2 (= 2.10), libcryptsetup4 (=
2:1.4.3), libdbus-1-3 (= 1.1.1), [-libgcrypt11 (= 1.5.1),-] libkmod2 (=
5~), [-liblzma5 (= 5.1.1alpha+20120614),-] libpam0g (= 0.99.7.1),
libselinux1 (= 2.1.9), [-libsystemd-daemon0 (= 208-5),-]
libsystemd-journal0 (= 208-5), libudev1 (= 189), libwrap0 (= 7.6-4~),
libsystemd-login0 (= 208-5), util-linux (= 2.19.1-2), initscripts (=
2.88dsf-17), sysv-rc, udev, acl, adduser, libcap2-bin
{+Pre-Depends: libc6 (= 2.17), libdbus-1-3 (= 1.0.2), libgcrypt11 (=
1.5.1), liblzma5 (= 5.1.1alpha+20120614), libselinux1 (= 2.0.65),
libsystemd-daemon0 (= 208-5)+}
Expanded dependency tree:
libc6 is already quasi-Essential, via e.g. coreutils
libdbus-1-3 Depends: libc6 (= 2.17)
libgcrypt11 Depends: libc6 (= 2.15)
libgcrypt11 Depends: libgpg-error0 (= 1.10), already satisfied in stable
[...]
Hello,
Could you use this opportunity to move to libgcrypt20? It would be
nice to avoid adding th pre-dependency on libgcrypt11 now and later
have another discussion when replacing with one on libgcrypt20.
thanks for considering, cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757031: missing dependency on julia
Package: julia-factcheck Version: 0.1.2-1 Severity: serious As per subject. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594 signature.asc Description: Digital signature
Bug#753589: systemd: missing pre-dependencies for runlevel(8) etc.
Andreas Metzler ametz...@bebt.de writes: Could you use this opportunity to move to libgcrypt20? It would be nice to avoid adding th pre-dependency on libgcrypt11 now and later have another discussion when replacing with one on libgcrypt20. Obviously it's a good idea to move with SONAME changes, but for the record, there's no need to have the discussion again after a library SONAME change. Pre-Depends on libraries should be assumed to track SONAME changes in that library. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755014: marked as done (apq: uninstallable on sid, needs update for gnat-4.9)
Your message dated Mon, 04 Aug 2014 17:48:54 +
with message-id e1xemns-0005hc...@franck.debian.org
and subject line Bug#755014: fixed in apq 3.2.0-1.1
has caused the Debian Bug report #755014,
regarding apq: uninstallable on sid, needs update for gnat-4.9
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.)
--
755014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: apq
Version: 3.2.0-1
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Dear Maintainer,
This package depends on a old gnat version. Currently it doesn't build on
ppc64el because ppc64el support started on GCC/GNAT 4.8, so, I would like if
you can increase the gnat version on the dependencies, to a more recent version.
I am providing a patch that would do it for you.
On the other side, if you want to continue to use the current gnat version, you
can do something like:
-Depends: gnat-4-6
+Depends: gnat-4.6 [!ppc64el] | gnat-4.8 [ppc64el]
Thank you,
Breno
Index: apq-3.2.0/debian/control
===
--- apq-3.2.0.orig/debian/control
+++ apq-3.2.0/debian/control
@@ -4,7 +4,7 @@ Priority: optional
Maintainer: Adrian-Ken Rueegsegger k...@codelabs.ch
Uploaders: Reto Buerki r...@codelabs.ch
DM-Upload-Allowed: yes
-Build-Depends: debhelper (= 8), gnat, gnat-4.6, gprbuild, chrpath,
+Build-Depends: debhelper (= 8), gnat, gnat-4.8, gprbuild, chrpath,
texlive-latex-recommended, texlive-fonts-recommended, latex-xcolor
Standards-Version: 3.9.3
Homepage: http://framework.kow.com.br/
@@ -22,7 +22,7 @@ Description: Pluggable Ada 95 Binding to
Package: libapq3.2.0-dev
Section: libdevel
Architecture: any
-Depends: ${misc:Depends}, libapq3.2.0 (= ${binary:Version}), gnat, gnat-4.6
+Depends: ${misc:Depends}, libapq3.2.0 (= ${binary:Version}), gnat, gnat-4.8
Description: Pluggable Ada 95 Binding to various database systems (development)
APQ is a pluggable Ada 95 Binding to various database systems like
PostgreSQL or MySQL. This is the core package providing the plugin
---End Message---
---BeginMessage---
Source: apq
Source-Version: 3.2.0-1.1
We believe that the bug you reported is fixed in the latest version of
apq, 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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose doko@foobar (supplier of updated apq package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 04 Aug 2014 19:34:36 +0200
Source: apq
Binary: libapq3.2.0 libapq3.2.0-dev libapq3.2.0-dbg
Architecture: source amd64
Version: 3.2.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Adrian-Ken Rueegsegger k...@codelabs.ch
Changed-By: Matthias Klose doko@foobar
Description:
libapq3.2.0 - Pluggable Ada 95 Binding to various database systems (library)
libapq3.2.0-dbg - Pluggable Ada 95 Binding to various database systems (debug)
libapq3.2.0-dev - Pluggable Ada 95 Binding to various database systems
(development
Closes: 755014
Changes:
apq (3.2.0-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Build using gnat-4.9. Closes: #755014.
Checksums-Sha1:
b06d11351c59ba047239bf6d157e4960caf61bca 1396 apq_3.2.0-1.1.dsc
c9a667837adaec881d816f1153b9de9ec044dc48 3792 apq_3.2.0-1.1.debian.tar.xz
da2f21ffa05f0805276c3cf06b38b10e0cc4bea2 39950 libapq3.2.0_3.2.0-1.1_amd64.deb
9ea4be9621f19eb808f5d2e0c075aa3ab5d0e6ff 689242
libapq3.2.0-dev_3.2.0-1.1_amd64.deb
eaa9e814cf789b5f429a4f31ff78951209a03328 48384
libapq3.2.0-dbg_3.2.0-1.1_amd64.deb
Checksums-Sha256:
b7e3acf2bfee0aec45bb2aca495ead869f78a9878b85167b5fec8b999836a3e4 1396
apq_3.2.0-1.1.dsc
0d6f53dde4c2227783f4241b980887155b8fa5a6ef12f9354693eaaf1489370e 3792
apq_3.2.0-1.1.debian.tar.xz
7a92d7d7285da018f1a4cdff682e12be80bb9c4e1dbed41f6a56a33ccc77a523 39950
libapq3.2.0_3.2.0-1.1_amd64.deb
915f77ba1a2c701dee624c2d73b54fd8ee389d796ee6e638db22f64ef30a7d33 689242
libapq3.2.0-dev_3.2.0-1.1_amd64.deb
bc41e5733fba08ea2b75819b24e8eac473503588a734868ce482c38b72f6bf1e 48384
Bug#755339: Please make sure you file an upstream bug in future
The foolscap bug tracker is easy to find: http://foolscap.lothar.com/trac -- Daira Hopwood ⚥ signature.asc Description: OpenPGP digital signature
Bug#755016: marked as done (apq-postgresql: uninstallable on sid, needs update for gnat-4.9)
Your message dated Mon, 04 Aug 2014 18:04:11 +
with message-id e1xemcf-0007bs...@franck.debian.org
and subject line Bug#755016: fixed in apq-postgresql 3.2.0-2.1
has caused the Debian Bug report #755016,
regarding apq-postgresql: uninstallable on sid, needs update for gnat-4.9
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.)
--
755016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: apq-postgresql
Version: 3.2.0-2
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Dear Maintainer,
This package depends on a old gnat version. Currently it doesn't build on
ppc64el because ppc64el support started on GCC/GNAT 4.8, so, I would like if
you can increase the gnat version on the dependencies, to a more recent version.
I am providing a patch that would do it for you.
On the other side, if you want to continue to use the current gnat version, you
can do something like:
-Depends: gnat-4-6
+Depends: gnat-4.6 [!ppc64el] | gnat-4.8 [ppc64el]
Thank you,
Breno
Index: apq-postgresql-3.2.0/debian/control
===
--- apq-postgresql-3.2.0.orig/debian/control
+++ apq-postgresql-3.2.0/debian/control
@@ -4,7 +4,7 @@ Priority: optional
Maintainer: Adrian-Ken Rueegsegger k...@codelabs.ch
Uploaders: Reto Buerki r...@codelabs.ch
DM-Upload-Allowed: yes
-Build-Depends: debhelper (= 8), gnat, gnat-4.6, gcc (= 4.6), gprbuild, chrpath,
+Build-Depends: debhelper (= 8), gnat, gnat-4.8, gcc (= 4.6), gprbuild, chrpath,
libpq-dev, libapq3.2.0-dev
Standards-Version: 3.9.3
Homepage: http://framework.kow.com.br/
@@ -22,7 +22,7 @@ Package: libapq-postgresql3.2.0-dev
Section: libdevel
Architecture: any
Depends: ${misc:Depends}, libapq-postgresql3.2.0 (= ${binary:Version}),
- libpq-dev, libapq3.2.0-dev, gnat, gnat-4.6
+ libpq-dev, libapq3.2.0-dev, gnat, gnat-4.8
Conflicts: libapq-postgresql-dev
Replaces: libapq-postgresql-dev
Description: APQ Ada 95 Postgresql Binding Plugin (development)
---End Message---
---BeginMessage---
Source: apq-postgresql
Source-Version: 3.2.0-2.1
We believe that the bug you reported is fixed in the latest version of
apq-postgresql, 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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated apq-postgresql package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 04 Aug 2014 19:49:56 +0200
Source: apq-postgresql
Binary: libapq-postgresql3.2.0 libapq-postgresql3.2.0-dev
libapq-postgresql3.2.0-dbg
Architecture: source amd64
Version: 3.2.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Adrian-Ken Rueegsegger k...@codelabs.ch
Changed-By: Matthias Klose d...@debian.org
Description:
libapq-postgresql3.2.0 - APQ Ada 95 Postgresql Binding Plugin (library)
libapq-postgresql3.2.0-dbg - APQ Ada 95 Postgresql Binding Plugin (debug)
libapq-postgresql3.2.0-dev - APQ Ada 95 Postgresql Binding Plugin (development)
Closes: 755016
Changes:
apq-postgresql (3.2.0-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Build using gnat 4.9. Closes: #755016.
Checksums-Sha1:
de07e84bf79d3794e8256eac5f11864017a1b05a 1533 apq-postgresql_3.2.0-2.1.dsc
2938d3d6f802bced989d00a5761811663c3d7323 4804
apq-postgresql_3.2.0-2.1.debian.tar.xz
4245fc42a48edcc3b7504615babc9592e8bd6d4e 42360
libapq-postgresql3.2.0_3.2.0-2.1_amd64.deb
862ce398d042b6e76ecb67be6a6d5023dc073120 90190
libapq-postgresql3.2.0-dev_3.2.0-2.1_amd64.deb
a5d69c95c8324d13321924a94d1f8a532119 64846
libapq-postgresql3.2.0-dbg_3.2.0-2.1_amd64.deb
Checksums-Sha256:
608582eb1a7d2522c9f9c04721c243174375a43e17f42004617545543451f7a5 1533
apq-postgresql_3.2.0-2.1.dsc
9a391e47885531a7e66c687df7f32ce80d4bdd7d20c649a5dd89ffdc68c50729 4804
apq-postgresql_3.2.0-2.1.debian.tar.xz
d7705e43c28f7bf783344a0db5c371baeffc2f95ac686a984b4819c198da894e 42360
libapq-postgresql3.2.0_3.2.0-2.1_amd64.deb
9da503f68bd03d3e98f170dfdca1407fae4f0ed0ca8e95c76722eb050d5903a7 90190
Bug#756465: maxima: Segmentation fault during startup
Greetings! OK, I think I can fix this with the next upload. It would
be helpful if you could send in the gdb session:
(gdb) p/x my_stdin
(gdb) p/x my_stdout
(gdb) p/x my_stderr
Take care,
Jörg Morbitzer j...@morbitzer.de writes:
Here we go, maybe|hopefully it is helpful:
- cut --
jomo@mars [/home/jomo] gdb /usr/lib/maxima/5.33.0/binary-gcl/maxima
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as i486-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/lib/maxima/5.33.0/binary-gcl/maxima...(no
debugging symbols found)...done.
(gdb) set env MAXIMA_PREFIX /usr/lib/maxima/5.33.0/
(gdb) handle SIGSEGV nostop noprint
SignalStop Print Pass to program Description
SIGSEGV NoNo Yes Segmentation fault
(gdb) b error
Breakpoint 1 at 0x2a020
(gdb) r -eval '(run)'
Starting program: /usr/lib/maxima/5.33.0/binary-gcl/maxima -eval '(run)'
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need set solib-search-path or set sysroot?
Breakpoint 1, 0x0002a020 in error ()
(gdb) where
#0 0x0002a020 in error ()
#1 0x0002a0ad in ?? ()
#2 signal handler called
#3 __GI__IO_fflush (fp=0x403e0aa0) at iofflush.c:40
#4 0x000c8ac7 in ?? ()
#5 0x000cb8e6 in ?? ()
#6 0x000d9e87 in malloc ()
#7 0x4b274f2c in __fopen_internal (filename=filename@entry=0x4b370d01
/proc/meminfo,
mode=mode@entry=0x4b36e43c rce, is32=is32@entry=1) at iofopen.c:73
#8 0x4b27500b in _IO_new_fopen (filename=filename@entry=0x4b370d01
/proc/meminfo,
mode=mode@entry=0x4b36e43c rce) at iofopen.c:103
#9 0x4b2f9237 in phys_pages_info (format=0x4b370d4a MemTotal: %ld kB)
at ../sysdeps/unix/sysv/linux/getsysstats.c:296
#10 0x4b2f9696 in __get_phys_pages () at
../sysdeps/unix/sysv/linux/getsysstats.c:340
#11 0x4b2c811a in posix_sysconf (name=85) at ../sysdeps/posix/sysconf.c:632
#12 linux_sysconf (name=85) at
../sysdeps/unix/sysv/linux/x86_64/../sysconf.c:145
#13 __GI___sysconf (name=85) at
../sysdeps/unix/sysv/linux/x86_64/sysconf.c:36
#14 0x000271fd in ?? ()
#15 0x000d6997 in ?? ()
#16 0x00020cc6 in ?? ()
#17 0x4b22aa63 in __libc_start_main (main=0x20c90, argc=3,
argv=0xb464, init=0x31a0f0, fini=0x31a160,
rtld_fini=0x4b1fcc90 _dl_fini, stack_end=0xb45c) at
libc-start.c:287
#18 0x00021b4c in ?? ()
(gdb)
- cut --
- cut --
jomo@mars [/home/jomo] strace -f /usr/lib/maxima/5.33.0/binary-gcl/maxima
execve(/usr/lib/maxima/5.33.0/binary-gcl/maxima,
[/usr/lib/maxima/5.33.0/binary-gc...], [/* 44 vars */]) = 0
brk(0) = 0x2f27000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb77c3000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or
directory)
open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=194548, ...}) = 0
mmap2(NULL, 194548, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7793000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/usr/lib/i386-linux-gnu/libX11.so.6, O_RDONLY|O_CLOEXEC) = 3
read(3,
\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200\4OK4\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=1278448, ...}) = 0
mmap2(0x4b4dc000, 1280816, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x4b4dc000
mprotect(0x4b61, 4096, PROT_NONE) = 0
mmap2(0x4b611000, 16384, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x134000) = 0x4b611000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i386-linux-gnu/i686/cmov/libm.so.6, O_RDONLY|O_CLOEXEC) = 3
read(3,
\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\226K4\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=281844, ...}) = 0
mmap2(0x4b3c5000, 282784, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x4b3c5000
mmap2(0x4b409000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x43000) = 0x4b409000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/usr/lib/i386-linux-gnu/libgmp.so.10, O_RDONLY|O_CLOEXEC) = 3
read(3,
Bug#757033: python-yahoo: websearch fails with urlopen error [Errno -2] Name or service not known
Package: python-yahoo Version: 3.1-3 Severity: grave python-yahoo is no longer usable. The included websearch.py example fails with: Got an error - urlopen error [Errno -2] Name or service not known Also, both servers (search.yahooapis.com and local.yahooapis.com) that are used to submit search requests cannot be resolved. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#755339: Please make sure you file an upstream bug in future
On 04.08.2014 19:57, Daira Hopwood wrote: The foolscap bug tracker is easy to find: http://foolscap.lothar.com/trac the issue was already fixed upstream before this bug was filed: https://github.com/warner/foolscap/commit/2eeabc61c2573652d7482d039644d62d782c2e3a -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: sqlite: Still useful?
Processing control commands: severity -1 serious Bug #607969 [sqlite] sqlite: Still useful? Severity set to 'serious' from 'important' -- 607969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607969: sqlite: Still useful?
Control: severity -1 serious Hi, I stumbled upon this bug by chance when looking at why it did not compile in some new ports. Raising severity so at the very least it gets auto-removed from testing and thus it does not get included in the next stable release (it already was included in the last, despite opinions in this bug about the contrary). I guess that it's better to just ask FTP masters to remove the package, but I'll leave that to other people, since they were interested in doing that in the past (all in copy now). Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: sqlite: Still useful?
Processing control commands: severity -1 serious Bug #607969 [sqlite] sqlite: Still useful? Ignoring request to change severity of Bug 607969 to the same value. -- 607969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607969 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#755457: marked as done (gpsbabel-doc: No documentation contained, all files only contain a few lines of PHP)
Your message dated Mon, 04 Aug 2014 19:18:59 + with message-id e1xenmd-00070t...@franck.debian.org and subject line Bug#755457: fixed in gpsbabel 1.5.0-3 has caused the Debian Bug report #755457, regarding gpsbabel-doc: No documentation contained, all files only contain a few lines of PHP 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.) -- 755457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gpsbabel-doc Version: 1.5.0-2 Severity: grave Justification: makes the package unusable or mostly so Dear Bernd, gpsbabel-doc does not (or likely no more) contain any useful HTML files. All HTML files are the same and look like this: ?php require(../lib/smarty_common.php); $smarty-display($template); ? $ dpkg -L gpsbabel-doc | fgrep .html | xargs md5sum 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_land_air_sea.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_navilink.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_destinator_poi.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_cambridge.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_gtm.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_navicache.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_dg-100.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_sbn.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_mapfactor.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_jogmap.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_enigma.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_garmin_gpi.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_cst.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_humminbird.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_an1.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/inifile.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_hiketech.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_google.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_iblue757.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/filter_polygon.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/Route_And_Track_Modes.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_tabsep.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_arc.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_ik3d.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/Introduction.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/styles_internal_const.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_dg-200.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/tracking.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_vitosmt.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_tef.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/filter_height.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_wfff.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_bcr.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_mmo.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_wintec_tes.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/Glossary.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_naviguide.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_saroute.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_m241-bin.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_garmin_xt.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/style_behavior.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_psitrex.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_xcsv.html 0be029b4e3bcbd3894b638f789be2ab5 /usr/share/doc/gpsbabel/htmldoc/fmt_vidaone.html 0be029b4e3bcbd3894b638f789be2ab5
Bug#747804: marked as done (spotlighter: FTBFS: error: Test for GTK3+ failed)
Your message dated Mon, 04 Aug 2014 19:40:18 + with message-id e1xeo7g-0001lg...@franck.debian.org and subject line Bug#747804: fixed in spotlighter 0.3-1.1 has caused the Debian Bug report #747804, regarding spotlighter: FTBFS: error: Test for GTK3+ failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 747804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: spotlighter Version: 0.3-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140510 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/05/10/spotlighter_0.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. ---End Message--- ---BeginMessage--- Source: spotlighter Source-Version: 0.3-1.1 We believe that the bug you reported is fixed in the latest version of spotlighter, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YunQiang Su s...@debian.org (supplier of updated spotlighter 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: Wed, 30 Jul 2014 16:26:02 +0800 Source: spotlighter Binary: spotlighter Architecture: source amd64 Version: 0.3-1.1 Distribution: unstable Urgency: low Maintainer: Andrea Colangelo war...@debian.org Changed-By: YunQiang Su s...@debian.org Description: spotlighter - gtk interface to make annotations on the screen Closes: 747804 Changes: spotlighter (0.3-1.1) unstable; urgency=low . * Non-maintainer upload. * don't use AM_PATH_GTK_3_0 in configure.ac, as it cannot work * use dh-autoreconf update build system (Closes: #747804 #727974) Checksums-Sha1: bd6f36db976d93b352b11eaa58371c81a5287bfe 1573 spotlighter_0.3-1.1.dsc f1c13d12e9714d607bd85490445281980ddbbad8 4228 spotlighter_0.3-1.1.debian.tar.xz 3b41c754f9542bd851843c4ac9ae9620bdd910c9 30412 spotlighter_0.3-1.1_amd64.deb Checksums-Sha256: 4f28660cee6f3f2c8f1f82beb748c0d544bd9a7b0b286462114e50a9e253b25e 1573 spotlighter_0.3-1.1.dsc e6d30392dbce530a7c7b159b7bec1113717935b2d21a60b8a4cd2f98d27a3ae7 4228 spotlighter_0.3-1.1.debian.tar.xz df498f1b64d7fb8b93850ab94a764b18c485bc8bf9c08ad72f39d0d6da98240a 30412 spotlighter_0.3-1.1_amd64.deb Files: 62541742b1323743e717f7974f1454df 30412 misc extra spotlighter_0.3-1.1_amd64.deb 71767429218dd947cd3f77f7a8b64202 1573 misc extra spotlighter_0.3-1.1.dsc 3d86425c3a744834b56a7a400a2d52b9 4228 misc extra spotlighter_0.3-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJT2LLwAAoJECVrfCskLhmeh5IIAK1GcfgGZhIKN+Vg9U53SLGF SL8uG1jDZpYHaUEK3gp0CQzYGmszlgH1tKoA7mYxf8CBtQU8jFoJBQwlrSNP25OD RUpHZnRHVeRXT3P+UDpDFPiCFczEH+usevcp14RKV8saP79JbbDn7pwnWovGLg5y N1AzVyplh86cVBzOjSE1I5nrh/mtBCVogUKhmvA+IG+AwYZE2wl3sDzwVuitvVmE 40fsLhW8R2GTSCMOM/ANphxSGbQun5M64FhR8GzBU6bpUatmvewqttgGKXmRmpMp hDvXD6vSzTD3UzlAWqPYHgpEela6kxURPXf+CxQdWZ7hVgW/xuN4gtU1qBNxQAk= =lhSe -END PGP SIGNATUREEnd Message---
Bug#752614: marked as done (smarty3 is licensed under the PHP license and is not PHP)
Your message dated Mon, 04 Aug 2014 19:49:03 + with message-id e1xeofj-0003pt...@franck.debian.org and subject line Bug#752614: fixed in smarty3 3.1.19-1 has caused the Debian Bug report #752614, regarding smarty3 is licensed under the PHP license and is not PHP 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.) -- 752614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: php-gearman Severity: serious User: paul...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks From the REJECT faq: / | You have a PHP add-on package (any php script/app/thing, not PHP | itself) and it's licensed only under the standard PHP license. That | license, up to the 3.x which is actually out, is not really usable for | anything else than PHP itself. I've mailed our -legal list about that | and got only one response, which basically supported my view on this. | Basically this license talks only about PHP, the PHP Group, and includes | Zend Engine, so its not applicable to anything else. And even worse, | older versions include the nice ad-clause. | | One good solution here is to suggest a license change to your upstream, | as they clearly wanted a free one. LGPL or BSD seems to be what they | want. \ Sorry this made it through NEW, Hope you're well, and thanks for your work, Paul -- .''`. Paul Tagliamonte paul...@debian.org : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: smarty3 Source-Version: 3.1.19-1 We believe that the bug you reported is fixed in the latest version of smarty3, 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 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel sunwea...@debian.org (supplier of updated smarty3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Aug 2014 21:32:20 +0200 Source: smarty3 Binary: smarty3 Architecture: source all Version: 3.1.19-1 Distribution: unstable Urgency: medium Maintainer: Mike Gabriel sunwea...@debian.org Changed-By: Mike Gabriel sunwea...@debian.org Description: smarty3- Template engine for PHP Closes: 752614 Changes: smarty3 (3.1.19-1) unstable; urgency=medium . * New upstream release. + Obtain upstream sources as zip files from upstream. Stop checking out SVN tags. This change drops three embedded PHP libraries and files with problematic PHP licenses. (Closes: #752614). * debian/control: + Alioth-canonicalize Vcs-Git field. + Bump Standards: to 3.9.5. No changes needed. * lintian: + Drop unused override: embedded-php-library. Checksums-Sha1: a7c9ed37d595b1175469f9c125ab064ed11f1216 1845 smarty3_3.1.19-1.dsc 35877c5c5cf58399ed5c781296a7bf797a74505b 207208 smarty3_3.1.19.orig.tar.gz 1b593e8cfc10505fd2aa308d80437ce9f4561647 3208 smarty3_3.1.19-1.debian.tar.xz 9914fecb89b26de22b34765b104a98de813f7960 164696 smarty3_3.1.19-1_all.deb Checksums-Sha256: 534ce94504ad10f8138cb1cbcd1a0fa1f3a987bf79135fd40942e165ee14e333 1845 smarty3_3.1.19-1.dsc 400462c48981ab95d875f43d8249e25cc413282285d9d21c6034ba487c34bc41 207208 smarty3_3.1.19.orig.tar.gz 4087aeea18444e0c9890bede334351e071e155939746e919d24370ad133ed3c5 3208 smarty3_3.1.19-1.debian.tar.xz 39ae9f3242cd83b44b4a30edfef13d9678a8df75e7c11bc584b4ca13c07d2c33 164696 smarty3_3.1.19-1_all.deb Files: 2a78b9ff250c41f253461a2502252b21 164696 web optional smarty3_3.1.19-1_all.deb 46d9b72f86bffe47c608ef57622f4210 1845 web optional smarty3_3.1.19-1.dsc e84fac37afd4363b1f929d236cd7de62 207208 web optional smarty3_3.1.19.orig.tar.gz ac14e4044596f1e88b876ded42ef8906 3208 web optional smarty3_3.1.19-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJT3+DeAAoJEJr0azAldxsxQrAP/2vNkh+knUlFV/70Q/Fds7O1 NawfIhpuXpDnzeqtgLKHgDlrwU4ScIwE7EUMQMQ0qLdWg5ZnY9SBNmC5PYiyKsAa uSsC6A48VJfUosH3U41E1rS3efe2Lky3VdDkDwNov/2bSD3aMgkD72mWVI5rXUxN
Processed: not quite fixed...
Processing commands for cont...@bugs.debian.org:
reopen 756914
Bug #756914 {Done: Felipe Sateler fsate...@debian.org} [src:pulseaudio]
pulseaudio: FTBFS on kfreebsd-*: portability issue
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pulseaudio/5.0-5.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
756914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756914
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#754758: musl: FTBFS on armhf: wrong asm instructions?
musl 1.1.4 was submitted some minutes ago, which will resolve all pending known issues. This will fix the bug described. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757044: gstreamer-vaapi: FTBFS: unsupported GStreamer API version 1.4
Source: gstreamer-vaapi Version: 0.5.8-1 Severity: serious Justification: fails to build from source Automatic builds of gstreamer-vaapi have been failing: checking for GStreamer API version... 1.4 configure: error: unsupported GStreamer API version 1.4 It's not immediately clear what the actual problem is, since I see no newer gstreamer in NEW, and the uploaded amd64 binaries just require libgstreamer1.0-0 (= 1.0.0). Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749835: marked as done (sandboxgamemaker: Please update to use wxwidgets3.0)
Your message dated Mon, 04 Aug 2014 21:42:48 + with message-id e1xeq1o-cn...@franck.debian.org and subject line Bug#749835: fixed in sandboxgamemaker 2.8.2+dfsg-1 has caused the Debian Bug report #749835, regarding sandboxgamemaker: Please update to use wxwidgets3.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.) -- 749835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sandboxgamemaker Version: 2.7.1+dfsg-2 Severity: serious Justification: Blocks an on-going transition User: freewx-ma...@lists.alioth.debian.org Usertags: wx3.0 Control: block 748169 by -1 Dear maintainer, We're aiming to migrate the archive to using wxwidgets3.0 instead of wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released. Many upstreams have already updated their code to be compatible with wx3.0. But if your package doesn't rebuild cleanly, you may find wx upstream's overview of changes since wx2.8 useful: http://docs.wxwidgets.org/3.0/overview_changes_since28.html One of the most common reasons for packages failing to build seems to be that wx3.0 drops compatibility with things which were deprecated in wx2.8 (so for example you now must use wxFD_SAVE not wxSAVE). Updating these should remain compatible with wx2.8, so shouldn't block pushing fixes upstream even if your upstream still cares about supporting wx2.8. Another thing to be aware of is that wx3.0 turns on WXDEBUG mode by default, and some applications throw up a lot of assertion failed dialogs due to using the wx API in invalid ways. If you compile your package with -DNDEBUG then such assertions aren't checked, and the same fallbacks which were quietly used in wx2.8 are used instead. If you hit any problems with getting packages working with wxwidgets3.0 which you can't overcome, let me know and I'll try to help. Cheers, Olly ---End Message--- ---BeginMessage--- Source: sandboxgamemaker Source-Version: 2.8.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of sandboxgamemaker, 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 749...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony F McInerney afm...@gmail.com (supplier of updated sandboxgamemaker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 01 Aug 2014 21:15:16 +0100 Source: sandboxgamemaker Binary: sandboxgamemaker Architecture: source amd64 Version: 2.8.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Anthony F McInerney afm...@gmail.com Changed-By: Anthony F McInerney afm...@gmail.com Description: sandboxgamemaker - 3D game maker and 3D game design program Closes: 694990 749835 Changes: sandboxgamemaker (2.8.2+dfsg-1) unstable; urgency=medium . * New maintainer upload (Closes: #694990) * New Upstream Release * New Depends on wxwidgets 3.0 (Closes: #749835) * Fixed vcs fields in control file * Removed empty useless files in debian folder * Removed comments from man/sandbox_unix.6 * Removed sandboxgamemaker.docs updated debian/copyright and README.debian * Removed debian/postrm debian/postinst - No longer installing non-free data with this package, so not required. Checksums-Sha1: a0c12fb4bcbbf9af210f185cda49139ba3a5fcc7 2065 sandboxgamemaker_2.8.2+dfsg-1.dsc f68864ef0a4b6192c6c27e80f54a18b5d4375248 1065446 sandboxgamemaker_2.8.2+dfsg.orig.tar.gz bfcc780c093e3487eb67ec3c414fabff8e794d7a 110460 sandboxgamemaker_2.8.2+dfsg-1.debian.tar.xz 4335a4f19b7ec91c50d34b494104072a1f094c37 2020660 sandboxgamemaker_2.8.2+dfsg-1_amd64.deb Checksums-Sha256: 08c22462a5d275307f7d9347b652cd2c38d285c6bfc8474350b46ed4b6504d65 2065 sandboxgamemaker_2.8.2+dfsg-1.dsc 9c3faa6cc6a3711dd88ae7a2d906d6ffd33881133ecadec83617781b971c0e12 1065446 sandboxgamemaker_2.8.2+dfsg.orig.tar.gz f76e500973afa573da06dac73d24a47df78e7d1461176dcfaaee5e597a49c42b 110460 sandboxgamemaker_2.8.2+dfsg-1.debian.tar.xz 75a1a700493b4dc939feb24713c4c71fda6b738a18f6641636a983e41496af83 2020660 sandboxgamemaker_2.8.2+dfsg-1_amd64.deb Files:
Bug#756790: marked as done (tcpdump: FTBFS on kfreebsd-*)
Your message dated Mon, 04 Aug 2014 21:43:21 + with message-id e1xeq2l-jw...@franck.debian.org and subject line Bug#756790: fixed in tcpdump 4.6.1-2 has caused the Debian Bug report #756790, regarding tcpdump: FTBFS on kfreebsd-* 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.) -- 756790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: tcpdump Version: 4.6.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) tcpdump failed to build on kfreebsd-* with: | gcc -ffloat-store -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FILE_OFFSET_BITS=64 -DHAVE_CONFIG_H -D_FORTIFY_SOURCE=2 -D_U_=__attribute__((unused)) -I. -I/usr/include -DINET6 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FILE_OFFSET_BITS=64 -o strlcat.o -c ./missing/strlcat.c | ./print-pflog.c:34:26: fatal error: net/if_pflog.h: No such file or directory | #include net/if_pflog.h | ^ | compilation terminated. Full build logs are available from https://buildd.debian.org/status/package.php?p=tcpdump. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: tcpdump Source-Version: 4.6.1-2 We believe that the bug you reported is fixed in the latest version of tcpdump, 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 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Romain Francoise rfranco...@debian.org (supplier of updated tcpdump package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Aug 2014 22:37:24 +0200 Source: tcpdump Binary: tcpdump Architecture: source Version: 4.6.1-2 Distribution: unstable Urgency: medium Maintainer: Romain Francoise rfranco...@debian.org Changed-By: Romain Francoise rfranco...@debian.org Description: tcpdump- command-line network traffic analyzer Closes: 756790 Changes: tcpdump (4.6.1-2) unstable; urgency=medium . * Expand configure check for net/pfvar.h to also check for existence of net/if_pflog.h to fix build on GNU/kFreeBSD, which ships the former but not the latter, see #756553 (closes: #756790). Checksums-Sha1: 801bc608651c261446f15c6db799481b6a1dad7c 1917 tcpdump_4.6.1-2.dsc 70d2d8d7a9bb4ef68038322a23b116806fafcd8d 11604 tcpdump_4.6.1-2.debian.tar.xz Checksums-Sha256: 19f45fd7ce150f29a20ed5226345446f39e6abfbd47478dd5d6cf5b6d11478ca 1917 tcpdump_4.6.1-2.dsc 71237fb9f3f79d4d0ab5fcf20135d6456d81a9656e77c483d89ee7bc4ade5ddb 11604 tcpdump_4.6.1-2.debian.tar.xz Files: 8c87d44e09ee2247869693e92026f63f 1917 net optional tcpdump_4.6.1-2.dsc 189a024ff6d7fd072dc99aa5967e37f1 11604 net optional tcpdump_4.6.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT3/A9AAoJEK0V9DXwX5YtofYQAM2uLEffIPCv/GFAmD946CFZ lG4aJN7l7l0d0KlQCdOc9GZAwnD8wJQ23lZpt8rgQHJBmUzhdrtmL4jVj995fB+i RUgxuvpwxNgulliYDEmNT8c5hMM01eHsFGs8J5ouWUY6xYUMZtic42cq4Whc+Tzj NGWCimXXYzOsoBw44D8fN+0wGVg6LNzUhfoj4oKhGtyI+LK5t88D3LIlDy9Jj4U9 VfywlIyiLP5XKiXTFsDbfQvOnHUu1Ng31EaIOt9t/pJfuKU/eoPXMu5+F+aZPubp RoLZX6M55t/lsjmJ/e+HDqbR+eNCxoCs7BcrOaW1aVMaC6XV/j6y4ggVqXbpKK+x PoknySWCmU5Ux2jGWPTXv/E7Wm4xCyXleISSYkh+o6vsT4KpuWuDw5xUDL96v1/y BGIsgaQTxa0zT5NSbyBnC3Uam6ZJLKo0icfloupwCmuNqhvvwNxJMdQH3T3de7Xe +Dh1X9koe5I0WhnnDBnKNXvhblcp+0ZFlmUvGRHtefvflVVLIW+GFFIp/DX8Pmue Zaa1++bCgetmXxd39eU6AWwIE27fhY6Ueo8C+azzV2xzjnKutmooWeEDB6FMFfPm YMJuIWNwPWnvYlD9LBS0cH9FvPUQLOiri/L9JDdClWMoi0xTW4qxZ088QyVRyc7A 3SJ84k2gMKqEFBt1OYU8 =//mv -END PGP SIGNATUREEnd Message---
Bug#757044: gstreamer-vaapi: FTBFS: unsupported GStreamer API version 1.4
On 04/08/14 23:24, Aaron M. Ucko wrote: Source: gstreamer-vaapi Version: 0.5.8-1 Severity: serious Justification: fails to build from source Automatic builds of gstreamer-vaapi have been failing: checking for GStreamer API version... 1.4 configure: error: unsupported GStreamer API version 1.4 It's not immediately clear what the actual problem is, since I see no newer gstreamer in NEW, and the uploaded amd64 binaries just require libgstreamer1.0-0 (= 1.0.0). Could you please take a look? I think it's pretty clear by looking at configure.ac: dnl Versions for GStreamer and plugins-base case $GST_API_VERSION in 0.10) GST_VERSION_REQUIRED=gst0_version GST_PLUGINS_BASE_VERSION_REQUIRED=gst0_plugins_base_version GST_PLUGINS_BAD_VERSION_REQUIRED=gst0_plugins_bad_version ;; 1.0) GST_VERSION_REQUIRED=gst1_version GST_PLUGINS_BASE_VERSION_REQUIRED=gst1_plugins_base_version GST_PLUGINS_BAD_VERSION_REQUIRED=gst1_plugins_bad_version ;; 1.2) GST_VERSION_REQUIRED=gst12_version GST_PLUGINS_BASE_VERSION_REQUIRED=gst12_plugins_base_version GST_PLUGINS_BAD_VERSION_REQUIRED=gst12_plugins_bad_version ;; 1.3) GST_VERSION_REQUIRED=gst14_version GST_PLUGINS_BASE_VERSION_REQUIRED=gst14_plugins_base_version GST_PLUGINS_BAD_VERSION_REQUIRED=gst14_plugins_bad_version ;; *) AC_MSG_ERROR([unsupported GStreamer API version $GST_API_VERSION]) ;; esac GStreamer is now at 1.4 so that fails. This probably just needs to change 1.3 with 1.4. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 756658 in 7.0.0+dfsg-1, found 756658 in 7.0.0+dfsg-2, found 756658 in 7.0.1+dfsg-1
Processing commands for cont...@bugs.debian.org: found 756658 7.0.0+dfsg-1 Bug #756658 [owncloud] owncloud: After migration from 6.0.4, database upgrade fail to find a table Marked as found in versions owncloud/7.0.0+dfsg-1. found 756658 7.0.0+dfsg-2 Bug #756658 [owncloud] owncloud: After migration from 6.0.4, database upgrade fail to find a table Marked as found in versions owncloud/7.0.0+dfsg-2. found 756658 7.0.1+dfsg-1 Bug #756658 [owncloud] owncloud: After migration from 6.0.4, database upgrade fail to find a table Marked as found in versions owncloud/7.0.1+dfsg-1. thanks Stopping processing here. Please contact me if you need assistance. -- 756658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756658 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#749002: marked as done (FTBFS: build-depends gnat, gnat-4.6)
Your message dated Tue, 05 Aug 2014 00:49:16 +0200 with message-id 53e00dec.4060...@debian.org and subject line fixed in 2013-1 has caused the Debian Bug report #749002, regarding FTBFS: build-depends gnat, gnat-4.6 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.) -- 749002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libflorist Version: 2011-2 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] W: no hooks of type D found -- ignoring - Attempting to parse the build-deps - Considering build-dep dpkg-dev (= 1.16.1) - Trying dpkg-dev - Considering build-dep debhelper (= 9) - Trying debhelper - Considering build-dep gnat - Trying gnat - Considering build-dep gnat-4.6 (= 4.6.4-2) - Trying gnat-4.6 - Cannot install gnat-4.6; apt errors follow: Reading package lists... Building dependency tree... Reading state information... dpkg-dev is already the newest version. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gnat : Depends: gnat-4.9 but it is not going to be installed E: Unable to correct problems, you have held broken packages. This is caused by the build dependency on both gnat and gnat-4.6: gnat depends on gnat-4.9, which replaces gnat 4.6.1. Best, Michael pgpSpTtZOZdb1.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Version: 2013-1---End Message---
Bug#757057: lack of depency on syslinux-stuff breaks extlinux on kernel upgrade
Package: extlinux Version: 3:6.03~pre18+dfsg-1 Severity: critical Dear extlinux maintainer(s), Having extlinux installed with no syslinux-stuff package causes system to not boot after kernel upgrade and subsequent removal of the previous kernel version. To achieve an ability to boot systems, extlinux relies on an extlinux-update utility which is now contained in syslinux-stuff package. And yet, extlinux does not depend on syslinux-stuff. Please add dependency on syslinux-stuff. (No, adding note in NEWS file is not solving the problem of silently leaving systems unbootable. Please add dependency on syslinux-stuff to the extlinux package.) Thanks in advance, Best regards – Miroslaw Baran -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (1000, 'stable'), (500, 'stable-updates'), (100, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-0.bpo.2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755311: marked as done (gnat-gps: FTBFS: LaTeX Errors)
Your message dated Tue, 05 Aug 2014 00:03:52 +
with message-id e1xesek-0005tw...@franck.debian.org
and subject line Bug#755311: fixed in gnat-gps 5.3-2.1
has caused the Debian Bug report #755311,
regarding gnat-gps: FTBFS: LaTeX Errors
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.)
--
755311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: gnat-gps
Version: 5.3-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140718 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»/docs/users_guide/_build/latex'
pdflatex 'GPS.tex'
This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014/Debian)
(preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./GPS.tex
LaTeX2e 2014/05/01
Babel 3.9k and hyphenation patterns for 2 languages loaded.
(./sphinxmanual.cls
Document Class: sphinxmanual 2009/06/02 Document class (Sphinx manual)
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
(/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/utf8.def
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.dfu)
(/usr/share/texlive/texmf-dist/tex/latex/base/ot1enc.dfu)
(/usr/share/texlive/texmf-dist/tex/latex/base/omsenc.dfu)))
! LaTeX Error: File `cmap.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.7 \usepackage
[T1]{fontenc}^^M
! == Fatal error occurred, no output PDF file produced!
Transcript written on GPS.log.
make[5]: *** [GPS.pdf] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/07/18/gnat-gps_5.3-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
---End Message---
---BeginMessage---
Source: gnat-gps
Source-Version: 5.3-2.1
We believe that the bug you reported is fixed in the latest version of
gnat-gps, 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 755...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated gnat-gps package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 05 Aug 2014 00:38:40 +0200
Source: gnat-gps
Binary: gnat-gps gnat-gps-dbg gnat-gps-doc gnat-gps-common
Architecture: source amd64 all
Version: 5.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Brenta lbre...@debian.org
Changed-By: Matthias Klose d...@debian.org
Description:
gnat-gps - integrated development environment for C and Ada
gnat-gps-common - integrated development environment for C and Ada (common
files)
gnat-gps-dbg - integrated development environment for C and Ada (debugging
symbo
gnat-gps-doc - integrated development environment for C and Ada (documentation)
Closes: 755311
Changes:
gnat-gps (5.3-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Build-depend on texlive-latex-recommended. Closes: #755311.
Checksums-Sha1:
fb36e4cc5a76bb1819c4cdf91179883d115ed39b 1905 gnat-gps_5.3-2.1.dsc
10fdd0670a38fa1686ee14ad772805fefe935364 21892 gnat-gps_5.3-2.1.debian.tar.bz2
4988d739408c888d1d4c0d7c6c8adf573c18191d 7978882 gnat-gps_5.3-2.1_amd64.deb
805b6c9b9c6160c9d68d6958d02a74d9cfe1bc7a 31522314
gnat-gps-dbg_5.3-2.1_amd64.deb
a605c87961e67623d877f9764c519c0b9031a877 9175362 gnat-gps-doc_5.3-2.1_all.deb
393767bb60fcb66bf85d14674cea27c14edaefaf 1415866
gnat-gps-common_5.3-2.1_all.deb
Bug#752974: xdotool: FTBFS - tests fail with EOFError: end of file reached
On 07/29/2014 03:51 AM, Petter Reinholdtsen wrote: Is this failing test related to bug #740419 (Unreliable testsuite)? i don't think so, unfortunately. the failures in 752974 are very reliable :P these newer failures appear to be related to the version of ruby that is running. Should the bugs be merged? If the test suite is unreliable, perhaps running it during build should be optional, or at least not fatal when it fail? I'm tempted to do this, since xdotool clearly is still working, and it's just the ruby framework that appears to be breaking :/ --dkg signature.asc Description: OpenPGP digital signature
Bug#757044: marked as done (gstreamer-vaapi: FTBFS: unsupported GStreamer API version 1.4)
Your message dated Mon, 4 Aug 2014 20:23:40 -0700 with message-id CACZd_tD=u4t_rnzffdcuwqf1gy-repnfqheycwuqhr1n5k+...@mail.gmail.com and subject line Re: gstreamer-vaapi: FTBFS: unsupported GStreamer API version 1.4 has caused the Debian Bug report #757044, regarding gstreamer-vaapi: FTBFS: unsupported GStreamer API version 1.4 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.) -- 757044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gstreamer-vaapi Version: 0.5.8-1 Severity: serious Justification: fails to build from source Automatic builds of gstreamer-vaapi have been failing: checking for GStreamer API version... 1.4 configure: error: unsupported GStreamer API version 1.4 It's not immediately clear what the actual problem is, since I see no newer gstreamer in NEW, and the uploaded amd64 binaries just require libgstreamer1.0-0 (= 1.0.0). Could you please take a look? Thanks! ---End Message--- ---BeginMessage--- Version: 0.5.9-1 On Mon, 04 Aug 2014 17:24:50 -0400 Aaron M. Ucko u...@debian.org wrote: Source: gstreamer-vaapi Version: 0.5.8-1 Severity: serious Justification: fails to build from source Automatic builds of gstreamer-vaapi have been failing: checking for GStreamer API version... 1.4 configure: error: unsupported GStreamer API version 1.4 It's not immediately clear what the actual problem is, since I see no newer gstreamer in NEW, and the uploaded amd64 binaries just require libgstreamer1.0-0 (= 1.0.0). Could you please take a look? Fixed in gstreamer-vaapi/0.5.9-1. It built fine when I first uploaded 0.5.8 to NEW a few months back, but while it was sitting in NEW a newer version of gstreamer got uploaded to the archive as well. Regards, Vincent---End Message---
Bug#756465: marked as done (maxima: Segmentation fault during startup)
Your message dated Tue, 05 Aug 2014 03:36:44 + with message-id e1xevyk-0006yb...@franck.debian.org and subject line Bug#756465: fixed in maxima 5.33.0-14 has caused the Debian Bug report #756465, regarding maxima: Segmentation fault during startup 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.) -- 756465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: maxima Version: 5.33.0-13 Severity: grave Justification: renders package unusable Dear Maintainer, when satrting up maxima I get a Segmentation fault straight away: cut -- jomo@mars [/home/jomo] maxima Unrecoverable error: Segmentation violation.. Segmentation fault jomo@mars [/home/jomo] cut -- gdb isn't showing useful information either as far as I can see: cut -- jomo@mars [/home/jomo] libdir=/usr/lib jomo@mars [/home/jomo] layout_autotools=true jomo@mars [/home/jomo] MAXIMA_DEFAULT_IMAGESDIR=/usr/lib/maxima/5.33.0 jomo@mars [/home/jomo] MAXIMA_IMAGESDIR=/usr/lib/maxima/5.33.0 jomo@mars [/home/jomo] MAXIMA_DEFAULT_LISP=gcl jomo@mars [/home/jomo] MAXIMA_LISP=gcl jomo@mars [/home/jomo] maxima_image_base=/usr/lib/maxima/5.33.0/binary-gcl/maxima jomo@mars [/home/jomo] gdb /usr/lib/maxima/5.33.0/binary-gcl/maxima GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/lib/maxima/5.33.0/binary-gcl/maxima...(no debugging symbols found)...done. (gdb) r Starting program: /usr/lib/maxima/5.33.0/binary-gcl/maxima warning: Could not load shared library symbols for linux-gate.so.1. Do you need set solib-search-path or set sysroot? Program received signal SIGSEGV, Segmentation fault. 0x000c367f in ?? () (gdb) where #0 0x000c367f in ?? () #1 0x000c8d22 in ?? () #2 0x000d6984 in ?? () #3 0x00020cc6 in ?? () #4 0x4b22aa63 in __libc_start_main (main=0x20c90, argc=1, argv=0xb4a4, init=0x31a0f0, fini=0x31a160, rtld_fini=0x4b1fcc90 _dl_fini, stack_end=0xb49c) at libc-start.c:287 #5 0x00021b4c in ?? () (gdb) cut -- And finally some valgrind output: cut -- jomo@mars [/home/jomo] valgrind /usr/lib/maxima/5.33.0/binary-gcl/maxima ==12381== Memcheck, a memory error detector ==12381== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==12381== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info ==12381== Command: /usr/lib/maxima/5.33.0/binary-gcl/maxima ==12381== --12381-- WARNING: Serious error when reading debug info --12381-- When reading debug info from /usr/lib/maxima/5.33.0/binary-gcl/maxima: --12381-- Can't make sense of .data section mapping ==12381== Syscall param rt_sigaction(act-sa_mask) points to uninitialised byte(s) ==12381==at 0x4B23F746: __libc_sigaction (sigaction.c:74) ==12381==by 0xC361B: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) ==12381==by 0xC8D21: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) ==12381==by 0x4B22AA62: (below main) (libc-start.c:287) ==12381== Address 0xbec2bf40 is on thread 1's stack ==12381== ==12381== Syscall param rt_sigaction(act-sa_mask) points to uninitialised byte(s) ==12381==at 0x4B23F746: __libc_sigaction (sigaction.c:74) ==12381==by 0xC3638: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) ==12381==by 0xC8D21: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) ==12381==by 0x4B22AA62: (below main) (libc-start.c:287) ==12381== Address 0xbec2bf40 is on thread 1's stack ==12381== ==12381== Invalid read of size 4 ==12381==at 0x4B274A4D: fflush (iofflush.c:40) ==12381==by 0xC8AC6: ??? (in /usr/lib/maxima/5.33.0/binary-gcl/maxima) ==12381== Address 0x403e0aa0 is not stack'd, malloc'd or (recently) free'd ==12381== ==12381== Can't extend stack to 0x658790 during signal delivery for thread 1: ==12381== no stack segment ==12381== ==12381== Process terminating with default action of signal 11 (SIGSEGV) ==12381== Access not within
Processed: fixed 756651 in 1.5.1-1
Processing commands for cont...@bugs.debian.org: fixed 756651 1.5.1-1 Bug #756651 [src:gpgme1.0] gpgme1.0: CVE-2014-3564: heap-based buffer overflow in gpgsm status handler Marked as fixed in versions gpgme1.0/1.5.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 756651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756651 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#751308: marked as done (ccbuild: non-standard gcc/g++ used for build (gcc-4.8))
Your message dated Tue, 05 Aug 2014 05:48:25 + with message-id e1xexbl-00055o...@franck.debian.org and subject line Bug#751308: fixed in ccbuild 2.0.6-3 has caused the Debian Bug report #751308, regarding ccbuild: non-standard gcc/g++ used for build (gcc-4.8) 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.) -- 751308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ccbuild Version: 2.0.6-2.1 Severity: important Tags: sid jessie User: debian-...@lists.debian.org Usertags: non-standard-compiler, gcc-4.7, gcc-4.7-legacy This package builds with a non standard compiler version; please check if this package can be built with the default version of gcc/g++, or with gcc-4.9/g++-4.9. Please drop build dependencies of the form libstdc++6-4.7-dev, these are not needed and fulfilled by build-essential. Please keep this report open until the package uses the default compiler version (or gcc-4.9) for the package build. The severity of this report is likely to be raised before the release, so that the gcc-4.7 package can be removed for the release. ---End Message--- ---BeginMessage--- Source: ccbuild Source-Version: 2.0.6-3 We believe that the bug you reported is fixed in the latest version of ccbuild, 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 751...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jari Aalto jari.aa...@cante.net (supplier of updated ccbuild 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: Mon, 04 Aug 2014 10:21:00 +0300 Source: ccbuild Binary: ccbuild Architecture: source amd64 Version: 2.0.6-3 Distribution: unstable Urgency: low Maintainer: Jari Aalto jari.aa...@cante.net Changed-By: Jari Aalto jari.aa...@cante.net Description: ccbuild- source scanning build utility for C++ Closes: 751308 Changes: ccbuild (2.0.6-3) unstable; urgency=low . * debian/control - (Build-Depends): Update from Freshmeat to Author's site. * debian/control and debian/rules - Drop explicit g++-4.8 build dependency and use default g++. (RC serious; Closes: #751308). * debian/copyright - Add Dimitri John Ledkov x...@ubuntu.com. * debian/watch - Fix typo in comment. Checksums-Sha1: 224d3b5f0011352b37c62f247243a68914bd5bd7 1955 ccbuild_2.0.6-3.dsc b48b958cfc72b814162752c366156a90adcd0743 5636 ccbuild_2.0.6-3.debian.tar.xz 4ab1a69ac923a964706fac94e80f9ef826768d15 151076 ccbuild_2.0.6-3_amd64.deb Checksums-Sha256: 68bc720257141001bd537d91d272d69a5403e31501921936ef4c5f5f01bc6d9d 1955 ccbuild_2.0.6-3.dsc 211e020a623a91a56b24f42f095f86bb5f34e85466b7f67aab3e92ba905d15ca 5636 ccbuild_2.0.6-3.debian.tar.xz fd3ee4b2ea673ed278ec05fbab9c5d22fbe9d349bb7340cd1c0864c5b7704936 151076 ccbuild_2.0.6-3_amd64.deb Files: e93e7623acefc96850d9802dd265057c 151076 devel optional ccbuild_2.0.6-3_amd64.deb b1fb36327f852144bbe0590997c2f3e5 1955 devel optional ccbuild_2.0.6-3.dsc 906daa59acf64401fca83b86122d69a7 5636 devel optional ccbuild_2.0.6-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT4G8bAAoJECHSBYmXSz6WYakP/1cexwVJsh1V41kcw2d99rgM ezECD+Hn5pFT12wqRz2jSskkxttHHa2kv3dzaemgEaOD9EvZu3/jIRtrE4t2u/ym TOakifQq+ibxJUllpK4XDRQH8Tsgk9lToCWI9RWzS3dmpSlGiwa0yIfc9t9CRO1W nlZSAAcGx5XDbuAdlCJgZjS+7ZG+ZZRx//Tk/b0mKdGjOj+mhR5kC05k+qGxtw4c +eztYq3fZ/kM3lnwhulTpKA6owbzZw7cq7JxkbLL4oWPEYyuXKjtuZ0NE9y3m2eH 2liwMDWjt4t3vgDKkoSSzLu2VrlZvSQ0cv1X9RleRWFQ8rEdRxkt+P4tpEYQscbx WDngxvCVsr2G8WBT+z/QE0n6Tg839tNWUdpAktYI8b7K/1Kcg2xd6RRXnY+8lPtY eLQDjISSfkT7L0IQqFcAJc7QY5/B7FbqUVJ/Y+TtGLcO2TSSE2u/T5uQ+O+XPZum SEReS6z+fUJGuzDqqfGC8ow6Ps5p/35R0cdIZ5dlVcSWb+3cm+DQdDiOr6N8WRcj NtXqKRadj79ZJOeeKOCp+mS/5f7GXrGQjCmC+QD5kWe1xevBqOUXXiLDD3E43QZo OvFkX34/yGNa0I0re+mp128e+HPDRczVpVKMJ39/D5WT0T7hM7BIs8sIT6DGg8Lp bmmIdEPLC12+pNPqPyfq =vDp0 -END PGP SIGNATUREEnd Message---
