Package: bloscpack
Version: 0.15.0-1
Severity: serious
Justification: fails to build from source
Building on i386 there are two test failures:
==
FAIL: test_numpy_io.test_itemsize_chunk_size_mismatch(, , array([ 0, 1, 2,
I've begun to work on updating the package to 0.8.0, but I have given up now.
There are dozens over dozens of separately licensed templated config files
included in the
roles. Researching the new ones and registering them properly in deb/copyright
like I did
for the debops-playbooks package tak
Related to this was: https://bugs.debian.org/766740
Thanks for reporting,
DS
--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/
AFL on clang/llvm 6.0 currently fails:
[+] All set and ready to build.
clang-6.0 -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign -DAFL_PATH=\"/usr/lib/afl\"
-DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.52b\" afl-clang-fast.c -o ../afl-clang-fast
-Wl,-z,relro -Wl,-z,now
ln -sf afl-clang-fast ../afl-c
On 05/06/2018 08:56 PM, Adrian Bunk wrote:
> Control: severity -1 serious
>
> On Sat, May 05, 2018 at 05:58:21PM +0200, Daniel Stender wrote:
>> Control: severity -1 important
>>
>> I'm lowering the severity of this bug report now to unblock the migration to
>
Control: severity -1 important
I'm lowering the severity of this bug report now to unblock the migration to
testing.
DS
--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/
Package: pdf2djvu
Version: 0.9.8-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
A recent rebuild revealed this problem:
==
FAIL: test-1px-font.test.test
---
Source: afl
Version: 2.52b-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
AFL currently FTBFS:
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign
-DAFL_P
A couple of failures like this also with 1.1.2/blosc 1.14.2:
==
FAIL: test01b (bcolz.tests.test_carray.bloscFiltersTest)
Testing all available filters in big arrays (bcolz.defaults)
--
On 03/12/2018 02:03 PM, James Cowgill wrote:
Source: llvmlite
Version: 0.22.0-1
Severity: serious
Tags: sid buster
Hi,
llvmlite FTBFS on mips64el with this segmentation fault:
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{int
Please hang on, I'll update this shortly.
DS
--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/
On 02/03/2018 02:49 PM, Frans van Berckel wrote:
> Package: debops
> Version: 0.4.3-1
> Severity: serious
>
> There a new upstream version v0.6.0, in Github releases available.
>
> https://github.com/debops/debops/releases
>
> If i am well, this one doesn't depends on the debops-playbooks packag
Source: pytest-httpbin
Version: 0.2.3-1
Severity: serious
Justification: fails to build from source
pytest-httpbin currently FTBFS:
tests/test_httpbin.py::test_httpbin_accepts_lots_of_get_requests_in_single_session
FAILED
=== FAILURES
Source: pytest-catchlog
Version: 1.2.2+git20170915-2
Severity: serious
Justification: fails to build from source
pytest-catchlog currently FTBFS:
I: pybuild base:184: python2.7 -m pytest -v -x
= test session starts ==
platform linux2 -- Pyth
52461565087b886105df5a2fe5c182b879e9d5df
Author: Daniel Stender
Date: Tue Nov 14 00:02:06 2017 +0100
deb/rules: temporarily disable test_HTTPSConnection_SNI_support on ppc-s
diff --git a/debian/changelog b/debian/changelog
index 3e925bc..a3f2c00 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8
Thanks for writing the bug report.
This problem should have taken been care of by sni-test-race.patch,
which draws from https://gitlab.com/m2crypto/m2crypto/merge_requests/141
Unfortunately, not even bumping the timeout using $M2CRYPTO_TEST_SSL_SLEEP
makes this
disappear. I'm in contact with ups
Package: src:afl
Version: 2.50b-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: block 873404 by -1
AFL begun to FTBFS recently with a clang error:
[+] All set and ready to build.
clang-3.9 -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign
This appears to be a problem with the numpydoc extension. I can't tell what's
happening now,
however removing numpydoc from the needed/supported extensions in the package
temporarily
solves the FTBFS.
For the record, this happens both with python-sphinx/numpydoc and
python3-sphinx/numpydoc.
#
19741cd527073d1e4794ebc74bbf0742bc307aa9
Author: Daniel Stender
Date: Mon Aug 14 22:40:50 2017 +0200
deb/rules: build test_multiarray with -O0
diff --git a/debian/changelog b/debian/changelog
index e609a08..4e52420 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libvigraimpex
Source: libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Current Vigra FTBFS on mips64el [1]:
[ 63%] Building CXX object
test/multiarray/CMakeFiles/test_multiarray.dir/testsuccess.cxx.o
cd
Source: libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
With the latest upload there are FTBFS problems on some archs.
Running test_gridgraph
cd
/<>/libvigraimpex-1.10.0+git20160211.167be93
The particular testblock has been disabled temporarily with
1.10.0+git20160211.167be93+dfsg-3.
DS
--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/
1db160a61feaa438b2731e3dc97d60ab750b2c93
Author: Daniel Stender
Date: Wed Aug 9 00:46:43 2017 +0200
deb/changelog: finalized, upload to unstable
diff --git a/debian/changelog b/debian/changelog
index f34c475..fabb860 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,12 +1,11 @@
-libvigraimpex
On 07.08.2017 20:26, Matthias Klose wrote:
> Control: tags -1 + patch
>
> patch at
> http://launchpadlibrarian.net/332312910/libvigraimpex_1.10.0+git20160211.167be93+dfsg-2build3_1.10.0+git20160211.167be93+dfsg-2ubuntu1.diff.gz
Great! I'll take care of it shortly.
DS
--
4096R/DF5182C8 (sten...
868f5d6e0c37f6a420e2189f21496f14ada607a3
Author: Daniel Stender
Date: Sat Aug 5 19:29:04 2017 +0200
add temporarily-disable-test_looponfail_removed_test.patch
diff --git a/debian/changelog b/debian/changelog
index d1a63db..6506fe7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,8 +10,9
cddf44ea0ffdf8f4a7fc005023073452a90da60f
Author: Daniel Stender
Date: Sat Aug 5 19:47:43 2017 +0200
deb/changelog: add another bug to close
diff --git a/debian/changelog b/debian/changelog
index 39f1ffa..8c310ef 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
pytest-xdist (1.18.2
Control: retitle -1 packer: currently doesn't build (updated build-deps)
... I've mend build-deps.
DS
--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/
Package: packer
Version: 0.10.2+dfsg-6
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Packer currently doesn't build because we've begun to update the reverse-deps
for the upcoming packer update (#846549):
src/github.com/mitchellh/packer/communic
Package: python-blosc
Version: 1.4.4+ds1-3+b1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: forwarded -1 https://github.com/Blosc/python-blosc/issues/125
The building of python-blosc currenty breaks:
Running Sphinx v1.5.6
making output
Source: pytest-xdist
Version: 1.15.0-3
Severity: serious
Justification: fails to build from source
Control: forwarded -1 https://github.com/pytest-dev/pytest-xdist/issues/163
There is a new test failure with Pytest >= 3.1.0, during the build it appears
the first time with Python 2.7:
===
7cd007a50fe894534d61baefbac00a5d9c3e70ff
Author: Daniel Stender
Date: Wed Jul 19 08:26:36 2017 +0200
add fix-test-failures.patch
diff --git a/debian/changelog b/debian/changelog
index 9194596..bd73860 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,8 +5,9 @@ pytest-catchlog (1.2.2-3
Source: pytest-catchlog
Version: 1.2.2-1
Severity: serious
Justification: fails to build from source
Control: forwarded -1 https://github.com/eisensheng/pytest-catchlog/issues/68
Latest Pytest in Debian (3.1.3) breaks the tests of this package:
test_pytest_catchlog.py::test_record_tuples PASSED
Source: numba
Version: 0.33.0-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=s390x&ver=0.33.0-1&stamp=1495911986&raw=0
This test breaks on s390x:
numba/tests/test_array_attr.py::TestNestedArrayAttr::test_shape Segmentation
fault
E: pybuild pybuild:283: test: plug
Source: numba
Version: 0.33.0-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=ppc64el&ver=0.33.0-1&stamp=1495912133&raw=0
Tests break with a segault on s390x:
numba/tests/test_array_manipulation.py::TestArrayManipulation::test_add_axis2_npm
PASSED
numba/tests/test
Source: numba
Version: 0.33.0-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=mips&ver=0.33.0-1&stamp=1495913987&raw=0
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=mipsel&ver=0.33.0-1&stamp=1495915594&raw=0
This test breaks appears on the mips archs:
n
Source: numba
Version: 0.33.0-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=armel&ver=0.33.0-1&stamp=1495912245&raw=0
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=armhf&ver=0.33.0-1&stamp=1495912383&raw=0
FTBFS on armel and armhf:
http_proxy='127.0.0
Source: numba
Version: 0.33.0-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=armel&ver=0.33.0-1&stamp=1495912245&raw=0
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=armhf&ver=0.33.0-1&stamp=1495912383&raw=0
Tests are immediately breaking on armel and arm
Source: numba
Version: 0.33.0-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=i386&ver=0.33.0-1&stamp=1495914429&raw=0
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=arm64&ver=0.33.0-1&stamp=1495916190&raw=0
This test failure appears:
___
Source: numba
Version: 0.33.0-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=arm64&ver=0.33.0-1&stamp=1495916190&raw=0
There are a couple of supposedly related test failures on arm64:
___ TestTimedeltaArithmeticNoPython.test_mul ___
Source: numba
Version: 0.33.0-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=arm64&ver=0.33.0-1&stamp=1495916190&raw=0
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=i386&ver=0.33.0-1&stamp=1495914429&raw=0
This test failure appears:
__
Source: numba
Version: 0.33.0-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=i386&ver=0.33.0-1&stamp=1495914429&raw=0
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=arm64&ver=0.33.0-1&stamp=1495916190&raw=0
This failure appears among the tests several tim
Source: numba
Version: 0.33.0-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=i386&ver=0.33.0-1&stamp=1495914429&raw=0
https://buildd.debian.org/status/fetch.php?pkg=numba&arch=arm64&ver=0.33.0-1&stamp=1495916190&raw=0
This failure appeared in the tests:
__
For the latest upload (0.33.0 in experimental), the tests have been failsafed
again so that there are even packages building to try out.
Bug reports on the individual test failures and other remaining things to fix
are coming up.
Failsafe is going to be removed again when the package hits unstabl
667a3a9cd54a9b9530cf43b31b89625a114bc3df
Author: Daniel Stender
Date: Wed Apr 5 10:25:20 2017 +0200
add changes from NMU
diff --git a/debian/changelog b/debian/changelog
index d37e07e..44bc19f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+execnet (1.4.1-3.1) unstable; urgency=medium
+
+ * Non
667a3a9cd54a9b9530cf43b31b89625a114bc3df
Author: Daniel Stender
Date: Wed Apr 5 10:25:20 2017 +0200
add changes from NMU
diff --git a/debian/changelog b/debian/changelog
index d37e07e..44bc19f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+execnet (1.4.1-3.1) unstable; urgency=medium
+
+ * Non
Control: retitle -1 packer: sometimes FTBFS: FAIL
github.com/mitchellh/packer/packer/rpc
Actually, there's a test failure happening in these cases:
=== RUN TestPostProcessorRPC
panic: Fail in goroutine after TestMuxBroker has completed
goroutine 308 [running]:
panic(0x87a720, 0xc4201436a0)
Control: retitle ! packer: sometimes FTBFS:
github.com/mitchellh/packer/version[no test files]
Unfortunately this also happens on other archs:
? github.com/mitchellh/packer/version [no test files]
dh_auto_test: go test -v -p 1 -timeout 30m github.com/mitchellh/packer {...}
github.com
In the test builds for reproducible builds, this repeatedly occurs as segfault:
testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed
PASSEDSegmentation fault
E: pybuild pybuild:283: test: plugin custom failed with: exit code=139:
python3.5 -m pytest -v -x -rs testing/
dh_a
On 08.03.2017 01:01, Santiago Vila wrote:
> severity 854494 serious
> thanks
>
> Dear maintainer:
>
> I expected a general guideline from Release Managers regarding
> packages which FTBFS randomly like this one, but that will most surely
> not happen for stretch.
>
> So, the only guideline I hav
... in.
I'm going to upload this already.
There are a couple of problems left, I'll file bug reports on them so that they
could be
discussed, focused on if wanted.
DS
--
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/
On 17.02.2017 16:32, Daniel Stender wrote:
> On 17.02.2017 15:41, lumin wrote:
>> Control: tags -1 +patch
>>
>> Here is an NMU patch for this package. I intended to file an
>> RFS but the debomatic build failure stopped me to do so.
>>
>> The build failure w
On 17.02.2017 15:41, lumin wrote:
> Control: tags -1 +patch
>
> Here is an NMU patch for this package. I intended to file an
> RFS but the debomatic build failure stopped me to do so.
>
> The build failure was caused by testsuite failure:
> http://debomatic-amd64.debian.net/distribution#experimen
On 14.02.2017 08:43, Rebecca N. Palmer wrote:
> Found the problem: the affected functions (
> https://sources.debian.net/src/theano/0.8.2-4/theano/sparse/opt.py/#L862 ,
> https://sources.debian.net/src/theano/0.8.2-4/theano/sparse/opt.py/#L1902 )
> cast a pointer-to-intptr_t (64 bit) to a pointe
On 14.02.2017 08:59, Ole Streicher wrote:
> Hi Daniel,
>
> I don't really see why you declare this failure as "serious". From the
> source (and the bug name), it basically means that theano took a bit
> longer to calculate than scipy for the same calculation. This may depend
> on the scipy version
Thanks for the patch. It solves most of the problems towards Numpy 1.12, but
from the complete
testsuite 4 errors remain:
ERROR: test_DownsampleFactorMax
(theano.tensor.signal.tests.test_pool.TestDownsampleFactorMax)
--
Traceba
On 08.02.2017 16:15, Ole Streicher wrote:
> tag 834910 pending
> thanks
>
> Hello,
>
> Bug #834910 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=collab-maint/lasagne.git;a=commit
On 08.02.2017 13:54, Sandro Tosi wrote:
> control: reopen -1
>
> not so fast..
>
> On Wed, Feb 8, 2017 at 4:17 AM, Ole Streicher wrote:
>> Hi Daniel, Sandro,
>>
>> I tried to reproduce the bug and could not get the failure with the
>> latest unstable (Python revision 3.5.3-1). So, I would recomm
On 08.02.2017 10:17, Ole Streicher wrote:
> Hi Daniel, Sandro,
>
> I tried to reproduce the bug and could not get the failure with the
> latest unstable (Python revision 3.5.3-1). So, I would recommend to
> either close the bug as unreproducible, or at least to downgrade the
> severity.
>
> IMO t
I've got deeper into it now. I think that was pinned by mistake, but pydocstyle
was mend, the corresponding changelog
entry is on that. I've commented on the commit [1], waiting for a reaction ...
A simple patch for setup.py which removes the pinning would do it, because
actually there are no AP
On 05.02.2017 15:08, Sebastian Andrzej Siewior wrote:
> Control: tags 827068 + patch
> Control: tags 827068 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for m2crypto (versioned as 0.24.0-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer. I a
... please hang on, I'm going to provide a patch.
DS
--
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/
On 31.01.2017 21:52, Sebastian Andrzej Siewior wrote:
> On 2016-11-15 12:36:09 [+0100], Daniel Stender wrote:
>> On Mon, 14 Nov 2016 19:52:31 +0100 Daniel Stender
>> wrote:
>>> The diff doesn't work like that on the upstream code in the archive
>>
>> ...
All right. Thx for the bug report & patch.
Best,
DS
On 30.01.2017 22:11, Santiago Vila wrote:
> Package: src:golang-github-masterzen-winrm
> Version: 0.0~git20160323.0752679-2
> Severity: serious
> Tags: patch
>
> Dear maintainer:
>
> I tried to build this package in stretch with "dpkg-buildpac
Package: packer
Version: 0.10.2+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Since the tests are not fail safed anymore the package starts to FTBFS on arm64,
armel and armhf. There is a single test failure:
=== RUN TestConfigInstantiat
Control: tags -1 + unreproducible
Tell me if I miss something ... otherwise I'm going to close this issue in the
next days.
Anyway, Bcolz is in unstable now.
DS
--
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/
Package: bcolz
Version: 1.1.0+ds1-2
Severity: serious
Justification: fails to build from source
Control: forwarded -1 https://github.com/Blosc/bcolz/issues/329
There is a test failure on s390x and powerpc [1]:
==
FAIL: test_left
On 23.01.2017 14:02, Martin Steigerwald wrote:
> Package: python-bcolz
> Version: 1.1.0+ds1-2
> Severity: serious
>
> Dear Maintainer,
>
> on searching what to install to make
>
> […]/pkg-fio> tools/hist/fiologparser_hist.py
> Traceback (most recent call last):
> File "tools/hist/fiologparser_
Control: retitle -1 pycodestyle >= 2.1.0 breaks prospector 0.12.4
[CC-ing the pycodestyle maintainers]
OUCH!
In the upstream repo it's said that there are API changes in pycodestyle > 2.0.0
= 2.1.0 [1], and therefore 2.0.0 is pinned. I've missed that, and also the
DEP-8 tests
of prospector kept
cb7c53771f95c073bb945e54dd52af1f3983e9ba
Author: Daniel Stender
Date: Sun Jan 22 16:00:41 2017 +0100
add test_gateway-fix-race-condition.patch
diff --git a/debian/changelog b/debian/changelog
index cfb08a8..461e30f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,11 @@
execnet (1.4.1-3) UNRELEASED; urgency
On 22.01.2017 13:54, Andreas Cadhalpun wrote:
> I think the answer is that you were lucky. ;)
> The problem can be reproduced by running:
> $ python -m pytest -v -x -rs testing/test_gateway.py
>
> I did that 100 times and it failed 78 times, working only 22 times.
>
> The failing test contains:
>
Package: packer
Version: 0.10.2+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
dh_auto_test is currently failsafed because the tests aren't passing through,
there are some failures on missing test-fixtures which appear to be missing
in the t
On 21.01.2017 06:22, Rogério Brito wrote:
> Control: severity 852048 grave
> Control: retitle 852048 prospector: dependencies can't be satisfied in
> testing/sid
>
> Hi, Daniel.
>
> On Jan 21 2017, Rogério Brito wrote:
>> I have used prospector successfully in the past, but I can't now, as it
>>
On Thu, 5 Jan 2017 21:40:12 + Christopher Hoskin
wrote:
> Dear Dan,
>
> Thanks for getting in touch - sorry for not replying sooner. "winrm"
> is the name of a Microsoft Windows command, so users might expect a
> Linux command with the same name to perform a similar function. I'm
> not famil
Control: retitle -1 test failures with Numpy 1.12
This is been working on upstream [1], marked as being a cornerstone for release
9.0.
A partly fix has become available recently [2], but some failures remains.
DS
[1] https://github.com/Theano/Theano/issues/5396 (Make Theano support numpy
1.12)
Control: severity -1 important
This appeared once in reproducible builds CI, but currently not again. Hard to
reproduce, any comments
welcome. However, I'm lowering the severity of this bug report.
DS
--
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http
Control: severity -1 important
Like #840466 this is a test failure which appears only in DEP-8 testing.
Furthermore, it's
hard to reproduce, local autopkgtesting succeeds [1] (gets skipped in a Python2
environment).
This shouldn't be RC.
[1] http://www.danielstender.com/uploads/execnet-local-de
Source: pytest-httpbin
Version: 0.2.3-1
Severity: grave
Justification: renders package unusable
Pytest actually can't use the plugin:
/usr/lib/python2.7/dist-packages/pytest_httpbin/plugin.py:4: ImportWarning: Not
importing directory '/usr/lib/python2.7/dist-packages/pytest_httpbin/certs':
mis
Thanks for reporting this.
There are 3 errors and 2 failures in the tests in that build, the TypeError:
"'numpy.float64' object cannot be interpreted
as an index" (3) points to being another problem with numpy 1.12.0.
1)
ERROR: test_infer_shape (theano.sparse.tests.test_sp2.BinomialTester)
Source: llvmlite
Version: 0.14.0-2
Severity: serious
File: llvmlite
Justification: fails to build from source
llvmlite [1] (currently in experimental) has a test failure on some archs
(mips, ppc64el, s390x etc.) [2]:
==
ERROR:
Hi Christopher,
we have a binaries-have-conflict between our packages and we have to negotiate
how to handle
this.
I standpoint is, masterzen-winrm was in first (2016-04-14), so I would like to
ask if
you could change your package to solve this. I would change mine if this would
be the
other w
Control: severity -1 normal
Reopened because this appeared again in reproducible builds CI. However, this
failure is only
hardly reproducible. Currently it builds fine throughout. Therefore, I'm
lowering the severity
of this bug report.
DS
--
4096R/DF5182C8
Debian Developer (sten...@debian.or
Control: severity -1 normal
I've filed this about a FTBFS in reproducible builds CI on i386 in unstable.
But this
couldn't hardly be reproduced. The new package (0.2.3) doesn't contain a
particular
fix for this, but appears to build fine throughout. DEP-8 test doesn't brought
up
something, what
Control: severity -1 important
This is a toolchain problem. s390x support is currently removed for golang-go
[1].
And rdependend packages are going to be removed [2].
I'll leave this bug open until this happened.
DS
[1] https://bugs.debian.org/844258 (golang-go: go SIGILL on s390x)
[2] https:
Control: forwarded -1 https://github.com/pierrec/lz4/issues/9
This is reproducible on harris (Linux harris 3.16.0-4-armmp #1 SMP Debian
3.16.36-1+deb8u2
(2016-10-19) armv7l GNU/Linux).
DS
--
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.daniel
Source: execnet
Version: 1.4.1-2
Severity: serious
Justification: fails to build from source
Execnet currently fails in DEP-8 tests [1]:
testing/test_channel.py::TestStringCoerce::test_2to3 FAILED
{...}
=== FAILURES ===
Source: execnet
Version: 1.4.1-2
Severity: serious
Justification: fails to build from source
There is a test failure in this package from the reproducible builds CI in the
2nd build
on amd64 [1]:
testing/test_gateway.py::TestTracing::test_popen_stderr_tracing FAILED
{...}
==
Control: retitle -1 execnet:
testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen]
FAILED
There are two more RC test failures recorded, one from reproducible builds CI,
the other from DEP-8
tests. I'll file more bugs on these, now.
I can't reproduce this right now a
f99f42ab9ebb10c8f813ac9e5efe1fe79d295225
Author: Daniel Stender
Date: Sat Nov 19 22:43:47 2016 +0100
pass custom mfpu also to $CXXFLAGS
diff --git a/debian/changelog b/debian/changelog
index 8e6b0cf..d941e25 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+afl (2.34b-5) experimental; urgency=medium
Control: found -1 afl/2.34b-4
I've tried to build while passing "-mfpu=vfpv3" to $CFLAGS for llvm_mode/, but
although
it appears NEON has been disabled by that ("-target-feature -neon"), it doesn't
work out
like that (test build on abel which is non-NEON):
[*] Testing the CC wrapper and instru
bly to not build golang on Debian, sadly.
>
> On 17 November 2016 at 01:40, Daniel Stender
> wrote:
>
>> Package: packer
>> Version: 0.10.1+dfsg-1
>> Severity: serious
>> Justification: fails to build from source (but built successfully in the
>> past
Package: packer
Version: 0.10.1+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Packer currently (recently 0.10.2+dfsg-1) fails to build on s390x:
dh_auto_build -O--buildsystem=golang
cd obj-s390x-linux-gnu
go install -v
On 15.11.2016 19:11, Martín Ferrari wrote:
> Daniel,
>
>
> On 15/11/16 18:46, Daniel Stender wrote:
>
>> the new package golang-golang-x-oauth2-google-dev missed Breaks against the
>> previous
>> package revision:
>
> Oh, I completely forgot that, thank
Source: golang-golang-x-oauth2
Version: 0.0~git20161103.0.36bc617-2
Severity: serious
Justification: Policy 7.6
Hi,
the new package golang-golang-x-oauth2-google-dev missed Breaks against the
previous
package revision:
$ sudo dpkg -i
golang-golang-x-oauth2-google-dev_0.0~git20161103.0.36bc617
On Mon, 14 Nov 2016 19:52:31 +0100 Daniel Stender
wrote:
> The diff doesn't work like that on the upstream code in the archive
... the same is true for 0.25.1.
I'm on it.
DS
--
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/
Source: pytest-httpbin
Version: 0.2.0-1
Severity: serious
Justification: fails to build from source
The package currently doesn't build:
tests/test_httpbin.py::test_chunked_encoding[https] FAILED
=== FAILURES ===
__
On Sun, 16 Oct 2016 14:05:28 +0200 Kurt Roeckx wrote:
> tags 827068 + patch
> thanks
>
> Hi,
>
> A patch is available at:
> https://gitlab.com/m2crypto/m2crypto/merge_requests/98
>
> Kurt
The diff doesn't work like that on the upstream code in the archive, I'll
package
a repo snapshot as soon
Source: golang-github-pierrec-lz4
Version: 0.0~git20151216.222ab1f-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
The build of this package break in the reprod
a4abda1a4f8cdff5b4bd59df968e861f9d27bcb5
Author: Daniel Stender
Date: Mon Nov 14 13:50:31 2016 +0100
deb/rules: add -mfpu=vfp3 to $CFLAGS on armhf
diff --git a/debian/changelog b/debian/changelog
index 547b2ff..e78f22f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+afl (2.34b-3) UNRELEASED; urgency
Hi Gilles,
that's o.k. with me. Thx for taking care of this.
Best,
DS
On 06.11.2016 12:10, Gilles Filippini wrote:
> Control: tags 8430040 + patch
> Control: tags 8430040 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for c-blosc (versioned as 1.11.1+ds1-2.1) and
> uploaded it to DELA
Package: afl
Version: 2.34b-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
>From 2.30b-1 onwards (the first package which was tried to build against
>llvm-toolchain
> 3.7 on this arch), AFL build breaks with "illegal instruction" trying to
> co
1 - 100 of 219 matches
Mail list logo
