Processing commands for cont...@bugs.debian.org:
> found 835532 1.36-1
Bug #835532 [postgrey] default config dir change from /etc/postgrey to
/etc/postfix not handled
Marked as found in versions postgrey/1.36-1.
> found 835535 1.36-1
Bug #835535 [postgrey] fails to start after upgrade: default
Processing commands for cont...@bugs.debian.org:
> fixed 821734 1.3.0-3
Bug #821734 {Done: Nicholas Breen } [libvotca-csg3]
libvotca-csg3: fails to upgrade from 'jessie' - trying to overwrite
/usr/share/man/man7/votca-csg.7.gz
Marked as fixed in versions votca-csg/1.3.0-3.
>
Processing commands for cont...@bugs.debian.org:
> reassign 833001 mate-common
Bug #833001 {Done: John Paul Adrian Glaubitz }
[src:caja-actions] caja-actions: FTBFS: ./autogen.sh: 80: shift: can't shift
that many
Bug reassigned from package 'src:caja-actions' to
Processing commands for cont...@bugs.debian.org:
> reassign 831182 qbs-dev
Bug #831182 {Done: Adam Majer } [src:qtcreator] qtcreator:
FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or
directory
Bug reassigned from package 'src:qtcreator' to 'qbs-dev'.
No
Processing control commands:
> notfound -1 0.1.8-4
Bug #815004 {Done: Eric Dorland } [libengine-pkcs11-openssl]
Engine is installed at wrong location
No longer marked as found in versions engine-pkcs11/0.1.8-4.
--
815004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815004
Control: notfound -1 0.1.8-4
On Fri, Aug 26, 2016 at 13:39:13 +0200, Julien Cristau wrote:
> Control: found -1 0.1.8-4
>
[...]
> This seems broken in stable as well:
>
> $ openssl engine pkcs11
> 140063553324688:error:25066067:DSO support routines:DLFCN_LOAD:could not load
> the shared
>
Thank you Richard!
On August 26, 2016 7:40:50 PM EDT, Richard Hartmann
wrote:
>And uploaded.
Source: network-manager
Version: 1.4.0-2
Severity: serious
Hi,
network-manager FTBFS on all mips arches and on powerpc with this error:
> make[9]: Leaving directory '/«PKGBUILDDIR»/src/settings/plugins/ibft/tests'
> LD_BIND_NOW=1 LD_PRELOAD=./../.libs/libnm-settings-plugin-ibft.so
>
And uploaded.
On Fri, Aug 26, 2016 at 03:04:32PM -0400, Hubert Chathi wrote:
> On Mon, 22 Aug 2016 11:53:51 +0200 (CEST), Santiago Vila
> said:
>
> > This package does no longer build from source because the iconc
> > package does no longer exist (I'm not providing a build log, but this
> >
Your message dated Fri, 26 Aug 2016 23:19:24 +
with message-id
and subject line Bug#835514: fixed in protobuf 3.0.0-6
has caused the Debian Bug report #835514,
regarding libprotobuf-java: junit and easymock dependencies should only be
required for tests
Processing commands for cont...@bugs.debian.org:
> forwarded 835514 https://github.com/google/protobuf/issues/2019
Bug #835514 [libprotobuf-java] libprotobuf-java: junit and easymock
dependencies should only be required for tests
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> tags 831142 +patch
Bug #831142 [src:gcc-arm-none-eabi] gcc-arm-none-eabi: FTBFS with GCC 6:
cfns.gperf:101:1: error: 'const char* libc_name_p(const char*, unsigned int)'
redeclared inline with 'gnu_inline' attribute
Added tag(s) patch.
> thanks
tags 831142 +patch
thanks
Attached is the fix from upstream 4.9.4 for the gcc-arm-none-eabi FTBFS.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Processing commands for cont...@bugs.debian.org:
> block 832410 by 835546
Bug #832410 [python-clang-4.0,python-lldb-4.0] python-clang-4.0,
python-lldb-4.0: missing Breaks+Replaces against the corresponding python-*-3.9
packages
832410 was not blocked by any bugs.
832410 was not blocking any
Apparently ginac requires C++11 now, which you need to manually enable with GCC
5.
gcc-6 is now the default and has C++11 enabled by default, so this is no
longer an issue.
Unfortunately the packege now fails to build for a different reason.
Processing commands for cont...@bugs.debian.org:
> tag 811323 + pending
Bug #811323 [src:mugshot] mugshot: FTBFS: ImportError: No module named 'gi'
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
811323:
Processing commands for cont...@bugs.debian.org:
> tags 820186 + pending
Bug #820186 [src:kdevelop-python] kdevelop-python: build-depends on
python3.4-dev which is going away
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
820186:
I've tested the libprotobuf-java reverse dependencies and unfortunately
most are using maven and are affected by this issue, I've marked those
packages accordingly.
Kind Regards,
Bas
Processing commands for cont...@bugs.debian.org:
> affects 835514 src:bookkeeper src:projectreactor src:netty-3.9
Bug #835514 [libprotobuf-java] libprotobuf-java: junit and easymock
dependencies should only be required for tests
Added indication that 835514 affects src:bookkeeper,
Processing commands for cont...@bugs.debian.org:
> found 835540 log4cpp/1.1.1-1
Bug #835540 [src:log4cpp] Missing dependencies at linktime
Marked as found in versions log4cpp/1.1.1-1.
> severity 834979 important
Bug #834979 [src:bitz-server] bitz-server: FTBFS in testing (linking error)
Severity
Processing commands for cont...@bugs.debian.org:
> found 822787 0.99.22.4-1
Bug #822787 [src:quagga] quagga: CVE-2016-4049: Missing size check in
bgp_dump_routes_func in bgpd/bgp_dump.c allowing DoS
Marked as found in versions quagga/0.99.22.4-1.
> thanks
Stopping processing here.
Please
Source: log4cpp
Version: Missing Dependencies
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
at link time log4cpp produce this errors:
libtool: link: g++ -g -O2 -fdebug-prefix-map=/build/bitz-server-1.0.0=. -fPIE
- -fstack-protector-strong -Wformat
Hello,
Peter Keel, on Fri 26 Aug 2016 12:32:12 +0200, wrote:
> Downgraded to these:
>
> libatk-bridge2.0-0_2.14.0-2_amd64.deb
> libatk-wrapper-java_0.30.5-1_all.deb
> libatk-wrapper-java-jni_0.30.5-1_amd64.deb
Well, these are very old, and have other issues. The java wrapping
has been quite
Processing commands for cont...@bugs.debian.org:
> tags 833950 - pending
Bug #833950 [portaudio19] libasound2: brltty-espeak stops working with 1.1.2-1
Removed tag(s) pending.
> retitle 833950 libportaudio2: brltty-espeak stops working with libasound2
> 1.1.2-1
Bug #833950 [portaudio19]
Control: reassign -1 portaudio19
Hello,
Chris Brannon, on Thu 18 Aug 2016 11:32:40 -0700, wrote:
> I'm almost certain that the problem lies with portaudio, rather than
> libasound. It's described in my message to the portaudio list, found
> here:
>
>
On Mon, 22 Aug 2016 11:53:51 +0200 (CEST), Santiago Vila said:
> This package does no longer build from source because the iconc
> package does no longer exist (I'm not providing a build log, but this
> is very easy to check).
[...]
> So, I believe the attached patch should fix
Processing control commands:
> reassign -1 portaudio19
Bug #833950 [libasound2] libasound2: brltty-espeak stops working with 1.1.2-1
Bug reassigned from package 'libasound2' to 'portaudio19'.
No longer marked as found in versions alsa-lib/1.1.2-1.
Ignoring request to alter fixed versions of bug
I will package that soon(tm), maybe tonight. Sorry for missing that.
Richard
Sent by mobile; excuse my brevity.
On Fri, Jul 29, 2016 at 10:53:35AM +0200, LABBE Corentin wrote:
> Hello
Hi Corentin,
> The major problem seems the absence of home directory and not dying if
> TEMPYASATDIR does not exists.
> I will try to solve it by a fallback to /tmp/
can you upload a fix for this RC bug in your package?
>
On Fri, 26 Aug 2016, Richard Hartmann wrote:
>Jftr, if I can help with a new package or build, do let me know.
well -- there was also a new release of annex since last version in sid
6.20160808
FWIW I just verified that snapshot past it (current master) builds fine
on stretch
--
Your message dated Fri, 26 Aug 2016 18:49:17 +
with message-id
and subject line Bug#834677: fixed in refcard 9.0.2
has caused the Debian Bug report #834677,
regarding refcard: FTBFS in testing (xelatex compilation failed)
to be marked as done.
This means
Jftr, if I can help with a new package or build, do let me know.
Richard
Sent by mobile; excuse my brevity.
On Wed, Jul 20, 2016 at 05:24:06PM -0400, Scott Kitterman wrote:
> On Tuesday, January 19, 2016 08:13:48 PM you wrote:
> > Package: qwtplot3d
> > Version: 0.2.7+svn191-9
> > Severity: important
> > User: debian-...@lists.debian.org
> > Usertags: ftbfs-gcc-6 gcc-6-symbols
> >
> > This package
Processing commands for cont...@bugs.debian.org:
> block 835170 with 835514
Bug #835170 [release.debian.org] transition: protobuf
835170 was blocked by: 835425 835433 835427 835266 835430 822380 835290 835429
835435 835302 809290 811917
835170 was not blocking any bugs.
Added blocking bug(s) of
On Fri, 26 Aug 2016, Yaroslav Halchenko wrote:
> > Note 2: There is at least another package which broke after new git entered
> > testing.
> > It's git-build-recipe, Bug #835526. Maybe there is a common reason for
> > both packages to fail.
> FWIW -- #835526 is probably unrelated to this
On Fri, 26 Aug 2016 14:36:00 +0200 Markus Koschany wrote:
thanks for fixing #835358 so quickly. Unfortunately there is another
issue with the pom.xml file now. java/core/pom.xml lists junit and
easymock artifacts as dependencies but libprotobuf-java does not
depend on these packages. This causes
Processing commands for cont...@bugs.debian.org:
> affects 835514 src:libphonenumber src:osmosis
Bug #835514 [libprotobuf-java] libprotobuf-java: junit and easymock
dependencies should only be required for tests
Added indication that 835514 affects src:libphonenumber and src:osmosis
> thanks
On Fri, 26 Aug 2016, Yaroslav Halchenko wrote:
> > > Thank you Santiago for the report! I believe it is due to outdated
> > > git-annex in testing, which didn't migrate solely due to FTBFS on s390x.
> > > I will request gb for it -- could have been a spurious/toolchain issue.
> > > CCing
Processing control commands:
> severity -1 serious
Bug #835532 [postgrey] default config directory is /etc/postfix, not
/etc/postgrey
Severity set to 'serious' from 'important'
> retitle -1 default config dir change from /etc/postgrey to /etc/postfix not
> handled
Bug #835532 [postgrey] default
Quoting Luca Falavigna (2014-06-10 16:40:39)
> Your debian/copyright file contains lots of FIXMEs.
Status update: Most FIXMEs have been addressed now, through analysis of
the history of those files (documented as comments for each file in
debian/copyright).
Remaining are 2 FIXMEs.
One is
Processing commands for cont...@bugs.debian.org:
> forwarded 751121 https://github.com/Netatalk/Netatalk/issues/74
Bug #751121 [src:netatalk] Please fix "FIXME" statements in copyright file
Set Bug forwarded-to-address to
'https://github.com/Netatalk/Netatalk/issues/74'.
> thanks
Stopping
On Fri, 26 Aug 2016, Santiago Vila wrote:
> On Fri, Aug 26, 2016 at 12:22:20PM -0400, Yaroslav Halchenko wrote:
> > Thank you Santiago for the report! I believe it is due to outdated
> > git-annex in testing, which didn't migrate solely due to FTBFS on s390x.
> > I will request gb for it --
Your message dated Fri, 26 Aug 2016 18:04:04 +
with message-id
and subject line Bug#834999: fixed in libyaml-libyaml-perl 0.63-1
has caused the Debian Bug report #834999,
regarding YAML::XS generates broken multiline strings
to be marked as done.
This
On Fri, 26 Aug 2016, Santiago Vila wrote:
> On Fri, Aug 26, 2016 at 12:22:20PM -0400, Yaroslav Halchenko wrote:
> > Thank you Santiago for the report! I believe it is due to outdated
> > git-annex in testing, which didn't migrate solely due to FTBFS on s390x.
> > I will request gb for it --
Source: request-tracker4
Version: 4.2.12-6
Severity: serious
Justification: FTBFS
Now that libgnupg-interface-perl has been fixed to use gpg1 (
see #834281) request-tracker4 still FTBFS because it configures
GnuPG::Interface to use 'gpg' as the binary anyway.
I intend to patch out this
Package: postgrey
Version: 1.36-2
Severity: serious
Dear Maintainer,
After upgrade to 1.36-2, postgrey fails to start with the following message:
FATAL: ERROR: can't open lock file: /var/spool/postfix/postgrey/postgrey.lock
This is because the default database directory was changed from
On Fri, 26 Aug 2016 09:26:22 +0300, Niko Tyni wrote:
> > The problem is that we have a lintian ftp-master autoreject problem:
> > E: libyaml-libyaml-perl: embedded-library
> > usr/lib/perl5/auto/YAML/XS/LibYAML/LibYAML.so: libyaml
>
> Making it possible to use a system libyaml is discussed in
>
On Fri, Aug 26, 2016 at 03:53:03PM +, Santiago Vila wrote:
> ERROR:
> gitbuildrecipe.tests.test_recipe.BuildTreeTests.test_build_tree_merge_unrelated
[...]
> This used to build ok, so this failure seems related to git 2.9.3,
> which is in testing since a few days.
Thanks for your report.
Hi,
gregor herrmann:
> It seems we have (had) 3 packages where tests fails with gnupg2:
> #834522 libgnupg-perl
> #835075 libmail-gnupg-perl
> #834281 libgnupg-interface-perl
> The third one was fixed by intri by making it use gnupg1. Should we
> do the same for the two other bugs?
I'm in
Processing commands for cont...@bugs.debian.org:
> forwarded 835075 https://rt.cpan.org/Ticket/Display.html?id=117239
Bug #835075 [src:libmail-gnupg-perl] libmail-gnupg-perl: FTBFS: Failed 1/10
test programs. 0/4 subtests failed.
Set Bug forwarded-to-address to
It seems we have (had) 3 packages where tests fails with gnupg2:
#834522 libgnupg-perl
#835075 libmail-gnupg-perl
#834281 libgnupg-interface-perl
The third one was fixed by intri by making it use gnupg1. Should we
do the same for the two other bugs?
Cheers,
gregor
--
.''`. Homepage
Processing control commands:
> tag -1 + patch
Bug #835413 [pygobject] pygobject: wrong enum to hash conversion on 64-bit big
endian
Added tag(s) patch.
--
835413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
control: tag -1 + patch
On 2016-08-25 14:16, Aurelien Jarno wrote:
> On 2016-08-25 09:15, Aurelien Jarno wrote:
> > I have tried to debug the issue, and I came to the same conclusion. The
> > problem happens in the test-py-lookup.py test when creating a schema
> > with Secret.Schema.new. The
On Fri, Aug 26, 2016 at 12:22:20PM -0400, Yaroslav Halchenko wrote:
> Thank you Santiago for the report! I believe it is due to outdated
> git-annex in testing, which didn't migrate solely due to FTBFS on s390x.
> I will request gb for it -- could have been a spurious/toolchain issue.
> CCing
Source: theano
Version: 0.8.2-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Current theano now fails also on amd64:
FAIL: test_csr_correct_output_faster_than_scipy
(theano.sparse.tests.test_basic.test_structureddot)
Your message dated Fri, 26 Aug 2016 16:37:06 +
with message-id
and subject line Bug#834679: fixed in surefire 2.17-3
has caused the Debian Bug report #834679,
regarding surefire: FTBFS in testing (1 required artifact is missing)
to be marked as done.
This
Your message dated Fri, 26 Aug 2016 16:36:21 +
with message-id
and subject line Bug#830060: fixed in ruby-appraisal 0.5.1-2
has caused the Debian Bug report #830060,
regarding Could not find 'appraisal'
to be marked as done.
This means that you claim that
Control: tags -1 + pending
Hi Lucas, Santiago,
Sorry I just noticed this bug.
Thanks Santiago, I tested and added your patch to the git repository.
As I don't have upload rights in Debian, Alexander Wirt will have a
look when he has some time.
There are a lot of changes since the last release in
Processing control commands:
> tags -1 + pending
Bug #831965 [src:asciidoc] asciidoc: FTBFS with dpkg-buildpackage -A:
doc/testasciidoc.1: No such file or directory at /usr/bin/dh_installman line
131.
Added tag(s) pending.
--
831965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831965
Your message dated Fri, 26 Aug 2016 16:29:38 +
with message-id
and subject line Bug#834913: fixed in libslf4j-java 1.7.21-2
has caused the Debian Bug report #834913,
regarding libslf4j-java: FTBFS too much often (failing tests)
to be marked as done.
This
Your message dated Fri, 26 Aug 2016 16:21:51 +
with message-id
and subject line Bug#834833: fixed in javassist 1:3.20.0-2
has caused the Debian Bug report #834833,
regarding javassist: FTBFS too much often (failing tests)
to be marked as done.
This means
Your message dated Fri, 26 Aug 2016 16:20:36 +
with message-id
and subject line Bug#834890: fixed in commons-math 2.2-6
has caused the Debian Bug report #834890,
regarding commons-math: FTBFS with probability > 0 in a deliberate way
to be marked as done.
Thank you Santiago for the report! I believe it is due to outdated
git-annex in testing, which didn't migrate solely due to FTBFS on s390x.
I will request gb for it -- could have been a spurious/toolchain issue.
CCing git-annex Debian maintainer
Cheers!
On Fri, 26 Aug 2016, Santiago Vila wrote:
Package: src:datalad
Version: 0.2.3-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:git-build-recipe
Version: 0.3.2
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Processing control commands:
> severity -1 normal
Bug #834682 [src:mina2] mina2: FTBFS too much often (failing tests)
Severity set to 'normal' from 'serious'
> tags -1 unreproducible
Bug #834682 [src:mina2] mina2: FTBFS too much often (failing tests)
Added tag(s) unreproducible.
--
834682:
Control: severity -1 normal
Control: tags -1 unreproducible
On Wed, 17 Aug 2016 23:50:03 + Santiago Vila wrote:
> Package: src:mina2
> Version: 2.0.13-1
> Severity: serious
>
> Dear maintainer:
>
> I tried to build this package with "dpkg-buildpackage -A"
> (which is
Package: libprotobuf-java
Version: 3.0.0-5
Severity: serious
Tags: patch
Hello,
thanks for fixing #835358 so quickly. Unfortunately there is another
issue with the pom.xml file now. java/core/pom.xml lists junit and
easymock artifacts as dependencies but libprotobuf-java does not
depend on these
Hi
Santiago Vila píše v St 17. 08. 2016 v 22:20 +:
> Package: src:django-taggit
> Version: 0.20.2-1
> Severity: serious
>
> Dear maintainer:
>
> I tried to build this package with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
Your message dated Fri, 26 Aug 2016 12:03:59 +
with message-id
and subject line Bug#834241: fixed in open-iscsi 2.0.873+git1.4c1f2d90-2
has caused the Debian Bug report #834241,
regarding open-iscsi-udeb: uninstallable, depends on libmount1-udeb
to be
Processing control commands:
> tags -1 + pending
Bug #834241 [open-iscsi-udeb] open-iscsi-udeb: uninstallable, depends on
libmount1-udeb
Added tag(s) pending.
--
834241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags -1 + pending
On 08/13/2016 10:22 PM, Cyril Brulebois wrote:
> Christian Seiler (2016-08-13):
>> So I'd probably want to do the following:
>>
>> Step 1: build open-iscsi twice, once with libmount patched
>> out (closing this bug)
>> Step 2: file bugs
Control: found -1 0.1.8-4
On Wed, Feb 17, 2016 at 12:02:54 +0100, Wouter Verhelst wrote:
> Package: libengine-pkcs11-openssl
> Version: 0.2.1-1
> Severity: grave
> Justification: makes the package in question unusable
>
> Hi,
>
> After installing libengine-pkcs11-openssl, the following
Processing control commands:
> found -1 0.1.8-4
Bug #815004 {Done: Eric Dorland } [libengine-pkcs11-openssl]
Engine is installed at wrong location
Marked as found in versions engine-pkcs11/0.1.8-4.
--
815004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815004
Debian Bug
Processing commands for cont...@bugs.debian.org:
> unarchive 815004
Bug #815004 {Done: Eric Dorland } [libengine-pkcs11-openssl]
Engine is installed at wrong location
Unarchived Bug 815004
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
815004:
Addendum:
Downgraded to these:
libatk-bridge2.0-0_2.14.0-2_amd64.deb
libatk-wrapper-java_0.30.5-1_all.deb
libatk-wrapper-java-jni_0.30.5-1_amd64.deb
and installed that (incidentally, there's no debug library for
the 2.20.1-3 version that would really need one):
Your message dated Fri, 26 Aug 2016 10:29:22 +
with message-id
and subject line Bug#835433: fixed in ola 0.10.2-2
has caused the Debian Bug report #835433,
regarding ola: FTBFS with protobuf 3.0.0 (multiple issues)
to be marked as done.
This means that
Your message dated Fri, 26 Aug 2016 10:27:11 +
with message-id
and subject line Bug#832479: fixed in mat 0.6.1-3
has caused the Debian Bug report #832479,
regarding ValueError: Namespace Poppler not available
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> merge 835341 835477
Bug #835341 [mutt] mutt 1.6.2-3 has wrong dependencies
Bug #835477 [mutt] depends on libnotmuch3, not available in unstable
Added tag(s) pending.
Merged 835341 835477
> thanks
Stopping processing here.
Please contact me if
On Mon, 25 Jan 2016, Michael Tautschnig wrote:
> java.text.ParseException: Unparseable date: "Wed Oct 4 15:42:47 2006"
This happened to me today while checking for "dpkg-buildpackage -A" bugs.
I attach my build log.
> The full build log is attached; please do let me know if the problem is
>
Package: pyqso
Version: 0.3-1
Severity: grave
pyqso fails to start with the following console log.
/usr/bin/pyqso:20: PyGIWarning: Gtk was imported without specifying a version
first. Use gi.require_version('Gtk', '3.0') before import to ensure that the
right version gets loaded.
from
Hi Petter,
Your patch works for me.
> Is there a recipe for how to easily test this?
Not really. I use containers and tcpdump -i eth0 with some extra filters, but
you might have some luck with (a recent version of) nsntrace.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'`
Hi Carl,
2016-08-24 22:55 GMT+02:00 Carl Eugen Hoyos :
> Hi!
>
> First, please understand that so far, no ABI breakage between
> FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of
> non-public api (that we decided to work-around for 3.1.1).
OK, then assume that Kodi uses
Package: mutt
Version: 1.6.2-3
Severity: serious
Hi,
My system wants to update mutt to 1.6.2-3, but that depends on
libnotmuch3, whereas in unstable, that should now be libnotmuch4
instead.
As such, it tries to install libnotmuch3 from jessie, which wants to
pull in libxapian22 (conflicting
Processing commands for cont...@bugs.debian.org:
> severity 818380 normal
Bug #818380 [clang-3.7] clang-3.7: __builtin_return_address() segfaults on s390x
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
818380:
Control: tags -1 pending
On Thu, Aug 25, 2016 at 4:06 PM, Aaron M. Ucko wrote:
> Source: openvdb
> Version: 3.2.0-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Builds of openvdb for 32-bit architectures such as i386
Control: tags -1 + patch
[Chris Lamb]
> This appears to be caused by (at least) Sphinx's intersphinx mapping
> extension.
> Please see #830186 for more information, including suggestions on how to fix
> it.
Here is a patch I believe should fix the problem. Not quite sure how to verify
it.
Is
Processing control commands:
> tags -1 pending
Bug #835419 [src:openvdb] openvdb: FTBFS (32-bit): TestMultiResGrid.cc uses UL
for size_t constants
Added tag(s) pending.
--
835419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835419
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> tags -1 + patch
Bug #833411 [src:pam-python] pam-python: accesses the internet during build
Added tag(s) patch.
--
833411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 26 Aug 2016 07:18:34 +
with message-id
and subject line Bug#834301: fixed in ruby-fog-rackspace 0.1.1-2
has caused the Debian Bug report #834301,
regarding ruby-fog-rackspace and ruby-fog: error when trying to install together
to be
Your message dated Fri, 26 Aug 2016 08:44:59 +0200
with message-id <851a5456-7e8f-d3f5-b6d3-9caf4fb00...@adrianheine.de>
and subject line
has caused the Debian Bug report #824740,
regarding telepathy-ring: FTBFS: cp: cannot stat './AUTHORS--no-act': No such
file or directory
to be marked as
Your message dated Fri, 26 Aug 2016 08:44:59 +0200
with message-id <851a5456-7e8f-d3f5-b6d3-9caf4fb00...@adrianheine.de>
and subject line
has caused the Debian Bug report #665616,
regarding telepathy-ring: Including individual glib headers no longer supported
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> reassign 834301 ruby-fog-rackspace
Bug #834301 [ruby-fog,ruby-fog-rackspace] ruby-fog-rackspace and ruby-fog:
error when trying to install together
Bug reassigned from package 'ruby-fog,ruby-fog-rackspace' to
'ruby-fog-rackspace'.
Ignoring
On 18 August 2016 at 20:50, Paul Gevers wrote:
> @Graham, I suggest you also get this done in Ubuntu soon, such that the
> next release has the latest fpc from Debian again.
Steve Langasek starting working through LP: #1562480 [1] and removing
powerpc binaries.
He found a
On Fri, Aug 26, 2016 at 12:10:29AM +0200, gregor herrmann wrote:
> On Sun, 21 Aug 2016 13:18:33 +0200, Marco d'Itri wrote:
>
> > YAML::XS adds an extra \n at the end of each line.
> > The YAML module cannot read the generated files.
> > Test case attached.
>
> This seems to be fixed in newer
96 matches
Mail list logo