On 25.11.2021 17.38, Salvo Tomaselli wrote:
What about the evdev one?
What about it? -libinput replaced it and has more features.
--
t
Your message dated Fri, 26 Nov 2021 09:18:44 +
with message-id
and subject line Bug#1000625: fixed in opencv 4.5.4+dfsg-7
has caused the Debian Bug report #1000625,
regarding libopencv-dev: Broken pkg-config file
to be marked as done.
This means that you claim that the problem has been dealt
Package: gnubiff
Version: 2.2.17-3
Followup-For: Bug #984159
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
X-Debbugs-Cc: simon.cho...@canonical.com
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
*
Processing control commands:
> tags -1 patch
Bug #984159 [src:gnubiff] gnubiff: ftbfs with GCC-11
Added tag(s) patch.
--
984159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: node-monocle
Version: 1.1.51+dfsg-1.1
Severity: grave
Tags: upstream
Justification: renders package unusable
Enabling test proves that this package is broken. Since it is used only
by deprecated node-jade, I'll ask a ROM-RM instead of searching a
solution (not trivial).
Hi,
Would it be possible to either have the URL of the upstream VCS or a
proper patch file for 4ea9d5b78540c972e3fe1bf44db9f7b3f87c0ad0?
I couldn't find any mention of a VCS on the homepage, only tarballs.
Thanks in advance,
Cheers
--
Simon Chopin
Foundations Team
It's on https://github.com/folkertvanheusden/HTTPing
> Would it be possible to either have the URL of the upstream VCS or a
> proper patch file for 4ea9d5b78540c972e3fe1bf44db9f7b3f87c0ad0?
> I couldn't find any mention of a VCS on the homepage, only tarballs.
Source: caffe
Version: 1.0.0+git20180821.99bd997-8
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/logs.php?pkg=caffe=1.0.0%2Bgit20180821.99bd997-8%2Bb3
...
==
ERROR: test_coord_map
Your message dated Fri, 26 Nov 2021 09:33:41 +
with message-id
and subject line Bug#999764: fixed in gcc-12 12-20211126-1
has caused the Debian Bug report #999764,
regarding gcc-12: file conflicts with gcc-11 due to missing Breaks+Replaces or
renaming
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> tags 1000635 + ftbfs
Bug #1000635 [node-monocle] node-monocle is incompatible with current
node-readdirp
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000635:
Your message dated Fri, 26 Nov 2021 09:55:19 +0100
with message-id <4a18f085-34b6-1d54-5b0c-bcfc3b5b5...@debian.org>
and subject line Re: pillow: FTBFS
has caused the Debian Bug report #998585,
regarding pillow: FTBFS: /<>/docs/deprecations.rst:105: WARNING:
Unknown directive type
Source: php-facedetect
Version: 1.1.0-19-g135c72a-2
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/logs.php?pkg=php-facedetect=1.1.0-19-g135c72a-2%2Bb1
...
dh_clean
/usr/share/dh-php/gen-control
Package not converted to dh-php >= 4
make[1]: ***
Le 26 novembre 2021 12:42:23 GMT+01:00, Jordi Mallach a
écrit :
>Hi Pierre-Elliott!
>
>El dj. 25 de 11 de 2021 a les 22:19 +0100, en/na Pierre-Elliott Bécue
>va escriure:
>> > I might try to work on a fix in the following days, most probably
>> > including an update to the latest version, which
Processing commands for cont...@bugs.debian.org:
> block 998006 with 996300
Bug #998006 {Done: Paul Gevers } [src:ruby-jaeger-client]
src:ruby-jaeger-client: fails to migrate to testing for too long: unresolved RC
bug
998006 was not blocked by any bugs.
998006 was not blocking any bugs.
Added
X-Debbugs-CC: mba...@debian.org debichem-de...@lists.alioth.debian.org
Hi,
My personal preference would be implementing mutual conflict.
Michael: Please let me know whether this works for you. I can make an NMU to
implement mutual conflic for src:ga if you find it necessary.
--
Thanks,
Boyuan
Processing commands for cont...@bugs.debian.org:
> close 996403
Bug #996403 [src:ruby-rails-controller-testing] ruby-rails-controller-testing:
FTBFS: ERROR: Test "ruby3.0" failed.
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996403:
Your message dated Fri, 26 Nov 2021 14:44:09 +
with message-id
and subject line Bug#1000465: fixed in unixodbc 2.3.9-3
has caused the Debian Bug report #1000465,
regarding libodbc1: Missing dependency and dangling symlink
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 26 Nov 2021 12:18:43 +
with message-id
and subject line Bug#981680: fixed in golang-github-canonical-go-dqlite 1.10.1-1
has caused the Debian Bug report #981680,
regarding golang-github-canonical-go-dqlite FTBFS: test failures
to be marked as done.
This means that you
Your message dated Fri, 26 Nov 2021 12:34:04 +
with message-id
and subject line Bug#994365: fixed in python-pylibacl 0.6.0-2
has caused the Debian Bug report #994365,
regarding python-pylibacl: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you
Source: ruby-jaeger-client
Version: 1.2.0-1
Severity: serious
Tags: ftbfs
Control: block 998006 by -1
https://buildd.debian.org/status/logs.php?pkg=ruby-jaeger-client=all
...
Failures:
1) Jaeger::Encoders::ThriftEncoder without custom tags has ip
Failure/Error: expect(ip_tag.vStr).to
Processing control commands:
> block 998006 by -1
Bug #998006 {Done: Paul Gevers } [src:ruby-jaeger-client]
src:ruby-jaeger-client: fails to migrate to testing for too long: unresolved RC
bug
998006 was blocked by: 996300
998006 was not blocking any bugs.
Added blocking bug(s) of 998006:
Your message dated Fri, 26 Nov 2021 15:07:15 +
with message-id
and subject line Bug#1000307: fixed in node-http-proxy 1.18.1-6
has caused the Debian Bug report #1000307,
regarding FTBFS: autopkgtest fails sue to missing socket.io module
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> package rpm
Limiting to bugs with field 'package' containing at least one of 'rpm'
Limit currently set to 'package':'rpm'
> severity 968487 serious
Bug #968487 [rpm] rpm returns wrong %{_target}
Severity set to 'serious' from 'important'
> merge
Your message dated Fri, 26 Nov 2021 11:18:54 +
with message-id
and subject line Bug#855837: fixed in golang-petname 2.11~git20191129.8e5a1ed-1
has caused the Debian Bug report #855837,
regarding golang-petname: should this be in bullseye
to be marked as done.
This means that you claim that
Hi Pierre-Elliott!
El dj. 25 de 11 de 2021 a les 22:19 +0100, en/na Pierre-Elliott Bécue
va escriure:
> > I might try to work on a fix in the following days, most probably
> > including an update to the latest version, which includes other
> > fixes I
> > need.
>
> I'm waiting for some stuck
Control: reopen -1
On Fri, Nov 26, 2021 at 12:21:09PM +, Debian Bug Tracking System wrote:
>...
> golang-github-canonical-go-dqlite (1.10.1-1) unstable; urgency=medium
>...
>* Add patches to fix tests (Closes: #981680)
>...
Unfortunately this does not seem to be sufficient:
Processing control commands:
> reopen -1
Bug #981680 {Done: Mathias Gibbens }
[src:golang-github-canonical-go-dqlite] golang-github-canonical-go-dqlite
FTBFS: test failures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may
Package: haxe
Version: 1:4.1.5-1
Severity: grave
I was checking whether a recent dune would break any package, and my
test failed because Base64 was an unbound module -- it's a missing
build-dep on libbase64-ocaml-dev, so it should be pretty
straightforward to fix.
Cheers,
J.Puydt
Your message dated Fri, 26 Nov 2021 16:49:55 +
with message-id
and subject line Bug#996363: fixed in ruby-rbpdf 1.20.1-2
has caused the Debian Bug report #996363,
regarding ruby-rbpdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error:
test: Image get image file test(RbpdfHttpTest):
Your message dated Fri, 26 Nov 2021 19:08:02 +
with message-id
and subject line Bug#1000230: fixed in screenruler 0.960+bzr41+deb10-5
has caused the Debian Bug report #1000230,
regarding screenruler fails to start
to be marked as done.
This means that you claim that the problem has been
Le Wed, Nov 24, 2021 at 07:03:39PM -0400, David Prévot a écrit :
> Package: php-cboden-ratchet
[…]
> Since symfony 5 has finally been uploaded to unstable, packages now
> can’t depend on php-symfony-* (<< 5) anymore. Upgrading to a new
> upstream version should do the trick (Symfony 5 has been
Processing control commands:
> tag -1 pending
Bug #996363 [src:ruby-rbpdf] ruby-rbpdf: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed: Error: test: Image get image file test(RbpdfHttpTest):
NoMethodError: undefined method `shutdown' for nil:NilClass
Added tag(s) pending.
--
996363:
Control: tag -1 pending
Hello,
Bug #996363 in ruby-rbpdf 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:
I believe this is resolved in 1.0.12-1 published in unstable but I forgot
to add the *Closes* reference to the Changelog.
On Fri, Aug 20, 2021 at 10:51 AM Simon Chopin
wrote:
> Source: caml-crush
> Followup-For: Bug #973153
>
> There's a PR upstream to deal with this:
>
>
Your message dated Fri, 26 Nov 2021 17:33:54 +
with message-id
and subject line Bug#984299: fixed in psocksxx 1.1.1-2
has caused the Debian Bug report #984299,
regarding psocksxx: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
On Thu, 25 Nov 2021 16:48:50 + Debian FTP Masters
wrote:
> We believe that the bug you reported is fixed in the latest version of
> maxima, which is due to be installed in the Debian FTP archive.
...
> maxima (5.45.1-6) unstable; urgency=medium
> .
>* maxima-emacs conflicts with
Your message dated Fri, 26 Nov 2021 16:21:39 +
with message-id
and subject line Bug#996298: fixed in ruby-influxdb 0.8.1-1
has caused the Debian Bug report #996298,
regarding ruby-influxdb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error: specify {
I filed this upstream bug
https://github.com/gluster/glusterfs/issues/2979 and am using this
patch in Ubuntu:
diff --git a/debian/rules b/debian/rules
index 0e28ea8e..7bfab4c1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,6 +4,12 @@ include /usr/share/dpkg/pkg-info.mk
export
Your message dated Fri, 26 Nov 2021 21:19:36 +
with message-id
and subject line Bug#1000617: fixed in nbclient 0.5.6-2
has caused the Debian Bug report #1000617,
regarding python3-nbclient_0.5.6-1: trying to overwrite '/usr/bin/jupyter-run',
which is also in package jupyter-client 7.0.6-2
to
Processing commands for cont...@bugs.debian.org:
> #
> https://salsa.debian.org/ruby-team/forks/r10k/-/commit/8b869037d4fa83de1d5ab67b34ce6ac70718fd30
> tags 996116 + pending
Bug #996116 [src:r10k] r10k: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError:
Added tag(s)
Your message dated Sat, 27 Nov 2021 02:53:30 +0100
with message-id <4e48a243a735f622cd20ac3a783ee01b7b696799.ca...@debian.org>
and subject line Both issues fixed with the upload of test-kitchen/1.23.2-6
has caused the Debian Bug report #996307,
regarding ruby-kitchen-docker: FTBFS: ERROR: Test
Your message dated Sat, 27 Nov 2021 02:53:30 +0100
with message-id <4e48a243a735f622cd20ac3a783ee01b7b696799.ca...@debian.org>
and subject line Both issues fixed with the upload of test-kitchen/1.23.2-6
has caused the Debian Bug report #996308,
regarding ruby-kitchen-salt: FTBFS: ERROR: Test
Your message dated Fri, 26 Nov 2021 22:19:16 +
with message-id
and subject line Bug#1000197: fixed in assimp 5.1.1~ds0-2
has caused the Debian Bug report #1000197,
regarding assimp: binary-any FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Fri, 26 Nov 2021 23:35:51 +
with message-id
and subject line Bug#996137: fixed in ruby-binding-of-caller 1.0.0-1
has caused the Debian Bug report #996137,
regarding ruby-binding-of-caller: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed:
:85:in
`require': cannot load
Your message dated Fri, 26 Nov 2021 23:35:43 +
with message-id
and subject line Bug#968487: fixed in rpm 4.17.0+dfsg1-2
has caused the Debian Bug report #968487,
regarding rpm, autopkgtest failure on armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 26 Nov 2021 23:35:43 +
with message-id
and subject line Bug#968487: fixed in rpm 4.17.0+dfsg1-2
has caused the Debian Bug report #968487,
regarding rpm returns wrong %{_target}
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> tag -1 pending
Bug #967018 [src:test-kitchen] test-kitchen: FTBFS: ERROR: Test "ruby2.7"
failed: cannot load such file -- aruba/in_process (LoadError)
Added tag(s) pending.
--
967018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967018
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #996528 in test-kitchen reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #967018 in test-kitchen 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 #996528 [src:test-kitchen] test-kitchen: FTBFS: ERROR: Test "ruby2.7"
failed: Could not find 'thor' (~> 0.19) among 87 total gem(s)
(Gem::MissingSpecError)
Added tag(s) pending.
--
996528:
Your message dated Sat, 27 Nov 2021 01:48:45 +
with message-id
and subject line Bug#996528: fixed in test-kitchen 1.23.2-6
has caused the Debian Bug report #996528,
regarding test-kitchen: FTBFS: ERROR: Test "ruby2.7" failed: Could not find
'thor' (~> 0.19) among 87 total gem(s)
Your message dated Sat, 27 Nov 2021 01:48:45 +
with message-id
and subject line Bug#967018: fixed in test-kitchen 1.23.2-6
has caused the Debian Bug report #967018,
regarding test-kitchen: FTBFS: ERROR: Test "ruby2.7" failed: cannot load such
file -- aruba/in_process (LoadError)
to be marked
Package: npm
Severity: serious
Justification: Policy 2.2.1
X-Debbugs-Cc: i...@mikelpr.com
Dear Maintainer,
I was installing npm on my headless raspberry pi when I noticed it pulls
unnecessary libx11 packages and xserver-utils. Since they're not listed
on the package dependencies, I assume one of
Control: tag -1 pending
Hello,
Bug #996137 in ruby-binding-of-caller 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 #996137 [src:ruby-binding-of-caller] ruby-binding-of-caller: FTBFS with
ruby3.0: ERROR: Test "ruby3.0" failed:
:85:in
`require': cannot load such file -- binding_of_caller.so (LoadError)
Added tag(s) pending.
--
996137:
Your message dated Fri, 26 Nov 2021 23:18:45 +
with message-id
and subject line Bug#1000388: fixed in parlatype 3.0-2
has caused the Debian Bug report #1000388,
regarding FTBFS on s390x due to whitespace damage
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> block 996307 with 996528
Bug #996307 [src:ruby-kitchen-docker] ruby-kitchen-docker: FTBFS: ERROR: Test
"ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in
`rescue in block in activate_dependencies': Could not find
Control: severity -1 important
Hi Mikel,
Quoting Mikel Pérez (2021-11-26 23:57:36)
> Severity: serious
> Justification: Policy 2.2.1
Justification cannot be § 2.2.1 which is about what can go into Debian
or instead can only be part of the "contrib" or "non-free": the npm
package comply with
Processing commands for cont...@bugs.debian.org:
> block 996308 with 996528
Bug #996308 [src:ruby-kitchen-salt] ruby-kitchen-salt: FTBFS: ERROR: Test
"ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in
`rescue in block in activate_dependencies': Could not find 'thor'
Processing control commands:
> severity -1 important
Bug #1000673 [npm] reportbug: npm package depends on too many packages,
including X11
Severity set to 'important' from 'serious'
--
1000673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000673
Debian Bug Tracking System
Contact
Your message dated Sat, 27 Nov 2021 00:49:44 +
with message-id
and subject line Bug#994366: fixed in python-pyxattr 0.7.2-2
has caused the Debian Bug report #994366,
regarding python-pyxattr: Removal of the python3-*-dbg packages in sid/bookworm
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> severity 994359 important
Bug #994359 [src:python-llfuse] python-llfuse: Removal of the python3-*-dbg
packages in sid/bookworm
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> clone 996527 -1
Bug #996527 [src:sup-mail] sup-mail: FTBFS: ERROR: Test "ruby2.7" failed:
NameError: uninitialized constant ActiveSupport
Bug 996527 cloned as bug 1000679
> reassign -1 ruby-rr 3.0.7-1
Bug #1000679 [src:sup-mail] sup-mail: FTBFS:
Control: tag -1 pending
Hello,
Bug #996527 in sup-mail 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 #996527 [src:sup-mail] sup-mail: FTBFS: ERROR: Test "ruby2.7" failed:
NameError: uninitialized constant ActiveSupport
Added tag(s) pending.
--
996527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996527
Debian Bug Tracking System
Contact
Package: python3-aiohttp
Version: 3.7.4-2+b1
Severity: grave
X-Debbugs-Cc: mo...@debian.org
Control: affects -1 uvloop
Hello,
simply importing aiohttp results in an error:
root@zion:/# python3.9 -c "import aiohttp"
Traceback (most recent call last):
File "", line 1, in
File
Processing control commands:
> affects -1 uvloop
Bug #1000680 [python3-aiohttp] python3-aiohttp: fails to import, "TypeError:
function() argument 'code' must be code, not str"
Added indication that 1000680 affects uvloop
--
1000680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000680
Processing control commands:
> tag -1 pending
Bug #996378 [src:ruby-rspec-retry] ruby-rspec-retry: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: Failure/Error:
Added tag(s) pending.
--
996378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996378
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #996378 in ruby-rspec-retry 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:
> tags 1000341 -moreinfo
Bug #1000341 [release.debian.org] buster-pu: package mariadb-10.3
10.3.32-0+deb10u1
Removed tag(s) moreinfo.
> tags 1000340 -moreinfo
Bug #1000340 [src:bibtexconv] bibtexconv: autopkgtest failure: "Tests" field is
empty
Control: tag -1 pending
Hello,
Bug #1000679 in ruby-rr 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 #1000679 [ruby-rr] ruby-rr: NameError: uninitialized constant ActiveSupport
Added tag(s) pending.
--
1000679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sat, 27 Nov 2021 03:04:39 +
with message-id
and subject line Bug#1000679: fixed in ruby-rr 3.0.8-1
has caused the Debian Bug report #1000679,
regarding ruby-rr: NameError: uninitialized constant ActiveSupport
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 27 Nov 2021 04:29:12 +0100
with message-id <5bff162e3757627ba99b19e9d595ecf8e6fe4583.ca...@debian.org>
and subject line Fixed with the latest upload of ruby-rspec/3.10.0c1e1m2s3-1
has caused the Debian Bug report #996379,
regarding ruby-rspec: FTBFS with ruby3.0: ERROR:
Your message dated Sat, 27 Nov 2021 03:34:30 +
with message-id
and subject line Bug#1000360: fixed in segyio 1.8.3-1.1
has caused the Debian Bug report #1000360,
regarding segyio: FTBFS with Python 3.10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 27 Nov 2021 03:34:36 +
with message-id
and subject line Bug#996527: fixed in sup-mail 1.0-4
has caused the Debian Bug report #996527,
regarding sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError:
uninitialized constant ActiveSupport
to be marked as done.
This
Your message dated Sat, 27 Nov 2021 05:03:41 +
with message-id
and subject line Bug#996378: fixed in ruby-rspec-retry 0.6.2-2
has caused the Debian Bug report #996378,
regarding ruby-rspec-retry: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error:
to be marked as done.
77 matches
Mail list logo
