Your message dated Sun, 3 Jan 2021 17:45:49 +0100
with message-id <20210103164549.GV7178@Kraftkrust>
and subject line Dependency added
has caused the Debian Bug report #978974,
regarding freedict-tools FTBFS: No Python executable found, please make sure
that a recent Python is in the search path.
Your message dated Sun, 03 Jan 2021 19:19:04 +
with message-id
and subject line Bug#976556: fixed in latex-make 2.4.2-1
has caused the Debian Bug report #976556,
regarding latex-make: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1
returned exit code 2
to be marked as done.
This means
Your message dated Sun, 03 Jan 2021 17:35:58 +
with message-id
and subject line Bug#978341: fixed in node-babel7 7.12.11+~cs150.141.84-3
has caused the Debian Bug report #978341,
regarding node-ast-types: FTBFS:
node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016:
Your message dated Sun, 03 Jan 2021 17:35:58 +
with message-id
and subject line Bug#978341: fixed in node-babel7 7.12.11+~cs150.141.84-3
has caused the Debian Bug report #978341,
regarding node-recast: FTBFS:
node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016:
Could
Package: node-express-generator
Version: 4.0.0-2
Severity: grave
Tags: sid, ftbfs
Justification: renders package unusable
node-express-generator isn't compatible with current node-commander,
neither node-mkdirp. As it has no reverse dependency, I suggest to
remove it from Debian
Control: severity -1 important
Hi,
On Sat, 5 Dec 2020 21:45:34 +0100 Lucas Nussbaum wrote:
> This package only builds Arch:all binary packages. Unfortunately, I
> don't think that we have a way to indicate that such binary packages
> must be built on a specific architecture, and thus avoid a
Processing control commands:
> severity -1 important
Bug #976468 [src:python-ptrace] python-ptrace: FTBFS on arm64,ppc64el
(arch:all-only src pkg): dh_auto_test: error: pybuild --test -i python{version}
-p 3.9 returned exit code 13
Severity set to 'important' from 'serious'
--
976468:
Am 27.12.2020 um 12:42 teilte Rene Engelhard mit:
Hi,
dist-upgrade buster->bullseye which just caused my system to not get out of apt
-f install anymore:
Entpacken von texlive-base (2020.20201203-2) über (2018.20190227-2) ...
dpkg: Fehler beim Bearbeiten des Archivs
Your message dated Sun, 03 Jan 2021 22:48:32 +
with message-id
and subject line Bug#959904: fixed in android-platform-system-tools-hidl
10.0.0+r36-1
has caused the Debian Bug report #959904,
regarding android-platform-system-tools-hidl: FTBFS no matching function for
call to
Processing control commands:
> fixed -1 1.6.1-2
Bug #972377 [src:pyasn] pyasn FTBFS: FileNotFoundError in tests
The source 'pyasn' and version '1.6.1-2' do not appear to match any binary
packages
Marked as fixed in versions pyasn/1.6.1-2.
--
972377:
Control: fixed -1 1.6.1-2
I can't reproduce this, perhaps it was fixed by the upgrade to Python
3.9. For example:
https://salsa.debian.org/python-team/packages/pyasn/-/pipelines/214872
Source: libtool
Version: 2.4.6-14
Severity: serious
Tags: ftbfs patch
User: helm...@debian.org
Usertags: rebootstrap
libtool started to ftbfs with the recent gnulib upload. It needs to bump
the autoconf version to build again. The attached patch makes it work
again.
Helmut
---
On 03/01/21 4:48 pm, David Prévot wrote:
> Hi Sunil,
>
> Le 03/01/2021 à 20:06, Sunil Mohan Adapa a écrit :
>> On 03/01/21 8:24 am, David Prévot wrote:
> […]
>>> php-net-idna2 was introduced in Debian as part of the gnusocial
>>> packaging effort […]
>
>>> Unless someone disagree with the above,
tags 950761 - pending
thanks
Hello Salvatore,
hello @All,
following a tip from Salvatore, I have added the missing commits.
Although these can be incorporated manually, they are not reliably
functional in at least two places due to the different code base.
I think the best thing will be to
Processing commands for cont...@bugs.debian.org:
> tags 950761 - pending
Bug #950761 [src:ipmitool] ipmitool: CVE-2020-5208
Removed tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950761
Your message dated Sun, 03 Jan 2021 17:23:12 +
with message-id
and subject line Bug#978209: fixed in mrpt 1:2.1.7-1
has caused the Debian Bug report #978209,
regarding mrpt: FTBFS: mainwindow.h:218:2: error: reference to ‘Tracker’ is
ambiguous
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> close 978324
Bug #978324 [src:gdb-mingw-w64] gdb-mingw-w64: FTBFS: tar: /usr/src/gdb.tar.*:
Cannot open: No such file or directory
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
978324:
Just FYI, I'm running stock 5.10.0-rc7 with two patches for the new Intel
Wireless 6E card compiled using the Debian Docs to create the kernel package.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977299
and Official OpenZFS 2.0.0 source that I compiled against 5.10.0-rc7 source
and created
Processing commands for cont...@bugs.debian.org:
> forcemerge 977656 979158
Bug #977656 [zfs-dkms] zfs-dkms: Fail to build with 5.10 kernel with "error:
‘struct percpu_ref’ has no member named ‘count’"
Bug #979158 [zfs-dkms] fails to install under kernel version 5.10.0
Severity set to 'normal'
Processing commands for cont...@bugs.debian.org:
> severity 977656 grave
Bug #977656 [zfs-dkms] zfs-dkms: Fail to build with 5.10 kernel with "error:
‘struct percpu_ref’ has no member named ‘count’"
Bug #979158 [zfs-dkms] fails to install under kernel version 5.10.0
Severity set to 'grave' from
Processing control commands:
> tags 977683 + patch
Bug #977683 [src:bouncycastle] bouncycastle: CVE-2020-28052
Added tag(s) patch.
> tags 977683 + pending
Bug #977683 [src:bouncycastle] bouncycastle: CVE-2020-28052
Added tag(s) pending.
--
977683:
Control: tags 977683 + patch
Control: tags 977683 + pending
Dear maintainer,
X-Debbugs-CC'ing as well Markus Koschany.
I've prepared an NMU for bouncycastle (versioned as 1.65-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer. Alternatively feel free to
On 03/01/21 8:24 am, David Prévot wrote:
> Package: php-net-idna2
> Severity: serious
>
> [ Reported by a team member to see the package removed from testing ]
>
> php-net-idna2 was introduced in Debian as part of the gnusocial
> packaging effort, but its ITP (#782812) has no activity for more
Package: rust-lazycell
Version: 1.3.0-1
Severity: serious
The upload of rust-lazycell 1.3.0-1 introduced three new binary
packages, two of which are currently
uninstallable. This is preventing the package from migrating to testing
which is annoying the release
team (see:
Your message dated Sun, 03 Jan 2021 16:33:45 +
with message-id
and subject line Bug#952318: fixed in f2fs-tools 1.14.0-1
has caused the Debian Bug report #952318,
regarding f2fs-tools: FTBFS: dh_makeshlibs errors
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 03 Jan 2021 16:33:45 +
with message-id
and subject line Bug#970941: fixed in f2fs-tools 1.14.0-1
has caused the Debian Bug report #970941,
regarding f2fs-tools: CVE-2020-6070
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sun, 03 Jan 2021 19:03:34 +
with message-id
and subject line Bug#956878: fixed in groestlcoin 2.20.1~dfsg-1
has caused the Debian Bug report #956878,
regarding groestlcoin: FTBFS: error: cannot convert 'std::atomic' to
'const UniValue&'
to be marked as done.
This means
Your message dated Sun, 03 Jan 2021 19:35:44 +
with message-id
and subject line Bug#978216: fixed in liborigin2 2:20110117-4
has caused the Debian Bug report #978216,
regarding liborigin2: FTBFS: OriginObj.h:702:27: error: ‘find_if’ was not
declared in this scope; did you mean
Your message dated Sun, 03 Jan 2021 20:17:05 +
with message-id
and subject line Bug#978662: fixed in apertium-cy-en 0.1.1~r57554-7
has caused the Debian Bug report #978662,
regarding apertium-cy-en: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been
tag -1 upstream
thanks
Giving an update here, since many people may be interested in a status
report on this:
- There is *no released version* of ZoL/OpenZFS that supports 5.10.
- 5.10 appears to have been slightly more work for OpenZFS to adjust to.
- As of e1d9228b0 (on their 2.0.1-staging
Package: php-net-idna2
Severity: serious
[ Reported by a team member to see the package removed from testing ]
php-net-idna2 was introduced in Debian as part of the gnusocial
packaging effort, but its ITP (#782812) has no activity for more than
three years. Furthermore, php-net-idna2 in Debian
Your message dated Sun, 03 Jan 2021 16:33:45 +
with message-id
and subject line Bug#973380: fixed in f2fs-tools 1.14.0-1
has caused the Debian Bug report #973380,
regarding CVE-2020-6104 CVE-2020-6105 CVE-2020-6106 CVE-2020-6107 CVE-2020-6108
to be marked as done.
This means that you claim
Hi Tino,
On Tue, 29 Dec 2020 23:21:15 +0100 Tino Didriksen wrote:
> This is a chicken-and-egg problem that should solve itself. New apertium
> 3.7.1 can't migrate until apertium-cy-en is fixed, but fixed apertium-cy-en
> won't build correctly with existing apertium 3.6.1.
On declaring hard
Hi Sunil,
Le 03/01/2021 à 20:06, Sunil Mohan Adapa a écrit :
On 03/01/21 8:24 am, David Prévot wrote:
[…]
php-net-idna2 was introduced in Debian as part of the gnusocial
packaging effort […]
Unless someone disagree with the above, I intend to ask for removal of
this package soon (so if you
Your message dated Mon, 04 Jan 2021 00:48:29 +
with message-id
and subject line Bug#977489: fixed in rust-rand 0.7.3-3
has caused the Debian Bug report #977489,
regarding rust-rand: autopkgtest regression in testing: error: could not
compile `packed_simd`.
to be marked as done.
This means
Processing control commands:
> severity -1 grave
Bug #969885 [megadown] megadown: [python] is required and it's not installed
Severity set to 'grave' from 'important'
--
969885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969885
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> tag -1 pending
Bug #978341 [node-babel7] node-recast: FTBFS:
node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016:
Could not find a declaration file for module '@babel/types'.
'/<>/node_modules/@babel/types/lib/index.js' implicitly has an
Control: tag -1 pending
Hello,
Bug #978341 in node-babel 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:
Control: tags -1 help confirmed
In Python 3.9, the plistlib was changed to no longer have the internal
data structure plistlib.Data, which biplist relied on. Here's a
potential fix:
https://github.com/unified-font-object/ufoNormalizer/pull/74/files
Processing control commands:
> tags -1 help confirmed
Bug #973082 [src:python-biplist] python-biplist: FTBFS: dh_auto_test: error:
pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) confirmed and help.
--
973082:
Looking at
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rand/9312542/log.gz
It looks like the packed_simd feature test passes with unstable's
version of rust-packed-simd
but the all features test is still failing with
error[E0433]: failed to resolve: use of undeclared crate
Package: zfs-dkms
Version: 0.8.6-1
Severity: grave
Justification: Renders package unusable
Installing zfs-dkms fails with the following error message in
/var/lib/dkms/zfs/0.8.6/build/make.log:
CC [M] /var/lib/dkms/zfs/0.8.6/build/module/zfs/vdev_file.o
Your message dated Mon, 04 Jan 2021 05:18:24 +
with message-id
and subject line Bug#977683: fixed in bouncycastle 1.65-2
has caused the Debian Bug report #977683,
regarding bouncycastle: CVE-2020-28052
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> tag -1 pending
Bug #978293 [src:python-django-babel] python-django-babel: FTBFS:
'django.core.exceptions.ImproperlyConfigured: Requested settings, but settings
are not configured.' raised when building doumentation
Added tag(s) pending.
--
978293:
Control: tag -1 pending
Hello,
Bug #978293 in python-django-babel 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:
Thank you, with 5.20.4 the issue seems to be gone.
Best,
Mikko
ke 23. jouluk. 2020 klo 3.32 Norbert Preining (prein...@logic.at) kirjoitti:
> tags 973677 + unreproducible moreinfo
> severity 973677 normal
> thanks
>
> On Tue, 03 Nov 2020, Mikko Korhonen wrote:
> > but happens every time and at
Your message dated Mon, 04 Jan 2021 04:49:07 +
with message-id
and subject line Bug#977081: fixed in pytest-rerunfailures 9.1.1-1
has caused the Debian Bug report #977081,
regarding pytest-rerunfailures FTBFS with pytest 6
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 04 Jan 2021 07:18:29 +
with message-id
and subject line Bug#978291: fixed in python-enmerkar 0.7.1-3
has caused the Debian Bug report #978291,
regarding python-enmerkar: FTBFS: 'django.core.exceptions.ImproperlyConfigured:
Requested settings, but settings are not
Hi,
> Date: Mon, 04 Jan 2021 03:08:34 +0100
> Source: alure
> Architecture: source
> Version: 1.2-7
> Distribution: unstable
> Urgency: low
> Maintainer: Debian Games Team
> Changed-By: Bastian Germann
> Closes: 960707
> Changes:
> alure (1.2-7) unstable; urgency=low
> .
>* Team upload
>
Your message dated Mon, 04 Jan 2021 07:18:23 +
with message-id
and subject line Bug#978293: fixed in python-django-babel 0.6.2-5
has caused the Debian Bug report #978293,
regarding python-django-babel: FTBFS:
'django.core.exceptions.ImproperlyConfigured: Requested settings, but settings
are
Processing control commands:
> tags -1 patch
Bug #979026 [src:r-cran-rgdal] r-cran-rgdal: autopkgtest failure with PROJ 7.2.1
Added tag(s) patch.
--
979026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
On 1/2/21 9:42 AM, Sebastiaan Couwenberg wrote:
> On 1/2/21 6:54 AM, Bas Couwenberg wrote:
>> The autopkgtest of your package fail with PROJ 7.2.1:
>>
>> Error: isTRUE(all.equal(a, matrix(c(-5.917698, -1.87195), ncol = 2),
>> is not TRUE
>> Execution halted
>>
Your message dated Mon, 4 Jan 2021 00:37:38 -0500
with message-id
and subject line No longer failing
has caused the Debian Bug report #966435,
regarding autopkg test fails on arm64, triggered by gcc-defaults
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Hi Salvatore,
On Sun, Jan 03, 2021 at 09:27:41PM +0100, Salvatore Bonaccorso wrote:
> Control: tags 977683 + patch
> Control: tags 977683 + pending
>
>
> Dear maintainer,
> X-Debbugs-CC'ing as well Markus Koschany.
>
> I've prepared an NMU for bouncycastle (versioned as 1.65-1.1) and
>
Processing control commands:
> reopen -1
Bug #974608 {Done: Boyuan Yang } [gthumb] gthumb uses
internal libexiv2 functions to get the user comment
'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
Control: reopen -1
Control: severity -1 important
On Mon, 14 Dec 2020 23:32:16 +0100 Vincent Lefevre wrote:
> Control: severity -1 serious
>
> According to the upstream libexiv2 maintainer, gthumb uses some
> internal libexiv2 function, which means that an update of libexiv2
> can break it at
Your message dated Mon, 04 Jan 2021 04:33:25 +
with message-id
and subject line Bug#960707: fixed in alure 1.2-7
has caused the Debian Bug report #960707,
regarding bucklespring: error loading shared objectfile
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 04 Jan 2021 04:33:25 +
with message-id
and subject line Bug#960707: fixed in alure 1.2-7
has caused the Debian Bug report #960707,
regarding libalure1: Binary rebuild with current libfluidsynth2
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 04 Jan 2021 02:49:33 +
with message-id
and subject line Bug#974608: fixed in gthumb 3:3.11.1-0.1
has caused the Debian Bug report #974608,
regarding gthumb uses internal libexiv2 functions to get the user comment
to be marked as done.
This means that you claim that
Hi Norbert,
On Sat, Jan 02, 2021 at 07:49:37AM +0900, Norbert Preining wrote :
> I see you haven't done any further packaging of libqalculate since June
> 2019, and the qalculate v3 is stuck in experimental.
>
> Could you please let us know what are your plans with qalculate?
>
> I have raised
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for the package "alure".
The changes are also available at
https://salsa.debian.org/games-team/alure/-/merge_requests/3
* Package name: alure
Version : 1.2-7
Upstream Author : Chris
Processing control commands:
> tag -1 pending
Bug #977683 [src:bouncycastle] bouncycastle: CVE-2020-28052
Ignoring request to alter tags of bug #977683 to the same tags previously set
--
977683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977683
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #977683 in bouncycastle 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:
Michel Le Bihan writes:
> Hello,
>
> I opened a merge request, but merging all branches into your repo
> might cause issues in the upstream branch in the future due to the
> merge commits. Instead, it will be best to pull all branches from my
> repo into branches of your repo, but without adding
Processing commands for cont...@bugs.debian.org:
> # Binary package libnifti2 is not built anymore in the fixed version.
> # Assign to source package instead.
> reassign 968730 src:nifticlib nifticlib/2.0.0+git186-g84740c2-1
Bug #968730 {Done: Gianfranco Costamagna }
[libnifti2] libnifti2:
Processing commands for cont...@bugs.debian.org:
> severity 975963 serious
Bug #975963 [bmake] bmake: /usr/share/mk is now a symlink, upgrades from
non-symlinks are broken
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Control: reassign -1 node-postcss-minify-font-values
On Sat, 02 Jan 2021 21:48:11 +0530 Pirate Praveen
wrote:
> Package: node-postcss-filter-plugins,node-postcss-minify-font-values
> Severity: serious
>
> Already filed request for removal. Filing rc bug in case the removal
> takes longer than
Processing control commands:
> reassign -1 node-postcss-minify-font-values
Bug #979087 [node-postcss-filter-plugins,node-postcss-minify-font-values]
incompatible with node-postcss 8 and unmaintained
Bug reassigned from package
'node-postcss-filter-plugins,node-postcss-minify-font-values' to
Your message dated Sun, 03 Jan 2021 09:21:03 +
with message-id
and subject line Bug#947569: fixed in mongo-cxx-driver-legacy 1.1.3-3.1
has caused the Debian Bug report #947569,
regarding FTBFS with scons 3.1.2-1
to be marked as done.
This means that you claim that the problem has been dealt
Hi!
Gianfranco, thanks for your valuable input.
On Mon, 7 Dec 2020 01:15:35 +0100 Gianfranco Costamagna
wrote:
> Hello, how can three different binaries provide the very same old -dev
> library?
>
> what happens now is that apt gets the old real cruft binary -dev package, and
> not the
Your message dated Sun, 03 Jan 2021 09:48:19 +
with message-id
and subject line Bug#957434: fixed in libept 1.2.1
has caused the Debian Bug report #957434,
regarding libept: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
; urgency=high
.
* Non-maintainer upload.
* Update to the gdb-10-branch 20210103 (copyright updates).
* Fix building the gdb-source package. Closes: #978391.
* Call dh_dwz before dh_strip.
* Add x86_64-linux-gnux32 as a target for gdb-multiarch.
Checksums-Sha1
Package: elpa-racket-mode
Version: 20201227git0-2
Severity: serious
While trying to upgrade (no more sure from which version),
elpa-racket-mode fails to configure on a Raspberry Pi (armhf) for me as
follows:
Setting up elpa-racket-mode (20201227git0-2) ...
Install emacsen-common for emacs
Package: rails
Version: 2:6.0.3.4+dfsg-2
Severity: serious
When I rebuilt all the packages during the rollup plugin transitions,
rails did not ftbfs, even though the rollup command actually failed.
cd activestorage; mkdir node_modules; \
ln -s rollup-plugin-commonjs node_modules; rollup -c;
Your message dated Sun, 3 Jan 2021 08:04:32 +
with message-id
and subject line fixed in 1:10.0.0+r36-1
has caused the Debian Bug report #977023,
regarding symbol lookup error in libbacktrace.so.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sun, 03 Jan 2021 08:20:50 +
with message-id
and subject line Bug#957359: fixed in infinipath-psm 3.3+20.604758e7-6.1
has caused the Debian Bug report #957359,
regarding infinipath-psm: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has
Control: tag -1 pending
Hello,
Bug #957434 in apt 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 #957434 [src:libept] libept: ftbfs with GCC-10
Added tag(s) pending.
--
957434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Sun, 3 Jan 2021 11:11:02 +0800 YunQiang Su wrote:
> On Sun, 03 Jan 2021 00:08:34 +0800 Shengjing Zhu wrote:
> > Source: sopt
> > Version: 3.0.1-11
> > Severity: serious
> > X-Debbugs-Cc: z...@debian.org
> >
> >
> > When binNMU sopt, it FTBFS on mips64el, please check log at
> >
Your message dated Sun, 03 Jan 2021 10:03:50 +
with message-id
and subject line Bug#978704: fixed in securefs 0.11.1+ds-2
has caused the Debian Bug report #978704,
regarding securefs: autopkgtests hard-code dependency on libcrypto++6
to be marked as done.
This means that you claim that the
Your message dated Sun, 3 Jan 2021 11:09:37 +0100
with message-id
and subject line Resolved
has caused the Debian Bug report #978229,
regarding osmo-bsc: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (<
0.7.0) but 4.4.13-2 is to be installed
to be marked as done.
This means that you
Your message dated Sun, 3 Jan 2021 11:09:37 +0100
with message-id
and subject line Resolved
has caused the Debian Bug report #978239,
regarding openbsc: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (<
0.7.0) but 4.4.13-2 is to be installed
to be marked as done.
This means that you claim
Your message dated Sun, 3 Jan 2021 11:09:37 +0100
with message-id
and subject line Resolved
has caused the Debian Bug report #978233,
regarding osmo-hlr: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (<
0.7.0) but 4.4.13-2 is to be installed
to be marked as done.
This means that you
Your message dated Sun, 3 Jan 2021 11:09:37 +0100
with message-id
and subject line Resolved
has caused the Debian Bug report #978241,
regarding osmo-msc: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (<
0.7.0) but 4.4.13-2 is to be installed
to be marked as done.
This means that you
Your message dated Sun, 3 Jan 2021 11:09:37 +0100
with message-id
and subject line Resolved
has caused the Debian Bug report #978244,
regarding libosmo-netif: FTBFS: unsatisfiable build-dependency: libbctoolbox1
(< 0.7.0) but 4.4.13-2 is to be installed
to be marked as done.
This means that you
Your message dated Sun, 3 Jan 2021 11:09:37 +0100
with message-id
and subject line Resolved
has caused the Debian Bug report #978221,
regarding osmo-bts: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (<
0.7.0) but 4.4.13-2 is to be installed
to be marked as done.
This means that you
Your message dated Sun, 3 Jan 2021 11:09:37 +0100
with message-id
and subject line Resolved
has caused the Debian Bug report #978222,
regarding osmo-sgsn: FTBFS: unsatisfiable build-dependency: libbctoolbox1 (<
0.7.0) but 4.4.13-2 is to be installed
to be marked as done.
This means that you
Control: tags 957293 pending upstream
Matthias Klose wrote...
> The package fails to build in a test rebuild on at least amd64 with
> gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be done for
Processing control commands:
> tags 957293 pending upstream
Bug #957293 [src:gnupg1] gnupg1: ftbfs with GCC-10
Added tag(s) upstream and pending.
--
957293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 947384 + pending
Bug #947384 [ipmitool] ipmitool: conffile not removed: /etc/default/ipmievd
Added tag(s) pending.
> tags 950206 + pending
Bug #950206 [ipmitool] ipmitool: ipmievd.service should be
After=openipmi.service
Added tag(s)
Hi Jörg,
On Sat, Jan 02, 2021 at 01:22:09PM +0100, Salvatore Bonaccorso wrote:
> Control: severity -1 grave
>
> Hi Jörg, Adam,
>
> On Wed, Feb 05, 2020 at 10:11:58PM +0100, Salvatore Bonaccorso wrote:
> > Source: ipmitool
> > Version: 1.8.18-8
> > Severity: important
> > Tags: security upstream
Processing control commands:
> severity -1 serious
Bug #960707 [libalure1] libalure1: Binary rebuild with current libfluidsynth2
Bug #963122 [libalure1] bucklespring: error loading shared objectfile
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> found -1 1.2-6.1
Control: severity -1 serious
Control: found -1 1.2-6.1
Hi,
Bastian Germann wrote in #960707:
> libalure1 recommends libfluidsynth1. Please rebuild the package so that
> it uses the libfluidsynth2 ABI and recommends the current package
> version.
It's worse than you and I expected:
* That
Processing control commands:
> severity -1 serious
Bug #963122 [libalure1] bucklespring: error loading shared objectfile
Bug #960707 [libalure1] libalure1: Binary rebuild with current libfluidsynth2
Ignoring request to change severity of Bug 963122 to the same value.
Ignoring request to change
Package: mtail
Version: 3.0.0~rc38-1
Severity: serious
X-Debbugs-Cc: z...@debian.org
https://buildd.debian.org/status/logs.php?pkg=mtail=3.0.0%7Erc38-1=s390x
It has been tried 3 times, still failed to build.
Fail at the same place:
=== RUN TestReadFromPipe/10ms_false
Hi Bastien,
Hope you are ok.
On Tue, Dec 15, 2020 at 10:34:59AM +0100, Bastien ROUCARIES wrote:
> Hi,
>
> As said on debian-provate go ahead please. I am late due to payjob issue.
Alright attached is a proposed debdiff for covering the CVEs, but
please double check them as well please (it
Processing commands for cont...@bugs.debian.org:
> severity 976558 important
Bug #976558 [src:python-fluids] python-fluids: FTBFS on arm64,ppc64el
(arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.8 3.9" returned exit code 13
Severity set to
Your message dated Sun, 03 Jan 2021 14:26:00 +
with message-id
and subject line Bug#964834: fixed in haskell-yi-language 0.19.0-1
has caused the Debian Bug report #964834,
regarding haskell-yi-language: BD-Uninstallable
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 03 Jan 2021 14:26:00 +
with message-id
and subject line Bug#965206: fixed in haskell-yi-language 0.19.0-1
has caused the Debian Bug report #965206,
regarding haskell-yi-language: Removal notice: broken and unmaintained
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> fixed 966853 3.1.1-1
Bug #966853 [src:gophernicus] gophernicus: FTBFS: ld:
file.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity';
gophernicus.o:/usr/include/tcpd.h:115: first defined here
The source 'gophernicus' and version
1 - 100 of 122 matches
Mail list logo
