Your message dated Mon, 22 Aug 2016 06:48:36 +
with message-id
and subject line Bug#834907: fixed in gitlab 8.9.0+dfsg-10
has caused the Debian Bug report #834907,
regarding gitlab: dependency on rails is too strict; breaks on every update
to be marked as done.
This means that you claim that
Your message dated Mon, 22 Aug 2016 06:18:52 +
with message-id
and subject line Bug#834490: fixed in postgrey 1.36-2
has caused the Debian Bug report #834490,
regarding postgrey: fails to configure: missing Depends on libnetaddr-ip-perl
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> affects 834281 signing-party
Bug #834281 [libgnupg-interface-perl] libgnupg-interface-perl: FTBFS, test
failures, probably gpg2
Added indication that 834281 affects signing-party
> thanks
Stopping processing here.
Please contact me if you need a
Processing commands for cont...@bugs.debian.org:
> severity 831525 serious
Bug #831525 [src:libretro-mupen64plus] [libretro-mupen64plus] Remove copies of
mupen64plus-*
Severity set to 'serious' from 'wishlist'
> bye
Unknown command or malformed arguments to command.
> Then please integrate your c
Hi,
I have uploaded the patch to upstream's code review system [1]
[1]: https://android-review.googlesource.com/260250
Your message dated Mon, 22 Aug 2016 04:21:10 +
with message-id
and subject line Bug#833773: fixed in freeorion 0.4.5+git20160707-2
has caused the Debian Bug report #833773,
regarding freeorion: FTBFS with boost1.61
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Mon, 22 Aug 2016 04:20:25 +
with message-id
and subject line Bug#834488: fixed in ardour 1:5.0~dfsg-2
has caused the Debian Bug report #834488,
regarding ardour-data and ardour: error when trying to install together
to be marked as done.
This means that you claim that the p
Source: jade
Version: 1.2.1-49
Severity: serious
For example, if I rebuild jade locally, then try to build
dictionaries-common using the rebuilt jade, it gives an error:
jade -t sgml -V nochunks -d policy/html.dsl \
/usr/share/sgml/declaration/xml.decl policy/dsdt-policy.xml >
policy/dsdt-polic
Ops, broken link, here:
https://mentors.debian.net/debian/pool/main/libr/libretro-desmume/libretro-desmume_0.9.11+git20160819+dfsg1-1.dsc
sergio-br2
Your message dated Sun, 21 Aug 2016 23:19:27 +
with message-id
and subject line Bug#811611: fixed in libclaw 1.7.4-1
has caused the Debian Bug report #811611,
regarding FTBFS with GCC 6: cannot convert x to y
to be marked as done.
This means that you claim that the problem has been dealt with
Hi!
There's a fix right here:
https://mentors.debian.net/debian/pool/main/libr/libretro-desmume/libretro-desmume_0.9.11+git20160821+dfsg1-1.dsc
Upstream builds with -fpermissive now.
regards,
sergio-br2
On Thu, 14 Jul 2016 09:07:49 +0200 Lucas Nussbaum wrote:
> Source: libretro-desmume
> V
On 08/18/2016 12:21 AM, Santiago Vila wrote:
> xsltc.java_cup:
> [echo] java_cup preparsing
> [java] Exception in thread "main" java.lang.Error: Error: could not
> match input
> [java] at java_cup.Lexer.zzScanError(Lexer.java:728)
> [java] at java_cup.Lexer.next_token(Lexe
Your message dated Sun, 21 Aug 2016 22:19:25 +
with message-id
and subject line Bug#834978: fixed in cfengine3 3.9.1-3
has caused the Debian Bug report #834978,
regarding cfengine3: build log flood until ENOSPC
to be marked as done.
This means that you claim that the problem has been dealt wi
Thank you for working on this patch!
Me and rustybird agreed on the following. Please consider using the
following as netfilter-persistent.service.
#
[Unit]
Description=netfilter persistent configuration
DefaultDependencies=no
Wants=network-pre.target
Before=network-pre.target
Wants=system
A way to fix this would be to not bring up the network if the firewall
fails. I suggest adding the following file:
/lib/systemd/system/networking.service.d/30_netfilter-persistent.conf
With the following content:
[Unit]
## Fail Closed Mechanism.
## When the firewall systemd service failed, do no
Processing commands for cont...@bugs.debian.org:
> severity 831525 wishlist
Bug #831525 [src:libretro-mupen64plus] [libretro-mupen64plus] Remove copies of
mupen64plus-*
Severity set to 'wishlist' from 'serious'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Processing control commands:
> forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77300
Bug #834147 [src:binutils] binutils: breaks mips and mipsel link of blender
Set Bug forwarded-to-address to
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77300'.
--
834147: http://bugs.debian.org/cgi-
control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77300
On 2016-08-17 15:21, James Cowgill wrote:
> Hi,
>
> On Sun, 14 Aug 2016 13:04:18 + Mattia Rizzolo wrote:
> > Control: reopen -1
> > control: found -1 2.27-5
> >
> > On Sun, Aug 14, 2016 at 01:02:28PM +0200, Matthias Kl
Your message dated Sun, 21 Aug 2016 19:48:59 +
with message-id
and subject line Bug#834888: fixed in tempest 1:12.1.0-3
has caused the Debian Bug report #834888,
regarding tempest: FTBFS in testing (ImportError: No module named pep8)
to be marked as done.
This means that you claim that the pr
Your message dated Sun, 21 Aug 2016 19:48:53 +
with message-id
and subject line Bug#834888: fixed in tempest 6-2
has caused the Debian Bug report #834888,
regarding tempest: FTBFS in testing (ImportError: No module named pep8)
to be marked as done.
This means that you claim that the problem h
Package: src:golang-fsnotify
Version: 1.3.0-3
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 commands for cont...@bugs.debian.org:
> tag 834888 pending
Bug #834888 [src:tempest] tempest: FTBFS in testing (ImportError: No module
named pep8)
Ignoring request to alter tags of bug #834888 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you
Processing control commands:
> tags 817549 + patch
Bug #817549 [src:libropkg-perl] libropkg-perl: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817549 + pending
Bug #817549 [src:libropkg-perl] libropkg-perl: Removal of debhelper compat 4
Added tag(s) pending.
--
817549: http://bugs.de
tag 834888 pending
thanks
Hello,
Bug #834888 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=openstack/tempest.git;a=commitdiff;h=d86fd2f
---
commit d86fd2fd7eb7ed84268e0f7ff6cdd5a16709
Control: tags 817549 + patch
Control: tags 817549 + pending
Dear maintainer,
I've prepared an NMU for libropkg-perl (versioned as 0.4-1.2) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage https://info.comodo.priv.at/ - OpenPGP
Processing control commands:
> tags 759979 + patch
Bug #759979 [src:simba] simba: FTBFS: RoPkg::Rsync ...failed! (needed)
Ignoring request to alter tags of bug #759979 to the same tags previously set
> tags 759979 + pending
Bug #759979 [src:simba] simba: FTBFS: RoPkg::Rsync ...fa
Control: tags 759979 + patch
Control: tags 759979 + pending
Control: tags 834356 + patch
Control: tags 834356 + pending
Dear maintainer,
I've prepared an NMU for simba (versioned as 0.8.4-4.3) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
Regards.
--
.
On Sun, Aug 21, 2016 at 05:13:51PM +0300, Niko Tyni wrote:
> On Sun, Aug 21, 2016 at 03:13:23PM +0200, gregor herrmann wrote:
> > On Sun, 21 Aug 2016 15:27:34 +0300, Niko Tyni wrote:
>
> > "\x{00c2}" does not map to ascii at
> > /usr/share/perl/5.22/ExtUtils/MakeMaker.pm line 1187.
> > "\x{00a1}"
Your message dated Sun, 21 Aug 2016 19:33:43 +
with message-id
and subject line Bug#834887: fixed in python-keystoneclient 1:2.3.1-3
has caused the Debian Bug report #834887,
regarding python-keystoneclient: FTBFS in testing (ImportError: No module named
pep8)
to be marked as done.
This mean
Processing control commands:
> tags 759979 + patch
Bug #759979 [src:simba] simba: FTBFS: RoPkg::Rsync ...failed! (needed)
Added tag(s) patch.
> tags 759979 + pending
Bug #759979 [src:simba] simba: FTBFS: RoPkg::Rsync ...failed! (needed)
Added tag(s) pending.
> tags 834356 + patch
Hi,
This is not a valid bug. The libretro port of mupen64plus have many
changes, it also includes changes in the graphic plugins like rice and
glide64 and others.
i.e., you can't use the vanilla mupen plugins in the libretro port.
Take a look at the commits in the
https://github.com/libretr
Processing commands for cont...@bugs.debian.org:
> tag 834888 pending
Bug #834888 [src:tempest] tempest: FTBFS in testing (ImportError: No module
named pep8)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
834888: http://bugs.debian.org/cgi-
tag 834888 pending
thanks
Hello,
Bug #834888 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=openstack/tempest.git;a=commitdiff;h=f4cec04
---
commit f4cec048f077144af09ba4698eeb78a6effa
tag 834888 pending
thanks
Hello,
Bug #834888 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=openstack/tempest.git;a=commitdiff;h=53eae20
---
commit 53eae20365f8bfdac111b5635d2144a0d002
Processing commands for cont...@bugs.debian.org:
> tag 834888 pending
Bug #834888 [src:tempest] tempest: FTBFS in testing (ImportError: No module
named pep8)
Ignoring request to alter tags of bug #834888 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you
Processing commands for cont...@bugs.debian.org:
> tag 834887 pending
Bug #834887 [src:python-keystoneclient] python-keystoneclient: FTBFS in testing
(ImportError: No module named pep8)
Ignoring request to alter tags of bug #834887 to the same tags previously set
> thanks
Stopping processing here
tag 834887 pending
thanks
Hello,
Bug #834887 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=openstack/python-keystoneclient.git;a=commitdiff;h=37abec2
---
commit 37abec2989f1bee61c92d
Processing commands for cont...@bugs.debian.org:
> tag 834887 pending
Bug #834887 [src:python-keystoneclient] python-keystoneclient: FTBFS in testing
(ImportError: No module named pep8)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
834887:
tag 834887 pending
thanks
Hello,
Bug #834887 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=openstack/python-keystoneclient.git;a=commitdiff;h=734729d
---
commit 734729d337c4c69ab83d6
severity 819452 important
thanks
On Fri, Aug 19, 2016 at 05:06:27PM +0200, Santiago Vila wrote:
> severity 819452 serious
> thanks
>
> I could not build this package while checking for "dpkg-buildpackage -A",
> and it also fails on reproducible builds:
>
> https://tests.reproducible-builds.org/d
Processing commands for cont...@bugs.debian.org:
> severity 819452 important
Bug #819452 [src:golang-fsnotify] golang-fsnotify: FTBFS, not working at all in
ppc64el
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
819452:
Hi Santiago,
Thanks for reporting the bug.
I've pushed a fix for it to the master branch, http://deb.li/rKfh
RAM was not an issue here.
The buildscripts divided the number of available processors by 2,
however that obviously wouldn't work for a single processor so I added a
check to not do that w
Processing control commands:
> severity -1 serious
Bug #831418 [src:zendframework] EOL: not to be released with Stretch
Severity set to 'serious' from 'important'
--
831418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with prob
Your message dated Sun, 21 Aug 2016 18:48:39 +
with message-id
and subject line Bug#834980: fixed in cargo 0.11.0-2
has caused the Debian Bug report #834980,
regarding cargo: FTBFS in testing (linking error)
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sun, 21 Aug 2016 17:22:20 +
with message-id
and subject line Bug#826042: fixed in spyder 3.0.0~b4+dfsg1-1~exp1
has caused the Debian Bug report #826042,
regarding Spyder crashes on start
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Sun, 21 Aug 2016 17:22:20 +
with message-id
and subject line Bug#797069: fixed in spyder 3.0.0~b4+dfsg1-1~exp1
has caused the Debian Bug report #797069,
regarding spyder: QT_API 1 -> 2 migration broke reverse dependencies
to be marked as done.
This means that you claim that
Your message dated Sun, 21 Aug 2016 17:22:20 +
with message-id
and subject line Bug#784613: fixed in spyder 3.0.0~b4+dfsg1-1~exp1
has caused the Debian Bug report #784613,
regarding [spyder] Qt4's WebKit removal
to be marked as done.
This means that you claim that the problem has been dealt w
Source: deluge
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
Deluge is known not to work with any version of libtorrent after 1.0.9. Of
course 1.1.0 was just uploaded to unstable, so it breaks.
It will not be fixed on Deluge's side for quite some time,
Processing commands for cont...@bugs.debian.org:
> limit source request-tracker4
Limiting to bugs with field 'source' containing at least one of
'request-tracker4'
Limit currently set to 'source':'request-tracker4'
> tags 832829 + pending
Bug #832829 [src:request-tracker4] request-tracker4: FTBF
Processing commands for cont...@bugs.debian.org:
> tags 832829 + fixed-upstream
Bug #832829 [src:request-tracker4] request-tracker4: FTBFS: Tests failures
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
832829: http://bugs.debian.org/c
Processing commands for cont...@bugs.debian.org:
> forwarded 835037
> https://groups.google.com/forum/#!msg/ceres-solver/TbO3WDTiCGU/hj0q6J7BBgAJ
Bug #835037 [src:ceres-solver] ceres-solver: FTBFS with eigen3 >> 3.3~beta1
Set Bug forwarded-to-address to
'https://groups.google.com/forum/#!msg/cer
Source: chasen
Version: 2.4.5-25
Severity: serious
>From my pbuilder build log:
...
dh_fixperms
dh_strip
dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the
symb
Source: ceres-solver
Version: 1.11.0~dfsg0-5
Severity: serious
Tags: upstream
Justification: Policy 2.1
As found out through reproducible builds, ceres-solver FTBFS since
eigen3 3.3~beta2 was uploaded:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ceres-solver_1.11.0~dfsg0-5.r
Source: burp
Version: 1.4.40-2
Severity: serious
>From my pbuilder build log:
...
g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing
-fno-exceptions -fno-rtti -fno-strict-aliasing -fno-exceptions
-fno-rtti -I. -I.. -g -O2 -fdebug-prefix-map=/build/burp-1.4.40=.
-fstack-protector-st
Processing commands for cont...@bugs.debian.org:
> close 811987
Bug #811987 [ceres-solver] ceres-solver: FTBFS with GCC 6: the compiler can
assume...
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
811987: http://bugs.debian.org/cgi-bin/bugrepo
Source: binutils-mingw-w64
Version: 6.6
Severity: serious
>From my pbuilder build log:
...
# Revert gc-sections support for COFF and PE (#813144)
patch -d /build/binutils-mingw-w64-6.6/upstream -R -p1 <
debian/patches/coff-pe-gc-sections.patch
patching file bfd/coffcode.h
Hunk #2 succeeded at 599
Processing commands for cont...@bugs.debian.org:
> notfound 811987 1.11.0~dfsg0-5
Bug #811987 [ceres-solver] ceres-solver: FTBFS with GCC 6: the compiler can
assume...
There is no source info for the package 'ceres-solver' at version
'1.11.0~dfsg0-5' with architecture ''
Unable to make a source
What broke the build of geoip is that gcc 6 changed the default
C++ standard from C++98 to C++14.
Note that this just changed the default, when told to process C++98 code
gcc 6 does not differ in any significant way from gcc 5.
Not all valid C++98 code is also valid C++11 and C++14 code.
ompl
Source: bbpager
Version: 0.4.7-3
Severity: serious
>From my pbuilder build log:
...
x86_64-linux-gnu-g++ -Wall -g -O2 -I/usr/include/bt
-I/usr/include/freetype2 -s -lSM -lICE -lX11 -o bbpager bbpager.o
main.o Baseresource.o resource.o wminterface.o pager.o desktop.o
-lXext -lbt -fPIE -pie -
Processing commands for cont...@bugs.debian.org:
> severity 831825 important
Bug #831825 [gcompris] gcompris: Crash when i click on menu
Severity set to 'important' from 'grave'
> tags 831825 + unreproducible moreinfo
Bug #831825 [gcompris] gcompris: Crash when i click on menu
Added tag(s) unrepro
severity 831825 important
tags 831825 + unreproducible moreinfo
reassign 831825 gcompris-qt
thanks
Let's lower the severity as it seems not to impact all users.
Trying to reproduce, I'm puzzled by the description, as gcompris does not
have a bottom-left menu, although gompris-qt has one. I'm th
Processing commands for cont...@bugs.debian.org:
> retitle 710696 libsoup2.4 FTBFS too much often (failing tests)
Bug #710696 [src:libsoup2.4] libsoup2.4: FTBFS with test failures
Changed Bug title to 'libsoup2.4 FTBFS too much often (failing tests)' from
'libsoup2.4: FTBFS with test failures'.
>
Source: hhvm
Version: 3.12.1+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
Hi,
the following vulnerabilities were published for hhvm. The respective
upstream commits can be found in the security-tracker references.
CVE-2014-9709[0]:
| The GetCode_ function in g
On Sun, Aug 21, 2016 at 03:13:23PM +0200, gregor herrmann wrote:
> On Sun, 21 Aug 2016 15:27:34 +0300, Niko Tyni wrote:
> "\x{00c2}" does not map to ascii at
> /usr/share/perl/5.22/ExtUtils/MakeMaker.pm line 1187.
> "\x{00a1}" does not map to ascii at
> /usr/share/perl/5.22/ExtUtils/MakeMaker.pm
Your message dated Sun, 21 Aug 2016 16:09:25 +0200
with message-id
and subject line Fixed in grib-api (1.16.0-6)
has caused the Debian Bug report #834634,
regarding grib-api: Incorrect library path in CMake module
(/usr/lib/lib/libgrib_api.so.0)
to be marked as done.
This means that you claim th
Processing commands for cont...@bugs.debian.org:
> fixed 834634 grib-api/1.16.0-6
Bug #834634 [src:grib-api] grib-api: Incorrect library path in CMake module
(/usr/lib/lib/libgrib_api.so.0)
Marked as fixed in versions grib-api/1.16.0-6.
> thanks
Stopping processing here.
Please contact me if you
Your message dated Sun, 21 Aug 2016 13:18:40 +
with message-id
and subject line Bug#833776: fixed in gnash 0.8.11~git20160608-1.1
has caused the Debian Bug report #833776,
regarding gnash: FTBFS with boost1.61
to be marked as done.
This means that you claim that the problem has been dealt wit
On Sun, 21 Aug 2016 15:27:34 +0300, Niko Tyni wrote:
> > > tags 834961 + confirmed
> > Bug #834961 [src:libvitacilina-perl] libvitacilina-perl: FTBFS too much
> > often (configure fails)
>
> Gregor: I assume this means you can reproduce it? I can't.
Oh, usually it's me who can't reproduce them
Your message dated Sun, 21 Aug 2016 12:33:59 +
with message-id
and subject line Bug#821992: fixed in icinga 1.13.3-3
has caused the Debian Bug report #821992,
regarding icinga: Build arch:all+arch:any but is missing build-{arch,indep}
targets
to be marked as done.
This means that you claim t
Processing control commands:
> severity -1 important
Bug #831418 [src:zendframework] EOL: not to be released with Stretch
Severity set to 'important' from 'serious'
--
831418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pr
On Sun, Aug 21, 2016 at 12:18:05AM +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
> > tags 834961 + confirmed
> Bug #834961 [src:libvitacilina-perl] libvitacilina-perl: FTBFS too much often
> (configure fails)
Gregor: I assume this means you can rep
Control: severity -1 important
On 25.07.2016 13:11, Markus Frosch wrote:
> Hey all,
> this is a interesting problem, while looking on the 3 dependent packages.
> (see below)
>
> We have 3 choices to go on:
>
> 1. Still provide zendframework 1 in a separated path, so it won't conflict
> with ZF
Your message dated Sun, 21 Aug 2016 12:20:19 +
with message-id
and subject line Bug#811964: fixed in htmlcxx 0.86-1.1
has caused the Debian Bug report #811964,
regarding htmlcxx: FTBFS with GCC 6: symbol changes
to be marked as done.
This means that you claim that the problem has been dealt w
Package: libyaml-libyaml-perl
Version: 0.41-6+b1
Severity: grave
YAML::XS adds an extra \n at the end of each line.
The YAML module cannot read the generated files.
Test case attached.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1,
Hello,
please can one of you take a look at the bug[1]?
The error looks like a missing dependency:
libtool: link: g++ -g -O2 -fdebug-prefix-map=/build/bitz-server-1.0.0=. -fPIE
-fstack-protector-strong -Wformat -Werror=format-security -fPIE -pie -Wl,-z
-Wl,relro -Wl,-z -Wl,now -o .libs/bitz-se
Your message dated Sun, 21 Aug 2016 11:18:30 +
with message-id
and subject line Bug#817364: fixed in asterisk-prompt-es-co 0.20070403-2
has caused the Debian Bug report #817364,
regarding asterisk-prompt-es-co: Removal of debhelper compat 4
to be marked as done.
This means that you claim that
Your message dated Sun, 21 Aug 2016 10:49:35 +
with message-id
and subject line Bug#828641: fixed in django-haystack 2.5.0-1
has caused the Debian Bug report #828641,
regarding FTBFS under Django 1.10
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Hello during the packaging I get this error message for the tests
==
ERROR: spyderlib.widgets.tests.test_array_builder
(unittest.loader.ModuleImportFailure)
--
I
Processing commands for cont...@bugs.debian.org:
> severity 832965 normal
Bug #832965 [shotwell] shotwell: crash at startup with syslog message
Severity set to 'normal' from 'grave'
> retitle 832965 shotwell: aborted on startup when running on French
Bug #832965 [shotwell] shotwell: crash at star
tag 828641 pending
thanks
Hello,
Bug #828641 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=python-modules/packages/django-haystack.git;a=commitdiff;h=5f1a488
---
commit 5f1a488fee6a9
Processing commands for cont...@bugs.debian.org:
> tag 828641 pending
Bug #828641 [django-haystack] FTBFS under Django 1.10
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
828641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828641
Debian
Your message dated Sun, 21 Aug 2016 10:23:01 +
with message-id
and subject line Bug#818809: fixed in guiqwt 3.0.2-2
has caused the Debian Bug report #818809,
regarding guiqwt: FTBFS with libc 2.23: non-floating-point argument in call to
function '__builtin_isnan'
to be marked as done.
This m
Package: src:bitz-server
Version: 1.0.0-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:
--
Package: src:ros-robot-model
Version: 1.12.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:sdformat
Version: 4.1.0-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:cargo
Version: 0.11.0-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:
---
Processing commands for cont...@bugs.debian.org:
> tags 834976 + patch
Bug #834976 [src:auto-apt-proxy] auto-apt-proxy: FTBFS: SC2039: In POSIX sh,
'local' is undefined
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
834976: http://bugs.debian
tags 834976 + patch
thanks
Patch attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/auto-apt-proxy b/auto-apt-proxy
index c822c43..d2a29ab 100755
--- a/auto-apt-proxy
+++ b/auto-apt-proxy
@@ -16,8 +16,8 @@ h
Source: cfengine3
Version: 3.9.1-2
Severity: serious
The cfengine3 build ran the debian powerpc buildd out of disk space,
with a 15G build log.
$ grep -c 'Unable to open database lock file'
logs/cfengine3_3.9.1-2_powerpc-20160820-1716
109492858
$ grep -c 'Unable to open last seen db'
logs/cfeng
Source: auto-apt-proxy
Version: 1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
auto-apt-proxy fails to build from source in unstable/amd64:
Hi,
Note that since we compile with CPPFLAGS="-D_FORTIFY_SOURCE=2" this
leads to at most an application crash, but as discussed with Mortiz I
increased the severity to RC, so it should be fixed for the Stretch
release.
I'm attaching the patch and a tenative reproducer case (as from SuSE).
But I n
tags 831826 + moreinfo
tags 832965 + moreinfo
thanks
Hello,
thank you for spending your time helping to make Debian better with
this bug report.
Please can you test again after update to the latest version
gstreamer1.0 version from unstable?
Many thanks
CU
Jörg
--
New:
GPG Fingerprint: 63E
92 matches
Mail list logo
