Package: easy-rsa
Version: 2.2.2-2
Dear maintainer,
easy-rsa currently does not provide openssl configuration file for the
openssl version available in testing (1.1.*).
This makes the "whichopensslcnf" script to fail on Stretch, except if
the file openssl.cnf is manually created. It seems it
Lisandro Damián Nicanor Pérez Meyer wrote:
> > Maybe the next QT upload should simply add a note to the
> > changelog that it's unsupported. Do we have any notable
> > users of QXmlSimpleReader in stretch? Probably not.
>
> I'm afraid we do:
>
>
Hello Mike,
>For italc, multi-arch does not make sense, because libitalccore is not
>a real shared library. The library gets dynamically linked in via an
>RPATH and there is no point in make multi-arch installation possible.
>
>So, why do you think italc should be multi-arch'ified?
On Mon, 02 Jan 2017 11:19:47 +0100
=?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?=
wrote:
> I set the severity to normal because
> * there are only 2 open bugs[5] for release 0.25.x at shotwell
>bugtrackerÂ
I just tried using shotwell (I don't use it often) but it turned
Dear Ian,
while I see where you come from, and can empathize with some of your points, I
think that Daniel's following of upstream practices in using full paths is
both fairly common, and a valid practice in Debian Packages.
Le mercredi, 11 janvier 2017, 17.13:44 h CET Ian Jackson a écrit :
>
Thank you very much for the detailed analysis.
> I just hit this myself, and narrowed down the cause to running with
> TERM=linux-16color.
How can I reproduce the issue on Debian Linux?
Hi Wolfgang,
On Mi 11 Jan 2017 16:47:51 CET, Wolfgang Schweer wrote:
Package: gosa-plugin-netgroups
Version: 0.1~svn652-4
Severity: normal
User: debian-...@lists.debian.org
User-tags: debian-edu
Hi,
while testing Debian Edu stretch another PHP7 issue (constructor name)
showed up.
Please
Hi,
I was unable to reproduce any FTBFS errors with sbuild targeting
stretch or sid recently.
I also saw that in recent build attempts from Reproducible builds
team, they are succeeding in their first attempt but there are
failures in their second attempt, when they modify the environment of
the
Hi Gianfranco,
On Di 10 Jan 2017 10:17:48 CET, Gianfranco Costamagna wrote:
source: italc
version: 1:3.0.2.90+dfsg1-1
severity: wishlist
tags: patch
Hello, the following patch should make the package multiarch ready
can you please apply/test the package?
Note: I don't know if the change in
clone 850954 -1
reassign -1 qt4-x11 4:4.8.2+dfsg-11
thanks
On miércoles, 11 de enero de 2017 16:44:48 ART Moritz Muehlenhoff wrote:
> Source: qtbase-opensource-src
> Severity: important
> Tags: security
>
> Hi QT maintainers,
Hi Moritz!
> there was the following report on QXmlSimpleReader:
>
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
* Package name: brisk-menu
Version : 0.2.0
Upstream Author : Ikey Doherty
* URL : https://github.com/solus-project/brisk-menu/
* License : GPL-2+
Hi,
Quoting Ralf Treinen (2017-01-11 21:19:25)
> On Wed, Jan 11, 2017 at 02:15:26PM +0100, Johannes Schauer wrote:
> > currently, dose-builddebcheck can only check build dependency
> > satisfiability for full package builds. It would be great if
> > dose-builddebcheck could easily be used to also
Emmanuel Bourg a écrit le 11/01/2017 à 15:21 :
> Hi Gilles,
>
> Le 11/01/2017 à 14:54, Gilles Filippini a écrit :
>
>> Moreover, ant reports BUILD SUCCESSFUL while it is obviously unsuccessful.
>
> The task doesn't fail the build by default when an error occurs.
> The failonerror="true"
tag 851055 + patch
thanks
Hi,
The attached patch appears to fix the bug. Run
git am \
0001-Unbreak-Read-bug-functionality-in-urwid-UI-Closes-85.patch
on the attachment to apply the patch/commit to the git repo.
Best wishes,
Ryan
--
|_)|_/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734
Sam Hartman writes ("Re: Bug#850967: Clarify /usr/bin/foo should not be
hardcoded even in upstream parts"):
> [some stuff]
Please concentrate on the MIPS binutils bug.
Ian.
--
Ian Jackson These opinions are my own.
If I emailed you from an address
Package: python-evtx
Version: 0.5.3b-2
Severity: important
> /usr/bin/evtxdump.py
Traceback (most recent call last):
File "/usr/bin/evtxdump.py", line 25, in
from Evtx.Evtx import FileHeader
File "/usr/lib/python2.7/dist-packages/Evtx/Evtx.py", line 28, in
from .Nodes import
On Wed, Jan 11, 2017 at 08:58:20PM +0100, Thibaut Paumard wrote:
> Sure, maintainer gets the last say.
>
> > Lowering down to important. Please see
> > https://www.debian.org/Bugs/Developer#severities
>
> That's were I got this:
>
> grave
> [...] causes data loss [...]
>
> which looks
Hi, I can't check it because now I didn't have hardware with prime support
--
Alexander Kudrevatykh
11 января 2017 г. 22:42:25 GMT+03:00, Andreas Boll
пишет:
>Control: tag -1 moreinfo
>
>On Mon, Mar 24, 2014 at 12:01:15AM +0400, Alexander Kudrevatykh wrote:
>>
]] Sam Hartman
> So, I'd be much more comfortable if we wanted to help make people more
> aware of the tradeoffs than I would setting policy.
Overall, I agree with Sam here, it's hard to come up with hard rules
about this, and as long as upstream and the Debian maintainer have
thought properly
Package: digikam
Version: 4:5.3.0-1
Followup-For: Bug #743824
On Sun, Oct 23, 2016 at 08:03:54PM +0200, Simon Frei wrote:
> Can you try a more recent version, ideally version 5, to see whether
> this problem persists? The mysql database has been revised a lot in
> version 5.
I can still
On Wed, 11 Jan 2017 12:21:30 -0800, tony mancill wrote:
> > Aha, after looking at the new [0] removing the postgresql line in
> > debian/maven.rules seems to be enough. Good. Committed and pushed;
> > Tony, could you please check that this makes sense?
>
> Your fix in commit 4a7e334 looks good
Package: reportbug
Version: 7.1.2
Severity: normal
Trying to read a bug in the urwid UI causes reportbug to crash. This
does not happen, e.g, with the text interface. To reproduce, attempt to
report a bug, and then select a bug from the list of existing bugs, and
then select the Read bug menu
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20170111 qa-ftbfs
> > Justification: FTBFS on amd64
>
> Confirmed.
> Looks like libpostgresql-jdbc-java's upload from 2 days ago changed
> something which breaks jabref (which built fine 10 days ago).
>
tags 850712 +patch
thanks
On Mon, Jan 09, 2017 at 03:13:24PM +, Julian Gilbey wrote:
> Package: diaspora-common
> Version: 0.6.0.0+debian5
> Severity: normal
>
> Hi Pirate,
>
> I just noticed that on purge, diaspora-common doesn't remove the file
> /etc/dbconfig-common/diaspora-common.conf
Hello,
On Wed, Jan 11, 2017 at 02:15:26PM +0100, Johannes Schauer wrote:
> currently, dose-builddebcheck can only check build dependency
> satisfiability for full package builds. It would be great if
> dose-builddebcheck could easily be used to also check arch-all-only,
> arch-any-only,
I packaged version 2.4.18, it's on mentors, waiting for my sponsor to
upload it.
Regards,
Eva
On Jan 10, 2017 10:39 PM, "Niels Thykier" wrote:
On Tue, 3 Jan 2017 19:46:21 +0100 Eva Ramon wrote:
> Thanks Sebastian and Christian,
> I'm packaging
Control: tags -1 help
The recent update of libpgjava to 9.4.1212-1 is the cause, it removed
the PGObject class. I've asked on debian-java if Emmanuel can provide a
patch to make osmosis work with the libpgjava.
Help from others is greatly appreciated too.
Kind Regards,
Bas
--
GPG Key ID:
Package: openjdk-8-jre-headless
Version: 8u111-b14-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
While investigating about ant FTBFS on kfreebsd-* [1][2], I tried the
very simple testcase below. It fails with errcode 127 on kfreebsd-*:
$ cat MyTest.java
public
Package: abiword
Version: 3.0.2-2
Severity: important
Dear Maintainer,
After starting, the work area flickers up to 30 times. The flickering repeats
itself with
every character input and moust mouse actions. It seems that the upper part of
the
work area gets redrawn 30 times in about half a
Package: htop
Version: 2.0.2-1
Followup-For: Bug #793106
Dear Maintainer,
I just hit this myself, and narrowed down the cause to running with
TERM=linux-16color.
$ infocmp linux linux-16color
comparing linux to linux-16color.
comparing booleans.
comparing numbers.
colors: 8,
Control: fixed -1 2:17.0~rc2+dfsg1-1
2014-12-28 10:37 GMT+01:00 Bálint Réczey :
> Hi Mike,
>
> 2014-12-08 1:30 GMT+01:00 Mike Edwards :
>> Package: xbmc
>> Version: 2:13.2+dfsg1-4
>> Severity: important
>>
>> Dear Maintainer,
>>
>>* What
Le 11/01/2017 à 20:14, Carsten Schoenert a écrit :
> severity 850986 important
> thanks
>
Sure, maintainer gets the last say.
> Lowering down to important. Please see
> https://www.debian.org/Bugs/Developer#severities
That's were I got this:
grave
[...] causes data loss [...]
which
I'll note that the practice of hard-coding paths is fairly common.
One common cause for this is programs that don't want to rely on PATH
for calling exec. Systemd is a particularly interesting example.
ExecStart and related arguments in systemd units are required to include
full paths.
I am
Package: bison
Version: 2:3.0.4.dfsg-1
Severity: normal
Tags: upstream
Hi,
if an empty rule matches, but calls YYERROR, the parser catches a
segmentation fault in the line
yyerror_range[1].location = yystack_[yylen - 1].location;
inside the error handling, because yylen is 0, (yylen-1)
Control: tags -1 moreinfo
Hi Leandro,
2016-12-10 23:40 GMT+01:00 Leandro Noferini :
> Sebastian Ramacher writes:
>
>
> [...]
>
>>>00:02.0 VGA compatible controller: Intel Corporation Atom Processor
>>>D4xx/D5xx/N4xx/N5xx Integrated
On Wed, 2017-01-11 at 04:45 +, Daniel A wrote:
> Package: samba
> Version: 2:4.5.2+dfsg-2
> Severity: wishlist
> Tags: patch
>
> Please compile in support for the GPGME in the samba package.
> It's related to a new feature of the Samba 4.5 release, configured by
> the 'password hash gpg key
Hi Lucas,
Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
I actually expected this.
This is due to the fix for https://bugs.debian.org/850301 in asciidoc
— IMHO such transitions (neither the one in 8.6.9-4 c.f. #850305 nor
the one in
Control: tag -1 + confirmed pending
On Wed, 11 Jan 2017 20:10:05 +0100, Lucas Nussbaum wrote:
> Source: jabref
> Version: 3.8.1+ds-2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170111 qa-ftbfs
> Justification: F
Package: python-sphinxcontrib.plantuml
Version: 0.5-1
Severity: normal
I've got some sphinx docs that contain plantuml sources, and a conf.py with:
extensions = [
'sphinxcontrib.plantuml',
]
plantuml_output_format = 'svg'
However, when i try to build, i see:
preparing
tag 851033 + pending
thanks
Some bugs in the jabref package are closed in revision
4a7e334d54f80d7bfc63dd62b778461262d1ea94 in branch 'master' by gregor
herrmann
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jabref.git/commit/?id=4a7e334
Commit message:
Remove
Control: fixed -1 0.12+git20140509-6
Hi Paul,
2015-10-28 3:54 GMT+01:00 Paul Wise :
> Package: kerneloops-applet
> Version: 0.12+git20140509-1
> Severity: important
>
> The default configuration requires user permission before sending
> reports. Unfortunately while
Control: tag -1 moreinfo
On Mon, Mar 24, 2014 at 12:01:15AM +0400, Alexander Kudrevatykh wrote:
> Package: xserver-xorg-core
> Version: 2:1.15.0-2
> Severity: normal
>
> output of xrandr --listproviders
>
> Providers: number : 2
> Provider 0: id: 0x68 cap: 0xb, Source Output, Sink Output, Sink
Package: src:gli
Severity: important
Dear Maintainer,
CMake detection of gli fails on non 64-bit platforms [1].
Any attempt to call `find_package(gli REQUIRED)` produces the following
error:
```
Could not find a configuration file for package "glm" that is
compatible with requested version "".
On Wed, Jan 11, 2017 at 02:06:21PM -0500, Daniel Kahn Gillmor wrote:
> (b) it's not actually an issue on the debian buildd infrastructure
While I understand the downgrade of this bug in particular, I'm
worried about this rationale being used over and over again, when it's
clearly flawed (and not
Control: reopen -1
Control: found -1 1:1.4.6-6
Control: found -1 1:2.0.3-5
On 2016-12-19 14:45, Debian Bug Tracking System wrote:
> This should be fixed now. Thanks for the piuparts upgrade testing.
This seems to be a bit more difficult. Looks like the error
already exists in jessie, but
Hi Andreas,
Thank a lot.
I now understand why the report came so late in the release cycle and so
late after the relevant change: tango-db never required updating and
thus dumping the database until 9.2.5 hit testing.
@bts: I think I have made up my mind where the code needs to be changed.
On Sun, Oct 05, 2014 at 09:12:36PM +0200, Eduard Bloch wrote:
> reopen 764083
> thanks
>
> Hallo,
> * Debian Bug Tracking System [Sun, Oct 05 2014, 01:48:38PM]:
>
> > > The workaround is to use --git-compression=... but then this information
> > > maybe
> > > should have been stored in
Hi Alex,
On Wed, Sep 24, 2014 at 09:44:20PM +0200, Alex Muntada wrote:
> Package: git-buildpackage
> Version: 0.6.19
>
> After renaming the default debian branch from debian to master
> and the upstream branch from master to upstream on a pkg-perl
> team repository, we realized that the old
Source: f-el
Version: 0.19.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> faker
Source: python-apt
Version: 1.4.0~beta1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully
On Wed, Jan 11, 2017 at 07:36:56PM +0100, Sven Joachim wrote:
> The toplevel Makefile in the crafty source adds -march=k8 to CFLAGS,
Hi. I checked that a rebuild fixed the issue, but I've also removed
the -march thing to be safe.
Thanks a lot.
Source: gcc-6-cross
Version: 14
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: keystone
Version: 2:10.0.0-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully
Control: retitle -1 reconserver: FTBFS: reConServer.cxx:941:164: error: no
matching function for call to
'resip::HEPSipMessageLoggingHandler::HEPSipMessageLoggingHandler(resip::Data&,
int&, int&)'
I ran into this on amd64 as well.
Lucas
Source: gcc-6-cross-ports
Version: 11
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: molds
Version: 0.3.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
severity 850986 important
thanks
Lowering down to important. Please see
https://www.debian.org/Bugs/Developer#severities
Regards
Carsten
On Wed, Jan 11, 2017 at 08:08:47PM +0100, Thibaut Paumard wrote:
> Package: icedove
> Version: 1:45.4.0-1
> Severity: grave
>
> Dear maintainers,
>
> I
Source: tcsh
Version: 6.20.00-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: glance
Version: 2:13.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully
Source: python-ws4py
Version: 0.3.4-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> deb
Source: eclipse-xsd
Version: 2.9.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: kryo-serializers
Version: 0.22-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully
Source: eclipse-wtp
Version: 3.6.3-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: img2pdf
Version: 0.2.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: axis
Version: 1.4-24
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> debian/ru
Source: cxxtest
Version: 4.4-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: projectreactor
Version: 2.0.8-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: calcurse
Version: 4.2.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: jabref
Version: 3.8.1+ds-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> deb
Source: composite
Version: 0.006.2+dfsg0-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: gnocchi
Version: 3.0.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully
Source: dpmb
Version: 0~2016.06.30
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: python-asyncssh
Version: 1.8.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully
Source: python-oslo.middleware
Version: 3.19.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully
Source: sardana
Version: 2.2.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> debian/ru
Source: ffmpeg
Version: 7:3.2.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> gcc -Wl
Source: nut
Version: 2.7.4-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[3]: Enter
Source: postgis-java
Version: 1:2.2.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: python-xmp-toolkit
Version: 2.0.1+git20140309.5437b0a-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant
Source: beets
Version: 1.3.19-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> la
Source: eclipse-anyedit
Version: 2.4.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> m
Source: mapbox-vector-tile
Version: 0.5.0+ds-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully
Source: leap-cli
Version: 1.9-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> /usr/
Source: nikola
Version: 7.6.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: libpqxx
Version: 4.0.1+dfsg2-7
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: ocrmypdf
Version: 4.3.4-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> Found
Source: asyncpg
Version: 0.8.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> debian/ru
Source: txfixtures
Version: 0.2.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> deb
Source: python-django-pyscss
Version: 2.0.2-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully
Source: mixxx
Version: 2.0.0~dfsg-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> g++
Source: clementine
Version: 1.3.1+git240-g1a2f6e2+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part
Source: pyregion
Version: 1.2-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> pyregion/te
Source: ckermit
Version: 302-5.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> gcc -Wl
Source: qtwebengine-opensource-src
Version: 5.7.1+dfsg-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part
Source: kicad
Version: 4.0.4+dfsg2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: python-restless
Version: 2.0.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> m
Source: graphite2
Version: 1.3.9-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: ggcov
Version: 0.9-13
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> ERROR: (test
Source: erlang-ranch
Version: 1.2.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mak
Source: berkshelf
Version: 4.3.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> /usr/
101 - 200 of 451 matches
Mail list logo