Bug#801933: python-django-guardian

Hello Kouhei Maeda, Are you still interested in maintianing this package? It currently has an RC bug #801933 that means other packages such as djangorestframework will get removed from testing unless fixed. I note that I made the last 2 uploads as NMU and there has been no response yet to this

Bug#803082: [Python-modules-team] Bug#803082: Bug#803082: ipython ftbfs (too new lessc version)

Hi, Le mardi 03 nov. 2015 à 08:19:31 (+), Javi Merino a écrit : > On Fri, Oct 30, 2015 at 05:34:41PM +0100, Matthias Klose wrote: > > On 30.10.2015 10:03, Brian May wrote: > > >I suspect the solution to this is to update to use ipython 4.0.0 > > > > > >It looks like there have been

Bug#801973: [Pkg-roundcube-maintainers] Bug#801973: error 255 on package configuration

Hello, unfortunately, last week, I have forced the upgrade with exit 0 at the top of the script on my both servers. I'll activate "set -x" for the next upgrade. It's strange I was the the only one with this bug... Emmanuel.

Bug#801973: [Pkg-roundcube-maintainers] Bug#801973: error 255 on package configuration

But during the upgrade from 0.9.5+dfsg1-4.2 to 1.1.1+dfsg.1-1, I purged the roundcube* packages and removed /etc/roundcube because all was broken (error 255 too). Maybe I have forgotten symlinks. If you have a list of symlinks to check, let me known, Emmanuel.

Bug#801265: marked as done (svxlink: FTBFS: This file requires compiler and library support for the ISO C++ 2011 standard.)

Your message dated Tue, 03 Nov 2015 09:42:04 + with message-id and subject line Bug#801265: fixed in svxlink 14.08.1-2 has caused the Debian Bug report #801265, regarding svxlink: FTBFS: This file requires compiler and library support for the ISO C++ 2011

Bug#803700: mrpt: FTBFS: 7 FAILED TESTS

Thanks Andreas. For the records: This was caused by the use of the latest alpha version of Eigen 3.3, as explained in this bug report: http://eigen.tuxfamily.org/bz/show_bug.cgi?id=1066#c3 It is already fixed upstream in MRPT. We will release a new version soon to close this bug. JL On Sun,

Bug#803082: [Python-modules-team] Bug#803082: Bug#803082: ipython ftbfs (too new lessc version)

On Fri, Oct 30, 2015 at 05:34:41PM +0100, Matthias Klose wrote: > On 30.10.2015 10:03, Brian May wrote: > >I suspect the solution to this is to update to use ipython 4.0.0 > > > >It looks like there have been significant structural changes in 4.0.0, > >so work is required to merge the patches

Bug#801973: [Pkg-roundcube-maintainers] Bug#801973: error 255 on package configuration

❦ 3 novembre 2015 10:13 +0100, e-mmanuel  : > unfortunately, last week, I have forced the upgrade with exit 0 at the > top of the script on my both servers. > I'll activate "set -x" for the next upgrade. > > It's strange I was the the only one with this bug... It may be

Bug#803914: ejabberd-mod-http-upload and ejabberd: error when trying to install together

Hi On 03.11.2015 08:08, Ralf Treinen wrote: > dpkg: error processing archive > /var/cache/apt/archives/ejabberd-mod-http-upload_0.2015.10.02~dfsg0-1_amd64.deb > (--unpack): > trying to overwrite > '/usr/lib/x86_64-linux-gnu/ejabberd/ebin/mod_http_upload.beam', which is also > in package

Bug#803949: electrum: Electrum unable to start; Cannot read config file

Package: electrum Version: 1.9.8-4 Severity: grave Justification: renders package unusable Dear Maintainer, I've never had this problem before, but after recently re-installing Debian, I am unable to start Electrum. When I try from the command line, I get the following: Traceback (most recent

Processed: pimd: diff for NMU version 2.3.0-0.1

Processing control commands: > tags 719555 + patch Bug #719555 [pimd] pimd: consumes 100% CPU during sendto() failure Ignoring request to alter tags of bug #719555 to the same tags previously set > tags 719555 + pending Bug #719555 [pimd] pimd: consumes 100% CPU during sendto() failure Ignoring

Processed: block 803917 with 803669

Processing commands for cont...@bugs.debian.org: > block 803917 with 803669 Bug #803917 [src:owncloud-client] owncloud-client: FTBFS on mips* on FileSystemTest 803917 was not blocked by any bugs. 803917 was not blocking any bugs. Added blocking bug(s) of 803917: 803669 > thanks Stopping

Processed: pimd: diff for NMU version 2.3.0-0.1

Processing control commands: > tags 719555 + patch Bug #719555 [pimd] pimd: consumes 100% CPU during sendto() failure Ignoring request to alter tags of bug #719555 to the same tags previously set > tags 719555 + pending Bug #719555 [pimd] pimd: consumes 100% CPU during sendto() failure Ignoring

Processed: pimd: diff for NMU version 2.3.0-0.1

Processing control commands: > tags 719555 + patch Bug #719555 [pimd] pimd: consumes 100% CPU during sendto() failure Added tag(s) patch. > tags 719555 + pending Bug #719555 [pimd] pimd: consumes 100% CPU during sendto() failure Added tag(s) pending. > tags 725554 + patch Bug #725554 [src:pimd]

Bug#803686: [sebas...@xs4all.nl: Bug#803686: direwolf: FTBFS with libgps22]

Thanks for passing this along. The source code has been updated as suggested and this will be in version 1.3. John -Original Message- From: Iain R. Learmonth [mailto:i...@fsfe.org] Sent: Monday, November 02, 2015 9:27 AM To: wb2...@comcast.net; 803...@bugs.debian.org Subject:

Bug#803926: Should depend on libssl-dev

Package: libspice-server-dev Version: 0.12.6-3 Severity: serious libspice-server-dev should depend on the libssl-dev package. Without it an attempt to compile software with it fails: $ pkg-config --cflags 'spice-server >= 0.12.0' ; echo $? Package openssl was not found in the pkg-config search

Bug#803936: goplay: not installable using aptitude with "apt-xapian-index.postinst: update-python-modules: not found"

Package: goplay Severity: grave Justification: renders package unusable Dear Maintainer, goplay failed to install using aptitude with "apt-xapian-index.postinst: update-python-modules: not found": # aptitude install goplay The following NEW packages will be installed: apt-xapian-index{a}

Bug#802249: collectd: FTBFS: error: 'c_varnish_stats_t.. has no member named 'backend_toolate'

This is upstream bug https://github.com/collectd/collectd/issues/1302 Marius Gedminas -- Where are you most likely to need carpet tacks and a hammer, for example? Precisely. So leaving them on the stairs is simple ergonomics. -- http://www.mil-millington.com/

Bug#785908: marked as done (arista: Please update to GStreamer 1.x)

Your message dated Tue, 03 Nov 2015 12:12:14 + with message-id and subject line Bug#803781: Removed package(s) from unstable has caused the Debian Bug report #785908, regarding arista: Please update to GStreamer 1.x to be marked as done. This means that

Processed: Re: Bug#803936: goplay: not installable using aptitude with "apt-xapian-index.postinst: update-python-modules: not found"

Processing control commands: > reassign -1 apt-xapian-index Bug #803936 [goplay] goplay: not installable using aptitude with "apt-xapian-index.postinst: update-python-modules: not found" Bug reassigned from package 'goplay' to 'apt-xapian-index'. Ignoring request to alter found versions of bug

Bug#803936: goplay: not installable using aptitude with "apt-xapian-index.postinst: update-python-modules: not found"

Control: reassign -1 apt-xapian-index Control: forcemerge 793681 -1 Control: affects -1 goplay Hi, On Tue, 2015-11-03 at 13:41 +0100, twied wrote: > Package: goplay > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > goplay failed to install using aptitude with

Bug#801933: python-django-guardian

Brian May writes: > It looks like the Debian package is not in VCS, so I will also move it > to git as part of moving it to the Debian Python Modules Team. I have packaged the lastest upstream package in git:

Bug#803933: iceweasel: "Save Page As" has no effects or removes the target file under some conditions

Package: iceweasel Version: 38.3.0esr-1 Severity: grave Justification: causes non-serious data loss Under some conditions (to be determined), "Save Page As" has no effects. It seems to succeed, but nothing is saved, so that the data may be definitely lost! Here I have a page

Bug#803933: iceweasel: "Save Page As" has no effects or removes the target file under some conditions

On 2015-11-03 12:48:24 +0100, Vincent Lefevre wrote: > Under some conditions (to be determined), "Save Page As" has no effects. This seems to occur when the file displayed in the browser has been removed. In case the browser cannot retrieve the file: 1. There MUST be an error message. Otherwise

Processed: glibc: multiple overflows in strxfrm()

Processing control commands: > forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=16009 Bug #803927 [src:glibc] glibc: multiple overflows in strxfrm() Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=16009'. -- 803927:

Bug#803927: glibc: multiple overflows in strxfrm()

Source: glibc Version: 2.19-22 Severity: serious Tags: security fixed-upstream Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=16009 Hello, libc6 is vulnerable to buffer overruns in strxfrm() as reported in the following upstream ticket:

Bug#802356: Latest version (1.8.11) fails to build

Hi, in Debian a build time bug was reported here: https://bugs.debian.org/802356 Since this was not the latest available version 1.8.11 I downloaded the latest one but was running into an error as well: ... init-environment: compile-library: [mkdir] Created dir:

Bug#801973: [Pkg-roundcube-maintainers] Bug#801973: error 255 on package configuration

❦ 3 novembre 2015 10:48 +0100, e-mmanuel  : > But during the upgrade from 0.9.5+dfsg1-4.2 to 1.1.1+dfsg.1-1, I > purged the roundcube* packages and removed /etc/roundcube because all > was broken (error 255 too). > > Maybe I have forgotten symlinks. > If you have a list

Bug#803947: enigmail: completely broken after upgrade of gnupg2 to 2.1.9

This issue seems to be similar to the current RC bugs in gnupg2: #795639 and #796931 Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature

Bug#803949: electrum: Electrum unable to start; Cannot read config file

On Tue, 3 Nov 2015 at 17:09 Zachary Peterson wrote: > File "/usr/lib/python2.7/dist-packages/electrum/simple_config.py", line > 157, in read_user_config > raise IOError("Cannot read config file.") > IOError: Cannot read config file. This error is raised if an exception

Bug#803945: horae, artemis: error when trying to install together

Hi Carlo, the Debian Med team has struggled a long time to get artemis packaged. Now we are realising this name conflict. I know the rules that the name space is occupied by a first comes first served principle. However, in this case I'd like to discuss whether you see a chance to rename the

Processed: notfound 803949 in 1.9.8-4

Processing commands for cont...@bugs.debian.org: > notfound 803949 1.9.8-4 Bug #803949 {Done: Tristan Seligmann } [electrum] electrum: Electrum unable to start; Cannot read config file No longer marked as found in versions electrum/1.9.8-4. > thanks Stopping processing

Bug#803700: mrpt: FTBFS: 7 FAILED TESTS

Control: tags -1 fixed-upstream Hi Jose Luis, On 03.11.2015 10:34, Jose Luis Blanco wrote: > For the records: This was caused by the use of the latest alpha > version of Eigen 3.3, as explained in this bug report: > http://eigen.tuxfamily.org/bz/show_bug.cgi?id=1066#c3 > > It is already fixed

Processed: Re: Bug#803700: mrpt: FTBFS: 7 FAILED TESTS

Processing control commands: > tags -1 fixed-upstream Bug #803700 [src:mrpt] mrpt: FTBFS: 7 FAILED TESTS Added tag(s) fixed-upstream. -- 803700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#802265: marked as done (src:botch: FTBFS: target 'test-selfcontained' failed)

Your message dated Tue, 03 Nov 2015 19:19:10 + with message-id and subject line Bug#802265: fixed in botch 0.17-1 has caused the Debian Bug report #802265, regarding src:botch: FTBFS: target 'test-selfcontained' failed to be marked as done. This means

Bug#803971: apf: Uses ALL as cipherlist

Package: apf Severity: serious Tags: security Hi, Looking at your package I saw this: if (SSL_CTX_set_cipher_list(ctx, "ALL:@STRENGTH") == 0) { This enabled all ciphersuites, including those that don't provide any authentication or encryption. This is ussually not what you want. You

Bug#799821: marked as done (ruby-rspec-rails: FTBFS: cannot load such file -- rspec/core/deprecation (LoadError))

Your message dated Tue, 03 Nov 2015 17:21:15 + with message-id and subject line Bug#799821: fixed in ruby-rspec-rails 3.3.3-1 has caused the Debian Bug report #799821, regarding ruby-rspec-rails: FTBFS: cannot load such file -- rspec/core/deprecation

Bug#801973: [Pkg-roundcube-maintainers] Bug#801973: error 255 on package configuration

I've just verified on my second server. No filter or autoresponder installed and I've had the problem on the upgrade. Le 03/11/2015 18:57, e-mmanuel a écrit : Here are my symlinks : /usr/share/roundcube 0 lrwxrwxrwx 1 root root 46 oct. 6 15:19 plugins/jqueryui/config.inc.php ->

Bug#803949: electrum: Electrum unable to start; Cannot read config file

> Tristan Seligmann writes: > The following command should reproduce the process used by Electrum > 1.9.8 to load the config file: > python -c 'import ast, os; print > ast.literal_eval(open(os.path.expanduser("~/.electrum/config")))' > This should fail with a

Bug#797809: marked as done (gazebo ftbfs with SDF 3.0)

Your message dated Tue, 3 Nov 2015 19:47:52 +0100 with message-id <56390158.8050...@googlemail.com> and subject line Re: Bug#797809: gazebo ftbfs with SDF 3.0 has caused the Debian Bug report #797809, regarding gazebo ftbfs with SDF 3.0 to be marked as done. This means that you claim that the

Bug#801973: [Pkg-roundcube-maintainers] Bug#801973: error 255 on package configuration

Here are my symlinks : /usr/share/roundcube 0 lrwxrwxrwx 1 root root 46 oct. 6 15:19 plugins/jqueryui/config.inc.php -> /etc/roundcube/plugins/jqueryui/config.inc.php /var/lib/roundcube 0 lrwxrwxrwx 1 root root 14 sept. 11 08:43 config -> /etc/roundcube/ 0 lrwxrwxrwx 1 root root

Bug#803949: [Pkg-bitcoin-devel] Bug#803949: electrum: Electrum unable to start; Cannot read config file

Hello, That is right. You should use 2.5.2 or newer - 1.9.8, aside the fact that it uses only old version seeds, it won't be able to sign a transaction and broadcast it to the network because it doesn't contain the low-S enforcement in ECDSA signatures update. So you will have a hard time

Processed: found 803914 in 0.2015.10.02~dfsg0-1, found 803914 in 15.10-1, tagging 803916, tagging 801937 ...

Processing commands for cont...@bugs.debian.org: > found 803914 0.2015.10.02~dfsg0-1 Bug #803914 [ejabberd,ejabberd-mod-http-upload] ejabberd-mod-http-upload and ejabberd: error when trying to install together There is no source info for the package 'ejabberd' at version '0.2015.10.02~dfsg0-1'

Bug#803972: attic: Fixed depedency on libssl1.0.0

Source: attic Version: 0.13-1 Severity: serious Hi, The package seems to have a fixed dependency on libssl1.0.0. It's been renamed to libssl1.0.2 and you now have a dependency on both. Please remove the dependency on libssl1.0.0. Kurt

Bug#803949: marked as done (electrum: Electrum unable to start; Cannot read config file)

Your message dated Tue, 03 Nov 2015 18:50:54 + with message-id and subject line Re: Bug#803949: electrum: Electrum unable to start; Cannot read config file has caused the Debian Bug report #803949, regarding electrum:

Bug#803689: marked as done (pypy: DEFAULT_SOABI at pypy-26 while DEFAULT_MAGIC_TAG = 'pypy-40')

Your message dated Tue, 03 Nov 2015 22:33:52 + with message-id and subject line Bug#803689: fixed in dh-python 2.20151103 has caused the Debian Bug report #803689, regarding pypy: DEFAULT_SOABI at pypy-26 while DEFAULT_MAGIC_TAG = 'pypy-40' to be marked as

Bug#803975: libcrypt-ssleay-perl: Uses SSLv3_client_method()

Source: libcrypt-ssleay-perl Version: 0.58-1 Severity: serious Hi, Your package has code in SSLeay.xs that does: if(ssl_version == 23) { ctx = SSL_CTX_new(SSLv23_client_method()); } else if(ssl_version == 3) { ctx =

Bug#803959: marked as done (libelasticsearch1.7-java: fails to upgrade from 'testing' - trying to overwrite /usr/share/maven-repo/org/elasticsearch/elasticsearch/1.6/elasticsearch-1.6.pom)

Your message dated Tue, 03 Nov 2015 19:49:17 + with message-id and subject line Bug#803959: fixed in elasticsearch 1.7.3+dfsg-2 has caused the Debian Bug report #803959, regarding libelasticsearch1.7-java: fails to upgrade from 'testing' - trying to

Bug#803974: libnet-tclink-perl: FTBFS: Uses SSLv3_client_method

Source: libnet-tclink-perl Version: 3.4.0-7 Severity: serious Hi, Your package does this in tclink.c: c->meth = SSLv3_client_method(); Please call SSLv23_client_method() instead. The SSLv3_* methods only supports SSLv3 while the SSLv23_* is the only that supports multiple

Bug#803914: marked as done (ejabberd-mod-http-upload and ejabberd: error when trying to install together)

Your message dated Tue, 03 Nov 2015 19:49:03 + with message-id and subject line Bug#803914: fixed in ejabberd-contrib 0.2015.10.26~dfsg0-1 has caused the Debian Bug report #803914, regarding ejabberd-mod-http-upload and ejabberd: error when trying to

Bug#803975: libcrypt-ssleay-perl: Uses SSLv3_client_method()

On Tue, 03 Nov 2015 20:50:43 +0100, Kurt Roeckx wrote: > You really only ever want to use SSLv23_client_method() since that > is the only one that supports multiple versions. I suggest you > modify your nossl2.patch to just replace all of the above by: > ctx =

Bug#803994: rofi: segfaults on -show window (upstream#256)

Package: rofi Version: 0.15.10-1 Severity: grave Tags: upstream Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Dear Maintainer, It may be of note that upstream release 0.15.10 has serious bugs:

Bug#802166: otags: fails to install: post-installation script returned error exit status 3

Package: otags Version: 4.01.1-2 Followup-For: Bug #802166 I ran into this bug too. Here's some output that might be helpful: $ sudo update-otags [sudo] password for amu: Fatal error: escaping exception File "tags.ml", line 361, characters 32-37: Pattern matching failed Please rerun otags

Processed: [bts-link] source package src:celery

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:celery > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Bug#803375: marked as done (python-csvkit: No command-line tools)

Your message dated Wed, 4 Nov 2015 01:20:52 + with message-id and subject line Re: Bug#803375: python-csvkit: No command-line tools has caused the Debian Bug report #803375, regarding python-csvkit: No command-line tools to

Processed: [bts-link] source package src:influxdb-python

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:influxdb-python > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Processed: [bts-link] source package src:bitcoin

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:bitcoin > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Bug#803994: rofi: segfaults on -show window (upstream#256)

Hi, On 11/03/2015 08:57 PM, Guy Hughes wrote: > Package: rofi > Version: 0.15.10-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > Dear Maintainer, > > It may be of note that upstream release 0.15.10 has serious bugs: > >*

Bug#785922: marked as done (pychess: Please update to GStreamer 1.x)

Your message dated Wed, 04 Nov 2015 04:21:08 + with message-id and subject line Bug#785922: fixed in pychess 0.12-1 has caused the Debian Bug report #785922, regarding pychess: Please update to GStreamer 1.x to be marked as done. This means that you claim

Bug#803945: horae, artemis: error when trying to install together

Hello, On الثلاثاء 3 تشرين الثاني 2015 07:51, Andreas Tille wrote: > Hi Carlo, > > the Debian Med team has struggled a long time to get artemis packaged. > Now we are realising this name conflict. I know the rules that the name > space is occupied by a first comes first served principle.

Bug#803994: rofi: segfaults on -show window (upstream#256)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Hello, wow, you're fast. On Tue, Nov 03, 2015 at 09:38:04PM -0500, Jason Pleau wrote: > Hi, > > Do you have any rofi settings in $HOME/.Xresources you can provide in > this bug report? `rofi

Bug#803012: tar ftbfs everywhere (test suite errors)

Package: tar Version: 1.28-2 Followup-For: Bug #803012 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu xenial ubuntu-patch *** /tmp/tmp70_1Po/bug_body In Ubuntu, the attached patch was applied to achieve the following: * debian/patches/use-sort-in-t-dir-tests.diff: upstream

Processed: Re: Bug#798964: slapd: since security upgrade writing ber in accesslog is broken

Processing control commands: > severity -1 important Bug #798964 [slapd] slapd: since security upgrade writing ber in accesslog is broken Severity set to 'important' from 'grave' -- 798964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798964 Debian Bug Tracking System Contact

Bug#798964: slapd: since security upgrade writing ber in accesslog is broken

Control: severity -1 important Hello Benoit, I'm afraid I haven't made any more progress on replicating the problem you reported. From your end, have you discovered any more information that would help us diagnose it? I haven't seen any other similar bug reports, so this at least doesn't

Bug#803321: marked as done (rawdns: FTBFS: cp: cannot stat 'debian/tmp/debian/tmp/dh-exec.ShSIquIE/etc/rawdns.json': No such file or )

Your message dated Tue, 3 Nov 2015 21:00:29 -0800 with message-id and subject line Re: [pkg-go] Bug#803321: [Reproducible-builds] Bug#803321: rawdns: FTBFS: cp: cannot stat

Bug#803321: [pkg-go] Bug#803321: [Reproducible-builds] Bug#803321: rawdns: FTBFS: cp: cannot stat 'debian/tmp/debian/tmp/dh-exec.ShSIquIE/etc/rawdns.json': No such file or

On 28 October 2015 at 12:55, Niko Tyni wrote: > Looks like #802034, fixed today in dh-exec_0.22. Indeed! https://reproducible.debian.net/rb-pkg/unstable/amd64/rawdns.html appears happy now, so I'm going to close this. Thanks Chris for the heads up and thanks Niko for the

Bug#803559: marked as done (golang-go: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/go/pkg/tool/linux_amd64/cover)

Your message dated Wed, 04 Nov 2015 06:05:45 + with message-id and subject line Bug#803559: fixed in golang 2:1.5.1-4 has caused the Debian Bug report #803559, regarding golang-go: fails to upgrade from 'jessie' - trying to overwrite

Bug#803975: libcrypt-ssleay-perl: Uses SSLv3_client_method()

On Tue, Nov 03, 2015 at 10:33:21PM +0100, Kurt Roeckx wrote: > On Tue, Nov 03, 2015 at 09:56:36PM +0100, gregor herrmann wrote: > > On Tue, 03 Nov 2015 20:50:43 +0100, Kurt Roeckx wrote: > > > > > You really only ever want to use SSLv23_client_method() since that > > > is the only one that

Bug#803975: libcrypt-ssleay-perl: Uses SSLv3_client_method()

On Tue, Nov 03, 2015 at 09:56:36PM +0100, gregor herrmann wrote: > On Tue, 03 Nov 2015 20:50:43 +0100, Kurt Roeckx wrote: > > > You really only ever want to use SSLv23_client_method() since that > > is the only one that supports multiple versions. I suggest you > > modify your nossl2.patch to

Processed: block 797926 with 803975, block 797926 with 803974, block 797926 with 803881 ...

Processing commands for cont...@bugs.debian.org: > block 797926 with 803975 Bug #797926 [release.debian.org] transition: openssl: remove SSLv3 methods 797926 was not blocked by any bugs. 797926 was not blocking any bugs. Added blocking bug(s) of 797926: 803975 > block 797926 with 803974 Bug

Bug#801582: problem still exist

1.1-4 does not install the grub2 script anymore. You might need to manually delete /etc/grub.d/50_nvram_wakeup and run update-grub to clean up the mess I did with 1.1-3 (sorry for this!). Are you actually using nvram-wakeup? It's on of the packages I plan to completely remove sooner or later.

Processed: Bug#803958 critically affects Octave

Processing commands for cont...@bugs.debian.org: > affects 803958 octave Bug #803958 [libgraphicsmagick++-q16-11] libgraphicsmagick++-q16-11: SONAME changed without package name change Added indication that 803958 affects octave > stop Stopping processing here. Please contact me if you need

Bug#803958: critically affects Octave

affects 803958 octave stop This is just to register the fact that the graphicsmagick's soversion-bump-without-package-rename is also affecting Octave and the plethora of packages depending on it. Please, fix this bug as soon as possible. Rafael Laboissière

Bug#803945: horae, artemis: error when trying to install together

Ahh, OK, that would be a way simpler solution. I have read my PM first and was not aware of this ... On Tue, Nov 03, 2015 at 09:28:48PM -0800, Afif Elghraoui wrote: > Hello, > > On الثلاثاء 3 تشرين الثاني 2015 07:51, Andreas Tille wrote: > > Hi Carlo, > > > > the Debian Med team has struggled

Bug#803945: horae, artemis: error when trying to install together

On Tue, Nov 03, 2015 at 09:28:48PM -0800, Afif Elghraoui wrote: > but the name in > the menu will still be Artemis. Will that be a problem? As far as I can tell there is not technical problem. Since both packages are leaf packages I do not even see any real danger for confusion on users side.

Bug#801582: replaced nvram-wakeup with direct write to /sys

Hi For what it's worth, I've replaced nvram-wakeup with a direct write to /sys/class/rtc/rtc0/wakealarm . See this blog [1] for details. All the best [1]https://ddumont.wordpress.com/2012/04/14/my-setup-for-vdr-automatic-wake-up-and-shutdown/ -- https://github.com/dod38fr/ -o-

Processed: horae,artemis: error when trying to install together

Processing control commands: > found -1 071~svn537-2 Bug #803945 [horae,artemis] horae,artemis: error when trying to install together There is no source info for the package 'artemis' at version '071~svn537-2' with architecture '' Marked as found in versions horae/071~svn537-2. -- 803945:

Bug#803558: clang-tidy: fails to upgrade from 'testing' - trying to overwrite /usr/bin/clang-tidy

Followup-For: Bug #803558 Control: found -1 1:3.6-32 >* Fix the upgrade from 'testing' > Adds Breaks: clang (<< 0.28) & Replaces: clang (<< 0.28) > into clang-format, clang-tidy & clang-modernize (Closes: #803558) This didn't work, you need the real version of the binary packages,

Bug#803945: horae,artemis: error when trying to install together

Package: horae,artemis Version: 16.0.0+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 071~svn537-2 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has

Processed: Re: clang-tidy: fails to upgrade from 'testing' - trying to overwrite /usr/bin/clang-tidy

Processing control commands: > found -1 1:3.6-32 Bug #803558 {Done: Sylvestre Ledru } [clang-tidy] clang-tidy: fails to upgrade from 'testing' - trying to overwrite /usr/bin/clang-tidy Marked as found in versions llvm-defaults/0.32; no longer marked as fixed in versions

Bug#803947: enigmail: completely broken after upgrade of gnupg2 to 2.1.9

Package: enigmail Version: 2:1.8.2-4 Severity: grave Justification: renders package unusable Hi, after upgrade of gnupg2 to 2.1.9 enigmail becomes pretty much useless, at least when used under KDE / Plasma 5. Encrypting/Decrypting doesn't work anymore and key-management is seriously impacted as

Bug#803958: libgraphicsmagick++-q16-11: SONAME changed without package name change

Package: libgraphicsmagick++-q16-11 Severity: serious Control: affects -1 gnudatalanguage Control: block 803760 by -1 Hi, the package libgraphicsmagick++-q16-11 contains the library with a different soname: libGraphicsMagick++-Q16.so.12. This breaks existing packages, like gnudatalanguage, and

Processed: libgraphicsmagick++-q16-11: SONAME changed without package name change

Processing control commands: > affects -1 gnudatalanguage Bug #803958 [libgraphicsmagick++-q16-11] libgraphicsmagick++-q16-11: SONAME changed without package name change Added indication that 803958 affects gnudatalanguage > block 803760 by -1 Bug #803760 [gnudatalanguage] coyote: FTBFS: gdl:

Bug#803959: libelasticsearch1.7-java: fails to upgrade from 'testing' - trying to overwrite /usr/share/maven-repo/org/elasticsearch/elasticsearch/1.6/elasticsearch-1.6.pom

Package: libelasticsearch1.7-java Version: 1.7.3+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries