Control: tag -1 pending
Hello,
Bug #1011863 in guix 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 #1011863 [src:guix] guix: FTBFS in bullseye because of expired certificates
used in tests
Added tag(s) pending.
--
1011863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Your message dated Sat, 24 Dec 2022 01:45:24 +
with message-id
and subject line Bug#1026816: fixed in speedcrunch 0.12.0-6
has caused the Debian Bug report #1026816,
regarding speedcrunch: FTBFS: KeyError: 'extra-doc-strings'
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 24 Dec 2022 00:39:09 +
with message-id
and subject line Bug#1026472: fixed in python-blessed 1.19.1-1
has caused the Debian Bug report #1026472,
regarding python-blessed: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.11 3.10"
Your message dated Sat, 24 Dec 2022 00:34:44 +
with message-id
and subject line Bug#1026855: fixed in google-auto-service-java 1.0.1-1
has caused the Debian Bug report #1026855,
regarding libgoogle-auto-service-java: ships
Processing control commands:
> tag -1 pending
Bug #1026472 [src:python-blessed] python-blessed: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit
code 13
Added tag(s) pending.
--
1026472:
Control: tag -1 pending
Hello,
Bug #1026472 in python-blessed 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:
On Tue, Dec 20, 2022 at 06:32:07PM +0100, Lucas Nussbaum wrote:
> Source: apache-directory-api
> Version: 1.0.0-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220 ftbfs-bookworm
The FTBFS is due to the recent upload of mina2
Your message dated Fri, 23 Dec 2022 23:05:10 +
with message-id
and subject line Bug#1026854: fixed in google-auto-common-java 1.1.2-1
has caused the Debian Bug report #1026854,
regarding libgoogle-auto-common-java: ships
Your message dated Fri, 23 Dec 2022 22:34:11 +
with message-id
and subject line Bug#1026659: fixed in aeonbits-owner 1.0.12+ds-3
has caused the Debian Bug report #1026659,
regarding aeonbits-owner: FTBFS: make: *** [debian/rules:6: binary] Error 25
to be marked as done.
This means that you
Your message dated Fri, 23 Dec 2022 23:04:39 +0100
with message-id
and subject line Re: xournal: FTBFS: Makefile:263: *** missing separator. Stop.
has caused the Debian Bug report #1026110,
regarding xournal: FTBFS: Makefile:263: *** missing separator. Stop.
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> forcemerge 1019634 1026565 1026601 1026544 1026560 1026578 1026564 1026557
> 1026550 1026589 1026629
Bug #1019634 [src:jekyll] jekyll requires liquid gem v4, whereas the archive
has 5.4
Bug #1026601 [src:jekyll] ruby-jekyll-feed: FTBFS: ERROR:
Processing commands for cont...@bugs.debian.org:
> reassign 1026629 src:jekyll
Bug #1026629 [src:ruby-jekyll-commonmark] ruby-jekyll-commonmark: FTBFS: ERROR:
Test "ruby3.1" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in
activate_dependencies': Could
Processing commands for cont...@bugs.debian.org:
> reassign 1026589 src:jekyll
Bug #1026589 [src:jekyll-theme-minima] jekyll-theme-minima: FTBFS: ERROR: Test
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in
`rescue in block in activate_dependencies': Could not find
Processing commands for cont...@bugs.debian.org:
> reassign 1026550 src:jekyll
Bug #1026550 [src:ruby-jekyll-last-modified-at] ruby-jekyll-last-modified-at:
FTBFS: ERROR: Test "ruby3.1" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in
Processing commands for cont...@bugs.debian.org:
> reassign 1026578 src:jekyll
Bug #1026578 [src:ruby-jekyll-include-cache] ruby-jekyll-include-cache: FTBFS:
ERROR: Test "ruby3.1" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in
activate_dependencies':
Processing commands for cont...@bugs.debian.org:
> reassign 1026564 src:jekyll
Bug #1026564 [src:ruby-jekyll-polyglot] ruby-jekyll-polyglot: FTBFS: ERROR:
Test "ruby3.1" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in
activate_dependencies': Could not
Processing commands for cont...@bugs.debian.org:
> reassign 1026557 src:jekyll
Bug #1026557 [src:ruby-jekyll-toc] ruby-jekyll-toc: FTBFS: ERROR: Test
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in
`rescue in block in activate_dependencies': Could not find 'liquid'
Processing commands for cont...@bugs.debian.org:
> reassign 1026565 src:jekyll
Bug #1026565 [src:ruby-jekyll-seo-tag] ruby-jekyll-seo-tag: FTBFS: ERROR: Test
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in
`rescue in block in activate_dependencies': Could not find
Processing commands for cont...@bugs.debian.org:
> reassign 1026560 src:jekyll
Bug #1026560 [src:ruby-jekyll-asciidoc] ruby-jekyll-asciidoc: FTBFS: ERROR:
Test "ruby3.1" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in
activate_dependencies': Could not
Processing commands for cont...@bugs.debian.org:
> reassign 1026601 src:jekyll
Bug #1026601 [src:ruby-jekyll-feed] ruby-jekyll-feed: FTBFS: ERROR: Test
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in
`rescue in block in activate_dependencies': Could not find
Processing commands for cont...@bugs.debian.org:
> reassign 1026544 src:jekyll
Bug #1026544 [src:ruby-jekyll-data] ruby-jekyll-data: FTBFS: ERROR: Test
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in
`rescue in block in activate_dependencies': Could not find
Processing commands for cont...@bugs.debian.org:
> reassign 1019634 src:jekyll
Bug #1019634 [jekyll] jekyll requires liquid gem v4, whereas the archive has 5.4
Bug reassigned from package 'jekyll' to 'src:jekyll'.
Ignoring request to alter found versions of bug #1019634 to the same values
Your message dated Fri, 23 Dec 2022 20:55:01 +
with message-id
and subject line Bug#1019673: fixed in ruby-uniform-notifier 1.16.0-1
has caused the Debian Bug report #1019673,
regarding ruby-uniform-notifier: FTBFS with ruby3.1: ERROR: Test "ruby3.1"
failed: Failure/Error: require
Processing commands for cont...@bugs.debian.org:
> affects 1019634 ruby-jekyll-asciidoc ruby-jekyll-commonmark ruby-jekyll-data
> ruby-jekyll-feed ruby-jekyll-include-cache ruby-jekyll-last-modified-at
> ruby-jekyll-polyglot ruby-jekyll-remote-theme ruby-jekyll-seo-tag
> ruby-jekyll-toc
Bug
Package: arcanist
Version: 0~git20200925-1
Severity: grave
If one has one or more commits in /some/repo one can create a
Phabricator diff by running `arc diff $oldver`. If there are are
untracked files in the directory the arcanist client gives the message:
Processing commands for cont...@bugs.debian.org:
> forcemerge 1019634 1026565 1026601 1026544 1026560 1026578 1026564 1026557
> 1026550 1026589 1026629
Bug #1019634 [jekyll] jekyll requires liquid gem v4, whereas the archive has 5.4
Unable to merge bugs because:
package of #1026565 is
Processing commands for cont...@bugs.debian.org:
> reassign 1019634 jekyll
Bug #1019634 [src:ruby-jekyll-remote-theme] ruby-jekyll-remote-theme: FTBFS:
ERROR: Test "ruby3.0" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in
activate_dependencies': Could
Processing commands for cont...@bugs.debian.org:
> retitle 1019634 jekyll requires liquid gem v4, whereas the archive has 5.4
Bug #1019634 [jekyll] ruby-jekyll-remote-theme: FTBFS: ERROR: Test "ruby3.0"
failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in
block in
Source: hypre
Version: 2.18.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout
Control: found -1 2.25.0-2 2.26.0-2 2.22.1-3
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails regularly on
armhf. What's worse, it regularly fails because it seems
Package: calamares-settings-mobian
Version: 0.2.6
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.
There are three files in conflict:
Your message dated Fri, 23 Dec 2022 19:49:50 +
with message-id
and subject line Bug#1020970: fixed in evil-el 1.14.2-1
has caused the Debian Bug report #1020970,
regarding emacs-bind-map: FTBFS: Errors while processing: elpa-evil
sbuild-build-depends-main-dummy
to be marked as done.
This
Your message dated Fri, 23 Dec 2022 19:49:50 +
with message-id
and subject line Bug#1020970: fixed in evil-el 1.14.2-1
has caused the Debian Bug report #1020970,
regarding elpa-evil: emacs 28.1 upgrade fails with byte compiling elpa-evil
to be marked as done.
This means that you claim that
Your message dated Fri, 23 Dec 2022 19:49:50 +
with message-id
and subject line Bug#1020970: fixed in evil-el 1.14.2-1
has caused the Debian Bug report #1020970,
regarding elpa-evil: fails to install: wrong-number-of-arguments
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 23 Dec 2022 19:17:23 +
with message-id
and subject line Fixed in 1.13.0
has caused the Debian Bug report #1004813,
regarding retroarch: FTBFS with ffmpeg 5.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Processing control commands:
> severity -1 serious
Bug #1025490 [src:fastnetmon] fastnetmon: FTBFS with grpc 1.51+
Severity set to 'serious' from 'important'
--
1025490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> severity -1 serious
Bug #1025530 [src:llvm-toolchain-15] llvm-toolchain-15: FTBFS with grpc 1.51+
Severity set to 'serious' from 'important'
--
1025530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025530
Debian Bug Tracking System
Contact
Processing control commands:
> severity -1 serious
Bug #1025529 [src:llvm-toolchain-14] llvm-toolchain-14: FTBFS with grpc 1.51+
Severity set to 'serious' from 'important'
--
1025529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025529
Debian Bug Tracking System
Contact
Processing control commands:
> severity -1 serious
Bug #1025491 [src:open-vm-tools] open-vm-tools: FTBFS with grpc 1.51+
Severity set to 'serious' from 'important'
--
1025491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Hi Lajos,
On 23-12-2022 00:58, Lajos Veres wrote:
How can I test my changes on the below infrastructure?
Once your package is uploaded to the archive, the test will be run
automatically. If you have a salsa account, you can also trigger tests
yourself.
Does https://mentors.debian.net/
Processing control commands:
> close -1 2.6.0-1
Bug #1026909 [src:cvise] src:cvise: fails to migrate to testing for too long:
FTBFS on mipsel
Marked as fixed in versions cvise/2.6.0-1.
Bug #1026909 [src:cvise] src:cvise: fails to migrate to testing for too long:
FTBFS on mipsel
Marked Bug as
Source: cvise
Version: 2.5.0-1
Severity: serious
Control: close -1 2.6.0-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 days
Your message dated Fri, 23 Dec 2022 18:34:56 +
with message-id
and subject line Bug#1026582: fixed in python-apsw 3.40.0.0-2
has caused the Debian Bug report #1026582,
regarding python-apsw: FTBFS: ModuleNotFoundError: No module named 'setuptools'
to be marked as done.
This means that you
Your message dated Fri, 23 Dec 2022 18:22:03 +
with message-id
and subject line Bug#1026897: fixed in ruby-tilt 2.0.11-2
has caused the Debian Bug report #1026897,
regarding ruby-tilt: FTBFS: ERROR: Test "ruby3.1" failed.
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 23 Dec 2022 18:20:40 +
with message-id
and subject line Bug#1026869: fixed in lua-nvim 0.2.4-1-1
has caused the Debian Bug report #1026869,
regarding lua-nvim: flaky autopkgtest: times out on ppc64el and s390x
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #1026897 [src:ruby-tilt] ruby-tilt: FTBFS: ERROR: Test "ruby3.1" failed.
Added tag(s) pending.
--
1026897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1026897 in ruby-tilt 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 Fri, 23 Dec 2022 10:52:01 -0700
with message-id <871qoq9fem@melete.silentflame.com>
and subject line Re: Bug#1020851: elpa-ement: fails to install along emacs
has caused the Debian Bug report #1020851,
regarding elpa-ement: fails to install along emacs
to be marked as done.
Your message dated Fri, 23 Dec 2022 17:20:56 +
with message-id
and subject line Bug#984274: fixed in openclonk 8.1-3
has caused the Debian Bug report #984274,
regarding openclonk: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-webpack-rails: FTBFS in bookworm (missing build-depends on
tzdata)
to be marked as done.
This means that you
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-webpacker: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-voight-kampff: FTBFS in bookworm (missing build-depends on
tzdata)
to be marked as done.
This means that you
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-sprockets-rails: FTBFS in bookworm (missing build-depends on
tzdata)
to be marked as done.
This means that you
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-sassc-rails: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-rails-controller-testing: FTBFS in bookworm (missing
build-depends on tzdata)
to be marked as done.
This means
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-omniauth-rails-csrf-protection: FTBFS in bookworm (missing
build-depends on tzdata)
to be marked as done.
This
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-pry-rails: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-joiner: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim that
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-invisible-captcha: FTBFS in bookworm (missing build-depends on
tzdata)
to be marked as done.
This means that
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-factory-bot-rails: FTBFS in bookworm (missing build-depends on
tzdata)
to be marked as done.
This means that
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-haml: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim that
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-globalid: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-browser: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-enumerize: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-combustion: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-coffee-rails: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-arbre: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim that
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-ahoy-email: FTBFS in bookworm (missing build-depends on tzdata)
to be marked as done.
This means that you claim
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-active-model-serializers: FTBFS in bookworm (missing
build-depends on tzdata)
to be marked as done.
This means
Your message dated Fri, 23 Dec 2022 17:21:13 +
with message-id
and subject line Bug#1026178: fixed in ruby-tzinfo 2.0.5-1
has caused the Debian Bug report #1026178,
regarding ruby-tzinfo: missing dependency on tzdata
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> tags 1026855 + pending
Bug #1026855 [libgoogle-auto-service-java] libgoogle-auto-service-java: ships
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
Added tag(s) pending.
> thanks
Stopping processing here.
Control: tag -1 pending
Hello,
Bug #1026510 in openjfx 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 #1026510 [src:openjfx] openjfx: FTBFS:
ReadOnlyJavaBeanObjectPropertyBuilder.java:58: error: invalid use of @param
Added tag(s) pending.
--
1026510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026510
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hi Andreas and thanks for the report!
On 12/22/22 11:29, Andreas Beckmann wrote:
libgoogle-auto-common-java ships two dubious files that should probably
not be in the package at all:
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
Processing control commands:
> tag -1 pending
Bug #1026854 [libgoogle-auto-common-java] libgoogle-auto-common-java: ships
/usr/share/maven-repo/build-only/build-only/NO_VERSION/build-only-NO_VERSION.pom
Added tag(s) pending.
--
1026854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026854
On Fri, 2022-12-23 at 10:56 -0500, M. Zhou wrote:
> Control: tags -1 +moreinfo
>
> I'm confused. How did you manage to build the package from source
> using c65b3e662b7b08920172b710419d7a06b660be59 on salsa?
>
> I did not upload it because I can never successfully build it
> from source.
>
It
Processing commands for cont...@bugs.debian.org:
> forwarded 1024219
> https://github.com/TheTumultuousUnicornOfDarkness/CPU-X/commit/2765e68dc4650b7306255e0c10056508d5ab44f8
Bug #1024219 [src:cpu-x] cpu-x: FTBFS with libproc2
Set Bug forwarded-to-address to
Processing control commands:
> tag -1 pending
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on tzdata
Bug #1026179 [ruby-tzinfo] ruby-active-model-serializers: FTBFS in bookworm
(missing build-depends on tzdata)
Bug #1026180 [ruby-tzinfo] ruby-ahoy-email: FTBFS in bookworm (missing
Control: tag -1 pending
Hello,
Bug #1026178 in ruby-tzinfo 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 commands for cont...@bugs.debian.org:
> reassign 1026179 ruby-tzinfo
Bug #1026179 [src:ruby-active-model-serializers] ruby-active-model-serializers:
FTBFS in bookworm (missing build-depends on tzdata)
Bug reassigned from package 'src:ruby-active-model-serializers' to
'ruby-tzinfo'.
Processing commands for cont...@bugs.debian.org:
> forcemerge 1026178 1026179 1026180 1026181 1026182 1026183 1026184 1026185
> 1026186 1026187 1026188 1026189 1026190 1026191 1026192 1026193 1026194
> 1026195 1026196 1026197 1026198
Bug #1026178 [ruby-tzinfo] ruby-tzinfo: missing dependency on
Processing commands for cont...@bugs.debian.org:
> retitle 1026178 ruby-tzinfo: missing dependency on tzdata
Bug #1026178 [src:redmine] redmine: FTBFS in bookworm (missing build-depends on
tzdata)
Changed Bug title to 'ruby-tzinfo: missing dependency on tzdata' from 'redmine:
FTBFS in bookworm
On Tue, 20 Dec 2022 20:27:02 +0100, gregor herrmann wrote:
> > > # Failed test (t/cz-03zlib-v1.t at line 713)
> > > # got: 1
> > > # expected: -3
> > > # Looks like you failed 1 test of 471.
> > > t/cz-03zlib-v1.t
> > > 1..471
>
> I think this has to do with
Control: tags -1 +moreinfo
I'm confused. How did you manage to build the package from source
using c65b3e662b7b08920172b710419d7a06b660be59 on salsa?
I did not upload it because I can never successfully build it
from source.
-
Processing control commands:
> tags -1 +moreinfo
Bug #1024795 [python3-llvmlite] python3-llvmlite: Depends from non-existing
packages libllvm11 and llvm-11
Added tag(s) moreinfo.
--
1024795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024795
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> tags 979610 - bullseye
Bug #979610 {Done: Gregor Jasny } [src:v4l-utils]
v4l-utils: vendors ancient version of libbpf
Removed tag(s) bullseye.
> tags 1026853 + sid bookworm
Bug #1026853 [rust-svgdom] rust-svgdom: (build-)depends on old version
Your message dated Fri, 23 Dec 2022 15:43:42 +
with message-id
and subject line Bug#1025096: fixed in nanoc 4.12.14-1
has caused the Debian Bug report #1025096,
regarding nanoc: FTBFS in bullseye, and will also FTBFS in bookworm next year
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> tags 984274 + patch
Bug #984274 [src:openclonk] openclonk: ftbfs with GCC-11
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984274
Source: ruby-tilt
Version: 2.0.11-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
After updating ruby-haml to 6.1.1, ruby-tilt fails to build with a test
failure.
Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
>
>
Source: ruby-html2haml
Version: 2.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block
Your message dated Fri, 23 Dec 2022 15:45:59 +0100
with message-id
and subject line Re: Bug#1026891: mpv fails to start: undefined symbol:
ass_track_set_feature
has caused the Debian Bug report #1026891,
regarding mpv fails to start: undefined symbol: ass_track_set_feature
to be marked as done.
Your message dated Fri, 23 Dec 2022 14:45:31 +
with message-id
and subject line Bug#1026577: fixed in typer 0.7.0-1
has caused the Debian Bug report #1026577,
regarding typer: FTBFS: pytest-3: error: unrecognized arguments: --forked
to be marked as done.
This means that you claim that the
Source: ruby-haml-rails
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
After updating ruby-haml to 6.1.1, ruby-haml-rails has unsatisfiable
build dependencies.
Relevant part (hopefully):
>
Source: ruby-haml-contrib
Version: 1.0.0.1-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
After updaring ruby-haml to 6.6.1, ruby-haml-contrib fails to build with
a test failure.
Relevant part (hopefully):
>
Source: asciidoctor
Version: 2.0.17-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
I'm working on updating ruby-haml to the new upstream versinon 6.1.1,
and when trying asciidoctor against that the tests fail.
Relevant part (hopefully):
> /usr/bin/ruby3.1
Package: mpv
Version: 0.35.0-4
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU
Is this still an issue with 22.3.1-1?
[Looked briefly into this, since this is a RC bug]
* Otto Kekäläinen [Sat Mar 19, 2022 at 09:04:21AM -0700]:
> Thanks for looking into this. Can you elaborate why you filed this on
> 26.4.8 and not latest 26.4.10?
>
> Builds are passing. Thus tests indicate that there is no issue. What is the
>
Your message dated Fri, 23 Dec 2022 13:51:18 +
with message-id
and subject line Bug#1026658: fixed in onioncircuits 0.7-3
has caused the Debian Bug report #1026658,
regarding onioncircuits: FTBFS: make: *** [debian/rules:8: binary] Error 25
to be marked as done.
This means that you claim
Your message dated Fri, 23 Dec 2022 13:36:52 +
with message-id
and subject line Bug#1026500: fixed in pexpect 4.8.0-4
has caused the Debian Bug report #1026500,
regarding pexpect: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.11 3.10" returned exit code 13
1 - 100 of 128 matches
Mail list logo
