Your message dated Mon, 11 Jan 2021 11:54:39 +
with message-id
and subject line Bug#971299: fixed in onionshare 2.2-3
has caused the Debian Bug report #971299,
regarding onionshare: Switch to python3-pycryptodome
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> severity -1 serious
Bug #979156 [php-net-idna2] Useless in Debian
Severity set to 'serious' from 'important'
--
979156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 11 Jan 2021 13:13:43 +0100
with message-id
and subject line Fixed in 2.4.4-4
has caused the Debian Bug report #979338,
regarding python3-scapy: hardcodes tcpdump location to /usr/sbin/tcpdump
to be marked as done.
This means that you claim that the problem has been dealt
Package: libmeep23
Version: 1.17.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other
Your message dated Mon, 11 Jan 2021 13:49:22 +
with message-id
and subject line Bug#957601: fixed in netsniff-ng 0.6.8-1
has caused the Debian Bug report #957601,
regarding netsniff-ng: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Control: tag -1 pending
Hello,
Bug #978390 in node-rollup-plugin-typescript 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:
Processing control commands:
> tag -1 pending
Bug #978390 [src:node-rollup-plugin-typescript] node-rollup-plugin-typescript:
FTBFS: src/index.ts(69,54): error TS2345: Argument of type
'NormalizedOutputOptions' is not assignable to parameter of type
'OutputOptions'.
Added tag(s) pending.
--
Package: lld
Version: 1:11.0-51+nmu2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other
Hi Andreas,
On 1/7/21 4:51 PM, Andreas Tille wrote:
Hi Alex,
did you possibly by chance forgot to close #969597 in
your latest upload of libzstd 1.4.8+dfsg-1 ?
Kind regards
Andreas.
No, I didn't correct this specific issue. Just added the new symbols
from the new release. However
I can confirm that upgrading libx11-6 to match libx11-xcb1 fixed my
issue with chromium. Thanks!
After three full days of use, the desktop has not frozen again, and the
Xorg process has remained below 7% CPU use. Should I modify the menu to
include the alternate launch command, or is there a beta version of
chromium you would like me to try?
Steve
Steve A. wrote on 1/8/21 6:32 AM:
Control: tags 979817 + patch
Control: tags 979817 + pending
Dear maintainer,
I've prepared an NMU for llvm-defaults (versioned as 0.51+nmu3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru llvm-defaults-0.51+nmu2/debian/changelog
Processing control commands:
> tags 979817 + patch
Bug #979817 [lld] lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1)
Added tag(s) patch.
> tags 979817 + pending
Bug #979817 [lld] lld: missing Breaks+Replaces: llvm (= 1:11.0-51+nmu1)
Added tag(s) pending.
--
979817:
Your message dated Mon, 11 Jan 2021 15:48:30 +
with message-id
and subject line Bug#979734: fixed in calibre 5.9.0+dfsg-2
has caused the Debian Bug report #979734,
regarding calibre: remove python3-crypto from (Build-)Depends
to be marked as done.
This means that you claim that the problem
Hi,
On 10/01/2021 23:46, Sebastian Ramacher wrote:
> On 2020-10-05 15:18:46 +0200, Clément Hermann wrote:
>>
>> Hi,
>>
>> Control: block 971299 with 886291
>> thanks
>>
>> On 28/09/2020 23:29, Sebastian Ramacher wrote:
>>> Source: onionshare
>>> Version: 2.2-2
>>> Severity: important
>>> Tags:
Control: tags -1 fixed-upstream pending
The trigger was a change in the outside world, not Debian testing: the
tests (of HTML table parsing) were trying to access a web page that no
longer exists. Fixed in Salsa.
Your message dated Mon, 11 Jan 2021 16:03:21 +
with message-id
and subject line Bug#972306: fixed in analitza 4:20.12.0-2
has caused the Debian Bug report #972306,
regarding analitza: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
to be marked as done.
This means that you claim that
Your message dated Mon, 11 Jan 2021 11:54:20 +
with message-id
and subject line Bug#979590: fixed in libx11 2:1.7.0-2
has caused the Debian Bug report #979590,
regarding libx11 possible ABI break in libx11 breaks libx11-xcb1 and that
breaks chromium
to be marked as done.
This means that you
Your message dated Mon, 11 Jan 2021 11:54:20 +
with message-id
and subject line Bug#979590: fixed in libx11 2:1.7.0-2
has caused the Debian Bug report #979590,
regarding libx11 possible ABI break in libx11 breaks libx11-xcb1 and that
breaks chromium
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> forwarded 979727 https://github.com/lbcb-sci/racon/pull/48
Bug #979727 [src:racon] racon: FTBFS: fatal error: bioparser/bioparser.hpp: No
such file or directory
Set Bug forwarded-to-address to 'https://github.com/lbcb-sci/racon/pull/48'.
>
End
+jonas
Le 11/01/2021 à 14:52, Andreas Beckmann a écrit :
Package: lld
Version: 1:11.0-51+nmu2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the
Source: python-dlt
Version: 2.0-2
Severity: serious
Hello, looks like python-dlt is compatible only with one single dlt-daemon
release, and breaks also with minor updates, because it
relies on c structures not being stable in dlt-daemon.
I don't think this is currently suitable for stable,
On Sun, 10 Jan 2021 14:11:36 +0300 Alexander Gerasiov wrote:
> Yep, Andrey has retired from the project where he worked with the
> hardware. (So did I.) So he definitely is not interested in packaging
> this driver anymore.
>
>
> I thinks the package could be orphaned. Let's wait for Andrey's
Package: src:linux
Version: 5.10.5-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
Kernel update from buster's 4.19 to backports or using bullseye/sid 5.9 and 5.10
* What exactly did you do (or not do) that was effective (or
Processing commands for cont...@bugs.debian.org:
> fixed 979443 87.0.4280.141-0.1
Bug #979443 [chromium] chromium: desktop GUI locks up as Xorg process goes to
100%
Marked as fixed in versions chromium/87.0.4280.141-0.1.
>
End of message, stopping processing here.
Please contact me if you need
Dear Vagrant,
On Thu, 15 Oct 2020 17:10:39 -0700 Vagrant Cascadian wrote:
> Package: analitza
> Severity: normal
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: fixfilepath ftbfs
> X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
>
> When the
Processing commands for cont...@bugs.debian.org:
> severity 979744 serious
Bug #979744 [libpmix2] libpmix2: pmix_psquash_base_select failed during
pmix_init
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979744:
Your message dated Mon, 11 Jan 2021 14:36:35 +
with message-id
and subject line Bug#975789: fixed in golang-github-xenolf-lego 3.2.0-3
has caused the Debian Bug report #975789,
regarding golang-github-xenolf-lego: FTBFS:
src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment
On 2021, ജനുവരി 11 7:00:11 PM IST, Dragos Jarca
wrote:
>Package: gitlab
>Followup-For: Bug #979563
>
>Dear Maintainer,
>
>My instance work great after upgrade to 13.5.6.1!
>
>I can see the content of folder and files on UI.
>I can fetch, push, etc.
>I added versions off packages if I use,
Hi all,
Bullseye freeze is coming and we still have problems with node-request
removal. In particular, node-jsdom is not easy to patch. I tried a patch
(not approved by upstream) but it needs a lot of unavailable Node.js
modules.
Looking at the following list, it seems that only node-jsdom is
Processing commands for cont...@bugs.debian.org:
> severity 979823 serious
Bug #979823 [src:catch2] catch2: Needs source-only upload
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979823:
Control: tags 979823 + patch
Control: tags 979823 + pending
Dear maintainer,
I've prepared an NMU for catch2 (versioned as 2.13.4-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
(It is a no-change source only upload)
Regards.
diff -Nru
Processing control commands:
> tags 979823 + patch
Bug #979823 [src:catch2] catch2: Needs source-only upload
Added tag(s) patch.
> tags 979823 + pending
Bug #979823 [src:catch2] catch2: Needs source-only upload
Added tag(s) pending.
--
979823:
Processing commands for cont...@bugs.debian.org:
> reassign 979825 libx11
Bug #979825 [chromium] chromium: Chromium freezes on startup
Bug reassigned from package 'chromium' to 'libx11'.
No longer marked as found in versions chromium/87.0.4280.141-0.1.
Ignoring request to alter fixed versions of
Processing commands for cont...@bugs.debian.org:
> reassign 979694 ispell 3.4.01-1
Bug #979694 [dictionaries-common] dictionaries-common: 'espa~nol' dict contains
illegal characters
Bug reassigned from package 'dictionaries-common' to 'ispell'.
No longer marked as found in versions
Processing commands for cont...@bugs.debian.org:
> forcemerge 979590 979825
Bug #979590 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium
Bug #979618 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks
reassign 979694 ispell 3.4.01-1
reassign 979746 ispell 3.4.01-1
forcemerge 979575 979694 979746
affects 979575 ispanish
thanks
El dom, 10 ene 2021 a las 23:02, Agustin Martin
() escribió:
>
> El dom, 10 ene 2021 a las 22:39, Robert Luberda ()
> escribió:
> >
> > reassign 979549 ispell 3.4.01-1
>
On 11/01/21 4:37 am, Guilhem Moulin wrote:
> Control: severity -1 serious
>
> On Mon, 11 Jan 2021 at 00:58:01 +0100, Guilhem Moulin wrote:
>> On Sun, 03 Jan 2021 at 16:54:41 -0800, Sunil Mohan Adapa wrote:
>>> I will be filing an RM: bug on the package on Jan 10, 2021. I will
>>> wait to see if
Source: colord
Version: 1.4.4-2
Severity: serious
Control: close -1 1.4.5-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 978167
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are
Processing control commands:
> close -1 1.4.5-2
Bug #979831 [src:colord] src:colord: fails to migrate to testing for too long:
unresolved RC bug
Marked as fixed in versions colord/1.4.5-2.
Bug #979831 [src:colord] src:colord: fails to migrate to testing for too long:
unresolved RC bug
Marked
Package: chromium
Version: 87.0.4280.141-0.1
Severity: serious
Justification: unusable as shipped
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Starting today's chromium leads to
- - nothing within the window (actually an image from the previous
desktop)
- - tons of errors like
Xlib:
Your message dated Mon, 11 Jan 2021 16:33:51 +
with message-id
and subject line Bug#972302: fixed in grantlee5 5.2.0-3
has caused the Debian Bug report #972302,
regarding grantlee5: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
to be marked as done.
This means that you claim that
Your message dated Mon, 11 Jan 2021 16:34:08 +
with message-id
and subject line Bug#978390: fixed in node-rollup-plugin-typescript
6.0.0+~1.0.1-3
has caused the Debian Bug report #978390,
regarding node-rollup-plugin-typescript: FTBFS: src/index.ts(69,54): error
TS2345: Argument of type
Hi Alex,
On Mon, Jan 11, 2021 at 02:48:50PM +0100, Alex Mestiashvili wrote:
>
> No, I didn't correct this specific issue. Just added the new symbols from
> the new release. However a patch or a list of "all" symbols is very welcome.
I'd like to repeat my suggestion to move that package to a
Your message dated Mon, 11 Jan 2021 16:48:54 +
with message-id
and subject line Bug#972300: fixed in keditbookmarks 20.12.0-2
has caused the Debian Bug report #972300,
regarding keditbookmarks: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
to be marked as done.
This means that you
Hello,
I have filed an RM bug (#979832) against the package and CCed David and
all the uploaders.
Thanks,
--
Sunil
Hello,
Thank you for granting me access to the Salsa group. Can I push all my
commits to the chromium repo? Will you review my commits and check if
everything is OK and I didn't miss anything important or made any mayor
mistakes?
The window for getting in Bullseye will close soon and this issue
Michel and I just prepared an security update for unstable and
buster-security which changes the default to "desktop". This should be
soon in the archive.
Best,
Jan
Am 11.01.21 um 15:14 schrieb Steve A.:
> After three full days of use, the desktop has not frozen again, and the
> Xorg process has
Processing commands for cont...@bugs.debian.org:
> reassign 979704 src:shasta 0.6.0-5
Bug #979704 {Done: Michael R. Crusoe } [libspoa-dev]
libspoa-dev: breaks reverse-depends: shasta
Bug reassigned from package 'libspoa-dev' to 'src:shasta'.
No longer marked as found in versions spoa/4.0.6+ds-1.
Processing commands for cont...@bugs.debian.org:
> severity 972294 normal
Bug #972294 [openorienteering-mapper] openorienteering-mapper: FTBFS with
DEB_BUILD_OPTIONS=reproducible=+fixfilepath
Severity set to 'normal' from 'serious'
> tags 972294 - moreinfo
Bug #972294 [openorienteering-mapper]
Package: chromium
Version: 87.0.4280.141-0.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Chromium freezes on start up, requiring it to be killed, and making it
completely unusable.
Exactly the same with clean temporary profile.
Console output:
$ chromium
Control: tags -1 patch
There is a patch available; with it applied it builds here locally (until it
hits #975198)
https://build.opensuse.org/package/view_file/science/PrusaSlicer/PrusaSlicer-pr4340-boost-1-73.patch?expand=0
--
tobi
Package: gitlab
Followup-For: Bug #979563
Dear Maintainer,
My instance work great after upgrade to 13.5.6.1!
I can see the content of folder and files on UI.
I can fetch, push, etc.
I added versions off packages if I use, maby will help you.
If you want to give you more info, tell me.
Dragos
Processing control commands:
> tags -1 patch
Bug #975665 [slic3r-prusa] slic3r-prusa: FTBFS against boost_1.74
Added tag(s) patch.
--
975665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: rdflib
Version: 4.2.1-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You package has an autopkgtest, graet. However, it always fails on the
ci.debian.net infrastructure [1]. Can you please
Processing commands for cont...@bugs.debian.org:
> forcemerge 909651 956778
Bug #909651 {Done: Thomas Koch } [parcellite] Please enable
AppIndicator support and switch over to Ayatana AppIndicator
Unable to merge bugs because:
package of #956778 is 'src:parcellite' not 'parcellite'
Failed to
Package: fp-compiler-3.2.0
Version: 3.2.0+dfsg-9
Severity: grave
Justification: renders package unusable
Dear maintainer,
At upgrade time:
Setting up fp-compiler-5.2.0:amd64 (3.2.0+dfsg-9) ...
Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak"
Addendum:
The fix is to install nvidia-driver 460.27.04-1
No freezes happened since then:
system boot 5.10.x Fri Jan 8 15:20 still running
Cheers
Seegras
--
"Those who give up essential liberties for temporary safety deserve
neither liberty nor safety." -- Benjamin Franklin
"It's
Source: dns-root-data
Version: 2019052802
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a not so recent change (beginning 2020) somewhere outside your
package the autopkgtest of your package started to
Just to know, in previous version I have some trouble with licensee, and
I do the following to solve the problem:
gitaly(13.4.6+dfsg1-2) and gitlab(13.4.7-2) have in Gemfile:
gem 'rugged', '~> 0.28'
...
gem 'licensee', '~> 8.9'
But rugged is 1.1.0+ds-1 in testing and unstable and licensee
Source: python-django
Version: 2:2.2.17-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent in testing the autopkgtest of your package started to
fail. I copied some of the output at the bottom of
Processing commands for cont...@bugs.debian.org:
> # submitter mentions 5.9 as well
> found 979765 5.9.15-1
Bug #979765 [src:linux] linux-image-5.10.0-1-amd64: Kernel panic on boot on my
Via VX900
Marked as found in versions linux/5.9.15-1.
> thanks
Stopping processing here.
Please contact me
These packages are not installed by users, so leaving them as FTBFS is not a
big deal. If you want to clean it up, please feel free. I can certainly
understand if people (e.g. me) want to spend their time doing other things.
X
Santiago Vila:
> On Sun, 8 Sep 2019, Ximin Luo wrote:
>
>>
Control: reopen -1
Thank you for the very fast fix. python3-crypto is still listed in
Depends, though.
Cheers
On 2021-01-11 15:51:03 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:calibre package:
>
>
Processing control commands:
> reopen -1
Bug #979734 {Done: YOKOTA Hiroshi } [src:calibre]
calibre: remove python3-crypto from (Build-)Depends
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug
Source: twisted
Version: 18.9.0-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a not so recent change (March 2019) in testing the autopkgtest of
your package started to fail. I copied some of the output
> my .icewm/startup file at the moment contains:
>
> xscreensaver -nosplash -log wtf-xscreensaver.txt &
>
> When icewm starts, I see the splash screen for a brief moment (not joking,
> looks -nosplash has no effect there), but it does not happen every time.
This kinda sounds like *something
Am 11.01.21 um 22:04 schrieb Eduard Bloch:
Not sure which kind of backup you expect.
Well, you filed a serious bug report against systemd, so I expect at
least some kind of justification for that.
OpenPGP_signature
Description: OpenPGP digital signature
Source: icu
Version: 57.1-9
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Control: close -1 68.2-1
Dear maintainer(s),
You package has an autopkgtest, graet. However, it always fails on the
ci.debian.net infrastructure [1]. Can
Processing control commands:
> close -1 68.2-1
Bug #979836 [src:icu] icu: autopkgtest failure (fixed in experimental)
Marked as fixed in versions icu/68.2-1.
Bug #979836 [src:icu] icu: autopkgtest failure (fixed in experimental)
Marked Bug as done
--
979836:
Package: fp-compiler-3.2.0
Version: 3.2.0+dfsg-9
Severity: grave
Justification: renders package unusable
Hi!
During postinst the following happens:
Setting up fp-compiler-3.2.0:amd64 (3.2.0+dfsg-9) ...
Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak"
Your message dated Mon, 11 Jan 2021 22:55:57 +
with message-id
and subject line Bug#972298: fixed in okteta 5:0.26.4-2
has caused the Debian Bug report #972298,
regarding okteta: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
to be marked as done.
This means that you claim that the
On Sun, 8 Sep 2019, Ximin Luo wrote:
> Santiago Vila:
> > reopen 931003
> > found 931003 0.2.4-1
> > fixed 931003 0.2.4-1+rm
> > thanks
> >
> > Hi.
> >
> > This was automatically closed by ftpmaster because the package was
> > removed from unstable, but this still does not fix the FTBFS problem
Hallo,
* Michael Biebl [Sun, Jan 10 2021, 08:24:12PM]:
> Am 10.01.21 um 20:02 schrieb Jamie Zawinski:
> > > Why would a xscreensaver instance running for user A have any influence
> > > on a xscreensaver instance running for user B? That seems absolutely
> > > weird to me and something I don't
Processing commands for cont...@bugs.debian.org:
> reassign 956778 parcellite
Bug #956778 [src:parcellite] parcellite: Depends on deprecated libappindicator
Bug reassigned from package 'src:parcellite' to 'parcellite'.
No longer marked as found in versions parcellite/1.2.1-3.
Ignoring request to
Your message dated Mon, 11 Jan 2021 13:26:31 +
with message-id
and subject line Bug#979758: fixed in xxhash 0.8.0-2
has caused the Debian Bug report #979758,
regarding xxhash: broken pkgconfig file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> limit source llvm-defaults
Limiting to bugs with field 'source' containing at least one of 'llvm-defaults'
Limit currently set to 'source':'llvm-defaults'
> tags 979817 + pending
Bug #979817 [lld] lld: missing Breaks+Replaces: llvm (=
Processing commands for cont...@bugs.debian.org:
> severity 979856 important
Bug #979856 [src:linux] linux-image-5.10.0-1-amd64: 5.10.0-1 kernel does not
have the AMDGPU 'DCN 3.0 family' option turned on for Navi 21 support
Severity set to 'important' from 'critical'
> thanks
Stopping processing
Your message dated Tue, 12 Jan 2021 06:03:28 +
with message-id
and subject line Bug#954402: fixed in m2crypto 0.37.1-1
has caused the Debian Bug report #954402,
regarding m2crypto: FTBFS since openssl 1.1.1e
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 12 Jan 2021 06:03:28 +
with message-id
and subject line Bug#954402: fixed in m2crypto 0.37.1-1
has caused the Debian Bug report #954402,
regarding m2crypto FTBFS with pytest 6
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 12 Jan 2021 06:03:28 +
with message-id
and subject line Bug#954402: fixed in m2crypto 0.37.1-1
has caused the Debian Bug report #954402,
regarding m2crypto: FTBFS with OpenSSL 1.1.1i
to be marked as done.
This means that you claim that the problem has been dealt with.
> Can simply replacing the dependency in all of them with bbolt work?
I don't know myself, but some upstream think it's not a trivial change. For
example, see:
https://github.com/hashicorp/raft-boltdb/pull/19#issuecomment-703732437
In short: hashicorp-raft-boltdb wants to make sure there's no
Source: m2crypto
Version: 0.37.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=m2crypto=amd64=0.37.1-1=1610432018=0
...
I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_m2crypto/build;
python3.9 -m pytest tests
= test session starts
Processing commands for cont...@bugs.debian.org:
> forwarded 979865 https://gitlab.com/m2crypto/m2crypto/-/issues/292
Bug #979865 [src:m2crypto] m2crypto FTBFS on IPV6-only buildds
Set Bug forwarded-to-address to
'https://gitlab.com/m2crypto/m2crypto/-/issues/292'.
> thanks
Stopping processing
Source: knxd
Version: 0.14.41-1
Severity: serious
Tags: ftbfs
knxd fails to build from source for all attempted architectures on the
buildds. A build log usually ends with:
|dh_autoreconf -a
| find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' -o
-path '*/.bzr/*' -o
Processing commands for cont...@bugs.debian.org:
> found 979719 2.0.0~beta9-1
Bug #979719 [socat] socat in experimental is obsolete and no installable
Marked as found in versions socat/2.0.0~beta9-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979719:
Control: tag -1 pending
Hello,
Bug #954402 in m2crypto 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:
Processing control commands:
> tag -1 pending
Bug #954402 [src:m2crypto] m2crypto: FTBFS since openssl 1.1.1e
Bug #977070 [src:m2crypto] m2crypto FTBFS with pytest 6
Bug #977655 [src:m2crypto] m2crypto: FTBFS with OpenSSL 1.1.1i
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Processing control commands:
> reopen -1
Bug #978066 {Done: Alastair McKinstry } [src:pmix] pmix:
breaks openmpi autopkgtest
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked
Control: reopen -1
pmix/4.0.0-2 from unstable still causes the autopkgtests of openmpi
4.0.5-7 in testing to fail
If it is not intended that this combination should work together,
please add Breaks: libopenmpi3 (<< 4.1.0-3) or similar to libpmix2.
Your message dated Tue, 12 Jan 2021 07:33:16 +0100
with message-id <27ecbd49-0cd1-4a13-83b3-d92d8b155...@frost.de>
and subject line Re: Bug#979823: catch2: diff for NMU version 2.13.4-1.1
has caused the Debian Bug report #979823,
regarding catch2: Needs source-only upload
to be marked as done.
Your message dated Tue, 12 Jan 2021 01:33:29 +
with message-id
and subject line Bug#979734: fixed in calibre 5.9.0+dfsg-3
has caused the Debian Bug report #979734,
regarding calibre: remove python3-crypto from (Build-)Depends
to be marked as done.
This means that you claim that the problem
severity 942078 normal
tags 942078 + moreinfo unreproducible
thanks
Hi Nicholas,
I cannot reproduce this, nor anyone else in the team, and you haven't
given an update to whether this is reproducible or not on your side.
I thus downgrade this bug and tag it appropriately.
Thanks for your
Processing commands for cont...@bugs.debian.org:
> severity 942078 normal
Bug #942078 [baloo-kf5] [high quality bug] baloo crash, can't recover; forced
reindex does not fix; unusable via dolphin C-f
Severity set to 'normal' from 'serious'
> tags 942078 + moreinfo unreproducible
Bug #942078
severity 943462 normal
tags 943462 + moreinfo unreproducible
thanks
Hi Alex,
On Wed, 23 Dec 2020, Norbert Preining wrote:
> This is for a very old version of Plasma. Could you please try the
> current 5.20.4 from unstable.
Since we didn't get any feedback from your side about whether this is
Processing commands for cont...@bugs.debian.org:
> severity 943462 normal
Bug #943462 [polkit-kde-agent-1] [polkit-kde-agent-1] Fails to start with
elogind
Severity set to 'normal' from 'serious'
> tags 943462 + moreinfo unreproducible
Bug #943462 [polkit-kde-agent-1] [polkit-kde-agent-1] Fails
Your message dated Tue, 12 Jan 2021 10:58:09 +0900
with message-id
and subject line Re: Bug#955567: kalgebra: Output is always blank
has caused the Debian Bug report #955567,
regarding kalgebra: Output is always blank
to be marked as done.
This means that you claim that the problem has been
Thanks. Sure, let me look it and get back.
Thanks
Rajasekhar
On 11/01/21 6:54 am, Sunil Mohan Adapa wrote:
> Added CC: Rajasekhar Ponakala
>
> On 10/01/21 3:58 pm, Guilhem Moulin wrote:
>> Hi all,
>>
>> On Sun, 03 Jan 2021 at 16:54:41 -0800, Sunil Mohan Adapa wrote:
>>> I will be filing an RM:
Control: tag -1 pending
Hello,
Bug #975817 in mom 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/mom/-/commit/acf3d8596c145a3d3c9fc554df49fe27f82253b7
Processing control commands:
> tag -1 pending
Bug #975817 [src:mom] mom: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1
returned exit code 2
Added tag(s) pending.
--
975817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975817
Debian Bug Tracking System
Contact ow...@bugs.debian.org
1 - 100 of 130 matches
Mail list logo
