Bug#1025066: gimp: Segmentation fault when editing a text box on the picture

2022-12-15 Thread Patrik Svestka
Hello Bernhard,

I think the text was the following [containing Czech characters]:

"Ahoj, já se jmenuji Sam a ty se jmenuješ jak?  Máš takový krásný
kožíšek, že Ti v něm musí být teď pěkně teploučko.  Ta bačkůrka v které
ležíš má stejnou barvu jako já."

When I tried again it did not crash as I have finished editing the
whole picture.

The actions taken: I have placed a text tool field over a picture
(backround) which has created its own layer (with text tool icon left
of the layer's name) where I have entered the text.  After the text
tool field was created I started typing the text and then it crashed.

Best regards,

Patrik

On Mon, 2022-12-12 at 12:03 +0100, Bernhard Übelacker wrote:
> Hello Patrik,
> I just tried to collect some information and reconstruct
> the given backtrace with some line information [1].
> 
> This gimp_text_tool_move_cursor leads to this upstream
> bug reports [2]. Unfortunately all closed without result.
> 
> There are a few more upstream reports with g_utf8_get_char [3],
> all with some non-latin characters, but all seem not
> reproducible.
> 
> @Patrik, can you provide the text you wanted to enter?
> Had it contained some "special" e.g. non-latin characters?
> When you try it again, does it crash again?
> If yes, maybe describe exactly the actions shortly before the crash?
> 
> Kind regards,
> Bernhard
> 
> 
> 
> [1]
>     #7  0x7fbc1a3819a0 in g_utf8_get_char at
> ../../../glib/gutf8.c:336 at libglib-2.0.so.0
>     #8  0x55928b983ae0 in gimp_text_tool_move_cursor at
> ./app/tools/gimptexttool-editor.c:900 at gimp
>     #9  0x7fbc1a4463b0 in in g_closure_invoke at
> ../../../gobject/gclosure.c:832 at libgobject-2.0.so.0
>     #10 0x7fbc1a459076 in signal_emit_unlocked_R at
> ../../../gobject/gsignal.c:3796 at libgobject-2.0.so.0
> 
>    
> https://sources.debian.org/src/glib2.0/2.74.2-1/glib/gutf8.c/#L336
>     335   gunichar result;
>     336   unsigned char c = (unsigned char) *p;
>     337
> 
>    
> https://sources.debian.org/src/gimp/2.10.32-1/app/tools/gimptexttool-editor.c/#L900
>     899   if (new_index != -1 && new_index !=
> G_MAXINT &&
>     900   g_utf8_get_char (text + new_index) ==
> word_joiner)
>     901 {
> 
> 
> [2]
>     https://gitlab.gnome.org/GNOME/gimp/-/issues/7019
>     https://gitlab.gnome.org/GNOME/gimp/-/issues/4408
>     https://gitlab.gnome.org/GNOME/gimp/-/issues/3960
>     https://gitlab.gnome.org/GNOME/gimp/-/issues/3643
>     https://gitlab.gnome.org/GNOME/gimp/-/issues/3460
> 
> [3]
>     https://gitlab.gnome.org/GNOME/gimp/-/issues/6468
>     https://gitlab.gnome.org/GNOME/gimp/-/issues/6704
>     https://gitlab.gnome.org/GNOME/gimp/-/issues/6794



Bug#1025930: transition: openvdb

2022-12-15 Thread Mathieu Malaterre
> openvdb 10.0 is available in experimental (except mipsel):

openvdb 10.0 is now available in experimental (including mipsel):

https://buildd.debian.org/status/package.php?p=openvdb=experimental

Thanks



Bug#1026203: RM: ruby-omniauth-azure-oauth2 -- ROM; upstream inactive

2022-12-15 Thread Mohammed Bilal
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: mdbi...@disroot.org

Hello,

The upstream for ruby-omniauth-azure-oauth2 is no longer maintained[1] and the 
only reverse-dep gitlab uses its own fork of the gem. So I think we can remove 
this gem from the archive.

[1] - 
https://github.com/marknadig/omniauth-azure-oauth2/commit/58ccf0f26e74325c70f2257615023e2b5a7ace20
[2] - 
https://gitlab.com/gitlab-org/gitlab/-/tree/master/vendor/gems/omniauth-azure-oauth2

Thanks,
Mohd Bilal



Bug#1026202: RM: ruby-omniauth-cas3 -- ROM; upstream inactive

2022-12-15 Thread Mohammed Bilal
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: mdbi...@disroot.org

Hello,

The upstream for ruby-omniauth-cas3 has archived the project[1] and is no 
longer maintained.Moreover the only reverse-dependency gitlab uses their own 
fork[2] of the gem. So I think we can remove this package from the archive

[1] - https://github.com/tduehr/omniauth-cas3
[2] - 
https://gitlab.com/gitlab-org/gitlab/-/tree/master/vendor/gems/omniauth-cas3

Thanks,
Mohd Bilal



Bug#1025931: RM: openvdb [mipsel] -- ROM; FTBFS on mipsel

2022-12-15 Thread Mathieu Malaterre
Control: tags -1 wontfix

On Mon, Dec 12, 2022 at 1:09 PM Scott Kitterman  wrote:
>
> On Mon, 12 Dec 2022 08:31:18 +0100 Mathieu Malaterre  wrote:
> > Package: ftp.debian.org
> > Severity: normal
> >
> > I'd like to request the removal of openvdb on mipsel. I've tried
> > multiple times to get the latest release to build on the mipsel buildd
> > machines without no luck so far.
> >
> > The 13 attempts can be seen in the experimental section:
> >
> > * https://buildd.debian.org/status/logs.php?pkg=openvdb=mipsel
> >
> > debian-mips porters have remained silent about those repeated build
> > failures due to limited RAM on buildds.
> >
> > * https://lists.debian.org/debian-mips/2022/12/msg3.html
> > * https://lists.debian.org/debian-mips/2022/12/msg0.html
> > * https://lists.debian.org/debian-mips/2022/11/msg0.html
>
> There are rdepends that need to be addressed first:
>
> Checking reverse dependencies...
> # Broken Depends:
> openimageio: libopenimageio2.3
>
> Please remove the moreinfo tag once that's been addressed.

I've reduced the mipsel binary package and it seems to pass now:

* https://buildd.debian.org/status/package.php?p=openvdb=experimental

Closing for now.

Thanks and sorry for the noise.



Bug#1026201: gcc-13: Please drop build dependency on gdc-12 on unsupported D targets

2022-12-15 Thread John Paul Adrian Glaubitz
Source: gcc-13
Version: 13-20221214-1
Severity: normal

Hello!

Both gcc-snapshot and gcc-13 have a build-dependency on gdc-12 which we
haven't enabled on most ports architectures.

Could this build dependency be dropped for the architectures that are
BD-Uninstallable for gcc-13 [1] and gcc-snapshot [2]? We don't really
need D language support in Debian Ports as the language has no standard
library support for most architectures.

Thanks,
Adrian

> [1] https://buildd.debian.org/status/package.php?p=gcc-13=experimental
> [2] https://buildd.debian.org/status/package.php?p=gcc-snapshot=sid

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#920897: SPICE session's connection_id's are not unique

2022-12-15 Thread Michael Tokarev

Control: tag -1 + wontfix

..

Accoring to upstream, this is either not a bug or even if this is "fixed",
it is not sufficient to distinguish different connections from _different_
spice servers.

So I'm not really sure what to do here. To me this is notabug. Opinions?


It's been almost 4 years. Let's mark it "wontfix" until more info comes.

/mjt



Bug#1003648: Reassign

2022-12-15 Thread Anton Gladky
reassign 1003648 php-horde-prefs/2.9.0-8
thanks

The warning is in Prefs.php, which is in package php-horde-prefs.
Some other packages can be affected

Anton



Bug#1023697: Keep out of testing

2022-12-15 Thread Vincent Bernat

On Thu, 10 Nov 2022 22:45:57 +0100 Bastian Germann  wrote:

As a new maintainer has stepped up, this cannot be the reason anymore to dump 
the package.
Actually, with the next version of swupdate (one of those handful) I wanted to 
switch from OpenSSL
to SWUpdate.


As there are no real plan to provide QUIC support in OpenSSL 3 and the 
performance regressions of OpenSSL 3 are quite important, I may also 
switch HAProxy to WolfSSL.




Bug#1026174: linux: Please enable CONFIG_X86_SGX_KVM=y

2022-12-15 Thread Salvatore Bonaccorso
Hi,

On Thu, Dec 15, 2022 at 10:54:22PM +0100, Wojtek Porczyk wrote:
> Source: linux
> Severity: normal
> 
> Dear Maintainer,
> 
> Please consider CONFIG_X86_SGX_KVM=y config option. This option enables using
> SGX inside KVM virtual machines. Support for this landed in qemu around 7.0
> (I don't recall the exact version) and in libvirt 8.10.

So I assume with libvirt 8.10. beeing in bookworm as well in
meanwhile, the whole stack is functional/working? Out of interest, you
were able to test it?

Regards,
Salvatore



Bug#562765: Cheese segfault continues in Debian 11.5, i386. =8~/

2022-12-15 Thread peter
An old Dell Dimension 4600 and a Logitech M/N: V-U0006, 
P/N: 860-000177, PID: LZ944BN USB camera here.

A release or two back, cheese worked. =8~)

Now, without the camera plugged, cheese starts and appears OK.  If the 
preferences window is open, it shows "UVC Camera (046d:0807)".  No 
image appears. =8~/

With the camera plugged, cheese displays the window for no more than a 
few ms.  A good old seg fault results. =8~/

root@joule:~# cheese
Xlib: sequence lost (0x100a9 > 0xab) in reply type 0x0!
Segmentation fault

I can try to respond to any request for more specific information.

Thx,  ... P.




mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
https://en.wikibooks.org/wiki/User:PeterEasthope



Bug#1026200: Please package LilyPond 2.24.0 if possible

2022-12-15 Thread John Zaitseff
Package: lilypond
Severity: wishlist

I know it's a lot to ask for :-), but now that LilyPond 2.24.0 has
been released, it would be good to have it in Debian.  Let me know
if I can help bring this about!

Yours truly,

John Zaitseff

-- 
John Zaitseff   ╭───╮   Email: j.zaits...@zap.org.au
The ZAP Group   │ Z │   GnuPG: 0x0D254111C4EE569B
Australia Inc.  ╰───╯   https://www.zap.org.au/~john/



Bug#1025140: Re: Bug#1025140: diffutils: define SIGSEGV_FAULT_STACKPOINTER for loongarch

2022-12-15 Thread 张丹丹

Hi,maintainers,
> Hello. I believe you need a similar change for m4.
> Please submit a bug for m4 as well.
> 
I have added a change for m4.
Please consider it.

thanks,
Dandan Zhang


本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件通知发件人并删除本邮件。
 
This email and its attachments contain confidential information from Loongson 
Technology , which is intended only for the person or entity whose address is 
listed above. Any use of the information contained herein in any way 
(including, but not limited to, total or partial disclosure, reproduction or 
dissemination) by persons other than the intended recipient(s) is prohibited. 
If you receive this email in error, please notify the sender by phone or email 
immediately and delete it. 

diffutils-3.8-add-loongarch-define-and-m4-support.patch
Description: Binary data


Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language

2022-12-15 Thread Nick Hastings
Hi,

quick update.

* Nick Hastings  [221215 14:40]:

> * Bastian Germann  [221215 08:57]:
>
> > Your package fails to build from scratch on amd64 with a test fail 
> > (maybecaused by wrong pwd?):
> >
> > [100%] Built target zig
> > make[2]: Leaving directory '/home/bage/zig-0.9.1/obj-x86_64-linux-gnu'
> > /usr/bin/cmake -E cmake_progress_start 
> > /home/bage/zig-0.9.1/obj-x86_64-linux-gnu/CMakeFiles 0
> > make[1]: Leaving directory '/home/bage/zig-0.9.1/obj-x86_64-linux-gnu'
> >debian/rules override_dh_auto_test
> > make[1]: Entering directory '/home/bage/zig-0.9.1'
> > ./debian/zig/usr/bin/zig build test-fmt || exit 1; ./debian/zig/usr/bin/zig
> > build test-behavior || exit 1; ./debian/zig/usr/bin/zig build
> > test-compiler-rt || exit 1; ./debian/zig/usr/bin/zig build test-minilibc ||
> > exit 1; ./debian/zig/usr/bin/zig build test-compare-output || exit 1;
> > ./debian/zig/usr/bin/zig build test-standalone || exit 1;
> > ./debian/zig/usr/bin/zig build test-stack-traces || exit 1;
> > ./debian/zig/usr/bin/zig build test-cli || exit 1; ./debian/zig/usr/bin/zig
> > build test-asm-link || exit 1; ./debian/zig/usr/bin/zig build
> > test-runtime-safety || exit 1; ./debian/zig/usr/bin/zig build
> > test-translate-c || exit 1; ./debian/zig/usr/bin/zig build
> > test-run-translated-c || exit 1; ./debian/zig/usr/bin/zig build test-std ||
> > exit 1;
> > /bin/sh: 1: ./debian/zig/usr/bin/zig: not found
> > make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1
> > make[1]: Leaving directory '/home/bage/zig-0.9.1'
> > make: *** [debian/rules:8: binary] Error 2
> 
> I don't know why that is. It works for me on amd64 on unstable
> (bullseye with backports). I do recall that someone on #mentors had
> issues building it using sbuild at some point. But at least 3 or 4
> others did not: success was reported with both pbuilder and sbuild.

I updated my unstable chroot and now build the fails in this way for me
too. I will investigate.

Cheers,

Nick.



Bug#1026199: release.debian.org: Is the toolchain list updated for bookworm

2022-12-15 Thread Sam Hartman
Package: release.debian.org
Severity: normal



I was looking at 
https://release.debian.org/testing/essential-and-build-essential.txt

trying to figure out which packages I'm involved in are covered by the
toolchain freeze.  I am wondering what's still pulling
libgssapi-krb5-2 and friends into build-essential.  It used to be
pulled in via pam via libtirpc, but that should have gone away with
the pam upload of 1.4.0-13.


I'm wondering if that list hasn't been recently updated or if there's some 
other dependency cycle pulling in krb5?

Thanks for your consideration,

--Sam



Bug#1026087: ITP: distribution-gpg-keys -- GPG keys by various Linux distributions

2022-12-15 Thread debian
Hi!

On Thu, Dec 15, 2022 at 03:12:21PM +0100, Guillem Jover wrote:
> The project name talks about gpg keys, but those are really OpenPGP
> keys (or even better, certificates). I've asked upstream to rename the
> project to avoid this common confusion. So you might want to wait until
> that's settled to avoid multiple trips over NEW.
> 
>   
Thank you very much! I liked this issue on github and waiting for
upstream reply.
> 
> (If this project is also intended to only cover RPM-based distributions,
> as Adam brought up, you might want to further ask them to make that clear
> from the project name, say rpm-distribution-openpgp-keys or similar. But
> in any case regardless of the intended target use, it still seems like a
> very generic name which can be easily confused for a package that would
> be needed for Debian, or derivatives.)
Mainly for mock we just need keys for rpm-based
distributions/repositories. On the other way we have
extrepo-offline-data package where are repository keys for 3rd party debian 
repositories. Also maybe it's better to have extern PGP keys on one place.
What do you think about it?

Best Regards,
Juri Grabowski



Bug#1026198: ruby-webpack-rails: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-webpack-rails
Version: 0.9.11+git-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby

[... snipped ...]


TZInfo::DataSourceNotFound:
  tzinfo-data is not present. Please add gem 'tzinfo-data' to your Gemfile and 
run bundle install
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# /<>/spec/spec_helper.rb:13:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# /<>/spec/manifest_spec.rb:1:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `block in load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.

Finished in 0.7 seconds (files took 1.34 seconds to load)
0 examples, 0 failures, 2 errors occurred outside of examples

/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format documentation failed
mv ./.gem2deb.Gemfile.lock Gemfile.lock
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/ruby-webpack-rails-0.9.11\+git/debian/ruby-webpack-rails returned 
exit code 1
make: *** [debian/rules:6: binary-indep] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for 

Bug#1026197: ruby-webpacker: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-webpacker
Version: 5.4.3-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-webpacker/ -i -O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from /<>/test/test_app/config/environment.rb:4:in `'
from /<>/test/test_helper.rb:7:in `require_relative'
from /<>/test/test_helper.rb:7:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/command_test.rb:1:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
rake aborted!
Command failed with status (1): [ruby -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/command_test.rb" 
"test/compiler_test.rb" "test/configuration_test.rb" "test/dev_server_test.rb" "test/env_test.rb" "test/helper_test.rb" 
"test/manifest_test.rb" "test/rake_tasks_test.rb" "test/webpacker_test.rb"  -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
mv ./.gem2deb.Gemfile.lock Gemfile.lock
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-webpacker returned exit code 1
make: *** [debian/rules:8: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026196: ruby-voight-kampff: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-voight-kampff
Version: 1.1.3-4
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-voight-kampff/ -i -O--buildsystem=ruby

[... snipped ...]

# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
# 
/usr/share/rubygems-integration/all/gems/combustion-1.3.7/lib/combustion.rb:56:in
 `initialize!'
# ./spec/spec_helper.rb:6:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# ./spec/lib/voight_kampff_spec.rb:1:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `block in load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.

Finished in 0.6 seconds (files took 0.86722 seconds to load)
0 examples, 0 failures, 4 errors occurred outside of examples

/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format documentation failed
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-voight-kampff returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me 

Bug#1026195: ruby-sprockets-rails: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-sprockets-rails
Version: 3.4.1-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-sprockets-rails/ -i 
-O--buildsystem=ruby

[... snipped ...]

TZInfo::DataSourceNotFound: tzinfo-data is not present. Please add gem 
'tzinfo-data' to your Gemfile and run bundle install

/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'

/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'

/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'

/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'

/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'

/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
/usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:431:in `each_strongly_connected_component_from'
/usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
/usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
/<>/test/test_quiet_assets.rb:28:in `setup'

rails test <>/test/test_quiet_assets.rb:42


Finished in 7.276513s, 22.5383 runs/s, 92.9016 assertions/s.
164 runs, 676 assertions, 0 failures, 29 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/test_asset_url_processor.rb" "test/test_helper.rb" "test/test_quiet_assets.rb" "test/test_railtie.rb" 
"test/test_sourcemapping_url_processor.rb" "test/test_task.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-sprockets-rails returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026194: ruby-sassc-rails: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-sassc-rails
Version: 2.1.2-6
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-sassc-rails/ -i -O--buildsystem=ruby

[... snipped ...]

railties (6.1.7) lib/rails/railtie.rb:207:in `method_missing'
<>/test/sassc_rails_test.rb:43:in `initialize!'
<>/test/sassc_rails_test.rb:122:in 
`test_sass_imports_work_correctly'
minitest (5.14.2) lib/minitest/test.rb:98:in `block (3 levels) in run'
minitest (5.14.2) lib/minitest/test.rb:195:in `capture_exceptions'
minitest (5.14.2) lib/minitest/test.rb:95:in `block (2 levels) in run'
minitest (5.14.2) lib/minitest.rb:272:in `time_it'
minitest (5.14.2) lib/minitest/test.rb:94:in `block in run'
minitest (5.14.2) lib/minitest.rb:367:in `on_signal'
minitest (5.14.2) lib/minitest/test.rb:211:in `with_info_handler'
minitest (5.14.2) lib/minitest/test.rb:93:in `run'
minitest (5.14.2) lib/minitest.rb:1029:in `run_one_method'
minitest (5.14.2) lib/minitest.rb:341:in `run_one_method'
minitest (5.14.2) lib/minitest.rb:328:in `block (2 levels) in run'
minitest (5.14.2) lib/minitest.rb:327:in `each'
minitest (5.14.2) lib/minitest.rb:327:in `block in run'
minitest (5.14.2) lib/minitest.rb:367:in `on_signal'
minitest (5.14.2) lib/minitest.rb:354:in `with_info_handler'
minitest (5.14.2) lib/minitest.rb:326:in `run'
minitest (5.14.2) lib/minitest.rb:164:in `block in __run'
minitest (5.14.2) lib/minitest.rb:164:in `map'
minitest (5.14.2) lib/minitest.rb:164:in `__run'
minitest (5.14.2) lib/minitest.rb:141:in `run'
minitest (5.14.2) lib/minitest.rb:68:in `block in autorun'

rails test /<>/test/sassc_rails_test.rb:120


Finished in 0.144429s, 138.4761 runs/s, 0. assertions/s.
20 runs, 0 assertions, 0 failures, 18 errors, 2 skips
rake aborted!
Command failed with status (1): [ruby -w -I"test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/sassc_rails_test.rb" "test/test_helper.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-sassc-rails returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026193: ruby-rails-controller-testing: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-rails-controller-testing
Version: 1.0.5-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-rails-controller-testing/ -i 
-O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from /<>/test/dummy/config/environment.rb:5:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/test_helper.rb:4:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/controllers/assigns_test.rb:1:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
rake aborted!
Command failed with status (1): [ruby -w -I"test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/controllers/assigns_test.rb" 
"test/controllers/template_assertions_test.rb" "test/helpers/template_assertions_test.rb" 
"test/integration/template_assertions_test.rb" "test/test_helper.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-rails-controller-testing returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026192: ruby-pry-rails: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-pry-rails
Version: 0.3.9-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-pry-rails/ -i -O--buildsystem=ruby

[... snipped ...]

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
/<>/spec/config/environment.rb:23:in `'
:85:in 
`require'
:85:in 
`require'
/<>/debian/ruby-tests.rake:25:in `block in '
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'

Caused by:
TZInfo::DataSources::ZoneinfoDirectoryNotFound: None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `new'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `create_default_data_source'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
/<>/spec/config/environment.rb:23:in `'
:85:in 
`require'
:85:in 
`require'
/<>/debian/ruby-tests.rake:25:in `block in '
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default => test => console => development_env
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-pry-rails returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026191: ruby-omniauth-rails-csrf-protection: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-omniauth-rails-csrf-protection
Version: 1.0.1-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-omniauth-rails-csrf-protection/ -i 
-O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from /<>/test/test_helper.rb:56:in `'
from /<>/test/test_helper.rb:34:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/application_test.rb:1:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
Running test against Rails 6.1.7
rake aborted!
Command failed with status (1): [ruby -w -I"test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/application_test.rb" "test/test_helper.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-omniauth-rails-csrf-protection returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026190: ruby-joiner: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-joiner
Version: 0.6.0-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-joiner/ -i -O--buildsystem=ruby

[... snipped ...]

# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
# 
/usr/share/rubygems-integration/all/gems/combustion-1.3.7/lib/combustion.rb:56:in
 `initialize!'
# ./spec/spec_helper.rb:7:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# ./spec/acceptance/paths_spec.rb:1:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `block in load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.


Finished in 0.6 seconds (files took 0.81624 seconds to load)
0 examples, 0 failures, 2 errors occurred outside of examples

/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-joiner 
returned exit code 1
make: *** [debian/rules:8: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, 

Bug#1026189: ruby-invisible-captcha: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-invisible-captcha
Version: 1.1.0-5
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-invisible-captcha/ -i 
-O--buildsystem=ruby

[... snipped ...]

An error occurred while loading spec_helper.
Failure/Error: Rails.application.initialize!

TZInfo::DataSourceNotFound:
  tzinfo-data is not present. Please add gem 'tzinfo-data' to your Gemfile and 
run bundle install
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# ./spec/dummy/config/environment.rb:5:in `'
# ./spec/spec_helper.rb:5:in `'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.
No examples found.


Finished in 0.7 seconds (files took 0.90923 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

Finished in 0.7 seconds (files took 0.90923 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples


/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format documentation failed
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-invisible-captcha returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026188: ruby-haml: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-haml
Version: 5.2.2-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
dh_ruby --build
yard && mv doc yardoc
[warn]: @param tag has unknown parameter name: new
in file `lib/haml/parser.rb' near line 215
[warn]: @param tag has unknown parameter name: old

[... snipped ...]

from debian/ruby-tests.rb:7:in `'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize': None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories. (TZInfo::DataSources::ZoneinfoDirectoryNotFound)
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `new'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `create_default_data_source'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from /<>/test/test_helper.rb:32:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/attribute_parser_test.rb:3:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from debian/ruby-tests.rb:7:in `block in '
from debian/ruby-tests.rb:7:in `each'
from debian/ruby-tests.rb:7:in `'
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-haml 
returned exit code 1
make[1]: *** [debian/rules:15: override_dh_auto_install] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026187: ruby-globalid: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-globalid
Version: 0.6.0-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-globalid/ -i -O--buildsystem=ruby

[... snipped ...]

Error:
RailtieTest#test_GlobalID.app_for_Blog::Application_defaults_to_blog:
TZInfo::DataSourceNotFound: tzinfo-data is not present. Please add gem 
'tzinfo-data' to your Gemfile and run bundle install
test/cases/railtie_test.rb:22:in `block in '

rails test test/cases/railtie_test.rb:21

E

Error:
RailtieTest#test_SignedGlobalID.verifier_defaults_to_Blog::Application.message_verifier(:signed_global_ids)_when_secret_key_base_is_present:
TZInfo::DataSourceNotFound: tzinfo-data is not present. Please add gem 
'tzinfo-data' to your Gemfile and run bundle install
test/cases/railtie_test.rb:62:in `block in '

rails test test/cases/railtie_test.rb:61

E

Error:
RailtieTest#test_SignedGlobalID.verifier_can_be_set_with_config.global_id.verifier_=:
TZInfo::DataSourceNotFound: tzinfo-data is not present. Please add gem 
'tzinfo-data' to your Gemfile and run bundle install
test/cases/railtie_test.rb:82:in `block in '

rails test test/cases/railtie_test.rb:80



Finished in 0.585726s, 230.4834 runs/s, 402.9191 assertions/s.
135 runs, 236 assertions, 0 failures, 8 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"lib:test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/cases/global_id_test.rb" "test/cases/global_identification_test.rb" "test/cases/global_locator_test.rb" 
"test/cases/railtie_test.rb" "test/cases/signed_global_id_test.rb" "test/cases/uri_gid_test.rb" 
"test/cases/verifier_test.rb" ]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default => test
(See full trace by running task with --trace)
mv ./.gem2deb.Gemfile.lock Gemfile.lock
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-globalid 
returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026186: ruby-factory-bot-rails: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-factory-bot-rails
Version: 6.2.0-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-factory-bot-rails/ -i 
-O--buildsystem=ruby

[... snipped ...]

  tzinfo-data is not present. Please add gem 'tzinfo-data' to your Gemfile and 
run bundle install
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# ./spec/fake_app.rb:12:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# ./spec/spec_helper.rb:6:in `'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.
No examples found.


Finished in 0.00012 seconds (files took 0.75777 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

Finished in 0.00012 seconds (files took 0.75777 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples


/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format documentation failed
mv ./.gem2deb.Gemfile.lock Gemfile.lock
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-factory-bot-rails returned exit code 1
make: *** [debian/rules:8: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026185: ruby-enumerize: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-enumerize
Version: 2.5.0-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-enumerize/ -i -O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `create_default_data_source'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from /<>/test/test_helper.rb:26:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/activemodel_test.rb:3:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
rake aborted!
Command failed with status (1): [ruby -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/activemodel_test.rb" "test/activerecord_test.rb" 
"test/attribute_map_test.rb" "test/attribute_test.rb" "test/base_test.rb" "test/module_attributes_test.rb" "test/mongo_mapper_test.rb" "test/mongoid_test.rb" 
"test/multiple_test.rb" "test/predicates_test.rb" "test/rails_admin_test.rb" "test/sequel_test.rb" "test/set_test.rb" "test/value_test.rb" -v]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-enumerize returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to 

Bug#1026184: ruby-combustion: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-combustion
Version: 1.3.7-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-combustion/ -i -O--buildsystem=ruby

[... snipped ...]


An error occurred while loading spec_helper.rb.
Failure/Error: Combustion::Application.initialize!

TZInfo::DataSourceNotFound:
  tzinfo-data is not present. Please add gem 'tzinfo-data' to your Gemfile and 
run bundle install
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
# ./lib/combustion.rb:56:in `initialize!'
# ./spec/spec_helper.rb:17:in `block in '
# ./spec/spec_helper.rb:16:in `chdir'
# ./spec/spec_helper.rb:16:in `'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
No examples found.


Finished in 0.6 seconds (files took 1.82 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib:/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*_spec.rb failed
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-combustion returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026183: ruby-coffee-rails: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-coffee-rails
Version: 5.0.0-3
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby

[... snipped ...]


/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
/usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:431:in `each_strongly_connected_component_from'
/usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
/usr/lib/ruby/3.0.0/tsort.rb:347:in `each_strongly_connected_component'
/usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
/usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'

/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
/<>/test/assets_test.rb:16:in `setup'

Error:
AssetsTest#test_coffee-script.js_is_included_in_Sprockets_environment:
Errno::ENOENT: No such file or directory @ apply2files - 
/<>/test/tmp/coffee-script.js
/<>/test/assets_test.rb:22:in `delete'
/<>/test/assets_test.rb:22:in `teardown'

rails test test/assets_test.rb:25



Finished in 1.037368s, 4.8199 runs/s, 5.7839 assertions/s.
5 runs, 6 assertions, 0 failures, 2 errors, 0 skips
rake aborted!
Command failed with status (1)
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-coffee-rails returned exit code 1
make: *** [debian/rules:6: binary-indep] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026182: ruby-browser: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-browser
Version: 4.2.0-3
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from /<>/test/sample_app.rb:55:in `'
from 
:148:in 
`require'
from 
:148:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
from /<>/test/middleware_test.rb:5:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
Coverage report generated for Unit Tests to /<>/coverage. 768 / 
1256 LOC (61.15%) covered.
rake aborted!
Command failed with status (1): [ruby -w -I"lib:lib:test" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/browser_test.rb" 
"test/middleware_test.rb" "test/rails_test.rb" ]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-browser 
returned exit code 1
make: *** [debian/rules:8: binary-indep] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026181: ruby-arbre: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-arbre
Version: 1.4.0-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-arbre/ -i -O--buildsystem=ruby

[... snipped ...]

# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:159:in
 `rescue in create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:156:in
 `create_default_data_source'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
# 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
# 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
# 
/usr/share/rubygems-integration/all/gems/combustion-1.3.7/lib/combustion.rb:56:in
 `initialize!'
# ./spec/rails/rails_spec_helper.rb:4:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
# ./spec/rails/integration/rendering_spec.rb:1:in `'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `block in load'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
# 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:326:in
 `load'
# --
# --- Caused by: ---
# TZInfo::DataSources::ZoneinfoDirectoryNotFound:
#   None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
#   
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'

Finished in 0.7 seconds (files took 1.03 seconds to load)
0 examples, 0 failures, 2 errors occurred outside of examples

/usr/bin/ruby3.0 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --format documentation failed
mv ./.gem2deb.Gemfile.lock Gemfile.lock
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/ruby-arbre 
returned exit code 1
make: *** [debian/rules:8: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug 

Bug#1026180: ruby-ahoy-email: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-ahoy-email
Version: 1.1.1-2
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-ahoy-email/ -i -O--buildsystem=ruby

[... snipped ...]

from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `create_default_data_source'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
from 
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/railtie.rb:50:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `instance_exec'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:32:in
 `run'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:61:in
 `block in run_initializers'
from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from 
/usr/share/rubygems-integration/all/gems/combustion-1.3.7/lib/combustion.rb:56:in
 `initialize!'
from /<>/test/test_helper.rb:10:in `'
from /<>/test/click_test.rb:1:in `require_relative'
from /<>/test/click_test.rb:1:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
rake aborted!
Command failed with status (1)
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in `'
Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-ahoy-email returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 25
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.



Bug#1026179: ruby-active-model-serializers: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:ruby-active-model-serializers
Version: 0.10.12-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   dh_auto_install --destdir=debian/ruby-active-model-serializers/ -i 
-O--buildsystem=ruby

[... snipped ...]

from /usr/lib/ruby/3.0.0/tsort.rb:228:in `block in tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:350:in `block (2 levels) in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:431:in 
`each_strongly_connected_component_from'
from /usr/lib/ruby/3.0.0/tsort.rb:349:in `block in 
each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `each'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in `call'
from /usr/lib/ruby/3.0.0/tsort.rb:347:in 
`each_strongly_connected_component'
from /usr/lib/ruby/3.0.0/tsort.rb:226:in `tsort_each'
from /usr/lib/ruby/3.0.0/tsort.rb:205:in `tsort_each'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/initializable.rb:60:in
 `run_initializers'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/application.rb:391:in
 `initialize!'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `public_send'
from 
/usr/share/rubygems-integration/all/gems/railties-6.1.7/lib/rails/railtie.rb:207:in
 `method_missing'
from /<>/test/support/isolated_unit.rb:77:in 
`make_basic_app'
from /<>/test/support/rails_app.rb:5:in 
`'
from /<>/test/support/rails_app.rb:4:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `block in require'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in
 `load_dependency'
from 
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in
 `require'
from /<>/test/test_helper.rb:57:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /<>/test/action_controller/adapter_selector_test.rb:3:in 
`'
from 
:85:in 
`require'
from 
:85:in 
`require'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
 `block in '
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `select'
from 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
 `'
rake aborted!
Command failed with status (1): [ruby -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/action_controller/adapter_selector_test.rb" "test/action_controller/explicit_serializer_test.rb" "test/action_controller/json/include_test.rb" "test/action_controller/json_api/deserialization_test.rb" "test/action_controller/json_api/errors_test.rb" "test/action_controller/json_api/fields_test.rb" "test/action_controller/json_api/linked_test.rb" "test/action_controller/json_api/transform_test.rb" "test/action_controller/lookup_proc_test.rb" "test/action_controller/namespace_lookup_test.rb" 
"test/action_controller/serialization_scope_name_test.rb" "test/action_controller/serialization_test.rb" "test/active_model_serializers/adapter_for_test.rb" "test/active_model_serializers/json_pointer_test.rb" "test/active_model_serializers/logging_test.rb" "test/active_model_serializers/model_test.rb" "test/active_model_serializers/test/serializer_test.rb" "test/active_record_test.rb" "test/adapter/attributes_test.rb" "test/adapter/deprecation_test.rb" "test/adapter/json/belongs_to_test.rb" "test/adapter/json/collection_test.rb" "test/adapter/json/fields_test.rb" "test/adapter/json/has_many_test.rb" 
"test/adapter/json/transform_test.rb" "test/adapter/json_api/belongs_to_test.rb" "test/adapter/json_api/collection_test.rb" "test/adapter/json_api/errors_test.rb" "test/adapter/json_api/fields_test.rb" "test/adapter/json_api/has_many_explicit_serializer_test.rb" "test/adapter/json_api/has_many_test.rb" "test/adapter/json_api/has_one_test.rb" "test/adapter/json_api/include_data_if_sideloaded_test.rb" "test/adapter/json_api/json_api_test.rb" 

Bug#1026178: redmine: FTBFS in bookworm (missing build-depends on tzdata)

2022-12-15 Thread Santiago Vila

Package: src:redmine
Version: 5.0.0-1
Severity: serious
Tags: bookworm ftbfs patch

Dear maintainer:

During a rebuild of all packages in bookworm, your package failed to build:


[...]
 debian/rules binary-indep
dh binary-indep --with ruby
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./debian/check-locales
bundle --local --quiet
`/sbuild-nonexistent` is not a directory.
Bundler will use `/tmp/bundler20220525-2469344-bbkpvo2469344' as your home 
directory temporarily.
rm -f Gemfile.lock
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'

[... snipped ...]

/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/initializable.rb:60:in
 `run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:391:in
 `initialize!'
/<>/config/environment.rb:16:in `'
/usr/share/rubygems-integration/all/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in
 `require'
/usr/share/rubygems-integration/all/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in
 `require'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:332:in
 `block in require'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:299:in
 `load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:332:in
 `require'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:367:in
 `require_environment!'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:533:in
 `block in run_tasks_blocks'

Caused by:
TZInfo::DataSources::ZoneinfoDirectoryNotFound: None of the paths included in 
TZInfo::DataSources::ZoneinfoDataSource.search_path are valid zoneinfo 
directories.
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_sources/zoneinfo_data_source.rb:232:in
 `initialize'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `new'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:157:in
 `create_default_data_source'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:55:in
 `block in get'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `synchronize'
/usr/share/rubygems-integration/all/gems/tzinfo-2.0.4/lib/tzinfo/data_source.rb:54:in
 `get'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/railtie.rb:50:in
 `block in '
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/initializable.rb:32:in
 `instance_exec'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/initializable.rb:32:in
 `run'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/initializable.rb:61:in
 `block in run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/initializable.rb:60:in
 `run_initializers'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:391:in
 `initialize!'
/<>/config/environment.rb:16:in `'
/usr/share/rubygems-integration/all/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in
 `require'
/usr/share/rubygems-integration/all/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:34:in
 `require'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:332:in
 `block in require'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:299:in
 `load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.4.6/lib/active_support/dependencies.rb:332:in
 `require'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:367:in
 `require_environment!'
/usr/share/rubygems-integration/all/gems/railties-6.1.4.6/lib/rails/application.rb:533:in
 `block in run_tasks_blocks'
Tasks: TOP => db:migrate => db:load_config => environment
(See full trace by running task with --trace)
make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

Note 1: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).

Note 2: This bug is currently "hidden" by #1022340, which makes the build to 
fail for
another reason. After fixing #1022340, this package will ftbfs again if built in
a chroot with only build-essential and build-dependencies installed.


About the archive rebuild: The build was made using 

Bug#1026174: linux: Please enable CONFIG_X86_SGX_KVM=y

2022-12-15 Thread Diederik de Haas
found 1026174 linux/6.0.10-2



signature.asc
Description: This is a digitally signed message part.


Bug#1026177: bullseye-pu: package golang-github-prometheus-exporter-toolkit/0.5.1-2

2022-12-15 Thread Martina Ferrari
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: golang-github-prometheus-exporter-tool...@packages.debian.org, 
Santiago Vila 
Control: affects -1 + src:golang-github-prometheus-exporter-toolkit

[ Reason ]
This package is currently FTBFS on stable due to flaky tests.

[ Impact ]
No impact for users.

[ Tests ]
Santiago Vila has manually tested this issue and fix extensively, documented in
the original bug report (#1013578).

[ Risks ]
No risks, this just adds delays in tests.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
Just a couple of calls to time.Sleep(), plus updated Uploaders field in
debian/control.
diff -Nru golang-github-prometheus-exporter-toolkit-0.5.1/debian/changelog 
golang-github-prometheus-exporter-toolkit-0.5.1/debian/changelog
--- golang-github-prometheus-exporter-toolkit-0.5.1/debian/changelog
2021-01-25 14:10:41.0 +
+++ golang-github-prometheus-exporter-toolkit-0.5.1/debian/changelog
2022-12-15 22:33:17.0 +
@@ -1,3 +1,10 @@
+golang-github-prometheus-exporter-toolkit (0.5.1-2+deb11u1) bullseye; 
urgency=medium
+
+  * Patch tests to avoid race condition. Closes: #1013578.
+Thanks to Santiago Vila for the adjusted patch.
+
+ -- Martina Ferrari   Thu, 15 Dec 2022 22:33:17 +
+
 golang-github-prometheus-exporter-toolkit (0.5.1-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru golang-github-prometheus-exporter-toolkit-0.5.1/debian/control 
golang-github-prometheus-exporter-toolkit-0.5.1/debian/control
--- golang-github-prometheus-exporter-toolkit-0.5.1/debian/control  
2021-01-19 14:44:59.0 +
+++ golang-github-prometheus-exporter-toolkit-0.5.1/debian/control  
2022-12-15 22:33:17.0 +
@@ -1,6 +1,7 @@
 Source: golang-github-prometheus-exporter-toolkit
 Maintainer: Debian Go Packaging Team 
-Uploaders: Daniel Swarbrick 
+Uploaders: Daniel Swarbrick ,
+   Martina Ferrari ,
 Section: devel
 Testsuite: autopkgtest-pkg-go
 Priority: optional
diff -Nru 
golang-github-prometheus-exporter-toolkit-0.5.1/debian/patches/02-Avoid_race_in_test.patch
 
golang-github-prometheus-exporter-toolkit-0.5.1/debian/patches/02-Avoid_race_in_test.patch
--- 
golang-github-prometheus-exporter-toolkit-0.5.1/debian/patches/02-Avoid_race_in_test.patch
  1970-01-01 00:00:00.0 +
+++ 
golang-github-prometheus-exporter-toolkit-0.5.1/debian/patches/02-Avoid_race_in_test.patch
  2022-12-15 22:33:17.0 +
@@ -0,0 +1,31 @@
+Author: Martina Ferrari 
+Description: Fix test failures due to race conditions
+Forwarded: https://github.com/prometheus/exporter-toolkit/issues/108
+Last-Updated: Mon, 29 Aug 2022 17:39:56 +
+
+--- a/web/users_test.go
 b/web/users_test.go
+@@ -18,6 +18,7 @@
+   "net/http"
+   "sync"
+   "testing"
++  "time"
+ )
+ 
+ // TestBasicAuthCache validates that the cache is working by calling a 
password
+@@ -42,6 +43,7 @@
+   ListenAndServe(server, 
"testdata/tls_config_users_noTLS.good.yml", testlogger)
+   close(done)
+   }()
++  time.Sleep(250 * time.Millisecond)
+ 
+   login := func(username, password string, code int) {
+   client := {}
+@@ -106,6 +108,7 @@
+   ListenAndServe(server, 
"testdata/tls_config_users_noTLS.good.yml", testlogger)
+   close(done)
+   }()
++  time.Sleep(250 * time.Millisecond)
+ 
+   login := func() {
+   client := {}
diff -Nru golang-github-prometheus-exporter-toolkit-0.5.1/debian/patches/series 
golang-github-prometheus-exporter-toolkit-0.5.1/debian/patches/series
--- golang-github-prometheus-exporter-toolkit-0.5.1/debian/patches/series   
1970-01-01 00:00:00.0 +
+++ golang-github-prometheus-exporter-toolkit-0.5.1/debian/patches/series   
2022-12-15 22:33:17.0 +
@@ -0,0 +1 @@
+02-Avoid_race_in_test.patch


Bug#806717: Forwarding email with a long header causes longer than 998 byte lines

2022-12-15 Thread Hefee
Hey,

I think the fix will be published with KMime 22.12.0 (should reach unstable the 
next days), as there is a MR request that should fix that:
https://invent.kde.org/pim/kmime/-/merge_requests/7

Regards,

hefee

--

On Dienstag, 13. Dezember 2022 20:14:28 CET Mikko Tuumanen wrote:
> I received an email with a x-ms-exchange-antispam-messagedata-0: header
> and I tried to forward it with kmail.
> 
> That caused error message:
> "The server said: maximum allowed line length is 998 octets, got 1702"
> 
> In the original message, the header was split into multiple lines like
> this:
> 
> x-ms-exchange-antispam-messagedata-0:
>  =?iso-8859-1?Q?X9nvzr27qYcmEJpSHcp6K5gWYoBjPRlTmpppdR4VrmwY1cP0Mp4QNB9+kY?=
> =?iso-8859-1?Q?ZWd5EsMdHUa4x0pKA1ObLVns8RuLFV3mCsHlMT31xBfLxra6jZ+p5hbSHx?=
> 
> 
> But when the message was forwarded with kmail, the header
> turned into one too long line:
> 
> x-ms-exchange-antispam-messagedata-0: lwf7pdVSQS1T...
> 
> 
> It seems that kmail has more than one header "fixing" problem.



signature.asc
Description: This is a digitally signed message part.


Bug#1001513: Bug#989583: liblip: Fails to build reproducibly: multiple problems

2022-12-15 Thread Vagrant Cascadian
Control: tags 989583 pending
Control: tags 1001513 pending

Uploading an NMU to DELAYED/10 fixing reproducible builds and
cross-building issues:

diff -u liblip-2.0.0/debian/changelog liblip-2.0.0/debian/changelog
--- liblip-2.0.0/debian/changelog
+++ liblip-2.0.0/debian/changelog
@@ -1,3 +1,21 @@
+liblip (2.0.0-1.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Support cross-building (Closes: #1001513)
+
+ -- Vagrant Cascadian   Thu, 15 Dec 2022 
14:21:26 -0800
+
+liblip (2.0.0-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Nilesh Patra ]
+  * Build reproducibly (Closes: #989583)
+
+ -- Vagrant Cascadian   Thu, 15 Dec 2022 
13:49:39 -0800
+
 liblip (2.0.0-1.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u liblip-2.0.0/debian/rules liblip-2.0.0/debian/rules
--- liblip-2.0.0/debian/rules
+++ liblip-2.0.0/debian/rules
@@ -2,18 +2,24 @@
 # Copyright (C) 2004-2005 Anibal Monsalve Salazar 
 # Copyright (c) 2005 Juan Esteban Monsalve Tobon 
 
-STRIP  = strip --strip-unneeded --remove-section=.comment 
--remove-section=.note
+include /usr/share/dpkg/architecture.mk
+include /usr/share/dpkg/buildtools.mk
+
+STRIP  := $(STRIP) --strip-unneeded --remove-section=.comment 
--remove-section=.note
+
+CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS)
+CXXFLAGS += -ffile-prefix-map=$(CURDIR)=.
 
 build:
$(checkdir)
cp -f /usr/share/misc/config.sub .
cp -f /usr/share/misc/config.guess .
-   ./configure --prefix=/usr --enable-shared
-   $(MAKE) install prefix=$(CURDIR)/shared
+   ./configure --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE) 
--prefix=/usr --enable-shared ./configure --prefix=/usr --enable-shared
+   $(MAKE) install prefix=$(CURDIR)/shared CXXFLAGS="$(CXXFLAGS)"
[ ! -f Makefile ] || $(MAKE) distclean
-rm -f config.log config.cache
-   ./configure --prefix=/usr --enable-static
-   $(MAKE) install prefix=$(CURDIR)/static
+   ./configure --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE) 
--prefix=/usr --enable-static
+   $(MAKE) install prefix=$(CURDIR)/static CXXFLAGS="$(CXXFLAGS)"
touch build
 
 clean:
@@ -59,20 +65,22 @@
cp -p docs/* debian/liblip2/usr/share/doc/liblip2/
cp -p examples/example* debian/liblip2/usr/share/doc/liblip2/examples
cp -p examples/makefile debian/liblip2/usr/share/doc/liblip2/examples
-   cd debian/liblip2/usr/share/doc/liblip2 && gzip -9 changelog.Debian 
examples/*
+   cd debian/liblip2/usr/share/doc/liblip2 && gzip -9n changelog.Debian 
examples/*
 
ln -s liblip2 debian/liblip-dev/usr/share/doc/liblip-dev
 
dpkg-shlibdeps debian/liblip2/usr/lib/lip/*
dpkg-gencontrol -isp -pliblip2 -Pdebian/liblip2
-   cd debian/liblip2 && md5sum `find * -type f ! -regex "DEBIAN/.*"` > 
DEBIAN/md5sums
+   cd debian/liblip2 && find * -type f ! -regex "DEBIAN/.*" -print0 |\
+   LC_ALL=C sort -z | xargs -0r md5sum > DEBIAN/md5sums
chown -R root.root debian/liblip2
chmod -x debian/liblip2/usr/lib/lip/*
chmod -R go=rX debian/liblip2
dpkg --build debian/liblip2 ..
 
dpkg-gencontrol -isp -pliblip-dev -Pdebian/liblip-dev
-   cd debian/liblip-dev && md5sum `find * -type f ! -regex "DEBIAN/.*"` > 
DEBIAN/md5sums
+   cd debian/liblip-dev && find * -type f ! -regex "DEBIAN/.*" -print0 |\
+   LC_ALL=C sort -z | xargs -0r md5sum > DEBIAN/md5sums
chown -R root.root debian/liblip-dev
chmod -x debian/liblip-dev/usr/lib/lip/liblip.a
chmod -x debian/liblip-dev/usr/lib/lip/liblip.la


signature.asc
Description: PGP signature


Bug#1026176: ITP: nim-httpbeast -- Fast multi-threaded HTTP server library for Nim

2022-12-15 Thread Federico Ceratto
Package: wnpp
Severity: wishlist
Owner: Federico Ceratto 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: nim-httpbeast
  Version : 0.4.1
  Upstream Contact: Dominik Picheta
* URL : https://github.com/dom96/httpbeast
* License : Expat
  Programming Lang: Nim
  Description : Fast multi-threaded HTTP server library for Nim

Built on the Nim selectors module which makes efficient use of epoll on Linux
Automatic parallelization when compiling with --threads:on.
Support for HTTP pipelining.
On-demand parser so that only the requested data is parsed.
Integration with Nim's asyncdispatch allowing async/await to be used in.
the request callback whenever necessary.

Maintained by the Debian Nim Team at
https://salsa.debian.org/nim-team/nim-httpbeast



Bug#1026175: RM: gcc-python-plugin -- ROM; dead upstream; RC-buggy; last released with buster

2022-12-15 Thread Bastian Germann

Source: gcc-python-plugin

The package seems to be unmaintained. Please remove it from Debian by 
reassigning to ftp.debian.org if you agree.
It should not have any reverse (build) dependencies. Else, please consider 
orphaning.



Bug#1021418: builtin: echo: Treat -n as a string

2022-12-15 Thread наб
Control: tags -1 + upstream wontfix

Additionally, there is historical precedent since V7 UNIX
(and a little-known "BSD" system that derives from it)
for echo -n, so the dash minimalness argument also doesn't hold,
since the minimal thing is to not touch it.

Similarly, PWB/CB-UNIX/SysIII echo exists as printf %b
("XSI" is a stand-in for "alas, SysIII-and-friends do this
 and we ratified it when the standard was just XPG/SUS"),
and the standard encourages you to Not Use echo at all ‒
if there's backslash-escapes they /may/ get intepreted too!

For echo use printf %s\n, for echo -n use printf %s,
for SysIII-style echo-with-escapes use printf %b\n
(or convert to a native printf expression).
The only thing echo makes sense for is to Just Write A New-Line
if you don't give it arguments, and even then…

наб


signature.asc
Description: PGP signature


Bug#1026174: linux: Please enable CONFIG_X86_SGX_KVM=y

2022-12-15 Thread Wojtek Porczyk
Source: linux
Severity: normal

Dear Maintainer,

Please consider CONFIG_X86_SGX_KVM=y config option. This option enables using
SGX inside KVM virtual machines. Support for this landed in qemu around 7.0
(I don't recall the exact version) and in libvirt 8.10.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-5-amd64 (SMP w/24 CPU threads; PREEMPT)
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


-- 
pozdrawiam / best regards
Wojtek Porczyk
Gramine / Invisible Things Lab
 
 I do not fear computers,
 I fear lack of them.
-- Isaac Asimov


signature.asc
Description: PGP signature


Bug#1025823: qt6-base FTBFS on Alpha; Unknown Q_PROCESSOR_xxx macro

2022-12-15 Thread Patrick Franz
Hi Michael,

thanks for the patch. Could you please rebase this against the latest 
from the 6.4 branch ?


-- 
Med vänliga hälsningar

Patrick Franz



Bug#986601: libjama -- Fails to build reproducibly: usrmerge + gzip inserts timestamps

2022-12-15 Thread Vagrant Cascadian
Control: tags 986601 pending

On 2021-04-08, Nilesh Patra wrote:
> libjama does not build reproducibly due to two reasons:
>   - gzip inserts time stamps so -n flag should be added
>   - tar cf gives different permissions due to usrmerge.

I have uploaded an NMU to DELAYED/10 fixing this issue:

diff -u libjama-1.2.4/debian/changelog libjama-1.2.4/debian/changelog
--- libjama-1.2.4/debian/changelog
+++ libjama-1.2.4/debian/changelog
@@ -1,3 +1,13 @@
+libjama (1.2.4-2.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Nilesh Patra ]
+  * Build reproducibly: fix timestamps issues by passing gzip -n and fix
+permissions in included shipped tarball. (Closes: #986601)
+
+ -- Vagrant Cascadian   Thu, 15 Dec 2022 
13:18:25 -0800
+
 libjama (1.2.4-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u libjama-1.2.4/debian/rules libjama-1.2.4/debian/rules
--- libjama-1.2.4/debian/rules
+++ libjama-1.2.4/debian/rules
@@ -17,11 +17,11 @@
install -p -m 644 Changes debian/tmp/usr/share/doc/libjama-dev/changelog
install -p -m 644 debian/changelog 
debian/tmp/usr/share/doc/libjama-dev/changelog.Debian
install -p -m 644 examples debian/tmp/usr/share/doc/libjama-dev
-   gzip -9 debian/tmp/usr/share/doc/libjama-dev/*
+   gzip -9n debian/tmp/usr/share/doc/libjama-dev/*
install -p -m 644 README debian/tmp/usr/share/doc/libjama-dev
install -p -m 644 debian/copyright debian/tmp/usr/share/doc/libjama-dev
-   tar cf debian/tmp/usr/share/doc/libjama-dev/html-jama.tar html
-   gzip -9 debian/tmp/usr/share/doc/libjama-dev/html-jama.tar
+   tar caf debian/tmp/usr/share/doc/libjama-dev/html-jama.tar html 
--owner=0 --group=0 --numeric-owner --sort=name --mode=a+rX,og-w
+   gzip -9n debian/tmp/usr/share/doc/libjama-dev/html-jama.tar
chmod 644 debian/tmp/usr/share/doc/libjama-dev/html-jama.tar.gz
 
dpkg-gencontrol -isp


live well,
  vagrant


signature.asc
Description: PGP signature


Bug#1020560: diffutils: Missing LGPL-2.1+, GPL-2+ in d/copyright

2022-12-15 Thread Santiago Vila

El 13/12/22 a las 16:03, Bastian Germann escribió:

I guess the rule was to use a wildcard when it is possible.
You can certainly list every file but then the copyright file will be much 
bigger.


Note: What I finally did was to keep the lib/* and m4/* wildcards and expand 
the others.


> How did you generate the file?

It is not generated. If you can come up with a better file that is fine.


Well, I took your file as a base, and it helped a lot, but I also had to make 
several
important changes. By using "debmake -k", I found there was a bunch of files 
under
LGPL 2.0+ and another bunch of files under LGPL 3.0+ so I had to create new 
blocks for them.

While moving files to the right block it became clear to me that expanding
the wildcards was better than not expanding them.

The final file differs from the proposal in several minor ways: I looked at 
other people's copyright
file and realized that nobody puts the full path in the Source: field at the 
top, most people
put only the URL as the base directory, which I believe it is good enough.

Another change I did: I consider this paragraph:

 You should have received a copy of the GNU General Public License
 along with this file.  If not, see .

to be at the same "level" as this one:

 On Debian systems, the complete text of the GNU General Public License
 version 3 may be found in `/usr/share/common-licenses/GPL-3'.

as both tell the user where to find the license. So I put the latter after
the former, not in a Comment section.

I believe the file should be mostly correct now.

Thanks a lot.



Bug#1026006: heimdal FTCBFS: multiple reasons

2022-12-15 Thread Brian May
Helmut Grohne  writes:


> Note that python3 is used
> as a code generator, so rather than a host architecture python3 a build
> architecture python3 is needed. To achieve that, it should be annotated
> :native or :any.

Sounds reasonable.

> Once that has changed, one can actually attempt a cross build. That
> attempt quickly ends due to not finding ncurses, because it didn't do
> a cross build. The relevant --build and --host flags are missing from
> configure. Is there a reason for not using dh_auto_configure?

No idea now, sorry. I think this stuff was contributed by others.
Probably legacy reasons now.

> It would automatically pass them as needed. Once
> added, the build progresses quite far until it fails finding
> asn1_compile. The build system is clever enough to recognize that it
> cannot run the built asn1_compile and tries running the system copy
> instead, which isn't there. Unfortunately, asn1_compile does not reside
> in a Multi-Arch: foreign package and thus is not readily available. I
> propose splitting it out of heimdal-multidev into a heimdal-multidev-bin
> package that contains architecture-independent tools. Once done, we can
> depend on it (for cross compilation only to avoid a recursive
> depdendency in native builds). Are you ok with such a split? We have
> quite some prior art for this if you look for other packages matching
> the pattern "*-bin", especially in the qt/kde ecosystem. I'm attaching a
> patch for your convenience.

When I tried to build this with my build system I get:

$ apt-get-build-depends --yes
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package heimdal-multidev-bin
E: Unable to locate package 

Is "heimdal-multidev-bin ," correct syntax? If so, maybe
apt-get-build-depends doesn't support it.
-- 
Brian May 



Bug#1012496: inkscape: FTBFS on arm64, ppc64el, s390x

2022-12-15 Thread Sandro Tosi
On Wed, 8 Jun 2022 13:48:36 +0200 Mattia Rizzolo  wrote:
> Source: inkscape
> Version: 1.2-1
> Severity: serious
> Tags: ftbfs
> Forwarded: https://gitlab.com/inkscape/inkscape/-/issues/3554

Hello Mattia,
upstream doesnt seem to have make a dent in cracking this issue and in
https://gitlab.com/inkscape/inkscape/-/issues/3554#note_1120324670 you
mentioned you were planning on reverting (temporarily) inkscape to
1.1.2, but i still see 1.2.1 in unstable, with the problems mentioned
here.

Are you still planning on doing this?

Matplotlib, which i maintain, is impacted by inkscape not being built
on all archs and migrating to debian.

Regards,
Sandro



Bug#1025765: Happens due to no longer having separate language versions?

2022-12-15 Thread Lynoure Braakman
Here's the output I get:

$ torbrowser-launcher

Tor Browser Launcher

By Micah Lee, licensed under MIT

version 0.3.5

https://github.com/micahflee/torbrowser-launcher

Downloading Tor Browser for the first time.

Downloading
https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US

Latest version: 12.0

Downloading
https://dist.torproject.org/torbrowser/12.0/tor-browser-linux64-12.0_en-US.tar.xz.asc

Download Error: 404


And then it just seems to wait.

When I go and look at
https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US
and then follow to the link to the blog at
https://blog.torproject.org/new-release-tor-browser-120 and then to the
distribution directory at https://dist.torproject.org/torbrowser/12.0/ (so
far so good),

I can see there is no *en-US* or other languages at all, just *ALL*, which
is probably why things are not working so well anymore.

-- 

Lynoure
lyno...@gmail.com


Bug#1026116: Patches not applied in security release deb10u6, FTBFS

2022-12-15 Thread Mihai Moldovan
* On 12/15/22 18:42, Sven Joachim wrote:
> It seems you are slightly mistaken here, as the same problem had been
> reported for 2:1.20.4-1+deb10u3 already.  It has been fixed post-buster
> in 2:1.20.6-1.
Oh, sorry, that bug report didn't show up for me. I did search for bug reports
against xorg-server-source in oldstable before writing my report.

It does explain why I haven't seen this problem with deb10u3 any longer -
sunweaver/Mike has uploaded a fixed version to our (X2Go) package repository
previously, which I haven't known about. From what he told me, he assumed that
his patch was applied to buster's package version as well.

After deb10u6 made it to the security repository, though, the overridden package
version was lower and we've started seeing the issue again.

It would have been nice for sunweaver's fix to make it into an updated version
based on the deb10u6 version (so deb10u7 I figure?), but given that's buster is
almost oldoldstable, I don't think that there will be another release just to
fix that issue.



Mihai


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1026173: yabar: Errors out when calling it manually

2022-12-15 Thread Steve
Package: yabar
Version: 0.4.0-1.1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: stephen.d.al...@gmail.com

Dear Maintainer,

Below is the error when attempting to launch this program. It doesn't
create any config file, even when commanded to do so. :-)

~$ yabar -c /home/steve
Error in the config file at line 0 : file I/O error
Exiting...


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages yabar depends on:
ii  libc62.36-6
ii  libcairo21.16.0-7
ii  libconfig9   1.5-0.4
ii  libglib2.0-0 2.74.2-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libxcb-ewmh2 0.4.1-1.1
ii  libxcb-randr01.15-1
ii  libxcb1  1.15-1

yabar recommends no packages.

Versions of packages yabar suggests:
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-4.1

-- no debconf information



Bug#1026055: lapack breaks openturns autopkgtest: undefined reference to `ztrsyl3_' (and 3 more)

2022-12-15 Thread Paul Gevers

Hi Sébastien,

On 13-12-2022 21:59, Sébastien Villemot wrote:

The problem is that atlas needs to be recompiled against lapack 3.11.0.
Which has been done in atlas 3.10.3-13. But atlas itself cannot migrate
to testing because of #1025699.


While I understand recompiling "solves" the issue, normally this error 
"undefined reference" hints at removal of symbols. Normally that should 
be handled by a SONAME bump which would trigger auto trackers to be 
generated for the transition. Such trackers notify the release team of 
transitions and they can trigger rebuilds (you know that drill, 
including the transition bug filing for coordination). Why do you think 
that a SONAME bump wasn't the right solution in this case?


Paul


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1026172: mono: FTBFS on mipsel

2022-12-15 Thread Jo Shields
What hardware is in the mipsel-osuosl-* machines? Mono has a history of 
triggering hardware bugs in imperfect MIPS implementations, e.g. Loongson 2


On 12/15/22 14:57, Salvatore Bonaccorso wrote:

Source: mono
Version: 6.8.0.105+dfsg-3.2
Severity: serious
Justification: FTBFS
X-Debbugs-Cc: car...@debian.org

Hi

After uploading mono/6.8.0.105+dfsg-3.3 the package FTBFS on mipsel,
it suceeded on mipsel-osuosl-01 but the history of failures is found
at:

https://buildd.debian.org/status/logs.php?pkg=mono=6.8.0.105%2Bdfsg-3.3=mipsel

Regards,
Salvatore





Bug#1026056: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1026056: fixed in logol 1.7.9+dfsg-6)

2022-12-15 Thread Paul Gevers

Control: reassign -1 src:logol 1.7.9+dfsg-5
Control: fixed -1 logol/1.7.9+dfsg-6
Control: affects -1 src:swi-prolog

Hi,

On 14-12-2022 10:15, Debian Bug Tracking System wrote:

* rebuild against new swi-prolog (Closes: #1026056)


I can't but feel a bit uneasy by this "solution". Apparently it's not 
properly tracked by dependencies, so it doesn't show up on the Release 
Teams auto transition trackers [1] (which would typically trigger the 
Release Team to trigger binNMU's, but if nothing else at least would put 
it on the radar). For C based libraries this "solution" typically hides 
real problems. Do we believe we can improve the logol/swi-prolog 
situation in a similar way, or is the effort really not worth it 
(apparently autopkgtest catches the issue, but the solution isn't 
visible from the failure).


Paul

[1] https://release.debian.org/transitions/


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1026172: mono: FTBFS on mipsel

2022-12-15 Thread Salvatore Bonaccorso
Source: mono
Version: 6.8.0.105+dfsg-3.2
Severity: serious
Justification: FTBFS
X-Debbugs-Cc: car...@debian.org

Hi

After uploading mono/6.8.0.105+dfsg-3.3 the package FTBFS on mipsel,
it suceeded on mipsel-osuosl-01 but the history of failures is found
at:

https://buildd.debian.org/status/logs.php?pkg=mono=6.8.0.105%2Bdfsg-3.3=mipsel

Regards,
Salvatore



Bug#1026116: Patches not applied in security release deb10u6, FTBFS

2022-12-15 Thread Mihai Moldovan
[Resent to the bug tracker as well]

* On 12/15/22 19:15, Emilio Pozuelo Monfort wrote:
> I'm not sure I understand what the problem is. The patches are in 
> debian/patches/ and are applied during build using quilt.

Thank you for looking into it.


>  From the amd64's build log [1]:

It won't show up there, since the arch-indep part of the build is done
separately. The build log you have been searching for is at

https://buildd.debian.org/status/fetch.php?pkg=xorg-server=all=2%3A1.20.4-1%2Bdeb10u6=1667984135=0


dpkg-buildpackage
-

Command: dpkg-buildpackage -us -uc -mall Build Daemon (x86-grnet-02)
 -A -rfakeroot
--changes-option=-O../xorg-server_1.20.4-1+deb10u6_all-buildd.changes
--buildinfo-option=-O../xorg-server_1.20.4-1+deb10u6_all-buildd.buildinfo
dpkg-buildpackage: info: source package xorg-server
[...]
make[1]: Leaving directory '/<>'
 debian/rules build-indep
mkdir -p build-source
tar \
--owner=0 --group=0 \
--transform 's,^,xorg-server/,' \
--exclude=debian \
--exclude=autom4te.cache \
-cf - * | xz > build-source/xorg-server.tar.xz
tar: build-source/xorg-server.tar.xz: file changed as we read it
>build-source-stamp
dh build-indep --with quilt,autoreconf --parallel
   dh_quilt_patch -i -O--parallel
Applying patch 001_fedora_extramodes.patch
patching file hw/xfree86/common/extramodes

Applying patch 02_kbsd-input-devd.diff
[...]


As clearly visible, xorg-server.tar.xz, which ends up in the xorg-server-source
binary package, is created *before* applying the patches, which is leading to
the issue I have described initially.



Mihai



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1026171: Please enable large file support for sqllite3

2022-12-15 Thread Helge Deller

Package: sqlite3
Version: 3.40.0
Tags: hppa, patch, ftbfs

Please enable large file support (LFS) when building sqllite3.
This is necessary for 32-bit applications to be able to run on larger 
filesystems.
For example the "subversion" debian package depends on this feature to
successfully run it's testsuite when building on 32-bit.

Just change this line in debian/rules:
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
to
export DEB_BUILD_MAINT_OPTIONS = hardening=+all future=+lfs

This will affect only build on 32-bit platforms, and has no effect on 64-bit 
platforms.

Thanks!
Helge



Bug#1026170: barrier: Do you plan to switch from debauchee upstream to input-leap one?

2022-12-15 Thread Alban Browaeys
Package: barrier
Version: 2.3.3+dfsg-1.1
Severity: wishlist

A group of developper forked barrier to a new Github repository:
https://github.com/input-leap/input-leap

Note that the built binaries are still named barrier, barrierc, barriers
so the package should conflict if a new debian package name is created.
Maybe a new name for those binaries could be asked for, I have not
checkd the issue tracker for if it was already asked for.

Cheers,
Alban

-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable'), (90, 'testing-debug'), (90, 'unstable'), (90, 
'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-0.deb11.2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 barrier depends on:
ii  libavahi-compat-libdnssd1  0.8-5+deb11u1
ii  libc6  2.36-4
ii  libgcc-s1  12.2.0-9
ii  libqt5core5a   5.15.4+dfsg-5
ii  libqt5gui5 5.15.4+dfsg-5
ii  libqt5network5 5.15.4+dfsg-5
ii  libqt5widgets5 5.15.4+dfsg-5
ii  libssl1.1  1.1.1n-0+deb11u3
ii  libstdc++6 12.2.0-9
ii  libx11-6   2:1.8.1-2
ii  libxext6   2:1.3.3-1.1
ii  libxi6 2:1.8-1+b1
ii  libxinerama1   2:1.1.4-2
ii  libxrandr2 2:1.5.2-2+b1
ii  libxtst6   2:1.2.3-1
ii  openssl1.1.1n-0+deb11u3

barrier recommends no packages.

barrier suggests no packages.

-- no debconf information



Bug#1026070: kde-plasma-desktop: Right click on desktop and taskbar has no effect

2022-12-15 Thread Max Görner

Hello again,

I was able to find out a little bit more.

As I wrote I experience the issue on my second computer running on Debian
Testing too. However, a second user of that computer reported that she does
not suffer from that right click issue. So I tried to create a test user on
that second computer too and for this test user the issue did not appear
neither.

So, to sum up: On my Thinkpad both my main user and the fresh test user
experience the right click issue. On my PC only my main user, but neither the
permanent second user nor the fresh test user experienced the issue.

I cannot think of any actual relevant difference. The only thing that comes to
my mind is that the Thinkpad has the keyboard Neo2 configured as main layout,
so I even type in the passphrase for the whole disk encryption in Neo2. The
PC uses some more usual German variant.

I would be very glad if you would have any suggestion what I could do to
narrow down the issue a bit more.


When I created the test users, I noticed that each and every time KDE
complained about that the folder `~/.config/kdedefaults` was missing. I would
expect that after running `adduser` or adding a new user using KDE's settings
dialog KDE would be bootstrap itself. Instead, there are error messages in
`.xsession-errors` and the desktop background stays black.

Should I file a separate bug for this or is this behaviour already known?


Best Regards
Max Görner



Bug#1016047: Helping Chromium Web Browser

2022-12-15 Thread Silas
I'd be happy to help out. I have experience coding and using Linux, but I've 
never worked on a large software project. I have a lot of time at the moment to 
figure this out. It would be great to get into contact with someone who could 
direct me to resources and help me start out.

Best,
Silas



Bug#685265:

2022-12-15 Thread Catching Norman
Hello
Can u clear  bug.please


Bug#906966: closed by Maximiliano Curia (Bug#906966: fixed in kdesignerplugin 5.51.0-1)

2022-12-15 Thread Helmut Grohne
Control: reopen -1
Control: found -1 5.83.0-1

On Wed, Nov 07, 2018 at 05:27:04PM +, Debian Bug Tracking System wrote:
> #906966: kdesignerplugin FTCBFS: KF5::kgendesignerplugin: not found
> 
> It has been closed by Maximiliano Curia .

The fix has been reverted in 5.83.0-1. Would someone know why?

Helmut



Bug#1026062: kded5: kded crashes with signal 11

2022-12-15 Thread Tim Sattarov

I've just did a little test and can reproduce this by checking for updates in 
the Discover interface.

Is there anything I can do to help fixing this? So far it keeps crippling my workflow and the only 
way to fix it is to restart the kded service.


Thanks
Tim

On 12/13/22 19:58, Tim Sattarov wrote:

Package: kded5
Version: 5.100.0-1
Severity: normal
X-Debbugs-Cc: sti...@gmail.com

Dear Maintainer,

Starting with version 5.100.0-1 my local kded process started to crash and the
only way to restore it is to restart the service

systemctl  --user restart plasma-kded.service

It works for some time after restart and then crashes again.

Please see the logs from the crash attached.




-- System Information:
Debian Release: bookworm/sid
   APT prefers testing
   APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kded5 depends on:
ii  libc6  2.36-6
ii  libkf5configcore5  5.100.1-1
ii  libkf5coreaddons5  5.100.0-1
ii  libkf5crash5   5.100.0-1
ii  libkf5dbusaddons5  5.100.0-1
ii  libkf5service-bin  5.100.0-1
ii  libkf5service5 5.100.0-1
ii  libqt5core5a   5.15.6+dfsg-5
ii  libqt5dbus55.15.6+dfsg-5
ii  libqt5gui5 5.15.6+dfsg-5
ii  libqt5widgets5 5.15.6+dfsg-5
ii  libstdc++6 12.2.0-9

kded5 recommends no packages.

kded5 suggests no packages.

-- no debconf information




Bug#1014460: [pkg-php-pear] Bug#1014460: transition: php8.2

2022-12-15 Thread Ondřej Surý
Hey all,

I think everything is mostly ready in experimental. I'll try to sort out
the rest of the missing extensions over the weekend (imagick, memcached,
redis and maybe few others).

The bump from 8.x to 8.2 is relatively painless, so can we schedule the
transition in few days/weeks?

Ondrej
--
Ondřej Surý (He/Him)
ond...@sury.org



> On 10. 12. 2022, at 17:23, Ondřej Surý  wrote:
> 
> Hi Bas,
> 
> yes, in fact, I've mass uploaded[1] all the extensions to the experimental 
> today
> to be rebuilt with PHP 8.2
> 
> 1. It's kind of hackish, so it might take me couple of retries to figure out 
> the
> right mangling of the packages for the experimental uploads. So far, I hit
> the "empty-binary-package" auto-REJECTs and missing orig source. I hope
> that exp3 did hit the sweet spot, but even that there are couple NEW packages
> built from the source, so it might take some time to get them processed 
> through
> NEW queue.
> 
> Ondrej
> --
> Ondřej Surý (He/Him)
> ond...@sury.org
> 
> 
> 
>> On 5. 12. 2022, at 16:33, Sebastiaan Couwenberg  wrote:
>> 
>> On 10/22/22 21:46, Ondřej Surý wrote:
>>> I'll be uploading the PECL extensions for PHP 8.2 to experimental as I will 
>>> update them
>>> for PHP 8.2 - I haven't started yet, but should be able to do before or 
>>> around the PHP 8.2.0
>>> release.
>> 
>> Do you plan to include php-imagick in this?
>> 
>> I had to rebuild it with php8.2 from experimental for icingaweb2.
>> 
>> Kind regards,
>> 
>> Bas
>> 
>> -- 
>> GPG Key ID: 4096R/6750F10AE88D4AF1
>> Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
>> 
> 



Bug#1026117: golang-gogoprotobuf: FTBFS on all and ppc64el: test failures

2022-12-15 Thread Shengjing Zhu
Control: severity -1 important

On Thu, Dec 15, 2022 at 8:57 AM Cyril Brulebois  wrote:
>
> Source: golang-gogoprotobuf
> Version: 1.3.2-2
> Severity: serious
> Justification: FTBFS
> X-Debbugs-Cc: Jelmer Vernooij 
>
> Hi Jelmer,
>
> Your golang-gogoprotobuf upload FTBFSes on both all and ppc64el:
>   https://buildd.debian.org/status/package.php?p=golang-gogoprotobuf
>
>

I give it back, and it builds now.
https://buildd.debian.org/status/logs.php?pkg=golang-gogoprotobuf=1.3.2-2=all=sid

I have checked the code. It happens when

https://github.com/gogo/protobuf/blob/f67b8970b736e53dbd7d0a27146c8f1ac52f74e5/test/stdtypes/stdtypes.pb.go#L3432

If the rand source returns 0, then NullableTimestamp is not
initialized. There are many places that have the same check.

The code looks totally nonsense to me.

It's dead upstream, anyway.. If the flaky tests cause more troubles,
I'll just disable them.

-- 
Shengjing Zhu



Bug#1021278: (no subject)

2022-12-15 Thread David da Silva Polverari
fixed 1021278 3.0.2-2
thanks



Bug#1026169: dhcpcd5: Please rename source package to dhcpcd

2022-12-15 Thread Martin-Éric Racine
On Thu, Dec 15, 2022 at 8:30 PM Benjamin Drung  wrote:
> The source package name `dhcpcd5` does not reflect the reality any more.
> Debian stable ships version 7 and testing/unstable version 9, but the
> source package name indicates that is the version 5.
>
> Please rename the source package from `dhcpcd5` back to `dhcpcd` and
> probably also the binary package.

I fully agree. I've been meaning to do that at the same time as I
upload 9.4.2, pending upstream release. Now that upstream has informed
me that the next release is unlikely to happen until some time next
month (too close to the freeze), I might do it during the Christmas
vacations instead.

Martin-Éric



Bug#988966: /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure

2022-12-15 Thread Andrey Jr. Melnikov
Source: linux
Followup-For: Bug #988966
X-Debbugs-Cc: temnota...@gmail.com


Hmm. it's woking as intented with kernel from unstable:

# dmesg | grep -E '(dwmac|bcm5|model)'
[0.00] OF: fdt: Machine model: Lamobo R1.1
[   11.746088] sun7i-dwmac 1c5.ethernet: IRQ eth_wake_irq not found
[   11.755334] sun7i-dwmac 1c5.ethernet: IRQ eth_lpi not found
[   11.785153] sun7i-dwmac 1c5.ethernet: PTP uses main clock
[   11.805181] sun7i-dwmac 1c5.ethernet: Version ID not available
[   11.811698] sun7i-dwmac 1c5.ethernet:DWMAC1000
[   11.816825] sun7i-dwmac 1c5.ethernet: No HW DMA feature register 
supported
[   11.824154] sun7i-dwmac 1c5.ethernet: TX Checksum insertion supported
[   11.831067] sun7i-dwmac 1c5.ethernet: Normal descriptors
[   11.836812] sun7i-dwmac 1c5.ethernet: Ring mode enabled
[   12.812030] bcm53xx stmmac-0:1e: found switch: BCM53125, rev 4
[   13.149519] bcm53xx stmmac-0:1e: Using legacy PHYLIB callbacks. Please 
migrate to PHYLINK!
[   13.181089] bcm53xx stmmac-0:1e: Configured port 8 for rgmii-txid
[   13.199161] bcm53xx stmmac-0:1e lan2 (uninitialized): PHY [dsa-0.0:00] 
driver [Broadcom BCM53125] (irq=POLL)
[   13.219947] bcm53xx stmmac-0:1e lan3 (uninitialized): PHY [dsa-0.0:01] 
driver [Broadcom BCM53125] (irq=POLL)
[   13.241375] bcm53xx stmmac-0:1e lan4 (uninitialized): PHY [dsa-0.0:02] 
driver [Broadcom BCM53125] (irq=POLL)
[   13.262036] bcm53xx stmmac-0:1e wan (uninitialized): PHY [dsa-0.0:03] driver 
[Broadcom BCM53125] (irq=POLL)
[   13.278601] bcm53xx stmmac-0:1e lan1 (uninitialized): PHY [dsa-0.0:04] 
driver [Broadcom BCM53125] (irq=POLL)
[   21.348699] sun7i-dwmac 1c5.ethernet eth0: Register MEM_TYPE_PAGE_POOL 
RxQ-0
[   21.358952] sun7i-dwmac 1c5.ethernet eth0: No Safety Features support 
found
[   21.366375] sun7i-dwmac 1c5.ethernet eth0: RX IPC Checksum Offload 
disabled
[   21.373731] sun7i-dwmac 1c5.ethernet eth0: No MAC Management Counters 
available
[   21.381427] sun7i-dwmac 1c5.ethernet eth0: PTP not supported by HW
[   21.391146] sun7i-dwmac 1c5.ethernet eth0: configuring for fixed/rgmii 
link mode
[   21.401844] sun7i-dwmac 1c5.ethernet eth0: Link is Up - 1Gbps/Full - 
flow control off
[   21.428685] bcm53xx stmmac-0:1e lan1: configuring for phy/gmii link mode
[   21.437145] bcm53xx stmmac-0:1e lan1: Link is Up - 1Gbps/Full - flow control 
off
[   21.520381] bcm53xx stmmac-0:1e lan2: configuring for phy/gmii link mode
[   21.632977] bcm53xx stmmac-0:1e lan3: configuring for phy/gmii link mode
[   21.748557] bcm53xx stmmac-0:1e lan4: configuring for phy/gmii link mode
[   21.758708] bcm53xx stmmac-0:1e lan4: Link is Up - 100Mbps/Full - flow 
control off
[   27.067850] bcm53xx stmmac-0:1e wan: configuring for phy/gmii link mode
[   27.076441] bcm53xx stmmac-0:1e wan: Link is Up - 100Mbps/Full - flow 
control off

# bridge link
3: lan2@eth0:  mtu 1500 master br-lan state 
disabled priority 32 cost 100 
4: lan3@eth0:  mtu 1500 master br-lan state 
disabled priority 32 cost 100 
5: lan4@eth0:  mtu 1500 master br-lan state 
forwarding priority 32 cost 19 
7: lan1@eth0:  mtu 1500 master br-lan state 
forwarding priority 32 cost 4 

But installer stupidity "enable only one interface" prevent use any port on 
bcm53xx
switch - master port eth0 MUST BE ACTIVE.

-- System Information:
Debian Release: 11.5
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable'), (400, 'unstable'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 6.0.0-4-armmp-lpae (SMP w/2 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled



Bug#1018265: closed by Brian Potkin (cups picks manual tray on HP Color LaserJet M252dw)

2022-12-15 Thread Steinar Bang
> "Debian Bug Tracking System" :

> The thread beginning at

>   https://lists.cups.org/pipermail/cups/2022-December/075172.html

> indicates that this issue is now resolved. Hence closing.

Personally I won't say that I see it as resolved, yet.

It won't be, until I get predictable behaviour, and I don't have that, yet.



Bug#1026167: balsa: Balsa truncates the mail title

2022-12-15 Thread Jeremy Bicha
On Thu, Dec 15, 2022 at 12:15 PM Nicolas Patrois
 wrote:
> Package: balsa
> Version: 2.6.4-1
> Severity: minor
> Tags: upstream
>
> Dear Maintainer,
>
> Since the last upgrade, Balsa truncates the mail titles’ display.
> Yes, only their display: I checked with the mail command line tool.

Please report this issue to
https://gitlab.gnome.org/GNOME/balsa/-/issues

Thanks,
Jeremy Bicha



Bug#1026099: wireplumber: consider adding the NEWS(.rst) file?

2022-12-15 Thread Patrice Duroux
Hi Dylan,
No, sure that it is already there as changelog.gz.
The bug is on my side, sorry.
Regards,
Patrice

Le jeu. 15 déc. 2022 à 12:29, Dylan Aïssi  a écrit :
>
> Bonjour Patrice,
>
> Le mer. 14 déc. 2022 à 19:27, Patrice Duroux
>  a écrit :
> >
> > It would be very nice.
>
> The NEWS.rst file is already installed with each wireplumber binary packages
> since 0.4.8-1 [1] as you already reported #1003836 [2] .
> Am I missing something?
>
> [1] https://salsa.debian.org/utopia-team/wireplumber/-/commit/e49a5d0e
> [2] https://bugs.debian.org/1003836
>
> > I am not sure about another file (README.rst) regarding its content.
>
> README.rst doesn't contain any useful information for users and we have a
> wireplumber-doc package with the full documentation.
>
> Best,
> Dylan
>
> BTW, feel free to open merge requests if you feel some improvements can be 
> done.



Bug#1021278:

2022-12-15 Thread David Polverari
fixed 1021278 3.0.2-1
thanks



Bug#1026169: dhcpcd5: Please rename source package to dhcpcd

2022-12-15 Thread Benjamin Drung
Source: dhcpcd5
Version: 9.4.1-11
Severity: normal
X-Debbugs-Cc: bdr...@debian.org

Dear Maintainer,

The source package name `dhcpcd5` does not reflect the reality any more.
Debian stable ships version 7 and testing/unstable version 9, but the
source package name indicates that is the version 5.

Please rename the source package from `dhcpcd5` back to `dhcpcd` and
probably also the binary package.

The package has only a few bug reports and therefore this source package
rename should be easy.

Thanks.

-- 
Benjamin Drung
Debian & Ubuntu Developer



Bug#1026116: Patches not applied in security release deb10u6, FTBFS

2022-12-15 Thread Emilio Pozuelo Monfort

On 15/12/2022 18:42, Sven Joachim wrote:

Control: forcemerge 989852 -1

Am 15.12.2022 um 01:16 schrieb Mihai Moldovan:


Package: xorg-server-source
Version: 2:1.20.4-1+deb10u6
Severity: normal

Hi


It looks like the content of debian/patches/ has not been applied when packaging
xorg-server-source.

This at least one patch contains a FTBFS fix, it's impossible to build
xorg-server out of the box.

This is a regression - older versions of the same package (also in buster) had
the patches applied just fine. The Debian Security release, however, does not.


It seems you are slightly mistaken here, as the same problem had been
reported for 2:1.20.4-1+deb10u3 already.  It has been fixed post-buster
in 2:1.20.6-1.


I'm not sure I understand what the problem is. The patches are in 
debian/patches/ and are applied during build using quilt.


From the amd64's build log [1]:

dh build-arch --with quilt,autoreconf --parallel
   dh_quilt_patch -a -O--parallel
Applying patch 001_fedora_extramodes.patch
patching file hw/xfree86/common/extramodes

Applying patch 02_kbsd-input-devd.diff
patching file config/Makefile.am
patching file config/config-backends.h
patching file config/config.c
patching file config/devd.c
patching file configure.ac
Hunk #1 succeeded at 568 (offset 2 lines).
Hunk #2 succeeded at 954 (offset 3 lines).
Hunk #3 succeeded at 2483 (offset 38 lines).
patching file hw/xfree86/common/xf86Config.c
Hunk #1 succeeded at 1264 (offset 7 lines).
patching file hw/xfree86/common/xf86Globals.c
Hunk #1 succeeded at 119 (offset 2 lines).
patching file include/dix-config.h.in
Hunk #1 succeeded at 424 (offset -9 lines).
[...]

Cheers,
Emilio

[1] 
https://buildd.debian.org/status/fetch.php?pkg=xorg-server=amd64=2%3A1.20.4-1%2Bdeb10u6=1667984267=0




Bug#1022974: hplip: Needs sudo but does not depend on it

2022-12-15 Thread Brian Potkin
tags 1022974 moreinfo
thanks



On Fri 28 Oct 2022 at 19:11:36 +0300, Teemu Ikonen wrote:

> Package: hplip
> Version: 3.22.6+dfsg0-1
> Severity: normal
> X-Debbugs-Cc: tpiko...@gmail.com
> 
> When installing the non-free plugin with hp-plugin, the installer
> authenticates using 'sudo'. If sudo is not installed, the password
> prompt always reports an invalid password error.
> 
> hplip package should depend on sudo. Bonus points for checking that the
> sudo configuration works before starting the installation.

Thank you for your report, Teemu. Please inicate whether Debian was
installed with or without a root account.

Regards,
Brian.



Bug#1026116: Patches not applied in security release deb10u6, FTBFS

2022-12-15 Thread Sven Joachim
Control: forcemerge 989852 -1

Am 15.12.2022 um 01:16 schrieb Mihai Moldovan:

> Package: xorg-server-source
> Version: 2:1.20.4-1+deb10u6
> Severity: normal
>
> Hi
>
>
> It looks like the content of debian/patches/ has not been applied when 
> packaging
> xorg-server-source.
>
> This at least one patch contains a FTBFS fix, it's impossible to build
> xorg-server out of the box.
>
> This is a regression - older versions of the same package (also in buster) had
> the patches applied just fine. The Debian Security release, however, does not.

It seems you are slightly mistaken here, as the same problem had been
reported for 2:1.20.4-1+deb10u3 already.  It has been fixed post-buster
in 2:1.20.6-1.

Cheers,
   Sven



Bug#805940: Wrong diagnosis

2022-12-15 Thread Jeremy Sowden
Actually, the warning is still present, but I've got to the bottom of
why it's occurring.  Details in https://bugs.debian.org/731638.

J.


signature.asc
Description: PGP signature


Bug#731638: Wrong diagnosis

2022-12-15 Thread Jeremy Sowden
Actually, I've just realized that we've all been barking up the wrong
tree here.  The problem has nothing to do with the transition from ulogd
to ulogd2.  For example, here's a fresh install of the package currently
in testing:

  $ apt-cache policy ulogd2
  ulogd2:
Installed: (none)
Candidate: 2.0.7-1+b3
Version table:
   2.0.7-1+b3 990
  990 http://mirror.ox.ac.uk/debian testing/main amd64 Packages
  990 http://ftp.uk.debian.org/debian testing/main amd64 Packages
  990 http://ftp.debian.org/debian testing/main amd64 Packages
   99 http://mirror.ox.ac.uk/debian unstable/main amd64 Packages
   99 http://ftp.uk.debian.org/debian unstable/main amd64 Packages
   99 http://ftp.debian.org/debian unstable/main amd64 Packages
   2.0.7-1+b1 900
  900 http://mirror.ox.ac.uk/debian stable/main amd64 Packages
  900 http://ftp.uk.debian.org/debian stable/main amd64 Packages
  900 http://ftp.debian.org/debian stable/main amd64 Packages
  $ ls -ld /var/log/ulog
  ls: cannot access '/var/log/ulog': No such file or directory
  $ sudo apt-get install ulogd2
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Suggested packages:
ulogd2-dbi ulogd2-json ulogd2-mysql ulogd2-pcap ulogd2-pgsql ulogd2-sqlite3
  The following NEW packages will be installed:
ulogd2
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/108 kB of archives.
  After this operation, 569 kB of additional disk space will be used.
  Selecting previously unselected package ulogd2.
  (Reading database ... 585103 files and directories currently installed.)
  Preparing to unpack .../ulogd2_2.0.7-1+b3_amd64.deb ...
  Unpacking ulogd2 (2.0.7-1+b3) ...
  Setting up ulogd2 (2.0.7-1+b3) ...
  adduser: Warning: The home dir /var/log/ulog you specified already exists.
  adduser: The home directory `/var/log/ulog' already exists.  Not copying from 
`/etc/skel'.
  adduser: Warning: The home directory `/var/log/ulog' does not belong to the 
user you are currently creating.

The problem is the source package lists /var/log/ulog in ulogd2.dirs, so
dh_installdir creates it with ownership `root:root` and mode
`u=rwx,go=rx` and it is present in the binary package:

  $ dpkg-deb --contents /var/cache/apt/archives/ulogd2_2.0.7-1+b3_amd64.deb | 
grep /var/log/ulog
  drwxr-xr-x root/root 0 2022-10-16 11:37 ./var/log/ulog/

On a fresh install, therefore, when the package is unpacked the
directory is created with the wrong ownership and permissions.
Thereafter, adduser runs and complains about it.

However, since 2.0.5-5, the postinst script has called mkdir to create
the directory again and then fixed up the ownership and permissions, so
although the warning is still present, in the end the directory is
correctly set up.

J.


signature.asc
Description: PGP signature


Bug#1026167: balsa: Balsa truncates the mail title

2022-12-15 Thread Nicolas Patrois
Package: balsa
Version: 2.6.4-1
Severity: minor
Tags: upstream

Dear Maintainer,

Since the last upgrade, Balsa truncates the mail titles’ display.
Yes, only their display: I checked with the mail command line tool.

Regards,
n.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 5.16.0-6-686-pae (SMP w/3 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages balsa depends on:
ii  balsa-data  2.6.4-1
ii  libc6   2.36-6
ii  libcairo2   1.16.0-7
ii  libcanberra-gtk3-0  0.30-10
ii  libcanberra00.30-10
ii  libcompfaceg1   1:1.5.2-5.1
ii  libfribidi0 1.0.8-2.1
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-1
ii  libglib2.0-02.74.3-1
ii  libgmime-3.0-0  3.2.13+dfsg-2
ii  libgnutls30 3.7.8-4
ii  libgpgme11  1.18.0-3
ii  libgspell-1-2   1.12.0-1+b1
ii  libgssapi-krb5-21.20.1-1
ii  libgtk-3-0  3.24.35-3
ii  libgtksourceview-4-04.8.4-1
ii  libical33.0.16-1+b1
ii  libldap-2.5-0   2.5.13+dfsg-2+b1
ii  libpango-1.0-0  1.50.10+ds-1
ii  libpangocairo-1.0-0 1.50.10+ds-1
ii  libsecret-1-0   0.20.5-3
ii  libsqlite3-03.40.0-1
ii  libwebkit2gtk-4.0-372.38.2-1+b1
ii  libxml2 2.9.14+dfsg-1.1+b2
ii  pinentry-gnome3 [pinentry-x11]  1.2.1-1
ii  pinentry-gtk2 [pinentry-x11]1.2.1-1

Versions of packages balsa recommends:
ii  ca-certificates20211016
ii  gpgsm  2.2.40-1
ii  python3-html2text  2020.1.16-2
ii  yelp   42.2-1

balsa suggests no packages.

-- no debconf information


Bug#1026168: Xwayland: enable full hardening flags (BINDNOW)

2022-12-15 Thread Christian Göttsche
Source: xwayland
Version: 2:22.1.6-1
Tags: security,patch

Dear Maintaner,

please enable full hardening flags for Xwayland; in particular
currently the link feature BINDNOW[1] is missing.
As Xwayland is a long running daemon any potential startup costs are negligible.


[1]: 
https://wiki.debian.org/Hardening#DEB_BUILD_HARDENING_BINDNOW_.28ld_-z_now.29


diff --git a/debian/rules b/debian/rules
index 9cdefd5..3d384eb 100755
--- a/debian/rules
+++ b/debian/rules
@@ -2,6 +2,8 @@

include /usr/share/dpkg/pkg-info.mk

+export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+
SUPPORT = https://www.debian.org/support

%:



Bug#988260: guix: GNOME sessions crash with mismatched glib-2.0 schemas

2022-12-15 Thread Vagrant Cascadian
On 2022-12-15, Alberto Luaces wrote:
> Just confirming this issue also affects debian's emacs.
>
> /etc/profile.d/guix.sh implicitly sets up EMACSLOADPATH when sourcing
> the profile.
>
> I think that emacs only reads dirs in EMACSLOADPATH if it is set, so
> after that any .el files under /usr/ are not found.  Even if that were
> not the case, I also think that it would be still undesirable for
> debian emacs to look first into the guix profile directories, since it
> could cause mixed version .el file loads.
>
> I am a new guix user, so maybe I am not understanding something, but I
> tend to believe that currently the rationale is that it is not
> expected that the user can have co-existing guix and debian versions
> of the same software.

There are certain softwares where this is not possible because of how
they are designed, yes... namely anything that uses a PATH-like variable
that does not work with multiple sources, or modules that cannot handle
multiple underlying libraries at play...

Figuring that out on a case-by-case basis is definitely tricky.


> So far I have deleted /etc/profile.d/guix.sh and I am proceeding to
> activate guix profiles only when I am needing them.

This will mean you will need to manually add the guix profile
directories to your path if you want to be able to access software
installed via guix in your user profile, and to add the guix installed
via "guix pull" to your PATH (e.g. to get newer versions of software
and/or features available in guix).


live well,
  vagrant


signature.asc
Description: PGP signature


Bug#1026087: ITP: distribution-gpg-keys -- GPG keys by various Linux distributions

2022-12-15 Thread Adam Borowski
On Thu, Dec 15, 2022 at 03:12:21PM +0100, Guillem Jover wrote:
> On Wed, 2022-12-14 at 15:27:18 +0100, Juri Grabowski wrote:
> > * Package name: distribution-gpg-keys
> >   Upstream Author : Miroslav Suchý 
> > * URL : https://github.com/xsuchy/distribution-gpg-keys/
> >   Description : GPG keys by various Linux distributions
> > 
> > used by various Linux distributions to sign packages.
> > 
> > needed by mock/3.5 and I need a sponsor for this package. See current 
> > packaging in
> > https://salsa.debian.org/pkg-rpm-team/distribution-gpg-keys
> > After I know ITP bug number I upload this source package to
> > https://mentors.debian.net/package/distribution-gpg-keys/

> (If this project is also intended to only cover RPM-based distributions,
> as Adam brought up, you might want to further ask them to make that clear
> from the project name, say rpm-distribution-openpgp-keys or similar.

When in that project's native environment, ie a RPM distribution, the name
_is_ adequate.  It's only in Debian (/Alpine/Arch/Gentoo/...) where the
name can be confusing.  But then, there's no requirement for the package
name to match upstream.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Quis trollabit ipsos trollos?
⠈⠳⣄



Bug#1026166: mujoco: FTBFS on amd64 (symbols mismatches)

2022-12-15 Thread Gianfranco Costamagna

Source: mujoco
Version: 2.2.2-3
tags: patch

Hello, I found some more symbol disappearing on amd64 with different 
compiler/optimization.

Please mark them as optional, since they seems to be not part of the API anyway

diff -Nru mujoco-2.2.2/debian/changelog mujoco-2.2.2/debian/changelog
--- mujoco-2.2.2/debian/changelog   2022-12-14 17:09:03.0 +0100
+++ mujoco-2.2.2/debian/changelog   2022-12-15 17:44:27.0 +0100
@@ -1,3 +1,9 @@
+mujoco (2.2.2-3.1) unstable; urgency=medium
+
+  * Mark some more symbols as optional (Closes: #-1)
+
+ -- Gianfranco Costamagna   Thu, 15 Dec 2022 
17:44:27 +0100
+
 mujoco (2.2.2-3) unstable; urgency=medium

   * Fix symbols and riscv64 build (Closes: #1022065, #1025682)
diff -Nru mujoco-2.2.2/debian/libmujoco2.2.2.symbols.amd64 
mujoco-2.2.2/debian/libmujoco2.2.2.symbols.amd64
--- mujoco-2.2.2/debian/libmujoco2.2.2.symbols.amd642022-12-14 
17:07:57.0 +0100
+++ mujoco-2.2.2/debian/libmujoco2.2.2.symbols.amd642022-12-15 
17:44:25.0 +0100
@@ -29,10 +29,10 @@
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 2.2.0
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
 2.2.0
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE4findERS7_@Base
 2.2.0
- 
_ZSt16__do_uninit_copyIN9__gnu_cxx17__normal_iteratorIPKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt6vectorIS7_SaIS7_PS7_ET0_T_SG_SF_@Base
 2.2.2
+ 
(optional)_ZSt16__do_uninit_copyIN9__gnu_cxx17__normal_iteratorIPKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt6vectorIS7_SaIS7_PS7_ET0_T_SG_SF_@Base
 2.2.2
  
(optional)_ZStplIcSt11char_traitsIcESaIcEENSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_RKS8_@Base
 2.2.0
- _ZTI13mj_XMLPrinter@Base 2.2.0
- _ZTS13mj_XMLPrinter@Base 2.2.0
+ (optional)_ZTI13mj_XMLPrinter@Base 2.2.0
+ (optional)_ZTS13mj_XMLPrinter@Base 2.2.0
  (optional)_ZTV13mj_XMLPrinter@Base 2.2.0
  _mjPRIVATE__get_tls_error_fn@Base 2.2.0
  _mjPRIVATE__get_tls_warning_fn@Base 2.2.0


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1013578: Proposed fix for bullseye

2022-12-15 Thread Martina Ferrari

Hi Santiago,

I am sorry I could not look into this before, I have been very busy lately.

On 09/12/2022 00:00, Santiago Vila wrote:

Hi. Could somebody (not necessarily Martina) take care of this?
The proposed debdiff is in the previous message.


I will try this now, I have never done it before :)

[ I'm not a big fan of NMUs, so I'm actually considering to apply to 
join the team just for QA issues like this one. Would that be ok for you? ]


Totally! and most welcomed!

--
Martina Ferrari (Tina)



Bug#828903: auditd embeds a copy of libev

2022-12-15 Thread Bastian Germann

Control: severity -1 important
Control: tags -1 patch

On Tue, 28 Jun 2016 22:28:07 +0200 Nicolas Braud-Santoni 
 wrote:

The audit source package ships a (custom, patched) copy of libev.

Moreover, it is not listed in the security team's list of code copies:


https://anonscm.debian.org/viewvc/secure-testing/data/embedded-code-copies?view=markup


I discovered the issue while preparing a DEP5 copyright file for
the audit source package, and more generally fixing all Lintian
warnings while preparing a patch for #759604.


I think this is an important issue and have included a patch.
Would you please consider to apply this before the bookworm freeze?From a90a5a128acb223185efcad5e2bdacc573e04b72 Mon Sep 17 00:00:00 2001
From: Bastian Germann 
Date: Thu, 15 Dec 2022 16:52:28 +0100
Subject: [PATCH] Build auditd with system libev. (Closes: #828903)

The source package has an embedded libev, which is discouraged, and according to
the bug report it is not even registered at the Security Team.

Patch auditd's Makefile.am to use the system library.

Set EV_CHILD_ENABLE=0 as the build will break intentionally with it set.
---
 debian/control|  3 +-
 .../05-Build-auditd-with-system-libev.patch   | 38 +++
 debian/patches/series |  1 +
 debian/rules  |  1 +
 4 files changed, 41 insertions(+), 2 deletions(-)
 create mode 100644 debian/patches/05-Build-auditd-with-system-libev.patch

diff --git a/debian/control b/debian/control
index 5ad89d0..aaf1e28 100644
--- a/debian/control
+++ b/debian/control
@@ -6,8 +6,7 @@ Build-Depends: debhelper-compat (= 12),
 #   dh-golang,
dpkg-dev (>= 1.16.1~),
libcap-ng-dev,
-# audit sources embed their own patched version of libev
-#   libev-dev,
+   libev-dev,
libkrb5-dev,
libldap2-dev ,
libwrap0-dev,
diff --git a/debian/patches/05-Build-auditd-with-system-libev.patch b/debian/patches/05-Build-auditd-with-system-libev.patch
new file mode 100644
index 000..5ba81bd
--- /dev/null
+++ b/debian/patches/05-Build-auditd-with-system-libev.patch
@@ -0,0 +1,38 @@
+From: Bastian Germann 
+Date: Thu, 15 Dec 2022 16:48:04 +0100
+Forwarded: not-needed
+Subject: Build auditd with system libev
+
+---
+ src/Makefile.am | 7 ++-
+ 1 file changed, 2 insertions(+), 5 deletions(-)
+
+diff --git a/src/Makefile.am b/src/Makefile.am
+index 9c68b42..c759ca2 100644
+--- a/src/Makefile.am
 b/src/Makefile.am
+@@ -23,7 +23,7 @@
+ 
+ CONFIG_CLEAN_FILES = *.rej *.orig
+ SUBDIRS = test
+-AM_CPPFLAGS = -I${top_srcdir} -I${top_srcdir}/lib -I${top_srcdir}/src/libev -I${top_srcdir}/auparse -I${top_srcdir}/audisp -I${top_srcdir}/common
++AM_CPPFLAGS = -I${top_srcdir} -I${top_srcdir}/lib -I${top_srcdir}/auparse -I${top_srcdir}/audisp -I${top_srcdir}/common
+ sbin_PROGRAMS = auditd auditctl aureport ausearch autrace
+ AM_CFLAGS = -D_GNU_SOURCE -Wno-pointer-sign
+ noinst_HEADERS = auditd-config.h auditd-event.h auditd-listen.h ausearch-llist.h ausearch-options.h auditctl-llist.h aureport-options.h ausearch-parse.h aureport-scan.h ausearch-lookup.h ausearch-int.h auditd-dispatch.h ausearch-string.h ausearch-nvpair.h ausearch-common.h ausearch-avc.h ausearch-time.h ausearch-lol.h auditctl-listing.h ausearch-checkpt.h
+@@ -34,7 +34,7 @@ auditd_SOURCES += auditd-listen.c
+ endif
+ auditd_CFLAGS = -fPIE -DPIE -g -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pthread -Wno-pointer-sign
+ auditd_LDFLAGS = -pie -Wl,-z,relro -Wl,-z,now
+-auditd_LDADD = @LIBWRAP_LIBS@ ${top_builddir}/src/libev/libev.la ${top_builddir}/audisp/libdisp.la ${top_builddir}/lib/libaudit.la ${top_builddir}/auparse/libauparse.la -lpthread -lm $(gss_libs) ${top_builddir}/common/libaucommon.la
++auditd_LDADD = @LIBWRAP_LIBS@ ${top_builddir}/audisp/libdisp.la ${top_builddir}/lib/libaudit.la ${top_builddir}/auparse/libauparse.la -lpthread -lm -lev $(gss_libs) ${top_builddir}/common/libaucommon.la
+ 
+ auditctl_SOURCES = auditctl.c auditctl-llist.c delete_all.c auditctl-listing.c
+ auditctl_CFLAGS = -fPIE -DPIE -g -D_GNU_SOURCE
+@@ -49,6 +49,3 @@ ausearch_LDADD = ${top_builddir}/lib/libaudit.la ${top_builddir}/auparse/libaupa
+ 
+ autrace_SOURCES = autrace.c delete_all.c auditctl-llist.c
+ autrace_LDADD = ${top_builddir}/lib/libaudit.la
+-
+-libev/libev.a:
+-	make -C libev
diff --git a/debian/patches/series b/debian/patches/series
index 8c07650..b634337 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -2,3 +2,4 @@
 02-restorecon-path.patch
 03-Set-log_group-adm.patch
 04-auditswig-i-avoid-setter-generation-for-audit-rule-data.patch
+05-Build-auditd-with-system-libev.patch
diff --git a/debian/rules b/debian/rules
index 63d45fc..4522ad1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,6 +4,7 @@ DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 include /usr/share/dpkg/architecture.mk
 
+CPPFLAGS += 

Bug#1026165: Please drop build dependency on obsolete python3-contextlib2

2022-12-15 Thread Jochen Sprickerhof
Source: cmd2
Version: 2.4.2+ds-2
Severity: normal

Hi Josenilson,

we are in the transition to Python 3.11 and python3-contextlib2 is
currently RC buggy. As it is an obsolete package anyhow we would like to
remove it. The cmd2 build depends on it but does not need it and builds
fine without it as well. Would you be ok if I do a non maintainer upload
to fix this?

Cheers Jochen


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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



Bug#1024547: ITP: sparrow -- Bitcoin wallet with a focus on privacy and usability

2022-12-15 Thread Sam Hartman
> "Craig" == Craig Raw  writes:


Craig> I assume the next step is to upload these two files, but I'm
Craig> uncertain of where or how to do this.

No, probably the next step is to make sure all the dependencies are
packaged in Debian
and then to generate a Debian format source package that generates debs
similar to those.

See https://www.debian.org/doc/manuals/maint-guide/


That's probably targeted at packaging software written in C.
You probably will want to look at the Debian Java team's pages
https://wiki.debian.org/Teams/JavaPackaging

for how they do things
and of course the developers reference for procedures on things like
sponsorship (which you will need since you are not a Debian developer)
https://www.debian.org/doc/manuals/developers-reference/



Bug#1026164: ffprobe: "-of json" doesn't report anything

2022-12-15 Thread Matthias Urlichs
Package: ffmpeg
Version: 7:5.1.2-1
Severity: important
X-Debbugs-Cc: sm...@smurf.noris.de

$ ffprobe -of json ./01.ogg >/tmp/ff.stdout 2>/tmp/ff.stderr
$ cat /tmp/ff.stderr
ffprobe version 5.1.2-1 Copyright (c) 2007-2022 the FFmpeg developers
  built with gcc 12 (Debian 12.2.0-3)
  configuration: --prefix=/usr --extra-version=1 --toolchain=hardened 
--libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu 
--arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa 
--enable-libaom --enable-libass --enable-libbluray --enable-libbs2b 
--enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d 
--enable-libflite --enable-libfontconfig --enable-libfreetype 
--enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm 
--enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg 
--enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq 
--enable-librist --enable-librubberband --enable-libshine --enable-libsnappy 
--enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh 
--enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab 
--enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 
--enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq 
--enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl 
--enable-opengl --enable-sdl2 --disable-sndio --enable-pocketsphinx 
--enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm 
--enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 
--enable-libplacebo --enable-librav1e --enable-shared
  libavutil  57. 28.100 / 57. 28.100
  libavcodec 59. 37.100 / 59. 37.100
  libavformat59. 27.100 / 59. 27.100
  libavdevice59.  7.100 / 59.  7.100
  libavfilter 8. 44.100 /  8. 44.100
  libswscale  6.  7.100 /  6.  7.100
  libswresample   4.  7.100 /  4.  7.100
  libpostproc56.  6.100 / 56.  6.100
Input #0, ogg, from './01.ogg':
  Duration: 00:02:36.45, start: 0.00, bitrate: 141 kb/s
  Stream #0:0: Audio: vorbis, 44100 Hz, stereo, fltp, 160 kb/s
$ cat /tmp/ff.stdout
{

}

I'm fairly sure that this is not the intended behavior.

Upstream says that this works for them.
https://trac.ffmpeg.org/ticket/10104

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'stable'), (600, 'oldstable'), (500, 
'stable-security'), (500, 'unstable'), (450, 'focal'), (350, 'oldoldstable'), 
(300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.0.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 ffmpeg depends on:
ii  libavcodec597:5.1.2-1
ii  libavdevice59   7:5.1.2-1
ii  libavfilter87:5.1.2-1
ii  libavformat59   7:5.1.2-1
ii  libavutil57 7:5.1.2-1
ii  libc6   2.36-6
ii  libpostproc56   7:5.1.2-1
ii  libsdl2-2.0-0   2.24.2+dfsg-1
ii  libswresample4  7:5.1.2-1
ii  libswscale6 7:5.1.2-1

ffmpeg recommends no packages.

Versions of packages ffmpeg suggests:
pn  ffmpeg-doc  

-- debconf-show failed



Bug#988260: guix: GNOME sessions crash with mismatched glib-2.0 schemas

2022-12-15 Thread Alberto Luaces
Package: guix
Version: 1.3.0-5+b1
Followup-For: Bug #988260
X-Debbugs-Cc: alua...@udc.es

Just confirming this issue also affects debian's emacs.

/etc/profile.d/guix.sh implicitly sets up EMACSLOADPATH when sourcing
the profile.

I think that emacs only reads dirs in EMACSLOADPATH if it is set, so
after that any .el files under /usr/ are not found.  Even if that were
not the case, I also think that it would be still undesirable for
debian emacs to look first into the guix profile directories, since it
could cause mixed version .el file loads.

I am a new guix user, so maybe I am not understanding something, but I
tend to believe that currently the rationale is that it is not
expected that the user can have co-existing guix and debian versions
of the same software.

So far I have deleted /etc/profile.d/guix.sh and I am proceeding to
activate guix profiles only when I am needing them.

Regards.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 guix depends on:
ii  guile-3.0   3.0.8-2
ii  guile-3.0-libs  3.0.8-2
ii  guile-gcrypt0.4.0-2
ii  guile-git   0.5.2-5
ii  guile-gnutls3.7.8-4
ii  guile-json  4.7.3-2
ii  guile-lzlib 0.0.2-3
ii  guile-sqlite3   0.1.3-3
ii  guile-ssh   0.16.0-2
ii  guile-zlib  0.1.0-4
ii  libbz2-1.0  1.0.8-5+b1
ii  libc6   2.36-6
ii  libgcc-s1   12.2.0-9
ii  libgcrypt20 1.10.1-3
ii  libsqlite3-03.40.0-1
ii  libssh-dev  0.10.4-2
ii  libstdc++6  12.2.0-9
ii  zlib1g  1:1.2.13.dfsg-1

Versions of packages guix recommends:
ii  ca-certificates  20211016
ii  less 590-1
ii  nscd 2.36-6
ii  systemd  252.2-2

guix suggests no packages.

-- Configuration Files:
/etc/profile.d/guix.sh [Errno 2] No existe el fichero o el directorio: 
'/etc/profile.d/guix.sh'

-- no debconf information



Bug#1026163: Uses Java 11

2022-12-15 Thread Moritz Muehlenhoff
Source: puppetdb
Version: 7.11.2-3
Severity: grave

Thanks for all the great work on Puppetdb!

I was trying to setup a test environment with Puppetdb 7.11.2 from current
testing and I noticed that it's using openjdk-11-jre-headless.

While openjdk-11 is currently still in testing, Bookworm will only
include openjdk-17 (#1023237).

Cheers,
 Moritz



Bug#1026027: graphical installer: using nano in a installer shell fails

2022-12-15 Thread Philip Hands
Holger Wansing  writes:

> Hi,
>
> Philip Hands  wrote (Tue, 13 Dec 2022 20:34:17 +0100):
>> On the 11.5 netinst I just tried out, in the Graphical Install's shell,
>> TERM=xterm so that's obviously not the cause of the issue, but the
>> difference would appear to be that it has:
>> 
>>   /usr/share/vte/termcap-0.0/xterm
>> 
>> So I guess the fix for this is either to make sure that that termcap
>> file gets installed again, or to set TERM in the Graphical Install's
>> shell to something like 'bterm' or 'vt102'.
>> 
>> I suspect restoring the termcap file is the correct fix.
>
> /usr/share/vte/termcap-0.0/xterm is there on dailies.

Oh, so it is.  Hmm, I seem not to have checked that bit, sorry.

Perhaps the presence of the termcap file is irrelevant, or could it be
that nano used to be able to make use of that, and more recently only
supports terminfo?

> Hmm. Kibi mentioned that this bug comes from ncurses (however I fail to
> see any details here), should this be redirected to ncurses then?

Well, ncurses-base provides /lib/terminfo/x/xterm (in normal .deb
packages), so perhaps that's why, although AFAICS it wasn't including
that file in the udeb, even when things were working.

Making it ship a terminfo for xterm in the udeb would probably fix
things, but I think it would also be quite nice to know why it broke.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature


Bug#1026087: ITP: distribution-gpg-keys -- GPG keys by various Linux distributions

2022-12-15 Thread Guillem Jover
Hi!

On Wed, 2022-12-14 at 15:27:18 +0100, Juri Grabowski wrote:
> Package: wnpp
> Version: 1.79
> Severity: wishlist
> Owner: Juri Grabowski 
> X-Debbugs-Cc: debian-de...@lists.debian.org, deb...@jugra.de

> * Package name: distribution-gpg-keys
>   Version : 1.7.9
>   Upstream Author : Miroslav Suchý 
> * URL : https://github.com/xsuchy/distribution-gpg-keys/
> * License : CC0-1.0
>   Programming Lang: data
>   Description : GPG keys by various Linux distributions
> 
> used by various Linux distributions to sign packages.
> 
> needed by mock/3.5 and I need a sponsor for this package. See current 
> packaging in
> https://salsa.debian.org/pkg-rpm-team/distribution-gpg-keys
> After I know ITP bug number I upload this source package to
> https://mentors.debian.net/package/distribution-gpg-keys/

The project name talks about gpg keys, but those are really OpenPGP
keys (or even better, certificates). I've asked upstream to rename the
project to avoid this common confusion. So you might want to wait until
that's settled to avoid multiple trips over NEW.

  

(If this project is also intended to only cover RPM-based distributions,
as Adam brought up, you might want to further ask them to make that clear
from the project name, say rpm-distribution-openpgp-keys or similar. But
in any case regardless of the intended target use, it still seems like a
very generic name which can be easily confused for a package that would
be needed for Debian, or derivatives.)

Thanks,
Guillem



Bug#1026162: /usr/bin/keystone-manage: keystone-manage db_sync fails with traceback

2022-12-15 Thread Wojtek Porczyk
Package: python3-keystone
Version: 2:22.0.0-1.1
Severity: important
File: /usr/bin/keystone-manage

% keystone-manage db_sync
Exception ignored in: 
Traceback (most recent call last):
  File "/usr/lib/python3.10/logging/__init__.py", line 846, in _removeHandlerRef
  File "/usr/lib/python3.10/logging/__init__.py", line 226, in _acquireLock
  File "/usr/lib/python3.10/threading.py", line 164, in acquire
  File "/usr/lib/python3/dist-packages/eventlet/green/thread.py", line 34, in 
get_ident
AttributeError: 'NoneType' object has no attribute 'getcurrent'
keystone-manage db_sync  3.97s user 0.27s system 98% cpu 4.287 total
%


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-5-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-keystone depends on:
ii  python33.10.6-1
ii  python3-bcrypt 3.2.0-1+b2
ii  python3-cryptography   3.4.8-2
ii  python3-dateutil   2.8.2-1
ii  python3-dogpile.cache  1.1.8-2
ii  python3-flask  2.2.2-2
ii  python3-flask-restful  0.3.9-4
ii  python3-jsonschema 4.7.2-3
ii  python3-jwt2.4.0-2
ii  python3-keystoneclient 1:5.0.1-2
ii  python3-keystonemiddleware 10.1.0-4
ii  python3-ldap [python3-pyldap]  3.4.3-2+b1
ii  python3-ldappool   3.0.0-2
ii  python3-lxml   4.9.1-1+b2
ii  python3-memcache   1.59-5
ii  python3-migrate0.13.0-3
ii  python3-msgpack1.0.3-2
ii  python3-oauthlib   3.2.1-2
ii  python3-openstackclient6.0.0-2
ii  python3-oslo.cache 3.2.0-1
ii  python3-oslo.config1:9.0.0-3
ii  python3-oslo.context   5.0.0-2
ii  python3-oslo.db12.1.0-2
ii  python3-oslo.i18n  5.1.0-2
ii  python3-oslo.log   5.0.1-1
ii  python3-oslo.messaging 14.0.0-2
ii  python3-oslo.middleware5.0.0-2
ii  python3-oslo.policy4.0.0-2
ii  python3-oslo.serialization 5.0.0-2
ii  python3-oslo.upgradecheck  2.0.0-2
ii  python3-oslo.utils 6.0.1-2
ii  python3-osprofiler 3.4.3-2
ii  python3-passlib1.7.4-3
ii  python3-pbr5.10.0-2
ii  python3-pycadf 3.1.1-2
ii  python3-pymysql1.0.2-2
ii  python3-pysaml27.0.1-2
ii  python3-scrypt 0.8.20-2+b1
ii  python3-sqlalchemy 1.4.31+ds1-1
ii  python3-stevedore  4.0.2-2
ii  python3-tz 2022.6-1
ii  python3-webob  1:1.8.6-3

python3-keystone recommends no packages.

python3-keystone suggests no packages.


-- 
pozdrawiam / best regards
Wojtek Porczyk
Gramine / Invisible Things Lab
 
 I do not fear computers,
 I fear lack of them.
-- Isaac Asimov


signature.asc
Description: PGP signature


Bug#1026161: Removal notice: obsolete

2022-12-15 Thread Ilias Tsitsimpis
Source: haskell-ekg-json
Version: 0.1.0.6-7
Severity: serious

I intend to remove this package. It's a dependency of haskell-ekg, which
we plan on removing (see #1026158).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1026160: Removal notice: unused library

2022-12-15 Thread Ilias Tsitsimpis
Source: haskell-ekg-core
Version: 0.1.1.7-2
Severity: serious

I intend to remove this package. It's a dependency of haskell-ekg, which
we plan on removing (see #1026158).

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias



Bug#1024547: ITP: sparrow -- Bitcoin wallet with a focus on privacy and usability

2022-12-15 Thread Craig Raw
I would appreciate some guidance on how to proceed. The documentation says 
"package the software, upload it and close this bug once the package has been 
installed". The software is already available in the .deb format for amd64 and 
arm64 architectures:

https://github.com/sparrowwallet/sparrow/releases/download/1.7.1/sparrow_1.7.1-1_amd64.deb
https://github.com/sparrowwallet/sparrow/releases/download/1.7.1/sparrow_1.7.1-1_arm64.deb

I assume the next step is to upload these two files, but I'm uncertain of where 
or how to do this.

Thanks,
Craig




Bug#1023972: python-ase: FTBFS with Python 3.11 due to pathlib.Path.__enter__() deprecation

2022-12-15 Thread Andrius Merkys

On Sun, 13 Nov 2022 13:12:15 +0200 Andrius Merkys  wrote:
python-ase/3.22.1 FTBFS with the following after Python 3.11 support has 
been added:


DeprecationWarning: pathlib.Path.__enter__() is deprecated and scheduled 
for removal in Python 3.13; Path objects as a context manager is a no-op


I have forwarded this upstream.


A month has passed without any action from the upstream. Now the issue 
is of severity:serious. If threatened by autoremoval, one possibility to 
resolve it might be ignoring the warning for the time being:


import warnings
warnings.filterwarnings("ignore", category=DeprecationWarning)

Source: 
https://stackoverflow.com/questions/879173/how-to-ignore-deprecation-warnings-in-python


Haven't tested if this indeed works yet.

Andrius



Bug#1002501: release-notes: Quotes (" and ') in commands in PDF release notes are "smart" (”*” / ’hold$’) so don't copy/paste

2022-12-15 Thread Paul Gevers

Control: tag -1 help

Hi Alan,

Thanks for your report.

On 23-12-2021 12:34, alan wrote:

As the subject says really. Quotes (" and ') in commands in the PDF Release
Notes are "smart"/slanted (e.g. ”*” / ’hold$’) so when commands are copied from
the pdf and pasted into a shell, they don't work. It's necessary to edit the
command to put "straight" quotes into the command instead.

(Annoying and unnecessary!)

PDF I used: "Release Notes for Debian 11 (bullseye), 64-bit PC | December 14, 
2021"


The release notes are generated with docbook. I spend about an hour to 
find out how to prevent conversion of straight quotes to curly quotes, 
but I failed. I don't know how to fix this bug. The html version get it 
right, so I expect the issue to be in how LaTeX is called. If anybody 
knows how docbook and LaTeX work together and how to fix it, much 
appreciated.


Paul

I tried replacing " with  and  but both were still converted 
to curly quotes.


Paul


OpenPGP_signature
Description: OpenPGP digital signature


  1   2   >