Processing commands for cont...@bugs.debian.org:
> forwarded 997170 n...@uk.ibm.com
Bug #997170 [src:nmon] nmon: FTBFS: lmon16m.c:5478:45: error: format not a
string literal and no format arguments [-Werror=format-security]
Set Bug forwarded-to-address to 'n...@uk.ibm.com'.
> thanks
Stopping
> > === FAILURES
> > ===
> > _ test_supported_upgrade_request[H11Protocol]
> > __
> >
> > protocol_cls =
> >
> > @pytest.mark.parametrize("protocol_cls", HTTP_PROTOCOLS)
> > def
Your message dated Tue, 2 Nov 2021 00:26:51 -0300
with message-id <20211102032651.sn2lyyg6duvodsg7@debian>
and subject line Re: taskd: Unsuitable for stable release
has caused the Debian Bug report #960223,
regarding taskd: Unsuitable for stable release
to be marked as done.
This means that you
Your message dated Tue, 02 Nov 2021 03:19:59 +
with message-id
and subject line Bug#996371: fixed in ruby-roo 2.8.3-2
has caused the Debian Bug report #996371,
regarding ruby-roo: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
NoMethodError:
to be marked as done.
This means that you
On Tue, Oct 26, 2021 at 05:35:48AM +0200, Sebastiaan Couwenberg wrote:
> PROJ 8.2.0 is scheduled for release next week, just wait for that.
Oh, I see this has been uploaded. I'll try to sort out updating the
survex package to use it.
Cheers,
Olly
Processing commands for cont...@bugs.debian.org:
> fixed 997806 3.2.0-1
Bug #997806 {Done: Boyuan Yang } [src:aom] aom: possible ABI
breakage; causes ffmpeg autopkgtests failures
Marked as fixed in versions aom/3.2.0-1.
> fixed 972467 3.2.0-1
Bug #972467 {Done: Boyuan Yang } [src:aom] aom:
Hi
> What kind of files / tags did you process with easytag? If these files
that were mp3, not sure about what version of tags since they were gone
afterwards. At least they displayed fine in all music players I used.
But yes, I guess it is common here in Japan that id3v1 tags are coded in
UTF8
Your message dated Mon, 01 Nov 2021 23:36:48 +
with message-id
and subject line Bug#997605: fixed in pprofile 2.1.0-1
has caused the Debian Bug report #997605,
regarding pprofile: FTBFS: error in pprofile setup command: use_2to3 is invalid.
to be marked as done.
This means that you claim
Your message dated Mon, 01 Nov 2021 23:04:39 +
with message-id
and subject line Bug#995979: fixed in pamix 1.6~git20180112.ea4ab3b-4
has caused the Debian Bug report #995979,
regarding pamix FTBFS: error: format not a string literal and no format
arguments [-Werror=format-security]
to be
Source: mu-editor
Version: 1.1.0~alpha2+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
mu-editor/experimental recently started to FTBFS:
=== FAILURES ===
_
Your message dated Mon, 01 Nov 2021 22:19:14 +
with message-id
and subject line Bug#997163: fixed in nudoku 2.1.0-0.1
has caused the Debian Bug report #997163,
regarding nudoku: FTBFS: main.c:546:89: error: format not a string literal and
no format arguments [-Werror=format-security]
to be
Your message dated Mon, 01 Nov 2021 22:19:33 +
with message-id
and subject line Bug#997618: fixed in python-jsmin 3.0.0-1
has caused the Debian Bug report #997618,
regarding python-jsmin: FTBFS: error in jsmin setup command: use_2to3 is
invalid.
to be marked as done.
This means that you
Source: adios
Version: 1.13.1-29
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
autopkgtests fail with:
| Broken autopkgtest-satdep:amd64 Depends on libadios-mpi-dev:amd64 < none @un
H >
| Removing autopkgtest-satdep:amd64 because I can't find
libadios-mpi-dev:amd64
See
Your message dated Mon, 01 Nov 2021 22:04:00 +
with message-id
and subject line Bug#997167: fixed in ncdc 1.22.1-3
has caused the Debian Bug report #997167,
regarding ncdc: FTBFS: src/uit_dl.c:227:25: error: format not a string literal
and no format arguments [-Werror=format-security]
to be
Your message dated Mon, 01 Nov 2021 22:03:29 +
with message-id
and subject line Bug#997136: fixed in asterisk 1:16.16.1~dfsg-3
has caused the Debian Bug report #997136,
regarding asterisk: FTBFS: configure: error: *** ANSI C header files not found.
to be marked as done.
This means that you
Source: puma
Version: 5.3.2-3
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
puma fails to build on amd64 and mips*el:
| Errors & Failures:
|
| 1) Failure:
|
On Mon, 1 Nov 2021 at 23:33, Joshua Peisach wrote:
> Nemo (Cinnamon's file manager) is failing to build with this same "KeyError:
> 'install_dir'" issue, and I feel like it is a 0.60 regression as previous
> versions didn't fail.
>
> Hope this gets fixed soon.
This is already fixed upstream
I can confirm this. Upgrade of KDE on testing is totally broken at the moment.
On Sat, 23 Oct 2021 15:57:47 +0200 Chris Nospam wrote:
> KDE/Plasma (package dependencies) are currently completely broken under
testing. Is there currently a chance to (somehow simply) block the partial
transition
Processing control commands:
> tags 998124 + confirmed
Bug #998124 [meson] meson: gnome module missing install_dir fix for c_template
Added tag(s) confirmed.
--
998124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Your message dated Mon, 01 Nov 2021 21:19:18 +
with message-id
and subject line Bug#998238: fixed in syncany 0.4.9~alpha-4
has caused the Debian Bug report #998238,
regarding syncany: FTBFS: Could not resolve commons-io:commons-io:2.4.
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> severity 998285 important
Bug #998285 [src:libgig] libgig: fails to clean after build
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998285:
Source: vulkan-validationlayers
Version: 1.2.162.0-1
Severity: serious
X-Debbugs-CC: d...@duckcorp.org
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Processing commands for cont...@bugs.debian.org:
> reassign 995358 src:ruby-batch-loader 2.0.1+dfsg-2
Bug #995358 [src:ruby-graphql, src:ruby-batch-loader] ruby-graphql breaks
ruby-batch-loader autopkgtest: uninitialized constant
GraphQL::StaticValidation::Validator::Timeout
Bug reassigned from
Your message dated Mon, 01 Nov 2021 21:04:23 +
with message-id
and subject line Bug#996731: fixed in golang-github-go-macaron-i18n
0.0~git20160612.0.ef57533-8.1
has caused the Debian Bug report #996731,
regarding src:golang-github-go-macaron-i18n: fails to migrate to testing for
too long:
Processing control commands:
> close -1 0.13.1-1
Bug #998293 [src:phosh] src:phosh: fails to migrate to testing for too long
Marked as fixed in versions phosh/0.13.1-1.
Bug #998293 [src:phosh] src:phosh: fails to migrate to testing for too long
Marked Bug as done
--
998293:
Source: phosh
Version: 0.8.0-1
Severity: serious
Control: close -1 0.13.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as
Control: tags -1 important
On 2021-11-01 20:58:14 +0100, Andreas Beckmann wrote:
> Source: libgig
> Version: 4.3.0~ds1-1
> Severity: serious
>
> Hi,
>
> libgig fails to build twice in a row since it cannot clean up after a
> successful build:
>
>dh_clean
> rm: cannot remove './doc/html':
Your message dated Mon, 01 Nov 2021 20:36:29 +
with message-id
and subject line Bug#996723: fixed in python-pluggy 0.13.0-7.1
has caused the Debian Bug report #996723,
regarding src:python-pluggy: fails to migrate to testing for too long: uploader
built arch:all binaries
to be marked as
Your message dated Mon, 01 Nov 2021 20:36:34 +
with message-id
and subject line Bug#996721: fixed in pyzbar 0.1.8-3.1
has caused the Debian Bug report #996721,
regarding src:pyzbar: fails to migrate to testing for too long: uploader build
arch:all binaries
to be marked as done.
This means
On Mon, 1 Nov 2021 20:49:58 +0100 Paul Gevers wrote:
Hello Paul,
Is this run on all cores? Our armhf worker has 160 cores, so you may be
running into limits you didn't expect.
This would be a surprising bug, indeed.
I will have a closer look. But I think I have ultimately
to contact the
Processing commands for cont...@bugs.debian.org:
> found 982794 78.14.0esr-1+b1
Bug #982794 [firefox-esr] firefox-esr/armhf: fails on non-NEON systems
Marked as found in versions firefox-esr/78.14.0esr-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
Package: gnunet
Version: 0.14.0-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the
Package: node-clipanion
Version: 2.6.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-clipanion FTBFS in a minimal chroot:
dh_auto_build --buildsystem=nodejs
Found debian/nodejs/./build
cd ./. && sh -ex debian/nodejs/./build
+ rollup -c
Source: r-cran-pdftools
Version: 3.0.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
Your package r-cran-pdftools has an autopkgtest, great. However, it
fails. Can you please investigate the situation and
Source: r-cran-psych
Version: 2.1.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian...@lists.debian.org
Dear maintainer(s),
Your package has an autopkgtest, great! However, since somewhere between
20 October and 1 November 2021 it started to fail
Source: libgig
Version: 4.3.0~ds1-1
Severity: serious
Hi,
libgig fails to build twice in a row since it cannot clean up after a
successful build:
dh_clean
rm: cannot remove './doc/html': Is a directory
dh_clean: error: rm -f -- debian/libgig-dev.substvars debian/libgig10.substvars
Your right, but I think (not on the basis of real knowledge) that
ml-nlffigen isn't used in either the compilation
of the MLton compiler, nor by the MLton compiler in compiling user
code. I thought that it was
for a MLton compiler user to use, and had been tweaked so that the
output was usable by
Hi Jerome,
On 24-09-2021 22:23, Paul Gevers wrote:
> The above exception was the direct cause of the following exception:
>
> def test_elevation():
>
> G = ox.graph_from_address(address=address, dist=500,
> dist_type="bbox", network_type="bike")
> rasters =
Am Mon, Nov 01, 2021 at 08:28:50PM +0100 schrieb Moritz Mühlenhoff:
> Am Sun, Feb 09, 2020 at 01:18:27PM +0100 schrieb Andreas Tille:
> > Hi,
> >
> > I've taken over this package into Debian Med team to
> >
> >https://salsa.debian.org/med-team/python-neuroshare
> >
> > It needs some
Source: uhd
Version: 4.1.0.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
uhd/experimental FTBFS when building only the arch-all packages as done
on the buildd:
Am Sun, Feb 09, 2020 at 01:18:27PM +0100 schrieb Andreas Tille:
> Hi,
>
> I've taken over this package into Debian Med team to
>
>https://salsa.debian.org/med-team/python-neuroshare
>
> It needs some remaining work to port for Python3 which I
> can not do right now. Any help is welcome.
Am Fri, Jan 29, 2021 at 09:56:46PM + schrieb Thorsten Alteholz:
> Hi Moritz,
>
> On Fri, 29 Jan 2021, Moritz Mühlenhoff wrote:
> > opencaster seems dead upstream, should it be removed or are
> > you planning to port it to Python 3 yourself?
>
> I don't plan to do the porting myself, so I
Your message dated Mon, 01 Nov 2021 19:18:30 +
with message-id
and subject line Bug#998261: fixed in jsbundle-web-interfaces
1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2
has caused the Debian Bug report #998261,
regarding jsbundle-web-interfaces: autopkgtest regression: node: command not
found
to
Your message dated Mon, 01 Nov 2021 19:18:36 +
with message-id
and subject line Bug#997927: fixed in leveldb 1.23-3
has caused the Debian Bug report #997927,
regarding bitcoind: fails to start with undefined symbol: _ZTIN7leveldb6LoggerE
to be marked as done.
This means that you claim that
Your message dated Mon, 01 Nov 2021 19:18:36 +
with message-id
and subject line Bug#997927: fixed in leveldb 1.23-3
has caused the Debian Bug report #997927,
regarding Please re-enable RTTI support in leveldb
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> tag -1 pending
Bug #998261 [src:jsbundle-web-interfaces] jsbundle-web-interfaces: autopkgtest
regression: node: command not found
Added tag(s) pending.
--
998261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998261
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #998261 in jsbundle-web-interfaces 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:
Source: epigrass
Version: 3.0.3+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of epigrass the autopkgtest of epigrass fails in
testing when that autopkgtest is run with the binary
Source: llvmlite
Version: 0.35.0-3
Followup-For: Bug #974778
Control: affects -1 src:numba
Now that bullseye is released, please proceed fixing this bug now,
i.e. please package llvmlite 0.37.
It's required in order to package numba 0.54, which is needed to fix
problems on armel.
Processing control commands:
> affects -1 src:numba
Bug #974778 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-11
Bug #974801 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-11
Bug #974824 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-11
Added indication that
Source: jsbundle-web-interfaces
Version: 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-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 jsbundle-web-interfaces the autopkgtest of
Processing control commands:
> close -1 2.2-1
Bug #998259 [src:osslsigncode] src:osslsigncode: fails to migrate to testing
for too long: unresolved RC bugs
Marked as fixed in versions osslsigncode/2.2-1.
Bug #998259 [src:osslsigncode] src:osslsigncode: fails to migrate to testing
for too long:
Source: osslsigncode
Version: 2.1-1
Severity: serious
Control: close -1 2.2-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 993451 993452
Control: tags 993451 ftbfs
Control: severity 993451 serious
Control: tags 993452 ftbfs
Control:
Your message dated Mon, 01 Nov 2021 18:04:37 +
with message-id
and subject line Bug#996387: fixed in ruby-sigar 0.7.3-3
has caused the Debian Bug report #996387,
regarding ruby-sigar: FTBFS with ruby3.0: sigar_util.c:742:10: fatal error:
rpc/rpc.h: No such file or directory
to be marked as
Source: node-liftoff
Version: 3.1.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-liftoff/experimental recently started to FTBFS with
dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known
Processing commands for cont...@bugs.debian.org:
> # I don't think this warrants an RC bug
> severity 994456 important
Bug #994456 [src:ruby-stackprof] ruby-stackprof: flaky autopkgtests
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need
Source: fbzx
Version: 3.1.0-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
Hi,
fbzx FTBFS with GCC 11 which defaults to -std=c++17:
g++ -c -O2 -Wdate-time -D_FORTIFY_SOURCE=2 `pkg-config --cflags sdl
libpulse-simple
Your message dated Mon, 01 Nov 2021 17:34:32 +
with message-id
and subject line Bug#997309: fixed in django-countries 7.2.1-1
has caused the Debian Bug report #997309,
regarding django-countries: FTBFS: AttributeError: 'CountryField' object has no
attribute 'db_collation'
to be marked as
Your message dated Mon, 01 Nov 2021 17:20:12 +
with message-id
and subject line Bug#997411: fixed in libstatgen 1.0.15-2
has caused the Debian Bug report #997411,
regarding libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output
Processing control commands:
> tag -1 pending
Bug #997309 [src:django-countries] django-countries: FTBFS: AttributeError:
'CountryField' object has no attribute 'db_collation'
Added tag(s) pending.
--
997309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997309
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #997309 in django-countries 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:
* Henry Cejtin:
> (I assume you meant ml-nlffigen.) ml-nlffigen is part of SML/NJ, not
> part of MLton.
/usr/bin/mlnlffigen is part of mlton-tools.
I believe the code generation requirements are different for MLton and
SML/NJ.
Processing control commands:
> tag -1 pending
Bug #996387 [src:ruby-sigar] ruby-sigar: FTBFS with ruby3.0:
sigar_util.c:742:10: fatal error: rpc/rpc.h: No such file or directory
Added tag(s) pending.
--
996387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996387
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #996387 in ruby-sigar 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:
Your message dated Mon, 01 Nov 2021 16:48:48 +
with message-id
and subject line Bug#997330: fixed in cpl-plugin-amber 4.4.1+dfsg-1
has caused the Debian Bug report #997330,
regarding cpl-plugin-amber: FTBFS: configure: error: Installed cfitsio
(unknown) is too old
to be marked as done.
This
Your message dated Mon, 01 Nov 2021 16:50:04 +
with message-id
and subject line Bug#997292: fixed in wsclean 3.0-1
has caused the Debian Bug report #997292,
regarding wsclean: FTBFS: ld: libwsclean.so.2: undefined reference to
`H5::DataSpace::selectAll() const'
to be marked as done.
This
Your message dated Mon, 01 Nov 2021 16:49:00 +
with message-id
and subject line Bug#997195: fixed in cpl-plugin-vimos 4.1.6+dfsg-1
has caused the Debian Bug report #997195,
regarding cpl-plugin-vimos: FTBFS: vimos_flat_normalise.cc:479:23: error:
aggregate ‘std::stringstream ss’ has
Your message dated Mon, 01 Nov 2021 16:48:54 +
with message-id
and subject line Bug#997214: fixed in cpl-plugin-fors 5.5.7+dfsg-1
has caused the Debian Bug report #997214,
regarding cpl-plugin-fors: FTBFS: fors_flat_normalise.cc:582:23: error:
aggregate ‘std::stringstream ss’ has incomplete
Your message dated Mon, 01 Nov 2021 16:36:10 +
with message-id
and subject line Bug#997294: fixed in skesa 2.4.0-3
has caused the Debian Bug report #997294,
regarding skesa: FTBFS: ld:
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libncbi-vdb.so:
undefined reference to
the ubuntu tracker claims this is golang 1.16 related:
https://bugs.launchpad.net/debian/+source/consul/+bug/1940152
not sure how to proceed here, though...
--
regards,
Reinhard
Your message dated Mon, 01 Nov 2021 16:18:58 +
with message-id
and subject line Bug#997450: fixed in libseqlib 1.2.0+dfsg-7
has caused the Debian Bug report #997450,
regarding libseqlib: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output
Am Montag, dem 01.11.2021 um 16:53 +0100 schrieb Daniel Leidert:
> Am Mittwoch, dem 27.10.2021 um 11:02 -0300 schrieb Lucas Kanashiro:
>
> [..]
> > * ruby-ferret
> [..]
>
> Also a candidate for an RoM. Dead for 4 years, no reverse build-deps. Requires
> a lot of patches and seems to be seriously
Your message dated Mon, 01 Nov 2021 16:04:26 +
with message-id
and subject line Bug#997249: fixed in mpsolve 3.2.1-5
has caused the Debian Bug report #997249,
regarding mpsolve: FTBFS: ./conftest.c:34: undefined reference to `yywrap'
to be marked as done.
This means that you claim that the
Hi Gary,
KDE Plasma is currently broken in testing. Do you have a mixed Plasma,
e.g. some packages from 5.21.5 and some from 5.23.0 ?
If yes, then please see the following bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996726
--
Med vänliga hälsningar
Patrick Franz
Am Montag, dem 01.11.2021 um 07:20 -0700 schrieb tony mancill:
> On Mon, Nov 01, 2021 at 02:06:32PM +0100, Andreas Beckmann wrote:
> > Source: syncany
> > Version: 0.4.9~alpha-3
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source
> >
> > Hi,
> >
> > syncany
Your message dated Mon, 01 Nov 2021 15:35:32 +
with message-id
and subject line Bug#996530: fixed in yard 0.9.26-1
has caused the Debian Bug report #996530,
regarding yard: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load
such file -- webrick
to be marked as done.
This means
Processing control commands:
> tag -1 pending
Bug #996313 [src:ruby-libvirt] ruby-libvirt: FTBFS with ruby3.0:
common.c:27:10: fatal error: st.h: No such file or directory
Added tag(s) pending.
--
996313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996313
Debian Bug Tracking System
Control: tags -1 confirmed
On Sat, 23 Oct 2021 21:18:43 +0200 Lucas Nussbaum wrote:
During a rebuild of all packages in sid, your package failed to build
on amd64.
I believe this became an issue when autoconf was bumped from 2.69 to 2.71
in unstable a few months ago.
Fortunately, it has
Processing control commands:
> tags -1 confirmed
Bug #997249 [src:mpsolve] mpsolve: FTBFS: ./conftest.c:34: undefined reference
to `yywrap'
Added tag(s) confirmed.
--
997249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #996313 in ruby-libvirt 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:
Your message dated Mon, 01 Nov 2021 15:04:50 +
with message-id
and subject line Bug#996952: fixed in libkolabxml 1.2.0-3
has caused the Debian Bug report #996952,
regarding libkolabxml ftbfs with GCC 11
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 01 Nov 2021 14:49:08 +
with message-id
and subject line Bug#984015: fixed in cif-tools 1.0.0-4
has caused the Debian Bug report #984015,
regarding cif-tools: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If
(I assume you meant ml-nlffigen.) ml-nlffigen is part of SML/NJ, not
part of MLton.
On Mon, Nov 1, 2021 at 8:34 AM Florian Weimer wrote:
>
> * Henry Cejtin:
>
> > As far as I know, the ckit stuff is just included because it needed
> > some tweaks to work under MLton.
> > I don't think that any
Your message dated Mon, 01 Nov 2021 14:30:03 +
with message-id
and subject line Bug#997651: fixed in python-ara 1.5.7-1
has caused the Debian Bug report #997651,
regarding python-ara: FTBFS: TypeError: 'AnsibleYamlJinjaLexer' object is not
callable
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> owner 998238 tmanc...@debian.org
Bug #998238 [src:syncany] syncany: FTBFS: Could not resolve
commons-io:commons-io:2.4.
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
On Mon, Nov 01, 2021 at 02:06:32PM +0100, Andreas Beckmann wrote:
> Source: syncany
> Version: 0.4.9~alpha-3
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
>
> Hi,
>
> syncany recently started to FTBFS:
Hi Andreas,
Thank you for the bug report. The recent upload
* Henry Cejtin:
> As far as I know, the ckit stuff is just included because it needed
> some tweaks to work under MLton.
> I don't think that any of "our" stuff depends on it.
I think mlnffigen needs ckit.
Control: tag -1 pending
Hello,
Bug #997484 in sqlalchemy 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 #997484 [python3-sqlalchemy] python3-sqlalchemy: Undeclared dependency on
python3-greenlet
Added tag(s) pending.
--
997484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: cufflinks
Version: 2.2.1+dfsg.1-8
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
Hi,
cufflinks recently started to FTBFS:
dh_autoreconf
sh: 1: svnversion: not found
configure.ac:113: error: AM_INIT_AUTOMAKE
Processing commands for cont...@bugs.debian.org:
> tags 984213 + help
Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11
Added tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984213:
Your message dated Mon, 01 Nov 2021 13:33:57 +
with message-id
and subject line Bug#997447: fixed in libbpp-popgen 2.4.1-6
has caused the Debian Bug report #997447,
regarding libbpp-popgen: FTBFS: dpkg-gensymbols: error: some symbols or
patterns disappeared in the symbols file: see diff
Your message dated Mon, 01 Nov 2021 13:33:51 +
with message-id
and subject line Bug#997444: fixed in libbpp-phyl 2.4.1-6
has caused the Debian Bug report #997444,
regarding libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output
Your message dated Mon, 01 Nov 2021 13:34:03 +
with message-id
and subject line Bug#997413: fixed in libbpp-qt 2.4.1-6
has caused the Debian Bug report #997413,
regarding libbpp-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output below
Your message dated Mon, 01 Nov 2021 13:33:28 +
with message-id
and subject line Bug#997202: fixed in deepin-movie-reborn 5.7.15-1
has caused the Debian Bug report #997202,
regarding deepin-movie-reborn: FTBFS: compositing_manager.cpp:48:10: fatal
error: mpv/qthelper.hpp: No such file or
Package: texlive
Version: 2021.20210921-1
Severity: serious
Tags: sid bookworm
Control: affects -1 + src:lgrind
Hi,
lgrind recently started to FTBFS:
latex lgrind.dtx
This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian)
(preloaded format=latex)
restricted \write18
Processing control commands:
> affects -1 + src:lgrind
Bug #998240 [texlive] texlive: causes lgrind to FTBFS
Added indication that 998240 affects src:lgrind
--
998240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 01 Nov 2021 13:18:29 +
with message-id
and subject line Bug#997443: fixed in libbpp-core 2.4.1-7
has caused the Debian Bug report #997443,
regarding libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output
Source: syncany
Version: 0.4.9~alpha-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
syncany recently started to FTBFS:
:syncany-lib:debianMavenPom (Thread[Task worker for ':',5,main]) started.
:syncany-lib:debianMavenPom
Putting task artifact state for task
Source: arb
Version: 6.0.6-4
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
Hi,
arb FTBFS in sid:
g++ -fPIC -g -O2 -ffile-prefix-map=/build/arb-6.0.6=. -fstack-protector-strong
-Wformat -Werror=format-security -O3 -pipe
1 - 100 of 150 matches
Mail list logo
