On Wed, 7 Oct 2020 at 02:09, Shengjing Zhu wrote:
> Maybe due to the go-md2man v2 transition, docker.io is now FTBFS.
>
> dh_installman: warning: Section for
> ./.gopath/src/github.com/docker/cli/man/man1/docker-attach.1 is computed as
> "2020", which is not a valid section
> dh_installman:
Processing commands for cont...@bugs.debian.org:
> reopen 971672
Bug #971672 {Done: Sven Joachim } [libncurses6] rm:
/lib/i386-linux-gnu/libtinfo.so.6: version `NCURSES6_TINFO_6.2.current' not
found (required by /lib/i386-linux-gnu/libncurses.so.6)
Bug reopened
Ignoring request to alter fixed
reopen 971672
retitle 971672 ncurses: please add suitable Breaks for cowdancer (<< 0.89~)
severity 971672 normal
thanks
On Thu, 8 Oct 2020, Debian FTP Masters wrote:
> cowdancer (0.89) unstable; urgency=medium
>* Check isatty(3) rather than rely on ncurses/tinfo (Closes: #970555)
Would
Gostei
Control: tags -1 + patch
Control: fixed -1 0.14.0-1.3+deb10u1
Hi
In https://salsa.debian.org/qemu-team/spice/-/merge_requests/2 created
a respective merge request.
I repared as well an update for buster-security but it would be ideal
to expose first the fixes in unstable.
Regards,
Salvatore
Processing control commands:
> tags -1 + patch
Bug #971750 [src:spice] spice: CVE-2020-14355
Added tag(s) patch.
> fixed -1 0.14.0-1.3+deb10u1
Bug #971750 [src:spice] spice: CVE-2020-14355
The source 'spice' and version '0.14.0-1.3+deb10u1' do not appear to match any
binary packages
Marked as
Processing commands for cont...@bugs.debian.org:
> close 833170
Bug #833170 [src:linux] linux-image-3.16.0-4-amd64: Reproducable XFS filesystem
corruption, possibly connected with ACLs
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
833170:
Package: installation-reports
Severity: grave
Tags: d-i
Justification: renders package unusable
X-Debbugs-Cc: smckenna_deb...@clanlineage.com
Dear Maintainer,
First bug report, my appologies if I miss something. This is mostly to provide
info for improvement.
* What led up to the
Your message dated Thu, 08 Oct 2020 19:33:58 +
with message-id
and subject line Bug#970820: fixed in intelrdfpmath 2.0u2-3
has caused the Debian Bug report #970820,
regarding missing bid_functions.h header
to be marked as done.
This means that you claim that the problem has been dealt with.
Package: golang-1.14
Severity: serious
X-Debbugs-Cc: z...@debian.org
So, we have updated golang-defaults to 1.15.
Like buster, bullseye seems to be having only one version of Go compiler.
Let's see if anyone wants 1.14 for bullseye.
Or later we can convert this to RM bug for ftp.d.o.
Control: tag -1 pending
Hello,
Bug #970820 in intelrdfpmath 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 #970820 [libintelrdfpmath-dev] missing bid_functions.h header
Added tag(s) pending.
--
970820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #959904 [src:android-platform-system-tools-hidl]
android-platform-system-tools-hidl: FTBFS no matching function for call to
‘find(std::vector >::const_iterator,
std::vector >::const_iterator, const string&)’
Added tag(s) pending.
--
959904:
Control: tag -1 pending
Hello,
Bug #959904 in android-platform-system-tools-hidl 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:
Hi,
On 25-09-2020 20:44, Paul Gevers wrote:
>>> Both packages are key packages [1], so will not be removed
>>> automatically. Please align how to fix the situation.
>>
>> bleach needs to be upgraded to 3.2.1
>
> But is it possible that this new version of bleach must have a versioned
>
Hi Michael,
On 08-10-2020 16:21, Michael R. Crusoe wrote:
> As the picard-tools package does not list arm64 in its Architectures
> line for the binary packages, I'm surprised it is being expected to pass
> the autopkgtests for arm64, let alone armhf and i386 as well[0]
src:picard-tools builds
Your message dated Thu, 08 Oct 2020 17:49:27 +
with message-id
and subject line Bug#971794: fixed in fakeroot 1.25.3-1
has caused the Debian Bug report #971794,
regarding fakeroot: testsuite fails on mipsel
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 8 Oct 2020 19:49:46 +0200
with message-id <9e762b3e-6315-f62b-7dc4-d8d27e871...@eds.org>
and subject line no python depends nor used
has caused the Debian Bug report #967119,
regarding android-framework-23: Unversioned Python removal in sid/bullseye
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> severity 971644 important
Bug #971644 [elogind] elogind: accidentally hitting Fn-F12 crashes the system
(dirty filesystem)
Severity set to 'important' from 'critical'
> outlook 971644 workaround via /etc/elogind/logind.conf exists; upstream is
Your message dated Thu, 08 Oct 2020 17:33:29 +
with message-id
and subject line Bug#956996: fixed in android-platform-system-core 1:8.1.0+r23-8
has caused the Debian Bug report #956996,
regarding android-platform-system-core: ftbfs with GCC-10
to be marked as done.
This means that you claim
Your message dated Thu, 08 Oct 2020 17:18:32 +
with message-id
and subject line Bug#956999: fixed in android-platform-system-extras 8.1.0+r23-3
has caused the Debian Bug report #956999,
regarding android-platform-system-extras: ftbfs with GCC-10
to be marked as done.
This means that you
Your message dated Thu, 08 Oct 2020 17:05:15 +
with message-id
and subject line Bug#970502: fixed in picard-tools 2.23.4+dfsg-3
has caused the Debian Bug report #970502,
regarding picard-tools: autopkgtest arm64 failure
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 08 Oct 2020 16:19:00 +
with message-id
and subject line Bug#956994: fixed in android-platform-external-libunwind
10.0.0+r36-3
has caused the Debian Bug report #956994,
regarding android-platform-external-libunwind: ftbfs with GCC-10
to be marked as done.
This means
Your message dated Thu, 08 Oct 2020 15:33:40 +
with message-id
and subject line Bug#970589: fixed in tracker-miners 2.3.5-1
has caused the Debian Bug report #970589,
regarding tracker-extract: Crashes due to statx SIGABRT causes disk full ( need
update to 2.3.5 )
to be marked as done.
This
Control: tag -1 pending
Hello,
Bug #970589 in tracker-miners 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 #970589 [tracker-extract] tracker-extract: Crashes due to statx SIGABRT
causes disk full ( need update to 2.3.5 )
Added tag(s) pending.
--
970589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970589
Debian Bug Tracking System
Contact
Your message dated Thu, 08 Oct 2020 15:18:47 +
with message-id
and subject line Bug#964695: fixed in ktexteditor 5.74.0-2
has caused the Debian Bug report #964695,
regarding ktexteditor: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu &&
make -j1 test ARGS\+=-j1 returned exit code 2
to
Processing commands for cont...@bugs.debian.org:
> forwarded 946650 https://bugs.kde.org/427451
Bug #946650 [src:ktexteditor] ktexteditor: FTBFS on hurd-i386:
KateDocumentTest::testAutoReload fails
Set Bug forwarded-to-address to 'https://bugs.kde.org/427451'.
> forwarded 964695
Control: tag -1 pending
Hello,
Bug #964695 in ktexteditor 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 #964695 [src:ktexteditor] ktexteditor: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1 returned exit code 2
Added tag(s) pending.
--
964695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964695
Debian Bug
Processing commands for cont...@bugs.debian.org:
> fixed 971110 ruby-dalli/2.7.11-1
Bug #971110 {Done: Cédric Boutillier } [src:ruby-dalli]
ruby-dalli: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: wrong number of
arguments (given 3, expected 1..2)
Marked as fixed in versions
Processing commands for cont...@bugs.debian.org:
> fixed 971110 -i
Bug #971110 {Done: Cédric Boutillier } [src:ruby-dalli]
ruby-dalli: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: wrong number of
arguments (given 3, expected 1..2)
The source 'ruby-dalli' and version '-i' do not appear to
Processing commands for cont...@bugs.debian.org:
> fixed 971110 ruby-dalli/2.7.11-1
Bug #971110 {Done: Cédric Boutillier } [src:ruby-dalli]
ruby-dalli: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: wrong number of
arguments (given 3, expected 1..2)
Marked as fixed in versions
Processing commands for cont...@bugs.debian.org:
> close 971110
Bug #971110 [src:ruby-dalli] ruby-dalli: FTBFS: ERROR: Test "ruby2.7" failed:
ArgumentError: wrong number of arguments (given 3, expected 1..2)
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need
On Thu, 17 Sep 2020 13:50:45 +0200 Paul Gevers wrote:
> Source: picard-tools
> Version: 2.23.4+dfsg-2
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always
>
> Dear maintainer(s),
>
> Your package was recently removed from
Your message dated Thu, 08 Oct 2020 13:19:00 +
with message-id
and subject line Bug#970852: fixed in ruby-qr4r 0.4.1-2
has caused the Debian Bug report #970852,
regarding ruby-qr4r: ftbfs with ruby-rqrcode 1.0
to be marked as done.
This means that you claim that the problem has been dealt
Source: haskell-hoogle
Version: 5.0.18+dfsg1-1
Severity: serious
haskell-hoogle's autopkgtest currently fails on armhf:
| Processing triggers for hoogle (5.0.18+dfsg1-1+b2) ...
| Converting databases... done
| Processing triggers for ghc-doc (8.8.4-1) ...
| hoogle: The Hoogle file
Package: src:task
Version: 2.5.1+dfsg-10
Severity: serious
Tags: sid bullseye
autopkg test depends on unavailable package adequate, which was removed from
testing.
[...]
Package adequate is not available, but is referred to by another package.
This may mean that the package is missing, has been
Your message dated Thu, 08 Oct 2020 09:03:41 +
with message-id
and subject line Bug#965219: fixed in dbconfig-common 2.0.14
has caused the Debian Bug report #965219,
regarding dbconfig-common: Write file error (wrong owner)
to be marked as done.
This means that you claim that the problem has
Package: python3-pyopencl
Version: 2019.1.1-1
Severity: critical
Tags: upstream
Justification: causes serious data loss
Dear Maintainer,
We are using pyopencl to perform GPU computing in Python workflows.
Since we deployed Ubuntu 20.04 (which is using the same version as
Debian 10 (and newer),
Processing control commands:
> severity -1 serious
Bug #970852 [ruby-qr4r] ruby-qr4r: ftbfs with ruby-rqrcode 1.0 in experimental
Severity set to 'serious' from 'important'
> retitle -1 ruby-qr4r: ftbfs with ruby-rqrcode 1.0
Bug #970852 [ruby-qr4r] ruby-qr4r: ftbfs with ruby-rqrcode 1.0 in
Source: php-amqplib
Version: 2.12.1-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 php-amqplib the autopkgtest of php-amqplib fails
in testing when that autopkgtest is run with the
42 matches
Mail list logo
