Your message dated Fri, 11 Dec 2020 07:33:46 +
with message-id
and subject line Bug#976687: fixed in python-escript 5.6-2
has caused the Debian Bug report #976687,
regarding python3-escript: mixing incompatible libpython and libboost_python
to be marked as done.
This means that you claim that
Your message dated Fri, 11 Dec 2020 05:19:20 +
with message-id
and subject line Bug#976845: fixed in wxpython4.0 4.0.7+dfsg-7
has caused the Debian Bug report #976845,
regarding wxpython-tools needs source upload for Python 3.9 transition
to be marked as done.
This means that you claim that t
On Wed, 9 Dec 2020, Adrian Bunk wrote:
They probably don't. The tools are really just setuptools entry point
scripts. The dependency is just coming from the shebang in those scripts I
believe.
In that case it should be fixed with
override_dh_python3:
dh_python3 --shebang=/usr/bin/pyt
Your message dated Fri, 11 Dec 2020 03:48:32 +
with message-id
and subject line Bug#976990: fixed in fprintd 1.90.7-1
has caused the Debian Bug report #976990,
regarding fprintd: Impossible to verify:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1
matched rules
Your message dated Fri, 11 Dec 2020 03:48:32 +
with message-id
and subject line Bug#976990: fixed in fprintd 1.90.7-1
has caused the Debian Bug report #976990,
regarding fprintd: Latest update broke fprintd entirely
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Fri, 11 Dec 2020 01:33:30 +
with message-id
and subject line Bug#976934: fixed in notmuch 0.31.2-4
has caused the Debian Bug report #976934,
regarding notmuch: FTBFS on ppc64el: FileNotFoundError: [Errno 2] No such file
or directory: '/<>/emacs/notmuch.rsti'
to be marked as
Tomi Ollila writes:
> On Wed, Dec 09 2020, David Bremner wrote:
>
>> Under a sufficiently high level of parallelism [1] there seems to be a
>> a race condition that allows sphinx-build to start running before the
>> docstrings are extracted. This change moves the docstring stamp from
>> the phony
Your message dated Fri, 11 Dec 2020 01:11:56 +
with message-id
and subject line rust-libz-sys
has caused the Debian Bug report #975486,
regarding rust-libz-sys: autopkgtest failure: src/zlib/adler32.c: No such file
or directory
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 11 Dec 2020 00:48:22 +
with message-id
and subject line Bug#958604: fixed in ircd-irc2 2.11.2p3~dfsg-5.1
has caused the Debian Bug report #958604,
regarding ircd-irc2: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you
package: ruby-licensee
Version: 8.9.2-1
Severity: serious
Tags: bullseye, sid
The autopkgtest for ruby-licensee is failing with ruby-rugged 1.1.0.
GEM_PATH= ruby2.7 -e gem\ \"licensee\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1398:in `rescue in block in
activate_dependencies': Coul
package: ruby-gollum-rugged-apapter
Version: 0.4.4.2-2
Severity: serious
The autopkgtest for ruby-gollum-rugged-adapter is failing with ruby-rugged
1.1.0.
┌──┐
│ Checking Rubygems dependency resolution on ruby2.7
Processing commands for cont...@bugs.debian.org:
> package fprintd
Limiting to bugs with field 'package' containing at least one of 'fprintd'
Limit currently set to 'package':'fprintd'
> severity 976859 grave
Bug #976859 [fprintd] fprintd: Impossible to verify:
GDBus.Error:org.freedesktop.DBus.E
Your message dated Thu, 10 Dec 2020 22:19:20 +
with message-id
and subject line Bug#977036: fixed in skopeo 1.2.0+dfsg1-2
has caused the Debian Bug report #977036,
regarding skopeo: autopkgtest regression: cannot find package
"github.com/containers/common/pkg/retry"
to be marked as done.
Thi
Hi,
On 10/12/20 at 22:16 +0100, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 12/10/20 10:12 PM, Michael Biebl wrote:
> >> Did the test machine you used actually have that many cores?
> >
> > No idea
>
> I just checked plummer.debian.org and it has only 16 (virtual) CPUs.
>
> Would be curious
Your message dated Thu, 10 Dec 2020 21:49:19 +
with message-id
and subject line Bug#954270: fixed in kmc 3.1.1+dfsg-1
has caused the Debian Bug report #954270,
regarding kmc: autopgktest times out on multimulticore hosts
to be marked as done.
This means that you claim that the problem has bee
Source: chromium
Version: 83.0.4103.116-3.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
chromium fails to build on armhf:
| FAILED: obj/v8/v8_base_without_compiler/cpu-arm.o
| clang++ -MMD -MF obj/
On 12/10/20 10:16 PM, Michael Biebl wrote:
>>> Did the test machine you used actually have that many cores?
>>
>> No idea
>
> But given that there is only a single test, I wonder if that is really
> relevant anyway.
You're right. That's rather strange. Hmm.
Adrian
--
.''`. John Paul Adrian
Hi!
On 12/10/20 10:12 PM, Michael Biebl wrote:
>> Did the test machine you used actually have that many cores?
>
> No idea
I just checked plummer.debian.org and it has only 16 (virtual) CPUs.
Would be curious to hear whether Lucas' test machine had >= 160 CPUs.
Adrian
--
.''`. John Paul Ad
Am 10.12.20 um 22:12 schrieb Michael Biebl:
Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz:
Hi Michael!
On 12/10/20 8:42 PM, Michael Biebl wrote:
Testsuite summary for systemd-bootchart 233
=
Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz:
Hi Michael!
On 12/10/20 8:42 PM, Michael Biebl wrote:
Testsuite summary for systemd-bootchart 233
Hi Michael!
On 12/10/20 8:42 PM, Michael Biebl wrote:
>
> Testsuite summary for systemd-bootchart 233
>
> # TOTAL: 1
> # PASS: 1
> # SKIP: 0
>
Control: tag -1 pending
Hello,
Bug #954270 in kmc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/med-team/kmc/-/commit/8e0202a8386094935f162aa9472b6e743dd858a0
Processing control commands:
> tag -1 pending
Bug #954270 [src:kmc] kmc: autopgktest times out on multimulticore hosts
Added tag(s) pending.
--
954270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Thu, 10 Dec 2020 21:04:01 +
with message-id
and subject line Bug#935674: fixed in rust-blake2-rfc 0.2.18-3
has caused the Debian Bug report #935674,
regarding librust-blake2-rfc+clippy-dev/amd64 unsatisfiable Depends:
librust-clippy-0.0.41+default-dev
to be marked as done.
Your message dated Thu, 10 Dec 2020 20:48:26 +
with message-id
and subject line Bug#975737: fixed in bluebird-gtk-theme 1.3-2.1
has caused the Debian Bug report #975737,
regarding src:bluebird-gtk-theme: fails to migrate to testing for too long:
maintainer built arch:all binary
to be marked a
Processing control commands:
> reassign -1 git-buildpackage
Bug #977083 [pristine-tar,git-buildpackage,devscripts] pristine-tar: fails to
checkout when there are multiple source tarballs
Bug reassigned from package 'pristine-tar,git-buildpackage,devscripts' to
'git-buildpackage'.
No longer marke
Control: reassign -1 git-buildpackage
Control: forcemerge 917789 -1
On Fri, Dec 11, 2020 at 01:39:35AM +0530, Pirate Praveen wrote:
> Package: pristine-tar,git-buildpackage,devscripts
> Control: found -1 pristine-tar/1.49
> Control: found -1 devscripts/2.20.5
> Control: found -1 git-buildpackage/0
Your message dated Thu, 10 Dec 2020 20:36:02 +
with message-id
and subject line Bug#956767: fixed in fusion-icon 0.2.4-5
has caused the Debian Bug report #956767,
regarding fusion-icon: Depends on deprecated libappindicator
to be marked as done.
This means that you claim that the problem has
Source: proftpd-dfsg
Version: 1.3.7a-1
Severity: serious
Justification: Policy 2.2.1
As in subject, the RFCs need to be stripped before uploading a new upstream
tarball, because not compliant to DFSG. That step was missed at the time of
upload.
--
Francesco P. Lovergine
Package: pristine-tar,git-buildpackage,devscripts
Control: found -1 pristine-tar/1.49
Control: found -1 devscripts/2.20.5
Control: found -1 git-buildpackage/0.9.20
severity: serious
I'm filing against all 3 possible packages which might have a bug here.
Example package node-mermaid. It fails on
Processing control commands:
> found -1 pristine-tar/1.49
Bug #977083 [pristine-tar,git-buildpackage,devscripts] pristine-tar: fails to
checkout when there are multiple source tarballs
Marked as found in versions pristine-tar/1.49.
> found -1 devscripts/2.20.5
Bug #977083 [pristine-tar,git-buildp
Am 10.12.20 um 20:18 schrieb John Paul Adrian Glaubitz:
Hi Michael!
On 12/10/20 7:53 PM, Michael Biebl wrote:
Unfortunately, I can't reproduce the issue on a porter box (plummer).
So I'm not sure if I can do something about it.
It might be an issue with parallel jobs as Lucas built the packag
Processing commands for cont...@bugs.debian.org:
> tags 974546 + fixed-upstream
Bug #974546 [src:klatexformula] klatexformula FTBFS: error: invalid use of
incomplete type ‘class QPainterPath’
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance
Your message dated Thu, 10 Dec 2020 19:33:54 +
with message-id
and subject line Bug#976838: fixed in rocksdb 6.11.4-3
has caused the Debian Bug report #976838,
regarding librocksdb.so: missing libdl linkage
to be marked as done.
This means that you claim that the problem has been dealt with.
Hi Simon,
On Do 10 Dez 2020 16:08:00 CET, Simon McVittie wrote:
Control: severity -1 serious
On Thu, 10 Dec 2020 at 14:37:21 +, Mike Gabriel wrote:
On Do 10 Dez 2020 15:35:19 CET, Paul Gevers wrote:
> We're running into the freeze of bullseye soon. The first bug I checked
> is still onl
Processing commands for cont...@bugs.debian.org:
> forwarded 975931 https://github.com/pocl/pocl/issues/889
Bug #975931 [libllvm10,libllvm11] libgpuarray autopkgtest using pocl on armhf
triggers segfault in LLVM
Set Bug forwarded-to-address to 'https://github.com/pocl/pocl/issues/889'.
> thanks
S
Hi Michael!
On 12/10/20 7:53 PM, Michael Biebl wrote:
> Unfortunately, I can't reproduce the issue on a porter box (plummer).
> So I'm not sure if I can do something about it.
It might be an issue with parallel jobs as Lucas built the package with
make -j160 and some packages can't cope with that
Processing control commands:
> tags -1 + unreproducible
Bug #976922 [src:systemd-bootchart] systemd-bootchart: FTBFS on ppc64el:
dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Added tag(s) unreproducible.
--
976922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976922
Control: tags -1 + unreproducible
Hello Lucas
Am 09.12.20 um 09:42 schrieb Lucas Nussbaum:
Source: systemd-bootchart
Version: 233-2
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
Hi,
During a rebuild of all pack
Your message dated Thu, 10 Dec 2020 18:18:25 +
with message-id
and subject line Bug#976764: fixed in geophar 18.08.6+dfsg1-6
has caused the Debian Bug report #976764,
regarding geophar needs source upload for Python 3.9 transition
to be marked as done.
This means that you claim that the probl
Hi Andreas, Hi Paul,
Paul Gevers, on 2020-12-10 13:50:59 +0100:
> On 10-12-2020 13:10, Andreas Tille wrote:
> > My guess is that kmc was developed under and designed for amd64 and it
> > runs there. That's explicitly the case for the latest upstream version
> > which will not support any arm* out
On Thu, Dec 10, 2020 at 04:51:53PM +0100, Sven Mueller wrote:
> Hi.
>
> I just re-ran tests after adding a build dependency on libgrpc-java and
> that fixed the reported issue.
Hi Sven,
Would you mind sharing the build logs for the failed build? It's fine
if you send them to me directly.
I'm n
Your message dated Thu, 10 Dec 2020 17:34:14 +
with message-id
and subject line Bug#977034: fixed in libmaxminddb 1.4.3-2
has caused the Debian Bug report #977034,
regarding libmaxminddb-dev: File conflict libmaxminddb-dev & libmaxminddb0
to be marked as done.
This means that you claim that t
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:frr
> # 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
Setting
Processing control commands:
> severity -1 important
Bug #976995 [python3-pytest] Error importing plugin "pytest_tornasync": No
module named 'pytest_tornasync'
Severity set to 'important' from 'grave'
--
976995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976995
Debian Bug Tracking System
Control: severity -1 important
Tags: -1 unreproducible
Hi Julien,
I'm downgrading because the pytest currently does work with hundreds of
packages, implying that it cannot be (generally) unusable.
On Wed, 09 Dec 2020 21:08:39 +0100 Julien Puydt wrote:
> I was trying to update another package in
Your message dated Thu, 10 Dec 2020 17:18:21 +
with message-id
and subject line Bug#976189: fixed in catfish 1.4.13-2
has caused the Debian Bug report #976189,
regarding Catfish not starting anymore after installation of Python 3.9
to be marked as done.
This means that you claim that the prob
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:nipy
> # 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
Settin
Hi Mathieu,
On Thu, Dec 10, 2020 at 11:10:17AM +0100, Mathieu Malaterre wrote:
> "make -j160"
>
> that would be my guess :)
This sounds pretty likely, thought. Thanks for the hint.
> remove parallel from the dh option, and try again (fixes symptoms)
To cure the real issue rather than the symp
Your message dated Thu, 10 Dec 2020 17:03:44 +
with message-id
and subject line Bug#977039: fixed in pygrib 2.1.1-2
has caused the Debian Bug report #977039,
regarding pygrib: binary-any FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 10 Dec 2020 17:04:00 +
with message-id
and subject line Bug#92: fixed in xpdf 3.04-14
has caused the Debian Bug report #92,
regarding xpdf: FTBFS with poppler 0.85.0: error: 'getModRegion' was not
declared in this scope
to be marked as done.
This means that yo
Processing control commands:
> tag -1 pending
Bug #92 [src:xpdf] xpdf: FTBFS with poppler 0.85.0: error: 'getModRegion'
was not declared in this scope
Added tag(s) pending.
--
92: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92
Debian Bug Tracking System
Contact ow...@bugs.debi
Control: tag -1 pending
Hello,
Bug #92 in xpdf reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian/xpdf/-/commit/215057b1f8088fe263053f774b1013f048be50f6
Your message dated Thu, 10 Dec 2020 16:49:05 +
with message-id
and subject line Bug#976975: fixed in vtk9 9.0.1+dfsg1-3
has caused the Debian Bug report #976975,
regarding vtk9 FTBFS with freetype 2.10.4
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 10 Dec 2020 16:49:05 +
with message-id
and subject line Bug#976127: fixed in vtk9 9.0.1+dfsg1-3
has caused the Debian Bug report #976127,
regarding python3-vtk9 needs Breaks+Replaces: python3-paraview (<< 5.9.0~rc1-1~)
to be marked as done.
This means that you claim th
Le jeudi 10 décembre 2020 à 04:39 +0200, Adrian Bunk a écrit :
> Source: octave-level-set
> Version: 0.3.0-11
> Severity: serious
> Tags: ftbfs
I attach a patch that fixes the compilation of the source code (some
functions were deprecated). But then there is a failure in the tests,
which I don’t u
On 10/12/20 5:37 μ.μ., Andreas Beckmann wrote:
If it works with Linux 5.8, can you stick to an older kernel (which will
not receive security updates) until there is a newer driver release
available from Nvidia?
I just installed 5.8 from buster-backports along with tesla-440 driver
and it seems
Hi.
I just re-ran tests after adding a build dependency on libgrpc-java and
that fixed the reported issue.
Cheers,
Sven
Your message dated Thu, 10 Dec 2020 15:48:44 +
with message-id
and subject line Bug#975796: fixed in flit 3.0.0-1
has caused the Debian Bug report #975796,
regarding flit: FTBFS: ImportError: cannot import name 'build_thyself' from
'flit_core' (unknown location)
to be marked as done.
This me
On Wed, Dec 09 2020, David Bremner wrote:
> Under a sufficiently high level of parallelism [1] there seems to be a
> a race condition that allows sphinx-build to start running before the
> docstrings are extracted. This change moves the docstring stamp from
> the phony targets sphinx-html and sphi
On 12/10/20 10:37 AM, Konstantinos Margaritis wrote:
> On 10/12/20 1:19 π.μ., Andreas Beckmann wrote:
>> but I'm not sure whether it is worth backporting them,
>> since you most likely will be affected by
>> #973729 - nvidia-uvm does not work with Linux 5.9
>> which is fixed in 455.45.01
>
> Well,
Your message dated Thu, 10 Dec 2020 15:18:30 +
with message-id
and subject line Bug#976994: fixed in ccls 0.20201025-2
has caused the Debian Bug report #976994,
regarding ccls: autopkgtest regression in testing: FAIL: test_response
(__main__.TestLSP) [$ccls/info]
to be marked as done.
This m
Your message dated Thu, 10 Dec 2020 15:19:10 +
with message-id
and subject line Bug#972505: fixed in pgl-ddl-deploy 2.0.0-2
has caused the Debian Bug report #972505,
regarding pgl-ddl-deploy needs porting to PostgreSQL 13
to be marked as done.
This means that you claim that the problem has be
Processing control commands:
> severity -1 serious
Bug #956779 [src:redshift] redshift: Depends on deprecated libappindicator
Severity set to 'serious' from 'important'
--
956779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956779
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Processing control commands:
> severity -1 serious
Bug #956776 [src:osdlyrics] osdlyrics: Depends on deprecated libappindicator
Severity set to 'serious' from 'important'
--
956776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956776
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> severity -1 serious
Bug #956774 [src:kylin-burner] kylin-burner: Depends on deprecated
libappindicator
Severity set to 'serious' from 'important'
--
956774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956774
Debian Bug Tracking System
Contact ow...@bugs.debi
Processing control commands:
> severity -1 serious
Bug #956782 [src:zeal] zeal: Build-Depends (unnecessarily?) on deprecated
libappindicator
Severity set to 'serious' from 'important'
--
956782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956782
Debian Bug Tracking System
Contact ow...@bu
Processing control commands:
> severity -1 serious
Bug #956778 [src:parcellite] parcellite: Depends on deprecated libappindicator
Severity set to 'serious' from 'important'
--
956778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956778
Debian Bug Tracking System
Contact ow...@bugs.debian.or
Processing control commands:
> severity -1 serious
Bug #956772 [src:hime] hime: Depends on deprecated libappindicator
Severity set to 'serious' from 'important'
--
956772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with probl
Processing control commands:
> severity -1 serious
Bug #956769 [src:gromit-mpx] gromit-mpx: Depends on deprecated libappindicator
Severity set to 'serious' from 'important'
--
956769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956769
Debian Bug Tracking System
Contact ow...@bugs.debian.or
Processing control commands:
> severity -1 serious
Bug #956767 [src:fusion-icon] fusion-icon: Depends on deprecated libappindicator
Severity set to 'serious' from 'important'
--
956767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956767
Debian Bug Tracking System
Contact ow...@bugs.debian.
Processing control commands:
> severity -1 serious
Bug #956766 [src:gcin] gcin: Build-Depends (unnecessarily?) on deprecated
libappindicator
Severity set to 'serious' from 'important'
--
956766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956766
Debian Bug Tracking System
Contact ow...@bu
Processing control commands:
> severity -1 serious
Bug #956762 [autokey-gtk] autokey-gtk: Depends on deprecated libappindicator
Severity set to 'serious' from 'important'
--
956762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956762
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> severity -1 serious
Bug #956760 [src:cairo-dock-plug-ins] cairo-dock-plug-ins: (Build-)Depends on
deprecated libindicator
Severity set to 'serious' from 'important'
--
956760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956760
Debian Bug Tracking System
Cont
Processing control commands:
> severity -1 serious
Bug #921339 [psensor] Please switch to Ayatana AppIndicator
Severity set to 'serious' from 'important'
--
921339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 serious
Bug #895038 [src:libindicator] libindicator: deprecated in Debian, switch to
libayatana-indicator instead
Ignoring request to change severity of Bug 895038 to the same value.
--
895038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895038
D
Processing control commands:
> severity -1 serious
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Ignoring request to change severity of Bug 895037 to the same value.
--
895037: https://bugs.de
Control: severity -1 serious
On Thu, 10 Dec 2020 at 14:37:21 +, Mike Gabriel wrote:
> On Do 10 Dez 2020 15:35:19 CET, Paul Gevers wrote:
> > We're running into the freeze of bullseye soon. The first bug I checked
> > is still only severity important, so is it realistic to get this done
> > be
Your message dated Thu, 10 Dec 2020 15:05:12 +
with message-id
and subject line Bug#966839: fixed in openmm 7.5.0+dfsg-1
has caused the Debian Bug report #966839,
regarding openmm: withhold the package until a stable release
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> owner 977038 tmanc...@debian.org
Bug #977038 [google-oauth-client-java] google-oauth-client-java: FTBFS: Failed
to execute goal on project google-oauth-client: Could not resolve dependencies
for project com.google.api-client:google-api-client:ja
Control: tags -1 + pending
On Thu, Dec 10, 2020 at 4:09 AM Paul Gevers wrote:
>
> Source: ccls
> Version: 0.20201025-1
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
>
> Dear maintainer(s),
>
> With a recent change in testi
Processing control commands:
> tags -1 + pending
Bug #976994 [src:ccls] ccls: autopkgtest regression in testing: FAIL:
test_response (__main__.TestLSP) [$ccls/info]
Added tag(s) pending.
--
976994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976994
Debian Bug Tracking System
Contact ow...
Your message dated Thu, 10 Dec 2020 14:49:14 +
with message-id
and subject line Bug#977000: fixed in python-apt 2.1.7
has caused the Debian Bug report #977000,
regarding python3-apt: dak crashes after security update
to be marked as done.
This means that you claim that the problem has been de
Your message dated Thu, 10 Dec 2020 14:42:20 +
with message-id
and subject line Bug#973493: fixed in rust-log 0.4.11-2
has caused the Debian Bug report #973493,
regarding src:rust-log: fails to migrate to testing for too long: autopkgtest
regression
to be marked as done.
This means that you
Your message dated Thu, 10 Dec 2020 14:42:20 +
with message-id
and subject line Bug#970463: fixed in rust-log 0.4.11-2
has caused the Debian Bug report #970463,
regarding rust-log: autopkgtest regression can't find crate for `serde_test`
to be marked as done.
This means that you claim that th
Your message dated Thu, 10 Dec 2020 15:44:22 +0100
with message-id
and subject line Re: Bug#973200: powa-archivist: FTBFS: diff in generated
debian/control
has caused the Debian Bug report #973200,
regarding powa-archivist: FTBFS: diff in generated debian/control
to be marked as done.
This means
Hi Paul,
On Do 10 Dez 2020 15:35:19 CET, Paul Gevers wrote:
Hi Mike,
On Wed, 15 Apr 2020 19:06:59 + Mike Gabriel
wrote:
>> If you want to get this done for bullseye, please upgrade these bugs to
>> serious. Autoremovals will take care of some of the packages.
The rest will
>> need ma
Hi Mike,
On Wed, 15 Apr 2020 19:06:59 + Mike Gabriel
wrote:
> >> If you want to get this done for bullseye, please upgrade these bugs to
> >> serious. Autoremovals will take care of some of the packages. The rest will
> >> need manual fixes.
> >
> > I haven't done that. I think the severity o
Processing control commands:
> block -1 by 931197
Bug #939733 [lsb-release] lsb-release: lsb_release does not show point release
on Debian 10.1
939733 was not blocked by any bugs.
939733 was not blocking any bugs.
Added blocking bug(s) of 939733: 931197
> tags -1 bullseye-ignore
Bug #939733 [lsb-
Control: block -1 by 931197
Control: tags -1 bullseye-ignore
Hi,
The request to fix this in buster was turned down after some discussion.
As such I'm not sure that this should be RC for lsb-release. Without
changes, this needs to be fixed at the right time in base-files anyways
(there's a bug ope
Processing commands for cont...@bugs.debian.org:
> notfound 977034 1.3.2-1
Bug #977034 [libmaxminddb-dev] libmaxminddb-dev: File conflict libmaxminddb-dev
& libmaxminddb0
No longer marked as found in versions libmaxminddb/1.3.2-1.
> found 977034 1.4.3-1
Bug #977034 [libmaxminddb-dev] libmaxminddb
I have posted a merge request at
https://salsa.debian.org/python-team/packages/catfish/-/merge_requests/2
which fixes this.
Please review and merge.
/Andreas Rönnquist
gus...@debian.org
andr...@ronnquist.net
Source: pygrib
Version: 2.1.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=pygrib&suite=sid
...
debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
find debian/python3-grib -true -print0 2>/dev/null | xargs -0r chown
--no-d
Your message dated Thu, 10 Dec 2020 13:20:00 +
with message-id
and subject line Bug#976619: fixed in ts-node 9.1.1-1
has caused the Debian Bug report #976619,
regarding ts-node: required modules not declared as dependencies
to be marked as done.
This means that you claim that the problem has
Package: google-oauth-client-java
Version: 1.28.0-1
Severity: serious
This can likely be fixed with a build dependency on grpc-java
[ERROR] Failed to execute goal on project google-oauth-client: Could not
resolve dependencies for project
com.google.oauth-client:google-oauth-client:jar:1.28.0: Can
Control: tag -1 pending
Hello,
Bug #976619 in ts-node reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/js-team/ts-node/-/commit/79aeb9d5e76194d8153cc23fdc010b4c4
Processing control commands:
> tag -1 pending
Bug #976619 [ts-node] ts-node: required modules not declared as dependencies
Added tag(s) pending.
--
976619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi
On 10-12-2020 13:10, Andreas Tille wrote:
> On Thu, Dec 10, 2020 at 11:58:23AM +0100, Paul Gevers wrote:
>>> In the kmc case I'm seriously wondering whether we should restrict
>>> the architectures to those that are relevant in practice. It seems
>>> to be in line with upstream and I'm tempted
On Thu, Dec 10, 2020 at 11:58:23AM +0100, Paul Gevers wrote:
> > In the kmc case I'm seriously wondering whether we should restrict
> > the architectures to those that are relevant in practice. It seems
> > to be in line with upstream and I'm tempted to follow Étienne's
> > suggestion to upgrade t
Hi,
@Gabriel, the BTS doesn't automatically forward replies to bugs to the
submitter, if you want feedback, you need to send it manually.
@Antoine, can you please give the feedback still?
Paul
On Fri, 23 Aug 2019 00:07:29 -0400 Gabriel Filion
wrote:
> Hello,
>
> On Wed, 21 Aug 2019 10:16:26 -
1 - 100 of 139 matches
Mail list logo
