Processed: retitle 770972 to libksba: CVE-2014-9087: buffer overflow in ksba_oid_to_str
Processing commands for cont...@bugs.debian.org:
retitle 770972 libksba: CVE-2014-9087: buffer overflow in ksba_oid_to_str
Bug #770972 {Done: Andreas Metzler ametz...@debian.org} [src:libksba]
libksba: buffer overflow in ksba_oid_to_str
Changed Bug title to 'libksba: CVE-2014-9087: buffer overflow in
ksba_oid_to_str' from 'libksba: buffer overflow in ksba_oid_to_str'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
770972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770972
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#768369: Stack smashing in libjpeg-turbo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768369#114 I created a minimal test case in around 200 lines. It uses a file with the intercepted scanlines of the calls to jpeg_write_scanlines. Also the Exif marker is read from such a file. (And without this Exif marker the stack smash does not happen...) Use CVE-2014-9092. - -- CVE assignment team, MITRE CVE Numbering Authority M/S M300 202 Burlington Road, Bedford, MA 01730 USA [ PGP key available through http://cve.mitre.org/cve/request_id.html ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (SunOS) iQEcBAEBAgAGBQJUdYGqAAoJEKllVAevmvmsA7QH/ijNNlUkWF2Vst56xw9AZNUN dYdTRNXISkzOotHcglCpOomIzjbTWy4ablsLxryr0kUc4ZjIc5RlZuCTKAaVJ+EC RgphhkmFHkKNqPSVMLtIOpP4ZX/0uPSKAMlzoXsRzRgmEBG6pnYnokJTa47sit26 iSpvAqXUNwJ/ZA14eUFMDdP6FbpOB4wmHS9h5nnUO7lzhmM/93XasD6WluBB0EBo F9xZ/a0pCfEV+9RwKMiGsr2w+nPYDzUWlnrNbVnw8ou9msI/tolGadUbbwCM1NY9 FiemAFw4ZRExQIjDKaubApDlNuYzckmDNvBWJkwdVIJvBvQqNPVmUMP4MefDGhw= =F4GF -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: retitle 768369 to libjpeg-turbo: CVE-2014-9092: [DOS] Stack smashing
Processing commands for cont...@bugs.debian.org: retitle 768369 libjpeg-turbo: CVE-2014-9092: [DOS] Stack smashing Bug #768369 [libjpeg62-turbo] [libjpeg62-turbo] [DOS] Stack smashing Changed Bug title to 'libjpeg-turbo: CVE-2014-9092: [DOS] Stack smashing' from '[libjpeg62-turbo] [DOS] Stack smashing' thanks Stopping processing here. Please contact me if you need assistance. -- 768369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768369 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#768695: Bug #768695: statsmodels: FTBFS in jessie: ImportError: cannot import name DateRange
Good idea, feel free to change the patch. I won't be able to do it before the evening. Tomasz On 25/11/14 20:51, Yaroslav Halchenko wrote: On Wed, 26 Nov 2014, Tomasz Buchert wrote: + import pandas as _ +-return True ++return hasattr(_, DateRange) imho this is way too aggressive and would cause skipping all pandas related tests (DateRange dependent or not) + except ImportError: + return False + +Index: statsmodels-0.4.2/statsmodels/tsa/base/tests/test_datetools.py +=== +--- statsmodels-0.4.2.orig/statsmodels/tsa/base/tests/test_datetools.py statsmodels-0.4.2/statsmodels/tsa/base/tests/test_datetools.py +@@ -3,6 +3,7 @@ import numpy.testing as npt + from statsmodels.tsa.base.datetools import (_date_from_idx, + _idx_from_dates, date_parser, date_range_str, dates_from_str, + dates_from_range, _infer_freq, _freq_to_pandas) ++import nose + + def test_date_from_idx(): + d1 = datetime(2008, 12, 31) +@@ -15,6 +16,7 @@ def test_date_from_idx(): + npt.assert_equal(_date_from_idx(d1, idx, 'M'), datetime(2010, 3, 31)) + + def test_idx_from_date(): ++raise nose.SkipTest(Skipped because of missing DateRange) if you are introducing these changes, why not to make def skip_if_no_daterange(): try: import pandas as _ if not hasaattr(_, DateRange): raise nose.SkipTest(Skipped because...) except ImportError: raise nose.SkipTest(Skipped because no pandas...) and just call that one? -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770130: gnome-shell: Oh no! Something has gone wrong. (Fujitsu ST4121)
On Wed, 19 Nov 2014 at 18:33:47 -0800, Eric Shattow wrote: + syslog(LOG_ERR, COGL ERROR: allocate_with_size + ctx %lx, WxH %i x %i, ifmt %i\n, + (long unsigned int)ctx, width, height, internal_format); I notice this is consistently failing for non-power-of-two texture sizes, but only for gnome-shell[3624], not for gnome-shell[985]. 3624 appears to be running as uid 'user'- the actual login session - whereas 985 is presumably Debian-gdm running the login prompt, which is also done using gnome-shell. I'm not sure what would be different for the Debian-gdm instance in terms of driver support for NPOT textures, but perhaps this points someone else in the right direction? S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#767367: gnome-shell: Gnome shell refusing to start on intel graphics 3rd gen
Processing control commands: reassign 767367 src:nvidia-graphics-drivers Bug #767367 [gnome-shell] gnome-shell: Gnome shell refusing to start on intel graphics 3rd gen Bug reassigned from package 'gnome-shell' to 'src:nvidia-graphics-drivers'. No longer marked as found in versions gnome-shell/3.14.1-1. Ignoring request to alter fixed versions of bug #767367 to the same values previously set forcemerge 769072 767367 Bug #769072 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #769191 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #769481 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #770588 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #767367 [src:nvidia-graphics-drivers] gnome-shell: Gnome shell refusing to start on intel graphics 3rd gen Severity set to 'critical' from 'important' Summary recorded from message bug 767367 message Added indication that 767367 affects xorg,glx-diversions,xserver-xorg,gdm3 Bug #769191 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #769481 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #770588 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Merged 767367 769072 769191 769481 770588 affects 769072 gnome-shell Bug #769072 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #767367 [src:nvidia-graphics-drivers] gnome-shell: Gnome shell refusing to start on intel graphics 3rd gen Bug #769191 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #769481 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Bug #770588 [src:nvidia-graphics-drivers] Broken graphics due to libgl1-nvidia-glx auto-install on non-nvidia hardware Added indication that 769072 affects gnome-shell Added indication that 767367 affects gnome-shell Added indication that 769191 affects gnome-shell Added indication that 769481 affects gnome-shell Added indication that 770588 affects gnome-shell -- 767367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767367 769072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769072 769191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769191 769481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769481 770588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770588 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#770941: Wontfix #770941
severity 770941 wishlist retitle 770941 Please support ident ident auth in DSN tag 770941 +wontfix -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770941: [PKG-Openstack-devel] Bug#770941: closed by Thomas Goirand z...@debian.org (Re: Bug#770941: closed by Thomas Goirand z...@debian.org (Re: Bug#770941: nova-common - Overrides database c
On 11/26/2014 03:18 PM, Bastian Blank wrote: Well, I don't think so. You can yourself refer to the ctte or I will. Patches would be a way more efficient than wasting the ctte time. I will *not* have the time to work on this before the release of Jessie, so I welcome you to do so. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tag 770941 +help
Processing commands for cont...@bugs.debian.org: tag 770941 +help Bug #770941 [nova-common] nova-common - Overrides database config in nova.conf Added tag(s) help. End of message, stopping processing here. Please contact me if you need assistance. -- 770941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770941 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#768160: marked as done (ruby-twitter: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/twitter/version.rb)
Your message dated Wed, 26 Nov 2014 09:20:48 + with message-id e1xtymg-00081l...@franck.debian.org and subject line Bug#768160: fixed in ruby-twitter 5.11.0-2 has caused the Debian Bug report #768160, regarding ruby-twitter: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/twitter/version.rb 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.) -- 768160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ruby-twitter Version: 5.11.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' 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 ruby-twitter. Unpacking ruby-twitter (from .../ruby-twitter_5.11.0-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/ruby-twitter_5.11.0-1_all.deb (--unpack): trying to overwrite '/usr/lib/ruby/vendor_ruby/twitter/version.rb', which is also in package ruby-twitter4r 0.7.0-3 Errors were encountered while processing: /var/cache/apt/archives/ruby-twitter_5.11.0-1_all.deb cheers, Andreas ruby-twitter4r=0.7.0-3_ruby-twitter=5.11.0-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: ruby-twitter Source-Version: 5.11.0-2 We believe that the bug you reported is fixed in the latest version of ruby-twitter, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen prav...@debian.org (supplier of updated ruby-twitter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Nov 2014 14:01:21 +0530 Source: ruby-twitter Binary: ruby-twitter Architecture: source all Version: 5.11.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Pirate Praveen prav...@debian.org Description: ruby-twitter - Ruby interface to the Twitter API Closes: 768160 Changes: ruby-twitter (5.11.0-2) unstable; urgency=medium . * Team upload. * Add ruby-buftok to depends. * Conflict and Replace ruby-twitter4r (closes: #768160). * Bump standards version to 3.9.6 (no changes). Checksums-Sha1: 0d9a1f59c1f764b477127d405cac7bca0b162731 2306 ruby-twitter_5.11.0-2.dsc b66c910064cea608f13bb98d31f585592ba36695 2756 ruby-twitter_5.11.0-2.debian.tar.xz 9a2c12c8b75064722e96038964ada93a5c74eb65 68250 ruby-twitter_5.11.0-2_all.deb Checksums-Sha256: 92ff7145397f0622527b552091706ca8333648450fc8fb0d219f0574f0aa5ad8 2306 ruby-twitter_5.11.0-2.dsc ffe64986077d5488e1d61902bbf46db66f074fafadc786f78644c5de46db5df5 2756 ruby-twitter_5.11.0-2.debian.tar.xz 875d086f6bed4bb05ffce446d8e03b63df37423895439e2c7cfa652047d3643f 68250 ruby-twitter_5.11.0-2_all.deb Files: dd1fdeeef5b6ee9602d6d577e3466f23 2306 ruby optional ruby-twitter_5.11.0-2.dsc 50d293d76b0a4c1f62d7f4a3f37cef29 2756 ruby optional ruby-twitter_5.11.0-2.debian.tar.xz 9897c86bf42b3d919a82e736d2926530 68250 ruby optional ruby-twitter_5.11.0-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUdZCpAAoJEM4fnGdFEsIq4usQAKIKLQjcTB/pE3M0Bty/CLd7 5T14j/kGR/EeP2RAQrnq43pa5+zmsi55ppRW+1eLkpVIzYyLzwtS1spAGzAeVdLZ zBrcVL4QavjNcGEsCT4VOfHsU93zV333I7Gp35FHFbSO7R1mxhu/nKz7+1GGXfxc iwUWFcbHkqXS95/0DqfXmca8Qi1T6p/pvY/hBwVs1BDbuzu9kx/NFp76SOEBCqZF EwEhv6S5XjUp4yftv/HMnvZgCPsC4apKMoNyW2ofEMlLS6HdCuFOllZhf4dNHhP+ DwisttjLpvtrsZ/NEhwTXG60uLEVGHMH51XwpHJuQgh3RABxug+xsI36O4z5ZKUs 1CudS0wdNu8muU/eHHo9aS5VzlPmplC6PgU8SV0FAFg1xyIw27tK6bWpMvgXJeI+ SgsQkJPu2Dg3U8U5lR1G3zQfOkdbMhFVsXfRE8EHYNu7Tkh2nAdYHBQO95H+SWwZ EpobICaysUvkP4wBcgvC9JCu193SFwbEawbBllvzgUOJUl/uEy6XU3Iw4C5RZHDT WaupG9yFttRzqLd61faXQuzKb9iXpT0+R5im1SEZ2f5C8cxZ4ii7GY+RXHCcp4yF
Processed: reported upstream
Processing commands for cont...@bugs.debian.org: forwarded 768673 https://github.com/nahi/httpclient/issues/233 Bug #768673 [src:ruby-httpclient] ruby-httpclient: FTBFS in jessie: ERROR: Test ruby2.1 failed: Errno::ECONNRESET: Connection reset by peer - SSL_connect Set Bug forwarded-to-address to 'https://github.com/nahi/httpclient/issues/233'. thanks Stopping processing here. Please contact me if you need assistance. -- 768673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768673 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#770941: [PKG-Openstack-devel] Bug#770941: closed by Thomas Goirand z...@debian.org (Re: Bug#770941: closed by Thomas Goirand z...@debian.org (Re: Bug#770941: nova-common - Overrides database c
Hi Bastian Blank bastian.bl...@credativ.de writes: Control: reopen -1 On Wed, Nov 26, 2014 at 01:09:08AM +, Debian Bug Tracking System wrote: It is a valid DSN. In this: postgresql:///nova Where's the user and password? What's the hostname? User and password is not needed for ident auth, empty hostname is documented as using the unix socket. And the documentation tells:[1] | These URLs follow RFC-1738, and usually can include username, password, | hostname, database name as well as optional keyword arguments for | additional configuration. In some cases a file path is accepted, and in | others a “data source name” replaces the “host” and “database” portions. So they _can_ include, not they _must_ include. Also there are examples of this usage. If theoretically, this *may* be a valid DSN, but practically, I don't think you'd be using a DNS without a valid hostname, login and pass. It is valid in practice, otherwise it would not work in the first place. I tend to agree with Bastian here. This change must be preserved. And to me it also seems that having the database on the same host is a very valid and not only theoretical setup. But basically this is beyond the point (see below). And even if not, it must not change it. The idea behind the policy is that a config script shouldn't change a valid configuration, so that it is possible edit the configuration file, and that change be kept when installing or upgrading. No, the idea is that the user have all right to change it to whatever he wants. You can use ucf to do this task of merging config files. Again I tend to agree with Bastian. I can't see anything in policy (section 10.7.3) where the provision local changes must be preserved during a package upgrade is somehow limited to configurations the maintainer thinks are valid. While I can see some valid cases where you can change or upgrade a clearly non functioning config file. This is definitely not the case we are talking about. P.S: Please don't reopen the bug. The config and postinst scripts are doing exactly what I wanted them to do, and I feel like this is the correct behavior. If you don't like the current behavior, I welcome you to discuss it in the packaging list, but using BTS ping-pong isn't the way to do so. Please keep this bug open. There is obviously a bug somewhere in the maintainer scripts. Well, I don't think so. You can yourself refer to the ctte or I will. I don't think we need the ctte to solve this. Can't we just work together and find a solution? Gaudenz signature.asc Description: PGP signature
Processed: Re: Bug#769947: mate-terminal: Segfaults after update
Processing control commands: close -1 Bug #769947 [mate-terminal] mate-terminal: Segfaults after update Marked Bug as done -- 769947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769947 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#769947: mate-terminal: Segfaults after update
Control: close -1 Hi Alex, hi Ben, On Di 25 Nov 2014 20:40:03 CET, Alex Corcoles wrote: More or less, doing some trial and error I discovered that using desktopConfig instead of defaultConfig fixes magically the problem. https://github.com/alexpdp7/xmonad.pdp7/commit/037a44a8f7541fb3983ade528e34b4cfa0ea81a5 . I suppose there's some bug somewhere, but I'm happy for now- don't know if Ben Whyall has the same problem or not. ok. Thanks for feedback. Closing this bug as it is probably not (only) related to mate-terminal. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgp3Y_sWJ8fzk.pgp Description: Digitale PGP-Signatur
Processed: reported upstream
Processing commands for cont...@bugs.debian.org: forwarded 770251 https://github.com/plataformatec/responders/issues/105 Bug #770251 [ruby-jbuilder,ruby-responders] ruby-jbuilder,ruby-responders: error when trying to install together Set Bug forwarded-to-address to 'https://github.com/plataformatec/responders/issues/105'. End of message, stopping processing here. Please contact me if you need assistance. -- 770251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770251 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#770982: libwebcam0-dev: dynctrl-logitech.h is missing in libwebcam0-dev
Hi, I'll fix this and request a package upload. Thank you, Paulo 2014-11-25 20:24 GMT+00:00 Fufu Fang fangf...@fangfufu.co.uk: Hi, A temporary fix is indeed copying the header file from the source to /usr/local/include. However I haven't got much clue on Debian's package process. Are there any pointers to help me get started? I suppose I can submit a patch or something. Best wishes, Fufu On 25/11/14 20:19, Juhani Numminen wrote: Hi, http://sources.debian.net/src/libwebcam/0.2.4-1/common/include/ Folder: include .. (parent) dynctrl-logitech.h webcam.h Quickly checking using sources.debian.net shows that the file dynctrl-logitech.h is included in the source package. I think this bug might be easily fixable just by modifying debian/libwebcam0-dev.install. Cheers, Juhani PS. Sorry for not actually fixing an RC bug, but maybe providing additional info will speed up someone else’s job. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767821: gir1.2-caja is someway broken - unable to import Caja from gi.repository
Control: close -1 Hi Norbert, this issue is fixed in unstable (never was broken, actually). More info: see below. On So 02 Nov 2014 21:17:52 CET, Nrbrtx wrote: Package: gir1.2-caja Severity: grave Version: 1.8.1-2~bpo70+1 Dear Debian developers! As you may know from GitHub (mate-desktop / caja / 322 https://github.com/mate-desktop/caja/issues/322) and from LP: #1170017 https://bugs.launchpad.net/bugs/1170017 I'm trying to port TortoiseHG extension from Nautilus to Caja (see comment 18 https://bugs.launchpad.net/ubuntu/+source/nautilus-python/+bug/1170017/comments/18 from the bug). I placed my python extension script in my BitBucket repository https://bitbucket.org/nrbrtx/caja-thg. For integration with Caja my script should be copied to ~/.local/share/caja-python/extensions/caja-thg.py after that Caja should be relaunched with caja -q. I tested it in Debian 8 (jessie/sid) - it works as expected (there are green star icon on a folder and TortoiseHG drop-down menus). But if I install gir1.2-caja in Debian 7 I can't use my extension because of python error: $python -c from gi.repository import Caja ERROR:root:Could not find any typelib for Caja Traceback (most recent call last): File string, line 1, in module ImportError: cannot import name Caja This is caused by wrong file-structure of gir1.2-caja package. It has /usr/lib/i386-linux-gnu/girepository-1.0/Caja-2.0.typelib but not in /usr/lib/girepository-1.0/Caja-2.0.typelib. If I move typelib manually to correct location, I can use it, but get another bug - 766879 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766879. The bug about Caja-2.0.typelib exists in Ubuntu too - it is bug 1380313 https://bugs.launchpad.net/bugs/1380313. Please fix this bug in Debian. This is a wheezy-backports only bug. I Cc: the debian-backports ML with this mail. After I have uploaded all necessary bugfixes to Debian unstable (+ received unblock conformations) I will go through all MATE packages in wheezy-backports and bring them up-to-date. However, this may take a little while, because getting MATE fixed in Debian testing currently has my priority. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpQPbzlq6Ras.pgp Description: Digitale PGP-Signatur
Processed: gir1.2-caja is someway broken - unable to import Caja from gi.repository
Processing control commands: close -1 Bug #767821 [gir1.2-caja] gir1.2-caja is someway broken - unable to import Caja from gi.repository Marked Bug as done -- 767821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#761234: openvpn: Openvpn connects to server but no data pass the tunel. Bad LZO decompression in server log
Processing control commands: severity -1 important Bug #761234 [openvpn] openvpn: Openvpn connects to server but no data pass the tunel. Bad LZO decompression in server log Severity set to 'important' from 'grave' tags -1 + moreinfo unreproducible Bug #761234 [openvpn] openvpn: Openvpn connects to server but no data pass the tunel. Bad LZO decompression in server log Added tag(s) unreproducible and moreinfo. -- 761234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761234 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#761234: openvpn: Openvpn connects to server but no data pass the tunel. Bad LZO decompression in server log
Control: severity -1 important Control: tags -1 + moreinfo unreproducible On Thu, 02 Oct 2014, Alberto Gonzalez Iniesta wrote: Czesz Maciej, Could you send me your configuration files (minus the sensitive data) so I can try to reproduce it? Maciej, if you don't provide further information, there's no way that we can diagnose anything useful ouf of your report. Given that nobody else reported similar problems (and given that I'm using the current openvpn without problems), I'm downgrading the severity of this bug. It doesn't deserve to be release critical. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: akonadi-server: upgrade to akonadi-12-1-1 does not work so kmail too
Processing control commands: tag -1 + moreinfo Bug #747637 [akonadi-server] akonadi-server: upgrade to akonadi-12-1-1 does not work so kmail too Added tag(s) moreinfo. -- 747637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747637 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#767554: python-persistent and python-zodb: error when trying to install together
Hello, Andreas Beckmann a...@debian.org writes: Followup-For: Bug #767554 Control: found -1 767554 4.0.8-2 The Conflicts does not work ... without the proper epoch ... you need Conflicts: python-zodb ( 1:3.11.0~) Selecting previously unselected package python-persistent. Unpacking python-persistent (from .../python-persistent_4.0.8-2_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/python-persistent_4.0.8-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/persistent/dict.py', which is also in package python-zodb 1:3.9.7-2 Errors were encountered while processing: /var/cache/apt/archives/python-persistent_4.0.8-2_amd64.deb Really sorry about that. FTR, I have not uploaded anything yet because the release team would prefer to avoid the Conflicts if possible and make python-zodb depends upon python-persistent instead. AFAIK, it does not seem to be an issue but I have just sent an email to upstream author to confirm it's not going to be an issue... Cheers, -- Arnaud Fontaine signature.asc Description: PGP signature
Bug#747637: akonadi-server: upgrade to akonadi-12-1-1 does not work so kmail too
Control: tag -1 + moreinfo Hello Markus Merlin, you reported that you were affected by Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747637 Maximiliano believes that the latest update 1.13.0-1 should fix the db upgrade problems (see below). Can you confirm this so that we can close this bug ? On Tue, 19 Aug 2014, Maximiliano Curia wrote: I think the new uploaded akonadi version (1.13.0-1) fixes more db upgrade cases, but I haven't had any issues with the previous upgrades so it's hard for me to be sure. Could you please confirm if it fixes the issues you had with the 1.12.1 version? -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760733: libspring-java: CVE-2014-0225
Hello Stephen, On Mon, 08 Sep 2014, Stephen Nelson wrote: For what it's worth, CVE-2014-3578 was assigned to a directory traversal vulnerability in libspring-java ( http://www.pivotal.io/security/cve-2014-3578) Thanks for letting us know about this one. I've had a quick look and it might be more difficult to fix given that there hasn't been a specific commit made in a later version of Spring which could be backported. However, I will look into this in more detail and report back to the BTS for this bug. I haven't seen any followup yet. Do you still plan to do the required investigation? This bug is one of Jessie's remaining release critical bugs so it would be nice if there could be some progress. (Of course, packaging a new upstream version can also be considered by release team members if backporting is too much work) Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771054: lintian: FTBFS: binaries-from-other-arch fails with latest binutils
Package: lintian Severity: serious Justification: FTBFS Version: 2.5.30+deb8u2 Hello, With the recent binutils 2.24.90.20141124-1, one lintian test started failing: | Running binaries-from-other-arch 1.0... building... testing... FAILED | --- t/tests/binaries-from-other-arch/tags 2014-10-13 22:45:41.0 +0200 | +++ /«BUILDDIR»/lintian-2.5.30+deb8u2/debian/test-out/tests/binaries-from-other-arch/tags.binaries-from-other-arch 2014-11-26 12:15:08.758293112 +0100 | @@ -1,4 +1,3 @@ | E: binaries-from-other-arch: binary-from-other-architecture usr/bin/elfobject | E: binaries-from-other-arch: statically-linked-binary usr/bin/elfobject | -W: binaries-from-other-arch: apparently-corrupted-elf-binary usr/bin/elfobject | W: binaries-from-other-arch: binary-without-manpage usr/bin/elfobject This happens both during packge build (hence the RC level) and also during the autopkgtest. I confirm that the test works with binutils 2.24.90.2014 still. This might very well be a regression in binutils itself, or lintian's invocation of it needs to be adjusted, so please reassign if appropriate. I attach the complete build log for reference (but the above is the essential bit from it). Thanks for considering, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) lintian_2.5.30+deb8u2_amd64-20141126-1211.build.xz Description: Binary data signature.asc Description: Digital signature
Bug#760733: libspring-java: CVE-2014-0225
On 26 Nov 2014 10:45, Raphael Hertzog hert...@debian.org wrote: Hello Stephen, On Mon, 08 Sep 2014, Stephen Nelson wrote: For what it's worth, CVE-2014-3578 was assigned to a directory traversal vulnerability in libspring-java ( http://www.pivotal.io/security/cve-2014-3578) Thanks for letting us know about this one. I've had a quick look and it might be more difficult to fix given that there hasn't been a specific commit made in a later version of Spring which could be backported. However, I will look into this in more detail and report back to the BTS for this bug. I haven't seen any followup yet. Do you still plan to do the required investigation? This bug is one of Jessie's remaining release critical bugs so it would be nice if there could be some progress. (Of course, packaging a new upstream version can also be considered by release team members if backporting is too much work) I couldn't find any specifics on this vulnerability other than the upstream saying it's not present in their currently supported versions. Therefore it looks like upgrading to 3.2.x would solve the security issue but is quite a lot of work and involves dependencies not yet packaged in Debian. I'm happy to help but ask more experienced Java team members on what's the best course of action here. Cheers Stephen
Bug#760733: libspring-java: CVE-2014-0225
I've been investigating this issue as well. I contacted an upstream developer and it seems the actual fix for this issue is unknown. The version 3.2.0 was just reported as not vulnerable by the security researched who discovered this issue. I can prepare an upgrade to the latest 3.2.x version but this will at least require libhibernate-validator-java to be unblocked as well. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760733: libspring-java: CVE-2014-0225
On Wed, Nov 26, 2014 at 12:40:37PM +0100, Emmanuel Bourg wrote: I've been investigating this issue as well. I contacted an upstream developer and it seems the actual fix for this issue is unknown. The version 3.2.0 was just reported as not vulnerable by the security researched who discovered this issue. I can prepare an upgrade to the latest 3.2.x version but this will at least require libhibernate-validator-java to be unblocked as well. I didn't look into the specific issue, but Red Hat Bugzilla has references to isolated patches? https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-0225 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#760733: libspring-java: CVE-2014-0225
Le 26/11/2014 12:41, Moritz Muehlenhoff a écrit : I didn't look into the specific issue, but Red Hat Bugzilla has references to isolated patches? https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-0225 I don't know why the title of the mail refers to CVE-2014-0225, but the bug #760733 is related to CVE-2014-3578. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: FTBFS in a cowbuilder: Error: listen EADDRNOTAVAIL
Processing control commands: tags -1 patch Bug #766484 [nodejs] FTBFS in a cowbuilder: Error: listen EADDRNOTAVAIL Added tag(s) patch. -- 766484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766484 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#766484: FTBFS in a cowbuilder: Error: listen EADDRNOTAVAIL
Control: tags -1 patch On Sat, 22 Nov 2014 13:48:43 +0100 Tobias Frost t...@debian.org wrote: I saw your offer to prepare a patch, which would be very appreciated. I would sponsor this as an NMU. Well this is the patch mentioned earlier from 0.10.33 [1] which fixes the build for me. Thanks, James [1] https://github.com/joyent/node/commit/707cc25011d142fe4ade14ce2aa083a96ef15bcb -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766484: Info received (FTBFS in a cowbuilder: Error: listen EADDRNOTAVAIL)
Oops, actually attach the patch this time.
James
From 707cc25011d142fe4ade14ce2aa083a96ef15bcb Mon Sep 17 00:00:00 2001
From: Fedor Indutny fe...@indutny.com
Date: Wed, 15 Oct 2014 20:50:15 +0400
Subject: [PATCH] test: fix test-crypto-stream
Because of constant-timeness change made in openssl-1.0.1j the error is
no longer returned from EVP_DecryptFinal_ex. Now it just return 0, and
thus the error message does not contain proper error code. Adapt to this
change, there is not much that we could do about it.
---
test/simple/test-crypto-stream.js | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/test/simple/test-crypto-stream.js b/test/simple/test-crypto-stream.js
index 72c9776..402761e 100644
--- a/test/simple/test-crypto-stream.js
+++ b/test/simple/test-crypto-stream.js
@@ -70,8 +70,7 @@ var key = new Buffer('48fb56eb10ffeb13fc0ef551bbca3b1b', 'hex'),
cipher.pipe(decipher)
.on('error', common.mustCall(function end(err) {
-// TypeError: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
-assert(/:06065064:/.test(err));
+assert(/::/.test(err));
}));
cipher.end('Papaya!'); // Should not cause an unhandled exception.
Bug#771062: android-platform-frameworks-native: needs Breaks, Replaces for successful upgrades from 21-1
Source: android-platform-frameworks-native Version: 21-2 Severity: serious Tags: patch pending Justification: Policy 7.6 android-platform-frameworks-native has a bug very similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770328 which is already fixed in git by http://anonscm.debian.org/cgit/android-tools/android-platform-frameworks-native.git/commit/?id=3a4dc72b7d058caac7906ffa3e9a72c612621f3c. Please upload it when convenient. Would getting this into testing also fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769251 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769236 ? If it would, please reassign those bugs to src:android-platform-frameworks-native and mark them as fixed in 21-2. Regards, S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771054: lintian: FTBFS: binaries-from-other-arch fails with latest binutils
what is the test supposed to test? There is a test file shipped, but I can't see yet what is being tested for. Is there a way to call objdump directly to reproduce this issue? Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767653:
Hi Tobi, * Tobias Frost t...@debian.org [2014-11-25 20:53]: built uploaded! Thanks! Please apply for the unblock. Done: #771053 (Note that I s/UNRELEASED/unstable in d/changelog; make sure to do this to in your repository) Done. Cheers Jochen signature.asc Description: Digital signature
Bug#770597: go ahead an upload
Hey Reiner, Thanks for the fix, looks like you have the package ready to upload. Please go ahead and upload it! :-) .hc signature.asc Description: OpenPGP digital signature
Bug#770597: go ahead an upload
Hey Reiner, Thanks for the fix, looks like you have the package ready to upload. Please go ahead and upload it! :-) .hc signature.asc Description: OpenPGP digital signature
Processed: fixed 768369 in 1:1.3.1-11
Processing commands for cont...@bugs.debian.org: # close bug 768369, CVE-2014-9092 fixed with 1:1.3.1-11 upload to unstable fixed 768369 1:1.3.1-11 Bug #768369 [libjpeg62-turbo] libjpeg-turbo: CVE-2014-9092: [DOS] Stack smashing Marked as fixed in versions libjpeg-turbo/1:1.3.1-11. thanks Stopping processing here. Please contact me if you need assistance. -- 768369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768369 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#727800: kmail: KMail goes bonkers following Qt update
tag 727800 moreinfo thanks Hi! As Sandro pointed out, this seems fixed in newer versions. Can you please test if this is still an issue for you? Kinds regards, Lisandro. -- Without us [Free Software developers], people would study computer science and programming without ever having seen a real program in its entirety. That's like becoming writers without ever having read a complete book. Matthias Ettrich, founder of the KDE project. http://www.efytimes.com/efytimes/25412/news.htm Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: Re: kmail: KMail goes bonkers following Qt update
Processing commands for cont...@bugs.debian.org: tag 727800 moreinfo Bug #727800 [akonadi] kmail: KMail goes bonkers following Qt update Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 727800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727800 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: fixed 770329 21-4
Processing commands for cont...@bugs.debian.org: fixed 770329 21-4 Bug #770329 [android-libhost-dev] android-libhost-dev: fails to upgrade from 'testing' - trying to overwrite /usr/lib/android/libhost.so Ignoring request to alter fixed versions of bug #770329 to the same values previously set End of message, stopping processing here. Please contact me if you need assistance. -- 770329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770329 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: fixed 770329 21-4
Processing commands for cont...@bugs.debian.org: fixed 770329 21-4 Bug #770329 [android-libhost-dev] android-libhost-dev: fails to upgrade from 'testing' - trying to overwrite /usr/lib/android/libhost.so Marked as fixed in versions android-platform-build/21-4. End of message, stopping processing here. Please contact me if you need assistance. -- 770329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770329 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: fixed 770329 21-4
Processing commands for cont...@bugs.debian.org: fixed 770329 21-4 Bug #770329 [android-libhost-dev] android-libhost-dev: fails to upgrade from 'testing' - trying to overwrite /usr/lib/android/libhost.so Ignoring request to alter fixed versions of bug #770329 to the same values previously set End of message, stopping processing here. Please contact me if you need assistance. -- 770329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770329 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: fixed 769251 21-4
Processing commands for cont...@bugs.debian.org: fixed 769251 21-4 Bug #769251 [src:android-platform-build] android-platform-build: FTBFS in jessie/i386: libutils.so: undefined reference to `android_atomic_or' Marked as fixed in versions android-platform-build/21-4. End of message, stopping processing here. Please contact me if you need assistance. -- 769251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769251 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#771071: [cyrus-imapd-2.4] Missing separator breaks configure parameters
Package: cyrus-imapd-2.4 Version: 2.4.16-4+deb7u2 Severity: critical Tags: patch Dear Cyrus-Imapd maintainers, While looking for the reason why this version was using logging LOCAL6 as its logging facility, I came across an issue introduced on the parameters passed at configuring stage in which an order is missing a backslash, which breaks the configure line on several parameters, between others user/group of the cyrus daemon. Please find suitable applying this patch ASAP and requesting Release-Team a freeze exception: Thanks a lot for your work and keep the great work flowing! Cheers, Dererk -- BOFH excuse #59: failed trials, system needs redesigned diff -ruN cyrus-imapd-2.4-2.4.17+caldav~beta10/debian/rules cyrus-imapd-2.4-2.4.17+caldav~beta10-new/debian/rules --- cyrus-imapd-2.4-2.4.17+caldav~beta10/debian/rules 2014-11-18 10:37:11.0 -0300 +++ cyrus-imapd-2.4-2.4.17+caldav~beta10-new/debian/rules 2014-11-26 11:32:22.092151370 -0300 @@ -93,7 +93,7 @@ --enable-idled \ --enable-http \ --with-opendkim-libdir=/usr/include/opendkim \ - --with-opendkim-incdir=/usr/lib + --with-opendkim-incdir=/usr/lib \ --with-cyrus-user=cyrus --with-cyrus-group=mail \ --with-com_err= \ --with-pidfile=/var/run/cyrmaster.pid \
Bug#769646: still happening with android-libcutils 21-5
I can't reproduce this error on my chroot. I'm at a loss as to why this is happening. android-platform-build 21-4 failed again with the same error: https://buildd.debian.org/status/fetch.php?pkg=android-platform-buildarch=i386ver=21-4stamp=1417007655file=log signature.asc Description: OpenPGP digital signature
Bug#769446: [Pkg-freeipa-devel] Bug#769446: certmonger: Failed to issue method call: Unit dbus.socket failed to load: No such file or directory.
On 22.11.2014 16:35, Simon McVittie wrote: On Thu, 13 Nov 2014 at 23:30:00 -0800, Cameron Norman wrote: On Thu, 13 Nov 2014 17:59:51 +0100 Benjamin Drung benjamin.dr...@profitbricks.com wrote: Setting up certmonger (0.75.14-2) ... Failed to issue method call: Unit dbus.socket failed to load: No such file or directory. invoke-rc.d: initscript certmonger, action start failed. [...] certmonger should probably depend on dbus. Please do not do that. Both the Upstart job and init script work just fine without D-Bus installed. Instead, I think that the certmonger systemd service should change its type from dbus to forking and remove the `-n` option. Alternatively, it could use Type=simple and keep the `-n` option but then you do not get readiness. Not sure if that is critical. If you don't want to depend on dbus then changing the Type to forking (and removing the -n option) seems best. The service already has the necessary PIDFile= line to be able to tell systemd which of its processes after forking is to be considered the main one. I'll ask upstream why the change to dbus type was made in commit 74a89a3b6d7307a26b38055addee6a70908df370 Author: Nalin Dahyabhai na...@dahyabhai.net Date: Thu Aug 11 13:25:54 2011 -0400 - fix problems with the .service file I think you can still keep dbus based activation without Type=dbus and a without a dependency on dbus, but you should ask the systemd maintainers about that. If you leave the BusName= line intact, that provides the prerequisite for the systemd side of D-Bus system service activation. However, this seems to be irrelevant, because certmonger doesn't install anything in /usr/share/dbus-1/system-services, so dbus-daemon will never try to service-activate it on-demand anyway; anything communicating with it over D-Bus is only going to work because the init system already started it. There appears to be an attempt to provide system service activation in http://anonscm.debian.org/cgit/pkg-freeipa/certmonger.git/tree/systemd/org.fedorahosted.certmonger.service.in but (a) it isn't currently installed, (b) I think it may be starting the wrong binary (certmonger-session), and (c) it does not have the SystemdService key, so dbus-daemon would try to run it as a child process (via a setuid helper, dbus-daemon-launch-helper) instead of asking systemd to do it. That file was last modified over three years ago, so I guess the idea has since been dropped and forgotten. commit 359f1b3e6d13b1f7601951eb7cebbf4250fb389f Author: Nalin Dahyabhai nalin@ Date: Wed Jul 13 14:15:05 2011 -0400 - on second thought, put system bus activation on hold -- t -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771062: marked as done (android-platform-frameworks-native: needs Breaks, Replaces for successful upgrades from 21-1)
Your message dated Wed, 26 Nov 2014 15:19:27 + with message-id e1xtenl-0001zj...@franck.debian.org and subject line Bug#771062: fixed in android-platform-frameworks-native 21-3 has caused the Debian Bug report #771062, regarding android-platform-frameworks-native: needs Breaks, Replaces for successful upgrades from 21-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 771062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: android-platform-frameworks-native Version: 21-2 Severity: serious Tags: patch pending Justification: Policy 7.6 android-platform-frameworks-native has a bug very similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770328 which is already fixed in git by http://anonscm.debian.org/cgit/android-tools/android-platform-frameworks-native.git/commit/?id=3a4dc72b7d058caac7906ffa3e9a72c612621f3c. Please upload it when convenient. Would getting this into testing also fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769251 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769236 ? If it would, please reassign those bugs to src:android-platform-frameworks-native and mark them as fixed in 21-2. Regards, S ---End Message--- ---BeginMessage--- Source: android-platform-frameworks-native Source-Version: 21-3 We believe that the bug you reported is fixed in the latest version of android-platform-frameworks-native, 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 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hans-Christoph Steiner h...@eds.org (supplier of updated android-platform-frameworks-native package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Nov 2014 14:55:28 +0100 Source: android-platform-frameworks-native Binary: android-libutils android-libutils-dev Architecture: source amd64 Version: 21-3 Distribution: unstable Urgency: low Maintainer: Android tools Maintainer android-tools-de...@lists.alioth.debian.org Changed-By: Hans-Christoph Steiner h...@eds.org Description: android-libutils - Android utility library android-libutils-dev - Android utility library - Development files Closes: 771062 Changes: android-platform-frameworks-native (21-3) unstable; urgency=low . * add Breaks: and Replaces: for proper upgrading (Closes: #771062) Checksums-Sha1: 319906d628981b7cfa4866bca7ae2019438d0cb6 2488 android-platform-frameworks-native_21-3.dsc b95f936013934c44eed056e6f507fcbaddc5d430 7208 android-platform-frameworks-native_21-3.debian.tar.xz 47c407aef53ddeb3bc3c8e6eb86c5f87ff3931af 67984 android-libutils_21-3_amd64.deb 331d04dae09c81d7c8d8e144c5fe4aac42e15111 141850 android-libutils-dev_21-3_amd64.deb Checksums-Sha256: 545b679ce3af8b968980d471fc8aed46f2e8fc47ec558b3e5ece0f0ff430c4f7 2488 android-platform-frameworks-native_21-3.dsc 724f776e67eed943c67e5114ee9f61e4d0f0cc219873fcbbbce70d52e81bc8a5 7208 android-platform-frameworks-native_21-3.debian.tar.xz 5c207adf16e11394ce4f81559779c53099603ef3ba9f5a209a20efaa2722d642 67984 android-libutils_21-3_amd64.deb 73aa1cab982b23bc1fcc84f6658dcb8cf25e1c2d2cda1697be947fcdd45b4a71 141850 android-libutils-dev_21-3_amd64.deb Files: 3f51b9e5358de12c2c3c637a850fe0a3 2488 devel extra android-platform-frameworks-native_21-3.dsc e7447d51a872f287609a37cb00e3cd6c 7208 devel extra android-platform-frameworks-native_21-3.debian.tar.xz 0a2189b343fb4b415cd60078a662cd8c 67984 libs extra android-libutils_21-3_amd64.deb 134d1d840f1c718950a199691a26cace 141850 libdevel extra android-libutils-dev_21-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: GPG for Android - https://guardianproject.info/code/gnupg/ iQIcBAEBCAAGBQJUdd3oAAoJEJ8P5Yc3S76B6d0QAJ5+8/L4xC26CL0a26uZPU0L lYYMgM1aC2kjb0tTKkbhY2wPRvfBd4Dm5VhGgTUqYwoTBxSFmm9CJisnhuJ0ZI+j 0wdLInBDYzEDBW234/Lzkz6g8UH51LyeqAsV6RUiOw3W55CnqKhf5wkPic30Omdb MSKC7xAbMjOTUV6+lXBkw47Pd4NSCwEIDU7H3yginpPogDgXBKYmCC0z4h+gF6jN 5KY+d5ScpDEIQx8jzE6w7p71SlLg/wYrro93KpmzgW6XNOaFuCcyFvYcNj9vTfrN lGRmXSU86nuUzlSffs+jUe7q0zOfln/t7zCVNQIl7x26eOUeMZU3vnTXySC983hy
Processed: xdg-utils breaks MATE DE, please upgrade
Processing control commands: retitle -1 several breakages in xdg-utils 1.1.0~rc1 (esp. MATE) Bug #754219 [xdg-utils] xdg-utils: new upstream version available, update watch file Changed Bug title to 'several breakages in xdg-utils 1.1.0~rc1 (esp. MATE)' from 'xdg-utils: new upstream version available, update watch file' severity -1 grave Bug #754219 [xdg-utils] several breakages in xdg-utils 1.1.0~rc1 (esp. MATE) Severity set to 'grave' from 'normal' -- 754219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754219 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#770977: [Python-modules-team] Bug#770977: pytest: Fails to build from source
On Tue, Nov 25, 2014 at 04:35:52PM -0500, wrote: Hmm, interesting, I can try and see if I can reproduce it on more systems. So the machine I was building on is an IBM x3650 with 2 quad core 2.5GHz xeons. Kernel is amd64, userspace is i386 wheezy, chroot is i386 jessie buildd variant. So I just tried some more tests. jessie-amd64 on sid-amd64: works jessie-i386 on sid-amd64: works jessie-i386 on wheezy-i386(with amd64 kernel): fails Same chroot copied to a sid machine (so 3.16 kernel instead of 3.2 kernel: works It would appear that pytest fails on python 3.4.2 when the underlying kernel is 3.2 for some reason that I can't even imagine what is. I will try upgrading the kernel on our build machine to the wheezy-backprot of 3.16 and see if that solves the problem and report back. So to confirm I did this: Create a VM with a fresh wheezy install. Create a jessie chroot with debootstrap. Try building pytest. It fails. Upgrade wheezy kernel to 3.16 from wheezy-backports. Try building pytest in chroot again. It passes. So the problem is caused by running on the 3.2 wheezy kernel. So weird as that is, I think the bug can be closed. No idea if this is a bug in the old kernel, or glibc, or python 3.4, with one of them making some assumption about kernel behaviour based on the linux-libc-dev headers they were built against. I suppose it means there is a chance a system upgrading from wheezy to jessie could have some issues with running python3 stuff in some cases until it is rebooted to the jessie kernel, although that would probably be recommended to do as soon as possible anyhow. -- Len Sorensen -- 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 562907 is serious
Processing commands for cont...@bugs.debian.org: severity 562907 serious Bug #562907 [python-lightblue] missing dependency on pybluez Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 562907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562907 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: Grave severity
Processing commands for cont...@bugs.debian.org: severity 718596 grave Bug #718596 [obexd-client] Error: The name org.openobex.client was not provided by any .service files Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 718596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718596 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#770977: [Python-modules-team] Bug#770977: Bug#770977: pytest: Fails to build from source
Quoting Lennart Sorensen (2014-11-26 16:53:44) On Tue, Nov 25, 2014 at 04:35:52PM -0500, wrote: Hmm, interesting, I can try and see if I can reproduce it on more systems. So the machine I was building on is an IBM x3650 with 2 quad core 2.5GHz xeons. Kernel is amd64, userspace is i386 wheezy, chroot is i386 jessie buildd variant. So I just tried some more tests. jessie-amd64 on sid-amd64: works jessie-i386 on sid-amd64: works jessie-i386 on wheezy-i386(with amd64 kernel): fails Same chroot copied to a sid machine (so 3.16 kernel instead of 3.2 kernel: works It would appear that pytest fails on python 3.4.2 when the underlying kernel is 3.2 for some reason that I can't even imagine what is. I will try upgrading the kernel on our build machine to the wheezy-backprot of 3.16 and see if that solves the problem and report back. So to confirm I did this: Create a VM with a fresh wheezy install. Create a jessie chroot with debootstrap. Try building pytest. It fails. Upgrade wheezy kernel to 3.16 from wheezy-backports. Try building pytest in chroot again. It passes. So the problem is caused by running on the 3.2 wheezy kernel. So weird as that is, I think the bug can be closed. No idea if this is a bug in the old kernel, or glibc, or python 3.4, with one of them making some assumption about kernel behaviour based on the linux-libc-dev headers they were built against. I suppose it means there is a chance a system upgrading from wheezy to jessie could have some issues with running python3 stuff in some cases until it is rebooted to the jessie kernel, although that would probably be recommended to do as soon as possible anyhow. I think we should downgrade it and maybe tag it moreinfo, but it shouldn't be closed. The case of a Jessie kernel on a machine running a kernel that is not Jessie's is a valid use case IMHO. Not that I'm volunteering to track down and fix it! Cheers, Simon signature.asc Description: signature
Bug#770977: [Python-modules-team] Bug#770977: Bug#770977: pytest: Fails to build from source
On Wed, Nov 26, 2014 at 05:16:43PM +0100, Simon Chopin wrote: I think we should downgrade it and maybe tag it moreinfo, but it shouldn't be closed. The case of a Jessie kernel on a machine running a kernel that is not Jessie's is a valid use case IMHO. Not that I'm volunteering to track down and fix it! Yeah that was why I mentioned that part. It is a slight concern. But certainly not a true FTBFS and not RC for jessie. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754755: [rt.cpan.org #98683] libinline-java-perl: FTBFS on mips: test suite issues
: *** [debian/stamp-makefile-check] Error 2 /usr/share/cdbs/1/class/makefile.mk:67: recipe for target 'debian/stamp-makefile-check' failed dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ Build finished at 20141126-1651 Finished ââââââââ E: Build failure (dpkg-buildpackage died)
Bug#754755: [rt.cpan.org #98683] libinline-java-perl: FTBFS on mips: test suite issues
On Fri, 21 Nov 2014 10:39:51 -0500, Ed J via RT wrote: URL: https://rt.cpan.org/Ticket/Display.html?id=98683 Please could you try the new 0.56 rather than stick with 0.53? 0.56 has been uploaded to Debian unstable. Build results will soon show up at https://buildd.debian.org/status/logs.php?pkg=libinline-java-perl (and http://buildd.debian-ports.org/status/logs.php?pkg=libinline-java-perl for other architectures) 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#766879: gir1.2-caja is someway broken - unable to import Caja from gi.repository
Dear Mike! I tested my caja-thg.py with python-caja 1.8.1-2 (from unstable) in Debian jessie/sid - it works as expected. I hope that Jessie will have this correct version. Thank you! I understood about wheezy-backports. I'm ready to test updated packages. On Wed, Nov 26, 2014 at 1:30 PM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Control: close -1 Hi Norbert, this issue is fixed in unstable (never was broken, actually). More info: see below. On So 02 Nov 2014 21:17:52 CET, Nrbrtx wrote: Package: gir1.2-caja Severity: grave Version: 1.8.1-2~bpo70+1 Dear Debian developers! As you may know from GitHub (mate-desktop / caja / 322 https://github.com/mate-desktop/caja/issues/322) and from LP: #1170017 https://bugs.launchpad.net/bugs/1170017 I'm trying to port TortoiseHG extension from Nautilus to Caja (see comment 18 https://bugs.launchpad.net/ubuntu/+source/nautilus- python/+bug/1170017/comments/18 from the bug). I placed my python extension script in my BitBucket repository https://bitbucket.org/nrbrtx/caja-thg. For integration with Caja my script should be copied to ~/.local/share/caja-python/extensions/caja-thg.py after that Caja should be relaunched with caja -q. I tested it in Debian 8 (jessie/sid) - it works as expected (there are green star icon on a folder and TortoiseHG drop-down menus). But if I install gir1.2-caja in Debian 7 I can't use my extension because of python error: $python -c from gi.repository import Caja ERROR:root:Could not find any typelib for Caja Traceback (most recent call last): File string, line 1, in module ImportError: cannot import name Caja This is caused by wrong file-structure of gir1.2-caja package. It has /usr/lib/i386-linux-gnu/girepository-1.0/Caja-2.0.typelib but not in /usr/lib/girepository-1.0/Caja-2.0.typelib. If I move typelib manually to correct location, I can use it, but get another bug - 766879 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766879. The bug about Caja-2.0.typelib exists in Ubuntu too - it is bug 1380313 https://bugs.launchpad.net/bugs/1380313. Please fix this bug in Debian. This is a wheezy-backports only bug. I Cc: the debian-backports ML with this mail. After I have uploaded all necessary bugfixes to Debian unstable (+ received unblock conformations) I will go through all MATE packages in wheezy-backports and bring them up-to-date. However, this may take a little while, because getting MATE fixed in Debian testing currently has my priority. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das- netzwerkteam.de.xfb
Bug#770762: marked as done (libinline-java-perl: Build dependencies are too loose)
Your message dated Wed, 26 Nov 2014 17:49:10 + with message-id e1xtgie-00021k...@franck.debian.org and subject line Bug#770762: fixed in libinline-java-perl 0.56-1 has caused the Debian Bug report #770762, regarding libinline-java-perl: Build dependencies are too loose 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.) -- 770762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libinline-java-perl Version: 0.53-3 Severity: serious If I try building src:libinline-java-perl in a chroot with gcj-jdk installed but not default-jdk, then that satisfies the Build-Depends. However, the build then fails: debian/rules build test -x debian/rules mkdir -p . Scanning upstream source for new/changed copyright notices... licensecheck -c '.*' -r --copyright -i '^debian/(changelog|copyright(|_hints|_newhints))' -l '9' * | /usr/lib/cdbs/licensecheck2dep5 debian/copyright_newhints 7 combinations of copyright and licensing found. No new copyright notices found - assuming no news is good news... touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft (cd . /usr/bin/perl Makefile.PL INSTALLDIRS=vendor ) Welcome to the Inline::Java installation procedure. Using /usr/lib/jvm/default-java as J2SDK directory. Java 2 SDK installation directory '/usr/lib/jvm/default-java' does not exist. /usr/share/cdbs/1/class/perl-makemaker.mk:44: recipe for target 'Makefile' failed make: *** [Makefile] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: libinline-java-perl Source-Version: 0.56-1 We believe that the bug you reported is fixed in the latest version of libinline-java-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev r...@ringlet.net (supplier of updated libinline-java-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Nov 2014 12:31:04 +0200 Source: libinline-java-perl Binary: libinline-java-perl Architecture: source Version: 0.56-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Peter Pentchev r...@ringlet.net Description: libinline-java-perl - write Perl classes in Java Closes: 770762 770844 770845 Changes: libinline-java-perl (0.56-1) unstable; urgency=medium . * Team upload. . [ gregor herrmann ] * Imported Upstream version 0.55 * Add git URL to Source field in debian/copyright. * Update build and runtime dependencies. The new release needs libinline-perl (= 0.68) and libinline-c-perl. . [ Peter Pentchev ] * Depend unconditionally on default-jdk, as per the Debian policy for Java section 2.2. Closes: #770762 * Remove some autogenerated files to allow the package to build twice in a row. Closes: #770844 * Set LC_NUMERIC=C when running the tests since some of them assume that the decimal point separator is a period. Closes: #770845 * Depend on debhelper 8 to appease Lintian. * Bump Standards-Version to 3.9.6 with no changes. * Improve the package's long description. * Add the 01-typos patch to fix the manual pages. * Switch to the cgit frontend for Vcs-Browser. * New upstream release. Checksums-Sha1: e59b5a0abf240dac165bb30c1f19e7fd3b6a25bd 2252 libinline-java-perl_0.56-1.dsc cca9a0ce7782362dd6bc95d8641e26889c67bb2e 95398 libinline-java-perl_0.56.orig.tar.gz b640508b25adff9acbb6ff990de98d8933991101 6760 libinline-java-perl_0.56-1.debian.tar.xz Checksums-Sha256: f2f9ebf48bcbad80d563b009acad40b5603c69f0fbcce8df39beb9aa1203367b 2252 libinline-java-perl_0.56-1.dsc 2775d817453c61e7f2f6feebe7c19995821546db5ce2f5485ff1ebeafe2751b3 95398 libinline-java-perl_0.56.orig.tar.gz c246929f58354c4948c29afd3073c93e9d9f0d9fd3cfa2c79173ee331dc12c0c 6760 libinline-java-perl_0.56-1.debian.tar.xz Files: 4ac214573869a4ca08b2537c653d4244 2252 perl optional libinline-java-perl_0.56-1.dsc
Bug#770845: marked as done ([libinline-java-perl] FTBFS: Assumes a decimal point during the tests)
Your message dated Wed, 26 Nov 2014 17:49:10 + with message-id e1xtgie-00021w...@franck.debian.org and subject line Bug#770845: fixed in libinline-java-perl 0.56-1 has caused the Debian Bug report #770845, regarding [libinline-java-perl] FTBFS: Assumes a decimal point during the tests 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.) -- 770845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libinline-java-perl Severity: serious Tags: patch The test suite of the libinline-java-perl package seems to assume that the decimal point separator is a dot. This fails if the package is built with e.g. LANG=bg_BG.UTF-8 and without an appropriate LC_NUMERIC setting. Attached is a patch that runs the test suite with LC_NUMERIC=C. If there are no objections, I intend to commit it to the pkg-perl Git repository later today. G'luck, Peter -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash From 0ea2fa36fd43c5df0e3815dfa42dfa72b4934f30 Mon Sep 17 00:00:00 2001 From: Peter Pentchev r...@ringlet.net Date: Mon, 24 Nov 2014 17:29:30 +0200 Subject: [PATCH 2/3] Use the C locale's decimal point for the tests. --- debian/rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules b/debian/rules index d21dac9..22b091b 100755 --- a/debian/rules +++ b/debian/rules @@ -43,6 +43,9 @@ export JAVA_HOME=/usr/lib/jvm/default-java # Have testsuite use JNI export PERL_INLINE_JAVA_JNI=1 +# Have testsuite use the C locale's decimal point +DEB_MAKE_CHECK_TARGET += LC_NUMERIC=C + binary-post-install/$(pkg):: chrpath -d $(cdbs_curdestdir)$(perlpath)/auto/Inline/Java/JNI/JNI.so -- 2.1.3 signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: libinline-java-perl Source-Version: 0.56-1 We believe that the bug you reported is fixed in the latest version of libinline-java-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev r...@ringlet.net (supplier of updated libinline-java-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Nov 2014 12:31:04 +0200 Source: libinline-java-perl Binary: libinline-java-perl Architecture: source Version: 0.56-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Peter Pentchev r...@ringlet.net Description: libinline-java-perl - write Perl classes in Java Closes: 770762 770844 770845 Changes: libinline-java-perl (0.56-1) unstable; urgency=medium . * Team upload. . [ gregor herrmann ] * Imported Upstream version 0.55 * Add git URL to Source field in debian/copyright. * Update build and runtime dependencies. The new release needs libinline-perl (= 0.68) and libinline-c-perl. . [ Peter Pentchev ] * Depend unconditionally on default-jdk, as per the Debian policy for Java section 2.2. Closes: #770762 * Remove some autogenerated files to allow the package to build twice in a row. Closes: #770844 * Set LC_NUMERIC=C when running the tests since some of them assume that the decimal point separator is a period. Closes: #770845 * Depend on debhelper 8 to appease Lintian. * Bump Standards-Version to 3.9.6 with no changes. * Improve the package's long description. * Add the 01-typos patch to fix the manual pages. * Switch to the cgit frontend for Vcs-Browser. * New upstream release. Checksums-Sha1: e59b5a0abf240dac165bb30c1f19e7fd3b6a25bd 2252 libinline-java-perl_0.56-1.dsc cca9a0ce7782362dd6bc95d8641e26889c67bb2e 95398 libinline-java-perl_0.56.orig.tar.gz b640508b25adff9acbb6ff990de98d8933991101 6760 libinline-java-perl_0.56-1.debian.tar.xz Checksums-Sha256:
Processed: i can reproduce the problem now
Processing control commands: tags 750521 - unreproducible moreinfo Bug #750521 [scim-gtk-immodule] scim-gtk-immodule breaks pinentry-gtk2 and impairs gnome-keyring Removed tag(s) unreproducible and moreinfo. -- 750521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750521 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#750521: i can reproduce the problem now
Control: tags 750521 - unreproducible moreinfo Thanks for doing all the diagnostics, Ximin! I'm able to reproduce #750521 now, but i'm not sure it belongs specifically to scim-gtk-immodule. I think i'm able to reproduce the problem (no keyboard input accepted in pinentry-gtk-2) from a minimal gnome setup with just: apt install im-module scim --no-recommends and then log out and log back in. This results in 4 processes running in the session (2×scim-launcher, scim-helper-manager, scim-panel-gtk) -- when i kill those processes off, my gnome-terminal also dies, but then subsequent invocations of echo GETPIN | pinentry-gtk-2 work as expected. --dkg signature.asc Description: PGP signature
Bug#770844: marked as done ([libinline-java-perl] FTBFS twice in a row)
Your message dated Wed, 26 Nov 2014 17:49:10 + with message-id e1xtgie-00021q...@franck.debian.org and subject line Bug#770844: fixed in libinline-java-perl 0.56-1 has caused the Debian Bug report #770844, regarding [libinline-java-perl] FTBFS twice in a row 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.) -- 770844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libinline-java-perl Severity: serious Tags: patch The libinline-java-perl package fails to build twice in a row because the build system leaves several files lying around the source tree; dpkg-source is not happy with that. The attached patch adds a debian/clean file listing three files that should hopefully take care of this problem. I will commit this patch to the pkg-perl repository later today. G'luck, Peter -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash From c9fdcaf9b46cc18b92cd85433e84b3f2b34eb00c Mon Sep 17 00:00:00 2001 From: Peter Pentchev r...@ringlet.net Date: Mon, 24 Nov 2014 17:17:27 +0200 Subject: [PATCH 1/3] Remove some files to allow building twice in a row. --- debian/clean | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 debian/clean diff --git a/debian/clean b/debian/clean new file mode 100644 index 000..050f578 --- /dev/null +++ b/debian/clean @@ -0,0 +1,3 @@ +Makefile.old +Java/Makefile.old +t/t13.txt -- 2.1.3 signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: libinline-java-perl Source-Version: 0.56-1 We believe that the bug you reported is fixed in the latest version of libinline-java-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev r...@ringlet.net (supplier of updated libinline-java-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Nov 2014 12:31:04 +0200 Source: libinline-java-perl Binary: libinline-java-perl Architecture: source Version: 0.56-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Peter Pentchev r...@ringlet.net Description: libinline-java-perl - write Perl classes in Java Closes: 770762 770844 770845 Changes: libinline-java-perl (0.56-1) unstable; urgency=medium . * Team upload. . [ gregor herrmann ] * Imported Upstream version 0.55 * Add git URL to Source field in debian/copyright. * Update build and runtime dependencies. The new release needs libinline-perl (= 0.68) and libinline-c-perl. . [ Peter Pentchev ] * Depend unconditionally on default-jdk, as per the Debian policy for Java section 2.2. Closes: #770762 * Remove some autogenerated files to allow the package to build twice in a row. Closes: #770844 * Set LC_NUMERIC=C when running the tests since some of them assume that the decimal point separator is a period. Closes: #770845 * Depend on debhelper 8 to appease Lintian. * Bump Standards-Version to 3.9.6 with no changes. * Improve the package's long description. * Add the 01-typos patch to fix the manual pages. * Switch to the cgit frontend for Vcs-Browser. * New upstream release. Checksums-Sha1: e59b5a0abf240dac165bb30c1f19e7fd3b6a25bd 2252 libinline-java-perl_0.56-1.dsc cca9a0ce7782362dd6bc95d8641e26889c67bb2e 95398 libinline-java-perl_0.56.orig.tar.gz b640508b25adff9acbb6ff990de98d8933991101 6760 libinline-java-perl_0.56-1.debian.tar.xz Checksums-Sha256: f2f9ebf48bcbad80d563b009acad40b5603c69f0fbcce8df39beb9aa1203367b 2252 libinline-java-perl_0.56-1.dsc 2775d817453c61e7f2f6feebe7c19995821546db5ce2f5485ff1ebeafe2751b3 95398 libinline-java-perl_0.56.orig.tar.gz c246929f58354c4948c29afd3073c93e9d9f0d9fd3cfa2c79173ee331dc12c0c 6760
Processed: bug 770133 is forwarded to https://github.com/insanum/gcalcli/issues/153, tagging 770133
Processing commands for cont...@bugs.debian.org: forwarded 770133 https://github.com/insanum/gcalcli/issues/153 Bug #770133 [gcalcli] gcalcli 2.x is no longer compatible with google's api Set Bug forwarded-to-address to 'https://github.com/insanum/gcalcli/issues/153'. tags 770133 + fixed-upstream Bug #770133 [gcalcli] gcalcli 2.x is no longer compatible with google's api Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 770133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770133 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#750521: i can reproduce the problem now
On Wed 2014-11-26 12:49:47 -0500, Daniel Kahn Gillmor wrote: I think i'm able to reproduce the problem (no keyboard input accepted in pinentry-gtk-2) from a minimal gnome setup with just: apt install im-module scim --no-recommends Sorry, this should have been: apt install im-config scim --no-recommends hopefully i've got it right now :P --dkg signature.asc Description: PGP signature
Bug#635711: [monkeysphere] Bug#635711: further analysis of monkeysphere.postinst failures
On Tue, Nov 25, 2014 at 04:05:37PM -0500, Daniel Kahn Gillmor wrote: gpg_sphere is a shell function but according to the set -x it isn't even getting invoked before the SIGPIPE hits. No? + printf '%s:6:\n' 473F86D46E0B3CA0611450A8C9A7E0FFD1CD8FDC + gpg_sphere --import-ownertrust + RET=141 If, for some reason, su_monkeysphere_user (called by gpg_sphere) asked for a password instead of quietly changing to the monkeysphere user, you would get this SIGPIPE. I don't know why that would happen though. export GNUPGHOME=$(pwd) for x in 5 6 5 6 5 6 5 6 5 6 5 6; do printf %s:$x:\n $FPR | gpg --import-ownertrust 21 | log verbose done -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 770194
Processing commands for cont...@bugs.debian.org: # but no idea about it tags 770194 + confirmed Bug #770194 [src:ruby-stringex] ruby-stringex: FTBFS: Test failures Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 770194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770194 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#770352: marked as done (gcc-3.3: FTBFS: GCC_TARGET value is not a valid Debian architecture)
Your message dated Wed, 26 Nov 2014 18:48:57 + with message-id e1xthe5-ou...@franck.debian.org and subject line Bug#770352: fixed in gcc-3.3 1:3.3.6ds1-27.2 has caused the Debian Bug report #770352, regarding gcc-3.3: FTBFS: GCC_TARGET value is not a valid Debian architecture to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gcc-3.3 Version: 1:3.3.6ds1-27.1 Severity: serious From my pbuilder build log (on amd64): ... I: Running cd tmp/buildd/*/ env PATH=/usr/sbin:/usr/bin:/sbin:/bin dpkg-buildpackage -us -uc -rfakeroot dpkg-buildpackage: source package gcc-3.3 dpkg-buildpackage: source version 1:3.3.6ds1-27.1 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Eric Dorland e...@debian.org dpkg-buildpackage: host architecture amd64 dpkg-source --before-build gcc-3.3-3.3.6ds1 fakeroot debian/rules clean debian/rules.defs:58: *** GCC_TARGET value is not a valid Debian architecture. Stop. dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: gcc-3.3 Source-Version: 1:3.3.6ds1-27.2 We believe that the bug you reported is fixed in the latest version of gcc-3.3, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon Richter s...@debian.org (supplier of updated gcc-3.3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 23 Nov 2014 18:58:06 +0100 Source: gcc-3.3 Binary: libstdc++5 Architecture: source amd64 Version: 1:3.3.6ds1-27.2 Distribution: unstable Urgency: medium Maintainer: Philipp Kern pk...@debian.org Changed-By: Simon Richter s...@debian.org Description: libstdc++5 - The GNU Standard C++ Library v3 Closes: 770352 Changes: gcc-3.3 (1:3.3.6ds1-27.2) unstable; urgency=medium . * Non-maintainer upload. * Use a nonempty default target architecture as dpkg-architecture no longer supports -a without argument. (Closes: #770352) Checksums-Sha1: cff8fad82b607d9d4c05e324a4fc775b706be219 2000 gcc-3.3_3.3.6ds1-27.2.dsc b88a3d16251ecd67a8dcbd88065ea1e9cb923834 372086 gcc-3.3_3.3.6ds1-27.2.diff.gz fde1f232aeed3db414af578c94cbb3251b5e4503 251634 libstdc++5_3.3.6-27.2_amd64.deb Checksums-Sha256: de47b36c0ae55f82210172c1ce5ef61381fa13890feb8fde25d8bb5c06540d63 2000 gcc-3.3_3.3.6ds1-27.2.dsc 34f6cd6064f85082b1afc6327854cfcb9f4d758c3ce83f4fc80a6fac69e08fba 372086 gcc-3.3_3.3.6ds1-27.2.diff.gz 49d1c39f417269859070b5bc98d1ce7177abf9a9f2ed26718cc9cbc5f7f3b70d 251634 libstdc++5_3.3.6-27.2_amd64.deb Files: b87b1bac7f1fed5df97d2842bde7f7fb 2000 devel optional gcc-3.3_3.3.6ds1-27.2.dsc 936c5ee9bdc4556ca1e270ba3e25c0eb 372086 devel optional gcc-3.3_3.3.6ds1-27.2.diff.gz 4e83a2b69272d4a019be331634fbc5c7 251634 libs optional libstdc++5_3.3.6-27.2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iJwEAQECAAYFAlRyJscACgkQ0sfeulffv7sYSgP+OOlkS6zqdHe8CC2Zigtezqg/ Z833Bz+ecnPeSJeiw84oGtFcZkBVCKsKSJJA3hMt2cNkgPpZmDAwOMxJLSBuicbY hwoBlxrys5JD1psdGMhterjtpt93wbM4J50kgaQsJWHNPcmorplWqY2AZ6g0erOZ pstfqI9baeuasT4A068= =QCD+ -END PGP SIGNATUREEnd Message---
Bug#771100: dependency not scrict enough: libgpg-error.so.0: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20)
Package: libgcrypt20 Version: 1.6.2-4 Severity: serious During a wheezy to jessie dist-upgrade I get dozens if not hundreds of the following messages: systemctl: /lib/x86_64-linux-gnu/libgpg-error.so.0: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20 libgcrypt20 has a versioned dependency on libgpg-error0 (= 1.10) which is satisfied by the version from wheezy. And indeed, while the dist-upgrade is runnig, I have the following state: libgpg-error0: Installiert: 1.10-3.1 Installationskandidat: 1.17-2 Versionstabelle: 1.17-2 0 500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages *** 1.10-3.1 0 500 http://ftp.de.debian.org/debian/ wheezy/main amd64 Packages 100 /var/lib/dpkg/status libgcrypt20: Installiert: 1.6.2-4 Installationskandidat: 1.6.2-4 Versionstabelle: *** 1.6.2-4 0 500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status I assume, once the dist-upgrade has completed successfully, the error message would go away. That said, it looks like libgcrypt20 should have a stricter versioned dependency on libgpg-error0 so this error does not show up during a dist-upgrade. (a full log from the dist-upgrade is attached) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgcrypt20:amd64 depends on: ii libc6 2.19-13 ii libgpg-error0 1.17-2 ii multiarch-support 2.19-13 libgcrypt20:amd64 recommends no packages. Versions of packages libgcrypt20:amd64 suggests: pn rng-tools none -- no debconf information Script started on Wed Nov 26 19:35:32 2014 root@debian:~# apt-get ids dist-upgrade -y Reading package lists... 0% Reading package lists... 100% Reading package lists... Done Building dependency tree... 0% Building dependency tree... 0% Building dependency tree... 50% Building dependency tree... 50% Building dependency tree Reading state information... 0% Reading state information... 0% Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: foomatic-filters ghostscript-cups libaudit0 libcupsdriver1 libescpr1 libperl5.14 libsnmp15 virtualbox-guest-x11 virtualbox-ose-guest-x11 xserver-xorg-core The following NEW packages will be installed: cgmanager colord-data cpp-4.9 crda cups-browsed cups-core-drivers cups-daemon cups-filters-core-drivers cups-server-common dconf-gsettings-backend dconf-service dh-python docutils-common docutils-doc emacsen-common ethtool firmware-linux-free fonts-dejavu-core gcc-4.9 gcc-4.9-base gnupg-agent gnupg2 init init-system-helpers iproute2 irqbalance iw libalgorithm-c3-perl libarchive-extract-perl libasan1 libasn1-8-heimdal libasound2-data libassuan0 libatm1 libatomic1 libaudit-common libaudit1 libauthen-sasl-perl libavahi-glib1 libbind9-90 libboost-iostreams1.55.0 libcap2-bin libcgi-fast-perl libcgi-pm-perl libcgmanager0 libcilkrts5 libclass-c3-perl libclass-c3-xs-perl libcloog-isl4 libcolord2 libcolorhug2 libcpan-meta-perl libcurl3-gnutls libdata-optlist-perl libdata-section-perl libdb5.3 libdconf1 libdebconfclient0 libdns-export100 libdns100 libdrm-nouveau2 libegl1-mesa libegl1-mesa-drivers libelf1 libepoxy0 libestr0 libfakeroot libfcgi-perl libffi6 libfontembed1 libgbm1 libgcc-4.9-dev libgcrypt20 libgd3 libgl1-mesa-glx libglapi-mesa libgnutls-deb0-28 libgnutls-openssl27 libgphoto2-6 libgphoto2-port10 libgraphite2-3 libgssapi3-heimdal libharfbuzz0b libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhogweed2 libhx509-5-heimdal libicu52 libintl-perl libio-html-perl libirs-export91 libisc-export95 libisc95 libisccc90 libisccfg-export90 libisccfg90 libisl10 libjim0.75 libjpeg62-turbo libjpeg9 libjson-c2 libkrb5-26-heimdal libksba8 liblcms2-utils libldb1 libllvm3.5 liblog-message-perl liblog-message-simple-perl liblogging-stdlog0 liblognorm1 liblsan0 liblwres90 libmodule-build-perl libmodule-pluggable-perl libmodule-signature-perl libmpc3 libmpdec2 libmro-compat-perl libnet-smtp-ssl-perl libnettle4 libnih-dbus1 libnih1 libntdb1 libnuma1 libopenjpeg5 libopenvg1-mesa libpackage-constants-perl libpam-cap libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpangox-1.0-0 libpangoxft-1.0-0 libparams-util-perl libperl4-corelibs-perl libperl5.20 libpod-latex-perl libpod-readme-perl libpoppler46 libprocps3 libpsl0 libpython-stdlib libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3-stdlib libpython3.4-minimal libpython3.4-stdlib libqpdf13 libregexp-common-perl libroken18-heimdal librtmp1 libsasl2-modules-db libsigsegv2 libsmartcols1
Bug#768673: NMU patch
Hi,
I attach my NMU debdiff that fixes this issue.
Feel free to change the changelog and upload it
in a standard way.
Cheers,
Tomasz
diff -Nru ruby-httpclient-2.3.3/debian/changelog ruby-httpclient-2.3.3/debian/changelog
--- ruby-httpclient-2.3.3/debian/changelog 2014-06-27 03:03:36.0 +0200
+++ ruby-httpclient-2.3.3/debian/changelog 2014-11-26 12:00:23.0 +0100
@@ -1,3 +1,10 @@
+ruby-httpclient (2.3.3-3.1) testing; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix default SSL configuration (Closes: #768673)
+
+ -- Tomasz Buchert tomasz.buch...@inria.fr Wed, 26 Nov 2014 18:59:26 +0100
+
ruby-httpclient (2.3.3-3) unstable; urgency=medium
* fix-port-allocation-in-tests.patch: fix port allocation for servers
diff -Nru ruby-httpclient-2.3.3/debian/patches/0003-fix-ssl-config.patch ruby-httpclient-2.3.3/debian/patches/0003-fix-ssl-config.patch
--- ruby-httpclient-2.3.3/debian/patches/0003-fix-ssl-config.patch 1970-01-01 01:00:00.0 +0100
+++ ruby-httpclient-2.3.3/debian/patches/0003-fix-ssl-config.patch 2014-11-26 11:57:16.0 +0100
@@ -0,0 +1,64 @@
+Description: Change default SSL configuration
+ The POODLE attack (https://en.wikipedia.org/wiki/POODLE) deprecated the use
+ of SSLv3 protocol. We change the default configuration to autodetection
+ and try to explicitly disable SSLv2 and SSLv3, preferring TLS protocol suites
+ instead.
+ This patch is a minimal adaptation of a commit in the project's upstream:
+ https://github.com/nahi/httpclient/commit/90d5c791c941c72521784dc4ea8eed60987800da
+
+--- a/lib/httpclient/ssl_config.rb
b/lib/httpclient/ssl_config.rb
+@@ -34,7 +34,13 @@
+ class SSLConfig
+ include OpenSSL if SSLEnabled
+
+-# String name of OpenSSL's SSL version method name: SSLv2, SSLv23 or SSLv3
++# Which TLS protocol version (also called method) will be used. Defaults
++# to :auto which means that OpenSSL decides (In my tests this resulted
++# with always the highest available protocol being used).
++# String name of OpenSSL's SSL version method name: TLSv1_2, TLSv1_1, TLSv1,
++# SSLv2, SSLv23, SSLv3 or :auto (and nil) to allow version negotiation (default).
++# See {OpenSSL::SSL::SSLContext::METHODS} for a list of available versions
++# in your specific Ruby environment.
+ attr_reader :ssl_version
+ # OpenSSL::X509::Certificate:: certificate for SSL client authenticateion.
+ # nil by default. (no client authenticateion)
+@@ -83,8 +89,13 @@
+ @verify_callback = nil
+ @dest = nil
+ @timeout = nil
+- @ssl_version = SSLv3
+- @options = defined?(SSL::OP_ALL) ? SSL::OP_ALL | SSL::OP_NO_SSLv2 : nil
++ @ssl_version = :auto
++ # Follow ruby-ossl's definition
++ @options = OpenSSL::SSL::OP_ALL
++ @options = ~OpenSSL::SSL::OP_DONT_INSERT_EMPTY_FRAGMENTS if defined?(OpenSSL::SSL::OP_DONT_INSERT_EMPTY_FRAGMENTS)
++ @options |= OpenSSL::SSL::OP_NO_COMPRESSION if defined?(OpenSSL::SSL::OP_NO_COMPRESSION)
++ @options |= OpenSSL::SSL::OP_NO_SSLv2 if defined?(OpenSSL::SSL::OP_NO_SSLv2)
++ @options |= OpenSSL::SSL::OP_NO_SSLv3 if defined?(OpenSSL::SSL::OP_NO_SSLv3)
+ # OpenSSL 0.9.8 default: ALL:!ADH:!LOW:!EXP:!MD5:+SSLv2:@STRENGTH
+ @ciphers = ALL:!aNULL:!eNULL:!SSLv2 # OpenSSL 1.0.0 default
+ @cacerts_loaded = false
+@@ -283,7 +294,7 @@
+ ctx.timeout = @timeout
+ ctx.options = @options
+ ctx.ciphers = @ciphers
+- ctx.ssl_version = @ssl_version
++ ctx.ssl_version = @ssl_version unless @ssl_version == :auto
+ end
+
+ # post connection check proc for ruby 1.8.5.
+--- a/test/test_ssl.rb
b/test/test_ssl.rb
+@@ -33,7 +33,10 @@
+ assert_equal(OpenSSL::SSL::VERIFY_PEER | OpenSSL::SSL::VERIFY_FAIL_IF_NO_PEER_CERT, cfg.verify_mode)
+ assert_nil(cfg.verify_callback)
+ assert_nil(cfg.timeout)
+-assert_equal(OpenSSL::SSL::OP_ALL | OpenSSL::SSL::OP_NO_SSLv2, cfg.options)
++expected_options = OpenSSL::SSL::OP_ALL | OpenSSL::SSL::OP_NO_SSLv2 | OpenSSL::SSL::OP_NO_SSLv3
++expected_options = ~OpenSSL::SSL::OP_DONT_INSERT_EMPTY_FRAGMENTS if defined?(OpenSSL::SSL::OP_DONT_INSERT_EMPTY_FRAGMENTS)
++expected_options |= OpenSSL::SSL::OP_NO_COMPRESSION if defined?(OpenSSL::SSL::OP_NO_COMPRESSION)
++assert_equal(expected_options, cfg.options)
+ assert_equal(ALL:!aNULL:!eNULL:!SSLv2, cfg.ciphers)
+ assert_instance_of(OpenSSL::X509::Store, cfg.cert_store)
+ end
diff -Nru ruby-httpclient-2.3.3/debian/patches/series ruby-httpclient-2.3.3/debian/patches/series
--- ruby-httpclient-2.3.3/debian/patches/series 2014-06-27 00:41:13.0 +0200
+++ ruby-httpclient-2.3.3/debian/patches/series 2014-11-26 11:49:41.0 +0100
@@ -1,2 +1,3 @@
0001-Remove-Hash-element-order-dependency.patch
fix-port-allocation-in-tests.patch
+0003-fix-ssl-config.patch
Bug#769264: marked as done (freebirth: FTBFS in jessie/i386: XXX)
Your message dated Wed, 26 Nov 2014 19:03:50 + with message-id e1xthsu-0002tl...@franck.debian.org and subject line Bug#769264: fixed in freebirth 0.3.2-9.1 has caused the Debian Bug report #769264, regarding freebirth: FTBFS in jessie/i386: XXX 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.) -- 769264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: freebirth Version: 0.3.2-8 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141112 qa-ftbfs Justification: FTBFS in jessie on i386 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): make[1]: Entering directory '/«PKGBUILDDIR»' gcc -MM -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 oscillator.c sequencer.c envelope.c filter.c gtkdial.c mixer.c raw_wave.c event.c sample_producer.c blender.c delay.c reverb.c all_pass.c delay_panel.c reverb_panel.c multi_tap_delay.c sample_freq_strip.c Makefile.deps gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o freebirth.o freebirth.c gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o oscillator.o oscillator.c gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o sequencer.o sequencer.c gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o envelope.o envelope.c gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -O2 -c -o filter.o filter.c filter.c: In function 'filter_init_lookup_table': filter.c:101:28: warning: variable 'table_length' set but not used [-Wunused-but-set-variable] int freq_range, q_range, table_length; ^ gcc -g -Wall -pthread -I/usr/include/gtk-2.0 -I/usr/lib/i386-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0
Processed: found 771071 in 2.4.17+caldav~beta10-7
Processing commands for cont...@bugs.debian.org: found 771071 2.4.17+caldav~beta10-7 Bug #771071 [cyrus-imapd-2.4] [cyrus-imapd-2.4] Missing separator breaks configure parameters Marked as found in versions cyrus-imapd-2.4/2.4.17+caldav~beta10-7. thanks Stopping processing here. Please contact me if you need assistance. -- 771071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771071 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#768112: fixed in slurm-llnl 14.03.9-4
Control: tags -1 + jessie-ignore On Sat, 2014-11-08 at 16:24 +0100, Mehdi Dogguy wrote: Le 2014-11-08 10:53, Adam D. Barratt a écrit : Control: reopen -1 On 2014-11-06 10:21, Gennaro Oliva wrote: Source: slurm-llnl Source-Version: 14.03.9-4 We believe that the bug you reported is fixed in the latest version of slurm-llnl, which is due to be installed in the Debian FTP archive. [...] slurm-llnl (14.03.9-4) unstable; urgency=medium . * Declaring slurm-client conflict with sinfo (Closes: #768112) No. Please re-read policy (specifically 10.1) - you don't get to conflict with other packages just because you both want to use the same file path. I think that Gennaro fixed it that way because we were aware of this issue (which is here since before Lenny, fwiw) and we agreed with Gaudenz (sinfo's co-maintainer) to find a real solution to implement in Jessie+1. [...] So, is it acceptable to keep this workaround for Jessie and work on a better one for Jessie+1? That way, we hope to find time enough time to work this in coordination with both upstreams. I'm not sure acceptable is really the right word, and I've argued with myself a bunch over this, particularly given that sinfo+slurm-llnl is basically a closed set for dependency purposes, with a combined popcon of ~100. However, before I change my mind yet again, I'm willing to give this a one-time explicit waiver. This is on the assumption both that slurm-llnl 14.03.9-5 remains releasable for jessie and that this issue really is fixed for stretch in a sane and policy-compliant way, the earlier in the cycle the better. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#768112: fixed in slurm-llnl 14.03.9-4
Processing control commands: tags -1 + jessie-ignore Bug #768112 [slurm-client] slurm-client: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/sinfo Added tag(s) jessie-ignore. -- 768112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768112 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#770900: monkeysign: 'MonkeysignScan' object has no attribute 'dialog'
On 11/25/2014 10:44 PM, Antoine Beaupré wrote: It seems you have stumbled upon a dusty path in the GTK UI that is neither unit tested or often used by graphical users. I believe you may be attempting to sign a key that is already in your local keyring, which is freaking out some handler. Could you try the attached crude patch and see if it fixes the problem for you? yes, your patch avoids the backtrace. monkeyscan still seems stuck in an odd state to me, though: The monkeyscan main window freezes and an strace reveals that the process is stuck in a futex() call. So i don't think this is resolved for me. Is there some way i can debug it further? --dkg signature.asc Description: OpenPGP digital signature
Bug#771102: upstream license violation
Package: abduco Version: 0.1-2 Severity: serious Justification: Policy 2.3 Hi, abduco is derived from dtach, which is licensed under GPLv2. However, abduco is licensed under ISC with dtach's copyright notices removed. While abduco may be considered a rewrite of dtach that just has similar looking portions of code left in it, http://digital-law-online.info/lpdi1.0/treatise27.html says that: Many people have reimplemented computer programs by rewriting them to replace the source code with code of their own writing. There is no reason to believe that this would not be a copyright infringement, particularly if the reimplementer had access to the source code of the original program, even if none of the original source code remains. abduco should not be a part of Debian if it is violating dtach's copyright and license. -- Ned T. Crigler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766349: Diagnosing S/MIME issues.
Even if you can't set up a test environment could you forward (as an attachment) one your failed test emails? I'd really like to look more closely at the message structure. Diane On Monday, November 24, 2014 10:29:02 Diane Trout wrote: Could you try setting up a test environment? So far I haven't figured out how to duplicate it, and the bug is currently blocking the release of jessie. Diane On Monday, November 24, 2014 08:15:51 Jörg Frings-Fürst wrote: Hello Diane, first sorry for my late answer. During some other problems we have banned kmail2. But I can setup a virtual guest system with our last config this evening. I hope that's ok . CU Jörg Am Donnerstag, den 20.11.2014, 14:43 -0800 schrieb Diane Trout: Hello I was reviewing bugs for Jessie and saw your issue and had a few ideas to check. [...] smime.p7s Description: S/MIME cryptographic signature
Bug#770222: marked as done (icecast2: CVE-2014-9018: on-connect scripts: icecast can leak output to attentive sources)
Your message dated Wed, 26 Nov 2014 19:34:25 + with message-id e1xtim5-0006tq...@franck.debian.org and subject line Bug#770222: fixed in icecast2 2.4.0-1.1 has caused the Debian Bug report #770222, regarding icecast2: CVE-2014-9018: on-connect scripts: icecast can leak output to attentive sources 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.) -- 770222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: icecast2 Version: 2.4.0-1~bpo70+1 Severity: critical Tags: security upstream Justification: root security hole Icecast can leak the output of on-connect scripts to source clients by sending their output via HTTP. This information-disclosure can contain confidential information if the administrator of the icecast server did not explicitly check the output of their scripts. Information contained can include passwords or script interna helping to possibly exploit weak scripts. This bug has been reported upstream [1] which fixed it quickly in the bugfix release 2.4.1 [2]. Please consider upgrading to the latest upstream version. [1] https://trac.xiph.org/ticket/2089 [2] http://icecast.org/news/icecast-release-2_4_1/ -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.41-042stab094.7 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icecast2 depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38+deb7u6 ii libcurl3-gnutls7.26.0-1+wheezy11 ii libogg01.3.0-4 ii libspeex1 1.2~rc1-7 ii libtheora0 1.1.1+dfsg.1-3.1 ii libvorbis0a1.3.2-1.3 ii libxml22.8.0+dfsg1-7+wheezy2 ii libxslt1.1 1.1.26-14.1 icecast2 recommends no packages. Versions of packages icecast2 suggests: pn ices2 none -- Configuration Files: /etc/default/icecast2 changed [not included] /etc/icecast2/icecast.xml [Errno 13] Keine Berechtigung: u'/etc/icecast2/icecast.xml' -- debconf information excluded ---End Message--- ---BeginMessage--- Source: icecast2 Source-Version: 2.4.0-1.1 We believe that the bug you reported is fixed in the latest version of icecast2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 770...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon Richter s...@debian.org (supplier of updated icecast2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 23 Nov 2014 20:02:58 +0100 Source: icecast2 Binary: icecast2 Architecture: source amd64 Version: 2.4.0-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Simon Richter s...@debian.org Description: icecast2 - streaming media server Closes: 770222 Changes: icecast2 (2.4.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Include patchset 19313 (close file handles for external scripts). (Closes: #770222) Checksums-Sha1: f07815e8f3a5e224586a07682b810175b6b4b8a0 1795 icecast2_2.4.0-1.1.dsc 4afe6209220fcbde5299dd9988987ce016eeb9d7 29244 icecast2_2.4.0-1.1.debian.tar.xz 32ca9d8e32f9acde56950d2c49550c322e219d0b 277488 icecast2_2.4.0-1.1_amd64.deb Checksums-Sha256: 149ac55f0b9f687f8c7745b7441b4c6f264407a41b6493e884ac1fbc2b97648b 1795 icecast2_2.4.0-1.1.dsc 92d4df3614f535ab765954602c95318b680979051dda8b88b86c0f07d5fe6cf9 29244 icecast2_2.4.0-1.1.debian.tar.xz 4db127a84a19aaf48ace2604e529613e6d7e03b537adb129dff395c42d8ac697 277488 icecast2_2.4.0-1.1_amd64.deb Files: ac0e53e427e89add56022d383dece46a 1795 sound optional icecast2_2.4.0-1.1.dsc 85bdb6502864cc6371854ee6ccf27da1 29244 sound optional icecast2_2.4.0-1.1.debian.tar.xz f0bb99682fa75d1fc9511f4e382cf2ef 277488 sound optional icecast2_2.4.0-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iJwEAQECAAYFAlRyMQ8ACgkQ0sfeulffv7v3PQP/X2MDVYx6lr7oooJvtMK+iB92
Bug#767504: [Pkg-mpd-maintainers] Bug#767504: mpd: licence clash with libmp4v2 (MPL) and mpd GPL-+2
On 2014/11/02 21:16, Max Kellermann m...@duempel.org wrote: This copyright problem must be resolved by a license change of libmp4v2. If no solution appears possible on their side, the plugin will be removed from the next MPD release. The plugin has been removed from MPD 0.19.5, because no solution was in sight. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771104: [wine] wine is no more usable
Package: wine Version: 1.6.2-16 Severity: grave --- Please enter the report below this line. --- Dear Maintainer, the current version of wine is not usable anymore. Starting any program with wine results in the output of error messages of the form Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. http://www.freetype.org . . . Wine cannot find the ncurses library (libncurses.so.5). Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. But all the packages mentioned in the error messages are installed: sudo aptitude search (?installed)freetype i A libfreetype6 - Schrift-Engine FreeType 2 - Laufzeitbibliothek i A libfreetype6-dev - Schrift-Prozessor FreeType 2, Entwicklungsdateien sudo aptitude search (?installed)libncurses i libncurses5 - Gemeinsam benutzte Bibliotheken für Terminalsteuerung i A libncurses5-dev - Ncurses-Bibliotheken für Entwickler i libncursesw5 - Bibliotheken für Terminalsteuerung (Unterstützung für Multibyte-Zeichen) Furthermore, wine used to work properly in a previous version, but I can't remember which version it was. Let me know if further information is required. Kind regards, Georgios --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Foreign Architectures: i386 Debian Release: jessie/sid 500 testing-updates ftp.de.debian.org 500 testing security.debian.org 500 testing ftp.de.debian.org 500 stable deb.opera.com 100 jessie-backports ftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766758: marked as pending
tag 766758 pending thanks Hello, Bug #766758 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=75a857d --- commit 75a857d79d3d3a5cb8367bbd49d5e89bb94af0a1 Author: Guillem Jover guil...@debian.org Date: Fri Nov 14 18:35:32 2014 +0100 libdpkg: Register all pending triggers for deferred processing Trigger processing on the deferred stage is just opportunistic, but we enqueue all currently pending triggers that might have been activated on a previous unpack run, only when being called as «dpkg --configure pkgname…». This is a mostly conformant workaround for frontends like apt that do not correctly call «dpkg --configure -a» or «dpkg --triggers-only -a» after their normal runs, and leave packages in triggers-pending and triggers-awaited states. Closes: #766758 diff --git a/debian/changelog b/debian/changelog index e58d88d..ba10d7e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -28,6 +28,11 @@ dpkg (1.17.22) UNRELEASED; urgency=low should only fail on the former but ignore the latter. Closes: #768852 * Do not ignore trigger cycles for direct dependencies, these are just normal trigger cycles, and as such should not be special cased. + * Register all pending triggers for deferred processing when being called +as «dpkg --configure pkgname…». This is a mostly conformant workaround +for frontends like apt that do not correctly call «dpkg --configure -a» +or «dpkg --triggers-only -a» after their normal runs, and leave packages +in triggers-pending and triggers-awaited states. Closes: #766758 [ Updated programs translations ] * German (Sven Joachim). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769211: marked as pending
tag 769211 pending thanks Hello, Bug #769211 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=b1c19bc --- commit b1c19bc87eb661f074e63a2aa5c8ac9e55e3fac4 Author: Guillem Jover guil...@debian.org Date: Wed Nov 12 10:17:08 2014 +0100 libdpkg, dpkg: Normalize tar entry uid and gid only in dpkg unpack The tar extractor should be independent from the current system, so that testing it can be made reproducible. Move the preference over the system user and group names to the actual dpkg unpack code. Regression introduced in commit f71e02c8e913884bfbf9d97b58ded4591b823cdb. Closes: #769211 diff --git a/debian/changelog b/debian/changelog index 322c954..2fa248f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -19,6 +19,8 @@ dpkg (1.17.22) UNRELEASED; urgency=low Regression introduced in dpkg 1.10. * Fix build on Mac OS X. Regression introduced in dpkg 1.17.11. Reported by Dominyk Tiller dominyktil...@gmail.com. + * Normalize tar entry uid and gid from the current system only in dpkg +unpack. Regression introduced in dpkg 1.17.14. Closes: #769211 [ Updated programs translations ] * German (Sven Joachim). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#768599 marked as pending
Processing commands for cont...@bugs.debian.org: tag 768599 pending Bug #768599 [dpkg] dpkg: Need to Break/Conflict packages switched to nonawaited trigger directives Bug #766006 [dpkg] dpkg: cycle found while processing triggers Bug #768867 [dpkg] wheezy-jessie: Sub-process /usr/bin/dpkg returned an error code (1) Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 766006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766006 768599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768599 768867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768599: marked as pending
tag 768599 pending thanks Hello, Bug #768599 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=b89caa7 --- commit b89caa796ac54ca86db33c6b06e72a122975bf0e Author: Guillem Jover guil...@debian.org Date: Wed Nov 19 21:49:08 2014 +0100 debian: Add Breaks on man-db, fontconfig and readahead-fedora The old versions of these packages produced trigger cycles as they were using awaiting trigger directives. Closes: #768599 diff --git a/debian/changelog b/debian/changelog index 473d243..e5f6955 100644 --- a/debian/changelog +++ b/debian/changelog @@ -8,6 +8,8 @@ dpkg (1.17.22) UNRELEASED; urgency=low compatibility symlinks under /usr/sbin/. There are still packages using those paths, but the relevant lintian check did not list any, so this got removed prematurely. + * Add Breaks on old man-db, fontconfig and readahead-fedora packages using +awaiting triggers, as they produce trigger cycles. Closes: #768599 [ Updated programs translations ] * German (Sven Joachim). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#769211 marked as pending
Processing commands for cont...@bugs.debian.org: tag 769211 pending Bug #769211 [src:dpkg] dpkg: FTBFS in jessie: tests failed Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 769211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769211 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: Bug#766758 marked as pending
Processing commands for cont...@bugs.debian.org: tag 766758 pending Bug #766758 [dpkg] dpkg: Needs to workaround apt not processing pending triggers Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 766758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766758 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#635711: [monkeysphere] Bug#635711: further analysis of monkeysphere.postinst failures
On 11/26/2014 01:19 PM, Clint Adams wrote: On Tue, Nov 25, 2014 at 04:05:37PM -0500, Daniel Kahn Gillmor wrote: gpg_sphere is a shell function but according to the set -x it isn't even getting invoked before the SIGPIPE hits. No? + printf '%s:6:\n' 473F86D46E0B3CA0611450A8C9A7E0FFD1CD8FDC + gpg_sphere --import-ownertrust + RET=141 this just tells us that bash wanted to invoke gpg_sphere, not that it actually did invoke it. Had it invoked it, we should see more set -x output messages, right? look further up the page for a previous invocation of gpg_sphere. I'd expect to see at least: + GNUPGHOME=/var/lib/monkeysphere/authentication/sphere + export GNUPGHOME ... If, for some reason, su_monkeysphere_user (called by gpg_sphere) asked for a password instead of quietly changing to the monkeysphere user, you would get this SIGPIPE. I don't know why that would happen though. Yep, i also don't know why that would happen :/ --dkg signature.asc Description: OpenPGP digital signature
Bug#770900: monkeysign: 'MonkeysignScan' object has no attribute 'dialog'
On 2014-11-26 14:21:02, Daniel Kahn Gillmor wrote: On 11/25/2014 10:44 PM, Antoine Beaupré wrote: It seems you have stumbled upon a dusty path in the GTK UI that is neither unit tested or often used by graphical users. I believe you may be attempting to sign a key that is already in your local keyring, which is freaking out some handler. Could you try the attached crude patch and see if it fixes the problem for you? yes, your patch avoids the backtrace. monkeyscan still seems stuck in an odd state to me, though: The monkeyscan main window freezes and an strace reveals that the process is stuck in a futex() call. So i don't think this is resolved for me. Is there some way i can debug it further? Did you try running with the --debug switch? a. -- Nothing in life is to be feared, it is only to be understood Now is the time to understand more, so that we may fear less. - Marie Curie signature.asc Description: PGP signature
Bug#770900: monkeysign: 'MonkeysignScan' object has no attribute 'dialog'
On 11/26/2014 04:15 PM, Antoine Beaupré wrote: On 2014-11-26 14:21:02, Daniel Kahn Gillmor wrote: The monkeyscan main window freezes and an strace reveals that the process is stuck in a futex() call. So i don't think this is resolved for me. Is there some way i can debug it further? Did you try running with the --debug switch? running with the --debug switch just shows me the command, return code, stdout, and stderr of the invocations of gpg. but gpg isn't running (it has already completed) by the time the dialog hangs on the futex() syscall and there are no child processes that i can see. Are you unable to reproduce this? --dkg signature.asc Description: OpenPGP digital signature
Bug#767671: marked as done (ekeyd: fails to remove: subprocess installed post-removal script returned error exit status 1)
Your message dated Wed, 26 Nov 2014 21:19:40 + with message-id e1xtjzw-0001xr...@franck.debian.org and subject line Bug#767671: fixed in ekeyd 1.1.5-6.1 has caused the Debian Bug report #767671, regarding ekeyd: fails to remove: subprocess installed post-removal script returned error exit status 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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 ---End Message--- ---BeginMessage--- Source: ekeyd Source-Version: 1.1.5-6.1 We believe that the bug you reported is fixed in the latest version of ekeyd, 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. gregor herrmann gre...@debian.org (supplier of updated ekeyd 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, 24 Nov 2014 21:46:45 +0100 Source: ekeyd Binary: ekeyd ekeyd-egd-linux Architecture: source Version: 1.1.5-6.1 Distribution: unstable Urgency: medium Maintainer: Simtec Electronics supp...@simtec.co.uk Changed-By: gregor herrmann gre...@debian.org Description: ekeyd - Simtec Electronics UDEKEY01 Entropy Key Daemon ekeyd-egd-linux - Transfers entropy from an EGD to the Linux kernel pool Closes: 767671 Changes: ekeyd (1.1.5-6.1) unstable; urgency=medium . * Non-maintainer upload. * Fix fails to remove: subprocess installed post-removal script returned error exit status 1: apply patch from Cameron Norman to ekeyd.postrm: use invoke-rc.d instead of calling udevcontrol and udevadm. (Closes: #767671) Checksums-Sha1: 9e53f7d2257b5f8b573f904fe1721323e82eb836 2080 ekeyd_1.1.5-6.1.dsc 9102ce06e8e1c3cbfe7b4d1588d7a4e326c5 8456 ekeyd_1.1.5-6.1.debian.tar.xz Checksums-Sha256: 2c568528ee935cb66f48b0071025ab24d00eba6b7738c2afcfa51ef96a46dffe 2080 ekeyd_1.1.5-6.1.dsc 84f83df46532b09dfac2ee1c4834da574ff7612c6fb605e8e43dfa0742f1b587 8456 ekeyd_1.1.5-6.1.debian.tar.xz Files: 91cdf62cd1114fd80c70d2e6ba91c527 2080 utils optional ekeyd_1.1.5-6.1.dsc eaf8fdadc16827246e9e9c075cee6c77 8456 utils optional ekeyd_1.1.5-6.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJUc5nRXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG5PgP/jMNQRR6u/ovMbciIKITiga6 xkUx87XJPhN5UnShEk6Y4JeHx3J65EiMDvj2qJ6HqfY7lcc4ee7E+EcKD+qKRNzt ZEh0rXvqT2DUxz4mc5y/GRkfixumuEjWnFxF8fNGFm/azsf4LopmFAvNO3RbWMZL oFpC1wtThBLsSProXIZLw4zw83T/22vTR4OqPdWhhXTFPECiw4r1szfDmLc+FG5P R8pWtYcPoYaBkOpjY8Ov5ra7MhUKOfFR4g2rliBaZ91rnVoI+ZJTyc4L/Xv8F82+ s9En5v/Uwl14cdL3mteLAq9iqnOgVKPnJQ2Rcbs4nqA3oA3cXI/NokYQkrtFx2MA fBChKeg2b/K2LlMjMUH6hTLItEHCC+wfIJDpvygfu3+ZgrYY3picAJpWDIK2jmr6 OvJl9B0xMG+K2MgrNM1AaNYgQENoVm0hY5rHAbOBzuhMQZgmTW0JqvTbUDvzpf6c 6P6GFC/89ObZqvfEuWyGcwViuwUgQ7xnGmaJBvyhXSUbLK9400NOv6u02CpkxRRN lychOp/2wThjVGitGAqs9ZpORmOy4a5LJuDONXhWcIrF2r2jyrVhw0bbe34U+TwE cSp0eN0qZR9zDj08dRrghS9ceCNAk9sJL2D9dYA2xbs3iiXu68840GdGHwk6ZROh yQuXtsbg/4zLm85ELaSE =FsU+ -END PGP SIGNATUREEnd Message---
Bug#770900: monkeysign: 'MonkeysignScan' object has no attribute 'dialog'
On 2014-11-26 16:20:23, Daniel Kahn Gillmor wrote: On 11/26/2014 04:15 PM, Antoine Beaupré wrote: On 2014-11-26 14:21:02, Daniel Kahn Gillmor wrote: The monkeyscan main window freezes and an strace reveals that the process is stuck in a futex() call. So i don't think this is resolved for me. Is there some way i can debug it further? Did you try running with the --debug switch? running with the --debug switch just shows me the command, return code, stdout, and stderr of the invocations of gpg. but gpg isn't running (it has already completed) by the time the dialog hangs on the futex() syscall and there are no child processes that i can see. Are you unable to reproduce this? I haven't actually tried yet, i was assuming that the simpler patch would fix the problem. I'll need to dig into this deeper now. Having some confirmation, maybe through the --debug output, that it is indeed the import path that is being taken, would help. Thanks! A. -- Imagination is more important than knowledge - Albert Einstein signature.asc Description: PGP signature
Bug#770425: wordpress: 4.0.1 security release
On sam., 2014-11-22 at 21:45 +0100, Yves-Alexis Perez wrote: On Sat, 22 Nov 2014 19:13:26 +1100 Craig Small csm...@debian.org wrote: On Fri, Nov 21, 2014 at 08:19:03AM +0100, Salvatore Bonaccorso wrote: Setting this as severity grave as it is mentioned as critical update. See https://wordpress.org/news/2014/11/wordpress-4-0-1/ for details. Thanks for the heads-up, I knew it was out there but was waiting for some free time. Better to be sure anyhow! There are no CVEs assigned yet for these issues. Oh good, I couldn't find any either and figured I was doing something wrong. The 4.0.1 should be pretty easy, it will take some time for backporting as that is a lot more fiddly as you know. By the way, as 3.6 is now unsupported, would it make sense to update stable to 3.7 (or later), like we did in DSA 2670-1, DSA 2718-1 and DSA 2757-1? Also, any idea where are the changes currently living in stable? I didn't found them in the git tree (http://anonscm.debian.org/cgit/collab-maint/wordpress.git/log/?h=wheezy) Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#635711: [monkeysphere] Bug#635711: Bug#635711: further analysis of monkeysphere.postinst failures
On Wed, Nov 26, 2014 at 04:07:57PM -0500, Daniel Kahn Gillmor wrote: + printf '%s:6:\n' 473F86D46E0B3CA0611450A8C9A7E0FFD1CD8FDC + gpg_sphere --import-ownertrust + RET=141 this just tells us that bash wanted to invoke gpg_sphere, not that it actually did invoke it. Had it invoked it, we should see more set -x output messages, right? look further up the page for a previous invocation of gpg_sphere. I'd expect to see at least: + GNUPGHOME=/var/lib/monkeysphere/authentication/sphere + export GNUPGHOME ... There should be no chance that gpg_sphere is not invoked in a subshell, though I may not remember how pipelines actually work in bash. Presumably it starts to run but is killed off by the SIGPIPE before it can set GNUPGHOME? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771113: lintian: FTBFS on i386: binaries-from-other-arch FAILED
Source: lintian Version: 2.5.30+deb8u2 Severity: serious Justification: fails to build from source Lintian FTBFS in i386 jessie chroot: | Running binaries-from-other-arch 1.0... building... testing... FAILED | --- t/tests/binaries-from-other-arch/tags 2014-10-13 20:45:41.0 + | +++ /build/lintian-YbPqW5/lintian-2.5.30+deb8u2/debian/test-out/tests/binaries-from-other-arch/tags.binaries-from-other-arch 2014-11-26 20:37:07.731101742 + | @@ -1,4 +1,3 @@ | -E: binaries-from-other-arch: binary-from-other-architecture usr/bin/elfobject | E: binaries-from-other-arch: statically-linked-binary usr/bin/elfobject | W: binaries-from-other-arch: apparently-corrupted-elf-binary usr/bin/elfobject | W: binaries-from-other-arch: binary-without-manpage usr/bin/elfobject I believe the culprit is this part of t/tests/binaries-from-other-arch/debian/debian/dumpobj: | case $DEB_BUILD_GNU_TYPE in | i486-linux-gnu|i686-linux-gnu|x86_64-linux-gnu) The GNU triplet for i386 is i586-linux-gnu these days. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770900: monkeysign: 'MonkeysignScan' object has no attribute 'dialog'
On 11/26/2014 04:31 PM, Antoine Beaupré wrote: On 2014-11-26 16:20:23, Daniel Kahn Gillmor wrote: running with the --debug switch just shows me the command, return code, stdout, and stderr of the invocations of gpg. but gpg isn't running (it has already completed) by the time the dialog hangs on the futex() syscall and there are no child processes that i can see. Are you unable to reproduce this? I haven't actually tried yet, i was assuming that the simpler patch would fix the problem. I'll need to dig into this deeper now. Having some confirmation, maybe through the --debug output, that it is indeed the import path that is being taken, would help. the gpg commands that are run are: --export --import (in tmpdir) --list-secret-keys It hangs after that point. --dkg signature.asc Description: OpenPGP digital signature
Bug#635711: [monkeysphere] Bug#635711: Bug#635711: further analysis of monkeysphere.postinst failures
On 11/26/2014 04:39 PM, Clint Adams wrote: There should be no chance that gpg_sphere is not invoked in a subshell, though I may not remember how pipelines actually work in bash. Presumably it starts to run but is killed off by the SIGPIPE before it can set GNUPGHOME? but the SIGPIPE should only happen if a write is actually being done to the closed pipe, though, right? And what would be writing to that pipe? --dkg signature.asc Description: OpenPGP digital signature
Bug#771114: FTBFS: GenFw: ERROR 3000: Invalid; Unsupported section alignment.
Source: edk2 Version: 0~20131112.2590861a-2 Severity: serious edk2 FTBFS in current unstable and testing. A tail of the buildlog follows. Building ... /tmp/buildd/edk2-0~20131112.2590861a/MdeModulePkg/Library/DxeNetLib/DxeNetLib.inf [X64] GenFw -o /tmp/buildd/edk2-0~20131112.2590861a/Build/OvmfX64/RELEASE_GCC47/X64/OvmfPkg/AcpiTables/AcpiTables/OUTPUT/./Facp.acpi -c /tmp/buildd/edk2-0~20131112.2590861a/Build/OvmfX64/RELEASE_GCC47/X64/OvmfPkg/AcpiTables/AcpiTables/OUTPUT/./Facp.dll make[2]: *** [/tmp/buildd/edk2-0~20131112.2590861a/Build/OvmfX64/RELEASE_GCC47/X64/OvmfPkg/AcpiTables/AcpiTables/OUTPUT/Facp.acpi] Error 2 echo Symbol renaming not needed for /tmp/buildd/edk2-0~20131112.2590861a/Build/OvmfX64/RELEASE_GCC47/X64/MdeModulePkg/Library/CustomizedDisplayLib/CustomizedDisplayLib/OUTPUT/./AutoGen.obj Symbol renaming not needed for /tmp/buildd/edk2-0~20131112.2590861a/Build/OvmfX64/RELEASE_GCC47/X64/MdeModulePkg/Library/CustomizedDisplayLib/CustomizedDisplayLib/OUTPUT/./AutoGen.obj /usr/bin/ar -cr /tmp/buildd/edk2-0~20131112.2590861a/Build/OvmfX64/RELEASE_GCC47/X64/MdeModulePkg/Library/CustomizedDisplayLib/CustomizedDisplayLib/OUTPUT/CustomizedDisplayLib.lib @/tmp/buildd/edk2-0~20131112.2590861a/Build/OvmfX64/RELEASE_GCC47/X64/MdeModulePkg/Library/CustomizedDisplayLib/CustomizedDisplayLib/OUTPUT/object_files.lst GenFw: ERROR 3000: Invalid Unsupported section alignment. GNUmakefile:322: recipe for target '/tmp/buildd/edk2-0~20131112.2590861a/Build/OvmfX64/RELEASE_GCC47/X64/OvmfPkg/AcpiTables/AcpiTables/OUTPUT/Facp.acpi' failed make[2]: Leaving directory '/tmp/buildd/edk2-0~20131112.2590861a/Build/OvmfX64/RELEASE_GCC47/X64/OvmfPkg/AcpiTables/AcpiTables' build.py... : error 7000: Failed to execute command make tbuild [/tmp/buildd/edk2-0~20131112.2590861a/Build/OvmfX64/RELEASE_GCC47/X64/OvmfPkg/AcpiTables/AcpiTables] build.py... : error F002: Failed to build module /tmp/buildd/edk2-0~20131112.2590861a/OvmfPkg/AcpiTables/AcpiTables.inf [X64, GCC47, RELEASE] - Failed - Build end time: 23:55:58, Nov.25 2014 Build total time: 00:00:53 debian/rules:28: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 1 make[1]: Leaving directory '/tmp/buildd/edk2-0~20131112.2590861a' debian/rules:25: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 arm64 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747637: akonadi-server: upgrade to akonadi-12-1-1 does not work so kmail too
Le mercredi 26 novembre 2014, 11:40:48 Raphael Hertzog a écrit : Control: tag -1 + moreinfo Hello Markus Merlin, you reported that you were affected by Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747637 Maximiliano believes that the latest update 1.13.0-1 should fix the db upgrade problems (see below). Can you confirm this so that we can close this bug ? On Tue, 19 Aug 2014, Maximiliano Curia wrote: I think the new uploaded akonadi version (1.13.0-1) fixes more db upgrade cases, but I haven't had any issues with the previous upgrades so it's hard for me to be sure. Could you please confirm if it fixes the issues you had with the 1.12.1 version? Yes you can close. With the new version there is no problem. Sorry I forget to say this. Philippe Merlin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771101: wheezy - jessie dist-upgrade failure when systemd is the active PID1
Am 26.11.2014 um 19:54 schrieb Michael Biebl: Nov 26 19:36:57 debian systemd[1]: Reloading. Nov 26 19:36:57 debian systemd[1]: bind(@run/systemd/notify) failed: Address already in use Nov 26 19:36:57 debian systemd[1]: Failed to reload: Address already in use Nov 26 19:36:59 debian groupadd[19888]: group added to /etc/group: name=input, GID=122 Nov 26 19:36:59 debian groupadd[19888]: group added to /etc/gshadow: name=input Nov 26 19:36:59 debian groupadd[19888]: new group: name=input, GID=122 Nov 26 19:36:59 debian systemd[1]: Stopping udev.service... Nov 26 19:36:59 debian systemd[1]: Stopped udev.service. Nov 26 19:36:59 debian systemd[1]: Stopping udev Control Socket. Nov 26 19:36:59 debian systemd[1]: Closed udev Control Socket. Nov 26 19:36:59 debian systemd[1]: Stopping udev Kernel Socket. Nov 26 19:36:59 debian systemd[1]: Closed udev Kernel Socket. Nov 26 19:36:59 debian systemd[1]: Reloading. Nov 26 19:36:59 debian systemd[1]: bind(@run/systemd/notify) failed: Address already in use Nov 26 19:36:59 debian systemd[1]: Failed to reload: Address already in use Nov 26 19:36:59 debian systemd[1]: Reloading. Nov 26 19:36:59 debian systemd[1]: bind(@run/systemd/notify) failed: Address already in use Nov 26 19:36:59 debian systemd[1]: Failed to reload: Address already in use Nov 26 19:36:59 debian systemd[1]: Starting udev Kernel Socket. Nov 26 19:36:59 debian systemd[1]: Listening on udev Kernel Socket. Nov 26 19:36:59 debian systemd[1]: Starting udev Control Socket. Nov 26 19:36:59 debian systemd[1]: Listening on udev Control Socket. Nov 26 19:36:59 debian systemd[1]: Starting udev Kernel Device Manager... Nov 26 19:36:59 debian systemd-udevd[19952]: Network interface NamePolicy= disabled on kernel commandline, ignoring. Nov 26 19:37:56 debian systemd[1]: systemd-journald.service watchdog timeout (limit 1min)! Nov 26 19:37:56 debian systemd-journal[19434]: Journal stopped Nov 26 19:37:56 debian systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... Nov 26 19:37:56 debian systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. Nov 26 19:38:29 debian systemd[1]: systemd-udevd.service start operation timed out. Terminating. Nov 26 19:38:29 debian systemd[1]: Failed to start udev Kernel Device Manager. I think, that's the relevant part from the journal, specifically: Nov 26 19:36:57 debian systemd[1]: bind(@run/systemd/notify) failed: Address already in use Nov 26 19:36:57 debian systemd[1]: Failed to reload: Address already in use Running lsof /run/systemd/notify, doesn't show any process listening on the socket. systemd-udevd in v215 uses Type=notify and I suspect it get's stuck in State activating since the sd_notify call doesn't succeed. I remember Sjoerd running into this issue as well, but I don't remember anymore if he found the root cause and how to fix it. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#635711: [monkeysphere] Bug#635711: Bug#635711: Bug#635711: further analysis of monkeysphere.postinst failures
On Wed, Nov 26, 2014 at 04:44:53PM -0500, Daniel Kahn Gillmor wrote: but the SIGPIPE should only happen if a write is actually being done to the closed pipe, though, right? And what would be writing to that pipe? I suppose logic would indicate that printf is writing and gpg_sphere is aborting abruptly for no apparent reason. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767857: kernel-package: diff for NMU version 13.014+nmu1
Control: tags 767857 + patch Control: tags 767857 + pending Dear maintainer, I've prepared an NMU for kernel-package (versioned as 13.014+nmu1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 diff -Nru kernel-package-13.014/debian/changelog kernel-package-13.014+nmu1/debian/changelog --- kernel-package-13.014/debian/changelog 2014-06-16 20:25:20.0 +0100 +++ kernel-package-13.014+nmu1/debian/changelog 2014-11-26 21:56:47.0 + @@ -1,3 +1,11 @@ +kernel-package (13.014+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Move examples to /usr/share/kernel-common and symlink from +/u/s/d (Closes: #767857) + + -- Jonathan Wiltshire j...@debian.org Wed, 26 Nov 2014 21:56:16 + + kernel-package (13.014) unstable; urgency=medium * There was a bug in the dh install configuration file, that moved all diff -Nru kernel-package-13.014/debian/kernel-common.dirs kernel-package-13.014+nmu1/debian/kernel-common.dirs --- kernel-package-13.014/debian/kernel-common.dirs 1970-01-01 01:00:00.0 +0100 +++ kernel-package-13.014+nmu1/debian/kernel-common.dirs 2014-11-26 22:01:17.0 + @@ -0,0 +1 @@ +usr/share/kernel-common/examples diff -Nru kernel-package-13.014/debian/kernel-common.examples kernel-package-13.014+nmu1/debian/kernel-common.examples --- kernel-package-13.014/debian/kernel-common.examples 2014-06-16 20:25:20.0 +0100 +++ kernel-package-13.014+nmu1/debian/kernel-common.examples 1970-01-01 01:00:00.0 +0100 @@ -1,2 +0,0 @@ -kernel/examples/etc -kernel/examples/sample.module.control diff -Nru kernel-package-13.014/debian/kernel-common.install kernel-package-13.014+nmu1/debian/kernel-common.install --- kernel-package-13.014/debian/kernel-common.install 1970-01-01 01:00:00.0 +0100 +++ kernel-package-13.014+nmu1/debian/kernel-common.install 2014-11-26 22:01:06.0 + @@ -0,0 +1,2 @@ +kernel/examples/etc usr/share/kernel-common/examples +kernel/examples/sample.module.control usr/share/kernel-common/examples diff -Nru kernel-package-13.014/debian/kernel-common.links kernel-package-13.014+nmu1/debian/kernel-common.links --- kernel-package-13.014/debian/kernel-common.links 1970-01-01 01:00:00.0 +0100 +++ kernel-package-13.014+nmu1/debian/kernel-common.links 2014-11-26 21:59:22.0 + @@ -0,0 +1 @@ +usr/share/kernel-common/examplesusr/share/doc/kernel-common/examples diff -Nru kernel-package-13.014/debian/kernel-common.postinst kernel-package-13.014+nmu1/debian/kernel-common.postinst --- kernel-package-13.014/debian/kernel-common.postinst 2014-06-16 20:25:20.0 +0100 +++ kernel-package-13.014+nmu1/debian/kernel-common.postinst 2014-11-26 22:06:32.0 + @@ -4,10 +4,10 @@ # Author : Manoj Srivastava ( sriva...@glaurung.green-gryphon.com ) # Created On : Fri Nov 14 11:25:07 2003 # Created On Node : glaurung.green-gryphon.com -# Last Modified By : Manoj Srivastava -# Last Modified On : Sun Aug 20 16:28:01 2006 -# Last Machine Used: glaurung.internal.golden-gryphon.com -# Update Count : 11 +# Last Modified By : Jonathan Wiltshire +# Last Modified On : Wed 26 Nov 22:06:03 GMT 2014 +# Last Machine Used: +# Update Count : 12 # Status : Unknown, Use with caution! # HISTORY : # Description : @@ -69,7 +69,7 @@ # information, do it here. my_arch=$(dpkg --print-architecture) new_config=/etc/kernel-img.conf.ucf-new -sample_config=/usr/share/doc/kernel-common/examples/etc/sample.kernel-img.conf +sample_config=/usr/share/kernel-common/examples/etc/sample.kernel-img.conf cp -f $sample_config $new_config case $my_arch in mips|mipsel|m68k) signature.asc Description: Digital signature
