Processing commands for cont...@bugs.debian.org:
> severity 861987 serious
Bug #861987 [flightcrew] flightcrew: insecure use of /tmp
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
861987: http://bugs.debian.org/cgi-bin/bugr
Hi Samuel,
I'm not sure whether this bug should be marked as serious. Since your test
cases are mixing the default cc (GCC-6) and clang-3.8 together.
I reproduced the failure you reported, but there is a simpler solution
to the issue
as shown below.
test$ CC=clang-3.8 make
clang-3.8-c -o tes
Package: libclc-amdgcn
Version: 0.2.0+git20160907-3
Severity: grave
Justification: renders package unusable
Tags: upstream patch
Hardware information:
- platform: Clover (Mesa)
- device: AMD OLAND (DRM 2.48.0 / 4.9.0-2-amd64, LLVM 3.9.1)
With the libclc version from testing nearly all OpenCL
On 6 May 2017 at 22:34, Tomasz Buchert wrote:
| Hey,
|
| On 06/05/17 14:43, Dirk Eddelbuettel wrote:
| >
| > On 6 May 2017 at 20:43, Tomasz Buchert wrote:
| > | On 06/05/17 19:23, Tomasz Buchert wrote:
| > | > [...]
| > |
| > | Ok, I confirm that dlopen() is required to properly resolve some
| >
Your message dated Sat, 06 May 2017 21:06:16 +
with message-id
and subject line Bug#861748: fixed in rmpi 0.6-6-4
has caused the Debian Bug report #861748,
regarding r-cran-rmpi: Loading library fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Am / On Sat, 06 May 2017 22:09:54 +0300
schrieb / wrote serge :
> Dear Maintainer,
I'm not a Debian maintainer but will try to clear up your situation
nevertheless.
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> $ audacity
>
>* What was the outc
Lucas Nussbaum wrote...
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.
[ reformatted ]
> > AssertionError:
| '[4294967295L, 4294967294L, 4294967296L, 4294967293L, 4294967297L,
8589934590L, 2147483647L]' !=
| '[4294
Hey,
On 06/05/17 14:43, Dirk Eddelbuettel wrote:
>
> On 6 May 2017 at 20:43, Tomasz Buchert wrote:
> | On 06/05/17 19:23, Tomasz Buchert wrote:
> | > [...]
> |
> | Ok, I confirm that dlopen() is required to properly resolve some
> | symbols later: I can only assume that openmpi does some magic
> |
Processing commands for cont...@bugs.debian.org:
> forwarded 860164 https://github.com/mrash/fwsnort/pull/14
Bug #860164 {Done: Axel Beckert } [fwsnort] fwsnort:
iptables-restore v1.6.0: invalid port/service `[6789]' specified. Error
occurred at line: 11462
Set Bug forwarded-to-address to 'https
Processing control commands:
> block 861957 by -1
Bug #861957 [raincat] raincat: Raincat doesn't run: user error (unknown GLUT
entry glutInit)
861957 was not blocked by any bugs.
861957 was not blocking any bugs.
Added blocking bug(s) of 861957: 861976
--
861957: http://bugs.debian.org/cgi-bin/
Your message dated Sat, 06 May 2017 19:48:48 +
with message-id
and subject line Bug#861868: fixed in ilisp 5.12.0+cvs.2004.12.26-24
has caused the Debian Bug report #861868,
regarding installation script /usr/lib/emacsen-common/packages/install/ilisp
not idempotent
to be marked as done.
This
On 6 May 2017 at 20:43, Tomasz Buchert wrote:
| On 06/05/17 19:23, Tomasz Buchert wrote:
| > [...]
|
| Ok, I confirm that dlopen() is required to properly resolve some
| symbols later: I can only assume that openmpi does some magic
| there. Here are 2 solutions I came up with:
|
| 1. Just like
Processing commands for cont...@bugs.debian.org:
> limit source ilisp
Limiting to bugs with field 'source' containing at least one of 'ilisp'
Limit currently set to 'source':'ilisp'
> tags 850072 + pending
Bug #850072 [ilisp] ilisp: Fail to intall into emacs25.
Added tag(s) pending.
> tags 861868
Processing commands for cont...@bugs.debian.org:
> severity 861868 serious
Bug #861868 [ilisp] installation script
/usr/lib/emacsen-common/packages/install/ilisp not idempotent
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Package: audacity
Version: 2.0.6-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
# apt-get install audacity
* What exactly did you do (or not do) that was effective (or
ineffective)?
$ audacity
* What was the outcome o
On Sat, May 06, 2017 at 08:00:11PM +0200, Michael Stapelberg wrote:
> Thanks. It seems like getaddrinfo() is returning two results when resolving
> localhost. Can you provide the contents of your hostname resolution-related
> configuration please? I.e., /etc/hosts, /etc/resolv.conf,
> /etc/nsswitch
On 06/05/17 19:23, Tomasz Buchert wrote:
> [...]
Ok, I confirm that dlopen() is required to properly resolve some
symbols later: I can only assume that openmpi does some magic
there. Here are 2 solutions I came up with:
1. Just like in #741297: add another dlopen() call to the chain (see
a
Processing control commands:
> severity -1 grave
Bug #861957 [raincat] raincat: Raincat doesn't run: user error (unknown GLUT
entry glutInit)
Severity set to 'grave' from 'important'
--
861957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861957
Debian Bug Tracking System
Contact ow...@bugs
Hi
I uplaoded an NMU to unstable to fix this bug. I mostly used the debdiff
prepared by Louis Bouchard but fixed the version number to be
0.93.1+nmu1 instead of 0.93.2 and actually fixed the systemd unit in the
way proposed in this bug. The debdiff attached to the bug missed the
critical changes.
Your message dated Sat, 06 May 2017 18:19:39 +
with message-id
and subject line Bug#809669: fixed in unattended-upgrades 0.93.1+nmu1
has caused the Debian Bug report #809669,
regarding unattended-upgrades: files got created under /var/ mountpoint
to be marked as done.
This means that you clai
Processing commands for cont...@bugs.debian.org:
> notfound 861870 8.13.11+dfsg1-3
Bug #861870 {Done: Balasankar C } [src:gitlab]
gitlab: CVE-2017-8778
No longer marked as found in versions gitlab/8.13.11+dfsg1-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
8
Hi
On Tue, May 02, 2017 at 10:01:31PM +0200, Salvatore Bonaccorso wrote:
> CVE-2017-8400[0]:
> | In SWFTools 0.9.2, an out-of-bounds write of heap data can occur in the
> | function png_load() in lib/png.c:755. This issue can be triggered by a
> | malformed PNG file that is mishandled by png2swf.
Thanks. It seems like getaddrinfo() is returning two results when resolving
localhost. Can you provide the contents of your hostname resolution-related
configuration please? I.e., /etc/hosts, /etc/resolv.conf,
/etc/nsswitch.conf, anything else you might have tweaked in that area.
On Sat, May 6, 20
Processing control commands:
> tags 861040 + patch
Bug #861040 [camping] camping: broken symlink:
/usr/share/doc/camping/rdoc/fonts/Lato-RegularItalic.ttf ->
../../../../fonts/truetype/lato/Lato-RegularItalic.ttf
Ignoring request to alter tags of bug #861040 to the same tags previously set
> tag
Control: tags 861040 + patch
Control: tags 861040 + pending
Chris Lamb wrote...
> Christoph Biedl wrote:
>
> > So would just naming the link Lato-RegularItalic.ttf [..]
> > fix the issue?
>
> Works for me :) Updated patch attached.
Thanks for testing, here we go:
Dear maintainer,
I've prepa
Processing commands for cont...@bugs.debian.org:
> affects 860689 src:blockdiag
Bug #860689 [python-wand] double free or corruption when loading unhandled SVG
from BytesIO
Added indication that 860689 affects src:blockdiag
> thanks
Stopping processing here.
Please contact me if you need assistan
On samedi 6 mai 2017 13:01:50 CEST you wrote:
> Lintian uses the YAML::XS module to validate YAML in
> debian/upstream/metadata.
Unless debian/upstream/metadata needs fancy YAML format (e.g. anchor alias
tags ...), the easiest way out it to use YAML::Tiny instead of YAML::XS. This
should be a dr
Your message dated Sat, 6 May 2017 23:00:37 +0530
with message-id
<20170506173037.vekbilq5hdsnbigc@chelamattathu.chelamattathu.localhost>
and subject line Re: Requesting unblock
has caused the Debian Bug report #861870,
regarding gitlab: CVE-2017-8778
to be marked as done.
This means that you cla
Hi,
On Sat, 6 May 2017 10:43:13 +0200 Tomasz Buchert wrote:
>
> Hi,
> in this case I'm going to close my request in #861914, and let you
> take care of it.
I just confirmed that this vulnerability does not apply to the GitLab version we
have in Debian. This is because the SVG rendering feature
On 06/05/17 11:58, Dirk Eddelbuettel wrote:
>
> Hi Tomasz,
>
> [...]
>
> While true for us, it is not always true for Rmpi on other system so upstream
> for Rmpi added this. I haven't heard from him a while.
>
> But I do recall that we needed this for some other braindeadness with the
> multiple s
Processing commands for cont...@bugs.debian.org:
> tags 861958 + confirmed
Bug #861958 [lintian] lintian: insecure YAML validation
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
861958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8619
Processing commands for cont...@bugs.debian.org:
> severity 846548 serious
Bug #846548 [libengine-pkcs11-openssl] libengine-pkcs11-openssl: Can't load
pkcs11 engine into openssl
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance
Hi Tomasz,
On 6 May 2017 at 18:46, Tomasz Buchert wrote:
| On 03/05/17 17:54, Ralf Stubner wrote:
| > [...]
|
| Hi all,
| this is really another iteration of #741297.
|
|
| Honestly, I believe that the whole test of openmpi "existence" using
| dlopen is unnecessary. This code is only executed
Your message dated Sun, 7 May 2017 01:50:09 +0900
with message-id
and subject line Re:
has caused the Debian Bug report #861965,
regarding Fails to build for sid, build-depends not strict enough
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
On 03/05/17 17:54, Ralf Stubner wrote:
> [...]
Hi all,
this is really another iteration of #741297.
Honestly, I believe that the whole test of openmpi "existence" using
dlopen is unnecessary. This code is only executed if we have compiled
against openmpi, so why do we have to double-check that i
Thanks for the strace. We can see that sslh creates two sockets of the same
address family, on the same host and port:
[…]
[pid 23812] socket(AF_INET, SOCK_STREAM, IPPROTO_IP) = 3
[pid 23812] setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
[pid 23812] setsockopt(3, SOL_IP, IP_FREEBIND, [1], 4)
Processing commands for cont...@bugs.debian.org:
> notfound 858250 1.0.0~rc2+git20161109.131.5137186-2
Bug #858250 [runc] Fails to build for stretch, build-depends not strict enough
No longer marked as found in versions runc/1.0.0~rc2+git20161109.131.5137186-2.
> notfound 861966 0.1.1+dfsg1-2
Bug
Processing control commands:
> clone -1 -2
Bug #858250 [runc] Fails to build, build-depends not strict enough
Bug 858250 cloned as bug 861965
> notfound -1 runc 1.0.0~rc2+git20161109.131.5137186-2
Unknown command or malformed arguments to command.
> affects -1 stretch
Bug #858250 [runc] Fails to
Processing control commands:
> clone -1 -2
Bug #858250 [runc] Fails to build for stretch, build-depends not strict enough
Bug 858250 cloned as bug 861966
> notfound -1 runc 1.0.0~rc2+git20161109.131.5137186-2
Unknown command or malformed arguments to command.
> affects -1 stretch
Bug #858250 [run
control: clone -1 -2
control: notfound -1 runc 1.0.0~rc2+git20161109.131.5137186-2
control: affects -1 stretch
control: retitle -1 Fails to build for stretch, build-depends not strict enough
control: notfound -2 runc 0.1.1+dfsg1-2
control: affects -2 sid
control: retitle -2 Fails to build for sid,
Your message dated Sat, 06 May 2017 15:14:33 +
with message-id
and subject line Bug#861959: fixed in torcs 1.3.3+dfsg2-1
has caused the Debian Bug report #861959,
regarding torcs: non-free car models
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 06 May 2017 15:08:12 +
with message-id
and subject line Bug#861486: fixed in openblas 0.2.19-3
has caused the Debian Bug report #861486,
regarding openblas: random segfaults on mips64el
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Sat, 06 May 2017 15:04:26 +
with message-id
and subject line Bug#860164: fixed in fwsnort 1.6.5-2
has caused the Debian Bug report #860164,
regarding fwsnort: iptables-restore v1.6.0: invalid port/service `[6789]'
specified. Error occurred at line: 11462
to be marked as don
Your message dated Sat, 06 May 2017 15:05:53 +
with message-id
and subject line Bug#860705: fixed in golang-github-shopify-sarama 1.9.0-2
has caused the Debian Bug report #860705,
regarding golang-github-shopify-sarama: FTBFS on i386: dh_auto_test: go test -v
-p 1 github.com/Shopify/sarama gi
On Sat, May 6, 2017 at 4:02 PM, Adam Borowski wrote:
> On Sat, May 06, 2017 at 03:44:42PM +0200, Michael Stapelberg wrote:
> > I pushed a commit adding a patch which fixes the test by picking an
> > unused port. The mechanism is not atomic (i.e., the port is picked by
> > the test process, as opp
Hi,
thanks a lot for adopting the package and taking care of it! Are you
planning to upload a fix for unstable, too?
Regards,
Tobias
signature.asc
Description: OpenPGP digital signature
Processing commands for cont...@bugs.debian.org:
> tag 860705 + pending
Bug #860705 [src:golang-github-shopify-sarama] golang-github-shopify-sarama:
FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/Shopify/sarama
github.com/Shopify/sarama/mocks returned exit code 1
Added tag(s) pending.
>
tag 860705 + pending
thanks
Some bugs in the golang-github-shopify-sarama package are closed in
revision cac636158aa618abe4d957cc7a4c5c0a7df6e1e8 in branch 'master'
by David Lazăr
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-shopify-sarama.git/commit/
Processing commands for cont...@bugs.debian.org:
> fixed 861959 1.3.7+dfsg-1
Bug #861959 [torcs-data-cars] torcs: non-free car models
There is no source info for the package 'torcs-data-cars' at version
'1.3.7+dfsg-1' with architecture ''
Unable to make a source version for version '1.3.7+dfsg-1'
Package: desmume
Version: 0.9.10-2
Followup-For: Bug #777640
Dear Maintainer,
can confirm bug
"serge@debian:~$ desmume
Failed to set format: Invalid argument
Microphone init failed.
DeSmuME 0.9.10 svn0 dev+ x86-JIT NOSSE
terminate called after throwing an instance of 'std::bad_alloc'
what(): s
Florian Vessaz wrote:
> To me it looks like the issue is triggered by something specific to the
> configuration of your Docker container. To enable us to reproduce the
> issue, would you be able to share a simple Dockerfile to build a Docker
> image in which the problem appears?
Whilst I don't ha
On Sat, May 06, 2017 at 03:44:42PM +0200, Michael Stapelberg wrote:
> I pushed a commit adding a patch which fixes the test by picking an
> unused port. The mechanism is not atomic (i.e., the port is picked by
> the test process, as opposed to the listening process itself and
> communicated back to
Processing commands for cont...@bugs.debian.org:
> severity 861958 grave
Bug #861958 [lintian] lintian: insecure YAML validation
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
861958: http://bugs.debian.org/cgi-bin/bugreport.
On Sat, May 06, 2017 at 03:44:42PM +0200, Michael Stapelberg wrote:
> Tomasz Buchert writes:
> > On 04/05/17 04:47, Adam Borowski wrote:
> >> [...]
> >
> > I cannot reproduce these failures. I've built in my stretch sbuild
> > around 15 times, and succedeed every time.
I found just one of my mach
Hi Chris,
I tried without success to reproduce the issue building the package in a
Docker container based on the debian:stretch image available from
hub.docker.com with the addition of the build dependencies and a couple
of tools installed with apt.
To me it looks like the issue is triggered by s
Am 01.05.2017 um 02:31 schrieb Roger Shimizu:
There's a pull-request patch upstream:
https://github.com/go-asn1-ber/asn1-ber/pull/7/commits/4563065
But unfortunately it's not clean, and only consider 32-bit system.
Need to figure out a better way.
Hi,
I would suggest that we remove this pac
Processing control commands:
> tags -1 + pending
Bug #851877 [src:sslh] sslh: FTBFS randomly (sbuild hangs)
Added tag(s) pending.
--
851877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
control: tags -1 + pending
Hi,
Tomasz Buchert writes:
> On 04/05/17 04:47, Adam Borowski wrote:
>> [...]
>
> I cannot reproduce these failures. I've built in my stretch sbuild
> around 15 times, and succedeed every time.
>
> I use:
> gbp buildpackage --git-builder='sbuild --source-only-changes -
Package: torcs-data-cars
Version: 1.3.3+dfsg-0.4
Severity: serious
while I was working on a new upstream version of Torcs, I discovered
that the Debian package includes many non-free car models. The license
of these car models is as follows:
* Copyright / Permissions *
** Authors m
Christoph Biedl wrote:
> So would just naming the link Lato-RegularItalic.ttf [..]
> fix the issue?
Works for me :) Updated patch attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/debian/rules b/debian/ru
Your message dated Sat, 06 May 2017 13:30:02 +
with message-id
and subject line Bug#860628: fixed in golang-github-ghodss-yaml
0.0~git20150909.0.73d445a-2
has caused the Debian Bug report #860628,
regarding golang-github-ghodss-yaml: FTBFS on i386: dh_auto_test: go test -v -p
1 github.com/gh
Processing commands for cont...@bugs.debian.org:
> tags 861486 + upstream patch
Bug #861486 [src:openblas] openblas: random segfaults on mips64el
Added tag(s) patch and upstream.
> forwarded 861486 https://github.com/xianyi/OpenBLAS/pull/1178
Bug #861486 [src:openblas] openblas: random segfaults o
Christian Hofstaedtler wrote...
> * Chris Lamb [170424 11:45]:
> > > The fonts-lato ships /usr/share/fonts/truetype/lato/Lato-Italic.ttf
> > > instead.
> >
> > Indeed. Patch attached.
>
> > - ln -s /usr/share/fonts/truetype/lato/Lato-RegularItalic.ttf
> > debian/camping/usr/share/doc/camping
Processing commands for cont...@bugs.debian.org:
> owner 851877 !
Bug #851877 [src:sslh] sslh: FTBFS randomly (sbuild hangs)
Owner recorded as Michael Stapelberg .
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
851877: http://bugs.debian.org/cgi-bin/bugreport.cgi
Since there's already a newer package in unstable, it's
necessary to use "testing-proposed-updates", so I write to
release team by filing unblock request:
https://bugs.debian.org/861953
Changes are pushed to mentors branch (updated):
https://anonscm.debian.org/cgit/pkg-go/packages/runc.git/com
On Tue, May 2, 2017 at 10:23 AM, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> On 2 May 2017 at 19:23, Michael Stapelberg wrote:
>
>> Sorry for the late reply, I’ve been swamped.
>>
>> On Fri, Apr 21, 2017 at 10:28 AM, Niels Thykier
>> wrote:
>>
>>> Michael Stapelberg:
>>> > On F
Processing commands for cont...@bugs.debian.org:
> tag 860628 + pending
Bug #860628 [src:golang-github-ghodss-yaml] golang-github-ghodss-yaml: FTBFS on
i386: dh_auto_test: go test -v -p 1 github.com/ghodss/yaml returned exit code 2
Added tag(s) pending.
> thanks
Stopping processing here.
Please
tag 860628 + pending
thanks
Some bugs in the golang-github-ghodss-yaml package are closed in
revision 473230dd32d60b19b3737535bf544eca5db1ff1c in branch 'master'
by Michael Stapelberg
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-ghodss-yaml.git/commit
Processing control commands:
> severity -1 grave
Bug #861952 [src:libcgi-validop-perl] libcgi-validop-perl: FTBFS on May 1st (?)
Severity set to 'grave' from 'important'
> tags -1 stretch-ignore
Bug #861952 [src:libcgi-validop-perl] libcgi-validop-perl: FTBFS on May 1st (?)
Added tag(s) stretch-ig
Processing commands for cont...@bugs.debian.org:
> tags 860164 + pending
Bug #860164 [fwsnort] fwsnort: iptables-restore v1.6.0: invalid port/service
`[6789]' specified. Error occurred at line: 11462
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistanc
tag 858250 + pending
thanks
Some bugs in the runc package are closed in revision
14fb6ea3b964fbab720c0071e64e04754718310a in branch ' mentors' by
Roger Shimizu
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/runc.git/commit/?id=14fb6ea
Commit message:
debian/co
Processing commands for cont...@bugs.debian.org:
> tag 858250 + pending
Bug #858250 [runc] Fails to build, build-depends not strict enough
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
858250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bu
Hi again,
Axel Beckert wrote:
> I also noticed that there is a new upstream release from shortly
> before Debian's freeze (December 2016) at
> http://www.cipherdyne.org/fwsnort/download/, but neither the upstream
> changelog nor the diff shows anything which looks related to this bug
> report.
Ju
On Sat, 6 May 2017 12:29:08 +0900
Roger Shimizu wrote:
> releasing commit pushed to branch mentors.
> package is uploaded to mentors for RFS.
upload sponsored by deferred/2 (BTS#861936).
updated commit pushed to branch mentors2, with tag.
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6
Control: tag -1 + confirmed
Control: user bugsqu...@qa.debian.org
Control: usertag -1 + a...@debian.org
Hi,
allorder wrote:
> - Update the snort rules: sudo fwsnort --update-rules
> - Run fwsnort: sudo fwsnort
> - instantiate the fwsnort policy: sudo /var/lib/fwsnort/fwsnort.sh
>
> The result:
>
Processing control commands:
> tag -1 + confirmed
Bug #860164 [fwsnort] fwsnort: iptables-restore v1.6.0: invalid port/service
`[6789]' specified. Error occurred at line: 11462
Added tag(s) confirmed.
> user bugsqu...@qa.debian.org
Unknown command or malformed arguments to command.
> usertag -1
Processing commands for cont...@bugs.debian.org:
> owner 860628 !
Bug #860628 [src:golang-github-ghodss-yaml] golang-github-ghodss-yaml: FTBFS on
i386: dh_auto_test: go test -v -p 1 github.com/ghodss/yaml returned exit code 2
Owner recorded as Michael Stapelberg .
> thanks
Stopping processing her
Your message dated Sat, 06 May 2017 08:45:55 +
with message-id
and subject line Bug#861888: Removed package(s) from unstable
has caused the Debian Bug report #834186,
regarding cpp-netlib: FTBFS: 94% tests passed, 1 tests failed out of 17
to be marked as done.
This means that you claim that t
Processing commands for cont...@bugs.debian.org:
> found 860735 8:6.9.7.4+dfsg-5
Bug #860735 {Done: Bastien Roucariès } [src:imagemagick]
CVE-2017-7942: memory leak in avs
Marked as found in versions imagemagick/8:6.9.7.4+dfsg-5.
> thanks
Stopping processing here.
Please contact me if you need a
Michael Biebl wrote...
> Am 06.05.2017 um 00:00 schrieb Christoph Biedl:
> > I've prepared an NMU for gcr (versioned as 3.20.0-5.1), upload to
> > DELAYED/5 will follow in a few hours. Please feel free to tell me if I
> > should delay it longer.
> >
>
> Seems to be missing doc/
That's not obvi
On 06/05/17 11:12, Balasankar C wrote:
> Hi Tomasz,
>
> GitLab package co-maintainer here. We will be uploading the fix to unstable
> and
> requesting an unblock, hopefully by Monday. In the mean time, there is already
> an unblock request open[0] for the latest version in unstable,
> 8.13.11+dfs
Hi,
> Christoph Biedl wrote:
> > tags 861523 moreinfo unreproducible
> > thanks
In all cases I am building in a Docker container, so that could be
the underlying cause.
I can actually get two different FTBFS; the aforementioned "test-ls"
one if I let my container inherit the timezone from the ho
Le vendredi 05 mai 2017 à 22:06 +0100, James Cowgill a écrit :
> On 05/05/17 12:10, Graham Inggs wrote:
> > Control: reassign -1 src:openblas 0.2.19-2
> > Control: retitle -1 openblas: random segfaults on mips64el
> > Control: affects -1 src:julia
> >
> > Hi Sébastien
> >
> > I was able to repro
83 matches
Mail list logo