Source: bijiben
Version: 40.1-2
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: jpakk...@gmail.com
bijiben fails to build from source in unstable. A build notably
contains:
| dh_auto_configure -- \
| -Dupdate_mimedb=false
| cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson ..
--wrap-mo
Package: easytag
Version: 2.4.3-4+b1
Severity: critical
Justification: causes serious data loss
Hi
it seems easytag has not arrived in the 20th century, since today it
deleted all tags of 3 CD releases containing compilations of Japanese
singers on my disk. All information that contained UTF8 cod
Control: tags 997136 + patch
Control: tags 997136 + pending
Dear maintainer,
I've prepared an NMU for asterisk (versioned as 1:16.16.1~dfsg-2.1). The diff
is attached to this message.
I require a sponsor to have it uploaded.
This is particularly urgent as unixodbc is about to enter a transition
Processing control commands:
> tags 997136 + patch
Bug #997136 [src:asterisk] asterisk: FTBFS: configure: error: *** ANSI C header
files not found.
Added tag(s) patch.
> tags 997136 + pending
Bug #997136 [src:asterisk] asterisk: FTBFS: configure: error: *** ANSI C header
files not found.
Added t
The problem is that executing exe/byebug fails:
RUBYLIB=. GEM_PATH=/build/ruby-byebug-tmDpwr/ruby-byebug-11.1.3/debian/ruby-
byebug/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0:/build/ruby-byebug-
tmDpwr/ruby-byebug-
11.1.3/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.
Dixi quod…
>contents of files that start with a cpp-able string *and* contain
>a tab somewhere after that (because calendar(1) does not call cpp(1)
>with -traditional-cpp, which is another minor bug in the port), but
I was mistaken, it does call it like that, and it does work:
#define·ssh·Nov·01
Package: calendar
Version: 12.1.7+nmu3
Severity: serious
Tags: security
Justification: security
X-Debbugs-Cc: t...@mirbsd.de, Debian Security Team
I was wondering how Debian’s calendar(1) packaging handled the
setusercontext(3) part, and after finding d/p/calendar_cap.diff
I see it just… does awa
Your message dated Sun, 31 Oct 2021 23:19:40 +
with message-id
and subject line Bug#995419: fixed in rust-utf-8 0.7.6-2
has caused the Debian Bug report #995419,
regarding rust-utf-8: autopkgtest regression: crate directory not found:
/usr/share/cargo/registry/utf-8-0.7.6
to be marked as done
Again, I don't think that that is anything used either in MLton
construction or use.
I would tink that if the license can be found and is good enough, like
the ckit stuff, it could go in
a MLton non-free package. Otherwise, I guess just remove it.
Matthew?
On Sun, Oct 31, 2021 at 12:41 PM Ryan Ka
Package: plasma-desktop
Version: 4:5.21.5-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
after rebooting my computer, I am unable to log into my plasma de
Processing control commands:
> close -1 6.0.0-1
Bug #998202 [src:unicorn] unicorn: test failure with ruby 3.0 as supported
version
Marked as fixed in versions unicorn/6.0.0-1.
Bug #998202 [src:unicorn] unicorn: test failure with ruby 3.0 as supported
version
Marked Bug as done
--
998202: https
Source: unicorn
Version: 5.5.3-1
Severity: serious
Tags: ftbfs bookworm sid
Control: close -1 6.0.0-1
https://buildd.debian.org/status/logs.php?pkg=unicorn&ver=5.5.3-1%2Bb4
...
===
Failure: test_client_malformed_body(WebS
Source: ruby-commonmarker
Version: 0.21.0-1
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/logs.php?pkg=ruby-commonmarker&ver=0.21.0-1%2Bb1
...
Finished in 14.625775s, 18.8024 runs/s, 26.1866 assertions/s.
1) Failure:
TestCommands#test_basic [/<>/test/test_commands
Your message dated Sun, 31 Oct 2021 22:03:58 +
with message-id
and subject line Bug#984071: fixed in jigdo 0.8.1-1
has caused the Debian Bug report #984071,
regarding jigdo: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sun, 31 Oct 2021 22:04:15 +
with message-id
and subject line Bug#991650: fixed in python-django-imagekit 4.0.2-4
has caused the Debian Bug report #991650,
regarding python-django-imagekit: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.9 returned exit co
Your message dated Sun, 31 Oct 2021 21:49:22 +
with message-id
and subject line Bug#996233: fixed in ruby-gd 0.8.0-8
has caused the Debian Bug report #996233,
regarding ruby-gd: FTBFS with ruby3.0: error: assignment of read-only member
‘klass’
to be marked as done.
This means that you claim
Processing control commands:
> tag -1 pending
Bug #991650 [src:python-django-imagekit] python-django-imagekit: FTBFS:
dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit
code 13
Added tag(s) pending.
--
991650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991650
De
Control: tag -1 pending
Hello,
Bug #991650 in python-django-imagekit 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/python-team/packages/python-django-imagekit
Your message dated Sun, 31 Oct 2021 21:33:29 +
with message-id
and subject line Bug#997428: fixed in cloud-sptheme 1.10.1.post20200504175005-2
has caused the Debian Bug report #997428,
regarding cloud-sptheme: FTBFS: AttributeError: module 'sphinx.roles' has no
attribute 'emph_literal_role'
t
Processing control commands:
> tag -1 pending
Bug #996233 [src:ruby-gd] ruby-gd: FTBFS with ruby3.0: error: assignment of
read-only member ‘klass’
Added tag(s) pending.
--
996233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996233
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Control: tag -1 pending
Hello,
Bug #996233 in ruby-gd 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/ruby-team/ruby-gd/-/commit/79eb24c02a5e6e5acb2f33d3984e495
Control: tag -1 pending
Hello,
Bug #997428 in cloud-sptheme 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/python-team/packages/cloud-sptheme/-/commit/2f5eee37
Processing control commands:
> tag -1 pending
Bug #997428 [src:cloud-sptheme] cloud-sptheme: FTBFS: AttributeError: module
'sphinx.roles' has no attribute 'emph_literal_role'
Added tag(s) pending.
--
997428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997428
Debian Bug Tracking System
Con
Your message dated Sun, 31 Oct 2021 21:06:24 +
with message-id
and subject line Bug#997537: fixed in python-mediafile 0.8.1-2
has caused the Debian Bug report #997537,
regarding python-mediafile: FTBFS: rm: cannot remove
'/<>/debian/python3-mediafile/usr/lib/python3.9/dist-packages/mediafile-
Hi,
On 31-10-2021 08:09, Alexis Bienvenüe wrote:
> After rebuilding auto-multiple-choice from the same 1.5.1-2 sources in
> a sid environment, it passes the autopkgtest.
> Maybe this is related to this issue, where it is said that OpenCV 4.x
> releases don't guarantee ABI compatibility:
> https://
Processing commands for cont...@bugs.debian.org:
> forwarded 997428 https://foss.heptapod.net/doc-utils/cloud_sptheme/-/issues/45
Bug #997428 [src:cloud-sptheme] cloud-sptheme: FTBFS: AttributeError: module
'sphinx.roles' has no attribute 'emph_literal_role'
Set Bug forwarded-to-address to
'http
Your message dated Sun, 31 Oct 2021 19:34:35 +
with message-id
and subject line Bug#997266: fixed in trinculo 0.96+dfsg-4
has caused the Debian Bug report #997266,
regarding trinculo: FTBFS: src/trinculo.cpp:45:19: error: invalid ‘static_cast’
from type ‘std::__cxx11::basic_ostringstream’ to
Package: gitlab
Version: 14.1.7+ds1-2~fto11+1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Fresh installation of gitlab from fasttrack repository fails
Your message dated Sat, 30 Oct 2021 23:31:03 +
with message-id
and subject line Fixed in 3.2.0+bzr7543-1
has caused the Debian Bug report #994223,
regarding lintian-brush is unusable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Control: tag -1 pending
Hello,
Bug #997266 in trinculo reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/med-team/trinculo/-/commit/135b861c44d975b2e87e07755dfb28
Processing control commands:
> tag -1 pending
Bug #997266 [src:trinculo] trinculo: FTBFS: src/trinculo.cpp:45:19: error:
invalid ‘static_cast’ from type ‘std::__cxx11::basic_ostringstream’ to
type ‘std::ostringstream&’ {aka ‘std::__cxx11::basic_ostringstream&’}
Added tag(s) pending.
--
997266:
Your message dated Sun, 31 Oct 2021 19:18:47 +
with message-id
and subject line Bug#997259: fixed in xgammon 0.99.1128-5
has caused the Debian Bug report #997259,
regarding xgammon: FTBFS: save.c:145:60: error: ‘sys_siglist’ undeclared (first
use in this function)
to be marked as done.
This
Processing control commands:
> block -1 by 992003
Bug #998190 [src:sagemath] sagemath: package new upstream version
998190 was not blocked by any bugs.
998190 was not blocking any bugs.
Added blocking bug(s) of 998190: 992003
> block 986527 by -1
Bug #986527 [src:sagemath] testsuite is too fragile
Source: sagemath
Version: 9.2-2
Severity: serious
Control: block -1 by 992003
Control: block 986527 by -1
Control: block 993149 by -1
I started updating sagemath to version 9.4, which is the first version that
supports pari 2.13 (which is already in Debian and causes a large part of the
failing
Your message dated Sun, 31 Oct 2021 18:03:23 +
with message-id
and subject line Bug#997110: fixed in console-setup 1.206
has caused the Debian Bug report #997110,
regarding console-setup: FTBFS: ./kbdcompiler: ckbcomp failed
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 31 Oct 2021 18:03:28 +
with message-id
and subject line Bug#997564: fixed in golang-github-facebookgo-stack
0.0~git20160209.0.7517733-9
has caused the Debian Bug report #997564,
regarding golang-github-facebookgo-stack: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-
On Sun, Oct 31, 2021 at 12:01:34PM -0500, Henry Cejtin wrote:
> I would think that the right solution would be to move it into a
> separate package, and that package would be part of the "non-free"
> world in Debian.
That would work from my point of view.
While we're discussing non-free files, I'
Processing control commands:
> tag -1 pending
Bug #997564 [src:golang-github-facebookgo-stack]
golang-github-facebookgo-stack: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/facebookgo/stack
returned exit code 1
Added tag(s) pending.
--
997564: http
Control: tag -1 pending
Hello,
Bug #997564 in golang-github-facebookgo-stack 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/go-team/packages/golang-github-fac
Processing control commands:
> tag -1 pending
Bug #997110 [src:console-setup] console-setup: FTBFS: ./kbdcompiler: ckbcomp
failed
Added tag(s) pending.
--
997110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #997110 in console-setup 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/installer-team/console-setup/-/commit/8de87da89372d7
Samuel Thibault, le dim. 31 oct. 2021 18:00:11 +0100, a ecrit:
> Lucas Nussbaum, le sam. 23 oct. 2021 20:32:13 +0200, a ecrit:
> > Relevant part (hopefully):
> > > Compiling compact keymaps for amiga...
> > > Compiling compact keymaps for ataritt...
> > > Compiling compact keymaps for pc105...
> >
Lucas Nussbaum, le sam. 23 oct. 2021 20:32:13 +0200, a ecrit:
> Relevant part (hopefully):
> > Compiling compact keymaps for amiga...
> > Compiling compact keymaps for ataritt...
> > Compiling compact keymaps for pc105...
> > Compiling compact keymaps for sun4...
> > ./kbdcompiler: ckbcomp failed
>
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 would think that the right solution would be to move it into a
separate package, and that package
would be part of the "non-free" world in Debi
Your message dated Sun, 31 Oct 2021 16:54:29 +
with message-id
and subject line Bug#996336: fixed in pygalmesh 0.10.5-2
has caused the Debian Bug report #996336,
regarding pygalmesh: autopkgtest regression on i386
to be marked as done.
This means that you claim that the problem has been dealt
Control: forwarded -1 https://github.com/ceres-solver/ceres-solver/issues/715
On Sat, 23 Oct 2021 20:31:26 +0200 Lucas Nussbaum wrote:
Source: ceres-solver
Version: 1.14.0-14
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
This also breaks on the current draft version 2.0.0-1.
Processing control commands:
> forwarded -1 https://github.com/ceres-solver/ceres-solver/issues/715
Bug #997128 [src:ceres-solver] ceres-solver: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit
code 2
Set Bug forwarded-to-address to
Source: mklibs
Version: 0.1.40
Severity: serious
Justification: FTBFS
Hello,
mklibs currently fails to build in sid:
g++ -DHAVE_CONFIG_H -I. -I../../../src/mklibs-readelf -I../.. -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/build/mklibs-0.1.44.1=.
-fstack-protector-strong -Wfor
Your message dated Sun, 31 Oct 2021 15:49:11 +
with message-id
and subject line Bug#984293: fixed in plink 1.07+dfsg-4
has caused the Debian Bug report #984293,
regarding plink: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> fixed 997489 4.27.1-1
Bug #997489 [src:fonttools] fonttools: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.9 returned exit code 13
The source 'fonttools' and version '4.27.1-1' do not appear to match any binary
Control: tag -1 pending
Hello,
Bug #984293 in plink reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/med-team/plink/-/commit/d81491dbcd423a1e51f160c3523f897c15f2
Processing control commands:
> tag -1 pending
Bug #984293 [src:plink] plink: ftbfs with GCC-11
Added tag(s) pending.
--
984293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 normal
Hi Jens,
* Jens Schmidt [2021-10-30 20:27 +0200]:
> Package: libasound2-plugins
> Version: 1.2.2-2
> Severity: grave
> Justification: renders package unusable
The package is not unusable because of one use case out of many.
> Dear Maintainer,
>
> * What led up to
Processing control commands:
> severity -1 normal
Bug #998125 [libasound2-plugins] libasound2-plugins: Config file for a52 plugin
(60-a52-encoder.conf) produces no/garbled sound via optical digital out (S/PDIF)
Severity set to 'normal' from 'grave'
--
998125: https://bugs.debian.org/cgi-bin/bug
Your message dated Sun, 31 Oct 2021 15:22:06 +
with message-id
and subject line Bug#984370: fixed in tvc 5.0.3+git20151221.80e144e+dfsg-4
has caused the Debian Bug report #984370,
regarding tvc: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> tag -1 pending
Bug #984370 [src:tvc] tvc: ftbfs with GCC-11
Added tag(s) pending.
--
984370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 996152 + experimental
Bug #996152 [src:libsemanage] libsemanage: FTBFS: build-dependency not
installable: secilc (>= 3.2)
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996152: ht
Control: tag -1 pending
Hello,
Bug #984370 in tvc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/med-team/tvc/-/commit/9246131486fb4caa01ecb0d996c1936f83f3ea50
Source: ffcx
Version: 2019.2.0~git20210122.22ca4c0-2
Severity: serious
The binaries have been taken over by fenics-ffcx and ffcx should be
removed.
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Source: basix
Version: 0.0.1~git20210122.4f10ef2-2
Severity: serious
The binaries have been taken over by fenics-basix and basix should be
removed.
Cheers
--
Sebastian Ramacher
Your message dated Sun, 31 Oct 2021 14:49:01 +
with message-id
and subject line Bug#984334: fixed in skewer 0.2.2-6
has caused the Debian Bug report #984334,
regarding skewer: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Processing control commands:
> tag -1 pending
Bug #997561 [src:golang-github-zclconf-go-cty] golang-github-zclconf-go-cty:
FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4
github.com/zclconf/go-cty/cty github.com/zclconf/go-cty/cty/convert
github.com/zclconf/go-cty/cty/function
Control: tag -1 pending
Hello,
Bug #997561 in golang-github-zclconf-go-cty 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/go-team/packages/golang-github-zclco
Processing commands for cont...@bugs.debian.org:
> owner 997561 !
Bug #997561 [src:golang-github-zclconf-go-cty] golang-github-zclconf-go-cty:
FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4
github.com/zclconf/go-cty/cty github.com/zclconf/go-cty/cty/convert
github.com/zclconf
Processing commands for cont...@bugs.debian.org:
> forwarded 997563 https://github.com/urfave/cli/issues/1298
Bug #997563 [src:golang-github-urfave-cli] golang-github-urfave-cli: FTBFS:
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4
github.com/urfave/cli returned exit c
Processing commands for cont...@bugs.debian.org:
> forwarded 997557 https://github.com/urfave/cli/issues/1298
Bug #997557 [src:golang-github-urfave-cli-v2] golang-github-urfave-cli-v2:
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4
github.com/urfave/cli/v2 return
On Sun, Oct 31, 2021 at 6:42 PM Drew Parsons wrote:
>
> This doesn't seem to be a bug in the package. It just declares "vet" as
> a cli.Command in build.go.
>
> The error must be elsewhere in the go infrastructure, possibly in the dh
> go addon (dh-golang) which generates "go test" for dh_auto_tes
Your message dated Sun, 31 Oct 2021 13:18:43 +
with message-id
and subject line Bug#997629: fixed in pyraf 2.2.0~rc1-2
has caused the Debian Bug report #997629,
regarding pyraf: FTBFS: error in setup command: use_2to3 is invalid.
to be marked as done.
This means that you claim that the proble
Your message dated Sun, 31 Oct 2021 13:03:23 +
with message-id
and subject line Bug#998114: fixed in asciidoc 10.0.1-3
has caused the Debian Bug report #998114,
regarding Missing egg info directory prevents asciidoc cli tools from running
to be marked as done.
This means that you claim that t
Your message dated Sun, 31 Oct 2021 12:48:59 +
with message-id
and subject line Bug#996143: fixed in ruby-bunny 2.19.0-1
has caused the Debian Bug report #996143,
regarding ruby-bunny: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
RuntimeError:
to be marked as done.
This means that you c
Control: tag -1 pending
Hello,
Bug #996143 in ruby-bunny 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/ruby-team/ruby-bunny/-/commit/344874a3568d2bb2cedb7f766
Processing control commands:
> tag -1 pending
Bug #996143 [src:ruby-bunny] ruby-bunny: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed: RuntimeError:
Added tag(s) pending.
--
996143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996143
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Processing control commands:
> reopen -1
Bug #996724 {Done: Antonio Terceiro } [src:ruby3.0]
ruby3.0: FTBFS on ppc64el: Segmentation fault
'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
Control: reopen -1
Control: retitle -1 ruby3.0: Segmentation fault on ppc64el when compiled with
gcc-11
Control: severity -1 important
Hi,
On Sat, Oct 30, 2021 at 08:50:10AM +0200, Lucas Nussbaum wrote:
> Hi,
>
> On 30/10/21 at 00:13 +0200, Lucas Nussbaum wrote:
> > Hi,
> >
> > ruby 3.0 3.0.2-
Your message dated Sun, 31 Oct 2021 12:18:48 +
with message-id
and subject line Bug#997749: fixed in mdtraj 1.9.6-2
has caused the Debian Bug report #997749,
regarding mdtraj: FTBFS: sed: no input files
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Processing commands for cont...@bugs.debian.org:
> owner 997564 !
Bug #997564 [src:golang-github-facebookgo-stack]
golang-github-facebookgo-stack: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/facebookgo/stack
returned exit code 1
Owner recorded as A
Processing commands for cont...@bugs.debian.org:
> reopen 996407
Bug #996407 {Done: Nilesh Patra } [src:diamond-aligner,
src:proteinortho] diamond-aligner breaks proteinortho autopkgtest: diamond
failed with code 256
'reopen' may be inappropriate when a bug has been closed with a version;
all fi
Your message dated Sun, 31 Oct 2021 11:47:55 +0100
with message-id <9a4137bcc4e82060384a86d6807ef...@debian.org>
and subject line Re: Bug#997449 py-stringmatching: FTBFS: '! LaTeX Error: File
`tgtermes.sty' not found.'
has caused the Debian Bug report #997449,
regarding py-stringmatching: FTBFS:
Processing commands for cont...@bugs.debian.org:
> fixed 997449 0.4.2+git20201204.6a7fb57-3
Bug #997449 [src:py-stringmatching] py-stringmatching: FTBFS: '! LaTeX Error:
File `tgtermes.sty' not found.'
Marked as fixed in versions py-stringmatching/0.4.2+git20201204.6a7fb57-3.
> thanks
Stopping
Your message dated Sun, 31 Oct 2021 10:48:51 +
with message-id
and subject line Bug#998050: fixed in xygrib 1.2.6.1-1
has caused the Debian Bug report #998050,
regarding xygrib: Sources for xygrib-1.2.6 are actually incluse xygrib-1.2.5
to be marked as done.
This means that you claim that the
This doesn't seem to be a bug in the package. It just declares "vet" as
a cli.Command in build.go.
The error must be elsewhere in the go infrastructure, possibly in the dh
go addon (dh-golang) which generates "go test" for dh_auto_test.
Your message dated Sun, 31 Oct 2021 10:34:29 +
with message-id
and subject line Bug#997276: fixed in vast 2021.05.27-8
has caused the Debian Bug report #997276,
regarding vast: FTBFS: disk_monitor.hpp:32:8: error: ‘optional’ in namespace
‘std’ does not name a template type
to be marked as don
This doesn't seem to be a bug in the package. It just declares "vet" as
a cli.Command in build.go.
The error must be elsewhere in the go infrastructure, possibly in the dh
go addon (dh-golang) which generates "go test" for dh_auto_test.
Your message dated Sun, 31 Oct 2021 11:20:44 +0100
with message-id <7519a9e2d27269bdd139fc10b502d...@debian.org>
and subject line Re: Bug#997532 python-meshio: FTBFS: mv: cannot stat
'paraview_*'
has caused the Debian Bug report #997532,
regarding python-meshio: FTBFS: mv: cannot stat 'paraview_*'
Processing commands for cont...@bugs.debian.org:
> fixed 997532 5.0.2-1
Bug #997532 [src:python-meshio] python-meshio: FTBFS: mv: cannot stat
'paraview_*': No such file or directory
The source 'python-meshio' and version '5.0.2-1' do not appear to match any
binary packages
Marked as fixed in ver
Processing commands for cont...@bugs.debian.org:
> # Why is BTS so damn complicated? :/ I wish we had a simpler system to simply
> mark bugs as done
> # A simple web-service maybe?
> reopen 996407
Bug #996407 {Done: Nilesh Patra } [src:diamond-aligner,
src:proteinortho] diamond-aligner breaks pr
Your message dated Sun, 31 Oct 2021 10:03:30 +
with message-id
and subject line Bug#997028: fixed in python-gsd 2.5.0-1
has caused the Debian Bug report #997028,
regarding python-gsd: FTBFS with sphinx 4.2.0
to be marked as done.
This means that you claim that the problem has been dealt with.
Control: tag -1 upstream fixed-upstream
On Sat, 23 Oct 2021 21:50:07 +0200 Lucas Nussbaum wrote:
> Source: pelican
> Version: 4.0.1+dfsg-1.1
> Severity: serious
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> Exception occur
Processing control commands:
> tag -1 upstream fixed-upstream
Bug #997376 [src:pelican] pelican: FTBFS: AttributeError: 'Sphinx' object has
no attribute 'add_stylesheet'
Added tag(s) fixed-upstream and upstream.
--
997376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997376
Debian Bug Trac
Processing commands for cont...@bugs.debian.org:
> reopen 996407
Bug #996407 {Done: Nilesh Patra } [src:diamond-aligner,
src:proteinortho] diamond-aligner breaks proteinortho autopkgtest: diamond
failed with code 256
'reopen' may be inappropriate when a bug has been closed with a version;
all fi
On 31 oct. 2021 07:56, Itaï BEN YAACOV wrote:
> Package: gourmet
> Version: 1.0.1-2
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
>
> Dear Maintainer,
Hi,
> gourmet fails to run with python3-sqlalchemy v 1.4.23 (in sid).
> Reason : removal of FromClause.count() (w
Processing control commands:
> tags -1 + moreinfo
Bug #996557 [src:linux] linux-image-5.14.0-3-686-pae-unsigned: just about every
sse2 program crashes with a SIGFPE
Added tag(s) moreinfo.
--
996557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996557
Debian Bug Tracking System
Contact ow..
Control: tags -1 + moreinfo
Hi
On Fri, Oct 15, 2021 at 02:52:17PM +0200, Jiri Palecek wrote:
> Package: src:linux
> Version: 5.14.12-1
> Severity: serious
> X-Debbugs-Cc: Jiri Palecek
>
> Dear Maintainer,
>
> when I booted my system with the latest kernel from unstable, many of
> the applicati
Hi.
Than you for your report.
After rebuilding auto-multiple-choice from the same 1.5.1-2 sources in
a sid environment, it passes the autopkgtest.
Maybe this is related to this issue, where it is said that OpenCV 4.x
releases don't guarantee ABI compatibility:
https://github.com/opencv/opencv/iss
Package: gourmet
Version: 1.0.1-2
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
gourmet fails to run with python3-sqlalchemy v 1.4.23 (in sid).
Reason : removal of FromClause.count() (which was already deprecated in v 1.3).
This is an upstream problem, of
95 matches
Mail list logo
