Dima Kogan:
> Niels Thykier writes:
>
>> The issue in geda-gaf cannot be solved in debhelper correctly. Please
>> have a look at #766711 to understand the reasoning.
>>
>> Basically:
>> * We can only support two style of binNMUs: arch:all -> arch:all OR
>>arch:any -> arch: any. Anything el
Processing commands for cont...@bugs.debian.org:
> clone 856349 -1
Bug #856349 [src:mpi4py] mpi4py: FTBFS (Exception: MPI_ERR_WIN: invalid window)
Bug 856349 cloned as bug 857604
> severity -1 serious
Bug #857604 [src:mpi4py] mpi4py: FTBFS (Exception: MPI_ERR_WIN: invalid window)
Severity set to '
Processing commands for cont...@bugs.debian.org:
> forwarded 857546 https://github.com/boothj5/profanity/issues/280
Bug #857546 [profanity] profanity: Server certificates are not verified
Set Bug forwarded-to-address to
'https://github.com/boothj5/profanity/issues/280'.
> thanks
Stopping processi
Processing commands for cont...@bugs.debian.org:
> found 857546 0.5.0-0.1
Bug #857546 [profanity] profanity: Server certificates are not verified
Marked as found in versions profanity/0.5.0-0.1.
> found 857546 0.4.7-1
Bug #857546 [profanity] profanity: Server certificates are not verified
Marked a
Hi,
I have back-ported the patch that limits number of threads to 10 to current
debian version (1.5.4-1).
With these changes build pass successfully on my local mips and mipsel machines.
The patch is attached, if you want to go with this solution.
This change is already merged in 1.6.1 release.
Hi!
On 03/06/2017 10:49 AM, John Paul Adrian Glaubitz wrote:
> The attached debdiff contains a trivial patch which changes the declaration
> of tbl[] from "char" to "signed char". With the patch applied, I verified
> that the package builds successfully on armhf.
Any progress on this? Shall I go
Hi all,
Thanks for the bug report and for the thoughful advice.
On 2017-03-10.11:18, Vincent Bernat wrote:
> ❦ 10 mars 2017 09:29 GMT, Simon McVittie :
>
> >> I suppose that's why I am in copy (the other actions are pretty obvious
> >> and I suppose Scott will apply them soon; I can also do th
Thanks Radovan. I plan to upload 1.6.1 to Debian soon (via my sponsor
Roberto Sanchez) so let's do that instead of backporting.
Processing control commands:
> tags 631057 + pending
Bug #631057 [bibcursed] bibcursed: FTBFS with --as-needed
Added tag(s) pending.
> tags 817375 + patch
Bug #817375 [src:bibcursed] bibcursed: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817375 + pending
Bug #817375 [src:bibcursed] bi
Processing control commands:
> tags 631057 + pending
Bug #631057 [bibcursed] bibcursed: FTBFS with --as-needed
Ignoring request to alter tags of bug #631057 to the same tags previously set
> tags 817375 + patch
Bug #817375 [src:bibcursed] bibcursed: Removal of debhelper compat 4
Ignoring request t
Control: tags 631057 + pending
Control: tags 817375 + patch
Control: tags 817375 + pending
Dear maintainer,
I've prepared an NMU for bibcursed (versioned as 2.0.0-6.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.
Regards.
--
regards,
Your message dated Mon, 13 Mar 2017 14:15:00 +0100
with message-id <20170313131457.gm2ms4r6jgbzp...@mapreri.org>
and subject line Re: Bug#846705: cadvisor: FTBFS: dh_auto_build: go install -v
-p 1 github.com/google/cadvisor github.com/google/cadvisor/api
github.com/google/cadvisor/cache github.co
On Mon, 13 Mar 2017 at 23:43:52 +1100, Scott Leggett wrote:
> FYI the version bump originated from this post to the upstream mailing
> list[0], which shows upstream's somewhat relaxed attitude to ABI
> stability. I guess this is understandable as the libraries are intended
> to be private.
This lo
Your message dated Mon, 13 Mar 2017 15:07:19 +
with message-id
and subject line Bug#857565: Removed package(s) from unstable
has caused the Debian Bug report #669541,
regarding underscore.logger: FTBFS: SyntaxError: In
src/underscore.logger.coffee, octal escape sequences "\033[#{color}m" are
Your message dated Mon, 13 Mar 2017 15:07:19 +
with message-id
and subject line Bug#857565: Removed package(s) from unstable
has caused the Debian Bug report #669541,
regarding underscore.logger: FTBFS: new copyright notices found
to be marked as done.
This means that you claim that the probl
Your message dated Mon, 13 Mar 2017 15:08:41 +
with message-id
and subject line Bug#857570: Removed package(s) from unstable
has caused the Debian Bug report #817397,
regarding cl-postoffice: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has be
Your message dated Mon, 13 Mar 2017 15:09:17 +
with message-id
and subject line Bug#857571: Removed package(s) from unstable
has caused the Debian Bug report #817400,
regarding cl-salza: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been de
Your message dated Mon, 13 Mar 2017 15:09:56 +
with message-id
and subject line Bug#857572: Removed package(s) from unstable
has caused the Debian Bug report #817366,
regarding athcool: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Mon, 13 Mar 2017 15:10:45 +
with message-id
and subject line Bug#857626: Removed package(s) from unstable
has caused the Debian Bug report #817314,
regarding bsign: Mandatory debian/compat for debhelper
to be marked as done.
This means that you claim that the problem has be
Your message dated Mon, 13 Mar 2017 15:10:45 +
with message-id
and subject line Bug#857626: Removed package(s) from unstable
has caused the Debian Bug report #800288,
regarding bsign: Please migrate a supported debhelper compat level
to be marked as done.
This means that you claim that the pr
found 850507 4.20.0-2
thanks
Hello Jordi.
As you have already noticed, this still fails in (most of the) reproducible
builds autobuilers:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-tideland-golib.html
To double-check, I've built this a lot of times in my ow
Processing commands for cont...@bugs.debian.org:
> found 850507 4.20.0-2
Bug #850507 {Done: Jordi Mallach }
[src:golang-github-tideland-golib] golang-github-tideland-golib: FTBFS randomly
(failing tests)
Marked as found in versions golang-github-tideland-golib/4.20.0-2; no longer
marked as fixe
Source: putty
Version: 0.63-10
Severity: grave
Tags: security upstream patch
Justification: user security hole
Hi,
the following vulnerability was published for putty.
CVE-2017-6542[0]:
|integer overflow permits memory overwrite by forwarded ssh-agent
|connections
If you fix the vulnerability p
Thanks for this QA work. I am travelling right now and am not in a
position to fix this now, but I will do so very soon.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter
Processing commands for cont...@bugs.debian.org:
> forcemerge 850719 850863
Bug #850719 [src:node-rollup] FTBFS: uses npm to download from the network
during the build
Bug #850863 [src:node-rollup] node-rollup: FTBFS due to missing
build-dependency on npm
Severity set to 'normal' from 'serious'
Processing commands for cont...@bugs.debian.org:
> severity 850719 serious
Bug #850719 [src:node-rollup] FTBFS: uses npm to download from the network
during the build
Bug #850863 [src:node-rollup] node-rollup: FTBFS due to missing
build-dependency on npm
Severity set to 'serious' from 'normal'
S
¡Hola John!
El 2017-03-13 a las 12:40 +0100, John Paul Adrian Glaubitz escribió:
Hi!
On 03/06/2017 10:49 AM, John Paul Adrian Glaubitz wrote:
The attached debdiff contains a trivial patch which changes the declaration
of tbl[] from "char" to "signed char". With the patch applied, I verified
t
Your message dated Mon, 13 Mar 2017 18:18:36 +
with message-id
and subject line Bug#855869: fixed in dsniff 2.4b1+debian-24
has caused the Debian Bug report #855869,
regarding dsniff: segfaults on portmapper messages
to be marked as done.
This means that you claim that the problem has been de
Source: audiofile
Severity: grave
Tags: security
Hi,
please see these security tracker entries for details, which
have all the links to the reports, github issues and patches:
https://security-tracker.debian.org/tracker/CVE-2017-6829
https://security-tracker.debian.org/tracker/CVE-2017-6831
https
Processing commands for cont...@bugs.debian.org:
> found 857651 0.3.6-1
Bug #857651 [src:audiofile] Multiple security issues
Marked as found in versions audiofile/0.3.6-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
857651: http://bugs.debian.org/cgi-bin/bugre
Followup-For: Bug #856869
Hi Sylvestre,
this issue also shows up in clang-4.0 and clang-5.0. Do you prefer
separate bug reports for them or does the fix "automatically" flow to
the newer versions?
e.g.
0m46.8s ERROR: FAIL: Broken symlinks:
/usr/bin/scan-build-5.0-py -> ../share/clang/scan-bui
I'm unable to reproduce the bug.
Upon upgrade you should have seen the NEWS via apt-listchanges.
You're right as far as README.Debian is concerned. IMO it might be
adjusted like this:
--- a/README.Debian 2017-01-07 17:36:04.0 +0100
+++ b/README.Debian 2017-03-13 20:14:53.8187592
Package: liblld-4.0
Version: missing liblld-4.0.so.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...):
0m24.5s ERROR: FAIL: Broken sy
Package: pybit-client
Version: 1.0.0-2.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...):
1m36.3s ERROR: FAIL: Broken symlinks:
/v
Hi,
On Wed, 11 Jan 2017 00:35:19 + Jonathan McCrohan
wrote:
Unfortunately upstream [1] [2] is not responsive at the moment. I have
noticed another fork [3] which is in significantly better shape when
using Mercurial 4.0 (only two tests failing), but this has diverged
significantly from th
Le 13/03/2017 à 20:22, Andreas Beckmann a écrit :
> Followup-For: Bug #856869
>
> Hi Sylvestre,
>
> this issue also shows up in clang-4.0 and clang-5.0. Do you prefer
> separate bug reports for them or does the fix "automatically" flow to
> the newer versions?
>
> e.g.
>
> 0m46.8s ERROR: FAIL: Brok
Processing control commands:
> severity -1 serious
Bug #856805 [gstreamer1.0-crystalhd] gstreamer1.0-crystalhd: libgstbcmdec.so
not found by gstreamer
Severity set to 'serious' from 'important'
--
856805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856805
Debian Bug Tracking System
Contact
Your message dated Mon, 13 Mar 2017 20:49:02 +
with message-id
and subject line Bug#856805: fixed in crystalhd 1:0.0~git20110715.fdd2f19-12
has caused the Debian Bug report #856805,
regarding gstreamer1.0-crystalhd: libgstbcmdec.so not found by gstreamer
to be marked as done.
This means that
Your message dated Mon, 13 Mar 2017 20:50:39 +
with message-id
and subject line Bug#854000: fixed in libplist 1.12+git+1+e37ca00-0.1
has caused the Debian Bug report #854000,
regarding CVE-2017-5834 CVE-2017-5835 CVE-2017-5836
to be marked as done.
This means that you claim that the problem h
Your message dated Mon, 13 Mar 2017 20:50:38 +
with message-id
and subject line Bug#852385: fixed in libplist 1.12+git+1+e37ca00-0.1
has caused the Debian Bug report #852385,
regarding libplist: CVE-2017-5545
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Mon, 13 Mar 2017 20:50:38 +
with message-id
and subject line Bug#851196: fixed in libplist 1.12+git+1+e37ca00-0.1
has caused the Debian Bug report #851196,
regarding libplist: CVE-2017-5209
to be marked as done.
This means that you claim that the problem has been dealt with
Package: vlc-plugin-vlsub
Version: 0.9.13-1
Severity: grave
Justification: renders package unusable
/usr/lib/vlc/lua/extensions is no longer on the Lua script search path, so the
script included in vlc-plugin-vlsub will not be loaded. It should move to
/usr/share/vlc/lua/extensions instead.
Also,
Processing control commands:
> clone -1 -2
Bug #856864 {Done: Sylvestre Ledru } [liblldb-3.8-dev]
liblldb-3.8-dev: broken symlinks: /usr/lib/llvm-3.8/lib/liblldb*.so
Bug 856864 cloned as bug 857683
> reassign -2 liblldb-3.9-dev
Bug #857683 {Done: Sylvestre Ledru } [liblldb-3.8-dev]
liblldb-3.8-d
On Sat, Mar 11, 2017 at 08:15:02PM +0100, Andreas Henriksson wrote:
> Could you please test editing nfs-blkmap.service on your system
> and replace:
> PIDFile=/var/run/blkmapd.pid
> with:
> PIDFile=/run/blkmapd.pid
> .. and report back if that solves the issue or not?
Yes, this fixes the issue.
B
Followup-For: Bug #856864
Control: clone -1 -2
Control: reassign -2 liblldb-3.9-dev
Control: found -2 1:3.9.1-4
Control: retitle -2 liblldb-3.9-dev: broken symlinks:
/usr/lib/llvm-3.9/lib/liblldb*.so
Hi,
this issue also shows up in liblldb-{3.9,4.0,5.0}-dev. Sorry for missing
this earlier.
0m35
Your message dated Mon, 13 Mar 2017 21:48:55 +
with message-id
and subject line Bug#856904: fixed in ksirk 4:16.04.0-1.1
has caused the Debian Bug report #856904,
regarding ksirk FTBFS on architectures where char is unsigned
to be marked as done.
This means that you claim that the problem has
Hi Michael,
On Fri, Mar 10, 2017 at 07:26:58PM +0100, Michael Biebl wrote:
> On Sun, 26 Feb 2017 17:00:22 +0100 Florian Schlichting
> > Given that it's too late now to get a mallard-rng package into Stretch,
> > I suggest to ship the mallard-1.0.rng file as part of the yelp-tools
> > package for
Processing commands for cont...@bugs.debian.org:
> notfound 857604 mpi4py/2.0.0-2.1
Bug #857604 {Done: Niels Thykier } [src:mpi4py] mpi4py:
FTBFS (Exception: MPI_ERR_WIN: invalid window)
No longer marked as found in versions mpi4py/2.0.0-2.1.
> thanks
Stopping processing here.
Please contact me
On 11/03/17 02:46, gregor herrmann wrote:
From reading the above URLs, it seems that
remote_addr -> client_addr
remote_ip -> client_ip
should do the trick.
Could you maybe try this proposed fix?
If it works, we can prepare an updated package for stretch.
I tried that, and it's bet
On Thu, Dec 15, 2016 at 10:35:16AM +0100, Matthias Klose wrote:
> remaining issues:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=gcc-5-legacy;users=debian-...@lists.debian.org
All the actionable ones are done (apart from llvm-toolchain-snapshot,
which doesn't seem to explictly be using any
Your message dated Tue, 14 Mar 2017 00:33:39 +
with message-id
and subject line Bug#843038: fixed in elki 0.7.1-3
has caused the Debian Bug report #843038,
regarding FTBFS test failures on slow CPUs (test timeout)
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 14 Mar 2017 00:50:21 +
with message-id
and subject line Bug#788769: fixed in yelp-tools 3.18.0-3
has caused the Debian Bug report #788769,
regarding yelp-check validate fails without networking: relax-ng: failed to
load external entity [..] mallard-1.0.rng
to be marked
On Wed, 01 Mar 2017 15:49:41 +0100 Dominik George wrote:
> Package: opendmarc
> Version: 1.3.2~Beta1-2
> Severity: grave
> Justification: renders package unusable
>
> At some point, OpenDMARC stopped honouring the Socket option in its
> config file. This results in 127.0.0.1:12302 never being bou
Control: tag -1 pending
Hi,
On Sat, 11 Mar 2017 at 20:29:11 +0100, Salvatore Bonaccorso wrote:
> 1.2.4 roundcube release fixed a XSS issue in handling of a style tag
> inside of an svg element.
Thanks for the ping and the pointers! I applied the fix to 1.2.3
(unstable) and 1.1.5 (jessie-backpor
Processing control commands:
> tag -1 pending
Bug #857473 [src:roundcube] roundcube: CVE-2017-6820: XSS issue in handling of
a style tag inside of an svg element
Added tag(s) pending.
--
857473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857473
Debian Bug Tracking System
Contact ow...@bug
Package: ioquake3
Version: 1.36
Severity: grave
Hi,
earlier today ioquake3 fixed a vulnerability that, as far as I
understand, could let malicious multiplayer servers execute code on
connecting clients.
It affects all prior versions of ioquake3 (and I think also original
Quake 3).
Details:
h
Processing commands for cont...@bugs.debian.org:
> fixed 857426 8:6.8.9.9-5+deb8u8
Bug #857426 {Done: Bastien ROUCARIES }
[src:imagemagick] [Bug 1671630] Memory leak in IsOptionMember function
The source 'imagemagick' and version '8:6.8.9.9-5+deb8u8' do not appear to
match any binary packages
Ma
Processing control commands:
> severity -1 serious
Bug #787291 [needrestart-session] needrestart-session: doesn't show the same
results as needrestart
Severity set to 'serious' from 'important'
--
787291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787291
Debian Bug Tracking System
Contact
Hello Bastien,
On Sat, Mar 11, 2017 at 03:18:04PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:imagemagick package:
>
> #857426: [Bug 1671630] Memory leak in IsOptionMember function
>
> It has been closed
Processing commands for cont...@bugs.debian.org:
> fixed 857426 8:6.9.2.10+dfsg-1
Bug #857426 {Done: Bastien ROUCARIES }
[src:imagemagick] [Bug 1671630] Memory leak in IsOptionMember function
Marked as fixed in versions imagemagick/8:6.9.2.10+dfsg-1.
> thanks
Stopping processing here.
Please con
Processing commands for cont...@bugs.debian.org:
> fixed 857426 8:6.9.6.2+dfsg-2
Bug #857426 {Done: Bastien ROUCARIES }
[src:imagemagick] [Bug 1671630] Memory leak in IsOptionMember function
Marked as fixed in versions imagemagick/8:6.9.6.2+dfsg-2.
> thanks
Stopping processing here.
Please conta
Hi,
On Tue, Mar 14, 2017 at 07:23:25AM +0100, Salvatore Bonaccorso wrote:
> Hello Bastien,
>
> On Sat, Mar 11, 2017 at 03:18:04PM +, Debian Bug Tracking System wrote:
> > This is an automatic notification regarding your Bug report
> > which was filed against the src:imagemagick package:
> >
❦ 14 mars 2017 04:16 +0100, Guilhem Moulin :
>> 1.2.4 roundcube release fixed a XSS issue in handling of a style tag
>> inside of an svg element.
>
> Thanks for the ping and the pointers! I applied the fix to 1.2.3
> (unstable) and 1.1.5 (jessie-backports).
>
> Could someone else in the team up
63 matches
Mail list logo