Bug#1031472: marked as done (ruby-omniauth-facebook: FTBFS: ERROR: Test "ruby3.1" failed.)
Your message dated Wed, 22 Mar 2023 05:48:58 +
with message-id
and subject line Bug#1031472: fixed in ruby-omniauth-facebook 4.0.0-3
has caused the Debian Bug report #1031472,
regarding ruby-omniauth-facebook: FTBFS: ERROR: Test "ruby3.1" failed.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1031472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-facebook
Version: 4.0.0-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1
> │
> └──┘
>
> GEM_PATH=/<>/debian/ruby-omniauth-facebook/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
> ruby3.1 -e gem\ \"omniauth-facebook\"
>
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rb
> │
> └──┘
>
> RUBYLIB=/<>/debian/ruby-omniauth-facebook/usr/lib/ruby/vendor_ruby:.
>
> GEM_PATH=/<>/debian/ruby-omniauth-facebook/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
> ruby3.1 debian/ruby-tests.rb
> mv example/Gemfile.lock example/.gem2deb.Gemfile.lock
> Mocha deprecation warning at
> :160:in
> `require': Require 'mocha/test_unit', 'mocha/minitest' or 'mocha/api'
> instead of 'mocha/setup'.
> Run options: --seed 19466
>
> # Running:
>
> EE...E..DEPRECATED: Use assert_nil if expecting nil
> from /<>/test/strategy_test.rb:455. This will fail in Minitest 6.
> .EE.E
>
> Finished in 0.091243s, 800.0599 runs/s, 1183.6503 assertions/s.
>
> 1) Error:
> SignedRequestTests::CookiePresentTest#test_parses_the_access_code_out_from_the_cookie:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
>
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean? MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:435:in `setup'
>
> 2) Error:
> SignedRequestTests::CookiePresentTest#test_throws_an_error_if_the_algorithm_is_unknown:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
>
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean? MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:435:in `setup'
>
> 3) Error:
> SignedRequestTests::MissingCodeInCookieRequestTest#test_calls_fail!_when_a_code_is_not_included_in_the_cookie:
> NameError: uninitialized constant SignedRequestHelpers::MultiJson
>
> encoded_payload = base64_encode_url(MultiJson.encode(payload))
> ^
> Did you mean? MultiXml
> /<>/test/strategy_test.rb:396:in `signed_request'
> /<>/test/strategy_test.rb:481:in `setup'
>
> 4) Error:
> SignedRequestTest#test_signed_request_parse:
> NameError: uninitialized constant SignedRequestTest::MultiJson
>
> @expected_payload = MultiJson.decode(fixture('payload.json'))
> ^
> Did you mean? MultiXml
> /<>/test/signed_request_test.rb:8:in `setup'
>
> 5) Error:
> SignedRequestTest#test_signed_request_payload:
> NameError: uninitialized constant SignedRequestTest::MultiJson
>
> @expected_payload = MultiJson.decode(fixture('payload.json'))
> ^
> Did you mean? MultiXml
> /<>/test/signed_request_test.rb:8:in `setup'
>
> 6) Error:
>
Bug#1033306: tor: Tor relays running 0.4.5.16 will soon be cut off from the network
Package: tor Version: 0.4.5.16-1 Severity: grave Justification: renders package unusable I received the following email from the Tor Project: Hi, You are running a bunch of Tor relays, which is great: However, those relays' Tor version is obsolete, and because of old bugs, we will soon cut relays and bridges running that version out of the network. Please consider upgrading! You can find Tor packages and instructions for your distro / OS here: https://community.torproject.org/relay/setup/guard/ If you need help upgrading your relays, please use the Tor Forum: https://forum.torproject.net/c/support/relay-operator/17 Let us know if we can do anything to make the process easier. Thanks! Georg They are currently aiming for a cut-off date 4-6 weeks from now. This means that the version of tor that's in bullseye will essentially stop working for most uses. There is already a version in backports that will work fine, but perhaps it's worth also uploading it to stable for the next point release? Francois -- https://fmarier.org/
Bug#980316: Update on packaging corepack
On Tue, Mar 21 2023 at 09:06:41 PM +01:00:00 +01:00:00, Paul Gevers wrote: Hi Pirate, Thanks for reaching out. On 20-03-2023 16:44, Pirate Praveen wrote: I request bookworm-ignore tags for these bugs (as such there is no immediate breakage, just unmaintained upstreams for these packages). > yarnpkg: 980316,958686, 1002902, 980316 > node-har-validator: 1024575 > node-request: 956423 > node-request-capture-har: 1002901 As the packages in question are key packages, we can't easily remove them. Hence adding a bookworm-ignore tag doesn't really change the situation in bookworm in any way. Hence, the question is whether fixing it now and adding an exception is better or worse than letting the bug ship in bookworm. If I understand correctly, than the required change would mean a new complex package (corepack) which (again, if I understand correctly) is considered also by you as inappropriate at this time. If you confirm my understanding, I agree that those bugs can be marked bookworm-ignore (I already marked them as bookworm-can-defer, which is less strong and less official). We won't be able to complete corepack in a few weeks or months. So we have to ship bookworm with these bugs and get this fixed in time for trixie. Paul
Bug#607969: marked as done (sqlite: removal of sqlite 2 is really overdue)
Your message dated Wed, 22 Mar 2023 00:51:28 + with message-id and subject line Bug#1033270: Removed package(s) from unstable has caused the Debian Bug report #607969, regarding sqlite: removal of sqlite 2 is really overdue to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 607969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sqlite Version: 2.8.17-6 Severity: important Hi, Is this package still useful since we also have an sqlite3 package? They have the same description other than that short description has a 3 in it. >From what I find it says that sqlite3 is compatible with all versions. So I don't see the point of keeping this version around. Kurt --- End Message --- --- Begin Message --- Version: 2.8.17-15+rm Dear submitter, as the package sqlite has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1033270 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#957397: marked as done (kannel-sqlbox: ftbfs with GCC-10)
Your message dated Wed, 22 Mar 2023 00:50:58 +
with message-id
and subject line Bug#1033269: Removed package(s) from unstable
has caused the Debian Bug report #957397,
regarding kannel-sqlbox: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
957397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kannel-sqlbox
Version: 0.7.2-5
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/kannel-sqlbox_0.7.2-5_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
|~~^~
sqlbox_sqlite3.c:220:35: note: in expansion of macro ‘st_str’
220 | st_str(msg->sms.boxc_id), st_str(msg->sms.binfo));
| ^~
sqlbox_sqlite3.c:195:38: warning: operation on ‘stuffcount’ may be undefined
[-Wsequence-point]
195 | #define st_str(x) (stuffer[stuffcount++] =
get_string_value_or_return_null(x))
|~~^~
sqlbox_sqlite3.c:220:35: note: in expansion of macro ‘st_str’
220 | st_str(msg->sms.boxc_id), st_str(msg->sms.binfo));
| ^~
sqlbox_sqlite3.c:195:38: warning: operation on ‘stuffcount’ may be undefined
[-Wsequence-point]
195 | #define st_str(x) (stuffer[stuffcount++] =
get_string_value_or_return_null(x))
|~~^~
sqlbox_sqlite3.c:220:35: note: in expansion of macro ‘st_str’
220 | st_str(msg->sms.boxc_id), st_str(msg->sms.binfo));
| ^~
sqlbox_sqlite3.c:195:38: warning: operation on ‘stuffcount’ may be undefined
[-Wsequence-point]
195 | #define st_str(x) (stuffer[stuffcount++] =
get_string_value_or_return_null(x))
|~~^~
sqlbox_sqlite3.c:220:35: note: in expansion of macro ‘st_str’
220 | st_str(msg->sms.boxc_id), st_str(msg->sms.binfo));
| ^~
sqlbox_sqlite3.c:195:38: warning: operation on ‘stuffcount’ may be undefined
[-Wsequence-point]
195 | #define st_str(x) (stuffer[stuffcount++] =
get_string_value_or_return_null(x))
|~~^~
sqlbox_sqlite3.c:220:35: note: in expansion of macro ‘st_str’
220 | st_str(msg->sms.boxc_id), st_str(msg->sms.binfo));
| ^~
sqlbox_sqlite3.c:195:38: warning: operation on ‘stuffcount’ may be undefined
[-Wsequence-point]
195 | #define st_str(x) (stuffer[stuffcount++] =
get_string_value_or_return_null(x))
|~~^~
sqlbox_sqlite3.c:220:35: note: in expansion of macro ‘st_str’
220 | st_str(msg->sms.boxc_id), st_str(msg->sms.binfo));
| ^~
sqlbox_sqlite3.c: At top level:
sqlbox_sqlite3.c:229:6: warning: no previous prototype for ‘sqlite3_leave’
[-Wmissing-prototypes]
229 | void sqlite3_leave()
| ^
sqlbox_sqlite3.c: In function ‘sqlbox_init_sqlite3’:
sqlbox_sqlite3.c:284:25: warning: passing argument 1 of ‘cfg_get_integer’ from
incompatible pointer type [-Wincompatible-pointer-types]
284 | if (cfg_get_integer(_timeout, grp, octstr_imm("lock-timeout"))
== -1 || lock_timeout == 0 )
| ^
| |
| int *
In file
Bug#972128: marked as done (kannel-sqlbox: Please remove support for long-unmaintained sqlite 2)
Your message dated Wed, 22 Mar 2023 00:50:58 + with message-id and subject line Bug#1033269: Removed package(s) from unstable has caused the Debian Bug report #972128, regarding kannel-sqlbox: Please remove support for long-unmaintained sqlite 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kannel-sqlbox Version: 0.7.2-5 Severity: important Tags: bullseye sid User: debian...@lists.debian.org Usertags: libsqlite0 Control: block 607969 by -1 kannel-sqlbox builds a binary package that Depends on libsqlite0. This is sqlite 2, which was superseded in 2004 and is planned to be removed (see #607969), and nothing in Debian seems to depend on it. Please remove the sqlite 2 dependency, leaving only sqlite 3 support. If I'm understanding the build system correctly, it might be possible to fix this with a binNMU, since kannel dropped support for sqlite 2 in January, and kannel-sqlbox picks up its sqlite 2 and/or 3 support from kannel. However, kannel-sqlbox needs source changes anyway to address a FTBFS with gcc 10 (#957397). This bug is currently non-RC, but is very likely to become RC soon. Thanks, smcv --- End Message --- --- Begin Message --- Version: 0.7.2-5+rm Dear submitter, as the package kannel-sqlbox has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1033269 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#999051: marked as done (sendpage: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Wed, 22 Mar 2023 00:49:22 + with message-id and subject line Bug#1033066: Removed package(s) from unstable has caused the Debian Bug report #999051, regarding sendpage: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sendpage Version: 1.0.3-1.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 1.0.3-1.1+rm Dear submitter, as the package sendpage has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1033066 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#965814: marked as done (sendpage: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Wed, 22 Mar 2023 00:49:22 + with message-id and subject line Bug#1033066: Removed package(s) from unstable has caused the Debian Bug report #965814, regarding sendpage: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sendpage Version: 1.0.3-1 Severity: normal Usertags: compat-5-6-removal Hi, The package sendpage uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 1.0.3-1.1+rm Dear submitter, as the package sendpage has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1033066 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1031441: marked as done (ruby-github-api: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not fin
Your message dated Wed, 22 Mar 2023 00:49:59 + with message-id and subject line Bug#1033093: Removed package(s) from unstable has caused the Debian Bug report #1031441, regarding ruby-github-api: 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 'oauth2' (~> 1.0) among 106 total gem(s) (Gem::MissingSpecError) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1031441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-github-api Version: 0.19.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230216 ftbfs-bookworm 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 > in activate_dependencies': Could not find 'oauth2' (~> 1.0) among 106 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-github-api/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > at: > /<>/debian/ruby-github-api/usr/share/rubygems-integration/all/specifications/github_api-0.19.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'oauth2' (~> 1.0) - did find: [oauth2-2.0.7] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-github-api/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > abbrev (default: 0.1.0) > addressable (2.8.1) > atomic (1.1.16) > base64 (default: 0.1.1) > benchmark (default: 0.2.0) > bigdecimal (default: 3.1.1) > bundler (default: 2.3.7) > cgi (default: 0.3.5) > csv (default: 3.2.2) > date (default: 3.2.2) > debug (1.4.0) > delegate (default: 0.2.0) > descendants_tracker (0.0.4) > did_you_mean (default: 1.6.1) > digest (default: 3.1.0) > drb (default: 2.1.0) > english (default: 0.7.1) > erb (default: 2.2.3) > error_highlight (default: 0.3.0) > etc (default: 1.3.0) > faraday (1.1.0) > fcntl (default: 1.0.1) > fiddle (default: 1.1.0) > fileutils (default: 1.6.0) > find (default: 0.1.1) > forwardable (default: 1.3.2) > getoptlong (default: 0.1.1) > hashie (5.0.0) > io-console (default: 0.5.11) > io-nonblock (default: 0.1.0) > io-wait (default: 0.2.1) > ipaddr (default: 1.2.4) > irb (default: 1.4.1) > json (default: 2.6.1) > jwt (2.5.0) > logger (default: 1.5.0) > matrix (0.4.2) > minitest (5.15.0) > multi_json (1.14.1) >
Bug#1033044: daily cron job broken?
That have happened and. I just want. An answer too maybe. I mean, I can't.
Seemed to get away from it.HELP
On Tue, Mar 21, 2023 at 12:30 AM tommy reid
wrote:
> Never broken
>
> On Thu, Mar 16, 2023, 5:45 AM Marc Haber
> wrote:
>
>> Package: aide-common
>> Version: 0.18.1-1
>> Severity: grave
>> Tags: confirmed
>>
>> Justification: Maintainer discretion, cron job broken
>>
>> diff --git a/debian/bin/dailyaidecheck b/debian/bin/dailyaidecheck
>> index aa4b59c..fbd0a57 100755
>> --- a/debian/bin/dailyaidecheck
>> +++ b/debian/bin/dailyaidecheck
>> @@ -161,7 +161,7 @@ FILTERUPDATES="${FILTERUPDATES:-no}"
>> FILTERINSTALLATIONS="${FILTERINSTALLATIONS:-no}"
>> CRONEXITHOOK="${CRONEXITHOOK:-}"
>> ONEXIT=""
>> -AIDEUSER="${AIDEUSER:-root}"
>> +AIDEUSER="${AIDEUSER:-$(id --user --name)}"
>> AIDEUSERUID="$(id --user "${AIDEUSER}")"
>>
>> # silent implies quiet
>>
>> And upload will follow shortly.
>>
>> Greetings
>> Marc, Maintainer
>>
>>
Processed (with 1 error): Re: chromium: #ozone-platform-hint should be set to auto
Processing commands for cont...@bugs.debian.org: > tags 1033223 - patch Bug #1033223 [chromium] chromium: #ozone-platform-hint should be set to auto Removed tag(s) patch. > clone 1033223 -1 Bug #1033223 [chromium] chromium: #ozone-platform-hint should be set to auto Bug 1033223 cloned as bug 1033302 > retitle -1 chromium: X11 backend broken in KDE Wayland Bug #1033302 [chromium] chromium: #ozone-platform-hint should be set to auto Changed Bug title to 'chromium: X11 backend broken in KDE Wayland' from 'chromium: #ozone-platform-hint should be set to auto'. > severity -1 important Bug #1033302 [chromium] chromium: X11 backend broken in KDE Wayland Severity set to 'important' from 'serious' > retitle 1033223 chromium: document how to enable Wayland backend in Bug #1033223 [chromium] chromium: #ozone-platform-hint should be set to auto Changed Bug title to 'chromium: document how to enable Wayland backend in' from 'chromium: #ozone-platform-hint should be set to auto'. > README.Debian Unknown command or malformed arguments to command. > severity 1033223 wishlist Bug #1033223 [chromium] chromium: document how to enable Wayland backend in Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1033223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033223 1033302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1033295 in 2.5.0-1.1
Processing commands for cont...@bugs.debian.org: > found 1033295 2.5.0-1.1 Bug #1033295 [src:cairosvg] cairosvg: CVE-2023-27586: SSRF & DOS vulnerability Marked as found in versions cairosvg/2.5.0-1.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028104: libboost-dev: Boost with C++20 uses unavailable std functions
Hi, On Sun, 08 Jan 2023 00:26:39 +0100 Andreas Beckmann wrote: This happens with g++-12 but not with g++-11. It is fixed in the boost version in experimental. Any chance for a *targeted* fix in bookworm? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1032647: fixed in nvidia-graphics-drivers 530.30.02-1
Hi Andreas, On Mon, 13 Mar 2023 23:04:41 + Debian FTP Masters wrote: Changes: nvidia-graphics-drivers (530.30.02-1) experimental; urgency=medium . * New upstream beta 530.30.02 (2023-02-28). (Closes: #1032647) I'm not expecting a targeted fix is reasonably possible for this issue, right? Did you intend to ignore it in bookworm from your side? Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: issue caused by bullseye kernel
Processing commands for cont...@bugs.debian.org: > # the issue is in the bullseye kernel so not affecting bookworm as such > tag 1030545 bookworm-ignore Bug #1030545 [src:qemu] qemu: qemu-img and qemu-system-s390x hang on s390x Added tag(s) bookworm-ignore. > retitle 1030545 qemu-(img|system-s390x) hang on s390x bullseye kernel Bug #1030545 [src:qemu] qemu: qemu-img and qemu-system-s390x hang on s390x Changed Bug title to 'qemu-(img|system-s390x) hang on s390x bullseye kernel' from 'qemu: qemu-img and qemu-system-s390x hang on s390x'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1030545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033297: xen: CVE-2022-42331 CVE-2022-42332 CVE-2022-42333 CVE-2022-42334
Source: xen Version: 4.17.0+46-gaaf74a532c-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for xen. CVE-2022-42331[0]: | x86: speculative vulnerability in 32bit SYSCALL path Due to an | oversight in the very original Spectre/Meltdown security work | (XSA-254), one entrypath performs its speculation-safety actions too | late. In some configurations, there is an unprotected RET instruction | which can be attacked with a variety of speculative attacks. CVE-2022-42332[1]: | x86 shadow plus log-dirty mode use-after-free In environments where | host assisted address translation is necessary but Hardware Assisted | Paging (HAP) is unavailable, Xen will run guests in so called shadow | mode. Shadow mode maintains a pool of memory used for both shadow page | tables as well as auxiliary data structures. To migrate or snapshot | guests, Xen additionally runs them in so called log-dirty mode. The | data structures needed by the log-dirty tracking are part of | aformentioned auxiliary data. In order to keep error handling efforts | within reasonable bounds, for operations which may require memory | allocations shadow mode logic ensures up front that enough memory is | available for the worst case requirements. Unfortunately, while page | table memory is properly accounted for on the code path requiring the | potential establishing of new shadows, demands by the log-dirty | infrastructure were not taken into consideration. As a result, just | established shadow page tables could be freed again immediately, while | other code is still accessing them on the assumption that they would | remain allocated. CVE-2022-42333[2]: | x86/HVM pinned cache attributes mis-handling T[his CNA information | record relates to multiple CVEs; the text explains which | aspects/vulnerabilities correspond to which CVE.] To allow cachability | control for HVM guests with passed through devices, an interface | exists to explicitly override defaults which would otherwise be put in | place. While not exposed to the affected guests themselves, the | interface specifically exists for domains controlling such guests. | This interface may therefore be used by not fully privileged entities, | e.g. qemu running deprivileged in Dom0 or qemu running in a so called | stub-domain. With this exposure it is an issue that - the number of | the such controlled regions was unbounded (CVE-2022-42333), - | installation and removal of such regions was not properly serialized | (CVE-2022-42334). CVE-2022-42334[3]: | x86/HVM pinned cache attributes mis-handling T[his CNA information | record relates to multiple CVEs; the text explains which | aspects/vulnerabilities correspond to which CVE.] To allow cachability | control for HVM guests with passed through devices, an interface | exists to explicitly override defaults which would otherwise be put in | place. While not exposed to the affected guests themselves, the | interface specifically exists for domains controlling such guests. | This interface may therefore be used by not fully privileged entities, | e.g. qemu running deprivileged in Dom0 or qemu running in a so called | stub-domain. With this exposure it is an issue that - the number of | the such controlled regions was unbounded (CVE-2022-42333), - | installation and removal of such regions was not properly serialized | (CVE-2022-42334). If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-42331 https://www.cve.org/CVERecord?id=CVE-2022-42331 [1] https://security-tracker.debian.org/tracker/CVE-2022-42332 https://www.cve.org/CVERecord?id=CVE-2022-42332 [2] https://security-tracker.debian.org/tracker/CVE-2022-42333 https://www.cve.org/CVERecord?id=CVE-2022-42333 [3] https://security-tracker.debian.org/tracker/CVE-2022-42334 https://www.cve.org/CVERecord?id=CVE-2022-42334 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Processed: Re: Processed (with 1 error): Re: Bug#1032989: Liferea 1.14.1-1 segfaults on startup when trying to read gsettings
Processing commands for cont...@bugs.debian.org: > forwarded 1032989 https://github.com/lwindolf/liferea/issues/1214 Bug #1032989 [liferea] Liferea 1.14.1-1 segfaults on startup when trying to read gsettings Changed Bug forwarded-to-address to 'https://github.com/lwindolf/liferea/issues/1214' from 'https://github.com/lwindolf/liferea/issues/1212'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1032989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032989: Liferea 1.14.1-1 segfaults on startup when trying to read gsettings
Control: forward -1 https://github.com/lwindolf/liferea/issues/1214 Hi Grzegorz, Thanks for your feedback, much appreciated. On 21-03-2023 17:48, Grzegorz Szymaszek wrote: I think we can set "forwarded" to issue 1214[3] which seems to more clearly describe this specific crash. Doing so now. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#980316: Update on packaging corepack
Hi Pirate, Thanks for reaching out. On 20-03-2023 16:44, Pirate Praveen wrote: I request bookworm-ignore tags for these bugs (as such there is no immediate breakage, just unmaintained upstreams for these packages). > yarnpkg: 980316,958686, 1002902, 980316 > node-har-validator: 1024575 > node-request: 956423 > node-request-capture-har: 1002901 As the packages in question are key packages, we can't easily remove them. Hence adding a bookworm-ignore tag doesn't really change the situation in bookworm in any way. Hence, the question is whether fixing it now and adding an exception is better or worse than letting the bug ship in bookworm. If I understand correctly, than the required change would mean a new complex package (corepack) which (again, if I understand correctly) is considered also by you as inappropriate at this time. If you confirm my understanding, I agree that those bugs can be marked bookworm-ignore (I already marked them as bookworm-can-defer, which is less strong and less official). Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1032547: marked as done (facet-analyser: FTBFS in testing: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)
Your message dated Tue, 21 Mar 2023 21:02:44 +0100 with message-id and subject line Re: Bug#1032547: facet-analyser: FTBFS in testing: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 has caused the Debian Bug report #1032547, regarding facet-analyser: FTBFS in testing: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1032547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: facet-analyser Version: 0.0~git20221121142040.6be10b8+ds1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230307 ftbfs-bookworm Hi, During a rebuild of all packages in testing (bookworm), your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j8 > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<>/obj-x86_64-linux-gnu > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: basicPluginTest01 > > 1: Test command: /usr/bin/pvpython "/<>/scripts/pvsm2webgl.py" > "-i" "8faced-rhombic-dodecahedron_twinned_simp+def_PVplugin.pvsm" "-o" > "/<>/docs/demos/WebGL/8faced-rhombic-dodecahedron_twinned_simp+def_PVplugin.webgl" > "-p" > "/<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/paraview-5.11/plugins/FacetAnalyser/FacetAnalyser.so" > 1: Working Directory: /<>/demos/ > 1: Test timeout computed to be: 1500 > test 2 > Start 2: basicPluginTest02 > > 2: Test command: /usr/bin/pvpython "/<>/scripts/pvsm2x3d.py" > "-i" "8faced-rhombic-dodecahedron_twinned_simp+def_PVplugin.pvsm" "-o" > "../docs/demos/X3D/8faced-rhombic-dodecahedron_twinned_simp+def_PVplugin.x3d" > "-p" > "/<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/paraview-5.11/plugins/FacetAnalyser/FacetAnalyser.so" > 2: Working Directory: /<>/demos/ > 2: Test timeout computed to be: 1500 > test 3 > Start 3: basicTest01 > > 3: Test command: > /<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/paraview-5.11/plugins/FacetAnalyser/FacetAnalyserTest > "8faced-rhombic-dodecahedron_twinned_simplified.vtk" > 3: Working Directory: /<>/testing/ > 3: Test timeout computed to be: 1500 > test 4 > Start 4: basicExampleTest01 > > 4: Test command: > /<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/paraview-5.11/plugins/FacetAnalyser/FacetAnalyserCLI > "8faced-rhombic-dodecahedron_twinned_010_deformed_wss.vtp" "51" "15" "0.2" > "0.001" "2" "0" "8faced-rhombic-dodecahedron_twinned_010_deformed_wss_FA.vtp" > 4: Working Directory: /<>/demos/ > 4: Test timeout computed to be: 1500 > 3: > vtkGaussianSplatterExtended progress: 0.0% > vtkGaussianSplatterExtended progress: 0.0% > vtkGaussianSplatterExtended progress: 4.2% > vtkGaussianSplatterExtended progress: 8.3% > vtkGaussianSplatterExtended progress: 12.5% > vtkGaussianSplatterExtended progress: 16.7% > vtkGaussianSplatterExtended progress: 20.8% > vtkGaussianSplatterExtended progress: 25.0% > vtkGaussianSplatterExtended progress: 29.2% > vtkGaussianSplatterExtended progress: 33.3% > vtkGaussianSplatterExtended progress: 37.5% > vtkGaussianSplatterExtended progress: 41.7% > vtkGaussianSplatterExtended progress: 45.8% > vtkGaussianSplatterExtended progress: 50.0% > vtkGaussianSplatterExtended progress: 54.2% > vtkGaussianSplatterExtended progress: 58.3% > vtkGaussianSplatterExtended progress: 62.5% > vtkGaussianSplatterExtended progress: 66.7% > vtkGaussianSplatterExtended progress: 70.8% > vtkGaussianSplatterExtended progress: 75.0% > vtkGaussianSplatterExtended progress: 79.2% > vtkGaussianSplatterExtended progress: 83.3% > vtkGaussianSplatterExtended progress: 87.5% > vtkGaussianSplatterExtended progress: 91.7% > vtkGaussianSplatterExtended progress: 95.8% > vtkGaussianSplatterExtended progress: 100.0% > 3: > MorphologicalWatershedFromMarkersImageFilter progress: 0.0% >
Bug#971783: marked as pending in mate-media
Crash again today, here the full backtrace:
(mate-volume-control-status-icon:59859): Gdk-CRITICAL **: 17:44:19.067:
gdk_window_thaw_toplevel_updates: assertion
'window->update_and_descendants_freeze_count > 0' failed
(mate-volume-control-status-icon:59859): Gtk-WARNING **: 19:58:21.546: Calling
gtk_widget_realize() on a widget that isn't inside a toplevel window is not
going to work very well. Widgets must be inside a toplevel container before
realizing them.
(mate-volume-control-status-icon:59859): GLib-GObject-CRITICAL **:
19:58:21.546: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(mate-volume-control-status-icon:59859): Gdk-CRITICAL **: 19:58:21.546:
gdk_window_get_scale_factor: assertion 'GDK_IS_WINDOW (window)' failed
**
Gtk:ERROR:../../../gtk/gtkwidget.c:5875:gtk_widget_get_frame_clock: assertion
failed: (window != NULL)
Bail out! Gtk:ERROR:../../../gtk/gtkwidget.c:5875:gtk_widget_get_frame_clock:
assertion failed: (window != NULL)
Thread 1 "mate-volume-con" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=, signo=signo@entry=6,
no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
44 ./nptl/pthread_kill.c: Aucun fichier ou dossier de ce type.
(gdb) bt full
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {140737340208256}}
ret =
#1 0x7702ad2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2 0x76fdbef2 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
ret =
#3 0x76fc6472 in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20},
sa_mask = {__val = {93824994969568, 140737488343016, 140737339441927,
93823560581168, 140733193388032, 93824994584288, 0, 93824997363264,
5024613291978080768, 140737339702443, 18446744073709551488, 11,
140737340210816, 140737348604049, 140737488343120, 140737340300128}}, sa_flags
= -150762193, sa_restorer = 0x77a3f133}
#4 0x7719eec8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x771fee1a in g_assertion_message_expr () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x77969d56 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#7 0x77978a6f in gtk_widget_realize () at
/lib/x86_64-linux-gnu/libgtk-3.so.0
#8 0x77978c68 in gtk_widget_map () at
/lib/x86_64-linux-gnu/libgtk-3.so.0
#9 0x776ccf80 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x7771ee5f in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#11 0x772cf4e0 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x772e8bbf in g_signal_emit_valist () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x772e8dbf in g_signal_emit () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x77978c12 in gtk_widget_map () at
/lib/x86_64-linux-gnu/libgtk-3.so.0
#15 0x77991d10 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#16 0x772cf5a9 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x772e8bbf in g_signal_emit_valist () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x772e8dbf in g_signal_emit () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x77978c12 in gtk_widget_map () at
/lib/x86_64-linux-gnu/libgtk-3.so.0
#20 0x7798786b in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#21 0x772cf3b0 in g_closure_invoke () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x772e1d2d in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x772e8bf5 in g_signal_emit_valist () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x772e8dbf in g_signal_emit () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x77972986 in gtk_widget_show () at
/lib/x86_64-linux-gnu/libgtk-3.so.0
#26 0x77924615 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#27 0x77924811 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#28 0x775277e7 in () at /lib/x86_64-linux-gnu/libgdk-3.so.0
#29 0x771d619a in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x771d567f in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x771d5a38 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x771d5cef in g_main_loop_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x778073e5 in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#34 0x9f33 in main ()
(gdb) c
Continuing.
Couldn't get registers: Aucun processus de ce type.
(gdb) [Thread 0x7fffe6c0 (LWP 67173) exited]
[Thread 0x7517e6c0 (LWP 59863) exited]
[Thread 0x7597f6c0 (LWP 59862) exited]
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
The program is not being run.
19 mars 2023 20:24 "Maxime G." a écrit:
> Hi.
>
> Issue
Bug#1033295: cairosvg: CVE-2023-27586: SSRF & DOS vulnerability
Source: cairosvg Version: 2.5.2-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for cairosvg. CVE-2023-27586[0]: | CairoSVG is an SVG converter based on Cairo, a 2D graphics library. | Prior to version 2.7.0, Cairo can send requests to external hosts when | processing SVG files. A malicious actor could send a specially crafted | SVG file that allows them to perform a server-side request forgery or | denial of service. Version 2.7.0 disables CairoSVG's ability to access | other files online by default. I am planning to look in the current bullseye version for a security upload, and can have a look as well for doing a NMU reaching bookworm. 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-tracker.debian.org/tracker/CVE-2023-27586 https://www.cve.org/CVERecord?id=CVE-2023-27586 [1] https://github.com/Kozea/CairoSVG/security/advisories/GHSA-rwmf-w63j-p7gv [2] https://github.com/Kozea/CairoSVG/commit/12d31c653c0254fa9d9853f66b04ea46e7397255 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1032554: h2o: FTBFS in testing: [h2o_mruby] in request:/:mruby raised: /tmp/UpqKGDqVnc:19: yeah! (RuntimeError)
El 21/3/23 a las 19:57, Chris Hofstaedtler escribió: it seems like its not 100% reproducible (in my builds at least). Hello. I can reproduce the FTBFS failure in a consistent way (i.e. not randomly but always) on three different kind of machines: Self-hosted VMs using kvm, VMs from GCP, and VMs from Hetzner. If you (or anybody else interested) want to debug this and it only fails randomly for you, please contact me privately and I can provide ssh access to a test machine where it happens always. This is my build history with all the machines combined: Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20220430T092608.165Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20220503T213948.786Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20220509T175008.611Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20220509T181241.653Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20221210T052645.088Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20221211T062519.570Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20221212T002906.924Z Status: successful h2o_2.2.5+dfsg2-6.2_amd64-20221212T004404.360Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230310T080600.446Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230310T081557.903Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230311T113541.485Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230311T215111.404Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230314T160532.877Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230314T160534.994Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230314T160639.774Z Status: failed h2o_2.2.5+dfsg2-6.2_amd64-20230314T160726.134Z One of the things which happened between 20221212 and 20230310 is that I started to use bookworm as the host OS for my VMs, so it could be the kernel. Thanks.
Bug#1032554: h2o: FTBFS in testing: [h2o_mruby] in request:/:mruby raised: /tmp/UpqKGDqVnc:19: yeah! (RuntimeError)
Hi Chris, thanks for your work! Please go ahead and upload without a delay. Please push your changes to git and tag it. Thanks and regards Anton Am Di., 21. März 2023 um 19:57 Uhr schrieb Chris Hofstaedtler < z...@debian.org>: > Hi, > > I will upload a change disabling the failing test to DELAYED/7. > Please let me know if I should cancel it. Debdiff attached. > > The failing mruby test might or might not point to a real problem, > it seems like its not 100% reproducible (in my builds at least). > I want src:h2o / libh2o to stay in bookworm so it can be used by > dnsdist; after bookworm I expect dnsdist upstream to switch away > from h2o, which itself seems upstream-dead. > > Thanks, > Chris > >
Bug#995156: marked as done (easy-rsa: vars Autodetection)
Your message dated Tue, 21 Mar 2023 19:04:00 + with message-id and subject line Bug#995156: fixed in easy-rsa 3.1.0-0.2 has caused the Debian Bug report #995156, regarding easy-rsa: vars Autodetection to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 995156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: easy-rsa Version: 3.0.8-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrading to Debian 11 * What exactly did you do (or not do) that was effective (or ineffective)? Creating new client cert * What was the outcome of this action? New cert whitout option from vars file * What outcome did you expect instead? New cert created with option from vars file. Before upgrade i've created cadir usign "make-cadir" which create some files and directory including a file named vars. Which i modified to my needs. After upgrade, options in this file were not used anymore (and the message "Note: using Easy-RSA configuration from: " were not displayed anymore). I've made some test, using make-cadir on Debian 11, a file named vars is still created but not used. I've made some research on vars Autodetection using /usr/share/doc/easy-rsa/doc/. Informations from EasyRSA-Advanced.md look identical from Debian 10 and Debian 11 about vars Autodetection : vars Autodetection A 'vars' file is a file named simply `vars` (without an extension) that Easy-RSA will source for configuration. This file is specifically designed *not* to replace variables that have been set with a higher-priority method such as CLI opts or env-vars. The following locations are checked, in this order, for a vars file. Only the first one found is used: 1. The file referenced by the `--vars` CLI option 2. The file referenced by the env-var named `EASYRSA_VARS_FILE` 3. The directory referenced by the `EASYRSA_PKI` env-var 4. The default PKI directory at `$PWD/pki` 4. The directory referenced by the `EASYRSA` env-var 5. The directory containing the easyrsa program Defining the env-var `EASYRSA_NO_VARS` will override the sourcing of the vars file in all cases, including defining it subsequently as a global option. I'm unsure 5. is still effective (or identical to previous version). Maybe i've missed warning about this change in https://metadata.ftp-master.debian.org/changelogs//main/e/easy-rsa/easy-rsa_3.0.8-1_changelog and i apologize for this. Regards, m.e. *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-cloud-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages easy-rsa depends on: ii openssl 1.1.1k-1+deb11u1 Versions of packages easy-rsa recommends: ii opensc 0.21.0-1 easy-rsa suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: easy-rsa Source-Version: 3.1.0-0.2 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of easy-rsa, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated easy-rsa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 Mar 2023 19:46:48 +0100 Source: easy-rsa Architecture: source Version: 3.1.0-0.2 Distribution: unstable Urgency: medium Maintainer: Michele Orrù Changed-By: Bastian Germann Closes: 995156 Changes: easy-rsa (3.1.0-0.2) unstable; urgency=medium . * Non-maintainer upload. * Upstream patch: Fix make-cadir (Closes: #995156). Checksums-Sha1:
Bug#1033230: marked as done (webkit2gtk: version 2.39.90-1 lost its libgles2 runtime dependency)
Your message dated Tue, 21 Mar 2023 19:06:18 +
with message-id
and subject line Bug#1033230: fixed in webkit2gtk 2.40.0-3
has caused the Debian Bug report #1033230,
regarding webkit2gtk: version 2.39.90-1 lost its libgles2 runtime dependency
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1033230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webkit2gtk
Version: 2.40.0-2
Severity: serious
Hello, for some reasons, now webkit2gtk is not linking anymore libGLESv2.so.2
causing surf to fail autopkgtests on arm64 and armhf
autopkgtest [05:16:23]: test command3: timeout -v 5m xvfb-run
debian/tests/test_text.sh
autopkgtest [05:16:23]: test command3: [---
(surf:7196): dbind-WARNING **: 05:16:24.536: AT-SPI: Error retrieving
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.a11y.Bus was not provided by any .service files
Could not determine the accessibility bus address
Could not read style file: /home/debci/.surf/styles/default.css
Couldn't open libGLESv2.so.2: libGLESv2.so.2: cannot open shared object file:
No such file or directory
web process terminated: crashed
Something is trying to load libGLESv2.so.2, but according to webkitgtk build
log, that library is now statically built inside webkitgtk?
What is really strange, the detection works, and then its statically built the
embedded one?
-- Found OpenGLES2: /usr/lib/aarch64-linux-gnu/libGLESv2.so (found version
"3.2")
[2681/6827] : && /usr/bin/cmake -E rm -f lib/libGLESv2.a && /usr/bin/ar crT lib/libGLESv2.a
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/egl_ext_stubs.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/egl_stubs.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/entry_points_egl_autogen.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/entry_points_egl_ext_autogen.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/entry_points_gles_1_0_autogen.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/entry_points_gles_2_0_autogen.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/entry_points_gles_3_0_autogen.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/entry_points_gles_3_1_autogen.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/entry_points_gles_3_2_autogen.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/entry_points_gles_ext_autogen.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/global_state.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/libGLESv2_autogen.cpp.o
Source/ThirdParty/ANGLE/CMakeFiles/GLESv2.dir/src/libGLESv2/proc_table_egl_autogen.cpp.o &&
/usr/bin/ranlib lib/libGLESv2.a && :
Why ANGLE did change its behaviour is unknown to me, and I find difficult to
understand if this is an upstream bug or a Debian specific one.
Gianfranco
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: webkit2gtk
Source-Version: 2.40.0-3
Done: Alberto Garcia
We believe that the bug you reported is fixed in the latest version of
webkit2gtk, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1033...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alberto Garcia (supplier of updated webkit2gtk package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 21 Mar 2023 18:11:48 +0100
Source: webkit2gtk
Architecture: source
Version: 2.40.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian WebKit Maintainers
Changed-By: Alberto Garcia
Closes: 1033230
Changes:
webkit2gtk (2.40.0-3) unstable; urgency=medium
.
* debian/{rules,control.in}:
- Add dependency on libgles2 on arm (Closes: #1033230).
Checksums-Sha1:
766ed0d8deea4009274c09123c3ee0bac5cffc79 5246 webkit2gtk_2.40.0-3.dsc
ed58747f9812c7f7c4c1830056bf9c24b102d2ca 80828
webkit2gtk_2.40.0-3.debian.tar.xz
c80ad18b7113096a77011fda000b900b909f158b 15156
Processed: tagging 1032554
Processing commands for cont...@bugs.debian.org: > tags 1032554 + pending Bug #1032554 [src:h2o] h2o: FTBFS in testing: [h2o_mruby] in request:/:mruby raised: /tmp/UpqKGDqVnc:19: yeah! (RuntimeError) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1032554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032554: h2o: FTBFS in testing: [h2o_mruby] in request:/:mruby raised: /tmp/UpqKGDqVnc:19: yeah! (RuntimeError)
Hi,
I will upload a change disabling the failing test to DELAYED/7.
Please let me know if I should cancel it. Debdiff attached.
The failing mruby test might or might not point to a real problem,
it seems like its not 100% reproducible (in my builds at least).
I want src:h2o / libh2o to stay in bookworm so it can be used by
dnsdist; after bookworm I expect dnsdist upstream to switch away
from h2o, which itself seems upstream-dead.
Thanks,
Chris
diff -Nru h2o-2.2.5+dfsg2/debian/changelog h2o-2.2.5+dfsg2/debian/changelog
--- h2o-2.2.5+dfsg2/debian/changelog2022-04-13 20:41:51.0 +
+++ h2o-2.2.5+dfsg2/debian/changelog2023-03-21 12:40:38.0 +
@@ -1,3 +1,11 @@
+h2o (2.2.5+dfsg2-7) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove VCS tags from picohttpparser source files
+ * Disable failing mruby test (Closes: #1032554)
+
+ -- Chris Hofstaedtler Tue, 21 Mar 2023 12:40:38 +
+
h2o (2.2.5+dfsg2-6.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru h2o-2.2.5+dfsg2/debian/patches/picohttpparser-vcstags.patch
h2o-2.2.5+dfsg2/debian/patches/picohttpparser-vcstags.patch
--- h2o-2.2.5+dfsg2/debian/patches/picohttpparser-vcstags.patch 1970-01-01
00:00:00.0 +
+++ h2o-2.2.5+dfsg2/debian/patches/picohttpparser-vcstags.patch 2023-03-21
12:40:38.0 +
@@ -0,0 +1,25 @@
+Remove expanded $Id$ strings, which seem to break building
+using h2o_2.2.5+dfsg2.orig.tar.xz from the archive.
+
+--- h2o-2.2.5+dfsg2.orig/deps/picohttpparser/picohttpparser.c
h2o-2.2.5+dfsg2/deps/picohttpparser/picohttpparser.c
+@@ -36,7 +36,7 @@
+ #endif
+ #include "picohttpparser.h"
+
+-/* $Id: a707070d11d499609f99d09f97535642cec910a8 $ */
++/* $Id$ */
+
+ #if __GNUC__ >= 3
+ #define likely(x) __builtin_expect(!!(x), 1)
+--- h2o-2.2.5+dfsg2.orig/deps/picohttpparser/picohttpparser.h
h2o-2.2.5+dfsg2/deps/picohttpparser/picohttpparser.h
+@@ -33,7 +33,7 @@
+ #define ssize_t intptr_t
+ #endif
+
+-/* $Id: 67fd3ee74103ada60258d8a16e868f483abcca87 $ */
++/* $Id$ */
+
+ #ifdef __cplusplus
+ extern "C" {
diff -Nru h2o-2.2.5+dfsg2/debian/patches/series
h2o-2.2.5+dfsg2/debian/patches/series
--- h2o-2.2.5+dfsg2/debian/patches/series 2022-04-13 20:41:51.0
+
+++ h2o-2.2.5+dfsg2/debian/patches/series 2023-03-21 12:40:38.0
+
@@ -5,3 +5,4 @@
link-libh2o-with-wslay.patch
fix_CVE-2019_1.patch
mruby_fileutils_no_verbose.patch
+picohttpparser-vcstags.patch
diff -Nru h2o-2.2.5+dfsg2/debian/rules h2o-2.2.5+dfsg2/debian/rules
--- h2o-2.2.5+dfsg2/debian/rules2022-04-13 20:41:51.0 +
+++ h2o-2.2.5+dfsg2/debian/rules2023-03-21 12:40:38.0 +
@@ -7,7 +7,7 @@
# Disable the following tests as they require network access
BAD_TESTS=10http1client 50access-log 50reverse-proxy-added-headers
50reverse-proxy-drop-headers 50reverse-proxy-https
50reverse-proxy-session-resumption 80invalid-h2-chars-in-headers 40server-push
50mruby-acl 80issues595 40max-connections 40session-ticket
# Disable test which fails with newer mruby
-BAD_TESTS += 50mruby-htpasswd
+BAD_TESTS += 50mruby-htpasswd 50mruby-http-request
%:
dh $@
Bug#1032884: marked as done (amanda-client: Amanda is unusable)
Your message dated Tue, 21 Mar 2023 18:49:12 + with message-id and subject line Bug#1032884: fixed in amanda 1:3.5.1-11 has caused the Debian Bug report #1032884, regarding amanda-client: Amanda 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 it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1032884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: amanda-client Version: 1:3.5.1-10 Severity: grave Justification: renders package unusable X-Debbugs-Cc: kjo...@poczta.onet.pl After recent update all my bacukups are unsuccessfull. Below log: sudo -u backup amstatus alfa Using: /var/lib/amanda/alfa/state/log/amdump.1 >From Mon Mar 13 13:10:37 CET 2023 alfa.kjonca:/etc 20230313131037 0 0k dump failed: [no backup size line] (13:10:46) SUMMARY dle real estimated size size - - disk: 1 estimated : 1 6044k flush dump failed : 1 6044k ( 0.00%) wait for dumping: 00k ( 0.00%) dumping to tape : 0 0k 0k ( 0.00%) ( 0.00%) dumping : 0 0k 0k ( 0.00%) ( 0.00%) dumped : 0 0k 0k ( 0.00%) ( 0.00%) wait for writing wait to flush writing to tape dumping to tape failed to tape taped 10 dumpers idle : no-dumpers network free kps: 8 holding space : 153600k (100.00%) chunker0 busy : 0:00:07 ( 75.41%) dumper0 busy: 0:00:04 ( 43.43%) 0 dumpers busy : 0:00:09 ( 99.80%) no-dumpers: 0:00:07 ( 76.31%) not-idle: 0:00:02 ( 23.69%) 1 dumper busy : 0:00:00 ( 0.13%) -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-6-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages amanda-client depends on: ii amanda-common 1:3.5.1-10 ii libc6 2.36-8 ii libglib2.0-02.74.6-1 ii libreadline88.2-1.3 ii libxml-simple-perl 2.25-2 ii perl5.36.0-7 amanda-client recommends no packages. Versions of packages amanda-client suggests: ii dump 0.4b47-4 ii gnuplot 5.4.4+dfsg1-2 ii gnuplot-qt [gnuplot] 5.4.4+dfsg1-2+b2 ii smbclient 2:4.17.6+dfsg-1 -- debconf-show failed --- End Message --- --- Begin Message --- Source: amanda Source-Version: 1:3.5.1-11 Done: Jose M Calhariz We believe that the bug you reported is fixed in the latest version of amanda, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1032...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jose M Calhariz (supplier of updated amanda package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 Mar 2023 17:35:47 + Source: amanda Architecture: source Version: 1:3.5.1-11 Distribution: unstable Urgency: medium Maintainer: Jose M Calhariz Changed-By: Jose M Calhariz Closes: 1032330 1032884 Changes: amanda (1:3.5.1-11) unstable; urgency=medium . * d/p/49-fix-CVE-2022-37705_part_2: 48-fix-CVE-2022-37705 broken one use case at least, this patch fix it, fixing the following two bugs. * Bug fix: "backups fail with the following summary FAILED [no backup size line]", thanks to Norman Lyon (Closes: #1032330). * Bug fix: "Amanda is unusable", thanks to Kamil Jonca (Closes: #1032884). Checksums-Sha1: 3c9147d428cdd09fdc3c8ca929169440ffecaecd 2216 amanda_3.5.1-11.dsc dd70deb0935f20f520f54f76692ce15d08f3cd7b 58920 amanda_3.5.1-11.debian.tar.xz 8b31b88a900fc348a08ff78530a9299825494460 14911 amanda_3.5.1-11_source.buildinfo Checksums-Sha256: f014f4de113115249cfd02e2a57a8a63dd532fd5cbe156fb2b6eb33ecff254fe 2216 amanda_3.5.1-11.dsc
Bug#1033280: marked as done (obs-worker: invalid syntax in systemd unit)
Your message dated Tue, 21 Mar 2023 17:04:17 + with message-id and subject line Bug#1033280: fixed in open-build-service 2.9.4-6 has caused the Debian Bug report #1033280, regarding obs-worker: invalid syntax in systemd unit to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1033280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: obs-worker Version: 2.9.4-5 Severity: grave Justification: renders package unusable While trying to use this package in production we found the systemd unit to use (unsupported) shell commands instead of the syntax systemd supports: systemd[1]: /lib/systemd/system/obsworker@.service:13: Executable "(cd" not found in path "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" systemd[1]: obsworker@0.service: Unit configuration has fatal error, unit will not be started. This prevents the package from being usable. --- End Message --- --- Begin Message --- Source: open-build-service Source-Version: 2.9.4-6 Done: Andrej Shadura We believe that the bug you reported is fixed in the latest version of open-build-service, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated open-build-service package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Mar 2023 17:50:16 +0100 Source: open-build-service Architecture: source Version: 2.9.4-6 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Andrej Shadura Closes: 1033280 Changes: open-build-service (2.9.4-6) unstable; urgency=medium . [ Debian Janitor ] * Apply multi-arch hints. + obs-productconverter: Add Multi-Arch: foreign. . [ Andrej Shadura ] * Rewrite the obsworker service unit to actually work (Closes: #1033280) * Restart the worker on failure automatically. * Only fix scripts in OBS package directories. * Add autopkgtest. Checksums-Sha1: 4d1e88c760a01662a907b5deaff07092a849d65a 1830 open-build-service_2.9.4-6.dsc aa3c9ad0776e122d5572ffb4e3577a22eddd15a0 22568 open-build-service_2.9.4-6.debian.tar.xz Checksums-Sha256: 912acc60c4dd945d015baf1cd7cbc7432de681daf565d54be275b210ede81b2b 1830 open-build-service_2.9.4-6.dsc e405da01bdc4292ce25f0b15fe6b08f3f76e9b89f30328dbd59ffce215a75b1b 22568 open-build-service_2.9.4-6.debian.tar.xz Files: 75958bcd5e59d1655ec6e109297131e3 1830 devel optional open-build-service_2.9.4-6.dsc 0da02572aabd194d31c6c7653f03a4b1 22568 devel optional open-build-service_2.9.4-6.debian.tar.xz -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCZBngsAAKCRDoRGtKyMdy YUQIAP0bWWN77xKqIjlGydw1vsWXX5YjyE2ADaeOrrAanqlcvAEA1uB0eIMJAB9q IBUx1+UFMOw4nPvQo82qYgnMhYyyWQ8= =i0fD -END PGP SIGNATURE End Message ---
Bug#1032989: Liferea 1.14.1-1 segfaults on startup when trying to read gsettings
Hi Paul, On Fri, Mar 17, 2023 at 09:49:31PM +0100, Paul Gevers wrote: > It seems upstream is on to something: > https://github.com/lwindolf/liferea/issues/1212#issuecomment-1472904260 Upstream issue 1212 is now closed and version 1.14.2 is released. I've built and tested two Liferea Debian packages: (1) the same as git tag debian/1.14.1-1, (2) the same as above, but with all upstream changes between 1.14.1 and 1.14.2[1] applied (except commit f04dae4ee0f54ac7ec630f35548aed4f31e2c5dc[2] which would cause the build to fail) as package patches, so technically version 1.14.2. Both segfault in the same place as I have originally reported. I think we can set "forwarded" to issue 1214[3] which seems to more clearly describe this specific crash. [1]: https://github.com/lwindolf/liferea/compare/v1.14.1...v1.14.2 [2]: https://github.com/lwindolf/liferea/commit/f04dae4ee0f54ac7ec630f35548aed4f31e2c5dc [3]: https://github.com/lwindolf/liferea/issues/1214 Thanks! -- Grzegorz signature.asc Description: PGP signature
Bug#1033230: webkit2gtk: version 2.39.90-1 lost its libgles2 runtime dependency
On Mon, Mar 20, 2023 at 01:29:51PM +0100, Gianfranco Costamagna wrote: > Hello, for some reasons, now webkit2gtk is not linking anymore > libGLESv2.so.2 causing surf to fail autopkgtests on arm64 and armhf Hmmm... the reason is that this is now handled via libepoxy, which opens libGLESv2.so.2 on runtime using dlopen(). I think that I'll add the dependencies manually for now, but I wonder if libepoxy should depend on those libraries instead? Berto
Processed: merging 1032558 1032045
Processing commands for cont...@bugs.debian.org: > merge 1032558 1032045 Bug #1032558 [src:tomopy] tomopy: autopkgtest failure on s390x: numerical differences Bug #1032045 [src:tomopy] tomopy: autopkgtest failure on s390x Merged 1032045 1032558 > thanks Stopping processing here. Please contact me if you need assistance. -- 1032045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032045 1032558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032547: facet-analyser: FTBFS in testing: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2
Le 08/03/2023 à 21:28, Lucas Nussbaum a écrit :
Source: facet-analyser
Version: 0.0~git20221121142040.6be10b8+ds1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230307 ftbfs-bookworm
Hi,
During a rebuild of all packages in testing (bookworm), your package failed
to build on amd64.
Hi,
I can't seem to reproduce this FTBFS with a bookworm cowbuilder. The
relevant part of the log (where the error used to be):
2/4 Test #4: basicExampleTest01 ... Passed 2.04 sec
2: Traceback (most recent call last):
2: File
"/build/facet-analyser-0.0~git20221121142040.6be10b8+ds1/scripts/pvsm2x3d.py",
line 73, in
2: main()
2: File
"/build/facet-analyser-0.0~git20221121142040.6be10b8+ds1/scripts/pvsm2x3d.py",
line 57, in main
2: exporters= pvs.servermanager.createModule("exporters")
2: ^^
2: AttributeError: module 'paraview.servermanager' has no attribute
'createModule'. Did you mean: 'updateModules'?
1: Traceback (most recent call last):
1: File
"/build/facet-analyser-0.0~git20221121142040.6be10b8+ds1/scripts/pvsm2webgl.py",
line 73, in
1: main()
1: File
"/build/facet-analyser-0.0~git20221121142040.6be10b8+ds1/scripts/pvsm2webgl.py",
line 57, in main
1: exporters= pvs.servermanager.createModule("exporters")
1: ^^
1: AttributeError: module 'paraview.servermanager' has no attribute
'createModule'. Did you mean: 'updateModules'?
3/4 Test #2: basicPluginTest02 ***Skipped 4.49 sec
4/4 Test #1: basicPluginTest01 ***Skipped 4.51 sec
100% tests passed, 0 tests failed out of 4
Attaching the full build log for reference. The difference may be in
either the versions of packages installed as build-dependencies, or in
the xvfb setup, since you get X server errors in your log.
If a rebuild on the testing buildds works, then I'd be grateful if you
could close this bug before facet-analyser gets AUTORMed from bookworm;
otherwise I'll be happy to help pinpoint (and fix) the root cause.
Roland.
Processed: tagging 1032392, tagging 1032038, tagging 1032041
Processing commands for cont...@bugs.debian.org:
> tags 1032392 + sid bookworm
Bug #1032392 [python3-scikit-rf] python3-scikit-rf: import fails:
AttributeError: module 'collections' has no attribute 'Sequence'
Added tag(s) sid and bookworm.
> tags 1032038 + sid bookworm
Bug #1032038 {Done: Martin } [src:picocom] picocom FTBFS on
mips64el/mipsel/sparc64
Added tag(s) bookworm and sid.
> tags 1032041 + sid bookworm
Bug #1032041 {Done: Emanuele Rocca } [src:arm-compute-library]
FTBFS: error: ‘size_t’ does not name a type
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1032038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032038
1032041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032041
1032392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026721: marked as done (knitpy: FTBFS: dh_install: error: missing files, aborting)
Your message dated Tue, 21 Mar 2023 13:19:01 + with message-id and subject line Bug#1026721: fixed in knitpy 0.1.1~git20180430-3 has caused the Debian Bug report #1026721, regarding knitpy: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: knitpy Version: 0.1.1~git20180430-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > dh_testdir > dh_testroot > python3.11 setup.py install \ > --prefix=/usr/ \ > --no-compile \ > --root=/<>/debian/tmp > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > running install_lib > creating /<>/debian/tmp > creating /<>/debian/tmp/usr > creating /<>/debian/tmp/usr/local > creating /<>/debian/tmp/usr/local/lib > creating /<>/debian/tmp/usr/local/lib/python3.11 > creating /<>/debian/tmp/usr/local/lib/python3.11/dist-packages > creating > /<>/debian/tmp/usr/local/lib/python3.11/dist-packages/knitpy > copying build/lib/knitpy/__init__.py -> > /<>/debian/tmp/usr//local/lib/python3.11/dist-packages/knitpy > copying build/lib/knitpy/knitpyapp.py -> > /<>/debian/tmp/usr//local/lib/python3.11/dist-packages/knitpy > copying build/lib/knitpy/documents.py -> > /<>/debian/tmp/usr//local/lib/python3.11/dist-packages/knitpy > copying build/lib/knitpy/py3compat.py -> > /<>/debian/tmp/usr//local/lib/python3.11/dist-packages/knitpy > copying build/lib/knitpy/knitpy.py -> > /<>/debian/tmp/usr//local/lib/python3.11/dist-packages/knitpy > copying build/lib/knitpy/encoding.py -> > /<>/debian/tmp/usr//local/lib/python3.11/dist-packages/knitpy > copying build/lib/knitpy/engines.py -> > /<>/debian/tmp/usr//local/lib/python3.11/dist-packages/knitpy > copying build/lib/knitpy/path.py -> > /<>/debian/tmp/usr//local/lib/python3.11/dist-packages/knitpy > copying build/lib/knitpy/utils.py -> > /<>/debian/tmp/usr//local/lib/python3.11/dist-packages/knitpy > running install_egg_info > running egg_info > creating knitpy.egg-info > writing knitpy.egg-info/PKG-INFO > writing dependency_links to knitpy.egg-info/dependency_links.txt > writing entry points to knitpy.egg-info/entry_points.txt > writing requirements to knitpy.egg-info/requires.txt > writing top-level names to knitpy.egg-info/top_level.txt > writing manifest file 'knitpy.egg-info/SOURCES.txt' > reading manifest file 'knitpy.egg-info/SOURCES.txt' > adding license file 'LICENSE.rst' > writing manifest file 'knitpy.egg-info/SOURCES.txt' > Copying knitpy.egg-info to > /<>/debian/tmp/usr//local/lib/python3.11/dist-packages/knitpy-0.1.1-py3.11.egg-info > running install_scripts > Installing knitpy script to /<>/debian/tmp/usr//local/bin > touch install-python3.11 > dh_testdir > dh_testroot > python3.10 setup.py install \ > --prefix=/usr/ \ > --no-compile \ > --root=/<>/debian/tmp > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > running install_lib > creating /<>/debian/tmp/usr/local/lib/python3.10 > creating /<>/debian/tmp/usr/local/lib/python3.10/dist-packages > creating > /<>/debian/tmp/usr/local/lib/python3.10/dist-packages/knitpy > copying build/lib/knitpy/__init__.py -> > /<>/debian/tmp/usr//local/lib/python3.10/dist-packages/knitpy > copying build/lib/knitpy/knitpyapp.py -> > /<>/debian/tmp/usr//local/lib/python3.10/dist-packages/knitpy > copying build/lib/knitpy/documents.py -> > /<>/debian/tmp/usr//local/lib/python3.10/dist-packages/knitpy > copying build/lib/knitpy/py3compat.py -> > /<>/debian/tmp/usr//local/lib/python3.10/dist-packages/knitpy > copying build/lib/knitpy/knitpy.py -> > /<>/debian/tmp/usr//local/lib/python3.10/dist-packages/knitpy > copying build/lib/knitpy/encoding.py -> > /<>/debian/tmp/usr//local/lib/python3.10/dist-packages/knitpy > copying build/lib/knitpy/engines.py -> > /<>/debian/tmp/usr//local/lib/python3.10/dist-packages/knitpy > copying
Processed: tagging 1032554
Processing commands for cont...@bugs.debian.org: > tags 1032554 + confirmed Bug #1032554 [src:h2o] h2o: FTBFS in testing: [h2o_mruby] in request:/:mruby raised: /tmp/UpqKGDqVnc:19: yeah! (RuntimeError) Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1032554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1032238 to src:linux, reassign 1033209 to apt, reassign 1033208 to apt, tagging 1032551 ...
Processing commands for cont...@bugs.debian.org:
> reassign 1032238 src:linux
Bug #1032238 {Done: Salvatore Bonaccorso }
[linux-image-6.1.0-5-amd64] linux-image-6.1.0-5-amd64: cryptsetup 2:2.6.1-1
password not recognized
Warning: Unknown package 'linux-image-6.1.0-5-amd64'
Bug reassigned from package 'linux-image-6.1.0-5-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #1032238 to the same values
previously set
Ignoring request to alter fixed versions of bug #1032238 to the same values
previously set
> reassign 1033209 apt 2.2.4
Bug #1033209 [apt-get] This info seems to have inadvertently been omitted from
the Debian Bug report logs
Warning: Unknown package 'apt-get'
Bug reassigned from package 'apt-get' to 'apt'.
No longer marked as found in versions 2.2.4.
Ignoring request to alter fixed versions of bug #1033209 to the same values
previously set
Bug #1033209 [apt] This info seems to have inadvertently been omitted from the
Debian Bug report logs
Marked as found in versions apt/2.2.4.
> reassign 1033208 apt 2.2.4
Bug #1033208 [apt-get] /etc/apt/sources.list
Warning: Unknown package 'apt-get'
Bug reassigned from package 'apt-get' to 'apt'.
Ignoring request to alter found versions of bug #1033208 to the same values
previously set
Ignoring request to alter fixed versions of bug #1033208 to the same values
previously set
Bug #1033208 [apt] /etc/apt/sources.list
Marked as found in versions apt/2.2.4.
> reassign 1033200 apt 2.2.4
Bug #1033200 [apt-get] apt, apt-get, aptitude and others have been failing for
an extended period.
Warning: Unknown package 'apt-get'
Bug reassigned from package 'apt-get' to 'apt'.
Ignoring request to alter found versions of bug #1033200 to the same values
previously set
Ignoring request to alter fixed versions of bug #1033200 to the same values
previously set
Bug #1033200 [apt] apt, apt-get, aptitude and others have been failing for an
extended period.
Marked as found in versions apt/2.2.4.
> reassign 1033124 src:linux
Bug #1033124 [kernel] kernel: Fails to rebuild initrd.img after firmware is
purged.
Warning: Unknown package 'kernel'
Bug reassigned from package 'kernel' to 'src:linux'.
No longer marked as found in versions 5.10.0-21-686-pae.
Ignoring request to alter fixed versions of bug #1033124 to the same values
previously set
> tags 1032551 - bookworm sid
Bug #1032551 {Done: Pirate Praveen } [src:ruby-kubeclient]
ruby-kubeclient: FTBFS in testing: ERROR: Test "ruby3.1" failed.
Removed tag(s) sid and bookworm.
> tags 983719 + experimental
Bug #983719 {Done: Faidon Liambotis } [esptool] Package is
severely outdated
Added tag(s) experimental.
> tags 1032557 - bookworm sid
Bug #1032557 {Done: Andreas Tille } [src:freebayes] libvcflib
breaks freebayes autopkgtest: Error: signal 11
Removed tag(s) bookworm and sid.
> tags 1005886 + sid bookworm
Bug #1005886 [debian-cd] debian-cd: bookworm net-install CD hangs on "Detecting
Network Hardware"
Added tag(s) bookworm and sid.
> reassign 966653 ruby-spamcheck
Bug #966653 {Done: Pirate Praveen } [ruby-grpc] gitlab:
[BUG] Segmentation fault at 0x
Bug reassigned from package 'ruby-grpc' to 'ruby-spamcheck'.
No longer marked as found in versions grpc/1.30.2-2.
No longer marked as fixed in versions
ruby-spamcheck/1.0.0+git20220819.662e6bf-2.
> fixed 966653 1.0.0+git20220819.662e6bf-2
Bug #966653 {Done: Pirate Praveen } [ruby-spamcheck]
gitlab: [BUG] Segmentation fault at 0x
Marked as fixed in versions ruby-spamcheck/1.0.0+git20220819.662e6bf-2.
> affects 966653 + src:gitlab
Bug #966653 {Done: Pirate Praveen } [ruby-spamcheck]
gitlab: [BUG] Segmentation fault at 0x
Added indication that 966653 affects src:gitlab
> notfixed 1005023 1:102.7.0-1
Bug #1005023 {Done: Carsten Schoenert } [thunderbird]
thunderbird subprocess (glxtest) dumps core on startup (with apparmor)
There is no source info for the package 'thunderbird' at version '1:102.7.0-1'
with architecture ''
Unable to make a source version for version '1:102.7.0-1'
No longer marked as fixed in versions 1:102.7.0-1.
> fixed 1005023 1:102.6.0-1
Bug #1005023 {Done: Carsten Schoenert } [thunderbird]
thunderbird subprocess (glxtest) dumps core on startup (with apparmor)
Marked as fixed in versions thunderbird/1:102.6.0-1.
> notfixed 685148 2.3
Bug #685148 {Done: Joachim Reichel } [cppcheck]
false positive: casting between pointer with incompatible binary data
representation
There is no source info for the package 'cppcheck' at version '2.3' with
architecture ''
Unable to make a source version for version '2.3'
No longer marked as fixed in versions 2.3.
> fixed 685148 2.3-1
Bug #685148 {Done: Joachim Reichel } [cppcheck]
false positive: casting between pointer with incompatible binary data
representation
Marked as fixed in versions cppcheck/2.3-1.
> reassign 1007981 src:cvc5
Bug #1007981 {Done: Scott Talbert } [src:cvc4] cvc4: Consider
upgrading to cvc5
Bug reassigned from package 'src:cvc4' to
Bug#1033243: [Pkg-puppet-devel] Bug#1033243: puppet: apt install puppet and puppet modules clash with official upstream repo
On 3/20/23 17:13, Renato Gallo wrote: Package: puppet Version: 7.23.0 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainers, At work I must install foreman and puppet using the official upstream repos for a testing environment which are cat puppet7.list # Puppet 7 bullseye Repository deb http://apt.puppetlabs.com bullseye puppet7 cat foreman.list deb http://deb.theforeman.org/ bullseye nightly deb http://deb.theforeman.org/ plugins nightly problem being that the puppet debian version is not 7.23.0 the upstream dep package has been named puppet7-release (not just puppet) and after having installed a module via apt I find myself in a broken condition where apt absolutely wants to install the old version of puppet (even when I try to uninstall it) which breaks the foreman nightly installation. Can you please I pray you upgrade the debian repo so that it follows the upstream one ? else can you tell me how can I set up my preferences so that only the upstream repo is considered ? I have tried setting priority 1001 but it doesn't seem to work for all the packages Thanks in advance Hi Renato, Thanks for your bug report. However... What you're reporting here, is an issue due to using upstream repository. In no way, this is a valid bug report for Debian (ie: the Debian repository and packages are working perfectly well). Therefore, I'm closing your bug. If you need help on how to setup and use upstream repositories, I strongly suggest you that you ask for such help upstream, or in another location than the bug tracker. If you think there's ways to improve the Debian packaging so that it plays in a nicer way with upstream repositories, this IMO is a case for a wishlist bug, absolutely not severity: grave. Cheers, Thomas Goirand (zigo)
Bug#1032914: phog: ships /etc/pam.d/greetd
Control: tags -1 + patch Hi, On Tue, 14 Mar 2023 00:20:10 +0100 Andreas Beckmann wrote: > > 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 bottom...): > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/phog/32130044/log.gz > > Preparing to unpack .../phog_0.1.3-1_amd64.deb ... > Unpacking phog (0.1.3-1) ... > dpkg: error processing archive /var/cache/apt/archives/phog_0.1.3-1_amd64.deb (--unpack): > trying to overwrite '/etc/pam.d/greetd', which is also in package greetd 0.9.0-2 > Errors were encountered while processing: > /var/cache/apt/archives/phog_0.1.3-1_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > greetd recently started to ship /etc/pam.d/greetd (with different > content) itself. Thanks for the heads-up! I have a pending MR for fixing this bug on phog's side (see https://salsa.debian.org/DebianOnMobile-team/phog/-/merge_requests/5), however this would require small changes to greetd as well (+cc duck for that matter) to ensure users don't end up in a messed up situation. I opened a MR on salsa's greetd (https://salsa.debian.org/debian/greetd/-/merge_requests/1), attaching the corresponding patches here as well for completeness. @duck, any comment on the above? Cheers, Arnaud > > > cheers, > > Andreas > > From eca07bda4c0b272ded196008c3d4528c756f5bb6 Mon Sep 17 00:00:00 2001 From: Arnaud Ferraris Date: Wed, 15 Mar 2023 13:51:11 +0100 Subject: [PATCH 1/3] debian: update PAM config(s) Except for the gnome-keyring bits, all items currently set in the `greetd` PAM config are already part of the `login` config. Including the latter makes the `greetd` config simpler. This commit also calls the PAM modules needed for unlocking the KDE wallet as well, and adds the `greetd-greeter` config (simply including `login` as the greeter itself doesn't need to deal with keyrings). Finally, switch to using debhelper for installing the configs instead of handling those manually. --- debian/greetd.greetd-greeter.pam | 2 ++ debian/greetd.greetd.pam | 8 debian/greetd.install| 1 - debian/pam.d/greetd | 22 -- debian/rules | 5 - 5 files changed, 14 insertions(+), 24 deletions(-) create mode 100644 debian/greetd.greetd-greeter.pam create mode 100644 debian/greetd.greetd.pam delete mode 100644 debian/pam.d/greetd diff --git a/debian/greetd.greetd-greeter.pam b/debian/greetd.greetd-greeter.pam new file mode 100644 index 000..1ed7162 --- /dev/null +++ b/debian/greetd.greetd-greeter.pam @@ -0,0 +1,2 @@ +#%PAM-1.0 +@include login diff --git a/debian/greetd.greetd.pam b/debian/greetd.greetd.pam new file mode 100644 index 000..7f2a906 --- /dev/null +++ b/debian/greetd.greetd.pam @@ -0,0 +1,8 @@ +#%PAM-1.0 +@include login + +-authoptionalpam_gnome_keyring.so +-authoptionalpam_kwallet5.so + +-session optionalpam_gnome_keyring.so auto_start +-session optionalpam_kwallet5.so auto_start diff --git a/debian/greetd.install b/debian/greetd.install index 0a3fbfb..83f2dad 100644 --- a/debian/greetd.install +++ b/debian/greetd.install @@ -1,4 +1,3 @@ greetd.service /lib/systemd/system/ config.toml /etc/greetd/ debian/needrestart/50_greetd.conf /etc/needrestart/conf.d/ -debian/pam.d/greetd /etc/pam.d/ diff --git a/debian/pam.d/greetd b/debian/pam.d/greetd deleted file mode 100644 index 062217b..000 --- a/debian/pam.d/greetd +++ /dev/null @@ -1,22 +0,0 @@ -#%PAM-1.0 - -# Block login if they are globally disabled -auth requisite pam_nologin.so - -# Load environment from /etc/environment and ~/.pam_environment -session required pam_env.so readenv=1 -session required pam_env.so readenv=1 envfile=/etc/default/locale - -@include common-auth - --auth optional pam_gnome_keyring.so - -@include common-account - -session requiredpam_limits.so -session requiredpam_loginuid.so -@include common-session - --session optionalpam_gnome_keyring.so auto_start - -@include common-password diff --git a/debian/rules b/debian/rules index 523b72b..1c1d9c5 100755 --- a/debian/rules +++ b/debian/rules @@ -30,10 +30,13 @@ execute_after_dh_install: # bad perms chmod a-x debian/greetd/lib/systemd/system/greetd.service +override_dh_installpam: + dh_installpam --name=greetd + dh_installpam --name=greetd-greeter + override_dh_installsystemd: dh_installsystemd --no-stop-on-upgrade --no-start execute_after_dh_auto_clean: make -C man clean rm -f debian/cargo-checksum.json - -- 2.39.1 From be90d0cb662cf94de32bbb95f9070a6127b25bef Mon Sep 17 00:00:00 2001 From: Arnaud Ferraris Date: Wed, 15 Mar 2023 13:52:39 +0100 Subject: [PATCH 2/3] d/control: break/replace older `phog` `phog` used to ship the `greetd` and `greetd-greeter` PAM configs, leading to conflicts with the
Processed: Re: Bug#1032914: phog: ships /etc/pam.d/greetd
Processing control commands: > tags -1 + patch Bug #1032914 [phog] phog: ships /etc/pam.d/greetd Added tag(s) patch. -- 1032914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033280: obs-worker: invalid syntax in systemd unit
Package: obs-worker Version: 2.9.4-5 Severity: grave Justification: renders package unusable While trying to use this package in production we found the systemd unit to use (unsupported) shell commands instead of the syntax systemd supports: systemd[1]: /lib/systemd/system/obsworker@.service:13: Executable "(cd" not found in path "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" systemd[1]: obsworker@0.service: Unit configuration has fatal error, unit will not be started. This prevents the package from being usable.
Bug#1033044: daily cron job broken?
Never broken
On Thu, Mar 16, 2023, 5:45 AM Marc Haber
wrote:
> Package: aide-common
> Version: 0.18.1-1
> Severity: grave
> Tags: confirmed
>
> Justification: Maintainer discretion, cron job broken
>
> diff --git a/debian/bin/dailyaidecheck b/debian/bin/dailyaidecheck
> index aa4b59c..fbd0a57 100755
> --- a/debian/bin/dailyaidecheck
> +++ b/debian/bin/dailyaidecheck
> @@ -161,7 +161,7 @@ FILTERUPDATES="${FILTERUPDATES:-no}"
> FILTERINSTALLATIONS="${FILTERINSTALLATIONS:-no}"
> CRONEXITHOOK="${CRONEXITHOOK:-}"
> ONEXIT=""
> -AIDEUSER="${AIDEUSER:-root}"
> +AIDEUSER="${AIDEUSER:-$(id --user --name)}"
> AIDEUSERUID="$(id --user "${AIDEUSER}")"
>
> # silent implies quiet
>
> And upload will follow shortly.
>
> Greetings
> Marc, Maintainer
>
>
Bug#1033243: puppet: apt install puppet and puppet modules clash with official upstream repo
Just to see what am I failing, Can you please tell me what would you put into apt preferences and even elsewhere to be positively sure I am NOT using the puppet/foreman debian packages ? Thank you in advance On Mon, 20 Mar 2023 13:39:33 -0400 =?UTF-8?Q?Louis-Philippe_V=c3=a9ronneau?= wrote: > tags 1033243 wontfix > thanks > > Hello, > > Generally, the Puppet ecosystem as packaged in the Debian archive isn't > compatible with the upstream repositories and we currently don't plan to > fix this. > > Files are not installed in the same directories, versions won't be the > same and you'll experience weird breakage, like the one you seem to have. > > If you absolutely need to use upstream's repositories, I would thus > recommend you don't use any of the Debian packages. > > If you want to keep using the Debian packages and you need Puppet > modules that aren't packaged in the Debian, a more common workflow would > be to use the Debian packages, but download Puppet modules either > "manually" via git or from the Puppet forge. > > -- >⢀⣴⠾⠻⢶⣦⠀ >⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau >⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org >⠈⠳⣄
Processed: Re: [Pkg-javascript-devel] Bug#1033250: Bug#1033250: node-request: CVE-2023-28155
Processing control commands: > block -1 by 956423 Bug #1033250 [src:node-request] node-request: CVE-2023-28155 1033250 was not blocked by any bugs. 1033250 was not blocking any bugs. Added blocking bug(s) of 1033250: 956423 -- 1033250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
