Package: libmyodbc
Version: 5.1.10-3
Followup-For: Bug #835166
Same issue here.
However, I have 4 installation of debian-unstable, only 1 has this issue.
I don't know what caused this in that installation.
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unst
Processing commands for cont...@bugs.debian.org:
> tags 857986 + sid stretch
Bug #857986 [npm] npm: This pakcage is 3 years old? (consider removal)
Added tag(s) stretch and sid.
> tags 857294 + sid
Bug #857294 [src:asterisk-prompt-es] asterisk-prompt-es: should be removed from
the archive?
Added
I actually did give a use case for this: try installing polymer as per the
instruction given on my initial report. It just doesn't work, as Jeremy
states. NPM is a growing, dynamic repository and you'll be hard pressed to
find any major package that is 3 years old and 100% compatible with the
curre
Am 17.03.2017 um 00:56 schrieb Michael Biebl:
> Package: gdm3
> Version: 3.22.1-2
> Severity: serious
>
>
> To reproduce the problem:
>
> reboot, login, logout, switch to console, login as root, systemctl
> restart gdm3.
>
> The result ist a constantly respawned gdm3.service which fails to star
Processing commands for cont...@bugs.debian.org:
> block 857986 by 857993
Bug #857986 [npm] npm: This pakcage is 3 years old? (consider removal)
857986 was blocked by: 857990 857988 857989 857994 857991
857986 was not blocking any bugs.
Added blocking bug(s) of 857986: 857993
>
End of message, sto
2017-03-17 0:30 GMT+01:00 Ben Finney :
> Control: tags -1 + moreinfo
>
> Alex Henry wrote:
>> Severity: grave
>> Justification: renders package unusable
>
> Thank you for considering the severity of bug reports. You claim the
> package is unusable in general, but I don't see anything in your
> des
Processing commands for cont...@bugs.debian.org:
> block 857986 by 857988 857989 857990 857991 957993 857994
Bug #857986 [npm] npm: This pakcage is 3 years old? (consider removal)
857986 was not blocked by any bugs.
857986 was not blocking any bugs.
Added blocking bug(s) of 857986: 857991, 857990,
Processing control commands:
> tags -1 + moreinfo
Bug #857986 [npm] npm: This pakcage is 3 years old? (consider removal)
Added tag(s) moreinfo.
--
857986: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
Alex Henry wrote:
> Severity: grave
> Justification: renders package unusable
Thank you for considering the severity of bug reports. You claim the
package is unusable in general, but I don't see anything in your
description that supports this.
The only description of
Hi Kirill!
> My case is not in the list of the cases, described in clone(2),
> when wrong pid may be returned, so this is a BUG.
Which case in particular do you mean? From the manpage it seems that
getpid() is simply not reliable under various circumstances and that
one should always use the sysc
Package: npm
Version: 1.4.21+ds-2
Severity: grave
Justification: renders package unusable
Sorry for opening such a non-standard bug report
but this page leads me to believe that the most
up-to-date version we have for this package on
Debian is from 2014 (see changelog on the menu on
the right side
Processing control commands:
> severity -1 serious
Bug #857748 [rt4-extension-customfieldsonupdate] Please package current version
- 1.02
Severity set to 'serious' from 'normal'
--
857748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857748
Debian Bug Tracking System
Contact ow...@bugs.debi
Your message dated Thu, 16 Mar 2017 21:19:00 +
with message-id
and subject line Bug#857651: fixed in audiofile 0.3.6-4
has caused the Debian Bug report #857651,
regarding Multiple security issues
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 16 Mar 2017 20:49:24 +
with message-id
and subject line Bug#598976: fixed in directfb 1.7.7-2
has caused the Debian Bug report #598976,
regarding directfb: FTBFS on armel: error: davinci_gfxdriver.h: No such file or
directory
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> tag 857651 pending
Bug #857651 [src:audiofile] Multiple security issues
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
857651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857651
Debian
tag 857651 pending
thanks
Hello,
Bug #857651 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://anonscm.debian.org/git/pkg-multimedia/audiofile.git/commit/?id=ff91739
---
commit ff91739ab9299170451d3b2f50a
Hi Alexander,
Thanks a million for the speedy response. After upgrading to the new
version minidlna appears to function properly, so as far as I'm
concerned this bug can be closed. Would the problem reappear I'll open
another ticket.
Once again, thanks so much for the prompt support.
Chee
Package: minidlna
Version: 1.1.6+dfsg-1
Followup-For: Bug #857849
Dear Maintainer,
I installed minidlna on Stretch. Fresh installation without any
modification to config file seems to work : right after install, minidlna
is started (by systemd ?) and is recognised by other devices.
Command 'pgrep
Processing commands for cont...@bugs.debian.org:
> tag 598976 pending
Bug #598976 [src:directfb] directfb: FTBFS on armel: error:
davinci_gfxdriver.h: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
598976: http://b
tag 598976 pending
thanks
Hello,
Bug #598976 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://anonscm.debian.org/git/pkg-multimedia/directfb.git/commit/?id=cef88eb
---
commit cef88eb94194684cccf6279c8e134
On 2017-03-16 20:56, Rhonda D'Vine wrote:
> Hi,
>
> * Andreas Beckmann [2017-03-16 20:48:35 CET]:
>> during a test with piuparts I noticed your package is no longer
>> installable in sid:
>>
>> The following packages have unmet dependencies:
>> tworld : Depends: tworld-data (= 1.3.2-2+b1) b
Hi,
* Andreas Beckmann [2017-03-16 20:48:35 CET]:
> during a test with piuparts I noticed your package is no longer
> installable in sid:
>
> The following packages have unmet dependencies:
> tworld : Depends: tworld-data (= 1.3.2-2+b1) but 1.3.2-2 is to be installed
>
> This dependency i
Control: notforwarded -1
Hi,
On Sat, 28 Jan 2017 09:25:05 +0100 Lucas Nussbaum wrote:
> Source: dstat
> Version: 0.7.3-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170128 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuil
Processing control commands:
> notforwarded -1
Bug #852927 [src:dstat] dstat: FTBFS: Test failures
Unset Bug forwarded-to-address
--
852927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: dstat
Version: 0.7.3-1
Severity: serious
Justification: Policy 4.9
Hi,
When running the testsuite, the ntp dstat plugin tries to get the time
using NTP from 0.fedora.pool.ntp.org. As policy says, accessing the
network in this way is not permitted for packages in the main archive.
Thanks,
Package: tworld
Version: 1.3.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
The following packages have unmet dependencies:
tworld : Depends: tworld-data (= 1.3.2-2+b1) but 1.3.2-2
Package: tagainijisho
Version: 1.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
The following packages have unmet dependencies:
tagainijisho : Depends: tagainijisho-common (= 1.0
Source: mldemos
Version: 0.5.1+git.1.ee5d11f-1
Severity: serious
https://buildd.debian.org/status/package.php?p=mldemos&suite=sid
...
g++ -c -pipe -Wno-all -Wno-unused-variable -Wno-unused-parameter -Wtrigraphs
-Wreturn-type -Wnon-virtual-dtor -Wunused-value -Wunknown-pragmas -Wno-shadow
-g -O2
Package: kmldonkey
Version: 2.0.5+kde4.3.3-3+b1
--- Please enter the report below this line. ---
On my system, Debian Sid up-to-date, I start mldonkey-server with a systemd
user service (btw, it does not matter how mldonkey-server starts, kmldonkey
keeps crashing even if mldonkey-server is a sy
Package: gitlab
Version: 8.13.11+dfsg-2
Severity: serious
Hi,
the postinst uses several
export $(cat $conffile)
constructs which are very fragile to the file content. This breaks on
comments, quoted multi-word strings, and probably many more things.
Since adding comments while making local m
d...@debian.org should be forwarding to my drake.diedr...@gmail.com
account. I've uploaded empire-hub 1.0.2.2 several times since December,
with a Closes: 809625, but it still hasn't closed.
The two most recent upload attempts from .upload:
u empire-hub_1.0.2.2.tar.gz ftp.upload.debian.org Th
Your message dated Thu, 16 Mar 2017 18:18:50 +
with message-id
and subject line Bug#857889: fixed in calendar-exchange-provider 3.9.0-3
has caused the Debian Bug report #857889,
regarding calendar-exchange-provider: FTBFS: python: can't open file
'/usr/lib/icedove-devel/sdk/bin/typelib.py': [
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package profanity
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian
On Thu, Mar 16, 2017 at 05:01:31PM +, Barak A. Pearlmutter wrote:
> Parallel builds were failing for some other mysterious reason, so I
> was trying to get that worked out. But in the interests of sanity I
> simply disabled parallel builds and uploaded the fixed version.
Well, while trying to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Parallel builds were failing for some other mysterious reason, so I
was trying to get that worked out. But in the interests of sanity I
simply disabled parallel builds and uploaded the fixed version. Thanks
for the nudge!
Cheers,
- --Barak.
-BE
Your message dated Thu, 16 Mar 2017 16:33:40 +
with message-id
and subject line Bug#857940: fixed in diffoscope 80
has caused the Debian Bug report #857940,
regarding diffoscope: FTBFS: test errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Processing control commands:
> severity -1 normal
Bug #857953 [bash] bash: debian/rules execute $(STRIP) even when empty
Severity set to 'normal' from 'serious'
--
857953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with proble
Control: severity -1 normal
On 16.03.2017 17:13, Tim Ruehsen wrote:
> Package: bash
> Version: 4.4-4+b1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Dear Maintainer,
>
> in debian/rules the $(STRIP) command is tried to be executed even
Package: libdevmapper-dev
Version: 2:1.02.137-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m22.8s ERROR: FAIL: Broken symlink
Your message dated Thu, 16 Mar 2017 16:18:57 +
with message-id
and subject line Bug#857893: fixed in python-eventlet 0.19.0-6
has caused the Debian Bug report #857893,
regarding python-eventlet: Non-determistically FTBFS due to unreliable timing
in tests
to be marked as done.
This means that
Mattia Rizzolo wrote:
> The buildds are using the aspcud sbuild resolver for experimental
I'm using mk-build-deps w/--no-install-recommends. It does not get
installed with that (and therefore I did not see the build failures
prior to uploading).
> Anyhow, if a package causes the build to fail it
Package: bash
Version: 4.4-4+b1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
in debian/rules the $(STRIP) command is tried to be executed even when empty.
The code is
ifneq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
ifneq
Processing commands for cont...@bugs.debian.org:
> tags 857940 + pending
Bug #857940 [src:diffoscope] diffoscope: FTBFS: test errors
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
857940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8579
tags 857940 + pending
thanks
Fixed in Git:
https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=d03037820c34ddd168d6ce5d000e5a5dbcbf4e7f
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
On Thu, Mar 16, 2017 at 03:40:46PM +, Chris Lamb wrote:
> Assuming this is from...
>
>
> https://buildd.debian.org/status/fetch.php?pkg=diffoscope&arch=all&ver=79&stamp=1489658432&raw=0
yes.
> ... it appears to be caused by "graphicsmagick-imagemagick-compat"
> package being installed. Wi
Hi Mattia,
> […]
Assuming this is from...
https://buildd.debian.org/status/fetch.php?pkg=diffoscope&arch=all&ver=79&stamp=1489658432&raw=0
... it appears to be caused by "graphicsmagick-imagemagick-compat"
package being installed. With this package installed locally I can
reproduce the test
Your message dated Thu, 16 Mar 2017 15:34:35 +
with message-id
and subject line Bug#812032: fixed in mldemos 0.5.1+git.1.ee5d11f-1
has caused the Debian Bug report #812032,
regarding mldemos: FTBFS with GCC 6: needed for in-class initialization
to be marked as done.
This means that you claim
Your message dated Thu, 16 Mar 2017 15:10:54 +
with message-id
and subject line Bug#857900: fixed in scythe 0.994-4
has caused the Debian Bug report #857900,
regarding scythe: binNMUs always FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> tags 857878 stretch
Bug #857878 [starvoyager] starvoyager: uninstallable after binNMU
Added tag(s) stretch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
857878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
below:
> Changes:
> gcc-6 (6.3.0-9) unstable; urgency=medium
> .
> * Update to SVN 20170316 (r246188) from the gcc-6-branch.
> - Fix PR target/79261 (PPC), PR fortran/78474, PR libstdc++/79789,
>PR target/79514 (x86), PR target/79544 (PPC), PR lto/79579,
>
On Thu, Mar 16, 2017 at 05:16:48AM -0400, Anders Kaseorg wrote:
> On Thu, 16 Mar 2017, Adam Borowski wrote:
> > The bug does reproduce for me on _some_ setups, all in regular sbuild:
> >
> > successful: amd64
> > FTBFS: armhf
> > FTBFS: armhf qemu-user on amd64
> > successful: armhf on a
Source: diffoscope
Version: 79
Severity: serious
=== FAILURES ===
test_diff_meta
differences_meta = []
@skip_unless_tools_exist('img2txt', 'identify')
@skip_u
g symbols)
Closes: 854881 856903 857384 857583
Changes:
gcc-6 (6.3.0-9) unstable; urgency=medium
.
* Update to SVN 20170316 (r246188) from the gcc-6-branch.
- Fix PR target/79261 (PPC), PR fortran/78474, PR libstdc++/79789,
PR target/79514 (x86), PR target/79544 (PPC), PR lto/79579,
Bug can be closed AFAIC, issue doesn't affect me personally anymore, since
update after reportbug report. Thanks for such a prompt fix. Now if we can get
the UI changes to stick on restart Another bug report. ;-)
Your message dated Thu, 16 Mar 2017 13:03:10 +
with message-id
and subject line Re: Bug#857871: get-iplayer: Upstream says should not be
included in stretch
has caused the Debian Bug report #857871,
regarding get-iplayer: Upstream says should not be included in stretch
to be marked as done.
Hi Chris!
> debian/rules override_dh_auto_build
> make[1]: Entering directory '«BUILDDIR»'
> for idlfile in $(find chrome/ components/ debian/ defaults/ email/
> interfaces/ locale/ -type f -name *.idl); do \
> python /usr/lib/icedove-devel/sdk/bin/typelib.py
> -I"/usr/lib/icedove-de
Processing commands for cont...@bugs.debian.org:
> tags 857889 + patch
Bug #857889 [src:calendar-exchange-provider] calendar-exchange-provider: FTBFS:
python: can't open file '/usr/lib/icedove-devel/sdk/bin/typelib.py': [Errno 2]
No such file or directory
Added tag(s) patch.
> thanks
Stopping pr
Processing control commands:
> tags -1 patch
Bug #857901 [src:tennix] tennix FTBFS on architectures where char is unsigned
Added tag(s) patch.
--
857901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
Hi!
The attached debdiff contains a patch which fixes the problem by
declaring char as signed for two instances. Tested in an armhf
chroot. Works.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitae
On 16 March 2017 at 07:33, Charles Plessy wrote:
| Hi Dirk and Salvatore,
|
| > From: Dirk Eddelbuettel
| > On 11 March 2017 at 17:56, Salvatore Bonaccorso wrote:
| > |
| > | The relevant changes seem to be the following, but I might be mistaken.
(btw,
| > | is there a VCS repository for r-bas
Processing commands for cont...@bugs.debian.org:
> block 857917 by 857923
Bug #857917 [ftp.debian.org] RM: golang-gocheck -- RoQA; duplicated package
exists; RC buggy
857917 was not blocked by any bugs.
857917 was not blocking any bugs.
Added blocking bug(s) of 857917: 857923
> block 857917 by 85
Package: fglrx-modules-dkms
Version: 1:15.12-2~bpo8+3
Severity: grave
--- Please enter the report below this line. ---
The DKMS is unable to build the module for kernel 4.9.13, which is the latest
4.9 kernel in Debian Backports (4.9.13-1~bpo8+1), found in packages:
* linux-image-4.9.0-0.bpo.2-a
Source: golang-go-dbus
Severity: serious
Version: 1~bzr20150122-1
This package build-depends on (FTBFS-ed) package golang-gocheck-dev. Please
switch to build depend on golang-gopkg-check.v1-dev.
--
Sincerely,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part.
Package: jython
Version: 2.5.3-15
Severity: serious
The (system) Jython cache dir is in /usr/share/jython/Cache, while the
FHS wants to have it in /var/cache/.
This is problematic, since the cache may tend to be filled by the
installation of Jython packages or by other Jython invocations as root,
Your message dated Thu, 16 Mar 2017 11:20:29 +
with message-id
and subject line Bug#857219: fixed in zeroc-ice 3.6.3-5
has caused the Debian Bug report #857219,
regarding libzeroc-ice-dev: missing Depends: libzeroc-icestorm3.6 (=
${binary:Version})
to be marked as done.
This means that you c
On Thu, Mar 16, 2017 at 11:34:25AM +0100, Andreas Tille wrote:
> Hi Adrian,
Hi Andreas,
> On Thu, Mar 16, 2017 at 10:43:35AM +0200, Adrian Bunk wrote:
> > Source: scythe
> > Version: 0.994-3
> > Severity: serious
> >
> > https://buildd.debian.org/status/package.php?p=scythe&suite=sid
> >
> > ..
On Thu, 16 Mar 2017 08:56:10 +, Boyuan Yang wrote:
> Source: golang-gocheck
> Version: 0.0~bzr20131118+85-2
> Severity: serious
> X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org
>
> Hello,
>
> The package golang-gocheck is actually an old version of
> golang-check.v1 with
> one RC bug
Hello jtg,
On Wed, 15 Mar 2017 18:07:44 +0100
jtg wrote:
> Package: minidlna
> Version: 1.1.5+dfsg-2~bpo8+1
Please check with 1.1.6, I've just uploaded backport into archive.
> Severity: grave
I can't confirm this. On my box it worked on jessie from backports
and right now it works on Stretch.
Hi Adrian,
On Thu, Mar 16, 2017 at 10:43:35AM +0200, Adrian Bunk wrote:
> Source: scythe
> Version: 0.994-3
> Severity: serious
>
> https://buildd.debian.org/status/package.php?p=scythe&suite=sid
>
> ...
> cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong
> -Wformat -Werror
Package: python3-gleetex
Version: 2.1-1
Severity: serious
Hi
It seems that texlive packages were re-ordered internally. This did not affect
me yet, since I'm usually using texlive-full. I a clean container, GladTeX (and
its library gleetex)fails to work because of missing dependencies. This rende
Package: libc6-dev
Version: 2.24-9
Severity: grave
Dear Maintainer,
the program below shows the problem, happening on my Debian laptop.
When I create a child using clone(CLONE_VM), glibc's clone wrapper
does not update cached pid, and I receive parent's pid in getpid().
Here is output of the prog
Package: logrotate
Version: 3.11.0-0.1
Severity: serious
Since updating one of my systems from jessie to stretch in January, the
cron.daily/logrotate cron job has been generating a large email every
day which appears to contain rather verbose output about everything it does.
I notice several line
Source: golang-gocheck
Version: 0.0~bzr20131118+85-2
Severity: serious
X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org
Hello,
The package golang-gocheck is actually an old version of golang-check.v1 with
one RC bug [1]. As a result, this package should be useless and should be
removed
On Thu, 16 Mar 2017, Adam Borowski wrote:
> The bug does reproduce for me on _some_ setups, all in regular sbuild:
>
> successful: amd64
> FTBFS: armhf
> FTBFS: armhf qemu-user on amd64
> successful: armhf on arm64
>
> The timezone is the same, so is schroot/sbuild configuration, all wh
Processing commands for cont...@bugs.debian.org:
> retitle 857891 logrotate: does not rotate logs
Bug #857891 [logrotate] [logrotate does not rotate logs]
Changed Bug title to 'logrotate: does not rotate logs' from '[logrotate does
not rotate logs]'.
> thanks
Stopping processing here.
Please con
Source: tennix
Version: 1.1-3
Severity: serious
https://buildd.debian.org/status/package.php?p=tennix&suite=sid
...
g++ -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong
-Wformat -Werror=format-security -W -Wall -DVERSION=\"1.1.1\" -O2
-DPREFIX=\"usr\" -I/usr/include/python2.7
Source: scythe
Version: 0.994-3
Severity: serious
https://buildd.debian.org/status/package.php?p=scythe&suite=sid
...
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat
-Werror=format-security -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic
-DVERSION="0.994-3+b1
Source: qtads
Version: 2.1.6-1
Severity: serious
https://buildd.debian.org/status/package.php?p=qtads&suite=sid
...
In file included from tads3/tcprs.cpp:39:0:
tads3/vmbignum.h: In static member function 'static vm_obj_id_t
CVmObjBigNum::create(int, const bignum_t*)':
tads3/vmbignum.h:585:45: er
Source: python-eventlet
Version: 0.19.0-5
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Dear Maintainer,
python-eventlet's testsuite appears to use method timing
The bug does reproduce for me on _some_ setups, all in regular sbuild:
successful: amd64
FTBFS: armhf
FTBFS: armhf qemu-user on amd64
successful: armhf on arm64
The timezone is the same, so is schroot/sbuild configuration, all what
differs are architectures and kernel versions.
And it'
Your message dated Thu, 16 Mar 2017 07:36:33 +
with message-id
<1489649793.1202439.913066992.2158e...@webmail.messagingengine.com>
and subject line Re: Bug#857890: git: FTBFS: debian/rules:55: recipe for target
'override_dh_auto_test-arch' failed
has caused the Debian Bug report #857890,
rega
Hi Anders,
> I can’t reproduce this using the locale and timezone settings listed at
> https://tests.reproducible-builds.org/debian/index_variations.html
Just to be clear, I don't file bugs unless I can reproduce them myself on
my own machine, well away from the Reproducible Builds variations &
es are
rotated, old logs are removed
considering log /var/log/monit.log
log needs rotating
rotating log /var/log/monit.log, log->rotateCount is 4
dateext suffix '-20170316'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
compressing log with: /bin/gzip
renaming /v
84 matches
Mail list logo
