Processed: tagging 767907
Processing commands for cont...@bugs.debian.org: > tags 767907 + patch Bug #767907 [libpcre3] too lax shlibs dependency? (newly added pcre_stack_guard needs >= 1:8.35) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 767907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767907 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#767907: too lax shlibs dependency? (newly added pcre_stack_guard needs >= 1:8.35)
Hello, What about the attached patch? BTW, while looking at libpcre3 package, I thought it would be a good idea to add a .symbols file and here is what I came up with (anyone could review it?): libpcre.so.3 libpcre3 #MINVER# pcre_assign_jit_stack@Base 1:8.30-4~ pcre_callout@Base 1:8.30-4~ pcre_compile2@Base 1:8.30-4~ pcre_compile@Base 1:8.30-4~ pcre_config@Base 1:8.30-4~ pcre_copy_named_substring@Base 1:8.30-4~ pcre_copy_substring@Base 1:8.30-4~ pcre_dfa_exec@Base 1:8.30-4~ pcre_exec@Base 1:8.30-4~ pcre_free@Base 1:8.30-4~ pcre_free_study@Base 1:8.30-4~ pcre_free_substring@Base 1:8.30-4~ pcre_free_substring_list@Base 1:8.30-4~ pcre_fullinfo@Base 1:8.30-4~ pcre_get_named_substring@Base 1:8.30-4~ pcre_get_stringnumber@Base 1:8.30-4~ pcre_get_stringtable_entries@Base 1:8.30-4~ pcre_get_substring@Base 1:8.30-4~ pcre_get_substring_list@Base 1:8.30-4~ pcre_info@Base 1:8.30-4~ pcre_jit_exec@Base 1:8.35 pcre_jit_free_unused_memory@Base 1:8.35 pcre_jit_stack_alloc@Base 1:8.30-4~ pcre_jit_stack_free@Base 1:8.30-4~ pcre_maketables@Base 1:8.30-4~ pcre_malloc@Base 1:8.30-4~ pcre_pattern_to_host_byte_order@Base 1:8.30-4~ pcre_refcount@Base 1:8.30-4~ pcre_stack_free@Base 1:8.30-4~ pcre_stack_guard@Base 1:8.35 pcre_stack_malloc@Base 1:8.30-4~ pcre_study@Base 1:8.30-4~ pcre_version@Base 1:8.30-4~ libpcreposix.so.3 libpcre3 #MINVER# pcreposix_regcomp@Base 1:8.30-4~ pcreposix_regerror@Base 1:8.30-4~ pcreposix_regexec@Base 1:8.30-4~ pcreposix_regfree@Base 1:8.30-4~ I don't think that could be considered for Jessie, but I think it would be worth asking anyway? Cheers, -- Arnaud Fontaine diff -urN pcre3-8.35.orig/debian/rules pcre3-8.35/debian/rules --- pcre3-8.35.orig/debian/rules 2014-11-20 16:04:51.630416683 +0900 +++ pcre3-8.35/debian/rules 2014-11-20 16:05:03.666453116 +0900 @@ -110,7 +110,7 @@ rm debian/libpcre3-dbg/usr/lib/debug/usr/lib/libpcre* dh_compress -a dh_fixperms -a - dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 8.10)' + dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 1:8.35)' dh_makeshlibs -plibpcrecpp0 -V 'libpcrecpp0 (>= 7.7)' dh_installdeb -a # dh_perl -a signature.asc Description: PGP signature
Bug#767903: mariadb-server-10.0: missing versioned dependency on libpcre3 >=1:8.35
tags 767903 - pending thanks > When sponsoring the upload, I didn't notice that the changes suggested > by Otto is not enough, my bad. debian/shlibs.local must be added to > really fix this bug. Preparing an upload now. After all, it would probably be much better to fix libpcre3 and then B-D on that fixed versions, instead of adding a workaround (eg d/shlibs.local). However, I'm not sure how to fix that properly for libpcre3, so I will ask on #767907 and debian-devel. Cheers, -- Arnaud Fontaine signature.asc Description: PGP signature
Processed: Re: mariadb-server-10.0: missing versioned dependency on libpcre3 >=1:8.35
Processing commands for cont...@bugs.debian.org: > tags 767903 - pending Bug #767903 [mariadb-server-10.0] mariadb-server-10.0: missing versioned dependency on libpcre3 >=1:8.35 Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 767903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768727: marked as done (t-code: FTBFS in jessie: build-dependency not installable: emacs23)
Your message dated Thu, 20 Nov 2014 06:34:32 + with message-id and subject line Bug#768727: fixed in t-code 2:2.3.1-3.5 has caused the Debian Bug report #768727, regarding t-code: FTBFS in jessie: build-dependency not installable: emacs23 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.) -- 768727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: t-code Version: 2:2.3.1-3.4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > ┌──┐ > │ Install t-code build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > 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: > sbuild-build-depends-t-code-dummy : Depends: emacs23 but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/t-code_2.3.1-3.4_jessie.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 --- --- Begin Message --- Source: t-code Source-Version: 2:2.3.1-3.5 We believe that the bug you reported is fixed in the latest version of t-code, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. HIGUCHI Daisuke (VDR dai) (supplier of updated t-code package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Nov 2014 14:57:57 +0900 Source: t-code Binary: t-code t-code-common Architecture: source all Version: 2:2.3.1-3.5 Distribution: unstable Urgency: medium Maintainer: NOSHIRO Shigeo Changed-By: HIGUCHI Daisuke (VDR dai) Description: t-code - Japanese direct input method environment for emacsen t-code-common - Japanese direct input method environment - common files Closes: 768239 768727 Changes: t-code (2:2.3.1-3.5) unstable; urgency=medium . * Non-maintainer upload. * debian/control - depends emacs24 instead of emacs23, emacs23 has been removed from jessie (Closes: #768727). * fix missing copyright file after upgrade (Closes: #768239). - debian/t-code.maintscript: new file. - debian/control: add Pre-Depends: dpkg (>= 1.17.5). Checksums-Sha1: deb8257883f2ccc1689f1d6f244a3ca287986429 2045 t-code_2.3.1-3.5.dsc 12d5def3537ef3c3da2f7714c3cd57997f6b53db 72968 t-code_2.3.1-3.5.debian.tar.xz d9a20a71f5ff26a48a2dfd9a6f041292a84f1910 118932 t-code_2.3.1-3.5_all.deb 6f5e0cf69698f45c7673af497f7b482c9f00b2e8 887006 t-code-common_2.3.1-3.5_all.deb Checksums-Sha256: a36a312ddb05f38c98b58467782be8cbdf325e6ad2d24fd412baff447f743d9d 2045 t-code_2.3.1-3.5.dsc f7912d66e4d1d91a9b66964c599019e3b7c72a05f8d4a52d513220588ba12911 72968 t-code_2.3.1-3.5.debian.tar.xz 249defe64f0ce3e04013feb9a880ccdcfb69fa7cda6bb0c3dbd511085ce679f9 118932 t-code_2.3.1-3.5_all.deb 16c1ca20e664e1afac035d2c716a49633ae380c95a663b7d91a5e60ff52716ed 887006 t-code-common_2.3.1-3.5_all.deb Files: cdf1cb31119c3650e9a3e71a2f9bdbd7 2045 utils optional t
Bug#768239: marked as done (t-code: copyright file missing after upgrade (policy 12.5))
Your message dated Thu, 20 Nov 2014 06:34:32 + with message-id and subject line Bug#768239: fixed in t-code 2:2.3.1-3.5 has caused the Debian Bug report #768239, regarding t-code: copyright file missing after upgrade (policy 12.5) 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.) -- 768239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: t-code Version: 2:2.3.1-3.4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. This was observed on the following upgrade paths: wheezy -> jessie >From the attached log (scroll to the bottom...): 1m58.0s ERROR: WARN: Inadequate results from running adequate! t-code: missing-copyright-file /usr/share/doc/t-code/copyright MISSING COPYRIGHT FILE: /usr/share/doc/t-code/copyright # ls -lad /usr/share/doc/t-code drwxr-xr-x 2 root root 40 Nov 2 15:19 /usr/share/doc/t-code # ls -la /usr/share/doc/t-code/ total 0 drwxr-xr-x 2 root root 40 Nov 2 15:19 . drwxr-xr-x 247 root root 5120 Nov 2 15:19 .. Additional info may be available here: http://wiki.debian.org/MissingCopyrightFile Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2) to perform the conversion, ideally using d/$PACKAGE.mainstscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. cheers, Andreas t-code_2:2.3.1-3.4.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: t-code Source-Version: 2:2.3.1-3.5 We believe that the bug you reported is fixed in the latest version of t-code, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. HIGUCHI Daisuke (VDR dai) (supplier of updated t-code package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 15 Nov 2014 14:57:57 +0900 Source: t-code Binary: t-code t-code-common Architecture: source all Version: 2:2.3.1-3.5 Distribution: unstable Urgency: medium Maintainer: NOSHIRO Shigeo Changed-By: HIGUCHI Daisuke (VDR dai) Description: t-code - Japanese direct input method environment for emacsen t-code-common - Japanese direct input method environment - common files Closes: 768239 768727 Changes: t-code (2:2.3.1-3.5) unstable; urgency=medium . * Non-maintainer upload. * debian/control - depends emacs24 instead of emacs23, emacs23 has been removed from jessie (Closes: #768727). * fix missing copyright file after upgrade (Closes: #768239). - debian/t-code.maintscript: new file. - debian/control: add Pre-Depends: dpkg (>= 1.17.5). Checksums-Sha1: deb8257883f2ccc1689f1d6f244a3ca287986429 2045 t-code_2.3.1-3.5.dsc 12d5def3537ef3c3da2f7714c3cd57997f6b53db 72968 t-code_2.3.1-3.5.debian.tar.xz d9a20a71f5ff26a48a2dfd9a6f041292a84f1910 118932 t-code_2.3.1-3.5_all.deb 6f5e0cf69698f45c7673af497f7b482c9f00b2e8 887006 t-code-common_2.3.1-3.5_all.deb Checksums-Sha256: a36a312ddb05f38c98b58467782be8cbdf325e6ad2d24fd412baff447f743d9d 2045 t-code_2.3.1-3.5.dsc f7912d66e4d1d91a9b66964c599019e3b7c72a05f8d4a52d513220588ba12911 72968 t-code_2.3.1-3.5.debian.tar.xz 249defe64f0ce3e04013feb9a880ccdcfb69fa7cda6bb0c3dbd511085ce679f9 118932 t-code_2.3.1-3.5_all.deb 16c1ca20e664e1afac035d2c716a49633ae380c95a663b7d91a5e60ff52716ed 887006 t-code-common_2.3.1-3.5_all.deb Files: cdf1cb31119c3650e9a3e71a2f9bdbd7 2045 utils optional t-code_2.3.1-3.5.dsc e41eaf253185db661491f9dbf27f36f0 72968 utils optional t-code_2.3.1-3.5.debian.tar.xz b2f
Bug#770226: [debhelper-devel] [Pkg-zsh-devel] Bug#770245: dh_installdeb: Using symlink_to_dir with relative symlinks needs ${misc:Pre-Depends} = dpkg >= 1.17.14
On 2014-11-20 01:17, Axel Beckert wrote:
> [...]
>
> Hi,
>
> [...]
>
> I could confirm that by downgrading dpkg from 1.17.21 to 1.17.13 and
> then installing zsh:
>
> [...]
>
Hi,
Thanks for testing and confirming the issue. :)
>> debhelper maintainers: Shall I clone or reassign this bug report to
>> debhelper for bumping ${misc:Pre-Depends} in such cases?
>
> I'm sure this should be fixed in debhelper's ${misc:Pre-Depends}, too,
> hence I cloned the bug report.
>
Ack.
> I'm just not sure if it should be generally bumped to dpkg >= 1.17.14
> or only in cases with relative symlinks.
>
The problem here is that debhelper do not know what is in the previous
version of a package. So we cannot do this conditionally.
> I'm also not sure if this is of RC severity for debhelper. Downgrading
> the clone to important for now. Feel free to raise it to RC severity
> again.
>
>> [...]
>
> Regards, Axel
>
If we do an upload for Jessie, I will probably just bump the
Pre-Depends. From a Wheezy -> Jessie upgrader, it should not matter if
it is >= 1.17.5 or >= 1.17.14 as they will not see a dpkg version
between 1.17.5 and 1.17.14.
~Niels
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770273: shadow (1:4.2-2+b2) no longer built with hardening flags
Package: shadow Version: 1:4.2-2+b2 Severity: serious Tags: patch It has been reported (but privately to me only) that the recent binNMU dropped the hardening flags for the shadow source package. A later analysis by Simon Ruderich mentioed this is related to cdbs and #712729. Simon provided a patch which I intend to apply in jessie, after seeking approval by the release team. - Forwarded message from "Dr. Markus Waldeck" - Date: Sun, 9 Nov 2014 14:27:36 +0100 From: "Dr. Markus Waldeck" To: Christian Perrier Cc: Simon Ruderich Subject: shadow (1:4.2-2+b2) X-CRM114-Status: UNSURE (-0.4308) This message is 'unsure'; please train it! Hi Christian, WHO triggered this "Binary-only non-maintainer upload for amd64"? It fucked up the correct applied hardening settings for shadow (1:4.2-2+b1) Thanks! Markus - End forwarded message - -- diff -Nru shadow-4.2/debian/control shadow-4.2/debian/control --- shadow-4.2/debian/control 2014-04-30 22:28:06.0 +0200 +++ shadow-4.2/debian/control 2014-11-10 13:30:34.0 +0100 @@ -5,6 +5,7 @@ Standards-Version: 3.9.5 Uploaders: Christian Perrier , Nicolas FRANCOIS (Nekral) Build-Depends: dh-autoreconf, gettext, libpam0g-dev, debhelper (>= 6.0.7~), quilt, dpkg-dev (>= 1.13.5), xsltproc, docbook-xsl, docbook-xml, libxml2-utils, cdbs, libselinux1-dev [linux-any], libsemanage1-dev [linux-any], gnome-doc-utils (>= 0.4.3), bison, libaudit-dev [linux-any] + ,hardening-wrapper Vcs-Git: git://anonscm.debian.org/git/pkg-shadow/shadow.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-shadow/shadow.git;a=summary Homepage: http://pkg-shadow.alioth.debian.org/ diff -Nru shadow-4.2/debian/rules shadow-4.2/debian/rules --- shadow-4.2/debian/rules 2014-04-30 22:28:06.0 +0200 +++ shadow-4.2/debian/rules 2014-11-10 13:30:34.0 +0100 @@ -3,6 +3,8 @@ DEB_HOST_ARCH_OS := $(shell dpkg-architecture -qDEB_HOST_ARCH_OS) +export DEB_BUILD_HARDENING=1 + # Enable PIE, BINDNOW, and possible future flags. export DEB_BUILD_MAINT_OPTIONS = hardening=+all signature.asc Description: Digital signature
Bug#768598: marked as done (fontconfig: cycle found while processing triggers)
Your message dated Thu, 20 Nov 2014 05:50:11 +0100 with message-id <20141120045011.ga31...@gaara.hadrons.org> and subject line Re: Bug#768598: NMUdiff for patch to fix this bug has caused the Debian Bug report #768598, regarding fontconfig: cycle found while processing triggers 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.) -- 768598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: font-config severity: serious x-debbugs-cc: debian-d...@lists.debian.org Hi, I'm not 100% sure the following issue is caused by font-config, please reassign appropriatly if it is not. https://jenkins.debian.net/job/chroot-installation_wheezy_install_education- desktop-kde_upgrade_to_jessie/2//console Setting up libgl1-mesa-glx:amd64 (10.3.2-1) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: fontconfig -> fontconfig packages' pending triggers which are or may be unresolvable: fontconfig: /usr/share/fonts shared-mime-info: /usr/share/mime/packages libc-bin: ldconfig gconf2: /usr/share/gconf/schemas dpkg: error processing package fontconfig (--configure): triggers looping, abandoned Setting up fontconfig-config (2.11.0-6.1) ... cheers, Holger signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Version: 2.11.0-6.2 Hi! On Mon, 2014-11-17 at 17:43:43 -0800, Don Armstrong wrote: > Control: tag -1 patch pending > > Below please find the NMU diff which fixes #768599 (from fontconfig's > end). This will still need Breaks in dpkg. I have uploaded this to > delayed/2. Please override with a maintainer upload if necessary. > diff -Nru fontconfig-2.11.0/debian/changelog > fontconfig-2.11.0/debian/changelog > --- fontconfig-2.11.0/debian/changelog2014-08-20 06:36:05.0 > -0700 > +++ fontconfig-2.11.0/debian/changelog2014-11-10 11:30:45.0 > -0800 > @@ -1,3 +1,13 @@ > +fontconfig (2.11.0-6.2) unstable; urgency=medium > + > + * Non-maintainer upload to delayed > + * Switch to noawait triggers to allow self-triggering; will still need > +Breaks from dpkg to resolve this (closes: #768599) > + * Add Pre-Depends on dpkg to allow for noawait just in case this gets > +backported to squeeze. > + > + -- Don Armstrong Mon, 10 Nov 2014 11:26:37 -0800 This got installed in the archive now, although the changelog had a typoed bug number so another bug report was closed. Doing so now with this mail. Thanks, Guillem--- End Message ---
Bug#768599: closed by Don Armstrong (Bug#768599: fixed in fontconfig 2.11.0-6.2)
Control: reopen -1 Control: notfixed -1 fontconfig/2.11.0-6.2 On Thu, 2014-11-20 at 03:21:19 +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the dpkg package: > > #768599: dpkg: Need to Break/Conflict packages switched to nonawaited trigger > directives > Format: 1.8 > Date: Mon, 10 Nov 2014 11:26:37 -0800 > Source: fontconfig […] > Closes: 768599 […] > Changes: > fontconfig (2.11.0-6.2) unstable; urgency=medium > . >* Non-maintainer upload to delayed >* Switch to noawait triggers to allow self-triggering; will still need > Breaks from dpkg to resolve this (closes: #768599) >* Add Pre-Depends on dpkg to allow for noawait just in case this gets > backported to squeeze. The bug number was typoed, it should have been #768598. Reopening and will be closing that one instead. Thanks, Guillem -- 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#768599 closed by Don Armstrong (Bug#768599: fixed in fontconfig 2.11.0-6.2)
Processing control commands:
> reopen -1
Bug #768599 {Done: Don Armstrong } [dpkg] dpkg: Need to
Break/Conflict packages switched to nonawaited trigger directives
Bug #766006 {Done: Don Armstrong } [dpkg] dpkg: cycle found
while processing triggers
Bug #768867 {Done: Don Armstrong } [dpkg] wheezy->jessie:
Sub-process /usr/bin/dpkg returned an error code (1)
'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 fontconfig/2.11.0-6.2.
No longer marked as fixed in versions fontconfig/2.11.0-6.2.
No longer marked as fixed in versions fontconfig/2.11.0-6.2.
> notfixed -1 fontconfig/2.11.0-6.2
Bug #768599 [dpkg] dpkg: Need to Break/Conflict packages switched to nonawaited
trigger directives
Bug #766006 [dpkg] dpkg: cycle found while processing triggers
Bug #768867 [dpkg] wheezy->jessie: Sub-process /usr/bin/dpkg returned an error
code (1)
Ignoring request to alter fixed versions of bug #768599 to the same values
previously set
Ignoring request to alter fixed versions of bug #766006 to the same values
previously set
Ignoring request to alter fixed versions of bug #768867 to the same values
previously set
--
766006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766006
768599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768599
768867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768867
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#770107: Bug#770270: unblock: dime/0.20111205-2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 See Bug#770270: unblock: dime/0.20111205-2 for my unblock request. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJUbW+PAAoJEFBB8YkfROCQ3jAP/jyCZifTQUSvmbBb21ngz5hI 7aqm12HFdDpAZsGWxr5z7H/xzv6FywpRHFfWVCPVqXKoFS0kyZmWt5Au3Z8rmDGJ PKIOB/cLIi0aVas8wGzJBVl+2IkNZqqU3Z/PRG5ZxOp5sJIacmsQCatWXsOR4U2i 1stuMWzuCb8SI6XTvDsdzVlb46QkAvEh3KUQ/H11Wli4mBsOP/jiZTtmj5B6t0K6 H0qNiTN39AhonJugHwlaFpwQk3S9Btkddf0MGge/eQMo7j5TULq6kCDydZRejREu w52rd4ETAr99GGewgOHQRRzhIHYZQQCS/HsazrexKgwv1QcIfrl/NjlarsRHU+OF kCSXKknBgRLgz19w2KROWMT9w3HOO8+A9gtNMyA4SpBiO0WnMWyqEWNY7rLRvW+4 AVQQN4cYrKuNRu1pxF7NTROyMCuJ5FhPTOUPMRUkwbl7Sxx6VhN1fo9QBP9RhZRq 2c46sb2qFgvYXFZjQtJV5m38l/yI3rl+LcGhkA7GJyOOhETBmu+eB74J60cnSYFr NvKtCxqcHPUMh08cwQ5DGy5cwNpUY4Snhc4ivecaiRhCav1u2U0khyxzjEamczsk B+GpQx57o4KpxUMM1eGbl5Uw/Q/BvgYXSsidXakQth6auvyxqkPDVf2B7f0PgcSm QlTw9SHkSd7n7Qdw2JIp =LWF7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770107: marked as done (libdime-dev must depends on libdime1)
Your message dated Thu, 20 Nov 2014 04:33:49 +
with message-id
and subject line Bug#770107: fixed in dime 0.20111205-2
has caused the Debian Bug report #770107,
regarding libdime-dev must depends on libdime1
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.)
--
770107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdime-dev
Version: 0.20111205-1
Severity: grave
Justification: renders package unusable
In the control file of the package, the libdime-dev entry is as follows:
Package: libdime-dev
Section: libdevel
Architecture: any
Depends: ${misc:Depends}
and it should be:
Package: libdime-dev
Section: libdevel
Architecture: any
Depends: libdime1 (= ${binary:Version}), ${misc:Depends}
the result of the missing dependency is that the package has not shared
library to link, because one user could simply do a:
apt-get install libdime-dev and no binary lib is installed. So, the package
is not usable.
Please, solve it.
Best regards,
Leopold
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dime
Source-Version: 0.20111205-2
We believe that the bug you reported is fixed in the latest version of
dime, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 770...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
A. Maitland Bottoms (supplier of updated dime 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, 19 Nov 2014 22:41:36 -0500
Source: dime
Binary: dime libdime1 libdime-dev libdime-doc
Architecture: source amd64 all
Version: 0.20111205-2
Distribution: unstable
Urgency: low
Maintainer: A. Maitland Bottoms
Changed-By: A. Maitland Bottoms
Description:
dime - DXF Import, Manipulation, and Export programs
libdime-dev - DXF Import, Manipulation, and Export library - devel
libdime-doc - DXF Import, Manipulation, and Export library - devel
libdime1 - DXF Import, Manipulation, and Export library
Closes: 770107
Changes:
dime (0.20111205-2) unstable; urgency=low
.
* Add libdime-dev dependency on libdime1 (Closes: #770107)
* Add ${shlibs:Depends} to dime package
* install dxf2vmrl and dxfsphere binaries into the dime package
Checksums-Sha1:
22a0d38ea6438943b5df8c99389e9a6ee3e39397 1938 dime_0.20111205-2.dsc
55c028aa88ef8940dc7e822996a007b0c49743de 42760 dime_0.20111205-2.debian.tar.xz
4cd26922ed0a2ea0c4b792808e13870476e735e1 13522 dime_0.20111205-2_amd64.deb
bd5fb61bcef665f712750194f0a68c710b65f908 98948 libdime1_0.20111205-2_amd64.deb
e1b610fe26a45fb5225e84d3abf0717a3dd81e9b 24204
libdime-dev_0.20111205-2_amd64.deb
b8a9dcf4cb0f9baef87ade9bc36d0a7d3cbdfe10 255704
libdime-doc_0.20111205-2_all.deb
Checksums-Sha256:
51632820c0bec1f0828218f206a67052944c4db3895dd90bb5e19296b8c8b2b8 1938
dime_0.20111205-2.dsc
134c4317ec32aa8e546a5663826a2c99c7e5bbd0f5e4dddb4d799d8b4f5df88c 42760
dime_0.20111205-2.debian.tar.xz
5272c0ba030e0ba4fc3637b81781a283e27e80987073f1334f8cf687fd00d822 13522
dime_0.20111205-2_amd64.deb
44e9e9f9d0bf71b3a08bf9b3dcf61a6ebf80e989ad8cb6dcc3dc2c6b784ce3c6 98948
libdime1_0.20111205-2_amd64.deb
31a888abf59aee5543e25e1b1e65177230d27d9cb8d013cac2bdd932530f1b93 24204
libdime-dev_0.20111205-2_amd64.deb
d037ef706478380b80b60351f8050a519e7cbf30488917b8c9a66c7232ffe24d 255704
libdime-doc_0.20111205-2_all.deb
Files:
5c2360f5245b0f74a492de3a18d8d334 1938 graphics optional dime_0.20111205-2.dsc
9ac1f33220f7909c6e4c393441951a4e 42760 graphics optional
dime_0.20111205-2.debian.tar.xz
498937ffaddcca75bf81c3202919d884 13522 graphics optional
dime_0.20111205-2_amd64.deb
d10b401fc3a6fe3d72f0d3e1b43ce9b3 98948 libs optional
libdime1_0.20111205-2_amd64.deb
50f60e28e528f6e7739482fd29b0a392 24204 libdevel optional
libdime-dev_0.20111205-2_amd64.deb
4b99b93b7850b19100
Bug#770107: libdime-dev must depends on libdime1
There's more wrong with dime 0.20111205-1
Some libtool wrappers were installed into /usr/bin/dxf2vrml
and /usr/bin/dxf2sphere in the dime binary package - rather
then the correct compiled ELF binary executables. Therefore,
the dime package did not depend upon the libdime1 library
package either.
Correctly installing the dxf2vrml and dxf2sphere binaries
in the dime package, along with adding ${shlibs:Depends},
results in a dime package correctly depending upon libdime1
as well.
The Debian packaged view3dscene verifies the correct
operation of the dime package by displaying a sphere
made by dxfsphere converted to vrml by dxf2vrml.
(I had not done this verification step before uploading
dime 0.20111205-1)
Expect a dime 0.20111205-2 upload soon, followed by an
unblock request for Jessie.
-Maitland
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768599: marked as done (dpkg: Need to Break/Conflict packages switched to nonawaited trigger directives)
Your message dated Thu, 20 Nov 2014 03:19:14 + with message-id and subject line Bug#768599: fixed in fontconfig 2.11.0-6.2 has caused the Debian Bug report #768599, regarding dpkg: Need to Break/Conflict packages switched to nonawaited trigger directives 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.) -- 768599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: man-db severity: serious x-debbugs-cc: debian-d...@lists.debian.org Hi, I'm not 100% sure the following issue is caused by man-db, please reassign appropriatly if it is not. https://jenkins.debian.net/job/chroot-installation_wheezy_install_education- networked_upgrade_to_jessie/2/console Setting up startpar (0.59-3) ... Installing new version of config file /etc/init/startpar-bridge.conf ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: man-db -> man-db packages' pending triggers which are or may be unresolvable: man-db: /usr/share/man dpkg: error processing package man-db (--configure): triggers looping, abandoned Setting up sysvinit-utils (2.88dsf-57) ... Errors were encountered while processing: man-db E: Sub-process /usr/bin/dpkg returned an error code (1) cheers, Holger signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: fontconfig Source-Version: 2.11.0-6.2 We believe that the bug you reported is fixed in the latest version of fontconfig, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Don Armstrong (supplier of updated fontconfig 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, 10 Nov 2014 11:26:37 -0800 Source: fontconfig Binary: fontconfig fontconfig-config fontconfig-udeb libfontconfig1-dev libfontconfig1 libfontconfig1-dbg Architecture: source all amd64 Version: 2.11.0-6.2 Distribution: sid Urgency: medium Maintainer: Keith Packard Changed-By: Don Armstrong Description: fontconfig - generic font configuration library - support binaries fontconfig-config - generic font configuration library - configuration fontconfig-udeb - generic font configuration library - minimal runtime (udeb) libfontconfig1 - generic font configuration library - runtime libfontconfig1-dbg - generic font configuration library - debugging symbols libfontconfig1-dev - generic font configuration library - development Closes: 768599 Changes: fontconfig (2.11.0-6.2) unstable; urgency=medium . * Non-maintainer upload to delayed * Switch to noawait triggers to allow self-triggering; will still need Breaks from dpkg to resolve this (closes: #768599) * Add Pre-Depends on dpkg to allow for noawait just in case this gets backported to squeeze. Checksums-Sha1: 524066727473a721ccd40a4058206f4d35afb135 2199 fontconfig_2.11.0-6.2.dsc 27e9e1cc8626741cbf2383e6901bf15b3ef1b312 1072028 fontconfig_2.11.0-6.2.debian.tar.xz 48965d54e96cbc989f4348e8b98463ef600b9686 273314 fontconfig-config_2.11.0-6.2_all.deb 80727ed2a5709b41da26a80f721d376cfcc2d0ef 328586 libfontconfig1_2.11.0-6.2_amd64.deb 4b0259d77f70355cdc341dc21dfabd3ef31fa635 402718 fontconfig_2.11.0-6.2_amd64.deb eb3ebe64117ee5cbe6f0dbbdd7e7f20fc9771cd2 111438 fontconfig-udeb_2.11.0-6.2_amd64.udeb b2e942c9284b55f5afb73f19553c8aa454924ea9 893864 libfontconfig1-dev_2.11.0-6.2_amd64.deb 6aee5e2b9a91f5aa4825dcb952695886c29c1ec8 512294 libfontconfig1-dbg_2.11.0-6.2_amd64.deb Checksums-Sha256: 8a6b63f586f28928b5229a482875db9e840ae15be9db37d77ad1a0028d17590a 2199 fontconfig_2.11.0-6.2.dsc f76a3360a3ebb5408c97a98eba5651f2e9ec76b09ee623f480e0349de9d2e0ea 1072028 fontconfig_2.11.0-6.2.debian.tar.xz 132b621141bf65e359f4bab06a9cbe7cda3f0997efda395f56cc1eea0cebf17e 273314 fontconfig-config_2.11.0-6.2_all.deb 3a3ccb4591cb157644f965367a5e45cc64c041314168258bfa65170d02c9d3de 328586 libfontconfig1_2.11.0-6.2_amd64.deb 088d8312cf661cd17d55872abd95168c5fd7337e3e58221212dd3cbbbe023ffd 402718 fontconfig_2.11.0-6.2_a
Bug#766006: marked as done (dpkg: cycle found while processing triggers)
Your message dated Thu, 20 Nov 2014 03:19:14 + with message-id and subject line Bug#768599: fixed in fontconfig 2.11.0-6.2 has caused the Debian Bug report #768599, regarding dpkg: cycle found while processing triggers 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.) -- 768599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: man-db Version: 2.7.0.2-2 Severity: normal Hi everyone, after some time away from my computer I did the usual aptitude upgrade routine (text gui, Shift-u, g), which ended in a message I have never seen before: - dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: man-db -> mime-support packages' pending triggers which are or may be unresolvable: man-db: /usr/share/man menu: /usr/share/menu desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package man-db (--unpack): triggers looping, abandoned - I am not sure who is the responsible here, so please reassign if appropriate. Remark: After restarting the installation process, dpkg seemed to have been successful. Thanks a lot Norbert -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages man-db depends on: ii bsdmainutils 9.0.6 ii debconf [debconf-2.0] 1.5.53 ii dpkg 1.17.18 ii groff-base 1.22.2-8 ii libc6 2.19-11 ii libgdbm3 1.8.3-13 ii libpipeline1 1.3.1-1 ii zlib1g 1:1.2.8.dfsg-2 man-db recommends no packages. Versions of packages man-db suggests: ii chromium [www-browser] 38.0.2125.101-2 ii groff 1.22.2-8 ii iceweasel [www-browser]31.1.0esr-1 ii less 458-3 ii lynx-cur [www-browser] 2.8.9dev1-2 ii netsurf-gtk [www-browser] 3.2+dfsg-2 ii w3m [www-browser] 0.5.3-17 -- debconf information: man-db/auto-update: true * man-db/install-setuid: true --- End Message --- --- Begin Message --- Source: fontconfig Source-Version: 2.11.0-6.2 We believe that the bug you reported is fixed in the latest version of fontconfig, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Don Armstrong (supplier of updated fontconfig 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, 10 Nov 2014 11:26:37 -0800 Source: fontconfig Binary: fontconfig fontconfig-config fontconfig-udeb libfontconfig1-dev libfontconfig1 libfontconfig1-dbg Architecture: source all amd64 Version: 2.11.0-6.2 Distribution: sid Urgency: medium Maintainer: Keith Packard Changed-By: Don Armstrong Description: fontconfig - generic font configuration library - support binaries fontconfig-config - generic font configuration library - configuration fontconfig-udeb - generic font configuration library - minimal runtime (udeb) libfontconfig1 - generic font configuration library - runtime libfontconfig1-dbg - generic font configuration library - debugging symbols libfontconfig1-dev - generic font configuration library - development Closes: 768599 Changes: fontconfig (2.11.0-6.2) unstable; urgency=medium . * Non-maintainer upload to delayed * Switch to noawait triggers to allow self-triggering; will still need Breaks from dpkg to resolve this (closes: #768599) * Add Pre-Depends on dpkg to allow for noawait just in case this gets backported to squeeze. Checksums-Sha1: 524066727473a721ccd40a4058206f4d35afb135 2199 fontconfig_2.11.0-6.2.dsc 27e9e1cc8626741cbf2383e6901bf15b3ef1b312 1072028 fontconfig_2.11.0-6.2.debian.tar.xz 48965d54e96cbc989f4348e8b98463ef600b9686 273314 fontconfig-config_2.11.0-6.2_all.deb 80727ed2a5709b41da26a80f721
Bug#768867: marked as done (wheezy->jessie: Sub-process /usr/bin/dpkg returned an error code (1))
Your message dated Thu, 20 Nov 2014 03:19:14 + with message-id and subject line Bug#768599: fixed in fontconfig 2.11.0-6.2 has caused the Debian Bug report #768599, regarding wheezy->jessie: Sub-process /usr/bin/dpkg returned an error code (1) 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.) -- 768599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: upgrade-reports Severity: critical Justification: breaks unrelated software My previous release is: wheezy I am upgrading to: jessie Archive date: Sun Nov 9 15:38:19 UTC 2014 (from ftp.at.debian.org) uname -a before upgrade: Linux cimaster 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux Method: apt-get dist-upgrade # cat /etc/apt/sources.list.d/* | egrep -v '^#' deb http://jenkins.grml.org/debian jenkins-debian-glue main deb-src http://jenkins.grml.org/debian jenkins-debian-glue main deb http://pkg.jenkins-ci.org/debian binary/ deb http://apt.puppetlabs.com wheezy main dependencies deb-src http://apt.puppetlabs.com wheezy main dependencies deb http://ftp.at.debian.org/debian jessie main non-free contrib deb-src http://ftp.at.debian.org/debian jessie main non-free contrib dpkg exited, but did not give any useful explanation why. Upgrade log: root@cimaster:~# apt-get install apt dpkg Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: bind9-host cowbuilder cowdancer debootstrap devscripts diffstat dpkg-dev gettext libaccess-bridge-java libaccess-bridge-java-jni libcroco3 libdpkg-perl libfont-freetype-perl libfontenc1 libgettextpo0 libgomp1 libunistring0 libxfont1 pbuilder quilt xfonts-encodings xfonts-utils Use 'apt-get autoremove' to remove them. The following extra packages will be installed: gcc-4.9-base libapt-inst1.5 libapt-pkg4.12 libc6 libselinux1 libstdc++6 locales Suggested packages: apt-doc glibc-doc The following NEW packages will be installed: gcc-4.9-base The following packages will be upgraded: apt dpkg libapt-inst1.5 libapt-pkg4.12 libc6 libselinux1 libstdc++6 locales 8 upgraded, 1 newly installed, 0 to remove and 375 not upgraded. Need to get 14.1 MB of archives. After this operation, 3313 kB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://ftp.at.debian.org/debian/ jessie/main locales all 2.19-12 [3916 kB] Get:2 http://ftp.at.debian.org/debian/ jessie/main libc6 amd64 2.19-12 [4818 kB] Get:3 http://ftp.at.debian.org/debian/ jessie/main libselinux1 amd64 2.3-2 [89.8 kB] Get:4 http://ftp.at.debian.org/debian/ jessie/main dpkg amd64 1.17.21 [2843 kB] Get:5 http://ftp.at.debian.org/debian/ jessie/main gcc-4.9-base amd64 4.9.1-19 [158 kB] Get:6 http://ftp.at.debian.org/debian/ jessie/main libstdc++6 amd64 4.9.1-19 [273 kB] Get:7 http://ftp.at.debian.org/debian/ jessie/main libapt-inst1.5 amd64 1.0.9.3 [168 kB] Get:8 http://ftp.at.debian.org/debian/ jessie/main libapt-pkg4.12 amd64 1.0.9.3 [780 kB] Get:9 http://ftp.at.debian.org/debian/ jessie/main apt amd64 1.0.9.3 [1100 kB] Fetched 14.1 MB in 1s (11.1 MB/s) Preconfiguring packages ... (Reading database ... 34358 files and directories currently installed.) Preparing to replace locales 2.13-38+deb7u6 (using .../locales_2.19-12_all.deb) ... Unpacking replacement locales ... Preparing to replace libc6:amd64 2.13-38+deb7u6 (using .../libc6_2.19-12_amd64.deb) ... Checking for services that may need to be restarted... Checking init scripts... Unpacking replacement libc6:amd64 ... Processing triggers for man-db ... Setting up libc6:amd64 (2.19-12) ... Checking for services that may need to be restarted... Checking init scripts... Restarting services possibly affected by the upgrade: cron: restarting...done. Services restarted successfully. (Reading database ... 34404 files and directories currently installed.) Preparing to replace libselinux1:amd64 2.1.9-5 (using .../libselinux1_2.3-2_amd64.deb) ... Unpacking replacement libselinux1:amd64 ... Setting up libselinux1:amd64 (2.3-2) ... (Reading database ... 34402 files and directories currently installed.) Preparing to replace dpkg 1.16.15 (using .../dpkg_1.17.21_amd64.deb) ... Unpacking replacement dpkg ... Processing triggers for man-db ... Setting up dpkg (1.17.21) ... Installing new version of config file /etc/cron.daily/dpkg ... Selecting previously unselected package gcc-4.9-base:amd64. (Reading database ... 34388 files and directories currently installed.) Prepar
Bug#770130: gnome-shell: Oh no! Something has gone wrong. (Fujitsu ST4121)
On Wed, 2014-11-19 at 12:00 +0100, intrigeri wrote:
> Looks like a bug in the kernel DRM drivers to me (or might be in Mesa,
> or in Cogl, or in the X.Org driver, I'm definitely no expert in this
> field).
>
> > Kernel: Linux 3.18.0-rc5 (SMP w/1 CPU core)
>
> Can you reproduce this bug with a kernel that we ship in Debian,
> e.g. current sid's 3.16 or experimental's 3.17?
Yes, same as mainline kernel.
$ uname -srvp
Linux 3.16.0-4-686-pae #1 SMP Debian 3.16.7-2 (2014-11-06) unknown
# BEGIN patch cogl-1.18.2/debian/patches/000_cogldebug.patch
Index: cogl-1.18.2/cogl/driver/gl/cogl-texture-2d-gl.c
===
--- cogl-1.18.2.orig/cogl/driver/gl/cogl-texture-2d-gl.c
+++ cogl-1.18.2/cogl/driver/gl/cogl-texture-2d-gl.c
@@ -35,6 +35,7 @@
#include
#include
+#include
#include "cogl-private.h"
#include "cogl-texture-private.h"
@@ -127,11 +128,22 @@ allocate_with_size (CoglTexture2D *tex_2
height,
internal_format))
{
+/*
_cogl_set_error (error, COGL_TEXTURE_ERROR,
COGL_TEXTURE_ERROR_SIZE,
"Failed to create texture 2d due to size/format"
" constraints");
return FALSE;
+*/
+ syslog(LOG_ERR, "COGL ERROR: allocate_with_size "
+ "ctx %lx, WxH %i x %i, ifmt %i\n",
+ (long unsigned int)ctx, width, height, internal_format);
+}
+else
+{
+ syslog(LOG_INFO, "COGL INFO: allocate_with_size "
+ "ctx %lx, WxH %i x %i, ifmt %i\n",
+ (long unsigned int)ctx, width, height, internal_format);
}
ctx->driver_vtable->pixel_format_to_gl (ctx,
@@ -196,11 +208,22 @@ allocate_from_bitmap (CoglTexture2D *tex
height,
internal_format))
{
+/*
_cogl_set_error (error, COGL_TEXTURE_ERROR,
COGL_TEXTURE_ERROR_SIZE,
"Failed to create texture 2d due to size/format"
" constraints");
return FALSE;
+*/
+ syslog(LOG_ERR, "COGL ERROR: allocate_from_bitmap "
+ "ctx %lx, WxH %i x %i, ifmt %i\n",
+ (long unsigned int)ctx, width, height, internal_format);
+}
+else
+{
+ syslog(LOG_INFO, "COGL INFO: allocate_from_bitmap "
+ "ctx %lx, WxH %i x %i, ifmt %i\n",
+ (long unsigned int)ctx, width, height, internal_format);
}
upload_bmp = _cogl_bitmap_convert_for_upload (bmp,
# END patch cogl-1.18.2/debian/patches/000_cogldebug.patch
# BEGIN journalctl output
-- Logs begin at Wed 2014-11-19 15:48:15 PST, end at Wed 2014-11-19 15:59:19
PST. --
Nov 19 15:58:29 boss gnome-shell[985]: COGL INFO: allocate_with_size ctx
9eaf6a0, WxH 46 x 30, ifmt 147
Nov 19 15:58:29 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 48 x 32, ifmt 17
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 64 x 64, ifmt 147
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 16 x 16, ifmt 147
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 48 x 48, ifmt 147
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 16 x 16, ifmt 147
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 16 x 16, ifmt 147
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 48 x 48, ifmt 147
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 24 x 24, ifmt 147
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 16 x 16, ifmt 147
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 64 x 64, ifmt 147
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_with_size ctx
9eaf6a0, WxH 46 x 30, ifmt 147
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 48 x 32, ifmt 17
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 10 x 10, ifmt 179
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 337 x 34, ifmt 179
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 10 x 10, ifmt 179
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 82 x 29, ifmt 179
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 10 x 10, ifmt 179
Nov 19 15:58:31 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 83 x 29, ifmt 179
Nov 19 15:58:32 boss gnome-shell[985]: COGL INFO: allocate_from_bitmap ctx
9eaf6a0, WxH 18 x 18, ifmt 147
Nov 19 15:58:33 boss gnome-shell[985]: COGL INFO: al
Bug#770261: python-pies: Rebuilding from source gives nearly empty python3-pies
Source: python-pies Version: 2.6.1-1 Severity: serious After I build python-pies using pbuilder, listing the contents of python3-pies gives: daniel@frobozz:/var/cache/pbuilder/result$ dpkg-deb -c python3-pies_2.6.1-1_all.deb drwxr-xr-x root/root 0 2014-11-19 18:45 ./ drwxr-xr-x root/root 0 2014-11-19 18:45 ./usr/ drwxr-xr-x root/root 0 2014-11-19 18:45 ./usr/lib/ drwxr-xr-x root/root 0 2014-11-19 18:45 ./usr/share/ drwxr-xr-x root/root 0 2014-11-19 18:45 ./usr/share/doc/ drwxr-xr-x root/root 0 2014-11-19 18:45 ./usr/share/doc/python3-pies/ -rw-r--r-- root/root 2044 2014-02-24 02:57 ./usr/share/doc/python3-pies/README.md.gz -rw-r--r-- root/root 159 2014-05-21 02:47 ./usr/share/doc/python3-pies/changelog.Debian.gz -rw-r--r-- root/root 1371 2014-02-15 16:10 ./usr/share/doc/python3-pies/copyright I noticed this because then, trying to rebuild src:frosted using this package gave test failures. -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770259: eglibc: FTBFS: These critical programs are missing or too old: make
Source: eglibc Version: 2.17-97 Severity: serious >From my pbuilder build log: ... checking for ld... ld checking version of ld... 2.24.90, ok checking for x86_64-linux-gnu-gcc... (cached) x86_64-linux-gnu-gcc-4.7 checking version of x86_64-linux-gnu-gcc-4.7... 4.7.4, ok checking for gnumake... no checking for gmake... no checking for make... make checking version of make... 4.0, bad checking for gnumsgfmt... no checking for gmsgfmt... no checking for msgfmt... msgfmt checking version of msgfmt... 0.19.3, ok checking for makeinfo... : checking version of :... v. ?.??, bad checking for sed... sed checking version of sed... 4.2.2, ok checking for gawk... gawk checking version of gawk... 4.1.1, ok checking for x86_64-linux-gnu-nm... x86_64-linux-gnu-nm checking for autoconf... false checking whether false works... no configure: error: *** These critical programs are missing or too old: make *** Check the INSTALL file for required versions. debian/rules.d/build.mk:31: recipe for target '/tmp/buildd/eglibc-2.17/stamp-dir/configure_libc' failed make: *** [/tmp/buildd/eglibc-2.17/stamp-dir/configure_libc] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Given that src:eglibc is pretty much obsoleted by src:glibc now, I'd guess the easiest way to fix this would be to just request the removal of src:eglibc from sid. -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 770226
Processing commands for cont...@bugs.debian.org: > # A potential fix has been pushed into the git repository > tags 770226 + pending Bug #770226 [zsh-common] zsh-common: installation fails with "dpkg-maintscript-helper: error: original symlink target is not an absolute path" Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 770226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770226 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#770254: manpages-pl: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/man/pl/man1/realpath.1.gz
Package: manpages-pl Version: 1:0.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package manpages-pl. Unpacking manpages-pl (from .../manpages-pl_1%3a0.6-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/manpages-pl_1%3a0.6-1_all.deb (--unpack): trying to overwrite '/usr/share/man/pl/man1/realpath.1.gz', which is also in package realpath 1.18 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/manpages-pl_1%3a0.6-1_all.deb cheers, Andreas realpath=1.18_manpages-pl=1%0.6-1.log.gz Description: application/gzip
Bug#768754: marked as done (backbone: FTBFS in jessie: build-dependency not installable: phantomjs)
Your message dated Thu, 20 Nov 2014 01:33:53 + with message-id and subject line Bug#768754: fixed in backbone 0.9.10-3 has caused the Debian Bug report #768754, regarding backbone: FTBFS in jessie: build-dependency not installable: phantomjs 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.) -- 768754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: backbone Version: 0.9.10-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > ┌──┐ > │ Install backbone build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > 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: > sbuild-build-depends-backbone-dummy : Depends: phantomjs but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/backbone_0.9.10-1_jessie.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 --- --- Begin Message --- Source: backbone Source-Version: 0.9.10-3 We believe that the bug you reported is fixed in the latest version of backbone, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated backbone 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: Thu, 20 Nov 2014 02:26:40 +0100 Source: backbone Binary: libjs-backbone node-backbone Architecture: source all Version: 0.9.10-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Description: libjs-backbone - some Backbone for JavaScript applications - browser library node-backbone - some Backbone for JavaScript applications - Node module Closes: 768754 Changes: backbone (0.9.10-3) unstable; urgency=medium . * Stop build-depend on phantomjs and avoid using it for testsuite. Closes: bug#768754. Thanks to Lucas Nussbaum. Checksums-Sha1: 5159d297af9d56be7e575f2d1f2a64649240bf3c 2237 backbone_0.9.10-3.dsc c6ec201552632c53d3c084c471263632a2018940 6952 backbone_0.9.10-3.debian.tar.xz a27c3c11620c2c748e69b907d8018ccef33b2f69 73336 libjs-backbone_0.9.10-3_all.deb 020caa79ec0a6a0e11678a371a2de99d00c4baf0 49892 node-backbone_0.9.10-3_all.deb Checksums-Sha256: 0ca453bda2acef95e365dbd15f899bff3485844fc986ca241747fe8767f240c6 2237 backbone_0.9.10-3.dsc 2b5df90bd9f16514f2f6c94265368dc91a62f298047331e87d1244c60c86b34e 6952 backbone_0.9.10-3.debian.tar.xz 54cdfa57e805c7192c137e2605cd33ef456eaa60679c53f0f4806a15b570a993 73336 libjs-backbone_0.9.10-3_all.deb 31bfe71110816a7600f1cc1e656fc4fdd9e271dcc4583ef2e4ab6ae2e1866292 49892 node-backbone_0.9.10-3_all.deb Files: cada7a031275cfb0b8877b3f2f02fb53 2237 web optional backbone_0.9.10-3.dsc e7d5105220c8bf67761414549a76a127 6952 web optional backbone_0.9.10-3.debian.tar.xz 60857044c6cc83c18958a4e7cd06045a 73336 web optional libjs-backbone
Bug#767554: python-persistent and python-zodb: error when trying to install together
Followup-For: Bug #767554 Control: found -1 767554 4.0.8-2 The Conflicts does not work ... without the proper epoch ... you need Conflicts: python-zodb (<< 1:3.11.0~) Selecting previously unselected package python-persistent. Unpacking python-persistent (from .../python-persistent_4.0.8-2_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/python-persistent_4.0.8-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/persistent/dict.py', which is also in package python-zodb 1:3.9.7-2 Errors were encountered while processing: /var/cache/apt/archives/python-persistent_4.0.8-2_amd64.deb Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768600: readahead-fedora: cycle found while processing triggers
Control: tags -1 pending patch Hi! On Sat, 2014-11-08 at 16:05:24 +, Holger Levsen wrote: > package: readahead-fedora > severity: serious > x-debbugs-cc: debian-d...@lists.debian.org > Processing triggers for man-db (2.7.0.2-2) ... > dpkg: cycle found while processing triggers: > chain of packages whose triggers are or may be responsible: > readahead-fedora -> readahead-fedora > packages' pending triggers which are or may be unresolvable: > readahead-fedora: /etc/init.d > dpkg: error processing package readahead-fedora (--configure): > triggers looping, abandoned > [...] > Errors were encountered while processing: > readahead-fedora > E: Sub-process /usr/bin/dpkg returned an error code (1) I'm uploading an NMU to delayed/2 with the attached patch, so that I can add known versioned Breaks from dpkg. Please let me know if you want to upload it yourself, so that I can cancel it, and update the vesioned Breaks on dpkg. Thanks, Guillem diff -u readahead-fedora-1.5.6/debian/changelog readahead-fedora-1.5.6/debian/changelog --- readahead-fedora-1.5.6/debian/changelog +++ readahead-fedora-1.5.6/debian/changelog @@ -1,3 +1,11 @@ +readahead-fedora (2:1.5.6-5.2) unstable; urgency=low + + * Non-maintainer upload. + * Switch trigger directives to noawait variants, to avoid trigger cycles. +(Closes: #768600) + + -- Guillem Jover Thu, 20 Nov 2014 00:10:05 +0100 + readahead-fedora (2:1.5.6-5.1) unstable; urgency=low * Non-maintainer upload. diff -u readahead-fedora-1.5.6/debian/triggers readahead-fedora-1.5.6/debian/triggers --- readahead-fedora-1.5.6/debian/triggers +++ readahead-fedora-1.5.6/debian/triggers @@ -1,2 +1,2 @@ -interest /etc/init.d -interest /lib/modules +interest-noawait /etc/init.d +interest-noawait /lib/modules
Processed: Re: Bug#768600: readahead-fedora: cycle found while processing triggers
Processing control commands: > tags -1 pending patch Bug #768600 [readahead-fedora] readahead-fedora: cycle found while processing triggers Added tag(s) pending and patch. -- 768600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768600 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#767811: marked as done (cl-acl-compat: fails to install: /usr/sbin/register-common-lisp-source: not found)
Your message dated Thu, 20 Nov 2014 01:03:54 + with message-id and subject line Bug#767811: fixed in cl-portable-aserve 1.2.42+cvs.2010.02.08-dfsg-1.2 has caused the Debian Bug report #767811, regarding cl-acl-compat: fails to install: /usr/sbin/register-common-lisp-source: not found 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.) -- 767811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cl-acl-compat Version: 1.2.42+cvs.2010.02.08-dfsg-1.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 cl-acl-compat. (Reading database ... 8908 files and directories currently installed.) Preparing to unpack .../cl-acl-compat_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... Unpacking cl-acl-compat (1.2.42+cvs.2010.02.08-dfsg-1.1) ... Setting up cl-acl-compat (1.2.42+cvs.2010.02.08-dfsg-1.1) ... /var/lib/dpkg/info/cl-acl-compat.postinst: 25: /var/lib/dpkg/info/cl-acl-compat.postinst: /usr/sbin/register-common-lisp-source: not found dpkg: error processing package cl-acl-compat (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: cl-acl-compat cheers, andreas cl-acl-compat_1.2.42+cvs.2010.02.08-dfsg-1.1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: cl-portable-aserve Source-Version: 1.2.42+cvs.2010.02.08-dfsg-1.2 We believe that the bug you reported is fixed in the latest version of cl-portable-aserve, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated cl-portable-aserve package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 18 Nov 2014 01:45:26 +0100 Source: cl-portable-aserve Binary: cl-aserve cl-acl-compat cl-htmlgen cl-webactions Architecture: source all Version: 1.2.42+cvs.2010.02.08-dfsg-1.2 Distribution: unstable Urgency: medium Maintainer: Debian Common Lisp Team Changed-By: Sebastian Ramacher Description: cl-acl-compat - Compatibility layer for Allegro Common Lisp cl-aserve - Portable Aserve cl-htmlgen - HTML generation library for Common Lisp programs cl-webactions - HTTP dispatch library for cl-aserve Closes: 767811 769509 769512 769513 Changes: cl-portable-aserve (1.2.42+cvs.2010.02.08-dfsg-1.2) unstable; urgency=medium . * Non-maintainer upload. * Add dependency on common-lisp-controller to all binary packages. (Closes: #767811, #769509, #769512, #769513) Checksums-Sha1: bab173ff322f2896d00c489e782daf7b738ea571 2255 cl-portable-aserve_1.2.42+cvs.2010.02.08-dfsg-1.2.dsc ac3388cd9435ac9d5a97139fba452e36274406ee 24973 cl-portable-aserve_1.2.42+cvs.2010.02.08-dfsg-1.2.diff.gz 49cb0d6f5496171eabf629bf74983366ee0bdbae 358978 cl-aserve_1.2.42+cvs.2010.02.08-dfsg-1.2_all.deb d16216e2b59afa1a091c6cdd726e4a3ef2773cab 47860 cl-acl-compat_1.2.42+cvs.2010.02.08-dfsg-1.2_all.deb 69906fe0c5b6a4366dc307f6833fc2b6f38b3c11 19414 cl-htmlgen_1.2.42+cvs.2010.02.08-dfsg-1.2_all.deb 1803471fb5104312fd18b4423cdce9d4ce15bc26 22108 cl-webactions_1.2.42+cvs.2010.02.08-dfsg-1.2_all.deb Checksums-Sha256: aa49ab891ba885fe3862f7465e4b74b96aa5848e7c9d08f6d7f7501b5ddab222 2255 cl-portable-aserve_1.2.42+cvs.2010.02.08-dfsg-1.2.dsc 27d450a4ec8bd616e89f9de36c4669ce38c4407d805e84aeed3d357df5deee72 24973 cl-portable-aserve_1.2.42+cvs.2010.02.08-dfsg-1.2.diff.gz 2d6a5643e38c6ee8555e6c6b6f06e8ccadb8739230f0ea93ec839967370a5c08 358978 cl-aserve_1.2.42+cvs.2010.02.08-dfsg-1.2_all.deb 24777f2b81dc4ffe2e67e1329d4397632765df643a5058a0f4d858cd0ab76b08 47860 cl-acl-compat_1.2.42+cvs.2010.02.08-dfsg-1.2_all.deb a62cbeb01e6f867a53fc197b03b885fa796208392a55633b6f7cd393f149888d 19414 cl-htmlgen_1.2.42+cvs.2010.02.0
Bug#769509: marked as done (cl-webactions: installation fails)
Your message dated Thu, 20 Nov 2014 01:03:54 + with message-id and subject line Bug#769509: fixed in cl-portable-aserve 1.2.42+cvs.2010.02.08-dfsg-1.2 has caused the Debian Bug report #769509, regarding cl-webactions: installation fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cl-webactions Version: 1.2.42+cvs.2010.02.08-dfsg-1.1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: > Reading package lists... > Building dependency tree... > Reading state information... > Starting pkgProblemResolver with broken count: 0 > Starting 2 pkgProblemResolver with broken count: 0 > Done > The following extra packages will be installed: > cl-acl-compat cl-aserve cl-htmlgen cl-ppcre cl-puri > Recommended packages: > cl-ptester > The following NEW packages will be installed: > cl-acl-compat cl-aserve cl-htmlgen cl-ppcre cl-puri cl-webactions > 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. > Need to get 628 kB of archives. > After this operation, 1996 kB of additional disk space will be used. > Get:1 http://localhost:/debian/ jessie/main cl-ppcre all 2.0.3-1 [102 kB] > Get:2 http://localhost:/debian/ jessie/main cl-puri all 20101006-1 [23.1 > kB] > Get:3 http://localhost:/debian/ jessie/main cl-acl-compat all > 1.2.42+cvs.2010.02.08-dfsg-1.1 [62.5 kB] > Get:4 http://localhost:/debian/ jessie/main cl-htmlgen all > 1.2.42+cvs.2010.02.08-dfsg-1.1 [21.2 kB] > Get:5 http://localhost:/debian/ jessie/main cl-aserve all > 1.2.42+cvs.2010.02.08-dfsg-1.1 [394 kB] > Get:6 http://localhost:/debian/ jessie/main cl-webactions all > 1.2.42+cvs.2010.02.08-dfsg-1.1 [24.5 kB] > Fetched 628 kB in 0s (4684 kB/s) > Selecting previously unselected package cl-ppcre. > (Reading database ... 8665 files and directories currently installed.) > Preparing to unpack .../cl-ppcre_2.0.3-1_all.deb ... > Unpacking cl-ppcre (2.0.3-1) ... > Selecting previously unselected package cl-puri. > Preparing to unpack .../cl-puri_20101006-1_all.deb ... > Unpacking cl-puri (20101006-1) ... > Selecting previously unselected package cl-acl-compat. > Preparing to unpack .../cl-acl-compat_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb > ... > Unpacking cl-acl-compat (1.2.42+cvs.2010.02.08-dfsg-1.1) ... > Selecting previously unselected package cl-htmlgen. > Preparing to unpack .../cl-htmlgen_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... > Unpacking cl-htmlgen (1.2.42+cvs.2010.02.08-dfsg-1.1) ... > Selecting previously unselected package cl-aserve. > Preparing to unpack .../cl-aserve_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... > Unpacking cl-aserve (1.2.42+cvs.2010.02.08-dfsg-1.1) ... > Selecting previously unselected package cl-webactions. > Preparing to unpack .../cl-webactions_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb > ... > Unpacking cl-webactions (1.2.42+cvs.2010.02.08-dfsg-1.1) ... > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/adduser.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/apt.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-files.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-passwd.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bash.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bsdutils.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-acl-compat.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-aserve.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-htmlgen.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dash.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debconf.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/debian-archive-keyring.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debianutils.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dmsetup.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dpkg.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/e2fslibs:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/findutils.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/gnupg.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/init-system-helpers.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/initscripts.postinst > Dpkg hook: enabling sh
Bug#769513: marked as done (cl-htmlgen: installation fails)
Your message dated Thu, 20 Nov 2014 01:03:54 + with message-id and subject line Bug#769513: fixed in cl-portable-aserve 1.2.42+cvs.2010.02.08-dfsg-1.2 has caused the Debian Bug report #769513, regarding cl-htmlgen: installation fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cl-htmlgen Version: 1.2.42+cvs.2010.02.08-dfsg-1.1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: > Reading package lists... > Building dependency tree... > Reading state information... > Starting pkgProblemResolver with broken count: 0 > Starting 2 pkgProblemResolver with broken count: 0 > Done > The following extra packages will be installed: > cl-ppcre cl-puri > Recommended packages: > cl-ptester > The following NEW packages will be installed: > cl-htmlgen cl-ppcre cl-puri > 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. > Need to get 147 kB of archives. > After this operation, 688 kB of additional disk space will be used. > Get:1 http://localhost:/debian/ jessie/main cl-ppcre all 2.0.3-1 [102 kB] > Get:2 http://localhost:/debian/ jessie/main cl-puri all 20101006-1 [23.1 > kB] > Get:3 http://localhost:/debian/ jessie/main cl-htmlgen all > 1.2.42+cvs.2010.02.08-dfsg-1.1 [21.2 kB] > Fetched 147 kB in 0s (1621 kB/s) > Selecting previously unselected package cl-ppcre. > (Reading database ... 8665 files and directories currently installed.) > Preparing to unpack .../cl-ppcre_2.0.3-1_all.deb ... > Unpacking cl-ppcre (2.0.3-1) ... > Selecting previously unselected package cl-puri. > Preparing to unpack .../cl-puri_20101006-1_all.deb ... > Unpacking cl-puri (20101006-1) ... > Selecting previously unselected package cl-htmlgen. > Preparing to unpack .../cl-htmlgen_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... > Unpacking cl-htmlgen (1.2.42+cvs.2010.02.08-dfsg-1.1) ... > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/adduser.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/apt.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-files.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-passwd.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bash.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bsdutils.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-htmlgen.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dash.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debconf.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/debian-archive-keyring.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debianutils.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dmsetup.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dpkg.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/e2fslibs:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/findutils.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/gnupg.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/init-system-helpers.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/initscripts.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/less.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libacl1:amd64.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/libapt-inst1.5:amd64.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/libapt-pkg4.12:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libattr1:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libaudit1:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libblkid1:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libbz2-1.0:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libc-bin.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libc6:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcap2:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libcomerr2:amd64.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/libcryptsetup4:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libdb5.3:amd64.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/libdebconfclient0:amd64.pos
Bug#769512: marked as done (cl-aserve: installation fails)
Your message dated Thu, 20 Nov 2014 01:03:54 + with message-id and subject line Bug#769512: fixed in cl-portable-aserve 1.2.42+cvs.2010.02.08-dfsg-1.2 has caused the Debian Bug report #769512, regarding cl-aserve: installation fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cl-aserve Version: 1.2.42+cvs.2010.02.08-dfsg-1.1 Severity: serious User: debian...@lists.debian.org Usertags: instest-20141113 instest Hi, While testing the installation of all packages in sid, I ran into the following problem: > Reading package lists... > Building dependency tree... > Reading state information... > Starting pkgProblemResolver with broken count: 0 > Starting 2 pkgProblemResolver with broken count: 0 > Done > The following extra packages will be installed: > cl-acl-compat cl-htmlgen cl-ppcre cl-puri > Suggested packages: > cl-webactions > Recommended packages: > cl-ptester > The following NEW packages will be installed: > cl-acl-compat cl-aserve cl-htmlgen cl-ppcre cl-puri > 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded. > Need to get 603 kB of archives. > After this operation, 1881 kB of additional disk space will be used. > Get:1 http://localhost:/debian/ jessie/main cl-ppcre all 2.0.3-1 [102 kB] > Get:2 http://localhost:/debian/ jessie/main cl-puri all 20101006-1 [23.1 > kB] > Get:3 http://localhost:/debian/ jessie/main cl-acl-compat all > 1.2.42+cvs.2010.02.08-dfsg-1.1 [62.5 kB] > Get:4 http://localhost:/debian/ jessie/main cl-htmlgen all > 1.2.42+cvs.2010.02.08-dfsg-1.1 [21.2 kB] > Get:5 http://localhost:/debian/ jessie/main cl-aserve all > 1.2.42+cvs.2010.02.08-dfsg-1.1 [394 kB] > Fetched 603 kB in 0s (6163 kB/s) > Selecting previously unselected package cl-ppcre. > (Reading database ... 8665 files and directories currently installed.) > Preparing to unpack .../cl-ppcre_2.0.3-1_all.deb ... > Unpacking cl-ppcre (2.0.3-1) ... > Selecting previously unselected package cl-puri. > Preparing to unpack .../cl-puri_20101006-1_all.deb ... > Unpacking cl-puri (20101006-1) ... > Selecting previously unselected package cl-acl-compat. > Preparing to unpack .../cl-acl-compat_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb > ... > Unpacking cl-acl-compat (1.2.42+cvs.2010.02.08-dfsg-1.1) ... > Selecting previously unselected package cl-htmlgen. > Preparing to unpack .../cl-htmlgen_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... > Unpacking cl-htmlgen (1.2.42+cvs.2010.02.08-dfsg-1.1) ... > Selecting previously unselected package cl-aserve. > Preparing to unpack .../cl-aserve_1.2.42+cvs.2010.02.08-dfsg-1.1_all.deb ... > Unpacking cl-aserve (1.2.42+cvs.2010.02.08-dfsg-1.1) ... > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/adduser.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/apt.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-files.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/base-passwd.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bash.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/bsdutils.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-acl-compat.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-aserve.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/cl-htmlgen.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dash.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debconf.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/debian-archive-keyring.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/debianutils.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dmsetup.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/dpkg.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/e2fslibs:amd64.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/findutils.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/gnupg.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/init-system-helpers.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/initscripts.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/less.postinst > Dpkg hook: enabling sh trace for /var/lib/dpkg/info/libacl1:amd64.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/libapt-inst1.5:amd64.postinst > Dpkg hook: enabling sh trace for > /var/lib/dpkg/info/libapt-pkg4.12:amd64.postinst > Dpkg hook: enab
Bug#770251: ruby-jbuilder,ruby-responders: error when trying to install together
Package: ruby-jbuilder,ruby-responders Version: 2.0.2-1 Severity: serious Tags: sid User: trei...@debian.org Usertags: edos-file-overwrite Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package ruby-responders. (Reading database ... 9354 files and directories currently installed.) Preparing to unpack .../ruby-responders_2.0.2-1_all.deb ... Unpacking ruby-responders (2.0.2-1) ... dpkg: error processing archive /var/cache/apt/archives/ruby-responders_2.0.2-1_all.deb (--unpack): trying to overwrite '/usr/lib/ruby/vendor_ruby/generators/rails/templates/controller.rb', which is also in package ruby-jbuilder 2.1.3-1 Errors were encountered while processing: /var/cache/apt/archives/ruby-responders_2.0.2-1_all.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/lib/ruby/vendor_ruby/generators/rails/templates/controller.rb This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html ruby-jbuilder=2.1.3-1_ruby-responders=2.0.2-1.log.gz Description: application/gzip
Bug#770185: marked as done (linux-image-3.2.0-4-kirkwood: Unknown symbol ip_idents_reserve breaks IPv6)
Your message dated Thu, 20 Nov 2014 00:35:43 + with message-id <1416443743.7215.0.ca...@decadent.org.uk> and subject line Re: Bug#770185: linux-image-3.2.0-4-kirkwood: Unknown symbol ip_idents_reserve breaks IPv6 has caused the Debian Bug report #770185, regarding linux-image-3.2.0-4-kirkwood: Unknown symbol ip_idents_reserve breaks IPv6 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.) -- 770185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.2.63-2+deb7u1 Severity: grave Tags: ipv6 Justification: renders package unusable Dear Maintainer, the package introduces unmet symbol dependencies for the ipv6 kernel module and hence breaks IPv6 support. This appears to be caused by the inclusion of a Debian specific patch 'drivers-net-ipv6-select-ipv6-fragment-idents-for-vir.patch' written by Ben Hutchings . Downgrading to version 3.2.60-1+deb7u3 appears to be the only remedy. Many thanks. -- Package-specific info: ** Version: Linux version 3.2.0-4-kirkwood (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 Debian 3.2.57-3+deb7u1 ** Command line: console=ttyS0,115200 ** Not tainted ** Kernel log: [ 24.361697] usbcore: registered new interface driver snd-usb-audio [ 24.517306] libertas_sdio mmc0:0001:1: firmware: agent aborted loading libertas/sd8688_helper.bin (not found?) [ 24.565007] libertas_sdio mmc0:0001:1: firmware: agent aborted loading sd8688_helper.bin (not found?) [ 24.574442] libertas_sdio: failed to find firmware (-2) [ 24.583236] libertas_sdio: probe of mmc0:0001:1 failed with error -2 [ 24.602645] Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2 [ 24.668293] btmrvl_sdio mmc0:0001:2: firmware: agent aborted loading sd8688_helper.bin (not found?) [ 25.253582] Adding 1049084k swap on /dev/sda2. Priority:-1 extents:1 across:1049084k SS [ 25.328307] EXT4-fs (sdb2): re-mounted. Opts: (null) [ 25.594492] EXT4-fs (sdb2): re-mounted. Opts: errors=remount-ro [ 25.822865] loop: module loaded [ 28.600446] EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended [ 28.610013] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: discard,data=ordered,errors=remount-ro [ 30.020234] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.040902] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.087839] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.320561] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.342165] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.408901] RPC: Registered named UNIX socket transport module. [ 30.414855] RPC: Registered udp transport module. [ 30.419631] RPC: Registered tcp transport module. [ 30.424359] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 30.470326] FS-Cache: Loaded [ 30.538512] FS-Cache: Netfs 'nfs' registered for caching [ 30.583836] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 32.957724] mv643xx_eth_port mv643xx_eth_port.1: eth1: link up, 1000 Mb/s, full duplex, flow control disabled [ 34.769176] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 35.017457] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 38.599557] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 42.329340] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 43.676240] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 54.137370] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 54.177423] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.147370] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.213917] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.867175] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.917969] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 60.548808] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 61.044748] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 61.176379] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 75.308553] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 75.371951] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 88.766351] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 99.726306] The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case. If you have one, please send an email to linux...@kvack.org. [ 191.458947] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 779.571632] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 874.047456] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 874.109899] ipv
Processed: Re: [Pkg-zsh-devel] Bug#770226: zsh-common: installation fails with "dpkg-maintscript-helper: error: original symlink target is not an absolute path"
Processing control commands:
> clone -1 -2
Bug #770226 [zsh-common] zsh-common: installation fails with
"dpkg-maintscript-helper: error: original symlink target is not an absolute
path"
Bug 770226 cloned as bug 770245
> reassign -2 debhelper 9.20141107
Bug #770245 [zsh-common] zsh-common: installation fails with
"dpkg-maintscript-helper: error: original symlink target is not an absolute
path"
Bug reassigned from package 'zsh-common' to 'debhelper'.
No longer marked as found in versions zsh/5.0.7-4.
Ignoring request to alter fixed versions of bug #770245 to the same values
previously set
Bug #770245 [debhelper] zsh-common: installation fails with
"dpkg-maintscript-helper: error: original symlink target is not an absolute
path"
Marked as found in versions debhelper/9.20141107.
> severity -2 important
Bug #770245 [debhelper] zsh-common: installation fails with
"dpkg-maintscript-helper: error: original symlink target is not an absolute
path"
Severity set to 'important' from 'serious'
> retitle -2 dh_installdeb: Using symlink_to_dir with relative symlinks needs
> ${misc:Pre-Depends} = dpkg >= 1.17.14
Bug #770245 [debhelper] zsh-common: installation fails with
"dpkg-maintscript-helper: error: original symlink target is not an absolute
path"
Changed Bug title to 'dh_installdeb: Using symlink_to_dir with relative
symlinks needs ${misc:Pre-Depends} = dpkg >= 1.17.14' from 'zsh-common:
installation fails with "dpkg-maintscript-helper: error: original symlink
target is not an absolute path"'
> tag -1 + confirmed
Bug #770226 [zsh-common] zsh-common: installation fails with
"dpkg-maintscript-helper: error: original symlink target is not an absolute
path"
Added tag(s) confirmed.
--
770226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770226
770245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770245
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#770226: [Pkg-zsh-devel] Bug#770226: zsh-common: installation fails with "dpkg-maintscript-helper: error: original symlink target is not an absolute path"
Control: clone -1 -2
Control: reassign -2 debhelper 9.20141107
Control: severity -2 important
Control: retitle -2 dh_installdeb: Using symlink_to_dir with relative symlinks
needs ${misc:Pre-Depends} = dpkg >= 1.17.14
Control: tag -1 + confirmed
Hi,
Axel Beckert wrote:
> I tried to reproduce this issue in a freshly bootstrapped jessie
> chroot, but couldn't (which doesn't surprise me much as piuparts
> couldn't either).
[...]
> One thing which is a good candidate for such a failure is a too old
> dpkg version. Both, zsh and zsh-common have a "Pre-Depends: dpkg (>=
> 1.17.5)" because of this, but maybe that Pre-Depends is not strict
> enough (despite it has been set by debhelper for using
> dpkg-maintscript-helper with symlink_to_dir. But reading dpkg's
> changelog.Debian.gz, I find the following entry for 1.17.14:
>
> * Add support for relative symlinks to dpkg-maintscript-helper
> symlink_to_dir command. [...]
>
> So I suspect this happened with a dpkg version < 1.17.14 and we likely
> need to bump that Pre-Depends to >= 1.17.14.
I could confirm that by downgrading dpkg from 1.17.21 to 1.17.13 and
then installing zsh:
Preparing to unpack .../zsh-common_5.0.7-4_all.deb ...
dpkg-maintscript-helper: error: original symlink target is not an absolute path
dpkg: error processing archive
/var/cache/apt/archives/zsh-common_5.0.7-4_all.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
dpkg-maintscript-helper: error: original symlink target is not an absolute path
> debhelper maintainers: Shall I clone or reassign this bug report to
> debhelper for bumping ${misc:Pre-Depends} in such cases?
I'm sure this should be fixed in debhelper's ${misc:Pre-Depends}, too,
hence I cloned the bug report.
I'm just not sure if it should be generally bumped to dpkg >= 1.17.14
or only in cases with relative symlinks.
I'm also not sure if this is of RC severity for debhelper. Downgrading
the clone to important for now. Feel free to raise it to RC severity
again.
> Scott, can you tell me the dpkg version which was running at that
> time.
No more needed. I'm sure now.
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770243: FTBFS: ../../lib/.libs/libgroonga.so: undefined reference to `GRN_ATOMIC_ADD_EX'
Source: groonga Version: 4.0.6.1-2 Severity: serious Tags: jessie sid Justification: FTBFS on arm64, armel, armhf, mips and other Dear Maintainer, groonga FTBFS on arm64, armel, armhf, mips and other. arm64: https://buildd.debian.org/status/fetch.php?pkg=groonga&arch=arm64&ver=4.0.6.1-2&stamp=1414249364 - Making all in suggest make[4]: Entering directory '/«PKGBUILDDIR»/src/suggest' CC groonga_suggest_create_dataset-groonga_suggest_create_dataset.o CXXLDgroonga-suggest-create-dataset ../../lib/.libs/libgroonga.so: undefined reference to `GRN_ATOMIC_ADD_EX' collect2: error: ld returned 1 exit status make[4]: *** [groonga-suggest-create-dataset] Error 1 - The build can not architecture seems GRN_ATOMIC_ADD_EX is not supported. Please add the function of GRN_ATOMIC_ADD_EX,or please limit the support architecture. Best regards, Nobuhiro -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: armhf armel sh4 powerpcspe powerpc Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770148: marked as done (gnome-logs doesn't start when launched from gnome-shell)
Your message dated Thu, 20 Nov 2014 00:03:43 + with message-id and subject line Bug#770148: fixed in gnome-logs 3.14.2-1 has caused the Debian Bug report #770148, regarding gnome-logs doesn't start when launched from gnome-shell 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.) -- 770148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-logs Version: 3.14.1-1 Severity: normal When launching gnome-logs from gnome-shell, nothing happens. It works when run from a terminal. This seems like exactly the same issue as Cheese had before. Looking at /usr/share/dbus/services.d/org.gnome.Logs.service you can see that the prefix has an unescaped shell variable. The fix seems to be in this git commit: https://git.gnome.org/browse/gnome-logs/commit/?h=gnome-3-14&id=5b9c09aa12caa5fadd2fb0c54bfaa449f1e5791f In case a full upgrade to 3.14.2 is not considered. //Marcus -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-logs depends on: ii gsettings-desktop-schemas 3.14.1-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-13 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.0-2 ii libgtk-3-0 3.14.4-2 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-01.36.8-2 ii libsystemd0215-5+b1 gnome-logs recommends no packages. gnome-logs suggests no packages. -- debconf-show failed --- End Message --- --- Begin Message --- Source: gnome-logs Source-Version: 3.14.2-1 We believe that the bug you reported is fixed in the latest version of gnome-logs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Henriksson (supplier of updated gnome-logs 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: Thu, 20 Nov 2014 00:50:34 +0100 Source: gnome-logs Binary: gnome-logs Architecture: source amd64 Version: 3.14.2-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Andreas Henriksson Description: gnome-logs - viewer for the systemd journal. Closes: 770148 Changes: gnome-logs (3.14.2-1) unstable; urgency=medium . * New upstream release - fixes file generation (Closes: #770148) Checksums-Sha1: 0d74f74ad1326f8a71cee30084197cc54543ef6d 2175 gnome-logs_3.14.2-1.dsc 2b9ad5f7f6011358522bc3811fe085ddf7eb4bec 602280 gnome-logs_3.14.2.orig.tar.xz 633fb6ad9f8f89bc0c6ae76c43b6b468f4c05fed 11220 gnome-logs_3.14.2-1.debian.tar.xz d0e4f7ad1f49336a5209ac9378ede02b635728c3 444052 gnome-logs_3.14.2-1_amd64.deb Checksums-Sha256: 8c6ff628de6e1d5bb4a166a8118541753d9a668189ad6899eb04dc88912281b4 2175 gnome-logs_3.14.2-1.dsc 9c470257a8dd998041b491d9109cca1500b136d84b846b574cd3b65cf374191f 602280 gnome-logs_3.14.2.orig.tar.xz 11c1a049ad1b25aafb91793690414fc706cb7a6af7d48d0832eeea0d031b2f73 11220 gnome-logs_3.14.2-1.debian.tar.xz 50640d2351b62033eed94f46a092f1a4c579e7ebcbb01d1954ec75c3b1b0e8e7 444052 gnome-logs_3.14.2-1_amd64.deb Files: d1c3cdc8eb2bd6663f17ae19b766f4b7 2175 gnome optional gnome-logs_3.14.2-1.dsc 7d4f7763ef8239bcd10b28113528482e 602280 gnome optional gnome-logs_3.14.2.orig.tar.xz 9fbde320fdb1cb1a1bd8aeb0bb40c756 11220 gnome optional gnome-logs_3.14.2-1.debian.tar.xz 42f708803f68e0c2ff118eb0e98b53f2 444052 gnome optional gnome-logs_3.14.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUbS8xAAoJEAvEfcZNE1MGK4IP/3LoCVSi86FgfHru6rDi9inj CNdmxpgLbX4vVhW4YX4MptcweZE/KpIoKqA44VsLAYyjV8OgGLti0rPkHkbxVBbG Y1S9Yhd00hwticmrsmRECS5VG2/Up3YLCrJjBKpSx/pR9PyCo2aBbLR0JmgoGvT1 mqHYEyXJFJSH/prkGBVaZJejG3+Z6N8urTFHb21WkZ/PEeqPcUUDi++6y+YuthQT VGqBp0/DV33ggJMV/c0
Processed: retitle 770226 to zsh-common: installation fails with "dpkg-maintscript-helper: error: original symlink target is not an absolute path"
Processing commands for cont...@bugs.debian.org: > retitle 770226 zsh-common: installation fails with "dpkg-maintscript-helper: > error: original symlink target is not an absolute path" Bug #770226 [zsh-common] zsh-common: installation fails for amd arch Changed Bug title to 'zsh-common: installation fails with "dpkg-maintscript-helper: error: original symlink target is not an absolute path"' from 'zsh-common: installation fails for amd arch' > thanks Stopping processing here. Please contact me if you need assistance. -- 770226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770226 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#770226: [Pkg-zsh-devel] Bug#770226: zsh-common: installation fails for amd arch
Hi Scott,
thanks for the bug report.
Scott Walsh wrote:
> aptitude install zsh, which lead to packages being in the 'half'
> installed state. Attempting to purge was unsucessful. Had to resort to
> dpkg --remove --force-remove-reinstreq zsh zsh-common to resolve the
> issue.
That's strange, because I would expect that piuparts would find such
issues, but definitely didn't, neither at
https://piuparts.debian.org/sid/source/z/zsh.html nor at
http://jenkins.grml.org/view/Debian/job/zsh-piuparts/
> Preparing to unpack .../zsh-common_5.0.7-4_all.deb ...
> dpkg-maintscript-helper: error: original symlink target is not an
> absolute path
> dpkg: error processing archive
> /var/cache/apt/archives/zsh-common_5.0.7-4_all.deb (--unpack):
This is clearly something which was introduced by one of the fixes in
5.0.7-4 as we didn't use dpkg-maintscript-helper before.
I tried to reproduce this issue in a freshly bootstrapped jessie
chroot, but couldn't (which doesn't surprise me much as piuparts
couldn't either).
So we need to see what so special in your setup.
One thing which is a good candidate for such a failure is a too old
dpkg version. Both, zsh and zsh-common have a "Pre-Depends: dpkg (>=
1.17.5)" because of this, but maybe that Pre-Depends is not strict
enough (despite it has been set by debhelper for using
dpkg-maintscript-helper with symlink_to_dir. But reading dpkg's
changelog.Debian.gz, I find the following entry for 1.17.14:
* Add support for relative symlinks to dpkg-maintscript-helper
symlink_to_dir command. [...]
So I suspect this happened with a dpkg version < 1.17.14 and we likely
need to bump that Pre-Depends to >= 1.17.14.
Cc'ing debhelper-devel to make them aware of this potential issue.
debhelper maintainers: Shall I clone or reassign this bug report to
debhelper for bumping ${misc:Pre-Depends} in such cases?
To be sure that my assumption is correct: Scott, can you tell me the
dpkg version which was running at that time. If the dpkg has changed
since then or was upgraded in the same run, please look in
/var/log/aptitude or /var/log/dpkg.log which was installed when that
error happened. (Verifying that dpkg was either uptodate in Jessie or
below version 1.17.14 at the time when this happened should suffice.)
Regards, Axel
--
,''`. | Axel Beckert , http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770222: CVE request: icecast: possible leak of on-connect scripts
Good morning, It was reported that Icecast could possibly leak the contents of on-connect scripts to clients, which may contain sensitive information. This issue has been fixed in the 2.4.1 release: http://icecast.org/news/icecast-release-2_4_1/ "Fix on-connect and on-disconnect script STDIN/STDOUT/STDERR corruption due to shared file descriptors." References: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770222 https://trac.xiph.org/ticket/2089 Cheers, -- Murray McAllister / Red Hat Product Security https://bugzilla.redhat.com/show_bug.cgi?id=1165880 -- 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#765129: tcos: FTBFS: build-dependency not installable: libxmlrpc-c3-dev
Processing commands for cont...@bugs.debian.org: > tags 765129 patch Bug #765129 [src:tcos] tcos: FTBFS: build-dependency not installable: libxmlrpc-c3-dev Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 765129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765129 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#770232: Please remove the non-free files and upload to main
Package: python-selenium Version: 2.2.0-1 Severity: serious Hi, It is my understanding that Selenium is non-free because of the .xpi files which upstream embbeds (and the .xpi contains pre-built .dll for windows and .so files for Linux). However, Selenium is still useful without these files. For example, Selenium could be used using the PhantomJS plugin. In Fedora, that's what they did: they ship Selenium in whatever matches the "main" repository of Debian, without the .xpi file. So, could you please upload python-selenium 2.2.0+dfsg1 to main, without the non-free files, to Debian main? The .xpi files could be shipped standalone in the non-free repositories if you still want them. Note that I would really appreciate if you could upload this in Experimental during the freeze, if the release team refuses to have the change, though it IMO would make sense to at least try to ask the release team if the change could go in Jessie. Last, if you need help, I'd be happy give some. (like if you don't have upload rights and need sponsoring of the upload, I'm not sure if that is the case here...) Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770230: CVE-2014-5146 CVE-2014-5149 CVE-2014-8594 CVE-2014-8595
Source: xen Severity: grave Tags: security Hi, the following security issues apply to Xen in jessie: CVE-2014-5146,CVE-2014-5149: https://marc.info/?l=oss-security&m=140784877111813&w=2 CVE-2014-8594: https://marc.info/?l=oss-security&m=141631359901060&w=2 CVE-2014-8595: https://marc.info/?l=oss-security&m=141631352601020&w=2 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767676: ola-rdm-tests: fails to install: subprocess installed post-installation script returned error exit status 10
On Tue, Nov 18, 2014 at 01:48:04PM +0100, Jean Baptiste Favre wrote: > Hello Helmut, > > Please find attached anew version for the patch. > > Here is what I fixed: > > * Remove debconf calls from ola-rdm-tests postinst. (Closes: #767676) > * Fix other seriouys issues: > - Provides missing /etc/default/ola from ola postinst script to allow > olad service control in the same way rdm_test_server is NAK. /etc/default/* to manage service status is a menace, and should be forbidden. (it isn't currently, so I'm not filing bugs on other packages, but I think it's *wrong*, and I don't want it in mine) This is why I removed the debconf and /etc/default stuff from the package provided by upstream before I uploaded to Debian (or at least, tried to ;-). What's still there can remain, but will probably be dropped for jessie+1. As long as your fixes are applied, of course. > - Update init scripts to change advice to enable olad & > drm_test_server services (dpkg-reconfigure won't work without debconf) > - add postrm scripts for packages ola & ola-rdm-tests to fully remove > configuration files & dirs so that piuparts tests can pass > > As you asked: > > - I didn't changed configuration file names. I thought this was a bit > "out of scope", you confirmed :) > - packages pass piuparts tests (I tested .changes file with > --no-upgrade-test since jessie package fails to install) > > I also documented verbosely changes in changelog as requested by [1] > > Please let me know wheter the work is satisfying or I need to iterate more. > > Regards, > Jean Baptiste > > [1] https://release.debian.org/jessie/freeze_policy.html > > On 18/11/2014 08:15, Helmut Grohne wrote: > > On Mon, Nov 17, 2014 at 11:42:54PM +0100, Jean Baptiste Favre wrote: > >> Thanks for your advice. I'm working on a new version of the patch. > >> In the meantime, what should I do with my already uploaded NMU (on > >> mentors.debian.net). Maybe I should delete it just to be sure nobody > >> will upload it ? > > > > You can do that. > > > >> I also noticed that init scripts ask for "dpkg-reconfigure package" to > >> enable service start, which is disabled by default. I guess this was OK > >> when debconf handles /etc/default/package content, but obviously it > >> won't work anymore. > >> I can change the init script to display another message. > > > > This sounds like a documentation fix. Currently, this should be covered > > by the freeze policy. So fixing it should be ok for now. > > > >> Finally, I'm considering shipping /etc/default/ola which is not shipped > >> currently, in the same way as /etc/default/ola-rdm-tests. It controls > >> whether olad service is enabled or not. > > > > This sounds like a functional change. While it looks like an > > improvement, I do not yet see why this should be release critical. So > > better skip this for the upload targeting jessie, but you can prepare a > > separate .debdiff for Wouter to apply later if you like. (Better create > > a new bug report at lower severity then.) > > > >> And, last question, speaking about /etc/default files, I wonder which > >> are the best practices: > >> - name /etc/default/xxx file according to the init script which will use > >> them > >> - name /etc/default/xxx file according to the package which provide them > >> > >> In my case, /etc/default/ola is provided by ola package but controls > >> olad service. Same with /etc/default/ola-rdm-tests which is provided by > >> eponym package to control rdm_test_server service. > >> > >> All these would indeed increase the overall package quality, but I > >> wonder if this is not a bit "out of scope" work considering Jessie freeze. > > > > You are rightly wondering. These changes are likely not acceptable for > > jessie. > > > > It looks to me that you are looking a bit too far at the moment. This > > bug was found using piuparts. After applying your initial .debdiff, > > piuparts still rightfully complains (about other things). This is why I > > asked you to reiterate. Nothing more. > > > > Helmut > > diff -Nru ola-0.9.1/debian/changelog ola-0.9.1/debian/changelog > --- ola-0.9.1/debian/changelog2014-08-17 10:07:29.0 +0200 > +++ ola-0.9.1/debian/changelog2014-11-18 09:47:02.0 +0100 > @@ -1,3 +1,17 @@ > +ola (0.9.1-1.1) unstable; urgency=medium > + > + * Non-maintainer upload. > + * Remove debconf calls from ola-rdm-tests postinst. (Closes: #767676) > + * Fix other seriouys issues: > +- Provides missing /etc/default/ola from ola postinst script to allow > + olad service control in the same way rdm_test_server is > +- Update init scripts to change advice to enable olad & drm_test_server > + services (dpkg-reconfigure won't work without debconf) > +- add postrm scripts for packages ola & ola-rdm-tests to fully remove > + configuration files & dirs so that piuparts tests can pass > + > + -- Jean Baptiste Favre Sun, 16 Nov 2014 17:44:18 +0100 > + > ola (
Processed: Re: Bug#770009: imagemagick: FTBFS on mips
Processing control commands: > severity -1 important Bug #770009 [imagemagick] imagemagick: FTBFS on mips Severity set to 'important' from 'serious' -- 770009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770009 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#770009: imagemagick: FTBFS on mips
Control: severity -1 important Hi, On Tue, Nov 18, 2014 at 04:53:23PM +, Dejan Latinovic wrote: > My assumption is that this action on cavium boards need a lot of time to > execute, > and that is the reason for TERM signal. > > > while read SIZE; do \ > > mkdir -p > > /«PKGBUILDDIR»/debian/tmp-Q16/usr/share/icons/hicolor/$SIZE/apps/ ;\ > > cd /«PKGBUILDDIR»/debian/build-quantum-Q16; \ > > ./magick.sh convert /«PKGBUILDDIR»/debian/display-im6.svg \ > > -background none -define filter:blur=0.75 -filter > > Gaussian -resize $SIZE \ > > -gravity center -extent $SIZE \ > > > > /«PKGBUILDDIR»/debian/tmp-Q16/usr/share/icons/hicolor/$SIZE/apps/display-im6.q16.png; > > \ > > done < /«PKGBUILDDIR»/debian/display-im6.iconssize > > > Starting whit 8:6.8.8.9-1 version > all imagemagick builds were done on ball (broadcom board). > > https://buildd.debian.org/status/logs.php?pkg=imagemagick&arch=mips It built fine this time on ball. > Also, for mipsel > all builds were done on non-cavium boards (broadcom, loongson). > > I will try it locally confirm this assumption. OK. Thanks for looking into this. I downgraded the severity of this bug, but didn't close it, as it would be good to know how to avoid this problem (even if it is by blacklisting imagemagic on certain buildds). Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767138: libfftw3 SIGILL on armhf
sorry for the lack of reply, I have been traveling for the last 1.5 weeks. I'll try to look at this weekend. Feel free to NMU if you need a faster solution. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770229: CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904
Source: cyassl Severity: grave Tags: security Please see https://marc.info/?l=oss-security&m=139779940032403&w=2 On a related note: I noticed that mysql/mariadb hasn't switched to using cyassl. Without any rev deps we should rather avoid including it in jessie IMO and base on cyassl for jessie+1. Cheers, Moritz -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#767138: libfftw3 SIGILL on armhf
Processing control commands:
> severity -1 serious
Bug #767138 [src:fftw3] fftw3: runtime detection of NEON is perhaps broken
Severity set to 'serious' from 'normal'
> block 760271 by -1
Bug #760271 [src:octave] octave: Random FTBFS on armhf: panic: Segmentation
fault -- stopping myself...
760271 was not blocked by any bugs.
760271 was not blocking any bugs.
Added blocking bug(s) of 760271: 767138
> block 769974 by -1
Bug #769974 [src:minimodem] minimodem: FTBFS on armhf
769974 was not blocked by any bugs.
769974 was not blocking any bugs.
Added blocking bug(s) of 769974: 767138
> reopen 752514
Bug #752514 {Done: Cédric Boutillier } [src:ruby-fftw3]
ruby-fftw3: FTBFS on armhf
Bug reopened
Ignoring request to alter fixed versions of bug #752514 to the same values
previously set
> block 752514 by -1
Bug #752514 [src:ruby-fftw3] ruby-fftw3: FTBFS on armhf
752514 was not blocked by any bugs.
752514 was not blocking any bugs.
Added blocking bug(s) of 752514: 767138
--
752514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752514
760271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760271
767138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767138
769974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769974
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: found 770222 in 2.4.0-1
Processing commands for cont...@bugs.debian.org: > found 770222 2.4.0-1 Bug #770222 [icecast2] icecast2: on-connect scripts: icecast can leak output to attentive sources Marked as found in versions icecast2/2.4.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 770222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770222 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#769722: marked as done (creepy: Fail to look up on Flickr (Error: 95: SSL is required))
Your message dated Wed, 19 Nov 2014 21:49:08 + with message-id and subject line Bug#769722: fixed in python-flickrapi 1.2-3.1 has caused the Debian Bug report #769722, regarding creepy: Fail to look up on Flickr (Error: 95: SSL is required) 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.) -- 769722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: creepy Version: 0.1.94-1 Severity: important Dear Maintainer, When testing creepy in wheezy, I tried to enter a flickr username into the targets dialog and press 'Geolocate Target', but only got a error dialog: Error connecting to flicr Error was Error: 95: SSL is required As far as I can tell, this was a fatal error causing the program to not find any information about the Flirk-user in question. I suspect this might really be a bug in the python-flickrapi package, as its /usr/share/pyshared/flickrapi/__init__.py file uses http and not https to talk to flickr. I tried applying the following change to the python-flickrapi package, and this got rid of the error message and the creepy tool seemed to start doing something. After a while, it even showed some map locations, so I suspect this is the correct fix. But I am unsure, so I hope you can reassign if the bug should be fixed there. --- /usr/share/pyshared/flickrapi/__init__.py 2009-05-13 09:20:43.0 +0200 +++ /tmp/__init__.py2014-11-15 22:16:08.446380054 +0100 @@ -386,7 +386,7 @@ if self.cache and self.cache.get(post_data): return self.cache.get(post_data) -url = "http://"; + FlickrAPI.flickr_host + FlickrAPI.flickr_rest_form +url = "https://"; + FlickrAPI.flickr_host + FlickrAPI.flickr_rest_form flicksocket = urllib.urlopen(url, post_data) reply = flicksocket.read() flicksocket.close() @@ -440,7 +440,7 @@ "frob": frob, "perms": perms}) -return "http://%s%s?%s"; % (FlickrAPI.flickr_host, \ +return "https://%s%s?%s"; % (FlickrAPI.flickr_host, \ FlickrAPI.flickr_auth_form, encoded) def web_login_url(self, perms): @@ -454,7 +454,7 @@ "api_key": self.api_key, "perms": perms}) -return "http://%s%s?%s"; % (FlickrAPI.flickr_host, \ +return "https://%s%s?%s"; % (FlickrAPI.flickr_host, \ FlickrAPI.flickr_auth_form, encoded) def __extract_upload_response_format(self, kwargs): @@ -578,7 +578,7 @@ if self.secret: kwargs["api_sig"] = self.sign(kwargs) -url = "http://%s%s"; % (FlickrAPI.flickr_host, form_url) +url = "https://%s%s"; % (FlickrAPI.flickr_host, form_url) # construct POST data body = Multipart() -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages creepy depends on: ii python2.7.3-4+deb7u1 ii python-beautifulsoup 3.2.1-1 ii python-configobj 4.7.2+ds-4 ii python-flickrapi 1.2-3 ii python-osmgpsmap 0.7.3-3 ii python-pyexiv20.3.2-5 ii python-simplejson 2.5.2-1 ii python-tweepy 1.7.1-2+deb7u1 creepy recommends no packages. creepy suggests no packages. --- End Message --- --- Begin Message --- Source: python-flickrapi Source-Version: 1.2-3.1 We believe that the bug you reported is fixed in the latest version of python-flickrapi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen (supplier of updated python-flickrapi 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, 17 Nov 2014 21:48:46 +0100 Source: python-flickrapi Binary: python-flickrapi Architecture: source all Version: 1.2-3.1 Distribution: unstable Urgency: low Mai
Bug#770226: zsh-common: installation fails for amd arch
Package: zsh-common
Version: 5.0.7-4
Severity: serious
Justification: Policy 3.5
Dear Maintainer,
* What led up to the situation?
Attempting to install zsh
* What exactly did you do (or not do) that was effective (or
ineffective)?
aptitude install zsh, which lead to packages being in the 'half'
installed state. Attempting to purge was unsucessful. Had to resort to
dpkg --remove --force-remove-reinstreq zsh zsh-common to resolve the
issue.
* What was the outcome of this action?
I'm not able to install zsh
* What outcome did you expect instead?
Being able to install zsh :)
-- Install Log:
# aptitude install zsh
The following NEW packages will be installed:
zsh zsh-common{a}
0 packages upgraded, 2 newly installed, 0 to remove and 361 not
upgraded.
Need to get 3,822 kB of archives. After unpacking 13.2 MB will be
used.
Do you want to continue? [Y/n/?] y
Get: 1 http://ftp.us.debian.org/debian/ testing/main zsh-common all
5.0.7-4 [3,122 kB]
Get: 2 http://ftp.us.debian.org/debian/ testing/main zsh amd64 5.0.7-4
[700 kB]
Fetched 3,822 kB in 1s (3,297 kB/s)
Selecting previously unselected package zsh-common.
(Reading database ... 51859 files and directories currently
installed.)
Preparing to unpack .../zsh-common_5.0.7-4_all.deb ...
dpkg-maintscript-helper: error: original symlink target is not an
absolute path
dpkg: error processing archive
/var/cache/apt/archives/zsh-common_5.0.7-4_all.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
dpkg-maintscript-helper: error: original symlink target is not an
absolute path
dpkg: error while cleaning up:
subprocess new post-removal script returned error exit status 1
Selecting previously unselected package zsh.
Preparing to unpack .../archives/zsh_5.0.7-4_amd64.deb ...
dpkg-maintscript-helper: error: original symlink target is not an
absolute path
dpkg: error processing archive
/var/cache/apt/archives/zsh_5.0.7-4_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
dpkg-maintscript-helper: error: original symlink target is not an
absolute path
dpkg: error while cleaning up:
subprocess new post-removal script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/zsh-common_5.0.7-4_all.deb
/var/cache/apt/archives/zsh_5.0.7-4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package. Trying to
recover:
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768897: MBR disklabels also yield destructive pvcreate
FYI: I've just confirmed with partman-lvm 99 (plus whatever libparted is in the last Debian testing weekly ISO) that MBR disklabels using 8e (Linux LVM) as a type code for LUKS are also affected by this. So it's not just GPT. It's arguably even more dangerous for MBR, because the type code space is so small that collisions should be expected, but util-linux's fdisk in MBR mode also provides a 0xda code for "non-FS data", so users in that case may be less tempted to default to the underlying volume type. ---> Drake Wilson -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768090: marked as done (beignet: pow(n), erf(c), tgamma give wrong results)
Your message dated Wed, 19 Nov 2014 21:19:10 +
with message-id
and subject line Bug#768090: fixed in beignet 0.9.3~really.0.8+dfsg-1
has caused the Debian Bug report #768090,
regarding beignet: pow(n), erf(c), tgamma give wrong results
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.)
--
768090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: beignet
Version: 0.9.3~dfsg-1
Severity: serious
Justification: a math library should NOT silently give wrong answers
Control: found -1 0.8-1.1
Control: tags -1 upstream patch
In current beignet (0.8, 0.9.3 and upstream-HEAD):
-pow/pown ignore the sign of their first argument (e.g. pow(-2,3) gives
8 instead of -8)
-erf/erfc diverge (instead of converging to 1 or 0) for arguments above
about 2
-tgamma is actually lgamma, a related but very different function (and
the test suite doesn't notice because it checks against glibc's gammaf,
which is also lgamma, instead of tgammaf)
#!/usr/bin/env python3
#Depends: python3-pyopencl python3-scipy
import pyopencl
import pyopencl.array
import numpy as np
import scipy.special as spfn
import time
ctx=pyopencl.create_some_context()
cq=pyopencl.CommandQueue(ctx)
a1=np.array(-0.95*np.random.rand(1e6)-0.01,dtype=np.float32)
a2=-1000*a1
a3=20*(a1+0.5)
ai=np.array(a3,dtype=np.int32)
aCL1=pyopencl.array.to_device(cq,a1)
aCL2=pyopencl.array.to_device(cq,a2)
aCL3=pyopencl.array.to_device(cq,a3)
aCLi=pyopencl.array.to_device(cq,ai)
bCL=aCL1+1
c=np.array(range(20),dtype=np.float32)/3-2
ci=np.array(c,dtype=np.int32)
cCL=pyopencl.array.to_device(cq,c)
cCLi=pyopencl.array.to_device(cq,ci)
dCL=cCL+1
def approx_erfc(x):
p = 0.3275911
a1 = 0.254829592
a2 = -0.284496736
a3 = 1.421413741
a4 = -1.453152027
a5 = 1.061405429
d = np.exp(-x*x)
t = 1/(1+p*np.abs(x))
r = (a1*t+a2*t*t+a3*t*t*t+a4*t*t*t*t+a5*t*t*t*t*t)*d
return r*np.sign(x)+1-np.sign(x)
erfc_err=np.abs(spfn.erfc(a3)-approx_erfc(a3))
print("x:",c,"\n",ci)
print("erfc:",np.max(erfc_err),np.mean(erfc_err))
f_to_test=[("cos",np.cos),("sin",np.sin),("tan",np.tan),("cosh",np.cosh),("cospi",lambda x:np.cos(np.pi*x)),("tanh",np.tanh),("exp",np.exp),("log",np.log),("sqrt",np.sqrt),("acos",np.arccos),("acosh",np.arccosh),("pow(a[i],c[i])",lambda x,y:x**y),("pown(a[i],d[i])",lambda x,y:x**y),("tgamma",spfn.gamma),("erf",spfn.erf),("erfc",spfn.erfc)]
for f in f_to_test:
for aCL in aCL1,aCL2,aCL3:
fCL=pyopencl.elementwise.ElementwiseKernel(ctx,"float *a,float *b,float *c,int *d","b[i]="+f[0]+("" if f[0] in ("pow(a[i],c[i])","pown(a[i],d[i])","powr(a[i],c[i])") else "(a[i])"))
t0=time.time()
fCL(aCL,bCL,aCL3,aCLi).wait()
t=time.time()-t0
b=bCL.get()
if f[0] in ("pow(a[i],c[i])","powr(a[i],c[i])"):
b0=f[1](aCL.get(),a3)
elif f[0] in ("pown(a[i],d[i])",):
b0=f[1](aCL.get(),ai)
else:
b0=f[1](aCL.get())
abserr=np.abs(b-b0)
relerr=np.abs(b/b0-1)
print(f[0],"abs avg err:",np.nanmean(abserr)," max err:",np.max(abserr),"rel avg err:",np.nanmean(relerr)," max err:",np.max(relerr)," time:",t)
if f[0] in ("erf","erfc","tgamma","pown(a[i],d[i])","pow(a[i],c[i])"):
fCL(cCL,dCL,cCL,cCLi).wait()
if f[0] in ("pow(a[i],c[i])","powr(a[i],c[i])"):
d0=f[1](c,c)
elif f[0] in ("pown(a[i],d[i])",):
d0=f[1](c,ci)
else:
d0=f[1](c)
print(dCL.get(),"\n",d0)
Description:
TODO: Put a short summary on the line above and replace this paragraph
with a longer explanation of this change. Complete the meta-information
with other relevant fields (see below for details). To make it easier, the
information below has been extracted from the changelog. Adjust it or drop
it.
.
beignet (0.9.3~dfsg-2) UNRELEASED; urgency=medium
.
* Fix tgamma,pow,pown,erf,erfc
* Enable debug output in tests
Author: Rebecca N. Palmer
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: ,
Bug:
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded:
Reviewed-By:
Last-Update:
--- beignet-0.9.3~dfsg.orig/utests/builtin_acos_asin.cpp
+++ beignet-0.9.3~dfsg/utests/builtin_acos_asin.cpp
@@ -2,12 +2,13 @@
#include
#include
-#define udebug 0
+#define udebug 1
#define printf_c(...) \
{\
printf("\033[1m
Bug#764930: marked as done (beignet: FTBFS - uses versioned llvm commands, but unversioned build dependency)
Your message dated Wed, 19 Nov 2014 21:19:10 +
with message-id
and subject line Bug#764930: fixed in beignet 0.9.3~really.0.8+dfsg-1
has caused the Debian Bug report #764930,
regarding beignet: FTBFS - uses versioned llvm commands, but unversioned build
dependency
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.)
--
764930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: beignet
Version: 0.8-1.1
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.
[...]
[ 0%] Generating ocl_memcpy.ll.bc
cd
/srv/jenkins-slave/workspace/sid-goto-cc-beignet/beignet-0.8/obj-x86_64-linux-gnu/backend/src
&& rm -f ocl_memcpy.ll.bc
cd
/srv/jenkins-slave/workspace/sid-goto-cc-beignet/beignet-0.8/obj-x86_64-linux-gnu/backend/src
&& llvm-as-3.4 -o ocl_memcpy.ll.bc
/srv/jenkins-slave/workspace/sid-goto-cc-beignet/beignet-0.8/backend/src/ocl_memcpy.ll
/bin/sh: 1: llvm-as-3.4: not found
backend/src/CMakeFiles/beignet.bc.dir/build.make:73: recipe for target
'backend/src/ocl_memcpy.ll.bc' failed
make[3]: *** [backend/src/ocl_memcpy.ll.bc] Error 127
The full build log is attached. The problem appears to be that
debian/patches/versioned-llvm-tools introduces the versioned commands, but
debian/control does not build-depend on a fixed version. This needs to be made
consistent.
Best,
Michael
beignet-build-log.txt.gz
Description: application/gunzip
pgp_AV7_mhX7M.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: beignet
Source-Version: 0.9.3~really.0.8+dfsg-1
We believe that the bug you reported is fixed in the latest version of
beignet, 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 764...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated beignet 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, 19 Nov 2014 19:52:26 +0100
Source: beignet
Binary: beignet-dev beignet
Architecture: source
Version: 0.9.3~really.0.8+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers
Changed-By: Andreas Beckmann
Description:
beignet- OpenCL library for Intel Ivy Bridge GPUs
beignet-dev - Intel OpenCL library
Closes: 764930 767387 768090
Changes:
beignet (0.9.3~really.0.8+dfsg-1) unstable; urgency=medium
.
[ Andreas Beckmann ]
* Set Maintainer to "Debian OpenCL Maintainers" with Simon's permission.
* Add Simon Richter, Rebecca N. Palmer and myself to Uploaders.
* Repack upstream tarball to remove non-distributable Len(n)a images and
CC-BY-NC-SA licensed parts from the test suite. (Closes: #767387)
* 0001-use-env-to-set-environment-variables-for-GBE_BIN_GEN.patch: New, fix
FTBFS of "~dfsg" versions in pbuilder etc.
- Backport patch to 0.8.
* Import debian/ packaging history into GIT. Add Vcs-* URLs.
* Update Homepage.
.
[ Rebecca N. Palmer ]
* Build-Depends: clang-3.4, lib{clang,llvm}-3.4-dev. (Closes: #764930)
* patches/versioned-llvm-tools: Fix one more unversioned use of clang.
* Skip-deleted-tests.patch: New. Skip tests removed in the dfsg version.
* Replace broken pow(n), rootn, erf(c), tgamma. (Closes: #768090)
* Document in the description what hardware this version supports.
Checksums-Sha1:
9f1f617f2f3a9fc1792747760c5d2c946aceedc9 2538
beignet_0.9.3~really.0.8+dfsg-1.dsc
60c577b192c415af1d74f04972c00b0b4e5862a5 407316
beignet_0.9.3~really.0.8+dfsg.orig.tar.xz
1225e34970fadd4db2c77e140ee053378094975f 58224
beignet_0.9.3~really.0.8+dfsg-1.debian.tar.xz
Checksums-Sha256:
c33e7bef033d85524530b0bc6f10cbba96d06b0ffcfea8c202fa005daccf492d 2538
beignet_0.9.3~really.0.8+dfsg-1.dsc
6929ba7fe07de39d7b815b71e9b930b6c8a579631bf1181424cad74765e92954 407316
beignet_0.9.3~really.0.8+dfsg.orig.tar.xz
cd417759b55844e52c171f8456d3fa9357154acc8b0c47b42bfa5ac2a90a0a37 58224
beignet_0.9.3~really.0.8+dfsg-1.debian.tar.xz
Files:
853f2ded8b820da9bf3e6b609c3a487c 2538 libs extra
beignet_0.9
Bug#767387: marked as done (beignet: Non-free files in test suite)
Your message dated Wed, 19 Nov 2014 21:19:10 +
with message-id
and subject line Bug#767387: fixed in beignet 0.9.3~really.0.8+dfsg-1
has caused the Debian Bug report #767387,
regarding beignet: Non-free files in test suite
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.)
--
767387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: beignet
Version: 0.8-1.1
Severity: serious
Justification: Policy 2.1
Control: tags -1 patch upstream
X-Debbugs-CC: pkg-opencl-de...@lists.alioth.debian.org
The beignet test suite contains three images derived from Lenna (
kernels/lenna128x128.bmp kernels/compiler_box_blur_float_ref.bmp
kernels/compiler_box_blur_ref.bmp ), which is non-distributable (
https://bugs.debian.org/758442 ).
It also contains a number of OpenCL kernels and expected outputs stated
in utests/compiler_shader_toy.cpp to be derived from shaders on
Shadertoy ( kernels/compiler_chocolux.cl
kernels/compiler_chocolux_ref.bmp kernels/compiler_clod.cl
kernels/compiler_clod_function_call.cl kernels/compiler_clod_ref.bmp
kernels/compiler_julia.cl kernels/compiler_julia_function_call.cl
kernels/compiler_julia_no_break.cl
kernels/compiler_julia_no_break_ref.bmp kernels/compiler_julia_ref.bmp
kernels/compiler_mandelbrot.cl kernels/compiler_mandelbrot_alternate.cl
kernels/compiler_mandelbrot_alternate_ref.bmp
kernels/compiler_mandelbrot_ref.bmp kernels/compiler_menger_sponge.cl
kernels/compiler_menger_sponge_no_shadow.cl
kernels/compiler_menger_sponge_no_shadow_ref.bmp
kernels/compiler_menger_sponge_ref.bmp kernels/compiler_nautilus.cl
kernels/compiler_nautilus_ref.bmp kernels/compiler_ribbon.cl
kernels/compiler_ribbon_ref.bmp ), with no explicitly stated license.
These particular shaders are no longer on Shadertoy, but its default
license and that author's usual one (
https://www.shadertoy.com/user/iq/sort=name ) is CC-BY-NC-SA, which is
not DFSG-free.
Since we don't run the test suite in the build anyway (servers typically
don't have the required GPU hardware) deleting all of these should be
harmless; if the second group do turn out to have permission, they can
be added back later.
--- End Message ---
--- Begin Message ---
Source: beignet
Source-Version: 0.9.3~really.0.8+dfsg-1
We believe that the bug you reported is fixed in the latest version of
beignet, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 767...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated beignet 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, 19 Nov 2014 19:52:26 +0100
Source: beignet
Binary: beignet-dev beignet
Architecture: source
Version: 0.9.3~really.0.8+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers
Changed-By: Andreas Beckmann
Description:
beignet- OpenCL library for Intel Ivy Bridge GPUs
beignet-dev - Intel OpenCL library
Closes: 764930 767387 768090
Changes:
beignet (0.9.3~really.0.8+dfsg-1) unstable; urgency=medium
.
[ Andreas Beckmann ]
* Set Maintainer to "Debian OpenCL Maintainers" with Simon's permission.
* Add Simon Richter, Rebecca N. Palmer and myself to Uploaders.
* Repack upstream tarball to remove non-distributable Len(n)a images and
CC-BY-NC-SA licensed parts from the test suite. (Closes: #767387)
* 0001-use-env-to-set-environment-variables-for-GBE_BIN_GEN.patch: New, fix
FTBFS of "~dfsg" versions in pbuilder etc.
- Backport patch to 0.8.
* Import debian/ packaging history into GIT. Add Vcs-* URLs.
* Update Homepage.
.
[ Rebecca N. Palmer ]
* Build-Depends: clang-3.4, lib{clang,llvm}-3.4-dev. (Closes: #764930)
* patches/versioned-llvm-tools: Fix one more unversioned use of clang.
* Skip-deleted-tests.patch: New. Skip tests removed in the dfsg version.
* Replace broken pow(n), rootn, erf(c), tgamma. (Closes: #768090)
* Document in the description what hardware this version supports.
Checksums-Sha1:
9f1f617f2f3a9fc1792747760c5d2c946aceedc9 2538
beignet_0.9.3~really.0.8+dfsg-1.
Bug#752514: libfftw3 SIGILL on armhf
On Wed, Nov 19, 2014 at 08:37:15PM +, Edmund Grimley Evans wrote:
> Finding out which armhf machines have NEON is depressingly difficult,
> but I think that abel ("Marvell Armada 370/XP CPU @ 1.6GHz on a
> Marvell MV78460 SoC Development Board (ARM v7)") doesn't have NEON and
> the others do, so it makes sense.
Well if it is Cortex-A7, A8, A12, A15 or A17, it has neon. If it
is A5 or A9 it probably has it unless it is made by nvidia and then it
doesn't. If it is not a Cortex, then if it marvell it does not have neon,
but if it is apple or qualcomm it seems it does. At least that's my
experience so far.
Sure would be nice if ARM had NOT made VFP and neon optional components
on the A5 and A9.
> I'd say it's serious.
>
> And I'd recommend throwing out the signal-catching code and just using
> auxv.
--
Len Sorensen
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768691: marked as done (beignet: FTBFS in jessie: /bin/sh: 1: llvm-as-3.4: not found)
Your message dated Wed, 19 Nov 2014 21:19:10 +
with message-id
and subject line Bug#764930: fixed in beignet 0.9.3~really.0.8+dfsg-1
has caused the Debian Bug report #764930,
regarding beignet: FTBFS in jessie: /bin/sh: 1: llvm-as-3.4: not found
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.)
--
764930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: beignet
Version: 0.8-1.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for 'utests/CMakeFiles/utest_generator.dir/build'.
> make[3]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_report
> /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles
> Scanning dependencies of target pch_object
> make[3]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> make -f backend/src/CMakeFiles/pch_object.dir/build.make
> backend/src/CMakeFiles/pch_object.dir/build
> [ 0%] [ 0%] [ 0%] make[3]: Entering directory
> '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_report
> /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles 15
> [ 0%] Generating ocl_memcpy.ll.bc
> Built target utest_generator
> Generating ocl_barrier.ll.bc
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/backend/src && rm -f ocl_barrier.ll.bc
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/backend/src && rm -f ocl_memcpy.ll.bc
> [ 1%] cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/backend/src && llvm-as-3.4 -o
> ocl_barrier.ll.bc /«PKGBUILDDIR»/backend/src/ocl_barrier.ll
> Generating ocl_memset.ll.bc
> /bin/sh: 1: llvm-as-3.4: not found
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/backend/src && llvm-as-3.4 -o
> ocl_memcpy.ll.bc /«PKGBUILDDIR»/backend/src/ocl_memcpy.ll
> make[3]: *** [backend/src/ocl_barrier.ll.bc] Error 127
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/08/beignet_0.8-1.1_jessie.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 ---
--- Begin Message ---
Source: beignet
Source-Version: 0.9.3~really.0.8+dfsg-1
We believe that the bug you reported is fixed in the latest version of
beignet, 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 764...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated beignet 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, 19 Nov 2014 19:52:26 +0100
Source: beignet
Binary: beignet-dev beignet
Architecture: source
Version: 0.9.3~really.0.8+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers
Changed-By: Andreas Beckmann
Description:
beignet- OpenCL library for Intel Ivy Bridge GPUs
beignet-dev - Intel OpenCL library
Closes: 764930 767387 768090
Changes:
beignet (0.9.3~really.0.8+dfsg-1) unstable; urgency=medium
.
[ Andreas Beckmann ]
* Set Maintainer to "Debian OpenCL Maintainers" with Simon's permission.
* Add Simon Richter, Rebecca N. Palmer and myself to Uploaders.
* Repack upstream tarball to remove non-distributable Len(n)a images and
CC-BY-NC-SA licensed parts from the test suite. (Closes: #767387)
* 0001-use-env-to-set-environment-variables-for-GBE_BIN_GEN.patch: New, fix
FTBFS of "~dfsg" versions in pbuilder etc.
- Backport patch to 0.8.
* Import debian/ packaging history into GIT. Add Vcs-* URLs.
* Update Homepage.
.
[ Rebecca N. Palmer ]
* Build-Depends: clang-3.4, lib{clang,llvm}-3.4-dev. (Closes: #764930
Bug#768332: About aschi.debian.org (Was: Builds on asachi.debian.org, patch)
Anton Gladky wrote: tags 768332 +patch thanks Hi, I have just built lightsparc on asachi.debian.org successfully. But it seems, it is a armhf. It seems that the MOTD and documentation could do with some work. The motd on asachi indeed confusingly announces the system as as the "Debian armhf porterbox". I guess it's autogenerated by some DSA script. the documentation at https://dsa.debian.org/doc/schroot/ does tell people how to get a list of chroots but if you don't know that the porterbox offers chroots for multiple architectures you are likely to skip that step. The "outer system" on asachi is an arm64 kernel with an armhf userland. AIUI this is because DSA preffer to have machines running stable and there is no arm64 stable yet. It seems the default chroots are also armhf (I guess again there is a DSA script that makes them follow the userland architecture of the "outer system"), to get an arm64 chroot session you need to do schroot -b -c sid_arm64-dchroot -n (replacing with the name of the session). Upstream fix for this bug is here [1]. [1] https://github.com/lightspark/lightspark/commit/3d55371ee7a2524274ff3cdc546c845203ccd8ea.patch Anton -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770084: spamassassin: Spamassassin not installable
On 19/11/2014 12:12, intrigeri wrote:
> Hi,
>
> does `sudo netcat -l 783' work (as in, does it result in the netcat
> process successfully listening on TCP port 783?)
On a terminal I do :
# netcat -l 783
and on a second I do :
# ss -tnlp|grep 783
LISTEN 0 1 *:783
*:* users:(("netcat",pid=31001,fd=3))
which show that netcat successfully listen on TCP port 783
>
> Cheers,
> --
> intrigeri
Regards
--
Francois Mescam
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768496: [Pkg-sysvinit-devel] Bug#768496: (no subject)
[ValdikSS] > When this will be pushed to testing? According to https://packages.qa.debian.org/s/sysvinit.html >, it should enter testing in 4 days. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770222: icecast2: on-connect scripts: icecast can leak output to attentive sources
Package: icecast2 Version: 2.4.0-1~bpo70+1 Severity: critical Tags: security upstream Justification: root security hole Icecast can leak the output of on-connect scripts to source clients by sending their output via HTTP. This information-disclosure can contain confidential information if the administrator of the icecast server did not explicitly check the output of their scripts. Information contained can include passwords or script interna helping to possibly exploit weak scripts. This bug has been reported upstream [1] which fixed it quickly in the bugfix release 2.4.1 [2]. Please consider upgrading to the latest upstream version. [1] https://trac.xiph.org/ticket/2089 [2] http://icecast.org/news/icecast-release-2_4_1/ -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.41-042stab094.7 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icecast2 depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38+deb7u6 ii libcurl3-gnutls7.26.0-1+wheezy11 ii libogg01.3.0-4 ii libspeex1 1.2~rc1-7 ii libtheora0 1.1.1+dfsg.1-3.1 ii libvorbis0a1.3.2-1.3 ii libxml22.8.0+dfsg1-7+wheezy2 ii libxslt1.1 1.1.26-14.1 icecast2 recommends no packages. Versions of packages icecast2 suggests: pn ices2 -- Configuration Files: /etc/default/icecast2 changed [not included] /etc/icecast2/icecast.xml [Errno 13] Keine Berechtigung: u'/etc/icecast2/icecast.xml' -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752514: libfftw3 SIGILL on armhf
Kamal Mostafa :
> Edmund et al., I would appreciate your expertise here... Does it also appear
> to
> you that my minimodem (0.20-1) failure[0] could be caused by the fftw3 "NEON
> is
> perhaps broken" bug? Does it make sense that abel.d.o would be affected by
> it, but harris and asachi would not?
Finding out which armhf machines have NEON is depressingly difficult,
but I think that abel ("Marvell Armada 370/XP CPU @ 1.6GHz on a
Marvell MV78460 SoC Development Board (ARM v7)") doesn't have NEON and
the others do, so it makes sense.
> All: Should the severity of the libfftw3 bug #767138 be elevated to "serious"?
I'd say it's serious.
And I'd recommend throwing out the signal-catching code and just using
auxv.
Edmund
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752514: libfftw3 SIGILL on armhf
I'm investigating an armhf FTBFS of my package 'minimodem'[0], which I now suspect might be caused by this libfftw3 bug in unstable: #767138 "fftw3: runtime detection of NEON is perhaps broken" https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767138 There, Edmund points out that "#752514 ruby-fftw3: FTBFS on armhf" [1] is possibly caused by that fftw3 bug. But Cédric notes that he was unable to reproduce the ruby failure on harris.debian.org. I am seeing exactly the same issues with minimodem: On the armhf buildd builders (only), minimodem compiles fine but then all its test cases fail. But when I try it on harris.d.o (or asachi.d.o), I cannot reproduce any problem. But I've just discovered that I *can* reproduce the minimodem crash on abel.debian.org, and it points to libfftw3: Linux abel 3.16-0.bpo.2-armmp-lpae #1 SMP Debian 3.16.3-2~bpo70+1 (2014-09-21) armv7l GNU/Linux (sid_armhf-dchroot) Program received signal SIGILL, Illegal instruction. 0xb6f47e9a in ?? () from /usr/lib/arm-linux-gnueabihf/libfftw3f.so.3 For comparison, harris and asachi (where no problem occurs) are: Linux harris 3.2.0-4-mx5 #1 Debian 3.2.63-2+deb7u1 armv7l GNU/Linux (sid_armhf-dchroot) Linux asachi 3.16-2-arm64 #1 SMP Debian 3.16.3-2 (2014-09-20) armv8l GNU/Linux (sid_armhf-dchroot) Edmund et al., I would appreciate your expertise here... Does it also appear to you that my minimodem (0.20-1) failure[0] could be caused by the fftw3 "NEON is perhaps broken" bug? Does it make sense that abel.d.o would be affected by it, but harris and asachi would not? Cédric, you might want to re-try your ruby-fftw3 build test on abel.debian.org and consider re-opening #752514 [1]. Hector, could this situation result in a possible inconsistency among the armhf buildd's? (Or at least, among the porterbox armhf chroots)? All: Should the severity of the libfftw3 bug #767138 be elevated to "serious"? Thanks in advance for your help, -Kamal [0] #769974 "minimodem: FTBFS on armhf" https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769974 To replicate the minimodem failure for debugging: (sid_armhf-dchroot)$ echo hello | src/minimodem --tx -f /tmp/foo.wav 1200 # this does not call libfftw3 (sid_armhf-dchroot)$ gdb --args src/minimodem --rx -f /tmp/foo.wav 1200 ... Program received signal SIGILL, Illegal instruction. 0xb6f47e9a in ?? () from /usr/lib/arm-linux-gnueabihf/libfftw3f.so.3 [1] #752514 "ruby-fftw3: FTBFS on armhf" https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752514
Bug#769981: closed by "Bernhard R. Link" (reply to 769...@bugs.debian.org) (Re: Bug#769981: reprepro complaining about 'all' architecture)
On Nov 19, 2014, at 12:45 PM, Debian Bug Tracking System wrote: > - delete "all" from all Architecture: lines in conf/distributions > - run reprepro --delete clearvanished (reprepro should tell you to do > this if you try to run it) So for my packages that will run on any platform, should they be architecture “any” then? Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Builds on asachi.debian.org, patch
Processing commands for cont...@bugs.debian.org: > tags 768332 +patch Bug #768332 [lightspark] lightspark FTBFS on arm64. fatal error: llvm/IR/Verifier.h: No such file or directory Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 768332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768332 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#768332: Builds on asachi.debian.org, patch
tags 768332 +patch thanks Hi, I have just built lightsparc on asachi.debian.org successfully. But it seems, it is a armhf. Upstream fix for this bug is here [1]. [1] https://github.com/lightspark/lightspark/commit/3d55371ee7a2524274ff3cdc546c845203ccd8ea.patch Anton -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765477: HTML-Mason 1.56 shipped with patch
-=| Kevin Falcone, 19.11.2014 12:22:17 -0500 |=- > This is just a note that Dave Rolsky made an official release of > HTML-Mason using the patch I originally proposed in this ticket (and > that I believe has been merged into the package already). Thanks. > It does contain one additional warning squash for the test suite. > > https://metacpan.org/changes/distribution/HTML-Mason > > final version of the patch > > https://github.com/jibsheet/HTML-Mason/commit/59a9d7fdbc8e53c569109e35ebac52ad90e9daef We'll include that when we update the package, probably after the release of Jessie. The warning is not yet visible in the build logs since we haven't put explicit build-dependency on libcgi-pm-perl (which is version 4.09), relying on the CGI.pm version 3.65, included in the perl package, which doesn't complain about param() usage in list context. I hope this is not confusing :) -- dam signature.asc Description: Digital signature
Bug#767067: No twitter timeline update
Le mercredi 19 novembre 2014 06:29:27 vous avez écrit : > Hello Xavier, > > first sorry for my late answer. > > What can I do? > Which infos you are needed? All informations that can be specific to your config. Sadly, choqok doesn't offer a lot of debugging message. But, what is the Latest update displayed (in the top left corner). If you restart the application, does it change ? If you go in the Settings → Account, then select the Twitter account and click on modify, do you see a green dot next to the text "Authenticated" ? If you click on "Authenticate with Twitter" does it work ? Does the timelines are updated again ? -- Xavier Claude cont...@xavierclaude.be signature.asc Description: This is a digitally signed message part.
Bug#769693: marked as done (libjogl2-java: FTBFS on arm64)
Your message dated Wed, 19 Nov 2014 19:17:56 +0100
with message-id <20141119181754.ga19...@ugent.be>
and subject line Re: Bug#769693: Please giveback libjogl2-java
has caused the Debian Bug report #769693,
regarding libjogl2-java: FTBFS on arm64
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.)
--
769693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjogl2-java
Version: 2.2.4+dfsg-1
Severity: serious
Your package FTBFS on arm64, ppc64el and s390x. Below is an excerpt from the
arm64 build log
Property "nativewindow_x11.useLibJAWT" has not been set
[echo] nativewindow_x11.useLibJAWT ${nativewindow_x11.useLibJAWT}
[echo] Compiling nativewindow_x11
[echo] java.lib.dir.platform:
/usr/lib/jvm/java-7-openjdk-arm64/jre/../jre/lib/aarch64
[cc] 4 total files to be compiled.
[cc] gcc -include
/usr/share/gluegen2/make/stub_includes/platform/glibc-compat-symbols.h -c
-fno-rtti -fPIC -D__unix__ -D__X11__ -DNDEBUG
-I/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/build/nativewindow/gensrc/native
-I/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/build/nativewindow/gensrc/native/X11
-I/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/src/nativewindow/native/x11
-I/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/src/nativewindow/native
-I/usr/lib/jvm/java-7-openjdk-arm64/include
-I/usr/lib/jvm/java-7-openjdk-arm64/include/linux
-I/usr/share/gluegen2/make/stub_includes/platform
/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/src/nativewindow/native/NativewindowCommon.c
/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/src/nativewindow/native/x11/Xmisc.c
/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/build/nativewindow/gensrc/native/X11/X11Lib_JNI.c
/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/src/nativewindow/native/x11/XineramaHelper.c
[cc] cc1: warning: command line option '-fno-rtti' is valid for
C++/ObjC++ but not for C
[cc] cc1: warning: command line option '-fno-rtti' is valid for
C++/ObjC++ but not for C
[cc] cc1: warning: command line option '-fno-rtti' is valid for
C++/ObjC++ but not for C
[cc]
/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/build/nativewindow/gensrc/native/X11/X11Lib_JNI.c:
In function 'Java_jogamp_nativewindow_x11_X11Lib_XSynchronize__JZ':
[cc]
/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/build/nativewindow/gensrc/native/X11/X11Lib_JNI.c:257:8:
warning: assignment makes integer from pointer without a cast
[cc]_res = XSynchronize((Display *) (intptr_t) display, (Bool) onoff);
[cc] ^
[cc] cc1: warning: command line option '-fno-rtti' is valid for
C++/ObjC++ but not for C
[cc] Starting link
[cc] gcc -static-libgcc -shared -o libnativewindow_x11.so
NativewindowCommon.o Xmisc.o X11Lib_JNI.o XineramaHelper.o -lX11 -lXxf86vm
-lXrender
[cc] /usr/bin/ld: libnativewindow_x11.so: No symbol version section for
versioned symbol `memcpy@GLIBC_2.0'
[cc] /usr/bin/ld: final link failed: Nonrepresentable section on output
[cc] collect2: error: ld returned 1 exit status
[ant] Exiting
/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/make/build-nativewindow.xml.
BUILD FAILED
The other two look much the same
This seems like some kind of screwup related to specifying a specific and old
symbol version that doesn't exist on more recent ports but i'm not an expert.
--- End Message ---
--- Begin Message ---
Hi,
On Tue, Nov 18, 2014 at 05:40:26PM +0100, gregor herrmann wrote:
> > Hmmm... I installed the build-deps into an arm64 sid chroot on asachi
> > (arm64 porterbox) to take a look, but it seems to build okay now.
> > Am I missing something, or can we try to run this through the buildd again?
>
> Hmmm … do we have an idea why it failed twice (on two separate
> machines) on 2014-11-15 and why it passes now an a third one?
>
> I guess the buildd people would be interesting in the reasons for yet
> another giveback :)
This time it built fine on the same buildd as last time. I'm not sure what
changed...
Cheers,
Ivo--- End Message ---
Bug#767653: libopenni-sensor-pointclouds0, libopenni-sensor-primesense0: modifying files from another package: /var/lib/ni/modules.xml
Package: libopenni-sensor-pointclouds0,libopenni-sensor-primesense0 Followup-For: Bug #767653 Hi, I've pushed a patch to [1] to fix this. Would be great if a DD could upload it. [1] http://anonscm.debian.org/git/pkg-multimedia/openni.git -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#769981: marked as done (reprepro complaining about 'all' architecture)
Your message dated Wed, 19 Nov 2014 18:19:01 +0100 with message-id <20141119171900.ga2...@client.brlink.eu> and subject line Re: Bug#769981: reprepro complaining about 'all' architecture has caused the Debian Bug report #769981, regarding reprepro complaining about 'all' architecture 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.) -- 769981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: reprepro Version: 4.12.5-1 Severity: serious Justification: Policy 5.6.8 Dear Maintainer, I tried to include a package in my existing custom apt repository, and now all it does is complain about the 'all' architecture, which is apparently a valid architecture. https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture bear:/var/www/apt# reprepro list wheezy Error: Distribution wheezy contains an architecture called 'all'. There have been errors! So now I cannot update my repository. This worked previously, and I do not understand the nature of the complaint. It is not providing sufficient detail, and my inquiries on the debian-user list go unanswered. I am not sure how to proceed. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-486 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reprepro depends on: ii libarchive12 3.0.4-3+nmu1 ii libbz2-1.0 1.0.6-4 ii libc6 2.13-38+deb7u4 ii libdb5.1 5.1.29-5 ii libgpg-error0 1.10-3.1 ii libgpgme11 1.2.0-1.4+deb7u1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages reprepro recommends: ii apt 0.9.7.9+deb7u5 Versions of packages reprepro suggests: pn gnupg-agent pn inoticoming pn lzip ii lzma 9.22-2 ii xz-utils [lzma] 5.1.1alpha+20120614-2 -- no debconf information --- End Message --- --- Begin Message --- * Michael P. Soulier [141118 03:57]: > I tried to include a package in my existing custom apt repository, and now all > it does is complain about the 'all' architecture, which is apparently a valid > architecture. > > https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture It is and it is not. "all" means something like "all architectures", i.e. not limiting a package to one repository. But you cannot have a Debian installation being architecture "all". > bear:/var/www/apt# reprepro list wheezy > Error: Distribution wheezy contains an architecture called 'all'. > There have been errors! > > So now I cannot update my repository. This worked previously, and I do not > understand the nature of the complaint. It is not providing sufficient detail, > and my inquiries on the debian-user list go unanswered. I am not sure how to > proceed. - delete "all" from all Architecture: lines in conf/distributions - run reprepro --delete clearvanished (reprepro should tell you to do this if you try to run it) Bernhard R. Link -- F8AC 04D5 0B9B 064B 3383 C3DA AFFC 96D1 151D FFDC--- End Message ---
Bug#768703: marked as done (chemfp: FTBFS in jessie: build-dependency not installable: python-unit)
Your message dated Wed, 19 Nov 2014 17:33:47 + with message-id and subject line Bug#768703: fixed in chemfp 1.1p1-2.1 has caused the Debian Bug report #768703, regarding chemfp: FTBFS in jessie: build-dependency not installable: python-unit 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.) -- 768703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: chemfp Version: 1.1p1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > ┌──┐ > │ Install chemfp build dependencies (apt-based resolver) > │ > └──┘ > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > 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: > sbuild-build-depends-chemfp-dummy : Depends: python-unit but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/chemfp_1.1p1-2_jessie.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 --- --- Begin Message --- Source: chemfp Source-Version: 1.1p1-2.1 We believe that the bug you reported is fixed in the latest version of chemfp, 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrey Rahmatullin (supplier of updated chemfp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 14 Nov 2014 21:55:00 +0500 Source: chemfp Binary: python-chemfp Architecture: source Version: 1.1p1-2.1 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrey Rahmatullin Description: python-chemfp - cheminformatics fingerprints file formats and tools Closes: 768703 Changes: chemfp (1.1p1-2.1) unstable; urgency=medium . * Non-maintainer upload. * Drop unnecessary build dependency on python-unit (Closes: #768703). Checksums-Sha1: e6b5011f641b22317b6ca0fbbdbacd31a7e00fcf 1966 chemfp_1.1p1-2.1.dsc 480056568fad9870aae7b07fc5c7bbcf826e8d23 6544 chemfp_1.1p1-2.1.debian.tar.xz Checksums-Sha256: 3d79a39636c95ab83cf350a613455c042d32402991418b6ff1250028ba9aab28 1966 chemfp_1.1p1-2.1.dsc b05dc3dab3cba01d842cb6682a9ca9aed88810504698d59ce415365f2811c8b5 6544 chemfp_1.1p1-2.1.debian.tar.xz Files: cead51093f15f381b20919cd9ccd6469 1966 science optional chemfp_1.1p1-2.1.dsc c0308964557c0e370cc3bfcf7d6edff7 6544 science optional chemfp_1.1p1-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUZjYXAAoJEDNi9wMaSZLhkqAQAKS85JJINfchQPTwF8SLKssT IBRRmSX8vj19cxELojZJIXB4r9iv7q2hyTgntA4Q8xa2ceShZ7HVtgApyXY88Rn2 fjGbV5PLXP96IzT0Srb8lZMp2StMb4o0OpQwK9g2rhb369vPnykyKvGz8pmWFuMW k0d+9bFzbOcBfNOiaFYLx7mhfAumNeso2UdPz1aIDYuFpC7fH5qUJ/cljb1spF6h mGHlTGia1ppz7UTWXGon/7gXU/ZImCCDLwfcLs9mZ8j6jRSSCSAmQvjWqSEFOaU8 bGmySibe9j2ttTLdmrMEFw7UW3DVh9SXm2OIygRIR4caKxTU6lCkMQpZkhuEGOmO 6PUC6gkpskSC5oc+tOFpMuYnoiNunJU5QZ7txZrNAn5Y/A5xxOL9378p1/lgPQNG UxdXPESimL2uB/5FchPU9xaHlapMTEnYWQ473ruKO5jyEM5sJjgOzhscUekP+3ne dvQ6osGX2ha+
Bug#765477: HTML-Mason 1.56 shipped with patch
This is just a note that Dave Rolsky made an official release of HTML-Mason using the patch I originally proposed in this ticket (and that I believe has been merged into the package already). It does contain one additional warning squash for the test suite. https://metacpan.org/changes/distribution/HTML-Mason final version of the patch https://github.com/jibsheet/HTML-Mason/commit/59a9d7fdbc8e53c569109e35ebac52ad90e9daef -kevin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: found 762690 in 4.0.2.GA-3
Processing commands for cont...@bugs.debian.org:
> found 762690 4.0.2.GA-3
Bug #762690 {Done: Emmanuel Bourg }
[libhibernate-validator-java] libhibernate-validator-java: affected by
CVE-2014-3558
Marked as found in versions libhibernate-validator-java/4.0.2.GA-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
762690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762690
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#770035: [Mlt-devel] Bug#770035: kdenlive: Processed videos have image pauses or accelerations while sound goes well
No. I do not know how to reproduce the problem. The bug reporter needs to narrow down the problem. Is it something in the project, something related specifically to those source files, or something related to that combination of MLT and Libav versions? I do consider the usage of the latest versions of Libav and FFmpeg with MLT somewhat experimental. On Wed, Nov 19, 2014 at 6:03 AM, Patrick Matthäi wrote: > Hi Dan, > > do you have an idea to http://bugs.debian.org/770035 ? > > Am 19.11.2014 um 14:54 schrieb Javier Ortega Conde (Malkavian): > >Could you retest it with the libmlt*, mlt*, melt* packages from >> experimental (not jessie/sid)? >> > > Done, and problem persists. > > >
Bug#770060: marked as done (backbone: FTBFS: Test failures)
Your message dated Wed, 19 Nov 2014 16:49:36 + with message-id and subject line Bug#770060: fixed in backbone 0.9.10-2 has caused the Debian Bug report #770060, regarding backbone: FTBFS: Test failures 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.) -- 770060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: backbone Version: 0.9.10-1 Severity: serious >From my pbuilder build log (on amd64): ... debian/rules build test -x debian/rules mkdir -p "." Scanning upstream source for new/changed copyright notices... licensecheck -c '.*' -r --copyright -i '^docs/images/.*\.(jpg|png)|debian/(changelog|copyright(|_hints|_newhints))' -l '9' * | /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints 7 combinations of copyright and licensing found. No new copyright notices found - assuming no news is good news... touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft coffee test/*.coffee passed 4 tests phantomjs test/vendor/runner.js test/index.html?noglobals=true Assertion Failed: Backbone.Model: defaults Failed assertion: expected: 2, but was: null Failed assertion: expected: 4, but was: null Took 2428ms to run 700 tests. 698 passed, 2 failed. debian/rules:58: recipe for target 'debian/stamp-build' failed make: *** [debian/stamp-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler --- End Message --- --- Begin Message --- Source: backbone Source-Version: 0.9.10-2 We believe that the bug you reported is fixed in the latest version of backbone, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated backbone 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: Wed, 19 Nov 2014 17:14:00 +0100 Source: backbone Binary: libjs-backbone node-backbone Architecture: source all Version: 0.9.10-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Description: libjs-backbone - some Backbone for JavaScript applications - browser library node-backbone - some Backbone for JavaScript applications - Node module Closes: 770060 Changes: backbone (0.9.10-2) unstable; urgency=medium . * Add patch cherry-picked upstream to fix testsuite to pass with Underscore 1.5.0 and newer. Closes: bug#770060. Thanks to Daniel Schepler and Matt Kraai. Checksums-Sha1: 8ae550f09ec834d4ca8a06b7b99ee9a7ff78d3f8 2248 backbone_0.9.10-2.dsc 32e948b6bf4b9df502f441f34064d277161463ba 6904 backbone_0.9.10-2.debian.tar.xz 201f8706370f211b3bfcae5fb12acb6dbf2be1fa 73432 libjs-backbone_0.9.10-2_all.deb 0345f55a43bce05de5ffb19e35a278aa0c3e2023 50010 node-backbone_0.9.10-2_all.deb Checksums-Sha256: 564afb4f7a738a535c89cd002c1a292a57c216765b723c7357171d8ec08f7bfc 2248 backbone_0.9.10-2.dsc 31afe7cf3aa6e747c38a3a618bfd31b20f9d0be88c32d9bee99d290f4e12157d 6904 backbone_0.9.10-2.debian.tar.xz 0187854e327cd8c29618363f941c931d5308799d1c68a4155205dc98f31fa1cc 73432 libjs-backbone_0.9.10-2_all.deb 1587793fb9af283f615f42f50484e6055dbbc9ebcebad8f21ec34d4d307efea4 50010 node-backbone_0.9.10-2_all.deb Files: 5569e6206a0d56d758c341fb54d7e412 2248 web optional backbone_0.9.10-2.dsc 895b84a2f9a92cf5631e1cee9629705f 6904 web optional backbone_0.9.10-2.debian.tar.xz b46a63d9a7b9d3436980584f08a80f12 73432 web optional libjs-backbone_0.9.10-2_all.deb ccec7ce7ff3f6ddf2a7c33b31e8d8f0a 50010 web optional node-backbone_0.9.10-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJUbMfnXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5RkUzRTlDMzY2OTFBNjlGRjUzQ0M2ODQy QzdDMzE0NkMxQTAwMTIxAAoJECx8MUbBoAEhYkMP/2+PYtI76c7xUpSc9b96i5QW 1ls9+McHu5cx7NdhP42NZOKsVwCBS16U89EtYIQwYfxlmQdZ23brFmybL/PvdlOW oT0KmCsD5riqBsdn32pWceg8c6AbPlZP8X7uh722BbG1zw5BkqlzlRcKEqaGGcQ3 R+0x8wNxtDiP92sNf+JrjLUGvDZyB3XidfthCkhziB7UEWYq7kem7LXsackG1gAQ rw/tFcj+u6nlAHAf8kSXCdgZpatk0Rb3lp97HyLsbG4oIpvGsBJ0rvYKF5H0VaWz OhWkj3YPK3MVey3AUZHn
Bug#770194: ruby-stringex: FTBFS: Test failures
Source: ruby-stringex Version: 2.5.2-2 Severity: serious >From my pbuilder build log (on amd64): ... === Error: test_vulgar_fractions_conversion: ⅞(GermanYAMLLocalizationTest) I18n::InvalidLocale: :de is not a valid locale /usr/lib/ruby/vendor_ruby/i18n.rb:285:in `enforce_available_locales!' /usr/lib/ruby/vendor_ruby/i18n.rb:150:in `translate' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/backend/i18n.rb:52:in `i18n_translations_for' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/backend/i18n.rb:35:in `block in translations' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/backend/i18n.rb:39:in `yield' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/backend/i18n.rb:39:in `initial_translation' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization.rb:94:in `initial_translation' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization.rb:43:in `translate' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:121:in `translate' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:106:in `block in vulgar_fractions' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:105:in `each' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:105:in `vulgar_fractions' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:58:in `block in translate!' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:57:in `each' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization/converter.rb:57:in `translate!' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/string_extensions.rb:92:in `block in convert_vulgar_fractions' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization.rb:86:in `instance_exec' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/localization.rb:86:in `convert' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/string_extensions.rb:199:in `stringex_convert' /tmp/buildd/ruby-stringex-2.5.2/lib/stringex/string_extensions.rb:91:in `convert_vulgar_fractions' /tmp/buildd/ruby-stringex-2.5.2/test/unit/localization/de_test.rb:115:in `block (2 levels) in ' === ...E === Error: test_assigns_locale_in_i18n_backend(LocalizationTest) I18n::InvalidLocale: :"pt-BR" is not a valid locale /usr/lib/ruby/vendor_ruby/i18n.rb:285:in `enforce_available_locales!' /usr/lib/ruby/vendor_ruby/i18n/config.rb:13:in `locale=' /usr/lib/ruby/vendor_ruby/i18n.rb:35:in `locale=' /tmp/buildd/ruby-stringex-2.5.2/test/unit/localization_test.rb:132:in `test_assigns_locale_in_i18n_backend' 129: 130: assert_equal :en, Stringex::Localization.locale 131: => 132: I18n.locale = other_locale 133: assert_equal other_locale, Stringex::Localization.locale 134: 135: Stringex::Localization.locale = :de === ... ... ... Finished in 5.835713975 seconds. 792 tests, 807 assertions, 0 failures, 305 errors, 0 pendings, 0 omissions, 0 notifications 61.4899% passed 135.72 tests/s, 138.29 assertions/s rake aborted! Command failed with status (1): [ruby -I"lib:lib:test" -I"/usr/lib/ruby/vendor_ruby" "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/unit/**/*_test.rb" ] -e:1:in `' Tasks: TOP => default => test (See full trace by running task with --trace) ERROR: Test "ruby2.1" failed. Exiting. dh_auto_install: dh_ruby --install /tmp/buildd/ruby-stringex-2.5.2/debian/ruby-stringex returned exit code 1 debian/rules:15: recipe for target 'binary' failed make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770193: libglib2.0-0: Failing to compile package libglibc (importing a unstable package on a testing system)
Package: libglib2.0-0 Version: 2.42.0-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** I am running a testing debian system and I would like to upgrade the libglib2.0-0 to the latest from the unstable repo. following the guide (https://wiki.debian.org/DebianUnstable#Can_I_use_sid_packages_on_testing.3F) I have performed the follwing steps: 1 - sudo apt-get build-dep libglib2.0-0 2 - sudo apt-get -b source libglib2.0-0 The compilation gets stuck here and never finishes, my expectation was to be able to install the resulting package with dpkg -i. [...] PASS: gsettings 21 /gsettings/writable-binding PASS: gsettings 22 /gsettings/typesafe-binding PASS: gsettings 23 /gsettings/no-read-binding [ never exits ] The sources.list file used : deb http://ftp.uk.debian.org/debian testing main contrib non-free deb-src http://ftp.uk.debian.org/debian testing main contrib non-free deb http://ftp.uk.debian.org/debian unstable main contrib non-free deb-src http://ftp.uk.debian.org/debian unstable main contrib non-free deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libglib2.0-0 depends on: ii libc6 2.19-13 ii libffi63.1-2 ii libpcre3 1:8.35-3.1 ii libselinux12.3-2 ii multiarch-support 2.19-13 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages libglib2.0-0 recommends: ii libglib2.0-data 2.42.0-2 ii shared-mime-info 1.3-1 ii xdg-user-dirs 0.15-2 libglib2.0-0 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770060: patch
Hi Matt, Quoting Matt Kraai (2014-11-19 15:37:53) > tag 770060 patch > thanks > > Hi, > > I extracted the following patch from upstream, which fixes this > problem: Grat. Thanks! Applying that now... - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#768686: maxima ftbfs due to gcl dependency
Greetings, and thanks for your report! Just to let you know that the issue has been resolved via the migration of gcl 2.6.12. Take care, Michael Gilbert writes: > Hi Camm, > > It looks like you're gcl uploads didn't make it to testing in time for > the freeze, but maxima did. > > Maxima in testing now has an unsatisfiable build dependency on gcl in > unstable. > > I did a rebuild of maxima 5.34.1-2 with gcl 2.6.11-3 from testing, > which seemed to work just fine, but I'm not familiar enough with why > there is so often a need for updating the gcl build-dep in the > package. > > Is it ok to downgrade the dependency to >= 2.6.11-3? > > Best wishes, > Mike > > > > -- Camm Maguirec...@maguirefamily.org == "The earth is but one country, and mankind its citizens." -- Baha'u'llah -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762690: libhibernate-validator-java: affected by CVE-2014-3558
Le 19/11/2014 14:49, Raphael Hertzog a écrit : > Given it fixes an RC bug, will you check with the release team about a > possible exception to the freeze rules? > > I saw you uploaded to experimental, thus I'm wondering if you were going > to try that anyway. Hi Raphael, I uploaded to experimental because the debdiff is 80k lines long and I'm not sure the release team is willing to consider it. I checked that libhibernate3-java still builds fine with this version. I'm confident this is a safe upgrade since libhibernate-validator-java has only one reverse dependency and is never used at runtime by another binary package. So this could go into oldstable/stable/testing but that's not my call. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770060: patch
tag 770060 patch
thanks
Hi,
I extracted the following patch from upstream, which fixes this problem:
Description: Use undefined instead of null in Backport.Model defaults test
Origin: backport,
https://github.com/jashkenas/backbone/commit/8e3c38a19f493f6cf002f9d25c1b5c84aaf6b2f2
Last-Update: 2014-11-19
Index: backbone-0.9.10/test/model.js
===
--- backbone-0.9.10.orig/test/model.js 2013-01-15 12:31:47.0 -0800
+++ backbone-0.9.10/test/model.js 2014-11-19 06:30:48.471307318 -0800
@@ -324,7 +324,7 @@
"two": 2
}
});
-var model = new Defaulted({two: null});
+var model = new Defaulted({two: undefined});
equal(model.get('one'), 1);
equal(model.get('two'), 2);
Defaulted = Backbone.Model.extend({
@@ -335,7 +335,7 @@
};
}
});
-model = new Defaulted({two: null});
+model = new Defaulted({two: undefined});
equal(model.get('one'), 3);
equal(model.get('two'), 4);
});
--
Matt
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: patch
Processing commands for cont...@bugs.debian.org: > tag 770060 patch Bug #770060 [src:backbone] backbone: FTBFS: Test failures Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 770060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770060 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: limit source to firetray, tagging 770182
Processing commands for cont...@bugs.debian.org: > limit source firetray Limiting to bugs with field 'source' containing at least one of 'firetray' Limit currently set to 'source':'firetray' > tags 770182 + pending Bug #770182 [xul-ext-firetray] Incompatible with recent icedove from wheezy-security Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 770182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770182 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: not starting should really be fixed
Processing commands for cont...@bugs.debian.org: > severity 770148 grave Bug #770148 [gnome-logs] gnome-logs doesn't start when launched from gnome-shell Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 770148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770148 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#770186: Incompatible with recent icedove from wheezy-security
Package: xul-ext-sieve Version: 0.2.3d-2~deb7u1 Severity: serious Control: fixed -1 0.2.3d-2 Hi, xul-ext-sieve currently in stable Breaks: icedove (>> 30.0+) Since icedove 31.2.0-1~deb7u1 has been pushed via wheezy-security, the package is currently broken. I’ll propose a package dropping this Breaks via a p-u request to the release team ASAP. Regards David signature.asc Description: Digital signature
Processed: Incompatible with recent icedove from wheezy-security
Processing control commands: > fixed -1 0.2.3d-2 Bug #770186 [xul-ext-sieve] Incompatible with recent icedove from wheezy-security Marked as fixed in versions sieve-extension/0.2.3d-2. -- 770186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770186 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#733974: Bug#769965: minetest: please support init.d scripts and a global configuration file
On 19.11.2014 09:27, Martin Quinson wrote: > On Tue, Nov 18, 2014 at 11:16:51PM +0100, Markus Koschany wrote: >> >> I agree that https://bugs.debian.org/733974 is a problem that should be >> fixed for Jessie. I suggest we wait a few more days until Friday and >> give the maintainer a chance to respond to the bug report. However the >> package looks rather neglected to me hence I would like to suggest that >> you just grab my attached debdiff from #733974 and NMU the package. I'm >> confident that the changes qualify for an unblock by the release team. I >> hope your last upload to unstable didn't introduce to many changes then >> I think we can get both, the Hurd FTBFS fix and the libjsoncpp fix, past >> the release team. > > I just uploaded the fixed package for libjsoncpp. Thanks for preparing > the debdiff, I always feel unconfident to work with packages that are > neither in a git not a svn. Thank you. > I confirmed that this is enough to fix the problem in minetest. We > just need to get the new libjsoncpp in Jessie, the current minetest > can stay. > > If you quickly know how to request that unblock, I'd be really > grateful if you could do so, please. It's quite easy reportbug release.debian.org and then a short explanation why you want that unblock + the debdiff against the version in testing. I'll take care of it. >> I think we should get in contact with Dominik George who already >> packaged some Minetest mods in the past. Perhaps he might be interested >> to package one of the other popular mods from this list >> >> http://minetest.net/mods >> >> He probably just needs a sponsor. Michael Dorrington also advertised his >> interest in packaging some Minetest mods on the mailing list not very >> long ago. > > I'm ok with helping if I'm contacted, but I wont seek for more work > myself ;) Ok, fair enough. [...] > The last issue that naggles me about minetest is whether we should > switch to freeminer at some point. The upstream community have forked, > and I cannot decide which version is the best one. We should maybe > package both, but that also seem to unnecessary burden the Debian > archive. There too, your advice would be very welcome. > I think we should stick with Minetest for the time being because I perceive the goals of freeminer as rather vague and I don't see any kind of big improvements that would justify a switch. I'm also quite reluctant when it comes to forks. They should really prove that they are the better alternative and I can't see that currently with freeminer. There is also only one server at the moment http://servers.freeminer.org/ and the Minetest community is much more vital and active. > Thanks for your time, > Mt. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#770185: linux-image-3.2.0-4-kirkwood: Unknown symbol ip_idents_reserve breaks IPv6
Package: src:linux Version: 3.2.63-2+deb7u1 Severity: grave Tags: ipv6 Justification: renders package unusable Dear Maintainer, the package introduces unmet symbol dependencies for the ipv6 kernel module and hence breaks IPv6 support. This appears to be caused by the inclusion of a Debian specific patch 'drivers-net-ipv6-select-ipv6-fragment-idents-for-vir.patch' written by Ben Hutchings . Downgrading to version 3.2.60-1+deb7u3 appears to be the only remedy. Many thanks. -- Package-specific info: ** Version: Linux version 3.2.0-4-kirkwood (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 Debian 3.2.57-3+deb7u1 ** Command line: console=ttyS0,115200 ** Not tainted ** Kernel log: [ 24.361697] usbcore: registered new interface driver snd-usb-audio [ 24.517306] libertas_sdio mmc0:0001:1: firmware: agent aborted loading libertas/sd8688_helper.bin (not found?) [ 24.565007] libertas_sdio mmc0:0001:1: firmware: agent aborted loading sd8688_helper.bin (not found?) [ 24.574442] libertas_sdio: failed to find firmware (-2) [ 24.583236] libertas_sdio: probe of mmc0:0001:1 failed with error -2 [ 24.602645] Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2 [ 24.668293] btmrvl_sdio mmc0:0001:2: firmware: agent aborted loading sd8688_helper.bin (not found?) [ 25.253582] Adding 1049084k swap on /dev/sda2. Priority:-1 extents:1 across:1049084k SS [ 25.328307] EXT4-fs (sdb2): re-mounted. Opts: (null) [ 25.594492] EXT4-fs (sdb2): re-mounted. Opts: errors=remount-ro [ 25.822865] loop: module loaded [ 28.600446] EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended [ 28.610013] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: discard,data=ordered,errors=remount-ro [ 30.020234] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.040902] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.087839] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.320561] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.342165] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.408901] RPC: Registered named UNIX socket transport module. [ 30.414855] RPC: Registered udp transport module. [ 30.419631] RPC: Registered tcp transport module. [ 30.424359] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 30.470326] FS-Cache: Loaded [ 30.538512] FS-Cache: Netfs 'nfs' registered for caching [ 30.583836] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 32.957724] mv643xx_eth_port mv643xx_eth_port.1: eth1: link up, 1000 Mb/s, full duplex, flow control disabled [ 34.769176] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 35.017457] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 38.599557] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 42.329340] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 43.676240] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 54.137370] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 54.177423] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.147370] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.213917] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.867175] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.917969] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 60.548808] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 61.044748] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 61.176379] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 75.308553] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 75.371951] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 88.766351] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 99.726306] The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case. If you have one, please send an email to linux...@kvack.org. [ 191.458947] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 779.571632] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 874.047456] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 874.109899] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 1040.791628] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 1560.301116] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 1734.276133] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 1734.339141] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 2240.469869] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 2341.065607] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 2642.217421] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 2642.341013] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 3121.831884] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 3440.280069] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 3539.840499] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 3539.905766] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 3902.719434] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 4107.627900] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 4446.188858] ipv6: Un
Bug#770035: kdenlive: Processed videos have image pauses or accelerations while sound goes well
Hi Dan, do you have an idea to http://bugs.debian.org/770035 ? Am 19.11.2014 um 14:54 schrieb Javier Ortega Conde (Malkavian): Could you retest it with the libmlt*, mlt*, melt* packages from experimental (not jessie/sid)? Done, and problem persists. -- Agur: Javier Ortega Conde (Malkavian) MetaUniversidad: servicios de educación online http://metauniversidad.com -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */
Bug#770035: kdenlive: Processed videos have image pauses or accelerations while sound goes well
> > Could you retest it with the libmlt*, mlt*, melt* packages from > experimental (not jessie/sid)? > Done, and problem persists. -- Agur: Javier Ortega Conde (Malkavian) MetaUniversidad: servicios de educación onlinehttp://metauniversidad.com
Bug#759960: marked as done (libcatalyst-engine-psgi-perl: FTBFS: dh_auto_test: make -j1 test returned exit code 2)
Your message dated Wed, 19 Nov 2014 13:47:03 +
with message-id
and subject line Bug#769933: Removed package(s) from unstable
has caused the Debian Bug report #759960,
regarding libcatalyst-engine-psgi-perl: FTBFS: dh_auto_test: make -j1 test
returned exit code 2
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.)
--
759960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcatalyst-engine-psgi-perl
Version: 0.13+dfsg-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory
> '/«BUILDDIR»/libcatalyst-engine-psgi-perl-0.13+dfsg'
> PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-MTest::Harness"
> "-e" "undef *Test::Harness::Switches; test_harness(0, 'inc', 'blib/lib',
> 'blib/arch')" t/*.t
> Possible precedence issue with control flow operator at
> /«BUILDDIR»/libcatalyst-engine-psgi-perl-0.13+dfsg/inc/Test/Builder.pm line
> 917.
> t/00_compile.t ... ok
> Possible precedence issue with control flow operator at
> /«BUILDDIR»/libcatalyst-engine-psgi-perl-0.13+dfsg/inc/Test/Builder.pm line
> 917.
> [debug] Debug messages enabled
> [debug] Statistics enabled
> Term::Size::Any is not installed, can't autodetect terminal column width
> Trouble trying to detect your terminal size, looking at $ENV{COLUMNS}
> Cannot determine desired terminal width, using default of 80 columns
> [debug] Loaded PSGI Middleware:
> ..
> | Catalyst::Middleware::Stash|
> | Plack::Middleware::HTTPExceptions |
> | Plack::Middleware::RemoveRedundantBody 0.04 |
> | Plack::Middleware::FixMissingBodyInRedirect 0.10 |
> | Plack::Middleware::ContentLength |
> | Plack::Middleware::MethodOverride 0.10|
> | Plack::Middleware::Head|
> ''
>
> [debug] Loaded Request Data Handlers:
> ..
> | application/x-www-form-urlencoded |
> | application/json |
> ''
>
> [debug] Loaded dispatcher "Catalyst::Dispatcher"
> [debug] Loaded engine "Catalyst::Engine"
> [debug] Found home
> "/«BUILDDIR»/libcatalyst-engine-psgi-perl-0.13+dfsg/t/Hello"
> [debug] Loaded components:
> .-+--.
> | Class | Type |
> +-+--+
> | Hello::Controller::Metalic | instance |
> | Hello::Controller::Root | instance |
> '-+--'
>
> [debug] Loaded Private actions:
> .--+--+--.
> | Private | Class| Method |
> +--+--+--+
> | /welcome | Hello::Controller::Root | welcome |
> | /default | Hello::Controller::Root | default |
> | /headers | Hello::Controller::Root | headers |
> | /index | Hello::Controller::Root | index|
> | /end | Hello::Controller::Root | end |
> '--+--+--'
>
> [debug] Loaded Path actions:
> .-+--.
> | Path| Private |
> +-+--+
> | / | /index |
> | /...
Bug#762690: closed by Emmanuel Bourg (Bug#762690: fixed in libhibernate-validator-java 4.2.1-1)
On Wed, 19 Nov 2014, Debian Bug Tracking System wrote: >* New upstream release > - Fixes CVE-2014-3558 (Closes: #762690) Thank you \o/ Given it fixes an RC bug, will you check with the release team about a possible exception to the freeze rules? I saw you uploaded to experimental, thus I'm wondering if you were going to try that anyway. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770104: marked as done (seivot completely fails)
Your message dated Wed, 19 Nov 2014 13:46:26 + with message-id and subject line Bug#770140: Removed package(s) from unstable has caused the Debian Bug report #770104, regarding seivot completely fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: seivot Version: 1.17-1 Severity: grave Seivot, as packaged in Debian, simply doesn't run: anarcat@marcos:~$ seivot /usr/bin/time: cannot run genbackupdata: No such file or directory ERROR: command failed: ['genbackupdata', '/tmp/tmpiWI_PW/data', '--create', '1024', '--file-size', '16384'] None Even as documented in the README: anarcat@marcos:src$ seivot --log=foo.log --log-level=debug --initial-data=1m --incremental-data=1m --generations=2 /usr/bin/time: cannot run genbackupdata: No such file or directory ERROR: command failed: ['genbackupdata', '/tmp/tmpdBnhp8/data', '--create', '100', '--file-size', '16384'] None It seems there's a Depends on genbackupdata that is missing... I'd be willing to make an NMU to fix this if you have no objections. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages seivot depends on: ii python 2.7.8-2 ii python-cliapp 1.20140719-1 ii python2.7 2.7.8-11 seivot recommends no packages. Versions of packages seivot suggests: ii summain 0.18-1 -- no debconf information --- End Message --- --- Begin Message --- Version: 1.17-1+rm Dear submitter, as the package seivot has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/770140 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: fixed 770182 in 0.5.2~rc1+dfsg-2
Processing commands for cont...@bugs.debian.org: > fixed 770182 0.5.2~rc1+dfsg-2 Bug #770182 [xul-ext-firetray] Incompatible with recent icedove from wheezy-security Marked as fixed in versions firetray/0.5.2~rc1+dfsg-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 770182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770182 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#770182: Incompatible with recent icedove from wheezy-security
Package: xul-ext-firetray Version: 0.4.6-1~deb7u1 Severity: serious Control: notfound -1 0.5.2~rc1+dfsg-2 Hi, xul-ext-firetray currently in stable Breaks: icedove (>> 23.0+) Since icedove 31.2.0-1~deb7u1 has been pushed via wheezy-security, the package is currently broken. I’ll test if dropping this Breaks is enough to fix the issue and will deal a p-u request with the release team ASAP. Regards David signature.asc Description: Digital signature
Processed: Incompatible with recent icedove from wheezy-security
Processing control commands: > notfound -1 0.5.2~rc1+dfsg-2 Bug #770182 [xul-ext-firetray] Incompatible with recent icedove from wheezy-security Ignoring request to alter found versions of bug #770182 to the same values previously set -- 770182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770182 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#762690: marked as done (libhibernate-validator-java: affected by CVE-2014-3558)
Your message dated Wed, 19 Nov 2014 13:33:45 + with message-id and subject line Bug#762690: fixed in libhibernate-validator-java 4.2.1-1 has caused the Debian Bug report #762690, regarding libhibernate-validator-java: affected by CVE-2014-3558 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.) -- 762690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libhibernate-validator-java Severity: serious Tags: security Hi, the following vulnerability was published for libhibernate-validator-java. CVE-2014-3558[0]: It was discovered that the implementation of org.hibernate.validator.util.ReflectionHelper together with the permissions required to run Hibernate Validator under the Java Security Manager could allow a malicious application deployed in the same application container to execute several actions with escalated privileges, which might otherwise not be possible. This flaw could be used to perform various attacks, including but not restricted to, arbitrary code execution in systems that are otherwise secured by the Java Security Manager. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3558 https://security-tracker.debian.org/tracker/CVE-2014-3558 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-3558 Please adjust the affected versions in the BTS as needed. The upstream fixes seem very involved and they have been pushed only on newer versions of the package: 4.2.1, 4.3.2, and 5.1.2 respectively. See https://hibernate.atlassian.net/browse/HV-912 Please switch to a new upstream version ASAP in unstable and help the security team and the LTS team to provide patched versions in stable/oldstable. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ --- End Message --- --- Begin Message --- Source: libhibernate-validator-java Source-Version: 4.2.1-1 We believe that the bug you reported is fixed in the latest version of libhibernate-validator-java, 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated libhibernate-validator-java 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: Wed, 19 Nov 2014 12:37:40 +0100 Source: libhibernate-validator-java Binary: libhibernate-validator-java Architecture: source all Version: 4.2.1-1 Distribution: experimental Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libhibernate-validator-java - Hibernate Validator Closes: 762690 Changes: libhibernate-validator-java (4.2.1-1) experimental; urgency=medium . * Team upload. * New upstream release - Fixes CVE-2014-3558 (Closes: #762690) - Refreshed the patches - Added libjaxb-java, libgeronimo-jpa-2.0-spec-java, libjoda-time-java, libjavassist-java and libmaven-bundle-plugin-java to the build deps * debian/control: - Use canonical URLs for the Vcs-* fields - Standards-Version updated to 3.9.6 (no changes) * debian/watch: Updated to watch the release tags on Github * Removed debian/orig-tar.* and use the Github archive as is * Switch to debhelper level 9 Checksums-Sha1: 8dc6b814da3f7f14f7f3f14bef6b93748b5082f1 2478 libhibernate-validator-java_4.2.1-1.dsc 9fecbbd47b668a308d554fb280e4c92897e6e65e 1678008 libhibernate-validator-java_4.2.1.orig.tar.gz 36ff71db21964b15b1ca4b2c60694b3ab1d15a13 5092 libhibernate-validator-java_4.2.1-1.debian.tar.xz 52e091cc4f67dd704cdf7a0d76dc655d817c191c 361664 libhibernate-validator-java_4.2.1-1_all.deb Checksums-Sha256: 6bf2bb4e1a50468a03e520ce59be5770fa4ea8ce95cb49ffcd9136a52deaab94 2478 libhibernate-validator-java_4.2.1-1.dsc 5111a81b4b7a1118459c7f20bc470db6266926b0fc099a0e917c489d6b6bb194 1678008 libhibernate-validator-java_4.2.1.orig.tar.gz 7645584c45cbe36813227e03170f42604
Processed: Re: [Pkg-mozext-maintainers] Bug#769231: Bug#769231: xul-ext-adblock-plus: incompatible with iceweasel in stable-security
Processing control commands: > tags -1 moreinfo Bug #769231 [xul-ext-adblock-plus] xul-ext-adblock-plus: incompatible with iceweasel in stable-security Added tag(s) moreinfo. -- 769231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769231 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#767676: ola-rdm-tests: fails to install: subprocess installed post-installation script returned error exit status 10
Hello,
Here is a new version of the patch, with following changes:
- I now ship /etc/ola in both ola & ola-rdm-tests packages, since they
both need it and I don't want to make ola-rdm-tests pre-depend on ola
just to ensure /etc/ola exists when installing ola-rdm-tests. Andreas, I
tried at first to ship /etc/ola within the package, but piuparts tests
failed. Thought it was due to that change, but I now realize this was
because of upgrade-tests instead.
- Removed useless comments to reduce patch size
- Fix typo in changelog (damn me)
Helmut, for now I still manage /etc/default/ola. As explained, I
consider it as important so that users don't have to dig into init
script to know which value they have to put into it to start olad
service. Please just let me know if you still disagree so that I can
remove it.
As usual (sounds strange to me since it's my first real patch, but
still), piuparts tests successfully pass (always with --no-upgrade-test
flag)
Job is not yet fully done, but I already wanted to deeply thank you for
your patience and your advices.
I'm learning a lot of things from you (and I enjoy it :p)
Regards,
Jean Baptiste
On 19/11/2014 12:32, Andreas Beckmann wrote:
> On 2014-11-19 07:41, Helmut Grohne wrote:
>> * "rm -rf /etc/ola" is dangerous and can potentially delete too much. I
>>suggest to use "rmdir --ignore-fail-on-non-empty" if that makes the
>>package purge cleanly as well.
> What about shipping the directory (potentially empty) and let dpkg do
> the rmdir?
> Then just delete the files in there your maintainer scripts placed.
> piuparts may complain that the *owned* directory is left after purge -
> that would be dpkg's fault not to retry the rmdir after the postrm purge
> was run. This does not need to be worked around. dpkg will be fixed
> eventually (for jessie +x)
>> * I suggest to remove the summary comments from the new scripts to
>>reduce the size of your patch.
> Andreas
diff -Nru ola-0.9.1/debian/changelog ola-0.9.1/debian/changelog
--- ola-0.9.1/debian/changelog 2014-08-17 10:07:29.0 +0200
+++ ola-0.9.1/debian/changelog 2014-11-19 13:45:05.0 +0100
@@ -1,3 +1,18 @@
+ola (0.9.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove debconf calls from ola-rdm-tests postinst. (Closes: #767676)
+ * Fix other serious issues:
+- Ship /etc/ola within package (wasn't deleted before on purge)
+- Provides missing /etc/default/ola from ola postinst script to allow
+ olad service control in the same way rdm_test_server is
+- Update init scripts to change advice to enable olad & drm_test_server
+ services (dpkg-reconfigure won't work without debconf)
+- add postrm scripts for packages ola & ola-rdm-tests to fully remove
+ configuration files so that piuparts tests can pass
+
+ -- Jean Baptiste Favre Sun, 16 Nov 2014 17:44:18 +0100
+
ola (0.9.1-1) unstable; urgency=low
* New upstream release
diff -Nru ola-0.9.1/debian/ola.dirs ola-0.9.1/debian/ola.dirs
--- ola-0.9.1/debian/ola.dirs 2014-04-21 08:19:26.0 +0200
+++ ola-0.9.1/debian/ola.dirs 2014-11-19 13:06:54.0 +0100
@@ -1,3 +1,4 @@
+etc/ola
usr/bin
usr/lib
usr/share/olad/www
diff -Nru ola-0.9.1/debian/ola.olad.init ola-0.9.1/debian/ola.olad.init
--- ola-0.9.1/debian/ola.olad.init 2014-08-17 09:17:40.0 +0200
+++ ola-0.9.1/debian/ola.olad.init 2014-11-18 14:04:41.0 +0100
@@ -23,7 +23,7 @@
if [ "$RUN_DAEMON" = "true" ] || [ "$RUN_DAEMON" = "yes" ] ; then
DAEMON_ARGS="--syslog --log-level 3 --config-dir /etc/ola"
elif [ "$1" = "start" ] || [ "$1" = "stop" ] ; then
- echo "The init script is currently inactive;\nuse \"dpkg-reconfigure ola\" to change this." >&2
+ echo "The init script is currently inactive;\nPlease update \"/etc/default/ola\" to change this." >&2
fi
[ -x "$DAEMON" ] || exit 0
diff -Nru ola-0.9.1/debian/ola.postinst ola-0.9.1/debian/ola.postinst
--- ola-0.9.1/debian/ola.postinst 2014-08-17 09:17:40.0 +0200
+++ ola-0.9.1/debian/ola.postinst 2014-11-19 13:40:58.0 +0100
@@ -8,13 +8,19 @@
groups olad | grep plugdev > /dev/null || adduser olad plugdev
# setup the config dir
-CONF_DIR=/etc/ola
-if [ ! -d ${CONF_DIR} ]; then
- mkdir -p ${CONF_DIR};
- chown -R olad:olad ${CONF_DIR};
- chmod g+s ${CONF_DIR};
-fi;
+chown -R olad:olad /etc/ola;
+chmod g+s /etc/ola;
+conffile="/etc/default/ola"
+
+if [ -f $conffile ] ; then
+ sed -i -e 's/^[ ]*DAEMON/RUN_DAEMON/g' $conffile
+else
+ cat << EOF > $conffile
+# If set to true, olad will run.
+RUN_DAEMON="true"
+EOF
+fi
# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.
diff -Nru ola-0.9.1/debian/ola.postrm ola-0.9.1/debian/ola.postrm
--- ola-0.9.1/debian/ola.postrm 1970-01-01 01:00:00.0 +0100
+++ ola-0.9.1/debian/ola.postrm 2014-11-19 13:39:49.0 +0100
@@ -0,0 +1,25 @@
+#!/bin/sh
+# postrm script for ola
+
+set -e
+
+case "$1" in
+ purge)
+if [ -f /etc/defaul
