Your message dated Thu, 11 Nov 2021 16:57:18 +0900
with message-id <2021075718.7zjkk6yqfvp5p...@glandium.org>
and subject line Re: Bug#976730: firefox: FTBFS on armhf (unresolved imports
`core::arch::arm::float32x4_t`, `core::arch::arm::int32x4_t`,
`core::arch::arm::vaddq_f32`)
has caused the
Hi Michael,
On 10-11-2021 23:00, Michael Hudson-Doyle wrote:
> If you have yours close at hand, feel free to upload them?
Uploaded to DELAYED/5
Paul
OpenPGP_signature
Description: OpenPGP digital signature
Processing control commands:
> tags -1 pending
Bug #994304 [src:libgpuarray] libgpuarray: Removal of the python3-*-dbg
packages in sid/bookworm
Added tag(s) pending.
--
994304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: python-igraph
Version: 0.9.0-2
Severity: serious
Control: close -1 0.9.6-1
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 unstable for more than 60
Processing control commands:
> close -1 0.9.6-1
Bug #999452 [src:python-igraph] src:python-igraph: fails to migrate to testing
for too long: ftbfs on s390x
Marked as fixed in versions python-igraph/0.9.6-1.
Bug #999452 [src:python-igraph] src:python-igraph: fails to migrate to testing
for too lo
Your message dated Thu, 11 Nov 2021 10:03:56 +
with message-id
and subject line Bug#998633: fixed in shadow 1:4.8.1-2
has caused the Debian Bug report #998633,
regarding shadow: Please switch libsemanage1-dev BD to libsemanage-dev
to be marked as done.
This means that you claim that the probl
Your message dated Thu, 11 Nov 2021 10:03:56 +
with message-id
and subject line Bug#998633: fixed in shadow 1:4.8.1-2
has caused the Debian Bug report #998633,
regarding shadow FTBFS: bd-uninstallable due to conflict on libsepol1-dev
to be marked as done.
This means that you claim that the pr
Control: tags -1 pending
Hi,
it seems a simple rebuild of minimac4 helps to fix this and thus
I'm doing so right now.
Kind regards
Andreas.
--
http://fam-tille.de
Processing control commands:
> tags -1 pending
Bug #996409 [src:libstatgen, src:minimac4] libstatgen breaks minimac4
autopkgtest: Segmentation fault
Added tag(s) pending.
--
996409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996409
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Source: apertium
Control: found -1 apertium/3.7.2-1
Control: affects -1 apertium-br-fr
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of apertium the autopkgtest
Processing control commands:
> found -1 apertium/3.7.2-1
Bug #999456 [src:apertium] apertium breaks apertium-br-fr autopkgtest: gawk:
command not found
Marked as found in versions apertium/3.7.2-1.
> affects -1 apertium-br-fr
Bug #999456 [src:apertium] apertium breaks apertium-br-fr autopkgtest:
Processing commands for cont...@bugs.debian.org:
> block 998509 with 984116
Bug #998509 [src:ruby-rspec-puppet] ruby-rspec-puppet: FTBFS: ERROR: Test
"ruby3.0" failed: cannot load such file -- libfacter.so
998509 was not blocked by any bugs.
998509 was not blocking any bugs.
Added blocking bug(
Processing commands for cont...@bugs.debian.org:
> block 998488 with 984116
Bug #998488 [src:facterdb] facterdb: FTBFS: ERROR: Test "ruby3.0" failed:
cannot load such file -- libfacter.so
998488 was not blocked by any bugs.
998488 was not blocking any bugs.
Added blocking bug(s) of 998488: 9841
Processing commands for cont...@bugs.debian.org:
> block 998481 with 984116
Bug #998481 [src:ruby-puppet-syntax] ruby-puppet-syntax: FTBFS: ERROR: Test
"ruby3.0" failed: cannot load such file -- libfacter.so
998481 was not blocked by any bugs.
998481 was not blocking any bugs.
Added blocking bu
Processing commands for cont...@bugs.debian.org:
> block 998494 with 984116
Bug #998494 [src:ruby-puppetlabs-spec-helper] ruby-puppetlabs-spec-helper:
FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so
998494 was not blocked by any bugs.
998494 was not blocking any bugs.
A
Processing commands for cont...@bugs.debian.org:
> block 998509 with 984116
Bug #998509 [src:ruby-rspec-puppet] ruby-rspec-puppet: FTBFS: ERROR: Test
"ruby3.0" failed: cannot load such file -- libfacter.so
998509 was blocked by: 984116 984082
998509 was not blocking any bugs.
Ignoring request t
Your message dated Thu, 11 Nov 2021 11:03:41 +
with message-id
and subject line Bug#996409: fixed in minimac4 1.0.2-3
has caused the Debian Bug report #996409,
regarding libstatgen breaks minimac4 autopkgtest: Segmentation fault
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> block 998506 with 984116
Bug #998506 [src:ruby-rspec-puppet-facts] ruby-rspec-puppet-facts: FTBFS:
ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so
998506 was not blocked by any bugs.
998506 was not blocking any bugs.
Added blo
Processing control commands:
> tag -1 pending
Bug #998511 [src:ruby-jekyll-data] ruby-jekyll-data: FTBFS: ERROR: Test
"ruby3.0" failed.
Added tag(s) pending.
--
998511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
Control: tag -1 pending
Hello,
Bug #998511 in ruby-jekyll-data 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-jekyll-data/-/commit/4f31d8d1474ba
Your message dated Thu, 11 Nov 2021 11:34:40 +
with message-id
and subject line Bug#998511: fixed in ruby-jekyll-data 1.1.1-2
has caused the Debian Bug report #998511,
regarding ruby-jekyll-data: FTBFS: ERROR: Test "ruby3.0" failed.
to be marked as done.
This means that you claim that the pro
Processing commands for cont...@bugs.debian.org:
> reassign 998512 ruby-commonmarker 0.21.0-2
Bug #998512 [src:ruby-jekyll-commonmark] ruby-jekyll-commonmark: FTBFS: ERROR:
Test "ruby3.0" failed: Failure/Error:
Jekyll::External.require_with_graceful_fail "commonmarker"
Bug reassigned from packag
Your message dated Thu, 11 Nov 2021 12:03:32 +
with message-id
and subject line Bug#998512: fixed in ruby-commonmarker 0.21.0-3
has caused the Debian Bug report #998512,
regarding ruby-jekyll-commonmark: FTBFS: ERROR: Test "ruby3.0" failed:
Failure/Error: Jekyll::External.require_with_gracefu
I narrowed down the freeze to the cubeb pulse code (part of the audio library
firefox uses), and I found that it was actually fixed almost a month ago:
https://github.com/mozilla/cubeb-pulse-rs/pull/72
It's already been merged into firefox on-track for v95:
https://bugzilla.mozilla.org/show_bug.cg
Package: python3-typeshed
Version: 0.0~git20211009.0142ea8-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bo
Your message dated Thu, 11 Nov 2021 12:18:29 +
with message-id
and subject line Bug#999456: fixed in apertium 3.7.2-2
has caused the Debian Bug report #999456,
regarding apertium breaks apertium-br-fr autopkgtest: gawk: command not found
to be marked as done.
This means that you claim that th
Processing commands for cont...@bugs.debian.org:
> forwarded 998108 https://github.com/mozilla/cubeb-pulse-rs/pull/72
Bug #998108 [firefox] firefox freezes shortly after start
Bug #998824 [firefox] firefox hangs randomly
Set Bug forwarded-to-address to
'https://github.com/mozilla/cubeb-pulse-rs/p
Processing commands for cont...@bugs.debian.org:
> forcemerge 998108 998824
Bug #998108 [firefox] firefox freezes shortly after start
Bug #998824 [firefox] firefox hangs randomly
Severity set to 'grave' from 'important'
Marked as found in versions firefox/93.0-1.
Merged 998108 998824
> thanks
Stop
Your message dated Thu, 11 Nov 2021 12:50:45 +
with message-id
and subject line Bug#996135: fixed in ruby-benchmark-memory 0.1.2-3
has caused the Debian Bug report #996135,
regarding ruby-benchmark-memory: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed: ArgumentError:
to be marked as d
Your message dated Thu, 11 Nov 2021 13:34:10 +
with message-id
and subject line Bug#997173: fixed in procinfo 1:2.0.304-6
has caused the Debian Bug report #997173,
regarding procinfo: FTBFS: procinfo.cpp:214:22: error: format not a string
literal and no format arguments [-Werror=format-securi
Your message dated Thu, 11 Nov 2021 15:32:34 +0100
with message-id <48e91477-8fbe-37ea-494c-b6f8e381b...@debian.org>
and subject line Re: trinityrnaseq: FTBFS: /bin/sh: 1: cd: can't cd to htslib
has caused the Debian Bug report #997702,
regarding trinityrnaseq: FTBFS: /bin/sh: 1: cd: can't cd to ht
Processing control commands:
> tag -1 pending
Bug #997616 [src:python-anyjson] python-anyjson: FTBFS: error in anyjson setup
command: use_2to3 is invalid.
Added tag(s) pending.
--
997616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997616
Debian Bug Tracking System
Contact ow...@bugs.debi
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:
https://salsa.debian.org/python-team/packages/sqlalchemy/-/commit/2e6b9b0c871247
Processing control commands:
> tag -1 pending
Bug #997484 [python3-sqlalchemy] python3-sqlalchemy: Undeclared dependency on
python3-greenlet!=0.4.17
Ignoring request to alter tags of bug #997484 to the same tags previously set
--
997484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997484
Control: tag -1 pending
Hello,
Bug #997616 in python-anyjson 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-anyjson/-/commit/7e5b95
Your message dated Thu, 11 Nov 2021 14:48:30 +
with message-id
and subject line Bug#997616: fixed in python-anyjson 0.3.3-3
has caused the Debian Bug report #997616,
regarding python-anyjson: FTBFS: error in anyjson setup command: use_2to3 is
invalid.
to be marked as done.
This means that yo
Processing control commands:
> reassign -1 imagemagick-6.q16 8:6.9.11.60+dfsg-1.3
Bug #993029 [ranger] ranger: No preview for mp(e)g files (mime-type:
image/x-tga) and fs saturation with .pam files
Bug reassigned from package 'ranger' to 'imagemagick-6.q16'.
No longer marked as found in versions
Control: reassign -1 imagemagick-6.q16 8:6.9.11.60+dfsg-1.3
Control: severity -1 important
Hi,
This bug does not belong to ranger. ranger called `identify` from
imagemagick on
the given video, and identify ends up creating a bulky magick-*.pam file
under /tmp
and exiting with error.
I can reprod
Your message dated Thu, 11 Nov 2021 15:19:43 +
with message-id
and subject line Bug#997484: fixed in sqlalchemy 1.4.23+ds1-3
has caused the Debian Bug report #997484,
regarding python3-sqlalchemy: Undeclared dependency on python3-greenlet!=0.4.17
to be marked as done.
This means that you clai
On Thu, Nov 11, 2021 at 12:49:32AM +0100, Diederik de Haas wrote:
> I'm responding to this bug as commenting out the pid_file line was the
> solution
> for me too, but my 'symptoms' are (a bit) different.
...
> nov 10 23:30:21 soundserver systemd[1]: Failed to start Music Player Daemon.
>
> I f
Your message dated Thu, 11 Nov 2021 15:49:01 +
with message-id
and subject line Bug#887834: fixed in mpd 0.23.4-1
has caused the Debian Bug report #887834,
regarding mpd installation fails, cannot open /var/lib/mpd/tag_cache,
/run/mpd/pid
to be marked as done.
This means that you claim that
Your message dated Thu, 11 Nov 2021 15:48:52 +
with message-id
and subject line Bug#984239: fixed in mir 1.8.0+dfsg1-19
has caused the Debian Bug report #984239,
regarding mir: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
On Thu, 2021-11-11 at 23:06 +1100, 小太 wrote:
> So either the change needs to be backported to v94
It seems Mike has already been active in that bug (and even found it
himself a ~month ago ^^) and indicated he'll backport it (AFAIU).
Which I hope really happens... I know there is no official secu
Your message dated Thu, 11 Nov 2021 16:33:32 +
with message-id
and subject line Bug#984118: fixed in farmhash 0~git20190513.0d859a8-2
has caused the Debian Bug report #984118,
regarding farmhash: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 11 Nov 2021 16:48:47 +
with message-id
and subject line Bug#974778: fixed in llvmlite 0.37.0-1
has caused the Debian Bug report #974778,
regarding llvmlite: Please upgrade to llvm-toolchain-11
to be marked as done.
This means that you claim that the problem has been de
Your message dated Thu, 11 Nov 2021 16:48:47 +
with message-id
and subject line Bug#974778: fixed in llvmlite 0.37.0-1
has caused the Debian Bug report #974778,
regarding llvmlite: Please upgrade to llvm-toolchain-11
to be marked as done.
This means that you claim that the problem has been de
Your message dated Thu, 11 Nov 2021 16:48:47 +
with message-id
and subject line Bug#974778: fixed in llvmlite 0.37.0-1
has caused the Debian Bug report #974778,
regarding llvmlite: Please upgrade to llvm-toolchain-11
to be marked as done.
This means that you claim that the problem has been de
Control: tag -1 pending
Hello,
Bug #998886 in node-slice-ansi 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/js-team/node-slice-ansi/-/commit/a42957aa716f666f9
Processing control commands:
> tag -1 pending
Bug #998886 [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Bug #998911 [node-string-width,node-slice-ansi] node-string-width: file
conflict with node-slice-ansi
Added tag(
Le 10/11/2021 à 16:06, Mattia Rizzolo a écrit :
> yep, that, sorry. I mean it's missing a Replaces.
Hi,
I added this field, however node-string-witdh 4.2.3+~3.0.0+~9.2.2-1 no
more exist anywhere, so this bug no more exist too (previous versions
didn't install conflict files)
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:ubertooth
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
S
Your message dated Thu, 11 Nov 2021 17:21:00 +
with message-id
and subject line Bug#998886: fixed in node-slice-ansi 5.0.0+~4.0.0-4
has caused the Debian Bug report #998886,
regarding node-string-width: file conflict with node-slice-ansi
to be marked as done.
This means that you claim that th
Your message dated Thu, 11 Nov 2021 17:21:00 +
with message-id
and subject line Bug#998886: fixed in node-slice-ansi 5.0.0+~4.0.0-4
has caused the Debian Bug report #998886,
regarding node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
to be marked as done
On Thu, 11 Nov 2021 23:06:44 +1100 =?UTF-8?B?4oCN5bCP5aSq?=
wrote:
> So either the change needs to be backported to v94, or we'll just have to wait
> until v95 (or compile the browser ourselves)
I was a bit adventurous and tried doing a binary patch on the current debian
version (94.0-1), and got
Your message dated Thu, 11 Nov 2021 17:49:54 +
with message-id
and subject line Bug#999461: fixed in typeshed 0.0~git20211009.0142ea8-3
has caused the Debian Bug report #999461,
regarding python3-typeshed: ships files already provided by python3-types-toml,
python3-types-typed-ast
to be marke
Source: mrgingham
Version: 1.20-1
Severity: serious
Tags: sid bookworm
See
https://buildd.debian.org/status/package.php?p=mrgingham
the symbols file is not ready for the release architectures.
Your message dated Thu, 11 Nov 2021 19:06:26 +
with message-id
and subject line Bug#991066: fixed in vlfeat 0.9.21+dfsg0-7
has caused the Debian Bug report #991066,
regarding vlfeat FTBFS with imagemagick with the #987504 change
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 11 Nov 2021 19:05:47 +
with message-id
and subject line Bug#996404: fixed in ruby-sassc-rails 2.1.2-6
has caused the Debian Bug report #996404,
regarding ruby-sassc-rails: FTBFS: ERROR: Test "ruby3.0" failed.
to be marked as done.
This means that you claim that the pro
Your message dated Thu, 11 Nov 2021 19:33:46 +
with message-id
and subject line Bug#997518: fixed in magit-forge-el 0.3.0-2
has caused the Debian Bug report #997518,
regarding magit-forge-el: FTBFS: make[2]: *** No rule to make target
'/usr/share/emacs/site-lisp/elpa-src/closql-1.0.6'. Stop.
Processing commands for cont...@bugs.debian.org:
> tags 997185 + confirmed
Bug #997185 [src:nfswatch] nfswatch: FTBFS: screen.c:227:57: error: format not
a string literal and no format arguments [-Werror=format-security]
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact m
Processing commands for cont...@bugs.debian.org:
> forcemerge 998512 998505
Bug #998512 {Done: Daniel Leidert } [ruby-commonmarker]
ruby-jekyll-commonmark: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error:
Jekyll::External.require_with_graceful_fail "commonmarker"
Unable to merge bugs because:
Processing commands for cont...@bugs.debian.org:
> forcemerge 998512 998492
Bug #998512 {Done: Daniel Leidert } [ruby-commonmarker]
ruby-jekyll-commonmark: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error:
Jekyll::External.require_with_graceful_fail "commonmarker"
Unable to merge bugs because:
Processing commands for cont...@bugs.debian.org:
> forcemerge 998512 998491
Bug #998512 {Done: Daniel Leidert } [ruby-commonmarker]
ruby-jekyll-commonmark: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error:
Jekyll::External.require_with_graceful_fail "commonmarker"
Unable to merge bugs because:
Processing commands for cont...@bugs.debian.org:
> reassign 998505 ruby-commonmarker 0.21.0-2
Bug #998505 [src:ruby-task-list] ruby-task-list: FTBFS: ERROR: Test "ruby3.0"
failed: LoadError: cannot load such file -- commonmarker
Bug reassigned from package 'src:ruby-task-list' to 'ruby-commonmark
Your message dated Thu, 11 Nov 2021 20:36:56 +
with message-id
and subject line Bug#996372: fixed in ruby-roxml 4.2.0-1
has caused the Debian Bug report #996372,
regarding ruby-roxml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
NoMethodError:
to be marked as done.
This means that
Your message dated Thu, 11 Nov 2021 21:03:28 +
with message-id
and subject line Bug#997962: fixed in bf-utf 0.08+nmu2
has caused the Debian Bug report #997962,
regarding src:bf-utf: fails to migrate to testing for too long: uploader built
arch:all binaries
to be marked as done.
This means th
Your message dated Thu, 11 Nov 2021 21:03:42 +
with message-id
and subject line Bug#997900: fixed in golang-github-go-xorm-builder 0.3.3-3.1
has caused the Debian Bug report #997900,
regarding src:golang-github-go-xorm-builder: fails to migrate to testing for
too long: uploader built arch:all
Hi,
El dj. 11 de 11 de 2021 a les 22:07 +0100, en/na Jordi Mallach va
escriure:
> Hi Salvatore,
>
> El dv. 04 de 06 de 2021 a les 23:07 +0200, en/na Salvatore Bonaccorso
> va escriure:
> > If you fix the vulnerability please also make sure to include the
> > CVE (Common Vulnerabilities & Exposure
Hi Salvatore,
El dv. 04 de 06 de 2021 a les 23:07 +0200, en/na Salvatore Bonaccorso
va escriure:
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>
> For further information see:
>
> [0] https://security-tr
On Nov 11, 小太 wrote:
> If you open /usr/lib/firefox/libxul.so in a hex editor and go to file offset
> 0x46a4703, you can perform a find and replace with the below hex strings:
> find:498B5C2408904889DFFF157FBD9703EBF5
> replace: 4D8B6C2408904C89EFFF157FBD9703EBDA
Great work! Quick one liner:
Your message dated Thu, 11 Nov 2021 21:21:14 +
with message-id
and subject line Bug#997963: fixed in golang-github-ogier-pflag
0.0~git20160129.0.45c278a-5.1
has caused the Debian Bug report #997963,
regarding src:golang-github-ogier-pflag: fails to migrate to testing for too
long: uploader b
Your message dated Thu, 11 Nov 2021 21:21:00 +
with message-id
and subject line Bug#998108: fixed in firefox 94.0-2
has caused the Debian Bug report #998108,
regarding firefox freezes shortly after start
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 11 Nov 2021 21:21:00 +
with message-id
and subject line Bug#998108: fixed in firefox 94.0-2
has caused the Debian Bug report #998108,
regarding firefox hangs randomly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not t
Your message dated Thu, 11 Nov 2021 21:49:00 +
with message-id
and subject line Bug#997965: fixed in golang-github-siddontang-go-snappy
0.0~git20140704.0.d8f7bb8-6.1
has caused the Debian Bug report #997965,
regarding src:golang-github-siddontang-go-snappy: fails to migrate to testing
for to
Source: zycore-c
Version: 1.0.0-2
Severity: serious
Hi,
The issue that seemed to be addressed by a patch included in the latest
revision was not fixed;
the package still FTBFS at least on mips64el:
/usr/bin/cc -DZYCORE_EXPORTS -DZycore_EXPORTS -D_CRT_SECURE_NO_WARNINGS -D_GNU_SOURCE
-I/<>/inc
Processing commands for cont...@bugs.debian.org:
> reassign 998497 gem2deb-test-runner 1.6
Bug #998497 [src:ruby-voight-kampff] ruby-voight-kampff: FTBFS: ERROR: Test
"ruby3.0" failed: cannot load such file -- combustion
Bug reassigned from package 'src:ruby-voight-kampff' to 'gem2deb-test-runn
Processing commands for cont...@bugs.debian.org:
> reassign 998480 ruby-nokogiri 1.11.7+dfsg-3+b1
Bug #998480 [src:ruby-fog-aws] ruby-fog-aws: FTBFS: ERROR: Test "ruby3.0"
failed: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in
`require': cannot load such file -- nokogiri (Lo
Processing commands for cont...@bugs.debian.org:
> reassign 998480 ruby-fog-aws 3.12.0-1
Bug #998480 [ruby-nokogiri] Please rebuild for Ruby 3.0 to fix FTBFS of
depending packages
Bug reassigned from package 'ruby-nokogiri' to 'ruby-fog-aws'.
No longer marked as found in versions ruby-nokogiri/1.
Your message dated Thu, 11 Nov 2021 19:00:52 -0500
with message-id
and subject line Re: php8.0: should not be released with bullseye?
has caused the Debian Bug report #982177,
regarding php8.0: should not be released with bullseye?
to be marked as done.
This means that you claim that the problem
Processing control commands:
> tag -1 pending
Bug #998480 [ruby-fog-aws] FTBFS: ERROR: Test ruby3.0 failed:
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require':
cannot load such file -- nokogiri (LoadError)
Added tag(s) pending.
--
998480: https://bugs.debian.org/cgi-
Control: tag -1 pending
Hello,
Bug #998480 in ruby-fog-aws 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-fog-aws/-/commit/9aab25c7deb95e71661df
Processing commands for cont...@bugs.debian.org:
> tags 954648 + ftbfs
Bug #954648 [rivet] FTBFS with Boost 1.71
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
954648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954648
Debian Bug Trackin
Your message dated Fri, 12 Nov 2021 00:34:20 +
with message-id
and subject line Bug#998480: fixed in ruby-fog-aws 3.12.0-2
has caused the Debian Bug report #998480,
regarding FTBFS: ERROR: Test ruby3.0 failed:
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require':
can
> (Immediate uploading _not_ recommended: it still needs a workaround for
> #997908.)
any idea when that will be addressed? i would like to remove numpy-dbg
sooner rather than later -- thanks!
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTos
Control: tag -1 pending
Hello,
Bug #998497 in gem2deb 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/gem2deb/-/commit/a970281abb6b3ac3abe44f3222cca6b
Processing control commands:
> tag -1 pending
Bug #998497 [gem2deb-test-runner] gem2deb-test-runner: Remove Gemfile.lock
files before running the tests
Added tag(s) pending.
--
998497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998497
Debian Bug Tracking System
Contact ow...@bugs.debian.
Your message dated Fri, 12 Nov 2021 03:18:56 +
with message-id
and subject line Bug#997482: fixed in sublime-music 0.11.16-1
has caused the Debian Bug report #997482,
regarding sublime-music: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code
Package: rust-tokio-signal
Version: 0.2.7-2
Severity: serious
rust-tokio-signal (build-)depends on version 0.1 of rust-futures. Upstream
seems to
have abandoned the project, there was an alpha release supporting futures 0.2,
but
the code appears to have been removed from the tokio git repositor
In addition to the (build-)dependency on an old version of rust-crossbeam-queue,
rust-tokio-process (build-)depends on version 0.1 of rust-futures. Upstream
seems to
have abandoned the crate, there was an alpha release supporting futures 0.2, but
the code appears to have been removed from the tok
89 matches
Mail list logo
