Source: mpc
Version: 0.28-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,
mpc fails to build from source in unstable/amd64:
[…]
Source: ocamldsort
Version: 0.16.0-2
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,
ocamldsort fails to build from source in unstable/amd64:
Processing commands for cont...@bugs.debian.org:
> merge 841751 840841
Bug #841751 [digikam] digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25
Unable to merge bugs because:
severity of #840841 is 'serious' not 'normal'
Failed to merge 841751: Did not alter merged bugs.
> thanks
Stopping pro
Processing commands for cont...@bugs.debian.org:
> forcemerge 841751 840841
Bug #841751 [digikam] digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25
Bug #840841 [digikam] digikam: fails to upgrade from jessie to stretch: gets
removed, not upgraded
Severity set to 'normal' from 'serious'
Bug
Processing commands for cont...@bugs.debian.org:
> severity 840841 serious
Bug #840841 [digikam] digikam: fails to upgrade from jessie to stretch: gets
removed, not upgraded
Bug #841751 [digikam] digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25
Severity set to 'serious' from 'normal'
Sever
Dominik George wrote:
> Besides speech-dispatcher, against which I also reported a bug, I do not
> have any packages on my system that show such behaviour.
Oh, really? But surely some of them adjust sys.path (probably the most
common?) as well as importing shared libraries and running stuff like
Hi,
> > Besides speech-dispatcher, against which I also reported a bug, I do not
> > have any packages on my system that show such behaviour.
>
> Oh, really? But surely some of them adjust sys.path (probably the most
> common?) as well as importing shared libraries and running stuff like
> ``apt
Control: reassign -1 python3-ipdb 0.10.1-1
Oh, I was actually wrong in that this is IPython's mistake…
The root cause is ipdb, which causes misbehaviour in both the core
interpreter and IPython ;)!
Sorry, IPython.
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
Do
Processing control commands:
> reassign -1 python3-ipdb 0.10.1-1
Bug #841726 [ipython3] ipython3: importing something from ipython has side
effects
Bug reassigned from package 'ipython3' to 'python3-ipdb'.
No longer marked as found in versions ipython/2.4.1-1.
Ignoring request to alter fixed vers
Caontrol: tags -1 +patch
The patch for this bug I found in the Ubuntu package is attached.
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.
Package: smarty-gettext
Version: 1.4.0-1
Severity: serious
Justification: fails to install
Hi Mike,
in current sid of today:
$ apt install smarty-gettext
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may
> There's no need to check this specific instance, it's just one example of a
> potential side-effects that mean importing everything is, alas, by design
> broken. Don't forget all the other import-time monkey-patching, etc. too.
Totally agreed.
-nik
--
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17
Dominik George wrote:
> I wouldn't open an RC bug against python-apt because it calls init_config(),
Sure; I explained poorly — packages that *use* apt_pkg would call init_config()
which presumably has side-effects (?), not python-apt itself…
There's no need to check this specific instance, it's
affects 841503 src:libguestfs
thanks
Thanks Raphaël for the report and Jonas for the quick fix.
I've noticed that this bug makes libguestfs to FTBFS in stretch.
Using "affects" here to avoid bugs against libguestfs.
Thanks.
Processing commands for cont...@bugs.debian.org:
> affects 841503 src:libguestfs
Bug #841503 {Done: Jonas Meurer } [cryptsetup] cryptsetup:
initramfs cryptroot hook fails when /etc/cryptsetup-initramfs/conf-hook does
not exist yet
Added indication that 841503 affects src:libguestfs
> thanks
Stop
Package: unattended-upgrades
Version: 0.92
Severity: grave
Dear Maintainer,
When unattended-upgrades has to upgrade apt itself, it will be
terminated and leaves the system in a state that requires manual
intervention, like
dpkg --reconfigure --pending
apt-get -f install
A second bug is th
Processing commands for cont...@bugs.debian.org:
> found 841763 0.86.5+build1
Bug #841763 [unattended-upgrades] unattended-upgrades: Breaks hard when apt is
upgraded
Marked as found in versions unattended-upgrades/0.86.5+build1.
> thanks
Stopping processing here.
Please contact me if you need as
On 23/10/16 00:48, Aurelien Jarno wrote:
> On 2016-10-21 15:15, James Cowgill wrote:
>> On 21/10/16 14:55, YunQiang Su wrote:
>>> On Fri, Oct 14, 2016 at 3:47 PM, Emilio Pozuelo Monfort
>>> wrote:
Control: severity -1 serious
On Fri, 19 Aug 2016 22:29:48 -0700 Afif Elghraoui wrote:
Processing control commands:
> affects -1 calypso
Bug #841247 [python-vobject] calypso: UnicodeDecodeError when importing an .ics
Added indication that 841247 affects calypso
> severity -1 grave
Bug #841247 [python-vobject] calypso: UnicodeDecodeError when importing an .ics
Severity set to 'grave'
Source: mtasc
Version: 1.14-3
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,
mtasc fails to build from source in unstable/amd64:
[…]
li
Processing commands for cont...@bugs.debian.org:
> forcemerge 840841 841751
Bug #840841 [digikam] digikam: fails to upgrade from jessie to stretch: gets
removed, not upgraded
Bug #841751 [digikam] digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25
Bug #841751 [digikam] digikam: Rebuild neede
Processing commands for cont...@bugs.debian.org:
> forwarded 841110 https://github.com/mdadams/jasper/issues/32
Bug #841110 [src:jasper] jasper: CVE-2016-8693
Set Bug forwarded-to-address to 'https://github.com/mdadams/jasper/issues/32'.
> thanks
Stopping processing here.
Please contact me if you
Source: libzypp
Version: 15.3.0-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,
libzypp fails to build from source in unstable/amd64:
[…]
On Sun, Oct 23, 2016 at 12:08:53PM +0200, Stefan Fritsch wrote:
> Package: unattended-upgrades
> Version: 0.92
> Severity: grave
>
> Dear Maintainer,
>
>
> When unattended-upgrades has to upgrade apt itself, it will be
> terminated and leaves the system in a state that requires manual
> interven
Le dimanche 23 octobre 2016, 13 h 43 min 59 s CEST Santiago Vila a écrit :
> Aha! I can reproduce this too. On the machines where this happens,
> I believe I answered "yes" to a debconf question about restarting
> services automatically (one of the times I upgraded by hand and not
> using unattende
Processing commands for cont...@bugs.debian.org:
> tag 841064 pending
Bug #841064 [src:awscli] awscli: FTBFS: ImportError: No module named
's3transfer'
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
841064: http://bugs.debian.org/cgi-bin/bu
tag 841064 pending
thanks
Hello,
Bug #841064 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/awscli.git;a=commitdiff;h=dfcad50
---
commit dfcad50a177cc3b459915f
Source: gnucash
Version: 1:2.6.13-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs timezone
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
gnucash fails to build from source in unstable/amd6
forwarded 841532 https://github.com/libgit2/libgit2/issues/3970
thanks
Russell Sim wrote:
> I have forwarded this bug report upstream
> https://github.com/libgit2/libgit2/issues/3970 in the mean time I'll add
> a fix to the existing package to force tests to run in GMT timezone.
Be careful; it c
Processing commands for cont...@bugs.debian.org:
> forwarded 841532 https://github.com/libgit2/libgit2/issues/3970
Bug #841532 [src:libgit2] libgit2: FTBFS under some timezones (eg. GMT-14)
Set Bug forwarded-to-address to
'https://github.com/libgit2/libgit2/issues/3970'.
> thanks
Stopping process
Hi all,
thanks John for the detailed explanation and the patches.
>> So the real solution here is to revert your autoconf-archive to 6dc6cc5^
>> and use that unborked ax_with_curses.m4, which will in future be bundled
>> with samtools.
>
> This should have been 0351b06^.
I see. For now I have b
What is the fix for this? I have the same problem. Cant update
anything due to this problem. Should any new sources be added to
/etc/apt/sources.list?
On Wed, 07 Sep 2016 23:18:47 +0200 Andreas Beckmann
wrote:
> Package: golang-doc
> Version: 2:1.7~1
> Severity: serious
> User: debian...@list
retitle 836450 FTBFS: RunTests: test 5: FAILED:
ref(train-sets/ref/0002a.stderr) != stderr(0002a.stderr)
thanks
Looks like non-deterministic test timings...?
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Processing commands for cont...@bugs.debian.org:
> retitle 836450 FTBFS: RunTests: test 5: FAILED:
> ref(train-sets/ref/0002a.stderr) != stderr(0002a.stderr)
Bug #836450 [src:vowpal-wabbit] vowpal-wabbit: FTBFS everywhere
Changed Bug title to 'FTBFS: RunTests: test 5: FAILED:
ref(train-sets/ref/
This is what I ended up doing. Not sure if this is correct method but
seems to have worked. I can now perform an apt-get update && apt-get
upgrade.
sudo rm /usr/lib/go -Rf
sudo rm /usr/share/doc/golang-doc/ -Rf
sudo mkdir /usr/lib/go
sudo apt-get -f install
sudo apt-get update && apt-get upgrade
severity 841364 important
retitle 841364 clementine: unable to play anything in special
configuration cases, "GStreamer encountered a general stream error"
thanks
Hi,
@Adam, I tried many migrations and I still could not reproduce your bug.
I still think that this is caused by a special use case o
Processing commands for cont...@bugs.debian.org:
> severity 841364 important
Bug #841364 [clementine] clementine: no sound at all, "GStreamer encountered a
general stream error."
Severity set to 'important' from 'grave'
> retitle 841364 clementine: unable to play anything in special
Bug #841364 [
Control: reopen -1
Hi!
On Thu, 2016-10-20 at 20:15:06 +, Debian Bug Tracking System wrote:
> Date: Thu, 20 Oct 2016 22:14:11 +0200
> From: Andreas Henriksson
> To: Santiago Vila
> Cc: 841098-d...@bugs.debian.org
> Subject: Re: Bug#841098: not fixed in rygel 0.32.1-1
> Message-ID: <201610202
Processing control commands:
> reopen -1
Bug #841098 {Done: Andreas Henriksson } [src:rygel] rygel:
FTBFS (rygel-media-engine-test fails)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No l
> The following packages have unmet dependencies:
> smarty-gettext : Depends: php7-cli but it is not installable
> E: Unable to correct problems, you have held broken packages.
should either be php-cli (as it has been before, prefered) or
php7.0-cli.
Wolfgang
signature.asc
Description: Digital
Processing control commands:
> severity -1 grave
Bug #837928 [molly-guard] usrmerge: fails to merge with molly-guard installed
Severity set to 'grave' from 'important'
--
837928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> severity 837925 normal
Bug #837925 {Done: Marco d'Itri } [usrmerge] usrmerge: fails to
merge with molly-guard installed
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
837925
Processing control commands:
> severity -1 important
Bug #834856 [python-pysam] python-pysam fails to build on mips64el arch.:
failed test
Severity set to 'important' from 'serious'
> retitle -1 python-pysam: FTBFS on 32-bit architectures: segmentation fault in
> testsuite
Bug #834856 [python-py
control: severity -1 important
control: retitle -1 python-pysam: FTBFS on 32-bit architectures: segmentation
fault in testsuite
On 2016-10-23 12:25, Emilio Pozuelo Monfort wrote:
> On 23/10/16 00:48, Aurelien Jarno wrote:
> > On 2016-10-21 15:15, James Cowgill wrote:
> >> On 21/10/16 14:55, YunQi
On Mon, Sep 12, 2016 at 01:18:32AM +0200, Balint Reczey wrote:
> During a rebuild of all packages in sid, gdcm
> failed to build on amd64 with patched GCC and dpkg. The root
> cause seems to be that libPapyrus3.a is shipped as a non-PIC library.
That cannot be the root cause. Debian Policy [1] i
Processing commands for cont...@bugs.debian.org:
> tags 804442 + pending
Bug #804442 [src:python-memory-profiler] python-memory-profiler: FTBFS:
NameError: name 'profile' is not defined
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
804442:
On Mon, Sep 12, 2016 at 01:18:32AM +0200, Balint Reczey wrote:
> /usr/bin/ld:
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/libPapyrus3.a(PapyError3.c.o):
> relocation
> R_X86_64_32 against `.rodata.str1.8' can not be used when making a
> shared object; recompile with -fPIC
> ...
The Ubuntu
Processing commands for cont...@bugs.debian.org:
> severity 838897 serious
Bug #838897 [src:jitsi] jitsi: Replace the glassfish dependencies
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
838897: http://bugs.debian.org/c
Processing control commands:
> retitle -1 kannel-dev: libgwlib.a needs binNMU rebuild with MySQL 5.7 and
> -fPIE
Bug #837663 [kannel-dev] kannel-dev: Please build libgwlib.a with -fPIC
Changed Bug title to 'kannel-dev: libgwlib.a needs binNMU rebuild with MySQL
5.7 and -fPIE' from 'kannel-dev: P
Control: tags 727930 + patch
Control: tags 727930 + pending
Control: tags 811808 + patch
Control: tags 811808 + pending
Dear maintainer,
I've prepared an NMU for ns2 (versioned as 2.35+dfsg-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
Processing control commands:
> tags 727930 + patch
Bug #727930 [src:ns2] ns2: run dh-autoreconf to update config.{sub,guess} and
{libtool,aclocal}.m4
Ignoring request to alter tags of bug #727930 to the same tags previously set
> tags 727930 + pending
Bug #727930 [src:ns2] ns2: run dh-autoreconf
Processing control commands:
> tags 727930 + patch
Bug #727930 [src:ns2] ns2: run dh-autoreconf to update config.{sub,guess} and
{libtool,aclocal}.m4
Added tag(s) patch.
> tags 727930 + pending
Bug #727930 [src:ns2] ns2: run dh-autoreconf to update config.{sub,guess} and
{libtool,aclocal}.m4
Add
Package: libtesseract3
Version: 3.04.01-4.1
Severity: serious
Justification: Debian Policy section 8.2
libtesseract3 includes data files in /usr/share/tesseract-ocr/tessdata.
That filename is not versioned. After a soname bump, the new library
package will thus conflict with libtesseract3. Such be
Your message dated Sun, 23 Oct 2016 22:10:45 +0300
with message-id <20161023191045.qjocu2psij7od...@bunk.spdns.de>
and subject line Re: Bug#828362: Acknowledgement (kannel-sqlbox: FTBFS with
openssl 1.1.0)
has caused the Debian Bug report #841635,
regarding kannel-sqlbox: FTBFS: Kannel gwlib is re
Control: tags -1 +patch
What broke the build is that gcc 6 changed the default C++ standard
from C++98 to C++14.
Not all valid C++98 code is also valid C++11 and C++14 code.
Note that this just changed the default, when told to process C++98 code
gcc 6 does not differ in any significant way fro
Processing control commands:
> tags -1 +patch
Bug #831093 [src:qterm] qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error:
narrowing conversion of ''\3777600'' from 'char' to 'uchar {aka unsigned
char}' inside { } [-Wnarrowing]
Added tag(s) patch.
--
831093: http://bugs.debian.org/cgi-bin
Processing control commands:
> retitle 837658 libfl_pic.a is not compiled with -fPIC
Bug #837658 [libfl-dev] libfl-dev: Please build libfl_pic.a with -fPIC
Bug #840394 [libfl-dev] motif: FTBFS: relocation R_X86_64_PC32 against symbol
`exit@@GLIBC_2.2.5' can not be used when making a shared object
Control: retitle 837658 libfl_pic.a is not compiled with -fPIC
#837658 is different from many other PIE issues:
This is a _pic.a library that includes the non-PIC objects instead of
the PIC objects it should contain.
A binNMU with -fPIE would not fix the root cause that this library is
suppose
On Mon, 26 Sep 2016 10:43:42 +0200 Emmanuel Bourg wrote:
> jitsi still depends on glassfish-activation and glassfish-mail which are
going
> to be removed. glassfish-activation can be safely removed (the API has
been
> integrated to the standard JDK) and glassfish-mail should be replaced by
libmail
Package: src:linux
Version: 4.7.8-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
when performing this week's regular update on my Debian Testing
systems, linux-image-4.7.0-1-686 was updated from 4.7.6-1 to
4.7.8-1_i386.deb on two Thinkpads T41.
On both of them, the
tag 841625 pending
thanks
Hello,
Bug #841625 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=pkg-gnome/gupnp-tools.git;a=commitdiff;h=d756041
---
commit d7560414d57520a05b4643d4d043b17b
Processing commands for cont...@bugs.debian.org:
> tag 841625 pending
Bug #841625 [src:gupnp-tools] gupnp-tools: FTBFS: playlist-treeview.h:35:34:
error: unknown type name 'GUPnPDeviceProxy'
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
84
* Neil Williams:
> The requirement for linuxboot_dma.bin is specific to QEMU 2.7 and is
> not provided by the seabios package (which provides linuxboot_dma.bin).
> As a workaround, symlinking linuxboot_dma.bin as linuxboot.bin
> in /usr/share/seabios/ allows the guestfs operations to proceed.
Thi
Control: tags -1 + patch
[Chris Lamb 2015-12-20]
> roboptim-core fails to build from source in unstable/amd64:
It still fail to build.
> dh_install: libroboptim-core2-plugin-base missing files
> (usr/lib/*/roboptim-core/*.so.2*), aborting
> debian/rules:26: recipe for target 'binary' failed
Your message dated Sun, 23 Oct 2016 20:58:09 +
with message-id
and subject line Bug#841665: fixed in boinc 7.6.33+dfsg-2
has caused the Debian Bug report #841665,
regarding boinc-client: The boinc-client init script has a badly constructed
parameter for xhost
to be marked as done.
This means
Processing control commands:
> tags -1 + patch
Bug #808455 [src:roboptim-core] roboptim-core: FTBFS: dh_install:
libroboptim-core2-plugin-base missing files (usr/lib/*/roboptim-core/*.so.2*),
aborting
Added tag(s) patch.
--
808455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808455
Debian
Processing commands for cont...@bugs.debian.org:
> reassign 841757 src:check
Bug #841757 [src:mpc] mpc: FTBFS: relocation R_X86_64_32S against `.rodata' can
not be used when making a shared object; recompile with -fPIC
Bug reassigned from package 'src:mpc' to 'src:check'.
No longer marked as foun
Your message dated Sun, 23 Oct 2016 21:09:58 +
with message-id
and subject line Bug#841751: fixed in digikam 4:5.2.0-2
has caused the Debian Bug report #841751,
regarding digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25
to be marked as done.
This means that you claim that the problem h
Your message dated Sun, 23 Oct 2016 21:09:58 +
with message-id
and subject line Bug#840841: fixed in digikam 4:5.2.0-2
has caused the Debian Bug report #840841,
regarding digikam: Rebuild needed as libmarblewidget-qt5 24 -> 25
to be marked as done.
This means that you claim that the problem h
Your message dated Sun, 23 Oct 2016 21:09:58 +
with message-id
and subject line Bug#840841: fixed in digikam 4:5.2.0-2
has caused the Debian Bug report #840841,
regarding digikam: fails to upgrade from jessie to stretch: gets removed, not
upgraded
to be marked as done.
This means that you cl
Your message dated Sun, 23 Oct 2016 21:09:58 +
with message-id
and subject line Bug#841751: fixed in digikam 4:5.2.0-2
has caused the Debian Bug report #841751,
regarding digikam: fails to upgrade from jessie to stretch: gets removed, not
upgraded
to be marked as done.
This means that you cl
Your message dated Sun, 23 Oct 2016 21:18:56 +
with message-id
and subject line Bug#841443: fixed in libcrypto++ 5.6.4-2
has caused the Debian Bug report #841443,
regarding hmqv.h is missing: refered to by /usr/include/cryptopp/eccrypto.h
to be marked as done.
This means that you claim that t
Your message dated Sun, 23 Oct 2016 21:19:29 +
with message-id
and subject line Bug#840728: fixed in libp11 0.4.2-1
has caused the Debian Bug report #840728,
regarding libp11: FTBFS: openssl-1.0.2/engines: No such file or directory
to be marked as done.
This means that you claim that the prob
Your message dated Sun, 23 Oct 2016 21:22:14 +
with message-id
and subject line Bug#830392: fixed in oidua 0.16.1-8
has caused the Debian Bug report #830392,
regarding oidua: FTBFS: dh_clean: Please specify the compatibility level in
debian/compat
to be marked as done.
This means that you cl
Your message dated Sun, 23 Oct 2016 21:28:50 +
with message-id
and subject line Bug#841548: fixed in wand 0.4.3-1
has caused the Debian Bug report #841548,
regarding Importing wand.image fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sun, 23 Oct 2016 21:28:06 +
with message-id
and subject line Bug#839181: fixed in transmission-remote-gtk 1.3.1-1
has caused the Debian Bug report #839181,
regarding transmission-remote-gtk: FTBFS: Option release requires an argument
[pod2man --release=""]
to be marked as
Your message dated Sun, 23 Oct 2016 21:28:50 +
with message-id
and subject line Bug#841548: fixed in wand 0.4.3-1
has caused the Debian Bug report #841548,
regarding autopkgtest: FTBFS: Tests failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Package: ardour
Version: 1:5.4.0~dfsg-1
Severity: grave
Ardour 1:4.7~dfsg-2 works great. If instead I upgrade to 1:5.3~dfsg-1 (current
unstable) or 1:5.4.0~dfsg-1 (current testing), I get a segfault when I try to
load any project.
I am attaching a gdb run (from 1:5.4.0~dfsg-1).
-- System Infor
Package: dgit
Version: 2.6
Severity: serious
gbp pq cannot cope with all patches that dpkg-source can, because it
uses git-apply and git-apply is not very compatible.
At the moment, this means that `dgit clone glibc' fails:
gbp:error: Failed to apply
'/home/ian/junk/d/glibc/.git/dgit/unpack
Your message dated Sun, 23 Oct 2016 22:32:11 +
with message-id
and subject line Bug#817354: fixed in aspell-br 0.50-2-6.1
has caused the Debian Bug report #817354,
regarding aspell-br: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Sun, 23 Oct 2016 22:32:29 +
with message-id
and subject line Bug#841064: fixed in awscli 1.11.7-2
has caused the Debian Bug report #841064,
regarding awscli: FTBFS: ImportError: No module named 's3transfer'
to be marked as done.
This means that you claim that the problem ha
Your message dated Sun, 23 Oct 2016 22:44:29 +
with message-id
and subject line Bug#841082: fixed in epiphany-browser 3.22.1-2
has caused the Debian Bug report #841082,
regarding epiphany-browser: bump dependency on epiphany-browser-data
to be marked as done.
This means that you claim that th
Your message dated Sun, 23 Oct 2016 22:44:56 +
with message-id
and subject line Bug#841707: fixed in eximdoc4 4.87-2
has caused the Debian Bug report #841707,
regarding eximdoc4: FTBFS with bash as /bin/sh
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Sun, 23 Oct 2016 23:02:04 +
with message-id
and subject line Bug#841625: fixed in gupnp-tools 0.8.12-2
has caused the Debian Bug report #841625,
regarding gupnp-tools: FTBFS: playlist-treeview.h:35:34: error: unknown type
name 'GUPnPDeviceProxy'
to be marked as done.
This
Your message dated Sun, 23 Oct 2016 23:10:56 +
with message-id
and subject line Bug#837568: fixed in libctl 3.2.2-3
has caused the Debian Bug report #837568,
regarding libctl-dev: Please build libctlgeom.a with -fPIC
to be marked as done.
This means that you claim that the problem has been de
Your message dated Sun, 23 Oct 2016 23:21:13 +
with message-id
and subject line Bug#841442: fixed in lintian 2.5.49
has caused the Debian Bug report #841442,
regarding lintian: FTBFS: fail tests::shared-libs-non-pic-i386
to be marked as done.
This means that you claim that the problem has bee
Yeah, I totally agree it's an upstream bug, the bug exists in not only
this version but also the master branch so I can't backport a fix.
I did have a quick look at the test code, and it's not obviously due to
that, so it must be related to how they store or retrieve the offset in
this case.
I'
Your message dated Sun, 23 Oct 2016 23:27:23 +
with message-id
and subject line Bug#824825: fixed in lxqt-l10n 0.11.0-19-g717bd7e-4
has caused the Debian Bug report #824825,
regarding liblxqt-l10n: fails to upgrade from 'sid' - trying to overwrite
/usr/share/lxqt/translations/liblxqt/liblxqt_
Your message dated Sun, 23 Oct 2016 23:31:33 +
with message-id
and subject line Bug#817613: fixed in outguess 1:0.2-7.1
has caused the Debian Bug report #817613,
regarding outguess: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Sun, 23 Oct 2016 23:34:01 +
with message-id
and subject line Bug#817627: fixed in poster 1:20050907-1.1
has caused the Debian Bug report #817627,
regarding poster: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 23 Oct 2016 23:43:07 +
with message-id
and subject line Bug#831093: fixed in qterm 1:0.5.12-1.2
has caused the Debian Bug report #831093,
regarding qterm: FTBFS with GCC 6: uaocodec.cpp:15598:1: error: narrowing
conversion of ''\3777600'' from 'char' to 'uchar {aka
Your message dated Sun, 23 Oct 2016 23:46:33 +
with message-id
and subject line Bug#841713: fixed in tunnelx 20160713-2
has caused the Debian Bug report #841713,
regarding tunnelx: FTBFS with dpkg-buildpackage -A (chown error)
to be marked as done.
This means that you claim that the problem h
Your message dated Sun, 23 Oct 2016 23:44:57 +
with message-id
and subject line Bug#841759: fixed in smarty-gettext 1.4.0-2
has caused the Debian Bug report #841759,
regarding smarty-gettext : Depends: php7-cli but it is not installable
to be marked as done.
This means that you claim that the
Your message dated Sun, 23 Oct 2016 23:46:28 +
with message-id
and subject line Bug#839306: fixed in translate-toolkit 2.0.0~b5-2
has caused the Debian Bug report #839306,
regarding translate-toolkit: FTBFS: Tests failures
to be marked as done.
This means that you claim that the problem has b
Your message dated Sun, 23 Oct 2016 23:48:33 +
with message-id
and subject line Bug#817742: fixed in yaret 2.1.0-5.1
has caused the Debian Bug report #817742,
regarding yaret: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Sun, 23 Oct 2016 23:49:06 +
with message-id
and subject line Bug#840230: fixed in zipl-installer 0.0.35
has caused the Debian Bug report #840230,
regarding When installing to rootfs on LVM, an empty subvol= is appended to
rootflags
to be marked as done.
This means that you
Your message dated Sun, 23 Oct 2016 23:48:15 +
with message-id
and subject line Bug#837712: fixed in xemacs21 21.4.24-4
has caused the Debian Bug report #837712,
regarding xemacs21: FTBFS with bindnow and PIE enabled
to be marked as done.
This means that you claim that the problem has been de
Your message dated Sun, 23 Oct 2016 23:48:44 +
with message-id
and subject line Bug#812532: fixed in yp-tools 3.3-5
has caused the Debian Bug report #812532,
regarding files with the same name installed in / and /usr
to be marked as done.
This means that you claim that the problem has been de
Your message dated Sun, 23 Oct 2016 23:48:21 +
with message-id
and subject line Bug#817733: fixed in xkbset 0.5-5.2
has caused the Debian Bug report #817733,
regarding xkbset: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Quoting Adrian Bunk (2016-10-23 20:32:23)
> Control: retitle -1 kannel-dev: libgwlib.a needs binNMU rebuild with MySQL
> 5.7 and -fPIE
> Control: severity -1 serious
> Control: affects -1 = src:kannel-sqlbox
>
> Two issues appeared in unstable:
> - MySQL 5.7 removes -lmysqlclient_r, which breaks
1 - 100 of 125 matches
Mail list logo
