Your message dated Fri, 02 Oct 2020 05:48:24 +
with message-id
and subject line Bug#969577: fixed in caml-crush 1.0.10-4
has caused the Debian Bug report #969577,
regarding caml-crush: FTBFS with GCC 10: multiple definition of `my_arch'
to be marked as done.
This means that you claim that the
Steve Langasek:
> Ximin,
>
> On Tue, Sep 08, 2020 at 09:23:49PM +0100, Ximin Luo wrote:
>> You keep filing these same bugs. I have told you this many times before
>> already: this is just how rust packaging works, Britney's migration policy
>> already prevents these packages from reaching Debian
Your message dated Thu, 1 Oct 2020 22:55:42 +0100
with message-id <20201001215542.ga315...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#970883: gjs: should not migrate to testing until GNOME
Shell 3.38 is ready
has caused the Debian Bug report #970883,
regarding gjs: should not migrate to
Your message dated Thu, 01 Oct 2020 21:33:47 +
with message-id
and subject line Bug#969141: fixed in doxygen 1.8.20-3
has caused the Debian Bug report #969141,
regarding websocketpp: errors while generating documentation & FTBFS with
doxygen 1.8.19
to be marked as done.
This means that you c
control: tags -1 pending
Since it is collaborative maintained, I just uploaded and committed the patch
on git
thanks!
G.
Processing control commands:
> tags -1 pending
Bug #969141 [doxygen] websocketpp: errors while generating documentation &
FTBFS with doxygen 1.8.19
Added tag(s) pending.
--
969141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969141
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Your message dated Thu, 01 Oct 2020 20:50:59 +
with message-id
and subject line Bug#970341: fixed in rampler 1.1.1-3
has caused the Debian Bug report #970341,
regarding rampler: autopkgtest failure on arm64:
to be marked as done.
This means that you claim that the problem has been dealt with.
Hey all,
Is there a timeline on this? Still present in 20200601~deb10u1.
Cheers,
Amin
Your message dated Thu, 1 Oct 2020 22:08:39 +0200
with message-id <20201001200839.GA861363@pisco.westfalen.local>
and subject line Re: subliminal (stretch) is not working with current providers
has caused the Debian Bug report #964190,
regarding subliminal (stretch) is not working with current prov
Source: golang-github-dgrijalva-jwt-go
Version: 3.2.0-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for golang-github-dgrijalva-jwt-go.
CVE-2020-26160[0]:
| jwt-go before 4.0.0-preview1 allows attack
[Please excuse the corporate-ese that comes with my email]
Hi Andreas,
We are readying another release. I actually have the time to work on the Debian
package again. I will take care of it.
Thanks,
Amul
-Original Message-
From: Andreas Tille
Sent: Thursday, October 01, 2020 9:52 AM
To:
Thanks, Scott, it worked!
https://buildd.debian.org/status/package.php?p=mrpt&suite=sid
JL
Dear Ryan,
thank you for the bug report: wminput does segfault when it is called.
I tried to modify the source to get rid of the build warnings, which in
fact should be reported as errors. It appears to be a tough task, since
many warnings are about unapropriate pointer casts, due to the mix of
p
Paul Gevers writes:
> So, vanish stopped providing vanishabi-11.0 and vanish-modules needs
> to be fixed, otherwise vanish is not allowed to migrate to testing
> (until vanish-modules is removed from testing). vanish-modules in
> unstable is broken now, we don't want that to happen in testing.
H
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:gemma
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setti
Source: astroquery
Version: 0.4.1+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Autopkgtests have recently started running on armhf, and there
astroquery fails [1].
I've copied what I hope i
Hi again
On Fri, 7 Aug 2020 14:55:21 +, Shah, Amul wrote:
> Thanks for the ping. We have a fix, just not enough time in a day. :(
I think we should upload that fix in the near future.
Kind regards
Andreas.
--
http://fam-tille.de
Your message dated Thu, 01 Oct 2020 13:49:39 +
with message-id
and subject line Bug#971135: fixed in user-mode-linux 5.8um1
has caused the Debian Bug report #971135,
regarding user-mode-linux: FTBFS: build-dependency not installable:
linux-source-5.7
to be marked as done.
This means that you
Hi,
I wanted to let you know that I have today looked into the very same
FTBFS and submitted
the fixes upstream.
https://lists.quagga.net/pipermail/quagga-dev/2020-October/033390.html
https://lists.quagga.net/pipermail/quagga-dev/2020-October/033391.html
With those two gcc-10 builds work.
[1] co
Your message dated Thu, 01 Oct 2020 13:04:05 +
with message-id
and subject line Bug#971217: fixed in python-poppler-qt5 0.75.0-2
has caused the Debian Bug report #971217,
regarding python-poppler-qt5: FTBFS: sip: Unable to find file
"QtCore/QtCoremod.sip"
to be marked as done.
This means tha
Your message dated Thu, 01 Oct 2020 12:20:05 +
with message-id
and subject line Bug#971522: fixed in parsnp 1.5.3+dfsg-2
has caused the Debian Bug report #971522,
regarding parsnp: autopkgtest arm64 regression: raxmlHPC-PTHREADS not in system
path!
to be marked as done.
This means that you c
Hi Nilesh,
On Thu, Oct 01, 2020 at 10:06:22AM +0200, Paul Gevers wrote:
> autopkgtest [21:17:40]: test run-unit-test: [---
> [93m[1mTest 1: With GenBank Annotations[0m
> |--Parsnp 1.5.3--|
> For detailed documentation please see -->
> http://harvest.readthedocs.org/en/latest
On Thu, Oct 1, 2020 at 09:44, Xavier wrote:
Upstream source are really missing, only repacked files are available.
Relevant bug: https://github.com/Rich-Harris/locate-character/issues/6
Attaching the diff between the two dist tarballs. Only addition seems
to be that of typings and switching
Forgot this information.
apt policy libsnmp30
libsnmp30:
Installed: 5.7.3+dfsg-5+b2
Candidate: 5.7.3+dfsg-5+deb10u1
Version table:
5.7.3+dfsg-5+deb10u1 990
990 http://ftp.de.debian.org/debian unstable/main amd64 Packages
*** 5.7.3+dfsg-5+b2 100
100 /var/lib/dpkg/status
Your message dated Thu, 01 Oct 2020 18:37:13 +0800
with message-id <4091130f2559afdbad60d9981d186...@debian.org>
and subject line fixed 971100 0.51.2-1
has caused the Debian Bug report #971100,
regarding dolfinx: FTBFS: unsatisfiable build-dependency: python3-llvmlite (<
0.34) but 0.34.0-1 is to b
Package: libsnmp30
Version: 5.7.3+dfsg-5+b2
Severity: serious
Justification: Policy 7.2
Dear Maintainer,
sudo apt install libsnmp30
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
req
Hi,
I was facing the same issue in Ubuntu just recently and found that the
upstream fix [1] does address this issue. I wanted to let you know so
you can get this fixed as well a bit more easily - because from just
knowing the error this is a head-scratcher.
When you have fixed this you most likely
Unfortunately, I seem to be suffering from the same issue.
Initially I thought it was a hardware issue (system was ~10 years old), so I
replaced the Intel DH67CF with core2duo processor by an Asrock H470M-ITX and
Intel i5-10400 processor (and new case, new power supply; only SSD is re-used).
A
Hi Bastian,
On 01-10-2020 10:02, Bastian Blank wrote:
> On Thu, Oct 01, 2020 at 09:54:05AM +0200, Paul Gevers wrote:
>> https://ci.debian.net/data/autopkgtest/testing/amd64/v/varnish-modules/7232545/log.gz
>
> Why is a simple ABI transition now also a autopkgtest failure?
Because vanish-modules
On Thu, Oct 01, 2020 at 09:54:05AM +0200, Paul Gevers wrote:
> https://ci.debian.net/data/autopkgtest/testing/amd64/v/varnish-modules/7232545/log.gz
Why is a simple ABI transition now also a autopkgtest failure?
| The following packages have unmet dependencies:
| varnish-modules : Depends: varni
Source: parsnp
Version: 1.5.3+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of parsnp the autopkgtest of parsnp fails in
testing on arm64 when that autopkgtest is run with the binary
Source: varnish-modules
Version: 0.16.0-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, varn...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:varnish
Dear maintainer(s),
With a recent upload of varnish the auto
Processing control commands:
> affects -1 src:varnish
Bug #971521 [src:varnish-modules] varnish-modules: autopkgtest needs update for
new version of varnish: Depends on old ABI
Added indication that 971521 affects src:varnish
--
971521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971521
D
Your message dated Thu, 01 Oct 2020 07:48:28 +
with message-id
and subject line Bug#970899: fixed in libflame 5.2.0-3
has caused the Debian Bug report #970899,
regarding libflame: add hypothesis to numpy autopkgtests dependencies
to be marked as done.
This means that you claim that the proble
Le 01/10/2020 à 09:25, Pirate Praveen a écrit :
>
>
> On 2020, ഒക്ടോബർ 1 12:23:20 PM IST, Xavier Guimard wrote:
>> Package: node-locate-character
>> Version: 2.0.5-1
>> Severity: serious
>> Justification: source-is-missing
>>
>> 2.0.5 is packaged from npm registry temporarily to be able to buil
Processing commands for cont...@bugs.debian.org:
> forwarded 971519 https://github.com/Rich-Harris/locate-character/issues/6
Bug #971519 [node-locate-character] node-locate-character: Rebuild from sources
Set Bug forwarded-to-address to
'https://github.com/Rich-Harris/locate-character/issues/6'.
Your message dated Thu, 01 Oct 2020 07:33:30 +
with message-id
and subject line Bug#954849: fixed in mesa 20.1.9-1
has caused the Debian Bug report #954849,
regarding mesa-opencl-icd: Applications using OpenCL crash with : CommandLine
Error: Option 'polly' registered more than once!
to be mar
Your message dated Thu, 01 Oct 2020 07:33:30 +
with message-id
and subject line Bug#954849: fixed in mesa 20.1.9-1
has caused the Debian Bug report #954849,
regarding hwloc: lstopo crash with: CommandLine Error: Option 'polly'
registered more than once!
to be marked as done.
This means that
Your message dated Thu, 01 Oct 2020 07:33:30 +
with message-id
and subject line Bug#954849: fixed in mesa 20.1.9-1
has caused the Debian Bug report #954849,
regarding opencl support is broken: LLVM ERROR: inconsistency in registered
CommandLine option
to be marked as done.
This means that yo
Your message dated Thu, 01 Oct 2020 07:33:30 +
with message-id
and subject line Bug#954849: fixed in mesa 20.1.9-1
has caused the Debian Bug report #954849,
regarding does not start: LLVM ERROR: inconsistency in registered CommandLine
options
to be marked as done.
This means that you claim t
On 2020, ഒക്ടോബർ 1 12:23:20 PM IST, Xavier Guimard wrote:
>Package: node-locate-character
>Version: 2.0.5-1
>Severity: serious
>Justification: source-is-missing
>
>2.0.5 is packaged from npm registry temporarily to be able to build
>rollup 2. Upstream didn't push 2.0.5 source in git repo (last
Processing commands for cont...@bugs.debian.org:
> notfound 971519 2.0.1-6
Bug #971519 [node-locate-character] node-locate-character: Rebuild from sources
Ignoring request to alter found versions of bug #971519 to the same values
previously set
> thanks
Stopping processing here.
Please contact m
42 matches
Mail list logo
