Processed: Re: NVIDIA non-free driver may break gdm3
Processing control commands: tags 761001 - moreinfo Bug #761001 [gdm3] gdm3: No way to log in Removed tag(s) moreinfo. severity 761001 serious Bug #761001 [gdm3] gdm3: No way to log in Severity set to 'serious' from 'important' -- 761001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761001 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#767411: torque: should not be released with jessie
On Thu, Oct 30, 2014 at 8:42 PM, Dominique Belhachemi domi...@debian.org wrote: I agree that the 2.4 branch is completely outdated. We should switch to a newer branch. The 2.5 and 4.1 branches are not suitable for Debian due to licensing issues. But the 4.2 branch is licensed under the same license as the 2.4 branch, so I suggest we upload the 4.2.9 release to unstable. I am afraid that the 4.2 branch cannot be used to replace the 2.4 branch. I updated our svn package repository to build the 4.2.9 release, but noticed that the license issues haven't been resolved. Upstream added the original PBS license file [1] back to the source tree, but they also keep a changed license [2] . [1] https://github.com/adaptivecomputing/torque/commits/4.2.9/PBS_License.txt [2] https://github.com/adaptivecomputing/torque/commits/4.2.9/LICENSE For more information see #641484 Unfortunately, I cannot spend more time on this package. Best -Dominique
Bug#767562: marked as done (littlewizard-data: fails to upgrade from 'testing' - trying to overwrite /usr/share/pixmaps/littlewizard.xpm)
Your message dated Sat, 01 Nov 2014 07:48:58 + with message-id e1xktqg-0001i7...@franck.debian.org and subject line Bug#767562: fixed in littlewizard 1.2.2-3 has caused the Debian Bug report #767562, regarding littlewizard-data: fails to upgrade from 'testing' - trying to overwrite /usr/share/pixmaps/littlewizard.xpm 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.) -- 767562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: littlewizard-data Version: 1.2.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to replace littlewizard-data 1.2.2-1 (using .../littlewizard-data_1.2.2-2_all.deb) ... Unpacking replacement littlewizard-data ... dpkg: error processing /var/cache/apt/archives/littlewizard-data_1.2.2-2_all.deb (--unpack): trying to overwrite '/usr/share/pixmaps/littlewizard.xpm', which is also in package littlewizard 1.2.2-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for fontconfig ... Errors were encountered while processing: /var/cache/apt/archives/littlewizard-data_1.2.2-2_all.deb cheers, Andreas littlewizard=1.2.2-1_littlewizard-data=1.2.2-2.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: littlewizard Source-Version: 1.2.2-3 We believe that the bug you reported is fixed in the latest version of littlewizard, 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. Kari Pahula k...@debian.org (supplier of updated littlewizard 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, 01 Nov 2014 09:38:11 +0200 Source: littlewizard Binary: littlewizard littlewizard-data Architecture: source all amd64 Version: 1.2.2-3 Distribution: unstable Urgency: medium Maintainer: Kari Pahula k...@debian.org Changed-By: Kari Pahula k...@debian.org Description: littlewizard - development environment for children littlewizard-data - littlewizard data files Closes: 767562 Changes: littlewizard (1.2.2-3) unstable; urgency=medium . * Add breaks and replaces to manage a file move from littlewizard to littlewizard-data. (Closes: #767562) Checksums-Sha1: fd55305bd7e0dea91084a29087385993d0299471 1862 littlewizard_1.2.2-3.dsc 39bc74e18e3098d68d8280a511b0290b04cfdfc6 5224 littlewizard_1.2.2-3.debian.tar.xz e61aa011760af5f86d6b591aff5c63867ead507a 226390 littlewizard-data_1.2.2-3_all.deb 8f986dbe72d96fe48f84801182dede141f0ee5bb 99950 littlewizard_1.2.2-3_amd64.deb Checksums-Sha256: dac93eaf6a4a298851368c09b18194e641746a493dd91e21169bf1f7b2b45f5b 1862 littlewizard_1.2.2-3.dsc 5201a2615e651f3f7d564b1eab663a527fc262119e204958b718a85a41fb7c66 5224 littlewizard_1.2.2-3.debian.tar.xz 56f0cafcc853eba055bf65e51ed16480d214a1d095bf8f898c588852000fa947 226390 littlewizard-data_1.2.2-3_all.deb 8d8f6fd7b0d6df5beab6e2bf63022b8d63732010c6226160d1d02ca564404877 99950 littlewizard_1.2.2-3_amd64.deb Files: b48431f1e04f8f17d364f8919389 1862 education optional littlewizard_1.2.2-3.dsc f52e27167f9fcab283f2de42315e56d0 5224 education optional littlewizard_1.2.2-3.debian.tar.xz 47ac39349b63bcb69b9c99f2effc6864 226390 education optional littlewizard-data_1.2.2-3_all.deb 4bfb7b3a94114e8c34a44ba5ddbded49 99950 education optional littlewizard_1.2.2-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUVI41AAoJEIQIZ+6djyZcmtEP/i0HonQkPOttJKez1e37Dg1X pXm0ZAhhMhTTrfqrI+gEBIC5Kjlnkjcgq4cK4cBuj4TnrIO9rc487BWgVakYzuec DErotdFfzxWf479TNOTLXX3jxltwopscSE7q/+ssNQ+5jxpZIaCan5wYXwPe0huF i0FjMOst2cRy3rdWKlY+qEDGpTLlTUpyKdbbs7KKrrrddOt/MyTC9CPmbw8aKZ2X
Processed: found 767561 in strongswan-starter/5.1.1-1
Processing commands for cont...@bugs.debian.org: found 767561 strongswan-starter/5.1.1-1 Bug #767561 [pki-tools,strongswan-starter] pki-tools,strongswan-starter: error when trying to install together The source strongswan-starter and version 5.1.1-1 do not appear to match any binary packages Marked as found in versions strongswan-starter/5.1.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 767561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767561 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#767579: python-markdown: FTBFS: tests failures with new Pygments
Source: python-markdown Version: 2.5.1-1 Severity: serious python-markdown FTBFS with new pygments 2.0 in testing: FAIL: testBasicCodeHilite (tests.test_extensions.TestCodeHilite) - div class=codehilitepre# A Code Comment + div class=codehiliteprespan class=c# A Code Comment/span ? +++ FAIL: testLinenumsNone (tests.test_extensions.TestCodeHilite) - div class=codehilitepre# A Code Comment + div class=codehiliteprespan class=c# A Code Comment/span ? +++ Full build log: http://mitya57.me/builds/python-markdown_2.5.1-1_amd64.build -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Processed: forwarded 767579
Processing commands for cont...@bugs.debian.org: forwarded 767579 https://github.com/waylan/Python-Markdown/issues/361 Bug #767579 [src:python-markdown] python-markdown: FTBFS: tests failures with new Pygments Set Bug forwarded-to-address to 'https://github.com/waylan/Python-Markdown/issues/361'. thanks Stopping processing here. Please contact me if you need assistance. -- 767579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767579 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#767557: libsocl-1.1-1,libsocl-contrib-1.1-1: error when trying to install together
Andreas Beckmann, le Sat 01 Nov 2014 03:39:21 +0100, a écrit : 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/libsocl-1.1.so.1 usr/lib/libsocl-1.1.so.1.0.1 Ah, indeed, when main got an OpenCL layer, I added libsocl in main, withtout thinking about adding the conflict with the libsocl-contrib, will so that. Samuel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfound 766832 in metview/4.4.8+dfsg.1-7
Processing commands for cont...@bugs.debian.org:
notfound 766832 metview/4.4.8+dfsg.1-7
Bug #766832 {Done: Alastair McKinstry mckins...@debian.org} [src:metview]
metview: FTBFS on mipsel: libMagWrapper.a: error adding symbols: Bad value
(recompile with -fPIC)
No longer marked as found in versions metview/4.4.8+dfsg.1-7.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
766832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766832
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#767095: gkrellm: CPU config changed after upgrade to 2.3.6~rc1-1
The Debian Policy Manual is about packaging and how package scripts (pre/post scripts) behave, not about how applications themselves behave on upgrade. Since gkrellm 2.3.6 changes how configuring CPU krells work it falls back to its internal default value. If you would extend the Debian Policy Manual to actual application behavior you would basically kick out any big desktop environment. I did not count the number of times I had to reconfigure things in KDE or XFCE on a new minor version but I can assure you there were many of such little hiccups. Regards, Stefan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767561: [Pkg-freeipa-devel] Bug#767561: pki-tools, strongswan-starter: error when trying to install together
On 01.11.2014 05:44, Andreas Beckmann wrote: Package: pki-tools,strongswan-starter Version: 10.2.0-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 5.2.1-4 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 strongswan-starter. Preparing to unpack .../strongswan-starter_5.2.1-4_amd64.deb ... Unpacking strongswan-starter (5.2.1-4) ... dpkg: error processing archive /var/cache/apt/archives/strongswan-starter_5.2.1-4_amd64.deb (--unpack): trying to overwrite '/usr/bin/pki', which is also in package pki-tools 10.2.0-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/strongswan-starter_5.2.1-4_amd64.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/bin/pki usr/share/man/man1/pki.1.gz 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. I don't mind adding a Conflicts. On Fedora though strongswan changed the binary/manpage name to strongswan-pki: http://pkgs.fedoraproject.org/cgit/strongswan.git/commit/strongswan.spec?id=710e5ac47162230da3e715a5117a8bb269e4af6d -- t -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 767579 + pending Bug #767579 [src:python-markdown] python-markdown: FTBFS: tests failures with new Pygments Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 767579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 728459 is important
Processing commands for cont...@bugs.debian.org: severity 728459 important Bug #728459 [flashcache-dkms] flashcache: Cannot load binary-module on i386 (undefined symbols) Severity set to 'important' from 'serious' # a year later I think important is enough thanks Stopping processing here. Please contact me if you need assistance. -- 728459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728459 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#767579: marked as done (python-markdown: FTBFS: tests failures with new Pygments)
Your message dated Sat, 01 Nov 2014 09:49:43 + with message-id e1xkvjx-00054u...@franck.debian.org and subject line Bug#767579: fixed in python-markdown 2.5.1-2 has caused the Debian Bug report #767579, regarding python-markdown: FTBFS: tests failures with new Pygments 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.) -- 767579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-markdown Version: 2.5.1-1 Severity: serious python-markdown FTBFS with new pygments 2.0 in testing: FAIL: testBasicCodeHilite (tests.test_extensions.TestCodeHilite) - div class=codehilitepre# A Code Comment + div class=codehiliteprespan class=c# A Code Comment/span ? +++ FAIL: testLinenumsNone (tests.test_extensions.TestCodeHilite) - div class=codehilitepre# A Code Comment + div class=codehiliteprespan class=c# A Code Comment/span ? +++ Full build log: http://mitya57.me/builds/python-markdown_2.5.1-1_amd64.build -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: python-markdown Source-Version: 2.5.1-2 We believe that the bug you reported is fixed in the latest version of python-markdown, 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. Dmitry Shachnev mity...@debian.org (supplier of updated python-markdown package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 01 Nov 2014 12:34:55 +0300 Source: python-markdown Binary: python-markdown python3-markdown python-markdown-doc Architecture: source all Version: 2.5.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Dmitry Shachnev mity...@debian.org Description: python-markdown - text-to-HTML conversion library/tool (implemented in Python 2) python-markdown-doc - text-to-HTML conversion library/tool (documentation) python3-markdown - text-to-HTML conversion library/tool (implemented in Python 3) Closes: 767579 Changes: python-markdown (2.5.1-2) unstable; urgency=medium . * Disable two tests that were relying on wrong assumption about Pygments lexer guessing algorithm (closes: #767579). Checksums-Sha1: 3df8cd50c9bbdf940873ffa5b8d8a7258b05791a 2382 python-markdown_2.5.1-2.dsc 5bc8c5a139107b10acf476677ab1c6b3bb9b679d 7244 python-markdown_2.5.1-2.debian.tar.xz 8bde4164dcb2cc645ed126bc26c0e9677e2e3a8b 54482 python-markdown_2.5.1-2_all.deb d19949806617799ce8a06af2e0cd8314b1b71385 53354 python3-markdown_2.5.1-2_all.deb e5a9cf316bd741b659e33d4df7cc9a6095fe12a3 72962 python-markdown-doc_2.5.1-2_all.deb Checksums-Sha256: 307c755b02e2018ef484bb0701f7efc94f881b91a5f6ea66242775eb19761a62 2382 python-markdown_2.5.1-2.dsc f00fafe94e7d7af3e5a6c319c8c7b9d706cedbbe3f2d2b5fec092f117e98ebad 7244 python-markdown_2.5.1-2.debian.tar.xz 4eab75683746c8517ccce5811ffd82885c1ff69c0d65b1f13948ac29797c957a 54482 python-markdown_2.5.1-2_all.deb cfb10b29c827616fc3fc679de7c242ffc7e4c2f2bc4358c1a172f43153ea8802 53354 python3-markdown_2.5.1-2_all.deb e11ea2bad6f8002f460ba57e34603af0f6611c0bc7e72a14a9d638fe44983026 72962 python-markdown-doc_2.5.1-2_all.deb Files: 9b8a7709ec0c1541a85152544e9c4fcb 2382 python optional python-markdown_2.5.1-2.dsc a11f42afda91acf2b5e1becf1a8089fe 7244 python optional python-markdown_2.5.1-2.debian.tar.xz 9dd134818f4e305f9729a013e8bf04b3 54482 python optional python-markdown_2.5.1-2_all.deb aa9fac612b91fd0bd3650631e3aec8e0 53354 python optional python3-markdown_2.5.1-2_all.deb c6973c1be27113e8b5db026d517abfa3 72962 doc optional python-markdown-doc_2.5.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUVKp+AAoJEGAmk20vHIrgwlMQAIk5pNUldM+OS/H4F99gEARl YJ3g38hnN/aYKls1tIjR+yO7bsuDMneUBBOstB52HYdU0vTQW0DiPUjolNkjZy1p dSkMGc3TmpHLfmPT5VTIZxm/pZJnnpv/arWYMZnUfq+XTUPoKVALq9csT4JINn9u
Bug#755140: Fails to shutdown or logout without gnome-shell
Control: severity -1 normal Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=738264 Logout and Shutdown from gnome-flashback session are working fine now as it pretends to be gnome-shell by exporting relevant interface. However it would still be nice if upstream gnome-session supported more generic interface name, so leaving the bug open and adding an upstream task. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#767583: kfreebsd-10: ar9300_devid.h license restricts modification
Source: kfreebsd-10
Severity: serious
Tags: upstream
Justification: Policy 2.2.1
Dear Maintainer,
After reading a discussion on the gnu-linux-libre mailing list [1],
I found that the two files named ar9300_devid.h have a license that
restricts modification:
* Copyright (c) 2002-2004 Sam Leffler, Errno Consulting, Atheros
* Communications, Inc. All rights reserved.
*
* Redistribution and use in source and binary forms are permitted
* provided that the following conditions are met:
* 1. The materials contained herein are unmodified and are used
*unmodified.
* 2. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following NO
*''WARRANTY'' disclaimer below (''Disclaimer''), without
*modification.
* 3. Redistributions in binary form must reproduce at minimum a
*disclaimer similar to the Disclaimer below and any redistribution
*must be conditioned upon including a substantially similar
*Disclaimer requirement for further binary redistribution.
* 4. Neither the names of the above-listed copyright holders nor the
*names of any contributors may be used to endorse or promote
*product derived from this software without specific prior written
*permission.
*
* NO WARRANTY
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
* ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
* LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT,
* MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
* IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE
* FOR SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
* USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
* OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGES.
*
* $FreeBSD$
The two files are:
/sys/dev/ath/ath_hal/ar9003/ar9300_devid.h
/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_devid.h
I'm not really sure what should be done about it, though.
[1] https://lists.nongnu.org/archive/html/gnu-linux-libre/2014-10/msg00014.html
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Fails to shutdown or logout without gnome-shell
Processing control commands: severity -1 normal Bug #755140 [gnome-session] Fails to shutdown or logout without gnome-shell Severity set to 'normal' from 'serious' forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=738264 Bug #755140 [gnome-session] Fails to shutdown or logout without gnome-shell Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=738264'. -- 755140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755140 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#767584: segfaults when a dot is used in the config as part of the hostname
Package: apt-dater
Version: 1.0.1-1
Severity: grave
Hi,
after the upgrade to 1.0.0 I first what surprised by a new configuration, w/o
an import of my old one, thanks :/
After rewriting the config, apt-dater segfaults on me.
Minimal config to reproduce the issue (based on your example):
Hosts:
{
localnet:
{
Title=local hosts;
localhost: {}
node1.ibh.net: {}
}
}
GDB backtrace:
evgeni@nana ~ % gdb apt-dater
GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from apt-dater...Reading symbols from
/usr/lib/debug/.build-id/0d/b0e0825ca8396749052e4555417b2144d17f01.debug...done.
done.
(gdb) run
Starting program: /usr/bin/apt-dater
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
** (apt-dater:30187): ERROR **: Error reading host file
[/home/evgeni/.config/apt-dater/hosts.config:40]: syntax error
Program received signal SIGTRAP, Trace/breakpoint trap.
g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR, format=optimized out,
args=args@entry=0x7fffdf40) at
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmessages.c:1046
1046/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmessages.c: No such file
or directory.
(gdb) bt full
#0 g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR, format=optimized
out, args=args@entry=0x7fffdf40)
at /build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmessages.c:1046
domain = 0x0
data = 0x0
depth = 0
log_func = 0x77b1d5c0 g_log_default_handler
domain_fatal_mask = optimized out
masquerade_fatal = 0
test_level = optimized out
was_fatal = optimized out
was_recursion = optimized out
msg = 0x620f00 Error reading host file
[/home/evgeni/.config/apt-dater/hosts.config:40]: syntax error
msg_alloc = 0x620f00 Error reading host file
[/home/evgeni/.config/apt-dater/hosts.config:40]: syntax error
i = 2
#1 0x77b1df6f in g_log (log_domain=log_domain@entry=0x0,
log_level=log_level@entry=G_LOG_LEVEL_ERROR,
format=format@entry=0x414d08 Error reading host file [%s:%d]: %s) at
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmessages.c:1079
args = {{gp_offset = 48, fp_offset = 48, overflow_arg_area =
0x7fffe020, reg_save_area = 0x7fffdf60}}
#2 0x004074b8 in loadHosts (filename=0x621dc0
/home/evgeni/.config/apt-dater/hosts.config) at keyfiles.c:298
efn = optimized out
hcfg = {root = 0x621d30, destructor = 0x0, flags = 0, tab_width = 2,
default_format = 0, include_dir = 0x0, error_text = 0x76fb7da5 syntax
error,
error_file = 0x6213c0 /home/evgeni/.config/apt-dater/hosts.config,
error_line = 40, error_type = CONFIG_ERR_PARSE, filenames = 0x621fc0,
num_filenames = 1}
cfghosts = optimized out
hosts = optimized out
i = optimized out
cfggroup = optimized out
#3 0x00405446 in main (argc=1, argv=0x7fffe208,
envp=0x7fffe218) at apt-dater.c:130
opts = optimized out
cfgfilename = 0x620fa0 /home/evgeni/.config/apt-dater/apt-dater.config
cfgdirname = 0x620f70 /home/evgeni/.config/apt-dater
hosts = 0x0
report = 0
refresh = 1
(gdb)
Renaming node1.ibh.net to node1ibhnet solves the issue, but then I
have to add SSHHost to every node and that sounds wrong.
Regards
Evgeni
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apt-dater depends on:
ii libc6 2.19-12
ii libconfig9 1.4.9-2
ii libglib2.0-02.42.0-2
ii libncursesw55.9+20140913-1
ii libpopt01.16-10
ii libtcl8.5 8.5.17-1
ii libtinfo5 5.9+20140913-1
ii libxml2 2.9.2+dfsg1-1
ii lockfile-progs 0.1.17
ii openssh-client 1:6.7p1-2
ii screen 4.2.1-3
apt-dater recommends no packages.
Versions of packages apt-dater suggests:
pn apt-dater-host none
ii xsltproc1.1.28-2+b1
-- no
Processed: severity 759348 serious
Processing commands for cont...@bugs.debian.org: severity 759348 serious Bug #759348 [cups-browsed] cups-browsed: May hang for 90 seconds when restarted Severity set to 'serious' from 'minor' End of message, stopping processing here. Please contact me if you need assistance. -- 759348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759348 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#767019: xscreensaver: postinst overwrites /etc/X11/app-defaults/XScreenSaver without asking
On Mon, Oct 27, 2014 at 6:42 PM, Bjørn Mork wrote: Package: xscreensaver Version: 5.30-1+b1 Severity: serious Justification: Policy 10.7.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This part of xscreensaver.postinst overwrites any locally modified /etc/X11/app-defaults/XScreenSaver configuration: # Use the correct app defaults cd /etc/X11/app-defaults if [ -f XScreenSaver-gl ]; then ln -sf XScreenSaver-gl XScreenSaver else ln -sf XScreenSaver-nogl XScreenSaver fi You should not do the above if an XScreenSaver file or symlink exists prior to installation Thanks for the report. Looking at that file, there's also lots of old cruft that probably can be deleted now. Ideally it should overwrite an existing configuration file if it hasn't been modified by the user. There are some standard recipes for this IIRC. Hmm, did you forget to attach the patch? :) Regards, Tormod -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767445: python-docker: throws ValueError exception on attempting any command
FYI this has also been reported upstream: https://github.com/docker/docker-py/issues/377. I believe that this is due to python-docker explicitly importing requests.packages.urllib3: /usr/lib/python2.7/dist-packages/docker/unixconn/unixconn.py:import requests.packages.urllib3.connectionpool as connectionpool /usr/lib/python2.7/dist-packages/docker/ssladapter/ssladapter.py:import requests.packages.urllib3 as urllib3 and the code breaks because: In [1]: from requests.packages.urllib3.util.timeout import Timeout as T1 In [2]: from urllib3.util.timeout import Timeout as T2 In [3]: T1 is T2 Out[3]: False IMO a package patch should be provided to import global urllib3 instead, following Debian packaging standards (c.f. related Debian bug #753578). -- Yours virtually, Jakub Warmuz signature.asc Description: OpenPGP digital signature
Processed: severity of 680435 is serious
Processing commands for cont...@bugs.debian.org: severity 680435 serious Bug #680435 [veromix] [veromix] Missing dependency Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 680435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680435 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#767498: [Debichem-devel] Bug#767498: Bug#767498: aces3: FTBFS on several architectures
On Fri, Oct 31, 2014 at 03:04:06PM +0100, Michael Banck wrote: The s390x is in the same ballpark, but IME s390x is fast enough that this might be a genuine compiler hang or so. Will try to reproduce on a porterbox as well. So zelenka.debian.org built all those files in 6,5 hours, it is not hanging. But clearly this is a huge liability on the buildds and AFAICT this functionality, while compiled in, is not readily made available to the user or documented. So I will look about patching it out in the build system, rather, which should help the other buildds as well. Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767600: python-versuchung: FTBFS everywhere
package: python-versuchung version: 1.1-1 severity: serious Hi, It seems python-versuchung doesn't build on the buildd's. The only available build is the maintainer upload. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: merging 766617 766614
Processing commands for cont...@bugs.debian.org: merge 766617 766614 Bug #766617 [src:cross-gcc-4.9-arm64] cross-gcc-4.9-arm64 is functional incomplete Bug #766614 [src:cross-gcc-4.9-arm64] cross-gcc-4.9-arm64 is functional incomplete Merged 766614 766617 thanks Stopping processing here. Please contact me if you need assistance. -- 766614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766614 766617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Kmail: Some times sign with S/MIME failed
Processing commands for cont...@bugs.debian.org: severity 766349 grave Bug #766349 [kmail] Kmail: Some times sign with S/MIME failed Severity set to 'grave' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 766349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 767307
Processing commands for cont...@bugs.debian.org: tags 767307 + moreinfo Bug #767307 [network-manager] [network-manager] after upgrade, all user passwords are lost Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 767307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767307 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#761001: marked as done (gdm3: No way to log in)
Your message dated Sat, 01 Nov 2014 13:17:27 +0100 with message-id 85bnorqfmw@boum.org and subject line Re: Bug#761001: No way to log in has caused the Debian Bug report #761001, regarding gdm3: No way to log in 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.) -- 761001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gdm3 Version: 3.12.2-2.1 Hi, gdm isn't giving me any option to log in anymore. After I boot, I get this nice black screen. With previous versions I had to do annoying slide afterwards to unlock the screen and I could still log in. With the current version just moving the mouse shows me something, but it's showing me a clock and some icons with things like network settings in the upper right corner. There doesn't seem to be any way to actually select or type a username and password. Kurt ---End Message--- ---BeginMessage--- Hi, Kurt Roeckx wrote (31 Oct 2014 23:33:32 GMT) : On Sat, Nov 01, 2014 at 12:08:43AM +0100, Michael Biebl wrote: Hi Kurt, Could you run dpkg-reconfigure libpam-runtime and make sure the systemd module is enabled. It's labeled Register user sessions in the systemd control group hierarchy That seems to have fixed things. Cool, thanks. My understanding is that it wasn't actually a bug in gdm, but a local misconfiguration issue. Closing accordingly. Feel free to reopen and/or reassign to the responsible package if I missed something. Still, maybe gdm could try to detect whether pam_systemd.so is active, and provide a clearer error message if it isn't the case? Cheers, -- intrigeri---End Message---
Processed: Re: Bug#765356: clobbers resolv.conf
Processing control commands: tag -1 + moreinfo Bug #765356 [network-manager] clobbers resolv.conf Added tag(s) moreinfo. -- 765356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 766619 is normal
Processing commands for cont...@bugs.debian.org: severity 766619 normal Bug #766619 [src:cross-gcc-4.9-armhf] cross-gcc-4.9-armhf is functional incomplete Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 766619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766619 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#765356: clobbers resolv.conf
Control: tag -1 + moreinfo Hi Daniel, Daniel Pocock wrote (14 Oct 2014 12:27:52 GMT) : I've rated this serious because it makes the network unusable when it happens and it requires a user with root privileges to rectify it. IMO, given the unusual settings in which the problem happens, severity should rather be important: a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. I'll let the maintainers judge, though. NetworkManager successfully connects to a WLAN Some time after that, I start an OpenSWAN VPN, for example, with ipsec start The VPN connects and the OpenSWAN log/console output shows something like: installing DNS server A.B.C.D to /etc/resolv.conf and then almost immediately afterwards, I see some NetworkManager entries in daemon.log: NetworkManager[5219]: info Policy set 'SSID-FOOBAR' (wlan0) as default for IPv4 routing and DNS. NetworkManager[5219]: info Policy set 'SSID-FOOBAR' (wlan0) as default for IPv6 routing and DNS. and the OpenSWAN entries from resolv.conf are gone again. If the VPN is being used for all routing (0.0.0.0/0) then the WLAN DNS servers may not be accessible any more and so there are no useful DNS servers in resolv.conf and all DNS requests time out. Manually adding the VPN DNS back into resolv.conf everything works Indeed, NetworkManager has no way to guess that it should not touch resolv.conf in this specific case. Your OpenSWAN VPN isn't managed by NM, is it? Could you please try checking Use this connection only for resources on its network in the NM settings of your Wi-Fi connection, and see if it fixes things for you? Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 4 errors): Debian bug: #735261
Processing commands for cont...@bugs.debian.org: found 735261 kdepim/4:4.14.2-2 Bug #735261 [kmail] kmail2 randomly marks read messages as unread Marked as found in versions kdepim/4:4.14.2-2. Hello, Unknown command or malformed arguments to command. also in 4:4.14.2-2. Unknown command or malformed arguments to command. CU Unknown command or malformed arguments to command. Jörg Unknown command or malformed arguments to command. -- Stopping processing here. Please contact me if you need assistance. -- 735261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735261 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#735261: Debian bug: #735261
found 735261 kdepim/4:4.14.2-2 Hello, also in 4:4.14.2-2. CU Jörg -- pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E CAcert Key S/N: 0E:D4:56 Jörg Frings-Fürst D-54526 Niederkail Threema-ID: SYR8SJXB IRC: j_...@freenode.net, j_...@oftc.net signature.asc Description: This is a digitally signed message part.
Processed: retitle 765356 to Replaces entries that were added by unmanaged connections to resolv.conf
Processing commands for cont...@bugs.debian.org: retitle 765356 Replaces entries that were added by unmanaged connections to resolv.conf Bug #765356 [network-manager] clobbers resolv.conf Changed Bug title to 'Replaces entries that were added by unmanaged connections to resolv.conf' from 'clobbers resolv.conf' thanks Stopping processing here. Please contact me if you need assistance. -- 765356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765356 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#767556: marked as done (perf-tools-unstable,ubuntu-dev-tools: error when trying to install together)
Your message dated Sat, 01 Nov 2014 12:34:03 + with message-id e1xkxsz-000453...@franck.debian.org and subject line Bug#767556: fixed in perf-tools-unstable 0.0.1~20140723+git942be0b-4 has caused the Debian Bug report #767556, regarding perf-tools-unstable,ubuntu-dev-tools: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: perf-tools-unstable,ubuntu-dev-tools Version: 0.0.1~20140723+git942be0b-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 0.153 Architecture: amd64 Distribution: jessie 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 ubuntu-dev-tools. Preparing to unpack .../ubuntu-dev-tools_0.153_all.deb ... Unpacking ubuntu-dev-tools (0.153) ... dpkg: error processing archive /var/cache/apt/archives/ubuntu-dev-tools_0.153_all.deb (--unpack): trying to overwrite '/usr/bin/bitesize', which is also in package perf-tools-unstable 0.0.1~20140723+git942be0b-3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for mime-support (3.57) ... Errors were encountered while processing: /var/cache/apt/archives/ubuntu-dev-tools_0.153_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/bin/bitesize 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 http://edos.debian.net/file-overwrites/. perf-tools-unstable=0.0.1~20140723+git942be0b-3_ubuntu-dev-tools=0.153.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: perf-tools-unstable Source-Version: 0.0.1~20140723+git942be0b-4 We believe that the bug you reported is fixed in the latest version of perf-tools-unstable, 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. Sebastien Delafond s...@debian.org (supplier of updated perf-tools-unstable 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, 01 Nov 2014 13:22:03 +0100 Source: perf-tools-unstable Binary: perf-tools-unstable Architecture: source all Version: 0.0.1~20140723+git942be0b-4 Distribution: unstable Urgency: medium Maintainer: Sebastien Delafond s...@debian.org Changed-By: Sebastien Delafond s...@debian.org Description: perf-tools-unstable - DTrace-like tools for Linux Closes: 767556 Changes: perf-tools-unstable (0.0.1~20140723+git942be0b-4) unstable; urgency=medium . * Record conflict with ubuntu-dev-tools (Closes: #767556) Checksums-Sha1: 3ce77a53d74452b8a3e873cc28efdd1a0f3dc80f 1749 perf-tools-unstable_0.0.1~20140723+git942be0b-4.dsc e2e7db9b5050072c43818b1bd033ae4ff8043dc3 2184 perf-tools-unstable_0.0.1~20140723+git942be0b-4.debian.tar.xz 558ae807496df65ba944ff75f78ec6977b4a8fb9 47208
Bug#767613: [kleopatra] hangs on OpenPGP-Zertifikate aktualisieren
Package: kleopatra Version: 4:4.14.2-2 Severity: grave on OpenPGP-Zertifikate aktualisieren runs kleopatra with 100 on 1 CPU and must be killed. The windows Subprozess Diagnose and Aktualisierung von OpenPGP-Zertifikaten - Fehler - Kleopatra are not scrollable. In Aktualisierung von OpenPGP-Zertifikaten - Fehler - Kleopatra the linefeeds are missing. This error is reproducible with every call. Kleopatra is partly, but in key areas, not usable, so I set the severity to grave. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/6 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 kleopatra depends on: ii dirmngr 1.1.1-4 ii gnupg-agent 2.0.26-3 ii gnupg22.0.26-3 ii gpgsm 2.0.26-3 ii kde-runtime 4:4.14.1-1+b1 ii libassuan02.1.2-2 ii libc6 2.19-12 ii libgcc1 1:4.9.1-16 ii libgpg-error0 1.16-2 ii libgpgme++2 4:4.14.2-1 ii libgpgme111.5.1-6 ii libkcmutils4 4:4.14.1-1+b1 ii libkdecore5 4:4.14.1-1+b1 ii libkdepim44:4.14.2-2 ii libkdeui5 4:4.14.1-1+b1 ii libkio5 4:4.14.1-1+b1 ii libkleo4 4:4.14.2-2 ii libkmime4 4:4.14.2-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libstdc++64.9.1-16 ii pinentry-gtk2 [pinentry-x11] 0.8.3-2 kleopatra recommends no packages. kleopatra suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 762361 to override: make-guile:devel/extra ..., severity of 764646 is normal
Processing commands for cont...@bugs.debian.org: retitle 762361 override: make-guile:devel/extra Bug #762361 [ftp.debian.org] make-guile should be priority: extra, not standard Changed Bug title to 'override: make-guile:devel/extra' from 'make-guile should be priority: extra, not standard' retitle 764646 RM: f-spot -- ROM; unmaintained, dead upstream, RC-buggy, depends on obsolete libs Bug #764646 [ftp.debian.org] RM: unmaintained, dead upstream, RC-buggy, depends on obsolete libs Changed Bug title to 'RM: f-spot -- ROM; unmaintained, dead upstream, RC-buggy, depends on obsolete libs' from 'RM: unmaintained, dead upstream, RC-buggy, depends on obsolete libs' severity 764646 normal Bug #764646 [ftp.debian.org] RM: f-spot -- ROM; unmaintained, dead upstream, RC-buggy, depends on obsolete libs Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 762361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762361 764646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764646 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: libpaper: diff for NMU version 1.1.24+nmu4
Processing control commands: tags 658159 + pending Bug #658159 [libpaper] [INTL:pl] Polish debconf translation Added tag(s) pending. tags 682420 + patch Bug #682420 [src:libpaper] libpaper: Multi-Arch: same but postrm removes arch-independent configuration Bug #695271 [src:libpaper] libpaper1: harmful purge action in M-A:same package Added tag(s) patch. Added tag(s) patch. tags 682420 + pending Bug #682420 [src:libpaper] libpaper: Multi-Arch: same but postrm removes arch-independent configuration Bug #695271 [src:libpaper] libpaper1: harmful purge action in M-A:same package Added tag(s) pending. Added tag(s) pending. tags 688293 + pending Bug #688293 [libpaper] [INTL:tr] Turkish debconf templates translation Added tag(s) pending. -- 658159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658159 682420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682420 688293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688293 695271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695271 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#682420: libpaper: diff for NMU version 1.1.24+nmu4
Control: tags 658159 + pending
Control: tags 682420 + patch
Control: tags 682420 + pending
Control: tags 688293 + pending
Dear maintainer,
I've prepared an NMU for libpaper (versioned as 1.1.24+nmu4) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Tom Waits: Black Market Baby
diff -Nru libpaper-1.1.24+nmu3/debian/changelog libpaper-1.1.24+nmu4/debian/changelog
--- libpaper-1.1.24+nmu3/debian/changelog 2014-04-04 03:00:09.0 +0200
+++ libpaper-1.1.24+nmu4/debian/changelog 2014-11-01 14:35:21.0 +0100
@@ -1,3 +1,18 @@
+libpaper (1.1.24+nmu4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix Multi-Arch: same but postrm removes arch-independent
+configuration:
+Guard removal of /etc/papersize in libpaper1.postrm with check for
+DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT; depend on dpkg (= 1.17.2).
+Thanks to Ivo De Decker for the proposal.
+(Closes: #682420)
+ * Debconf template translations:
+- new: Polish, thanks Michał Kułach, closes: #658159
+- updated: Turkish, thanks Atila KOÇ, closes: #688293
+
+ -- gregor herrmann gre...@debian.org Sat, 01 Nov 2014 14:35:13 +0100
+
libpaper (1.1.24+nmu3) unstable; urgency=low
* Non-maintainer upload.
diff -Nru libpaper-1.1.24+nmu3/debian/control libpaper-1.1.24+nmu4/debian/control
--- libpaper-1.1.24+nmu3/debian/control 2014-04-04 02:45:41.0 +0200
+++ libpaper-1.1.24+nmu4/debian/control 2014-11-01 14:12:56.0 +0100
@@ -9,7 +9,7 @@
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}, ucf (= 0.28)
+Depends: ${shlibs:Depends}, ${misc:Depends}, ucf (= 0.28), dpkg (= 1.17.2)
Replaces: libpaperg ( 1.1.9)
Provides: libpaperg
Recommends: libpaper-utils
diff -Nru libpaper-1.1.24+nmu3/debian/libpaper1.postrm libpaper-1.1.24+nmu4/debian/libpaper1.postrm
--- libpaper-1.1.24+nmu3/debian/libpaper1.postrm 2006-05-16 21:48:42.0 +0200
+++ libpaper-1.1.24+nmu4/debian/libpaper1.postrm 2014-11-01 14:12:33.0 +0100
@@ -4,8 +4,10 @@
case $1 in
purge)
-[ -x /usr/bin/ucf ] ucf --purge /etc/papersize
-rm -f /etc/papersize
+if [ ${DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT:-1} = 1 ]; then
+ [ -x /usr/bin/ucf ] ucf --purge /etc/papersize
+ rm -f /etc/papersize
+fi
;;
esac
exit 0
diff -Nru libpaper-1.1.24+nmu3/debian/po/pl.po libpaper-1.1.24+nmu4/debian/po/pl.po
--- libpaper-1.1.24+nmu3/debian/po/pl.po 1970-01-01 01:00:00.0 +0100
+++ libpaper-1.1.24+nmu4/debian/po/pl.po 2014-11-01 14:18:13.0 +0100
@@ -0,0 +1,300 @@
+# Copyright (C) 2007
+# This file is distributed under the same license as the libpaper package.
+#
+# Michał Kułach michal.kul...@gmail.com, 2012.
+msgid
+msgstr
+Project-Id-Version: \n
+Report-Msgid-Bugs-To: eppes...@debian.org\n
+POT-Creation-Date: 2007-07-18 19:50+0200\n
+PO-Revision-Date: 2012-01-31 18:40+0100\n
+Last-Translator: Michał Kułach michal.kul...@gmail.com\n
+Language-Team: Polish debian-l10n-pol...@lists.debian.org\n
+Language: pl\n
+MIME-Version: 1.0\n
+Content-Type: text/plain; charset=UTF-8\n
+Content-Transfer-Encoding: 8bit\n
+X-Generator: Lokalize 1.2\n
+Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10=2 n%10=4 (n%10010
+|| n%100=20) ? 1 : 2);\n
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid letter
+msgstr letter
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid a4
+msgstr A4
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid note
+msgstr note
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid legal
+msgstr legal
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid executive
+msgstr executive
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid halfletter
+msgstr halfletter
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid halfexecutive
+msgstr halfexecutive
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid 11x17
+msgstr 11x17
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid statement
+msgstr statement
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid folio
+msgstr folio
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid quarto
+msgstr quarto
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid 10x14
+msgstr 10x14
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid ledger
+msgstr ledger
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid tabloid
+msgstr tabloid
+
+#. Type: select
+#. Choices
+#: ../libpaper1.templates:2001
+msgid a0
+msgstr A0
+
+#. Type: select
+#. Choices
+#:
Processed (with 1 errors): merging 725543 766975
Processing commands for cont...@bugs.debian.org: merge 725543 766975 Bug #725543 [src:asterisk-flite] asterisk-flite: FTBFS: app_flite.c:168:13: error: dereferencing pointer to incomplete type Unable to merge bugs because: severity of #766975 is 'grave' not 'serious' Failed to merge 725543: Did not alter merged bugs thanks Stopping processing here. Please contact me if you need assistance. -- 725543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725543 766975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766975 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: libpaper: diff for NMU version 1.1.24+nmu4
Processing control commands: tags 658159 + pending Bug #658159 [libpaper] [INTL:pl] Polish debconf translation Ignoring request to alter tags of bug #658159 to the same tags previously set tags 682420 + patch Bug #682420 [src:libpaper] libpaper: Multi-Arch: same but postrm removes arch-independent configuration Bug #695271 [src:libpaper] libpaper1: harmful purge action in M-A:same package Ignoring request to alter tags of bug #682420 to the same tags previously set Ignoring request to alter tags of bug #695271 to the same tags previously set tags 682420 + pending Bug #682420 [src:libpaper] libpaper: Multi-Arch: same but postrm removes arch-independent configuration Bug #695271 [src:libpaper] libpaper1: harmful purge action in M-A:same package Ignoring request to alter tags of bug #682420 to the same tags previously set Ignoring request to alter tags of bug #695271 to the same tags previously set tags 688293 + pending Bug #688293 [libpaper] [INTL:tr] Turkish debconf templates translation Ignoring request to alter tags of bug #688293 to the same tags previously set -- 658159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658159 682420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682420 688293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688293 695271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695271 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: libpaper: diff for NMU version 1.1.24+nmu4
Processing control commands: tags 658159 + pending Bug #658159 [libpaper] [INTL:pl] Polish debconf translation Ignoring request to alter tags of bug #658159 to the same tags previously set tags 682420 + patch Bug #682420 [src:libpaper] libpaper: Multi-Arch: same but postrm removes arch-independent configuration Bug #695271 [src:libpaper] libpaper1: harmful purge action in M-A:same package Ignoring request to alter tags of bug #682420 to the same tags previously set Ignoring request to alter tags of bug #695271 to the same tags previously set tags 682420 + pending Bug #682420 [src:libpaper] libpaper: Multi-Arch: same but postrm removes arch-independent configuration Bug #695271 [src:libpaper] libpaper1: harmful purge action in M-A:same package Ignoring request to alter tags of bug #682420 to the same tags previously set Ignoring request to alter tags of bug #695271 to the same tags previously set tags 688293 + pending Bug #688293 [libpaper] [INTL:tr] Turkish debconf templates translation Ignoring request to alter tags of bug #688293 to the same tags previously set -- 658159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658159 682420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682420 688293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688293 695271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695271 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: cloning 703589, reassign -1 to ftp.debian.org, severity of -1 is normal ..., tagging 749836 ...
Processing commands for cont...@bugs.debian.org: clone 703589 -1 Bug #703589 [ptex-jisfonts] ptex-jisfonts: not installable in sid Bug 703589 cloned as bug 767614 reassign -1 ftp.debian.org Bug #767614 [ptex-jisfonts] ptex-jisfonts: not installable in sid Bug reassigned from package 'ptex-jisfonts' to 'ftp.debian.org'. No longer marked as found in versions ptex-jisfonts/2-21.2. Ignoring request to alter fixed versions of bug #767614 to the same values previously set severity -1 normal Bug #767614 [ftp.debian.org] ptex-jisfonts: not installable in sid Severity set to 'normal' from 'serious' retitle -1 RM: ptex-jisfonts -- RoQA; RC-buggy, superseded by texlive-lang-cjk Bug #767614 [ftp.debian.org] ptex-jisfonts: not installable in sid Changed Bug title to 'RM: ptex-jisfonts -- RoQA; RC-buggy, superseded by texlive-lang-cjk' from 'ptex-jisfonts: not installable in sid' tags 749836 - moreinfo Bug #749836 [ftp.debian.org] RM: makejvf -- ROM; included in texlive-binaries Removed tag(s) moreinfo. block 749836 with -1 Bug #749836 [ftp.debian.org] RM: makejvf -- ROM; included in texlive-binaries 749836 was not blocked by any bugs. 749836 was not blocking any bugs. Added blocking bug(s) of 749836: 767614 thanks Stopping processing here. Please contact me if you need assistance. -- 703589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703589 749836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749836 767614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767614 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#767615: [LCD Weather Station] timeout on wettercom
Package: plasma-widgets-addons Version: 4:4.14.1-1 Severity: grave On LCD Weather Station the city was found, but on geting the wetherdata it aways runs into a timeout. There is no other source available or selectable, so the program is unusable. So I set the severity to grave. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/6 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 plasma-widgets-addons depends on: ii libc6 2.19-12 ii libcln6 1.3.4-1 ii libdbusmenu-qt2 0.9.2-1 ii libgcc1 1:4.9.1-16 ii libkcmutils4 4:4.14.1-1+b1 ii libkdeclarative5 4:4.14.1-1+b1 ii libkdecore5 4:4.14.1-1+b1 ii libkdeui5 4:4.14.1-1+b1 ii libkdewebkit5 4:4.14.1-1+b1 ii libkexiv2-11 4:4.14.2-1 ii libkfile4 4:4.14.1-1+b1 ii libkio5 4:4.14.1-1+b1 ii libknewstuff3-4 4:4.14.1-1+b1 ii libkparts44:4.14.1-1+b1 ii libkunitconversion4 4:4.14.1-1+b1 ii libnepomuk4 4:4.14.1-1+b1 ii libnepomukutils4 4:4.14.1-1+b1 ii libphonon44:4.8.0-3 ii libplasma34:4.14.1-1+b1 ii libplasmaclock4abi4 4:4.11.13-1 ii libqalculate5 0.9.7-9 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-declarative4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-svg4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtwebkit4 2.3.4.dfsg-3 ii libstdc++64.9.1-16 ii libtaskmanager4abi4 4:4.11.13-1 ii libx11-6 2:1.6.2-3 ii libxtst6 2:1.2.2-1 ii phonon4:4.8.0-3 ii plasma-dataengines-addons 4:4.14.1-1 ii plasma-dataengines-workspace 4:4.11.13-1 Versions of packages plasma-widgets-addons recommends: ii plasma-widget-lancelot 4:4.14.1-1 Versions of packages plasma-widgets-addons suggests: pn plasma-widget-kimpanel none -- 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#767616: lyx: fails to upgrade from 'testing' - trying to overwrite /usr/share/icons/hicolor/48x48/apps/lyx.png
Package: lyx Version: 2.1.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to unpack .../archives/lyx_2.1.2-3_amd64.deb ... Unpacking lyx (2.1.2-3) over (2.1.2-2) ... dpkg: error processing archive /var/cache/apt/archives/lyx_2.1.2-3_amd64.deb (--unpack): trying to overwrite '/usr/share/icons/hicolor/48x48/apps/lyx.png', which is also in package lyx-common 2.1.2-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../lyx-common_2.1.2-3_all.deb ... Unpacking lyx-common (2.1.2-3) over (2.1.2-2) ... Errors were encountered while processing: /var/cache/apt/archives/lyx_2.1.2-3_amd64.deb cheers, Andreas lyx_2.1.2-3.log.gz Description: application/gzip
Bug#766349: Kmail: Some times sign with S/MIME failed
On November 1, 2014 12:52:01 AM CDT, Jörg Frings-Fürst deb...@jff-webhosting.net wrote: Hi, Am Samstag, 1. November 2014, 00:22:43 schrieb Scott Kitterman: Is there a pattern about when it fails and when it doesn't? No, only that I can sign 3 or 4 mail and then all other failed without any errormessage. For me I think is a memory hole... When you filed this bug, you filed it at severity critical. In Debian, critical is defined as: critical makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. I think that a not or wrong encrypted or signed mail is already a security issue. Failing to sign and failing to encrypt have different impacts (and thus severity). Is it also failing to encrypt? The bug only mentions signing. Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765314: mrpt: FTBFS on all non-x86-based architectures
Dear Olly, I think that all problematic old mrpt packages are now removed after the FTP removal request: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765962 Shall we re-upload a new patched version of MRPT for the system to re-try to get it into testing? Or it should go on automatically? (1.2.2-1.1 packages for 'standard' architectures are still there...) Best, and thanks for the help. JL On Thu, Oct 16, 2014 at 4:02 AM, Olly Betts o...@survex.com wrote: On Wed, Oct 15, 2014 at 01:40:43PM +0200, Jose Luis Blanco wrote: I would add a third patch to fix (avoid) errors in hurd. If you have the possibility of adding it it would be great! So, these are the 3 patches: https://github.com/jlblancoc/mrpt/commit/693bebedac9234fa00304a26aa854f54dc4d674f https://github.com/jlblancoc/mrpt/commit/bb294b9c7a9aef3b4bbbdc89811e7873805eba19 https://github.com/jlblancoc/mrpt/commit/c81effd1228234e2ed17caf0ef22f0caee6b Can be downloaded as git diffs as well: https://github.com/jlblancoc/mrpt/commit/693bebedac9234fa00304a26aa854f54dc4d674f.diff https://github.com/jlblancoc/mrpt/commit/bb294b9c7a9aef3b4bbbdc89811e7873805eba19.diff https://github.com/jlblancoc/mrpt/commit/c81effd1228234e2ed17caf0ef22f0caee6b.diff I don't mind making another NMU, but since mrpt takes an hour to build, I'd prefer to try to fix all the architectures at once, and mipsel has also failed to build with an internal compiler error: https://buildd.debian.org/status/fetch.php?pkg=mrptarch=mipselver=1%3A1.2.2-1.1stamp=1413406454 On Wed, Oct 15, 2014 at 7:31 AM, Jose Luis Blanco joseluisblan...@gmail.com wrote: Any recommendation about how to test it locally on s390x? qemu or alike? I've not tried qemu myself - I'd guess it's likely to take quite a while to build under qemu though. You can request guest access to the debian porter boxes: https://dsa.debian.org/doc/guest-account/ Not sure if you're a DM or in NM, but if not you'll need to get a DD to sponsor the request. It's probably most appropriate to get your usual upload sponsor to send in the request, but I guess I can if he/she isn't available. A partner got it tested in a physical mips device before submitting, so hopefully it will work there... It's not yet tried to build there yet. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767387: beignet 0.8+dfsg-1
This is my proposed freeze-policy-compliant 0.8+dfsg-1 for jessie (0.9.3
would go to jessie-backports). Please do not upload right now as it
hasn't been tested yet.
It may still happen that we decide to drop beignet from jessie and just
have 0.9.3 in -backports, but I'd rather not be rushed into choosing.
Non-DFSG files deleted:
kernels/lenna128x128.bmp kernels/compiler_box_blur_float_ref.bmp
kernels/compiler_box_blur_ref.bmp 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_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
Debian directory diff:
diff -Nru beignet-0.8/debian/changelog beignet-0.8+dfsg/debian/changelog
--- beignet-0.8/debian/changelog2014-09-12 17:11:43.0 +0100
+++ beignet-0.8+dfsg/debian/changelog 2014-11-01 14:08:08.0 +
@@ -1,3 +1,13 @@
+beignet (0.8+dfsg-1) unstable; urgency=medium
+
+ * Change of maintainer.
+ * Remove non-DFSG tests. (Closes: #767387)
+ * Revert to LLVM/Clang 3.4, update versioned-llvm-tools.patch.
+(Closes: #764930)
+ * State in the description what hardware this supports.
+
+ -- Rebecca N. Palmer rebecca_pal...@zoho.com Sat, 01 Nov 2014
14:01:26 +
+
beignet (0.8-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru beignet-0.8/debian/control beignet-0.8+dfsg/debian/control
--- beignet-0.8/debian/control 2014-09-11 16:43:33.0 +0100
+++ beignet-0.8+dfsg/debian/control 2014-11-01 14:01:06.0 +
@@ -1,12 +1,16 @@
Source: beignet
Priority: extra
-Maintainer: Simon Richter s...@debian.org
+Maintainer: Debian OpenCL Maintainers
pkg-opencl-de...@lists.alioth.debian.org
+Uploaders:
+ Simon Richter s...@debian.org,
+ Rebecca N. Palmer rebecca_pal...@zoho.com,
+ Andreas Beckmann a...@debian.org,
Build-Depends: debhelper (= 9), cmake, pkg-config, python-minimal,
ocl-icd-dev, ocl-icd-opencl-dev,
libdrm-dev, libxfixes-dev, libxext-dev,
- llvm-dev (= 1:3.4),
- clang (= 1:3.4),
- libclang-dev (= 1:3.4),
+ llvm-3.4-dev,
+ clang-3.4,
+ libclang-3.4-dev,
libgl1-mesa-dev (= 9) [!kfreebsd-any],
libegl1-mesa-dev (= 9) [!kfreebsd-any],
libgbm-dev (= 9) [!kfreebsd-any],
@@ -34,9 +38,13 @@
Conflicts: beignet0.0.1
Replaces: beignet0.0.1
Provides: opencl-icd
-Description: Intel OpenCL library
+Description: OpenCL library for Intel Ivy Bridge GPUs
OpenCL (Open Computing Language) is a multivendor open standard for
general-purpose parallel programming of heterogeneous systems that
include
CPUs, GPUs and other processors.
.
This package contains the shared library for the Intel implementation.
+ .
+ This version of the package supports only Ivy Bridge GPUs
+ (HD Graphics 2500/4000, Core ix-3xxx); versions supporting new hardware
+ will be made available in -backports.
diff -Nru beignet-0.8/debian/patches/versioned-llvm-tools
beignet-0.8+dfsg/debian/patches/versioned-llvm-tools
--- beignet-0.8/debian/patches/versioned-llvm-tools 2014-04-19
18:54:55.0 +0100
+++ beignet-0.8+dfsg/debian/patches/versioned-llvm-tools 2014-11-01
13:28:17.0 +
@@ -1,9 +1,20 @@
Description: Use versioned LLVM tools
-Author: Simon Richter s...@debian.org
-Last-Update: 2014-04-19
+Author: Simon Richter s...@debian.org, Rebecca N. Palmer
rebecca_pal...@zoho.com
+Bug-Debian: https://bugs.debian.org/759933,https://bugs.debian.org/764930
--- beignet-0.8.orig/backend/src/CMakeLists.txt
+++ beignet-0.8/backend/src/CMakeLists.txt
+@@ -58,8 +58,8 @@ set (clang_cmd ${clang_cmd} -fno-builtin
+ add_custom_command(
+ OUTPUT ${pch_object}
+ COMMAND rm -f ${pch_object}
+- COMMAND clang ${clang_cmd} --relocatable-pch -emit-pch -isysroot
${CMAKE_CURRENT_BINARY_DIR} ${ocl_blob_file} -o ${pch_object}
+- COMMAND clang ${clang_cmd} -emit-pch ${ocl_blob_file} -o
${local_pch_object}
++ COMMAND clang-3.4 ${clang_cmd} --relocatable-pch -emit-pch
-isysroot ${CMAKE_CURRENT_BINARY_DIR} ${ocl_blob_file} -o ${pch_object}
++ COMMAND clang-3.4 ${clang_cmd} -emit-pch ${ocl_blob_file} -o
${local_pch_object}
+ DEPENDS ${ocl_blob_file}
+ )
+
@@ -71,14 +71,14 @@ macro(ll_add_library ll_lib ll_sources)
add_custom_command(
OUTPUT ${ll}.bc
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718624: Possible problem with the patch
On Sun, 26 Oct 2014 20:30:23 +0530 Sunil Mohan Adapa su...@medhas.org wrote: Hello, I was interested in the fix that the patch aims to provide. A casual glance revealed a potential problem. +if dpkg --compare-versions $2 lt 2.84-0.2~; then +mkdir -p /var/lib/transmission-daemon/.config/transmission-daemon +chown -R debian-transmission:debian-transmission /var/lib/transmission-daemon/* /var/lib/transmission-daemon/* would not include .config folder. .config folder will end up being owned by 'root' user. After upgrade, the daemon would not be able to write to the settings.json file before exit. So settings modified using RPC or web interface will not be saved on exit. I have not tested this though. Thanks for Transmission, Transmission packaging and the patch. Hello Sunil, while the .config folder is owned by root .config/transmission-daemon is owned by debian-transmission thus all configuration files can be written successfully. Please CC me, I am not subscribed to this bug report. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#767626: wine64-tools: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/wine/bin/winegcc
Package: wine64-tools Version: 1.6.2-14 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package wine64-tools. Preparing to unpack .../wine64-tools_1.6.2-14_amd64.deb ... Unpacking wine64-tools (1.6.2-14) ... dpkg: error processing archive /var/cache/apt/archives/wine64-tools_1.6.2-14_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/wine/bin/winegcc', which is also in package wine64-dev-tools 1.6.2-8 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../wine64-dev-tools_1.6.2-14_amd64.deb ... Unpacking wine64-dev-tools (1.6.2-14) over (1.6.2-8) ... Preparing to unpack .../libwine-dev_1.6.2-14_amd64.deb ... Unpacking libwine-dev:amd64 (1.6.2-14) over (1.6.2-8) ... Preparing to unpack .../libwine_1.6.2-14_amd64.deb ... Unpacking libwine:amd64 (1.6.2-14) over (1.6.2-8) ... Preparing to unpack .../multiarch-support_2.19-12_amd64.deb ... Unpacking multiarch-support (2.19-12) over (2.19-11) ... Errors were encountered while processing: /var/cache/apt/archives/wine64-tools_1.6.2-14_amd64.deb cheers, Andreas wine64-dev-tools_1.6.2-14.log.gz Description: application/gzip
Processed: forcibly merging 725543 766975
Processing commands for cont...@bugs.debian.org: forcemerge 725543 766975 Bug #725543 [src:asterisk-flite] asterisk-flite: FTBFS: app_flite.c:168:13: error: dereferencing pointer to incomplete type Bug #766975 [src:asterisk-flite] asterisk-flite: FTBFS: fails to build with asterisk 13. Use latest version Severity set to 'serious' from 'grave' Merged 725543 766975 thanks Stopping processing here. Please contact me if you need assistance. -- 725543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725543 766975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 767615 is important
Processing commands for cont...@bugs.debian.org: severity 767615 important Bug #767615 [plasma-widgets-addons] [LCD Weather Station] timeout on wettercom Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 767615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767615 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#762638: metaconfig source control/distribution and Debian's DFSG
Hi all, Apologies for another long delay in replying; other matters have taken up most of my recent energy. I'm replying to both H.Merijn Brand and Andy Dougherty's most recent messages on the subject here. I've snipped some quoted parts for brevity, but kept what I hope are the most pertinent bits of conversation, to help summarise. On Sat, Oct 04, 2014 at 08:23:10PM +0200, H.Merijn Brand wrote: On Sat, 4 Oct 2014 17:50:51 +0100, Dominic Hargreaves d...@earth.li On Thu, Sep 25, 2014 at 09:07:59PM -0400, Andy Dougherty wrote: If we include all the units in the source tree instead, I think end users will have an expectation of greater support. They will expect it to work, and work easily, right out of the box. Getting it to that point will require significant effort, and I really don't see the benefit. Of course, if someone else wants to do it and support it, that's fine with me. One benefit would be that we wouldn't this acknowledged bus factor issue with the metaconfig wrangling. Disagree. Areas in the perl core are picked up by people that like that area: • Threading • 64bit/32bit • Regex • COW • Speed • Debugging • Toolchain • Configuration • … It just happens that Configuration is NOT an area that appeals to developers. It works, and they are happy it works the way it does. Improving the configuration or the configuration process does NOT make the language itself more appealing or more interesting, and eventually, that is what the developers want (to achieve). Yes, the bus-factor is (too) low, but it is not caused by (un)availability of the pieces Okay, I accept this. If we have to, we can make a tarball of that repository and include it with the perl source package, but it seems like it would we should explore the possibility of fixing this discrepancy upstream, rather than working around it in Debian. In fact, it's likely we'd also have to supply the patches between the current metaconfig output and what's actually in the perl release tarball, since Configure is explicitly allowed to be patched even though it's generated. To be complete, you would have to include both perl's metaconfig repository and an appropriately patched 'dist' source tree, which would likely differ somewhat from Debian's existing 'dist' tree. If the intent is to actually use it, there are probably a bunch of installation issues to work out. If you want to check your results, you'll have to confront the reshuffling problem. Short summary: I think it would be a lot of work for very little gain. On Fri, Sep 26, 2014 at 08:34:58AM +0200, H.Merijn Brand wrote: The main problem with generating Configure from meta is not the availability of the metaunits used for perl, but the way meta/dist has to be installed to make them work the way it does. Do you mean the fact that dist is being patched, or some other reason? Just like learning a new language, the whole *process* is rather complicated. It is not like most GNU tools sh autogen.sh, configure, make check, make install, but - for people building perl - Configure, make test, make install The source code for autogen is widely available, but it works fine only on Linux. (I'd invite you to the hell of using the auto* and (even worse) libtool on OS's like AIX and HP-UX. To make the developers' life of our Perl community *less* of a hell, we are shipping Configure, which is a autoconf/autogen/configure in one, that runs on almost every *nix like platform (VMS and Windows have special cased support). For how many of the GNU tools that you ship, do you include the autogen.sh stuff that is only used *before* the configure is included in the source package? I only see the auto-stuff if I clone the source repo for the tool itself. Most of the autotools stuff in Debian ships the source files and it's generally encourages to rerun autoconf/automake to generate configure these days, so that changes needed to support new architectures, etc, can be reflected without any work on the source of the package. The fact that we patched and extended meta is NO reason for it to be more complex than using meta/dist from scratch. It is like installing a patched version of autoconf. The changes are reasonable well documented, and the source is widely and openly available. Or at least it is now, thank you :) As the current maint for this process, I communicate with the maintainer of dist/meta on a rather regular basis. I give feedback of what we changed, and I look at the changes he makes to see if those will be usable for perl. As part of the metaunits is still used from dist, part is a set of (slightly) modified units from dist, and part is the units written only for perl, keeping those in sync is a hell of a job. On simply cannot stay in sync 100% Okay, so clearly from a pragmatic view we would need to
Bug#767628: pocl: ftbfs on several architectures
package: pocl version: 0.10-10 severity: serious Hi, The latest upload of pocl fails on a number of architectures where it built fine before, preventing migration to testing. https://buildd.debian.org/status/package.php?p=poclsuite=sid 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#767498: [Debichem-devel] Bug#767498: aces3: FTBFS on several architectures
On Sat, Nov 01, 2014 at 01:01:42PM +0100, Michael Banck wrote: So I will look about patching it out in the build system, rather, which should help the other buildds as well. Unfortunately, the F12 technology appears to be coded in pretty deeply. I had hoped that due to the way ACESIII is coded, it would be restricted to some specific SIAL (some bytecode language) codes which could be ommitted. However, it is also coupled to the integral routines, which are at the core of the system. So patching it out is unfortunately unfeasable. The next thing I noticed is that due to a bug or undocumented feature in the Makefiles, $(FFLAGS) is not used when compiling that code. As an aside that code is also the only Fortran90 code in the project. For those source files, $(FFLAGS1) is used in the Makefile, which is never defined, so no compiler flags at all are passed to make. That means that those files already get compiled without optimization. So far, I could not get it to link successfully on armhf with providing different compiler options, I've asked in #debian-arm now. The way forward appears to be to give-back aces3 and hope that it builds at least on s390x (and possibly mips*, if it gets queued on a beefier buildd), and then get the binary packages of the non-building arches removed in time for the freeze. Alas, it turns out -lmpi_cxx as added to GNULIBS in debian/rules will make it FTBFS on s390x. That's a shame, cause AFAICT after some investigation it's superfluous anyway (I copied it from INSTALL). Maybe that could be fixed post-freeze by a small patch, while removing the s390x binary from unstable for now. Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767630: birdfont: depends on libgit2-dev which is unavailable on kfreebsd and s390x
package: birdfont version: 1.7-1 severity: serious Hi, All recent uploads of birdfont build-depend on libgit2-dev, which is unavailable on kfreebsd and s390x. As birdfont built fine before on these architectures, this prevents migration to testing. This probably means the you need to request the removal from unstable of the binaries on these architectures (and close this bug at that point), to allow the package to migrate. 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#767632: ust: FTBFS on most architectures
package: ust severity: serious version: 2.5.1-1 Hi, The latest upload of ust fails on most architectures, but built fine in the past. This prevents migration to testing. https://buildd.debian.org/status/package.php?p=ust 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#767633: nsca-ng: depends on libsystemd-dev, which is unavailable on kfreebsd
package: nsca-ng severity: serious version: 1.4-1 Hi, The latest upload of nsca-ng build-depends on libsystemd-dev, which is unavailable on kfreebsd. The kfreebsd binaries from the old version prevent migration to testing. 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#743853: libpango-1.0-0 : Breaks: libpango1.0-0 ( 1.32.5-2) but 1.30.0-1 is to be installed
On Wed, 30 Jul 2014 12:32:36 +0200, Holger Levsen wrote: On Mittwoch, 30. Juli 2014, Simon McVittie wrote: I wonder whether this might have been the same apt issue as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722912. Do you use wheezy's apt or jessie's apt (or something else, like aptitude) for the upgrade? #722912 appears to have been fixed in jessie's apt. I use wheezy's apt (until it's upgraded). Looking at this jenkins job at https://jenkins.debian.net/job/chroot-installation_wheezy_install_developer_upgrade_to_jessie/ it seems (just from the build history column on the left) that the job has run successfully for the last ~20 days, so I assume this bug was temporarily and has (been) fixed (itself)? Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Bettina Wegner: Kinder signature.asc Description: Digital Signature
Bug#767633: nsca-ng: depends on libsystemd-dev, which is unavailable on kfreebsd
On Sat, 01 Nov 2014, Ivo De Decker wrote: package: nsca-ng severity: serious version: 1.4-1 Hi, The latest upload of nsca-ng build-depends on libsystemd-dev, which is unavailable on kfreebsd. The kfreebsd binaries from the old version prevent migration to testing. Yai, I'll remove those kfreebsd binarys. Alex -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633730: #FTBFS now earlier in build process
On Wed, 13 Aug 2014 15:51:06 +0100, Pedro Beja wrote: Hey Willi, see #741785. #741785 is fixed in 3.8.1-2 but the package still FTBFS on various architectures: https://buildd.debian.org/status/logs.php?pkg=seedver=3.8.1-2 Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Andrew Lloyd Webber Tim Rice signature.asc Description: Digital Signature
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
Hi Dominik, On 31-10-14 15:32, Paul Gevers wrote: dbconfig-generate-include should be called by dpkg/common on line 547 with the -U option, so the path should be the ucf path. While I was thinking about it I believe that indeed all the configuration files which are not conffiles should be handled by ucf, because that is supposed to do-the-right-thing. The more I look at the code, the less I am convinced that your patch in dbconfig-common actually solves your problem. I added set -x and set +x to dbconfig-generate-include around the block that we are discussing, and when I reconfigure roundcube-core I see: (pbuild29710)root@wollumbin:/# dpkg-reconfigure roundcube-core dbconfig-common: writing config to /etc/dbconfig-common/roundcube.conf + [ /etc/roundcube/debian-db.php ] + ls -al /tmp/dbconfig-generate-include.7z8TTm -rw--- 1 root root 546 Nov 1 12:04 /tmp/dbconfig-generate-include.7z8TTm + ls -al /etc/roundcube/debian-db.php -rw-r- 1 root www-data 546 Nov 1 10:51 /etc/roundcube/debian-db.php + [ 1 ] + ucf --debconf-ok /tmp/dbconfig-generate-include.7z8TTm /etc/roundcube/debian-db.php Replacing config file /etc/roundcube/debian-db.php with new version + rm -f /tmp/dbconfig-generate-include.7z8TTm + ls -al /etc/roundcube/debian-db.php -rw--- 1 root root 546 Nov 1 12:04 /etc/roundcube/debian-db.php + check_permissions + local line + dpkg-statoverride --list /etc/roundcube/debian-db.php + [ ] + [ ] + ls -al /etc/roundcube/debian-db.php -rw--- 1 root root 546 Nov 1 12:04 /etc/roundcube/debian-db.php + set +x apache2_invoke roundcube.conf: already enabled invoke-rc.d: policy-rc.d denied execution of reload. invoke-rc.d: policy-rc.d denied execution of reload. (pbuild29710)root@wollumbin:/# Your patch in the else statement is completely irrelevant in this sequence. So my question, how did you test your patch? [1] Furthermore, I have been reading up on the use of cp. It seems, but if you are using ACL's I like you to test, that cp opens the file for writing, so it should keep existing ACL's AFAICT. Paul [1] I think I now understand why my fix for bug 720517 was wrong and I didn't catch that during my testing. I had a local change, and then ucf leaves the original file completely alone. I didn't test better, because my expectation from ucf was just wrong. signature.asc Description: OpenPGP digital signature
Bug#728955: libatomic-ops: patch from Ubuntu
On Wed, 20 Aug 2014 12:04:02 +0200, Frédéric Bonnard wrote: Package: libatomic-ops Version: 7.4.2-1 Followup-For: Bug #728955 User: debian-powe...@lists.debian.org Usertags: ppc64el Dear Maintainer, the same problem occurs on ppc64el and here is a patch that provides : - a fix from Ubuntu - support for quilt patches with debian/source/format According to the build logs at https://buildd.debian.org/status/package.php?p=libatomic-opssuite=unstable https://buildd.debian.org/status/logs.php?pkg=libatomic-opsver=7.4.2-1 7.4.2-1 built everywhere, including powerpc and ppc64el (but these two needed two attempts). (And 7.4.2-1 migrated to testing despite this bug report ?!) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#767209: Fix pending
tags 767209 + fixed patch pending
thanks
Thanks for letting us know Julien.
I've found the problem. -fpie was added to BibleTime_CFLAGS unconditionally in
CMakeLists.txt
I've confirmed that it will build with this on zelenka, the s390x porterbox
Patch attached.
I'm not set up at the moment for building and uploading the package so if
someone gets to it
before I'm ready then please review, build and upload (including NMUers)
Regards,
Daniel
Index: bibletime-2.10.1/CMakeLists.txt
===
--- bibletime-2.10.1.orig/CMakeLists.txt
+++ bibletime-2.10.1/CMakeLists.txt
@@ -205,7 +205,7 @@ IF(MSVC)
SET(CMAKE_CXX_FLAGS_DEBUG -DNO_DBUS -DSWUSINGDLL /MDd /Zc:wchar_t- /W1 /D_UNICODE /DUNICODE /Zc:wchar_t /Od)
SET(BibleTime_LDFLAGS ${BibleTime_LDFLAGS} /SUBSYSTEM:WINDOWS)
ELSE()
- SET(BibleTime_CFLAGS ${BibleTime_CFLAGS} -Wextra -fpie -fexceptions)
+ SET(BibleTime_CFLAGS ${BibleTime_CFLAGS} -Wextra -fexceptions)
SET(CMAKE_CXX_FLAGS_RELEASE -O2)
SET(CMAKE_CXX_FLAGS_DEBUG -ggdb)
IF(APPLE)
signature.asc
Description: Digital signature
Processed: Fix pending
Processing commands for cont...@bugs.debian.org: tags 767209 + fixed patch pending Bug #767209 [src:bibletime] bibletime: FTBFS on s390x (relocation truncated to fit) Added tag(s) fixed, pending, and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 767209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767209 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#767411: torque: should not be released with jessie
Hi Julien, On Fri, Oct 31, 2014 at 02:07:25PM +0100, Julien Cristau wrote: On Thu, Oct 30, 2014 at 22:27:53 +0100, Salvatore Bonaccorso wrote: pbs-drmaa as reverse dependency of torque is easy as it is a leaf package. The more complicated one would be openmpi which would need to drop the build dependency on libtorque2-dev. The reason for this dependency was in https://bugs.debian.org/592887 , which needs to be dropped again. There's two solutions here. One is to drop torque support from openmpi; the other is to keep the torque source package but only build the libtorque library, as I'm assuming the security issues are on the torque server side. Though that's only useful is that library can still talk to newer torque version. Given Dominique's reply on #767411, from my POV I think the best solution would be to remove torque completely for jessie (i.e. first drop support from openmpi to be able to remove the package and remaining reverse dependencies). Alastair, could you please take care of updating openmpi to drop the torque support? Regards, Salvatore signature.asc Description: Digital signature
Bug#767230: bitlbee-plugin-otr: bitlbee no longer starts: libotr API version 4.1.0 incompatible with actual version 4.0.0
Hi, dequis wrote (30 Oct 2014 05:06:31 GMT) : API and ABI are still compatible, despite what the OTRL_INIT error may suggest. May you please share how you've verified this? We need to check that both for plan A and B anyway. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767230: libotr transition started by mistake :-/
Hi, Niels Thykier wrote (30 Oct 2014 22:05:20 GMT) : On 2014-10-29 17:09, intrigeri wrote: Plan A -- ship Jessie with libotr 4.1, drop the version check temporarily = 1. Patch libotr to loosen this version check on Jessie: assuming the no API/ABI break assumption is true, this should work just fine. I suspect this will be the least intrusive method assuming the no ABI/API assertion holds. I'll check this the best I can (I'll try my best with the readelf command you provided and also will generate shlibs files for both 4.0 and 4.1, and compare what's in there). I'll also test, as a practical usecase, that e.g. pidgin-otr built against libotr 4.0 works fine with libotr 4.1. 2. For Jessie+1, re-add the version check, and get proper shlibs support so that we get proper transition handling next time. As I recall, we generally prefer libraries do not have unnecessary strictly equal runtime version checks, since they tend to be wrong. Proper use of shlibs (or symbols) and SONAME bumping (with package renaming) makes such checks redundant (for Debian maintained reverse dependencies). Actually, the way I understand the code, what we have here is not a strictly equal runtime version check, but rather runtime version greater or equal to the build-time one, which is better in that it doesn't require binNMUs. But anyway, for Jessie+1 I'll add shlibs support, so indeed this check will be redundant; and then, my understanding is that it'll also become fully harmless. I generally agree with plan A (with the a minor remark mentioned above). OK, I'll do that. Thanks! Please also prepare a debdiff between libotr/4.1.0-1 and the proposed version[1] and send it to us (to this thread), so we can review the additional changes we will accept. Sure, will do. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 767557
Processing commands for cont...@bugs.debian.org: tags 767557 + pending Bug #767557 [libsocl-1.1-1,libsocl-contrib-1.1-1] libsocl-1.1-1,libsocl-contrib-1.1-1: error when trying to install together Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 767557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767557 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#767644: watchdog: modifies conffiles (policy 10.7.3): /etc/default/watchdog
Package: watchdog Version: 5.14-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/default/watchdog cheers, Andreas watchdog_5.14-1.log.gz Description: application/gzip
Bug#767646: miniupnpd: modifies conffiles (policy 10.7.3): /etc/miniupnpd/miniupnpd.conf
Package: miniupnpd Version: 1.8.20140523-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/miniupnpd/miniupnpd.conf cheers, Andreas miniupnpd_1.8.20140523-2.log.gz Description: application/gzip
Bug#767568: bibledit-bibletime needs to breaks+replaces bibledit 4.6-1
tags + pending thanks Thanks Andreas, A breaks+replaces on bibledit 4.6-1 (wheezy version) is indeed what is needed. (fwiw bibledit-bibletime only appeared in wheezy not squeeze.) I'm not set up for building and uploading right now so NMUs welcome. Daniel signature.asc Description: Digital signature
Bug#767649: fookebox: modifies conffiles (policy 10.7.3): /etc/fookebox/config.ini
Package: fookebox Version: 0.6.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/fookebox/config.ini cheers, Andreas fookebox_0.6.1-3.log.gz Description: application/gzip
Bug#743853: libpango-1.0-0 : Breaks: libpango1.0-0 ( 1.32.5-2) but 1.30.0-1 is to be installed
Hi Gregor, On Samstag, 1. November 2014, gregor herrmann wrote: Looking at this jenkins job at https://jenkins.debian.net/job/chroot-installation_wheezy_install_developer _upgrade_to_jessie/ it seems (just from the build history column on the left) that the job has run successfully for the last ~20 days, so I assume this bug was temporarily and has (been) fixed (itself)? I doubt it fixed itself but I'd be fine with closing it :-) Thanks for notifiying! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#762061: virtualbox-dkms fails to build on standard 3.14.15 kernel
Control: severity -1 normal On Thu, 18 Sep 2014 14:30:32 +0100, Ben Hutchings wrote: @Debian Kernel Maintainers: What would you recommend we add a Recommends for ? Nothing. Reassign this to dkms (with lower severity) and let them handle it. reassign + retitle have happened, doing the missing downgrading of the severity now. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Johnny Cash: Field Of Diamonds signature.asc Description: Digital Signature
Processed: Re: Bug#762061: virtualbox-dkms fails to build on standard 3.14.15 kernel
Processing control commands: severity -1 normal Bug #762061 [dkms] dkms should pull in the correct linux-headers package Severity set to 'normal' from 'grave' -- 762061: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 599670 is grave
Processing commands for cont...@bugs.debian.org: severity 599670 grave Bug #599670 [imdb-tools] [imdb-tools] New IMDb layout completely breaks parsing Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 599670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599670 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#743853: libpango-1.0-0 : Breaks: libpango1.0-0 ( 1.32.5-2) but 1.30.0-1 is to be installed
On Sat, 01 Nov 2014 17:27:17 +0100, Holger Levsen wrote: On Samstag, 1. November 2014, gregor herrmann wrote: Looking at this jenkins job at https://jenkins.debian.net/job/chroot-installation_wheezy_install_developer _upgrade_to_jessie/ it seems (just from the build history column on the left) that the job has run successfully for the last ~20 days, so I assume this bug was temporarily and has (been) fixed (itself)? I doubt it fixed itself but I'd be fine with closing it :-) Thanks for notifiying! Thanks, I guess I leave the pleasure of closing to the maintainer :) Cheers, gregor, in rc-bug-fixing-by-communicating mood -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Cássia Eller: Quando A Mare Encher signature.asc Description: Digital Signature
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 Version: 5.1.0.41.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 5.1.0.41-3 Hi, during a test with piuparts I noticed your package modifies files from another package. This is so wrong, I'm not even bothered to look up the part of policy this violates ;-P From the attached log (scroll to the bottom...): 0m23.6s ERROR: FAIL: debsums reports modifications inside the chroot: /var/lib/ni/modules.xml The file is owned by libopenni0. If you run the following command after installing the buggy packages apt-get install --reinstall libopenni0 /var/lib/ni/modules.xml will be reset to its shipped state. The same would happen if libopenni0 gets binNMUed for some reason ... so the current approach is very fragile. Since modules.xml is used as some kind of registry, it should only be generated, not shipped at all. Ideally dpkg triggers could be used for this task. cheers, Andreas libopenni-sensor-pointclouds0_5.1.0.41.3-1+b2.log.gz Description: application/gzip
Processed: libopenni-sensor-pointclouds0, libopenni-sensor-primesense0: modifying files from another package: /var/lib/ni/modules.xml
Processing control commands: found -1 5.1.0.41-3 Bug #767653 [libopenni-sensor-pointclouds0,libopenni-sensor-primesense0] libopenni-sensor-pointclouds0, libopenni-sensor-primesense0: modifying files from another package: /var/lib/ni/modules.xml There is no source info for the package 'libopenni-sensor-pointclouds0' at version '5.1.0.41-3' with architecture '' Marked as found in versions openni-sensor-primesense/5.1.0.41-3. -- 767653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org:
reassign 766799 grub-pc 2.00-22
Bug #766799 {Done: Theodore Ts'o ty...@mit.edu} [e2fsprogs] resizing root
partition with resize2fs makes system unbootable
Bug reassigned from package 'e2fsprogs' to 'grub-pc'.
No longer marked as found in versions e2fsprogs/1.42.12-1.
Ignoring request to alter fixed versions of bug #766799 to the same values
previously set
Bug #766799 {Done: Theodore Ts'o ty...@mit.edu} [grub-pc] resizing root
partition with resize2fs makes system unbootable
Marked as found in versions grub2/2.00-22.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
766799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766799
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#765156: flashproxy is marked for autoremoval from testing
On 28/10/14 11:19, Ximin Luo wrote: On 28/10/14 10:58, Holger Levsen wrote: Hi, On Dienstag, 28. Oktober 2014, Holger Levsen wrote: FWIW, https://jenkins.debian.net/userContent/rb-pkg/flashproxy.html shows that it build fine there on 2014-10-13 19:14 on amd64 too. I've scheduled another build there (should be visible in 15min roughly) to see if this is still the case... https://jenkins.debian.net/userContent/rb-pkg/flashproxy.html indeed shows the build failure now (but obviously not the test.log) cheers, Holger ACK, I will sort it out this weekend. I've so far been unable to reproduce this build failure. I've tried doing it through cowbuilder, disconnecting from the internet, setting `net.ipv6.bindv6only = 1` and `sudo sysctl -p`, and in every case the package builds fine. Can you, or anyone else, reproduce it locally? If not, I will have to request access to a build porter machine to try to reproduce it. In the meantime I will probably downgrade the severity of this bug so it doesn't get autoremoved. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git signature.asc Description: OpenPGP digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org:
reopen 766799
Bug #766799 {Done: Theodore Ts'o ty...@mit.edu} [grub-pc] resizing root
partition with resize2fs makes system unbootable
Bug reopened
Ignoring request to alter fixed versions of bug #766799 to the same values
previously set
retitle 766799 On-line resizing of root filesystem with resize2fs makes
system unbootable; grub says: unknown filesystem
Bug #766799 [grub-pc] resizing root partition with resize2fs makes system
unbootable
Changed Bug title to 'On-line resizing of root filesystem with resize2fs makes
system unbootable; grub says: unknown filesystem' from 'resizing root partition
with resize2fs makes system unbootable'
severity 766799 important
Bug #766799 [grub-pc] On-line resizing of root filesystem with resize2fs makes
system unbootable; grub says: unknown filesystem
Severity set to 'important' from 'grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
766799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766799
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#767632: ust: FTBFS on most architectures
* Ivo De Decker iv...@debian.org wrote: package: ust severity: serious version: 2.5.1-1 Hi, The latest upload of ust fails on most architectures, but built fine in the past. This prevents migration to testing. https://buildd.debian.org/status/package.php?p=ust Thanks, this is my fault and not upstream. I made a mistake in the symbols files, should have this fixed up by Monday. -- Jon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765156: flashproxy is marked for autoremoval from testing
Hi, On Samstag, 1. November 2014, Ximin Luo wrote: I've so far been unable to reproduce this build failure. I've tried doing it through cowbuilder, disconnecting from the internet, setting `net.ipv6.bindv6only = 1` and `sudo sysctl -p`, and in every case the package builds fine. you should send this to the bug. Can you, or anyone else, reproduce it locally? If not, I will have to request access to a build porter machine to try to reproduce it. it fails to build here too: https://jenkins.debian.net/userContent/rb-pkg/flashproxy.html In the meantime I will probably downgrade the severity of this bug so it doesn't get autoremoved. before I saw this failure on jenkins.d.n I was going to say sounds reasonable, now I'm not so sure anymore ;-) OTOH, fails to build sometimes could be justified as just an important bug esp as it should be fixed no matter the severity :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#767230: libotr transition started by mistake :-/
Hi,
[It's probably too late already, but if you prefer I can move this
discussion to a dedicated bug filed against release.d.o.]
Here's my analysis of the potential ABI/API breakage in libotr
4.0-4.1, and attached the debdiff (implementing plan A) that I could
upload to sid (and then request to be aged or unblocked so that it
migrates to testing eventually).
Functions added to context.h
otrl_context_find_recent_instance
-
ConnContext * otrl_context_find_recent_instance(ConnContext * context,
otrl_instag_t recent_instag);
This one is not modified at all in context.c
otrl_context_find_recent_secure_instance
ConnContext * otrl_context_find_recent_secure_instance(ConnContext * context);
This one is slightly changed in context.c. Ignoring the typo fix in
a comment, the change is:
- if (context-msgstate != OTRL_MSGSTATE_PLAINTEXT) return 1;
+ if (c_iter-msgstate != OTRL_MSGSTATE_PLAINTEXT) return 1;
I doubt this breaks the API or ABI.
Function added to both mem.c and mem.h
==
int otrl_mem_differ(const unsigned char *buf1, const unsigned char *buf2,
size_t len);
My (limited) understanding is that adding a function does not break
the API nor ABI.
readelf
===
I've diff'ed the output of the following command run on the one hand
on current Jessie (libotr 4.0.0-3) and current sid (libotr 4.1.0-1):
readelf -Ws /usr/lib/libotr.so.5 | awk '{print $8}' | sort
The result is that two symbols were added in 4.1:
gcry_mpi_snew@GCRYPT_1.6
otrl_mem_differ
The full output lines from readelf -Ws, regarding the added or modified
functions, is:
* 4.0:
117: 7a50 123 FUNCGLOBAL DEFAULT 11
otrl_context_find_recent_instance
185: 7b20 292 FUNCGLOBAL DEFAULT 11
otrl_context_find_recent_secure_instance
* 4.1:
118: 7af0 123 FUNCGLOBAL DEFAULT 11
otrl_context_find_recent_instance
181: bd50 100 FUNCGLOBAL DEFAULT 11 otrl_mem_differ
187: 7bc0 292 FUNCGLOBAL DEFAULT 11
otrl_context_find_recent_secure_instance
I lack the background to tell if the differences seen in the 1st (Num)
and 2nd (Value) columns matter. Do they indicate ABI breakage?
symbols
===
I've extracted the libotr5 binary packages from Jessie and sid, and
then run:
dpkg-gensymbols -v4.0.0 -plibotr5 -P/tmp/intrigeri/4.0-extracted -Osymbols
dpkg-gensymbols -v4.1.0 -plibotr5 -P/tmp/intrigeri/4.1-extracted -Osymbols
The second command tells me:
--- symbols (libotr5_4.1.0_amd64)
+++ dpkg-gensymbolsjwu_Lf 2014-11-01 17:42:21.409469548 +0100
@@ -51,6 +51,7 @@
otrl_instag_read_FILEp@Base 4.0.0
otrl_instag_write@Base 4.0.0
otrl_instag_write_FILEp@Base 4.0.0
+ otrl_mem_differ@Base 4.1.0
otrl_mem_init@Base 4.0.0
otrl_message_abort_smp@Base 4.0.0
otrl_message_disconnect@Base 4.0.0
... which seems to confirm the fact that there was no
API/ABI breakage.
Applications built against libotr 4.0 and running with 4.1
==
* pidgin-otr 4.0.1-1 rebuilt in a Jessie chroot: works fine on
current sid
= seems to confirm that applications built against the old version
still work fine with the new one.
The attached patch
==
I've gone with the smallest possible change (removing one single
line), and left the warning be printed on stderr, in the hope it may
help debugging issues in case something is wrong with this analysis.
If the RT prefers, I can drop the warning too.
I've successfully tested the resulting libotr5 binary package with:
* pidgin-otr 4.0.1-1 built in a Jessie chroot (against libotr 4.0)
* pidgin-otr 4.0.1-1 from sid (that was built against libotr 4.1)
... but I could not directly test the actual intended effect of the
patch (it would require building an _older_ version of libotr with
this patch, building a package against the new version, and running it
with the patched old version). This leads me to think that perhaps
this patch may not be as useful as I used to think.
Conclusion
==
Unless the differences I've found in readelf output indicate ABI
breakage, it seems equally safe to either:
* upload with the attached debdiff to sid, wait for it to build on
all architectures, and then let it migrate to testing;
* just let libotr migrate to testing as is (my current understanding
is that it should fix two RC bugs, without introducing any new
breakage).
So, whatever the release team feels more comfortable with :)
[Regarding the plans for Jessie+1, I've filed #767652 so we (pkg-otr
team) don't forget about it.]
Cheers,
--
intrigeri
diff -Nru libotr-4.1.0/debian/changelog libotr-4.1.0/debian/changelog
--- libotr-4.1.0/debian/changelog 2014-10-21 22:26:51.0 +0200
+++
Bug#767230: libotr transition started by mistake :-/
On Sat, Nov 1, 2014 at 16:50:54 +0100, intrigeri wrote: But anyway, for Jessie+1 I'll add shlibs support, so indeed this check will be redundant; and then, my understanding is that it'll also become fully harmless. It'd be better if this didn't wait until jessie+1. Please let me know off-list if you'd like help on this. (and no, it won't be harmless) Cheers, Julien signature.asc Description: Digital signature
Processed: pending
Processing commands for cont...@bugs.debian.org: tags 767568 + pending Bug #767568 [bibledit-bibletime] bibledit-bibletime: fails to upgrade from squeeze - trying to overwrite /usr/share/man/man1/bibledit-bibletime.1.gz Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 767568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767568 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#767411: torque: should not be released with jessie
On Sat, Nov 1, 2014 at 16:46:12 +0100, Salvatore Bonaccorso wrote: Hi Julien, On Fri, Oct 31, 2014 at 02:07:25PM +0100, Julien Cristau wrote: On Thu, Oct 30, 2014 at 22:27:53 +0100, Salvatore Bonaccorso wrote: pbs-drmaa as reverse dependency of torque is easy as it is a leaf package. The more complicated one would be openmpi which would need to drop the build dependency on libtorque2-dev. The reason for this dependency was in https://bugs.debian.org/592887 , which needs to be dropped again. There's two solutions here. One is to drop torque support from openmpi; the other is to keep the torque source package but only build the libtorque library, as I'm assuming the security issues are on the torque server side. Though that's only useful is that library can still talk to newer torque version. Given Dominique's reply on #767411, from my POV I think the best solution would be to remove torque completely for jessie (i.e. first drop support from openmpi to be able to remove the package and remaining reverse dependencies). I don't know how much of that reply applies to the library... Cheers, Julien signature.asc Description: Digital signature
Bug#738263: doxygen: full build profiles patch
clone 738263 -1 severity 738263 wishlist retitle -1 FTBFS: uses old build profile syntax no longer supported by dpkg unblock -1 by 744246 owner -1 ! owner 762272 ! thanks On Sat, Oct 25, 2014 at 03:58:05AM +0200, Guillem Jover wrote: With the agreed change in dpkg-source 1.17.21 to error out on obsolete Build-Profiles field syntax, this package will now FTBFS, so rising the severity. Or would you prefer a new bug report instead? I prefer a new bug, because the two issues conflated cannot be fixed together: #738263 is now about updating Build-Depends (cannot be uploaded now) #-1 is now about updating Build-Profiles (cannot be deferred) I will come up with a solution for #762272 before December and upload a doxygen fixing #762272 and #-1 by then. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 4 errors): Re: Bug#738263: doxygen: full build profiles patch
Processing commands for cont...@bugs.debian.org: clone 738263 -1 Bug #738263 [src:doxygen] doxygen: Patch to bootstrap without Qt Bug 738263 cloned as bug 767658 744246 was blocked by: 760158 744243 744246 was blocking: 709623 737946 738263 749470 749855 749990 751922 752103 752235 752271 752409 757147 758420 758462 758467 Added blocking bug(s) of 744246: 767658; removed blocking bug(s) of 744246: 760158 and 744243 Failed to clone 738263: can't find location for 744243. severity 738263 wishlist Bug #738263 [src:doxygen] doxygen: Patch to bootstrap without Qt Severity set to 'wishlist' from 'serious' retitle -1 FTBFS: uses old build profile syntax no longer supported by dpkg Failed to set the title of -1: The 'bug' parameter (-1) to Debbugs::Control::set_title did not pass regex check unblock -1 by 744246 Failed to set blocking bugs of -1: The 'bug' parameter (-1) to Debbugs::Control::set_blocks did not pass regex check owner -1 ! Failed to mark -1 as having an owner: The 'bug' parameter (-1) to Debbugs::Control::owner did not pass regex check owner 762272 ! Bug #762272 [src:doxygen] doxygen: segfaults when building efl (on ix86 amd amd64) Owner recorded as Helmut Grohne hel...@subdivi.de. thanks Stopping processing here. Please contact me if you need assistance. -- 738263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738263 762272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762272 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#765156: flashproxy is marked for autoremoval from testing
On 01/11/14 18:00, Holger Levsen wrote: Hi, On Samstag, 1. November 2014, Ximin Luo wrote: I've so far been unable to reproduce this build failure. I've tried doing it through cowbuilder, disconnecting from the internet, setting `net.ipv6.bindv6only = 1` and `sudo sysctl -p`, and in every case the package builds fine. you should send this to the bug. It is sent to the bug. Can you, or anyone else, reproduce it locally? If not, I will have to request access to a build porter machine to try to reproduce it. it fails to build here too: https://jenkins.debian.net/userContent/rb-pkg/flashproxy.html Yes, but it gives me no actionable information. Great, my build is failing, I can't even see the test output or the build environment. :/ In the meantime I will probably downgrade the severity of this bug so it doesn't get autoremoved. before I saw this failure on jenkins.d.n I was going to say sounds reasonable, now I'm not so sure anymore ;-) OTOH, fails to build sometimes could be justified as just an important bug esp as it should be fixed no matter the severity :) It's a slap in the face for my package to be auto-removed, without me even having a chance to fix things. I can't reproduce the bug locally and the build machines don't even output test-suite.log, which is a standard autotools test output file. Can you try building it locally? X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git signature.asc Description: OpenPGP digital signature
Bug#767411: torque: should not be released with jessie
On Sat, Nov 1, 2014 at 11:46 AM, Salvatore Bonaccorso wrote: Given Dominique's reply on #767411, from my POV I think the best solution would be to remove torque completely for jessie (i.e. first drop support from openmpi to be able to remove the package and remaining reverse dependencies). 4 wheezy DSAs doesn't necessarily sound that horrible, so I don't think we're clearly at the point where torque should be considered unsupportable. Maybe the patch backports were an incredible amount of work? The package does clearly need to be orphaned, so someone can step up post-jessie to get the package in sync with upstream. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765156: flashproxy is marked for autoremoval from testing
Hi, On Samstag, 1. November 2014, Ximin Luo wrote: you should send this to the bug. It is sent to the bug. right, here we're talking... Yes, but it gives me no actionable information. Great, my build is failing, I can't even see the test output or the build environment. :/ well, you are the maintainer you can make it output the test.log if there are failures... It's a slap in the face for my package to be auto-removed, without me even having a chance to fix things. I can't reproduce the bug locally and the build machines don't even output test-suite.log, which is a standard autotools test output file. Can you try building it locally? I did, but no log :( here's how I build: 504 apt-get source flashproxy 506 time ionice -c 3 nice sudo DEB_BUILD_OPTIONS=-j15 -b pbuilder --build flashproxy_1.7-1.dsc f.log 21 and then I build it manually... and it failed and I saw this: See ./test-suite.log which is wrong. it's not there. it's in ./facilitator/test-suite.log and attached. :) I'd be happy to rebuild again if you can give me something to try :) cheers, Holger == flashproxy-facilitator 1.7: ./test-suite.log == # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: fp-facilitator-test = ...E.E... == ERROR: test_af_v4_v6 (__main__.FacilitatorProcTest) Test that IPv4 proxies do not get IPv6 clients. -- Traceback (most recent call last): File ./fp-facilitator-test.py, line 257, in test_af_v4_v6 fac.put_reg(FACILITATOR_ADDR, self.IPV6_CLIENT_ADDR, CLIENT_TP) File /srv/reproducible-results/f/flashproxy-1.7/flashproxy/fac.py, line 147, in put_reg f = fac_socket(facilitator_addr) File /srv/reproducible-results/f/flashproxy-1.7/flashproxy/fac.py, line 132, in fac_socket return socket.create_connection(facilitator_addr, 1.0).makefile() File /usr/lib/python2.7/socket.py, line 571, in create_connection raise err error: [Errno 111] Connection refused == ERROR: test_af_v6_v6 (__main__.FacilitatorProcTest) Test that IPv6 proxies can get IPv6 clients. -- Traceback (most recent call last): File ./fp-facilitator-test.py, line 269, in test_af_v6_v6 fac.put_reg(FACILITATOR_ADDR, self.IPV4_CLIENT_ADDR, CLIENT_TP) File /srv/reproducible-results/f/flashproxy-1.7/flashproxy/fac.py, line 147, in put_reg f = fac_socket(facilitator_addr) File /srv/reproducible-results/f/flashproxy-1.7/flashproxy/fac.py, line 132, in fac_socket return socket.create_connection(facilitator_addr, 1.0).makefile() File /usr/lib/python2.7/socket.py, line 571, in create_connection raise err error: [Errno 111] Connection refused -- Ran 17 tests in 2.204s FAILED (errors=2) signature.asc Description: This is a digitally signed message part.
Bug#767445: python-docker: throws ValueError exception on attempting any command
On 01.11.2014 12:26, Jakub Warmuz wrote: IMO a package patch should be provided to import global urllib3 instead, following Debian packaging standards As discussed on #debian-python I'm attaching a patch. Let me know if I can help further. -- Yours virtually, Kuba Index: debian/changelog === --- debian/changelog (revision 31346) +++ debian/changelog (working copy) @@ -1,3 +1,13 @@ +python-docker (0.5.3-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Added debian/patches/02_use-system-urllib3.patch (Closes: #767445). + * Renamed debian/patches/requirements.patch to +debian/patches/01_requirements.patch following convention from other +Python packages. + + -- Jakub Warmuz ja...@warmuz.org Sat, 01 Nov 2014 18:19:57 +0100 + python-docker (0.5.3-1) unstable; urgency=medium * Update to 0.5.3 upstream release Index: debian/patches/01_requirements.patch === --- debian/patches/01_requirements.patch (revision 0) +++ debian/patches/01_requirements.patch (working copy) @@ -0,0 +1,22 @@ +Author: Tianon Gravi admwig...@gmail.com +Forwarded: https://github.com/dotcloud/docker-py/issues/101 (upstream has no interest) +Description: unpin dependencies so newer versions satisfy them appropriately + +diff --git a/requirements.txt b/requirements.txt +index a1cc1af..d4920a7 100644 +--- a/requirements.txt b/requirements.txt +@@ -1,3 +1,3 @@ +-requests==2.2.1 ++requests=2.2.1 + six=1.3.0 +-websocket-client==0.11.0 ++websocket-client=0.11.0 +diff --git a/requirements3.txt b/requirements3.txt +index 68533d1..ab74f44 100644 +--- a/requirements3.txt b/requirements3.txt +@@ -1,2 +1,2 @@ +-requests==2.2.1 ++requests=2.2.1 + six=1.3.0 Index: debian/patches/02_use-system-urllib3.patch === --- debian/patches/02_use-system-urllib3.patch (revision 0) +++ debian/patches/02_use-system-urllib3.patch (working copy) @@ -0,0 +1,33 @@ +Description: Use the system python-urllib3 instead of the + requests.packages.urllib3. +Author: Jakub Warmuz ja...@warmuz.org +Last-Update: 2014-11-01 + +--- a/docker/ssladapter/ssladapter.py b/docker/ssladapter/ssladapter.py +@@ -4,10 +4,7 @@ + + from distutils.version import StrictVersion + from requests.adapters import HTTPAdapter +-try: +-import requests.packages.urllib3 as urllib3 +-except ImportError: +-import urllib3 ++import urllib3 + + + PoolManager = urllib3.poolmanager.PoolManager +--- a/docker/unixconn/unixconn.py b/docker/unixconn/unixconn.py +@@ -20,10 +20,7 @@ + import requests.adapters + import socket + +-try: +-import requests.packages.urllib3.connectionpool as connectionpool +-except ImportError: +-import urllib3.connectionpool as connectionpool ++import urllib3.connectionpool as connectionpool + + + class UnixHTTPConnection(httplib.HTTPConnection, object): Index: debian/patches/requirements.patch === --- debian/patches/requirements.patch (revision 31346) +++ debian/patches/requirements.patch (working copy) @@ -1,22 +0,0 @@ -Author: Tianon Gravi admwig...@gmail.com -Forwarded: https://github.com/dotcloud/docker-py/issues/101 (upstream has no interest) -Description: unpin dependencies so newer versions satisfy them appropriately - -diff --git a/requirements.txt b/requirements.txt -index a1cc1af..d4920a7 100644 a/requirements.txt -+++ b/requirements.txt -@@ -1,3 +1,3 @@ --requests==2.2.1 -+requests=2.2.1 - six=1.3.0 --websocket-client==0.11.0 -+websocket-client=0.11.0 -diff --git a/requirements3.txt b/requirements3.txt -index 68533d1..ab74f44 100644 a/requirements3.txt -+++ b/requirements3.txt -@@ -1,2 +1,2 @@ --requests==2.2.1 -+requests=2.2.1 - six=1.3.0 Index: debian/patches/series === --- debian/patches/series (revision 31346) +++ debian/patches/series (working copy) @@ -1,2 +1,4 @@ # see https://github.com/dotcloud/docker-py/issues/101 -requirements.patch +01_requirements.patch +# see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767445 +02_use-system-urllib3.patch signature.asc Description: OpenPGP digital signature
Bug#764667: marked as done (distcc: Trigger cycle causes dpkg to fail processing)
Your message dated Sat, 01 Nov 2014 18:48:51 + with message-id e1xkdjh-0008mt...@franck.debian.org and subject line Bug#764667: fixed in distcc 3.1-6.1 has caused the Debian Bug report #764667, regarding distcc: Trigger cycle causes dpkg to fail processing 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.) -- 764667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: distcc Version: 3.1-6 Severity: serious Hi! This package introduces a trigger cycle, that while it might currently not be visible in most cases it will suddenly make dpkg abort (as per the spec) once #671711 is fixed in dpkg 1.17.17 to be uploaded later today. The problem is that distcc installs interests on /usr/lib/gcc which is provided by (say) gcc-4.9. Then distcc depends on libc6, depends on libgcc1, depends on libc6 and gcc-4.9-base. And gcc-4.9 depends on gcc-4.9-base and libc6 among others. When several of those are unpacked on the same run, and the trigger gets activated dpkg cannot proceed due to the trigger cycle and needs to bail out, which is not a very nice upgrade path. The solution to the above is to simply switch the triggers to their noawait variants. In this case from «interest» to «interest-noawait». Thanks, Guillem ---End Message--- ---BeginMessage--- Source: distcc Source-Version: 3.1-6.1 We believe that the bug you reported is fixed in the latest version of distcc, 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. gregor herrmann gre...@debian.org (supplier of updated distcc 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, 27 Oct 2014 19:18:30 +0100 Source: distcc Binary: distcc distccmon-gnome distcc-pump Architecture: source amd64 Version: 3.1-6.1 Distribution: unstable Urgency: medium Maintainer: Daniel Hartwig mand...@gmail.com Changed-By: gregor herrmann gre...@debian.org Description: distcc - simple distributed compiler client and server distcc-pump - pump mode for distcc a distributed compiler client and server distccmon-gnome - GTK+ monitor for distcc a distributed client and server Closes: 764667 Changes: distcc (3.1-6.1) unstable; urgency=medium . * Non-maintainer upload. * Fix Trigger cycle causes dpkg to fail processing: change triggers from interest to interest-noawait, as proposed by Guillem Jover. (Closes: #764667) Checksums-Sha1: 4db4254a4f8934cd8d2a965e66a83dddbedff7df 2052 distcc_3.1-6.1.dsc cbadff141c1b66ec56967f2c01d33690eab57dfc 55704 distcc_3.1-6.1.debian.tar.xz fc8b55306b2b4f3a6ea7f0750e634e9baddfd4f6 191478 distcc_3.1-6.1_amd64.deb d77ebfccf62ba530050d9e6c69d12943bf8476c1 42188 distccmon-gnome_3.1-6.1_amd64.deb cb00141f00f5316f2fa0e1ad9f8130298afe588d 122900 distcc-pump_3.1-6.1_amd64.deb Checksums-Sha256: 730e508f9fa76fd6850eb989a4fcb5babdec208bd70647ef238251a3d2a18055 2052 distcc_3.1-6.1.dsc b64b967ce64e934c5f386b333a21514c50f5f8c7b24a96b5083305dd6e7a2f2c 55704 distcc_3.1-6.1.debian.tar.xz 1893e7143762b1026694b72ea974563e58f5d27be643f255f488bbb034034388 191478 distcc_3.1-6.1_amd64.deb d042be28c1a1dd4bbd0da36ecf868a17a8e30fe91fb93237b70f218efebf3be1 42188 distccmon-gnome_3.1-6.1_amd64.deb 227c440cefe261dedc13c6c9d3651752719fed6adee9287438d33236effb948f 122900 distcc-pump_3.1-6.1_amd64.deb Files: cecbece77c276f7ed4cd96c2baec2e59 2052 devel optional distcc_3.1-6.1.dsc d3b37dc598d412d8cd2f2a4cbbd768c5 55704 devel optional distcc_3.1-6.1.debian.tar.xz b8983a3a7a66c5fabd68b2ab477d42ef 191478 devel optional distcc_3.1-6.1_amd64.deb 1aa828fa66510efbd1a829f53ac458ee 42188 devel optional distccmon-gnome_3.1-6.1_amd64.deb 8e21dd59c5a23626e52d9b96f09ad46f 122900 devel optional distcc-pump_3.1-6.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJUTo2FXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGcPwP/0mYGlra1UjodF54FfIfOsWr HBxmQ9qDCW1GH85u2slFpj0dfAUbb96VQ+kZurlxAlYasDsH+RNlOO4pB1UrzXVO
Bug#767248: dbconfig-common: removes any permissions from generated include files on upgrade
On 01-11-14 16:37, Paul Gevers wrote: Furthermore, I have been reading up on the use of cp. It seems, but if you are using ACL's I like you to test, that cp opens the file for writing, so it should keep existing ACL's AFAICT. My latest patch works correctly with acl: (pbuild29710)root@wollumbin:/# setfacl -m u:paul:5 /etc/roundcube/debian-db.php (pbuild29710)root@wollumbin:/# getfacl /etc/roundcube/debian-db.php getfacl: Removing leading '/' from absolute path names # file: etc/roundcube/debian-db.php # owner: root # group: www-data user::rw- user:paul:r-x group::r-- mask::r-x other::--- (pbuild29710)root@wollumbin:/# dpkg-reconfigure roundcube-core dbconfig-common: writing config to /etc/dbconfig-common/roundcube.conf + [ /etc/roundcube/debian-db.php ] + ls -al /tmp/dbconfig-generate-include.l6EBqg -rw-r-x---+ 1 root www-data 546 Nov 1 18:46 /tmp/dbconfig-generate-include.l6EBqg + ls -al /etc/roundcube/debian-db.php -rw-r-x---+ 1 root www-data 546 Nov 1 16:23 /etc/roundcube/debian-db.php + [ 1 ] + ucf --debconf-ok /tmp/dbconfig-generate-include.l6EBqg /etc/roundcube/debian-db.php Replacing config file /etc/roundcube/debian-db.php with new version + rm -f /tmp/dbconfig-generate-include.l6EBqg + ls -al /etc/roundcube/debian-db.php -rw-r-x---+ 1 root www-data 546 Nov 1 18:46 /etc/roundcube/debian-db.php + check_permissions + local line + dpkg-statoverride --list /etc/roundcube/debian-db.php + [ ] + [ ] + ls -al /etc/roundcube/debian-db.php -rw-r-x---+ 1 root www-data 546 Nov 1 18:46 /etc/roundcube/debian-db.php + set +x apache2_invoke roundcube.conf: already enabled invoke-rc.d: policy-rc.d denied execution of reload. invoke-rc.d: policy-rc.d denied execution of reload. (pbuild29710)root@wollumbin:/# getfacl /etc/roundcube/debian-db.php getfacl: Removing leading '/' from absolute path names # file: etc/roundcube/debian-db.php # owner: root # group: www-data user::rw- user:paul:r-x group::r-- mask::r-x other::--- (pbuild29710)root@wollumbin:/# Paul signature.asc Description: OpenPGP digital signature
Bug#765469: python3-tornado: get_secure_cookie get incorrect value by setting set_secure_cookie
I am not able to reproduce your problem. The code that you provided does
not even run due to the syntax error in post() method: username =
self.get_body_argument('username'):. Could you please:
- try to minimize the script as far as possible;
- remove try/except block surrounding: remember =
json.loads(remember_cookie.decode());
- attach it in full to the bug report;
- and finally attach a full Python traceback for the ValueError you are
experiencing?
Which unrelated software does this bug break? If none, then this is
probably not a critical bug.
--
Yours virtually,
Jakub Warmuz
signature.asc
Description: OpenPGP digital signature
Bug#767671: ekeyd: fails to remove: subprocess installed post-removal script returned error exit status 1
Package: ekeyd Version: 1.1.5-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to remove. From the attached log (scroll to the bottom...): Removing ekeyd (1.1.5-6) ... dpkg: error processing package ekeyd (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: ekeyd cheers, Andreas ekeyd_1.1.5-6.log.gz Description: application/gzip
Bug#767411: torque: should not be released with jessie
On Sat, Nov 01, 2014 at 02:30:02PM -0400, Michael Gilbert wrote: On Sat, Nov 1, 2014 at 11:46 AM, Salvatore Bonaccorso wrote: Given Dominique's reply on #767411, from my POV I think the best solution would be to remove torque completely for jessie (i.e. first drop support from openmpi to be able to remove the package and remaining reverse dependencies). 4 wheezy DSAs doesn't necessarily sound that horrible, so I don't think we're clearly at the point where torque should be considered unsupportable. Maybe the patch backports were an incredible amount of work? Well, but the 2.4 branch is already no longer unsupported upstream and we shouldn't knowingly introduce it into a release which will be supported for five more years. The package does clearly need to be orphaned, so someone can step up post-jessie to get the package in sync with upstream. As written by Dominique that's no possible for license reasons. 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#757825: haskell-hsmagick: diff for NMU version 0.5-4.1
Control: tags 757825 + patch Control: tags 757825 + pending Dear maintainer, I've prepared an NMU for haskell-hsmagick (versioned as 0.5-4.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru haskell-hsmagick-0.5/debian/changelog haskell-hsmagick-0.5/debian/changelog --- haskell-hsmagick-0.5/debian/changelog 2014-05-01 12:37:04.0 +0200 +++ haskell-hsmagick-0.5/debian/changelog 2014-11-01 20:46:58.0 +0100 @@ -1,3 +1,10 @@ +haskell-hsmagick (0.5-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Change depdendency of the module to lcms2. (Closes: #757825) + + -- Tobias Frost t...@debian.org Sat, 01 Nov 2014 19:46:58 + + haskell-hsmagick (0.5-4) unstable; urgency=high * Add liblcms-dev to Build-Depends (Closes: #746083) diff -Nru haskell-hsmagick-0.5/debian/control haskell-hsmagick-0.5/debian/control --- haskell-hsmagick-0.5/debian/control 2014-05-01 12:40:24.0 +0200 +++ haskell-hsmagick-0.5/debian/control 2014-11-01 20:35:21.0 +0100 @@ -16,7 +16,7 @@ , libpng-dev , libbz2-dev , libz-dev -, liblcms-dev +, liblcms2-dev Build-Depends-Indep: ghc-doc Standards-Version: 3.9.4 Vcs-Browser: http://darcs.debian.org/cgi-bin/darcsweb.cgi?r=pkg-haskell/haskell-hsmagick diff -Nru haskell-hsmagick-0.5/debian/patches/10-lcms2-dev.patch haskell-hsmagick-0.5/debian/patches/10-lcms2-dev.patch --- haskell-hsmagick-0.5/debian/patches/10-lcms2-dev.patch 1970-01-01 01:00:00.0 +0100 +++ haskell-hsmagick-0.5/debian/patches/10-lcms2-dev.patch 2014-11-01 20:45:59.0 +0100 @@ -0,0 +1,15 @@ +Description: Change dependency from lcms to lcms2 +Author: Tobias Frost t...@debian.org +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/hsmagick.cabal b/hsmagick.cabal +@@ -23,7 +23,7 @@ + ghc-options: -Wall + extra-libraries: tiff jasper jpeg png wmflite bz2 z m + pkgconfig-depends: GraphicsMagick = 1.3.3 +- , lcms ++ , lcms2 +, freetype2 +, libxml-2.0 + diff -Nru haskell-hsmagick-0.5/debian/patches/series haskell-hsmagick-0.5/debian/patches/series --- haskell-hsmagick-0.5/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ haskell-hsmagick-0.5/debian/patches/series 2014-11-01 20:24:50.0 +0100 @@ -0,0 +1 @@ +10-lcms2-dev.patch -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
